Setting up Devices for Prime Collaboration Assurance - Revision history

Ramyab: /* Required Protocols for the Devices (Includes Supported Software Versions) */

2013-06-15T08:48:36Z

Required Protocols for the Devices (Includes Supported Software Versions)

← Older revision		Revision as of 08:48, 15 June 2013
Line 101:		Line 101:
	\| -<br>		\| -<br>
	\|		\|
-	* Cisco Unified CM 9.1(1) is supported on Cisco Prime Collaboration Assurance 9.0.0.24376. If you are using Cisco Prime Collaboration Assurance 9.0.0-21354, upgrade to Cisco Prime Collaboration Assurance 9.0.0.24376. See [http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/release/notes/pc_rn.html#wp51296 ''Cisco Prime Collaboration Release Notes, 9.0''] for upgrade procedure.	+	* Cisco Unified CM 9.1(1) is supported on Cisco Prime Collaboration Assurance 9.0.0.24376. If you are using Cisco Prime Collaboration Assurance 9.0.0.21354, upgrade to Cisco Prime Collaboration Assurance 9.0.0.24376. See [http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/release/notes/pc_rn.html#wp51296 ''Cisco Prime Collaboration Release Notes, 9.0''] for upgrade procedure.
	*Prime Collaboration supports Cisco Unified CM clusters. You must ensure that the cluster IDs are unique. To verify the cluster ID go to the Enterprise Parameteres Configuration page (System > Enterprise Parameters) on Cisco Unified CM publisher (for every cluster).		*Prime Collaboration supports Cisco Unified CM clusters. You must ensure that the cluster IDs are unique. To verify the cluster ID go to the Enterprise Parameteres Configuration page (System > Enterprise Parameters) on Cisco Unified CM publisher (for every cluster).
	*The same credentials must be created for all devices in the cluster whenever clustering is used.		*The same credentials must be created for all devices in the cluster whenever clustering is used.

Ramyab: /* Required Protocols for the Devices (Includes Supported Software Versions) */

2013-06-14T17:31:54Z

Required Protocols for the Devices (Includes Supported Software Versions)

← Older revision		Revision as of 17:31, 14 June 2013
Line 101:		Line 101:
	\| -<br>		\| -<br>
	\|		\|
-	* Cisco Unified CM 9.1(1) is supported on Cisco Prime Assurance 9.0.0.24376. If you are using Cisco Prime Assurance 9.0.0-21354, upgrade to Cisco Prime Assurance 9.0.0.24376. See [http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/release/notes/pc_rn.html#wp51296 ''Cisco Prime Collaboration Release Notes, 9.0''] for upgrade procedure.	+	* Cisco Unified CM 9.1(1) is supported on Cisco Prime Collaboration Assurance 9.0.0.24376. If you are using Cisco Prime Collaboration Assurance 9.0.0-21354, upgrade to Cisco Prime Collaboration Assurance 9.0.0.24376. See [http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/release/notes/pc_rn.html#wp51296 ''Cisco Prime Collaboration Release Notes, 9.0''] for upgrade procedure.
	*Prime Collaboration supports Cisco Unified CM clusters. You must ensure that the cluster IDs are unique. To verify the cluster ID go to the Enterprise Parameteres Configuration page (System > Enterprise Parameters) on Cisco Unified CM publisher (for every cluster).		*Prime Collaboration supports Cisco Unified CM clusters. You must ensure that the cluster IDs are unique. To verify the cluster ID go to the Enterprise Parameteres Configuration page (System > Enterprise Parameters) on Cisco Unified CM publisher (for every cluster).
	*The same credentials must be created for all devices in the cluster whenever clustering is used.		*The same credentials must be created for all devices in the cluster whenever clustering is used.

Ramyab: /* Required Protocols for the Devices (Includes Supported Software Versions) */

2013-06-14T17:27:15Z

Required Protocols for the Devices (Includes Supported Software Versions)

← Older revision		Revision as of 17:27, 14 June 2013
Line 100:		Line 100:
	\| -<br>		\| -<br>
	\| -<br>		\| -<br>
-	\|	+	\|
		+	* Cisco Unified CM 9.1(1) is supported on Cisco Prime Assurance 9.0.0.24376. If you are using Cisco Prime Assurance 9.0.0-21354, upgrade to Cisco Prime Assurance 9.0.0.24376. See [http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/release/notes/pc_rn.html#wp51296 ''Cisco Prime Collaboration Release Notes, 9.0''] for upgrade procedure.
	*Prime Collaboration supports Cisco Unified CM clusters. You must ensure that the cluster IDs are unique. To verify the cluster ID go to the Enterprise Parameteres Configuration page (System > Enterprise Parameters) on Cisco Unified CM publisher (for every cluster).		*Prime Collaboration supports Cisco Unified CM clusters. You must ensure that the cluster IDs are unique. To verify the cluster ID go to the Enterprise Parameteres Configuration page (System > Enterprise Parameters) on Cisco Unified CM publisher (for every cluster).
	*The same credentials must be created for all devices in the cluster whenever clustering is used.		*The same credentials must be created for all devices in the cluster whenever clustering is used.

Ramyab: /* Required Protocols for the Devices (Includes Supported Software Versions) */

2013-06-14T17:08:13Z

Required Protocols for the Devices (Includes Supported Software Versions)

← Older revision		Revision as of 17:08, 14 June 2013
Line 93:		Line 93:
	\|-		\|-
	\| Cisco Unified CM<br>		\| Cisco Unified CM<br>
-	\| 7.1 – 9.0<br>	+	\| 7.1 – 9.1(1)<br>
	\| Yes<br>		\| Yes<br>
	\| Yes<br>		\| Yes<br>
Line 104:		Line 104:
	*The same credentials must be created for all devices in the cluster whenever clustering is used.		*The same credentials must be created for all devices in the cluster whenever clustering is used.
	*The JTAPI user needs to have these roles Standard AXL API Access, CCM Admin Users, SERVICEABILITY Administration, CTI Enabled, and CTI Allow Call Monitoring.		*The JTAPI user needs to have these roles Standard AXL API Access, CCM Admin Users, SERVICEABILITY Administration, CTI Enabled, and CTI Allow Call Monitoring.
-	*The session monitoring feature is supported only on Cisco Unified CM 8.5~~, 8.6 and 9.0~~.<br>	+	*The session monitoring feature is supported only from Cisco Unified CM 8.5 release onwards.<br>

	\|-		\|-
Line 278:		Line 278:
	\| End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration.<br>		\| End-to-end troubleshooting is not supported. However, the path trace can be discovered from the first-hop-router (FHR) if router CLI access is provided for Prime Collaboration.<br>
	\|-		\|-
-	\| Cisco Presence <br>	+	\| Cisco Unified Presence <br>
-	\| 8.0 - 9.0 <br>	+	\| 8.0 - 9.1 <br>
	\| Yes<br>		\| Yes<br>
	\| Yes<br>		\| Yes<br>
Line 286:		Line 286:
	\| -<br>		\| -<br>
	\| -<br>		\| -<br>
-	\| ~~<br>~~	+	\|Cisco Unified Presence 9.1 is supported through [http://software.cisco.com/download/type.html?mdfid=284259889&flowid=36842 ''Cisco Prime Collaboration Assurance 9.0 patch 2''].
	\|-		\|-
	\| Network devices (routers and switches) <br>		\| Network devices (routers and switches) <br>
Line 349:		Line 349:
	\|-		\|-
	\| Cisco Unity Connection		\| Cisco Unity Connection
-	\| 7.0 - 9.0	+	\| 7.0 - 9.1
	\| Yes<br>		\| Yes<br>
	\| Yes<br>		\| Yes<br>
Line 356:		Line 356:
	\| -<br>		\| -<br>
	\| -<br>		\| -<br>
-	\| ~~<br>~~	+	\| Cisco Unified Connection 9.1 is supported through [http://software.cisco.com/download/type.html?mdfid=284259889&flowid=36842 ''Cisco Prime Collaboration Assurance 9.0 patch 2''].
	\|-		\|-
	\| Cisco Unity Express		\| Cisco Unity Express

Vkasinat: /* Cisco Unified Communications Manager */

2013-05-30T11:05:55Z

Cisco Unified Communications Manager

← Older revision		Revision as of 11:05, 30 May 2013
Line 527:		Line 527:
	#Choose '''Tools > CDR Management'''.		#Choose '''Tools > CDR Management'''.
	#Scroll down to Application Billing Server Parameters and click '''Add New'''. <br> Enter the following:		#Scroll down to Application Billing Server Parameters and click '''Add New'''. <br> Enter the following:
-	#* Host Name / IP Address: Enter the IP address of the system where Prime Collaboration is installed.	+	#* Host Name / IP Address - Enter the IP address of the system where Prime Collaboration is installed.
-	#* User Name: Enter smuser. Do not enter any username other than smuser.	+	#* User Name - Enter smuser. Do not enter any username other than smuser.
-	#* Password: Enter a password. The default password is smuser. <br> To change this password, change it in Prime Collaboration first. Enter the same password that you entered for smuser while configuring other settings in Prime Collaboration. If you changed the password in Prime Collaboration and Cisco Unified Communications Manager does not immediately accept the new password, wait one minute and enter the new password again.	+	#* Password - Enter a password. The default password is smuser. <br> To change this password, change it in Prime Collaboration first. Enter the same password that you entered for smuser while configuring other settings in Prime Collaboration. If you changed the password in Prime Collaboration and Cisco Unified Communications Manager does not immediately accept the new password, wait one minute and enter the new password again.
	#* Select SFTP Protocol.		#* Select SFTP Protocol.
-	#* Directory Path: Enter /home/smuser/.	+	#* Directory Path - Enter /home/smuser/.
-	#* Resend on Failure (Displayed in Cisco Unified Communications Manager 7.0 and later): Select this check box.	+	#* Resend on Failure (Displayed in Cisco Unified Communications Manager 7.0 and later) - Select this check box.
-	#Click Add.	+	#Click '''Add'''.

	'''Changing the Password for smuser in Cisco Unified Communications Manager 6.x and Later'''		'''Changing the Password for smuser in Cisco Unified Communications Manager 6.x and Later'''

Vkasinat: /* Cisco Unified Communications Manager */

2013-05-30T08:28:49Z

Cisco Unified Communications Manager

← Older revision		Revision as of 08:28, 30 May 2013
Line 519:		Line 519:
	and for the JTAPI-related issues using https://<primecollaboration-ip>/emsam/log/Tomcat/CUCMJTAPIDiag.log		and for the JTAPI-related issues using https://<primecollaboration-ip>/emsam/log/Tomcat/CUCMJTAPIDiag.log
	</pre>		</pre>
		+
		+	'''Adding Prime Collaboration to Cisco Unified Communications Manager 6.x and Later as a Billing Server'''
		+
		+	'''Note:''' Perform this task on Cisco Unified Communications Manager version 6.x and later only. Perform this task only while Prime Collaboration is up and running.
		+
		+	#Launch Unified Communications Manager Serviceability.
		+	#Choose '''Tools > CDR Management'''.
		+	#Scroll down to Application Billing Server Parameters and click '''Add New'''. <br> Enter the following:
		+	#* Host Name / IP Address: Enter the IP address of the system where Prime Collaboration is installed.
		+	#* User Name: Enter smuser. Do not enter any username other than smuser.
		+	#* Password: Enter a password. The default password is smuser. <br> To change this password, change it in Prime Collaboration first. Enter the same password that you entered for smuser while configuring other settings in Prime Collaboration. If you changed the password in Prime Collaboration and Cisco Unified Communications Manager does not immediately accept the new password, wait one minute and enter the new password again.
		+	#* Select SFTP Protocol.
		+	#* Directory Path: Enter /home/smuser/.
		+	#* Resend on Failure (Displayed in Cisco Unified Communications Manager 7.0 and later): Select this check box.
		+	#Click Add.
		+
		+	'''Changing the Password for smuser in Cisco Unified Communications Manager 6.x and Later'''
		+
		+	Perform this task as needed on Cisco Unified Communications Manager versions 6.x and later only.
		+
		+	The SFTP password for smuser in Prime Collaboration and the password for the Application Billing Server smuser in Cisco Unified Communications Manager 6.x and later must be identical. Any time you change one, you must change the other to match.
		+
		+	Use this procedure to change the password for the Application Billing Server smuser in Cisco Unified Communications Manager 6.x and later.
		+
		+	#Launch Unified Communications Manager Serviceability.
		+	#Select '''Tools > CDR Manageability'''.
		+	#Scroll down to Application Billing Server Parameters and double-click the link for Prime Collaboration. <br> Enter a new password. If you changed the password in Prime Collaboration and Cisco Unified Communications Manager does not immediately accept the new password, wait one minute and enter the new password again. Do not change the values in any other fields; Host Name / IP Address, User Name, SFTP Protocol, and Directory Path must remain the same.
		+	#Click '''Update'''.
		+
	== Cisco TelePresence Video Communication Server <br> ==		== Cisco TelePresence Video Communication Server <br> ==

Stevchiu: /* Cisco TelePresence C and EX Series Video Endpoints */

2013-04-10T02:53:04Z

Cisco TelePresence C and EX Series Video Endpoints

← Older revision		Revision as of 02:53, 10 April 2013
Line 592:		Line 592:
	SSH must be enabled by default on TC 4.0 releases. Provide '''admin''' user access to Cisco Prime Collaboration ensure that the admin password is set and is not the default value, which is blank. Admin user access is necessary if you want to troubleshoot video sessions from Cisco TelePresence devices using Cisco Prime Collaboration. Some of the commands required to run the traceroutes are available only when you log in as root.		SSH must be enabled by default on TC 4.0 releases. Provide '''admin''' user access to Cisco Prime Collaboration ensure that the admin password is set and is not the default value, which is blank. Admin user access is necessary if you want to troubleshoot video sessions from Cisco TelePresence devices using Cisco Prime Collaboration. Some of the commands required to run the traceroutes are available only when you log in as root.

-	We recommend that you enter the real interface IP address of the gateway that runs the Hot Standby Router Protocol (HSRP), instead of the virtual IP address, while configuring the CTS. This enables Prime Collaborationto accurately discover the troubleshooting path.	+	We recommend that you enter the real interface IP address of the gateway that runs the Hot Standby Router Protocol (HSRP), instead of the virtual IP address, while configuring the CTS. This enables Prime Collaborationto accurately discover the troubleshooting path.
-		+
-	~~Endpoint monitoring is based on the SNMP polling. You can configure traps and syslogs on the endpoints, if required.~~	+
-		+
-	~~To monitor traps and syslogs:~~	+
-		+
-	*Configure trap and syslog receivers for endpoints in call processors.	+
-	*Enter the Prime Collaboration IP address to configure the trap receiver: <PrimeCollaboration_ip_addr>	+
-	*Enter the Prime Collaboration IP address and port number 20514 to configure syslog receiver.: <PrimeCollaboration_ip_addr>:20514.	+
-	*Enable endpoints to send traps and syslogs.	+
-		+
-	~~To enable traps:~~	+
-		+
-	*In CISCO-TELEPRESENCE-MIB, set ctpPeripheralErrorNotifyEnable to true (1)	+
-	*In CISCO-TELEPRESENCE-CALL-MIB, set ctpcStatNotifyEnable to true (1)	+
-	*In CISCO-TELEPRESENCE-CALL-MIB, set threshold values for call stats ctpcStatMonitoredEntry	+
-		+
-	~~To enable syslogs: In CISCO-SYSLOG-MIB, set clogNotificationsEnabled to true (1)~~.	+

	= Configuring Call Management Applications =		= Configuring Call Management Applications =

Stevchiu: /* Cisco TelePresence System Video Endpoints */

2013-04-10T02:52:18Z

Cisco TelePresence System Video Endpoints

← Older revision		Revision as of 02:52, 10 April 2013
Line 558:		Line 558:
	before the specified interval, for anyone or any application to be able to perform SSH		before the specified interval, for anyone or any application to be able to perform SSH
	in the device including Cisco Prime Collaboration. </pre>		in the device including Cisco Prime Collaboration. </pre>
		+
		+	Endpoint monitoring is based on the SNMP polling. You can configure traps and syslogs on the endpoints, if required.
		+
		+	To monitor traps and syslogs:
		+
		+	*Configure trap and syslog receivers for endpoints in call processors.
		+	*Enter the Prime Collaboration IP address to configure the trap receiver: <PrimeCollaboration_ip_addr>
		+	*Enter the Prime Collaboration IP address and port number 20514 to configure syslog receiver.: <PrimeCollaboration_ip_addr>:20514.
		+	*Enable endpoints to send traps and syslogs.
		+
		+	To enable traps:
		+
		+	*In CISCO-TELEPRESENCE-MIB, set ctpPeripheralErrorNotifyEnable to true (1)
		+	*In CISCO-TELEPRESENCE-CALL-MIB, set ctpcStatNotifyEnable to true (1)
		+	*In CISCO-TELEPRESENCE-CALL-MIB, set threshold values for call stats ctpcStatMonitoredEntry
		+
		+	To enable syslogs: In CISCO-SYSLOG-MIB, set clogNotificationsEnabled to true (1).
		+
	== Cisco TelePresence C and EX Series Video Endpoints ==		== Cisco TelePresence C and EX Series Video Endpoints ==

Stevchiu: /* Required Protocols for the Devices (Includes Supported Software Versions) */

2013-04-09T16:08:55Z

Required Protocols for the Devices (Includes Supported Software Versions)

← Older revision		Revision as of 16:08, 9 April 2013
Line 65:		Line 65:
	\| The HTTP user account must have both the Meeting Manager and Diagnostic Technician roles.<br>		\| The HTTP user account must have both the Meeting Manager and Diagnostic Technician roles.<br>
	\|-		\|-
-	\| Cisco TelePresence System <br>	+	\| Cisco TelePresence System (CTS) <br>
	\| 1.7 – 1.9<br>		\| 1.7 – 1.9<br>
	\| Yes<br>		\| Yes<br>
Line 71:		Line 71:
	\| Yes<br>		\| Yes<br>
	\| -		\| -
-	\| ~~Yes~~<br>	+	\| <br>
	\| -<br>		\| -<br>
	\|		\|

Ramyab: /* Required Protocols for the Devices (Includes Supported Software Versions) */

2013-04-01T16:47:55Z

Required Protocols for the Devices (Includes Supported Software Versions)

← Older revision		Revision as of 16:47, 1 April 2013
Line 101:		Line 101:
	\| -<br>		\| -<br>
	\|		\|
		+	*Prime Collaboration supports Cisco Unified CM clusters. You must ensure that the cluster IDs are unique. To verify the cluster ID go to the Enterprise Parameteres Configuration page (System > Enterprise Parameters) on Cisco Unified CM publisher (for every cluster).
	*The same credentials must be created for all devices in the cluster whenever clustering is used.		*The same credentials must be created for all devices in the cluster whenever clustering is used.
	*The JTAPI user needs to have these roles Standard AXL API Access, CCM Admin Users, SERVICEABILITY Administration, CTI Enabled, and CTI Allow Call Monitoring.		*The JTAPI user needs to have these roles Standard AXL API Access, CCM Admin Users, SERVICEABILITY Administration, CTI Enabled, and CTI Allow Call Monitoring.