Setting up Devices on the Network for Prime Collaboration Manager - Revision history

Ramyab at 18:23, 30 October 2012

2012-10-30T18:23:59Z

← Older revision		Revision as of 18:23, 30 October 2012
Line 291:		Line 291:
	== Configuring Cisco Mediatrace, Cisco IOS IP SLA, and Performance Monitoring for Network Devices ==		== Configuring Cisco Mediatrace, Cisco IOS IP SLA, and Performance Monitoring for Network Devices ==

-	If you have enabled Cisco Mediatrace on your network nodes, Cisco Prime CM provides Medianet Path View as part of the troubleshooting data. If you have enabled Cisco IOS IP Service Level Agreements (SLAs) on your network nodes, you can measure the network performance and health using the Proactive Troubleshooting feature.	+	If you have enabled [http://www.cisco.com/web/solutions/medianet/knowledgebase/index.html#~configure Cisco Mediatrace] on your network nodes, Cisco Prime CM provides Medianet Path View as part of the troubleshooting data. If you have enabled Cisco IOS IP Service Level Agreements (SLAs) on your network nodes, you can measure the network performance and health using the Proactive Troubleshooting feature.

	For Cisco Mediatrace:		For Cisco Mediatrace:
Line 297:		Line 297:
	*Enable the initiator and/or responder roles on relevant routers and switches using the following commands:<br>'''For Mediatrace Initiator''': <br>		*Enable the initiator and/or responder roles on relevant routers and switches using the following commands:<br>'''For Mediatrace Initiator''': <br>

-	<br>	+	<br>
-	<pre>mediatrace initiator source-ip ''IP Address''</pre>	+	<pre>mediatrace initiator source-ip ''IP Address''</pre>
-	<br>'''For Mediatrace Responder''': <br>	+	<br>'''For Mediatrace Responder''': <br>

-	<br>	+	<br>
	<pre>mediatrace responder		<pre>mediatrace responder
-	</pre>	+	</pre>
-	<br>	+	<br>

	*Configure a Telnet local login user with privilege 15 on the initiators.		*Configure a Telnet local login user with privilege 15 on the initiators.
-	*Configure Web Services Management Agent (WSMA) over HTTP or HTTPS on the initiators.	+	*Configure Web Services Management Agent (WSMA) over HTTP or HTTPS on the initiators. See ''Web Services Management Agent (WSMA) Configuration Guide'' for details on the configuration commands.<br>

-	'''Local Auth Example''': <br>	+	'''Local Auth Example''': <br>
	<pre>username <username> priv 15 secret <username_enable_password>		<pre>username <username> priv 15 secret <username_enable_password>
	ip http authentication local		ip http authentication local

-	</pre>	+	</pre>
	'''For WSMA (HTTP) Configuration''':		'''For WSMA (HTTP) Configuration''':
-	<pre>	+	<pre>ip http server
-	ip http server	+
	ip http timeout-policy idle 60 life 86400 requests 10000		ip http timeout-policy idle 60 life 86400 requests 10000
	wsma agent exec profile wsma_listener_http		wsma agent exec profile wsma_listener_http
Line 322:		Line 321:
	!		!
	wsma profile listener wsma_listener_http		wsma profile listener wsma_listener_http
-	transport http</pre>	+	transport http</pre>
-		+
	'''For WSMA (HTTPS) Configuration''':		'''For WSMA (HTTPS) Configuration''':

-		+	<br>
	<pre>ip http secure-server		<pre>ip http secure-server
	wsma agent exec profile wsma_listener_https		wsma agent exec profile wsma_listener_https
Line 334:		Line 332:
	transport https		transport https

		+	</pre>
		+	'''For WSMA SSH Configuration''':<br>
		+	<pre>crypto key generate rsa
		+	ip ssh timeout 120
		+	ip ssh version 2
		+	!
		+	wsma agent exec profile wsma_listener_ssh
		+	wsma agent config profile wsma_listener_ssh
		+	!
		+	wsma profile listener wsma_listener_ssh
		+	transport ssh
	</pre>		</pre>
	For Cisco IOS IP Service Level agreement (SLA):		For Cisco IOS IP Service Level agreement (SLA):
Line 340:		Line 349:
	<pre>ip sla responder		<pre>ip sla responder

-	</pre>	+	</pre>
	*The initiator role is not required. <br>		*The initiator role is not required. <br>
	*Configure a Telnet local login user with privilege 15 on the IP SLA initiators.		*Configure a Telnet local login user with privilege 15 on the IP SLA initiators.

Aakhter: /* Configuring Cisco Mediatrace, Cisco IOS IP SLA, and Performance Monitoring for Network Devices */

2012-07-05T03:22:10Z

Configuring Cisco Mediatrace, Cisco IOS IP SLA, and Performance Monitoring for Network Devices

← Older revision		Revision as of 03:22, 5 July 2012
Line 295:		Line 295:
	For Cisco Mediatrace:		For Cisco Mediatrace:

-	*Enable the initiator and/or responder roles on relevant routers and switches using the following commands:<br>'''For Mediatrace Initiator''': mediatrace initiator source-ip ''IP Address''<br>'''For Mediatrace Responder''': mediatrace responder<br>	+	*Enable the initiator and/or responder roles on relevant routers and switches using the following commands:<br>'''For Mediatrace Initiator''': <br>
		+
		+	<br>
		+	<pre>mediatrace initiator source-ip ''IP Address''</pre>
		+	<br>'''For Mediatrace Responder''': <br>
		+
		+	<br>
		+	<pre>mediatrace responder
		+	</pre>
		+	<br>
		+
	*Configure a Telnet local login user with privilege 15 on the initiators.		*Configure a Telnet local login user with privilege 15 on the initiators.
	*Configure Web Services Management Agent (WSMA) over HTTP or HTTPS on the initiators.		*Configure Web Services Management Agent (WSMA) over HTTP or HTTPS on the initiators.

-	'''Local Auth Example''':	+	'''Local Auth Example''': <br>
-	<br>~~username~~ <username> priv 15 secret <username_enable_password~~> <br>~~	+	<pre>username <username> priv 15 secret <username_enable_password>
-	ip http authentication local~~<br>~~	+	ip http authentication local

		+	</pre>
	'''For WSMA (HTTP) Configuration''':		'''For WSMA (HTTP) Configuration''':
-	<br>ip http server~~<br>~~ip http timeout-policy idle 60 life 86400 requests 10000~~<br>~~	+	<pre>
-	wsma agent exec profile wsma_listener_http~~<br>~~wsma agent config profile wsma_listener_http~~<br>~~!~~<br>~~wsma profile listener wsma_listener_http~~<br>~~transport http	+	ip http server
		+	ip http timeout-policy idle 60 life 86400 requests 10000
		+	wsma agent exec profile wsma_listener_http
		+	wsma agent config profile wsma_listener_http
		+	!
		+	wsma profile listener wsma_listener_http
		+	transport http</pre>

	'''For WSMA (HTTPS) Configuration''':		'''For WSMA (HTTPS) Configuration''':

-	~~ip http secure-server<br>~~
-	~~wsma agent exec profile wsma_listener_https<br>wsma agent config profile wsma_listener_https<br>!<br>wsma profile listener wsma_listener_https <br>transport https<br><br>~~

		+	<pre>ip http secure-server
		+	wsma agent exec profile wsma_listener_https
		+	wsma agent config profile wsma_listener_https
		+	!
		+	wsma profile listener wsma_listener_https
		+	transport https
		+
		+	</pre>
	For Cisco IOS IP Service Level agreement (SLA):		For Cisco IOS IP Service Level agreement (SLA):

-	*Enable the responder role using the command:<br> ip sla responder<br>The initiator role is not required. <br>	+	*Enable the responder role using the command:<br>
		+	<pre>ip sla responder
		+
		+	</pre>
		+	*The initiator role is not required. <br>
	*Configure a Telnet local login user with privilege 15 on the IP SLA initiators.		*Configure a Telnet local login user with privilege 15 on the IP SLA initiators.

Aakhter: /* Configuring Cisco Mediatrace, Cisco IOS IP SLA, and Performance Monitoring for Network Devices */

2012-07-05T03:18:42Z

Configuring Cisco Mediatrace, Cisco IOS IP SLA, and Performance Monitoring for Network Devices

← Older revision		Revision as of 03:18, 5 July 2012
Line 299:		Line 299:
	*Configure Web Services Management Agent (WSMA) over HTTP or HTTPS on the initiators.		*Configure Web Services Management Agent (WSMA) over HTTP or HTTPS on the initiators.

-	'''~~For WSMA (HTTP) Configuration~~''':	+	'''Local Auth Example''':
		+	<br>username <username> priv 15 secret <username_enable_password> <br>
		+	ip http authentication local<br>

		+	'''For WSMA (HTTP) Configuration''':
		+	<br>ip http server<br>ip http timeout-policy idle 60 life 86400 requests 10000<br>
	wsma agent exec profile wsma_listener_http<br>wsma agent config profile wsma_listener_http<br>!<br>wsma profile listener wsma_listener_http<br>transport http		wsma agent exec profile wsma_listener_http<br>wsma agent config profile wsma_listener_http<br>!<br>wsma profile listener wsma_listener_http<br>transport http

	'''For WSMA (HTTPS) Configuration''':		'''For WSMA (HTTPS) Configuration''':

		+	ip http secure-server<br>
	wsma agent exec profile wsma_listener_https<br>wsma agent config profile wsma_listener_https<br>!<br>wsma profile listener wsma_listener_https <br>transport https<br><br>		wsma agent exec profile wsma_listener_https<br>wsma agent config profile wsma_listener_https<br>!<br>wsma profile listener wsma_listener_https <br>transport https<br><br>

Ramyab at 11:53, 2 July 2012

2012-07-02T11:53:09Z

← Older revision		Revision as of 11:53, 2 July 2012
Line 297:		Line 297:
	*Enable the initiator and/or responder roles on relevant routers and switches using the following commands:<br>'''For Mediatrace Initiator''': mediatrace initiator source-ip ''IP Address''<br>'''For Mediatrace Responder''': mediatrace responder<br>		*Enable the initiator and/or responder roles on relevant routers and switches using the following commands:<br>'''For Mediatrace Initiator''': mediatrace initiator source-ip ''IP Address''<br>'''For Mediatrace Responder''': mediatrace responder<br>
	*Configure a Telnet local login user with privilege 15 on the initiators.		*Configure a Telnet local login user with privilege 15 on the initiators.
-	*Configure Web Services Management Agent (WSMA) ~~and the IP~~ HTTP or ~~IP ~~HTTPS ~~server~~ on the initiators.	+	*Configure Web Services Management Agent (WSMA) over HTTP or HTTPS on the initiators.

	'''For WSMA (HTTP) Configuration''':		'''For WSMA (HTTP) Configuration''':

Ramyab at 11:47, 2 July 2012

2012-07-02T11:47:38Z

← Older revision		Revision as of 11:47, 2 July 2012
Line 31:		Line 31:
	#*Standard AXL API Access		#*Standard AXL API Access
	#*Standard CCM Admin Users		#*Standard CCM Admin Users
-	#*Standard SERVICEABILITY Administration	+	#*Standard SERVICEABILITY Administration
	#Click '''Save'''.		#Click '''Save'''.
	#From the main menu, navigate to '''User Management''' > '''Application Users''' > '''Create a new user'''. <br>Specify a suitable password on the '''Application User Configuration''' page. You can select only certain type of devices from the Available Devices text area, or allow Cisco Prime Collaboration Manager to monitor all devices.		#From the main menu, navigate to '''User Management''' > '''Application Users''' > '''Create a new user'''. <br>Specify a suitable password on the '''Application User Configuration''' page. You can select only certain type of devices from the Available Devices text area, or allow Cisco Prime Collaboration Manager to monitor all devices.
Line 62:		Line 62:
	#*Standard CTI Allow Call Monitoring		#*Standard CTI Allow Call Monitoring
	#*Standard CTI Enabled		#*Standard CTI Enabled
-	#*Standard CTI Allow Control of Phones supporting Connected Xfer and conf	+	#*Standard CTI Allow Control of Phones supporting Connected Xfer and conf
	#Click '''Save'''.		#Click '''Save'''.
	#From the main menu, navigate to '''User Management''' > '''Application Users''' > '''Create a new user'''. <br>Specify a suitable password on the '''Application User Configuration''' page. You can select only certain type of devices from the Available Devices text area, or allow Cisco Prime Collaboration Manager to monitor all devices. <br>'''Note''': The password must not contain a semicolon (;) or equals (=).		#From the main menu, navigate to '''User Management''' > '''Application Users''' > '''Create a new user'''. <br>Specify a suitable password on the '''Application User Configuration''' page. You can select only certain type of devices from the Available Devices text area, or allow Cisco Prime Collaboration Manager to monitor all devices. <br>'''Note''': The password must not contain a semicolon (;) or equals (=).
Line 76:		Line 76:
	*Check the following log to verify if the endpoints are CTI-controlled in the CUCM		*Check the following log to verify if the endpoints are CTI-controlled in the CUCM
	and such JTAPI-related issues:[https://<cpcm-ip>/emsam/log/Tomcat/CUCMJTAPIDiag.log]		and such JTAPI-related issues:[https://<cpcm-ip>/emsam/log/Tomcat/CUCMJTAPIDiag.log]
-	</pre>	+	</pre>
	----		----

Line 117:		Line 117:
	However, if the value is not zero, the admin must ensure that passwords are changed		However, if the value is not zero, the admin must ensure that passwords are changed
	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 Manager. </pre>	+	in the device including Cisco Prime Collaboration Manager. </pre>
-		+
	=== Cisco TelePresence C and EX Series Video Endpoints ===		=== Cisco TelePresence C and EX Series Video Endpoints ===

Line 142:		Line 141:

	*Configure trap and syslog receivers for endpoints in call processors.		*Configure trap and syslog receivers for endpoints in call processors.
-	*Enter the Cisco Prime CM IP address to configure the trap receiver: <~~emsam_ip_addr~~>	+	*Enter the Cisco Prime CM IP address to configure the trap receiver: <PrimeCM_ip_addr>
-	*Enter the Cisco Prime CM IP address and port number 20514 to configure syslog receiver.: <~~emsam_ip_addr~~>:20514.	+	*Enter the Cisco Prime CM IP address and port number 20514 to configure syslog receiver.: <PrimeCM_ip_addr>:20514.
	*Enable endpoints to send traps and syslogs.		*Enable endpoints to send traps and syslogs.

Line 192:		Line 191:
	We recommend that you review the Getting Started With TelePresence Reporting API		We recommend that you review the Getting Started With TelePresence Reporting API
	document available at [http://developer.cisco.com/web/tra/start] for an understanding		document available at [http://developer.cisco.com/web/tra/start] for an understanding
-	of the Reporting API.</pre>	+	of the Reporting API.</pre>
	To enable Cisco Prime CM server to retrieve scheduled meetings from from CTS-Manager 1.8:		To enable Cisco Prime CM server to retrieve scheduled meetings from from CTS-Manager 1.8:

Line 206:		Line 205:
	After creating the user account in CTS-Manager for the Prime CM application, we recommend		After creating the user account in CTS-Manager for the Prime CM application, we recommend
	that you log in with this account in CTS-Manager at least once before you enter the		that you log in with this account in CTS-Manager at least once before you enter the
-	credentials in the Prime CM server.</pre>	+	credentials in the Prime CM server.</pre>
-		+
	== Configuring Cisco TMS Third Party Booking API User ==		== Configuring Cisco TMS Third Party Booking API User ==

Line 218:		Line 216:
	*For Cisco TMS 13.2 and later, any HTTP user can be used to retrieve scheduled meetings		*For Cisco TMS 13.2 and later, any HTTP user can be used to retrieve scheduled meetings
	from Cisco TMS server. In addition, you do not need to install a Booking API License to		from Cisco TMS server. In addition, you do not need to install a Booking API License to
-	use the API.</pre>	+	use the API.</pre>
	To enable Cisco Prime CM server to retrieve scheduled meetings from Cisco TMS:		To enable Cisco Prime CM server to retrieve scheduled meetings from Cisco TMS:

Line 227:		Line 225:
	#*encPassword - A base64 encoded password that is to be used for the newly created user. To encode the password to base64, we recommend <br>that you use the web utility available at the following URL: http://www.motobit.com/util/base64-decoder-encoder.asp.		#*encPassword - A base64 encoded password that is to be used for the newly created user. To encode the password to base64, we recommend <br>that you use the web utility available at the following URL: http://www.motobit.com/util/base64-decoder-encoder.asp.
	#*emailAddress - The email address of the user. Do not enter values in this field.		#*emailAddress - The email address of the user. Do not enter values in this field.
-	#*sendNotifications - To allow the user to receive scheduling notifications. You must enter False in this field since Cisco Prime CM <br>will be polling from Cisco TMS.	+	#*sendNotifications - To allow the user to receive scheduling notifications. You must enter False in this field since Cisco Prime CM <br>will be polling from Cisco TMS.
	#Click '''Invoke'''.		#Click '''Invoke'''.
	#In the Cisco TMS application, verify the user name configured in Step 3<font color="#0000ff"></font>is listed in the Users page.		#In the Cisco TMS application, verify the user name configured in Step 3<font color="#0000ff"></font>is listed in the Users page.
Line 237:		Line 235:
	For more information about the Cisco TMS, see the documents available at [[Www.tandberg.com/support/tms documentation.jsp\|TANDBERG]] site.		For more information about the Cisco TMS, see the documents available at [[Www.tandberg.com/support/tms documentation.jsp\|TANDBERG]] site.

-	For more information on creating groups and setting permission to the group, see ''Ciso Telepresence Management Suite Administrator Guide''.	+	For more information on creating groups and setting permission to the group, see ''Ciso Telepresence Management Suite Administrator Guide''.

	== Configuring MCUs ==		== Configuring MCUs ==
Line 290:		Line 288:
	that you log in with this account in CTMS at least once before you enter the		that you log in with this account in CTMS at least once before you enter the
	credentials in the Prime CM server.		credentials in the Prime CM server.
-	</pre>	+	</pre>
-		+
	== Configuring Cisco Mediatrace, Cisco IOS IP SLA, and Performance Monitoring for Network Devices ==		== Configuring Cisco Mediatrace, Cisco IOS IP SLA, and Performance Monitoring for Network Devices ==

Line 298:		Line 295:
	For Cisco Mediatrace:		For Cisco Mediatrace:

-	*Enable the initiator and/or responder roles on relevant routers and switches.	+	*Enable the initiator and/or responder roles on relevant routers and switches using the following commands:<br>'''For Mediatrace Initiator''': mediatrace initiator source-ip ''IP Address''<br>'''For Mediatrace Responder''': mediatrace responder<br>
	*Configure a Telnet local login user with privilege 15 on the initiators.		*Configure a Telnet local login user with privilege 15 on the initiators.
-	*Configure Web Services Management Agent (WSMA) and the IP HTTP server on the initiators.	+	*Configure Web Services Management Agent (WSMA) and the IP HTTP or IP HTTPS server on the initiators.
		+
		+	'''For WSMA (HTTP) Configuration''':
		+
		+	wsma agent exec profile wsma_listener_http<br>wsma agent config profile wsma_listener_http<br>!<br>wsma profile listener wsma_listener_http<br>transport http
		+
		+	'''For WSMA (HTTPS) Configuration''':
		+
		+	wsma agent exec profile wsma_listener_https<br>wsma agent config profile wsma_listener_https<br>!<br>wsma profile listener wsma_listener_https <br>transport https<br><br>

	For Cisco IOS IP Service Level agreement (SLA):		For Cisco IOS IP Service Level agreement (SLA):

-	*Enable the responder role. The initiator role is not required.	+	*Enable the responder role using the command:<br> ip sla responder<br>The initiator role is not required. <br>
	*Configure a Telnet local login user with privilege 15 on the IP SLA initiators.		*Configure a Telnet local login user with privilege 15 on the IP SLA initiators.

Chetrao at 13:51, 14 June 2012

2012-06-14T13:51:20Z

← Older revision		Revision as of 13:51, 14 June 2012
Line 287:		Line 287:
	<pre>Note:		<pre>Note:
	Replace snmpro and snmprw with your SNMP Read and Read/Write community strings.		Replace snmpro and snmprw with your SNMP Read and Read/Write community strings.
-	After creating the user account in CTMS for the Prime CM application, we recommend ~~that~~	+	After creating the user account in CTMS for the Prime CM application, we recommend
-	you log in with this account in CTMS at least once before you enter the ~~credentials~~	+	that you log in with this account in CTMS at least once before you enter the
-	in the Prime CM server.	+	credentials in the Prime CM server.
	</pre>		</pre>

Chetrao at 13:49, 14 June 2012

2012-06-14T13:49:19Z

← Older revision		Revision as of 13:49, 14 June 2012
Line 212:		Line 212:
	For the Cisco Prime CM server to retrieve scheduled meetings from Cisco TMS server 13.0 and Cisco TMS server 13.1, you must have one Application Integration License for each server that uses the API.		For the Cisco Prime CM server to retrieve scheduled meetings from Cisco TMS server 13.0 and Cisco TMS server 13.1, you must have one Application Integration License for each server that uses the API.
	<pre>Note:		<pre>Note:
-	*We recommend that you review the Cisco TMS Third Party Booking API document available at	+	*We recommend that you review the Cisco TMS Third Party Booking API document available
-	[http://www.tandberg.com/support/tms_documentation.jsp] for an understanding of the Booking API.	+	at [http://www.tandberg.com/support/tms_documentation.jsp] for an understanding of the
		+	Booking API.

-	*For Cisco TMS 13.2 and later, any HTTP user can be used to retrieve scheduled meetings ~~from~~	+	*For Cisco TMS 13.2 and later, any HTTP user can be used to retrieve scheduled meetings
-	Cisco TMS server. In addition, you do not need to install a Booking API License to use the API.</pre>	+	from Cisco TMS server. In addition, you do not need to install a Booking API License to
		+	use the API.</pre>
	To enable Cisco Prime CM server to retrieve scheduled meetings from Cisco TMS:		To enable Cisco Prime CM server to retrieve scheduled meetings from Cisco TMS:

Chetrao at 13:47, 14 June 2012

2012-06-14T13:47:48Z

← Older revision		Revision as of 13:47, 14 June 2012
Line 190:		Line 190:
	For Cisco Prime CM server to retrieve scheduled meetings from from CTS-Manager 1.8, you must have a valid Metrics Dashboard and Reporting API license in CTS-Manager. This user account should be configured in Active Directory with a mailbox and in a user group with general security. The Active Directory user group should be assigned the '''Reporting API '''role and the '''Live Desk '''role in the CTS-Manager Access Management page.		For Cisco Prime CM server to retrieve scheduled meetings from from CTS-Manager 1.8, you must have a valid Metrics Dashboard and Reporting API license in CTS-Manager. This user account should be configured in Active Directory with a mailbox and in a user group with general security. The Active Directory user group should be assigned the '''Reporting API '''role and the '''Live Desk '''role in the CTS-Manager Access Management page.
	<pre>Note:		<pre>Note:
-	We recommend that you review the Getting Started With TelePresence Reporting API ~~document~~	+	We recommend that you review the Getting Started With TelePresence Reporting API
-	available at [http://developer.cisco.com/web/tra/start] for an understanding	+	document available at [http://developer.cisco.com/web/tra/start] for an understanding
	of the Reporting API.</pre>		of the Reporting API.</pre>
	To enable Cisco Prime CM server to retrieve scheduled meetings from from CTS-Manager 1.8:		To enable Cisco Prime CM server to retrieve scheduled meetings from from CTS-Manager 1.8:
Line 204:		Line 204:
	For more information about user and group configuration in LDAP server, <font color="#0000ff"></font>see ''Cisco Telepresense Manager 1.8 Administration and Installation Guide''<font color="#0000ff">.</font>		For more information about user and group configuration in LDAP server, <font color="#0000ff"></font>see ''Cisco Telepresense Manager 1.8 Administration and Installation Guide''<font color="#0000ff">.</font>
	<pre>Note:		<pre>Note:
-	After creating the user account in CTS-Manager for the Prime CM application, we recommend ~~that~~	+	After creating the user account in CTS-Manager for the Prime CM application, we recommend
-	you log in with this account in CTS-Manager at least once before you enter the ~~credentials~~	+	that you log in with this account in CTS-Manager at least once before you enter the
-	in the Prime CM server.</pre>	+	credentials in the Prime CM server.</pre>

	== Configuring Cisco TMS Third Party Booking API User ==		== Configuring Cisco TMS Third Party Booking API User ==

Chetrao at 13:42, 14 June 2012

2012-06-14T13:42:59Z

← Older revision		Revision as of 13:42, 14 June 2012
Line 113:		Line 113:
	SSH access to the Cisco TelePresence Server devices is also controlled through Cisco Unified Communications Manager Phone Configuration.		SSH access to the Cisco TelePresence Server devices is also controlled through Cisco Unified Communications Manager Phone Configuration.
	<pre>Note:		<pre>Note:
-	If the value of SSH admin Life and SSH helpdesk Life field is zero, the password never ~~expires~~	+	If the value of SSH admin Life and SSH helpdesk Life field is zero, the password never
-	(recommended for lab testing scenarios).	+	expires (recommended for lab testing scenarios).
-	However, if the value is not zero, the admin must ensure that passwords are changed ~~before~~	+	However, if the value is not zero, the admin must ensure that passwords are changed
-	the specified interval, for anyone or any application to be able to perform SSH in the device	+	before the specified interval, for anyone or any application to be able to perform SSH
-	including Cisco Prime Collaboration Manager. </pre>	+	in the device including Cisco Prime Collaboration Manager. </pre>

	=== Cisco TelePresence C and EX Series Video Endpoints ===		=== Cisco TelePresence C and EX Series Video Endpoints ===

Chetrao at 13:41, 14 June 2012

2012-06-14T13:41:49Z

← Older revision		Revision as of 13:41, 14 June 2012
Line 74:		Line 74:
	to configure the application user.		to configure the application user.

-	*Check the following log to verify if the endpoints are CTI-controlled	+	*Check the following log to verify if the endpoints are CTI-controlled in the CUCM
-	in the CUCM and such JTAPI-related issues:[https://<cpcm-ip>/emsam/log/Tomcat/CUCMJTAPIDiag.log]	+	and such JTAPI-related issues:[https://<cpcm-ip>/emsam/log/Tomcat/CUCMJTAPIDiag.log]
	</pre>		</pre>
	----		----