Setting up Devices for Prime Collaboration Assurance

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m
(Supported Software Versions for the Cisco Medianet Feature)
(12 intermediate revisions not shown)
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>
|  
|  
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 100: Line 100:
| -<br>
| -<br>
| -<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.
 +
*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 &gt; 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.  
-
*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 277: Line 279:
| 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 285: Line 287:
| -<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 348: Line 350:
|-
|-
| Cisco Unity Connection  
| Cisco Unity Connection  
-
| 7.0 - 9.0
+
| 7.0 - 9.1
| Yes<br>
| Yes<br>
| Yes<br>
| Yes<br>
Line 355: Line 357:
| -<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  
Line 439: Line 441:
|-
|-
-
| Border Element, Gatekeeper, H323 Gateway, SIP Gateway MGCP Gateway, SRST Device, Voice Gateway, CUBE<br>
+
| Border Element, Gatekeeper, H323 Gateway, SIP Gateway MGCP Gateway, SRST Device, Voice Gateway<br>
| IOS 12.x or later<br>
| IOS 12.x or later<br>
| -<br>
| -<br>
Line 448: Line 450:
| -<br>
| -<br>
| <br>
| <br>
-
|-
 
-
| Cisco TelePresence Exchange
 
-
| 1.2
 
-
| Yes
 
-
| Yes
 
-
| -
 
-
| -
 
-
| -
 
-
| -
 
-
|
 
-
|-
 
-
| CUBE/SBC
 
-
| -
 
-
| Yes
 
-
|
 
-
|
 
-
|
 
-
|
 
-
|
 
-
|
 
|}
|}
Line 478: Line 460:
All CTS endpoints must be added as controlled devices in Cisco Unified CM to facilitate call detection. You must configure a HTTP and JTAPI user on the call processor.  
All CTS endpoints must be added as controlled devices in Cisco Unified CM to facilitate call detection. You must configure a HTTP and JTAPI user on the call processor.  
-
'''Note''': The procedures described below are applicable for Cisco Unified CM 8.5. If you are using any other supported versions, see the [http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html ''Cisco Unified CM guides''] to understand how to create groups, users and assign roles to them.<br>  
+
'''Note''': The procedures described below are applicable for Cisco Unified CM 8.5. If you are using any other supported versions, see the [http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html ''Cisco Unified CM guides''] to understand how to create groups, users and assign roles to them.<br>
'''Enable HTTP'''  
'''Enable HTTP'''  
Line 492: Line 474:
#*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''' &gt; '''Application Users''' &gt; '''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 to monitor all devices.  
#From the main menu, navigate to '''User Management''' &gt; '''Application Users''' &gt; '''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 to monitor all devices.  
Line 523: Line 505:
#*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''' &gt; '''Application Users''' &gt; '''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 to monitor all devices. <br>'''Note''': The password must not contain a semicolon (;) or equals (=).  
#From the main menu, navigate to '''User Management''' &gt; '''Application Users''' &gt; '''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 to monitor all devices. <br>'''Note''': The password must not contain a semicolon (;) or equals (=).  
Line 537: Line 519:
You can access the log files to verify whether the endpoints are assisned with the CTI-controlled roles in the Unified CM
You can access the log files to verify whether the endpoints are assisned with the CTI-controlled roles in the Unified CM
and for the JTAPI-related issues using https://&lt;primecollaboration-ip&gt;/emsam/log/Tomcat/CUCMJTAPIDiag.log
and for the JTAPI-related issues using https://&lt;primecollaboration-ip&gt;/emsam/log/Tomcat/CUCMJTAPIDiag.log
-
</pre>  
+
</pre>
-
== Cisco TelePresence Video Communication Server <br> ==
+
 
 +
'''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 VCS serves as a call-control appliance for the Cisco TelePresence C Series, E Series, and other similar video endpoints.  
Cisco VCS serves as a call-control appliance for the Cisco TelePresence C Series, E Series, and other similar video endpoints.  
Line 576: Line 587:
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. </pre>  
+
in the device including Cisco Prime Collaboration. </pre>
-
== Cisco TelePresence C and EX Series Video Endpoints  ==
+
-
 
+
-
'''Enable HTTP'''
+
-
 
+
-
By default, HTTP is enabled for Cisco TelePresence Endpoints. Point the web browser to http://&lt;ip_address&gt;, where &lt;ip_address&gt; is the IP address or hostname of the video endpoint. The default password for the administrator user '''admin''' is " ", blank space.
+
-
 
+
-
'''Enable SNMP'''
+
-
 
+
-
To enable SNMP access for Cisco Prime Collaboration from the web interface:
+
-
 
+
-
Navigate to '''Configuration''' &gt; '''Adv Configuration''' &gt; '''Network Services''' &gt; '''SNMP''' and click the value to edit.
+
-
 
+
-
'''Enable CLI Access'''
+
-
 
+
-
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.
+
Endpoint monitoring is based on the SNMP polling. You can configure traps and syslogs on the endpoints, if required.  
Endpoint monitoring is based on the SNMP polling. You can configure traps and syslogs on the endpoints, if required.  
Line 610: Line 604:
*In CISCO-TELEPRESENCE-CALL-MIB, set threshold values for call stats ctpcStatMonitoredEntry
*In CISCO-TELEPRESENCE-CALL-MIB, set threshold values for call stats ctpcStatMonitoredEntry
-
To enable syslogs: In CISCO-SYSLOG-MIB, set clogNotificationsEnabled to true (1).  
+
To enable syslogs: In CISCO-SYSLOG-MIB, set clogNotificationsEnabled to true (1).
 +
 
 +
== Cisco TelePresence C and EX Series Video Endpoints  ==
 +
 
 +
'''Enable HTTP'''
 +
 
 +
By default, HTTP is enabled for Cisco TelePresence Endpoints. Point the web browser to http://&lt;ip_address&gt;, where &lt;ip_address&gt; is the IP address or hostname of the video endpoint. The default password for the administrator user '''admin''' is " ", blank space.
 +
 
 +
'''Enable SNMP'''
 +
 
 +
To enable SNMP access for Cisco Prime Collaboration from the web interface:
 +
 
 +
Navigate to '''Configuration''' &gt; '''Adv Configuration''' &gt; '''Network Services''' &gt; '''SNMP''' and click the value to edit.
 +
 
 +
'''Enable CLI Access'''
 +
 
 +
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.
= Configuring Call Management Applications  =
= Configuring Call Management Applications  =
Line 650: Line 662:
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>
-
'''Note''': The procedures described below are applicable for CTS-Manager 1.8. If you are using any other supported versions, see the CTS-Manager Reporting API related documents.<br>  
+
'''Note''': The procedures described below are applicable for CTS-Manager 1.8. If you are using any other supported versions, see the CTS-Manager Reporting API related documents.<br>
To enable Prime Collaboration server to retrieve scheduled meetings from from CTS-Manager 1.8:  
To enable Prime Collaboration server to retrieve scheduled meetings from from CTS-Manager 1.8:  
Line 666: Line 678:
After creating the user account in CTS-Manager for the Prime Collaboration application, we recommend  
After creating the user account in CTS-Manager for the Prime Collaboration 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 Collaboration server.</pre>  
+
credentials in the Prime Collaboration server.</pre>
== Cisco TMS Third Party Booking API User  ==
== Cisco TMS Third Party Booking API User  ==
Line 677: Line 689:
*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 Prime Collaboration server to retrieve scheduled meetings from Cisco TMS:  
To enable Prime Collaboration server to retrieve scheduled meetings from Cisco TMS:  
Line 686: Line 698:
#*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 Prime Collaboration<br>will be polling from Cisco TMS.  
+
#*sendNotifications - To allow the user to receive scheduling notifications. You must enter False in this field since Prime Collaboration<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 724: Line 736:
'''Enable HTTP'''  
'''Enable HTTP'''  
-
A separate HTTP user account must be created with the Meeting Scheduler and Diagnostic Technician roles assigned to it for the Prime Collaboration application. This user can be configured in the Multipoint Switch web user interface when logged in as admin. After the dedicated HTTP user has been created, you must login to CTMS web UI using this user credential and then change the password (the same password can be entered).
+
A separate HTTP user account must be created with the Meeting Scheduler and Diagnostic Technician roles assigned to it for the Prime Collaboration application. This user can be configured in the Multipoint Switch web user interface when logged in as admin. After the dedicated HTTP user has been created, you must login to CTMS web UI using this user credential and then change the password (the same password can be entered).  
An '''admin''' user is not required by Cisco Prime Collaboration to manage the Multipoint Switch.  
An '''admin''' user is not required by Cisco Prime Collaboration to manage the Multipoint Switch.  
Line 750: Line 762:
credentials in the Prime Collaboration server.
credentials in the Prime Collaboration 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 759: Line 770:
*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. See ''Web Services Management Agent (WSMA) Configuration Guide'' for details on the configuration commands.<br>
*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 &lt;username&gt; priv 15 secret &lt;username_enable_password&gt;
<pre>username &lt;username&gt; priv 15 secret &lt;username_enable_password&gt;
ip http authentication local
ip http authentication local
-
</pre>  
+
</pre>
'''For WSMA (HTTP) Configuration''':  
'''For WSMA (HTTP) Configuration''':  
<pre>ip http server
<pre>ip http server
Line 783: Line 794:
!
!
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>  
+
<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 794: Line 805:
transport https
transport https
-
</pre>  
+
</pre>
-
'''For WSMA SSH Configuration''':<br>  
+
'''For WSMA SSH Configuration''':<br>
<pre>crypto key generate rsa
<pre>crypto key generate rsa
ip ssh timeout 120
ip ssh timeout 120
Line 805: Line 816:
wsma profile listener wsma_listener_ssh
wsma profile listener wsma_listener_ssh
transport ssh
transport ssh
-
</pre>  
+
</pre>
For Cisco IOS IP Service Level agreement (SLA):  
For Cisco IOS IP Service Level agreement (SLA):  
Line 811: Line 822:
<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.
Line 821: Line 832:
Configure the Performance Monitor policy on the relevant interfaces. Prime Collaboration collects PM flow statistics through MIBs. If this is configured, Prime Collaboration does not require the CLI access to routers.  
Configure the Performance Monitor policy on the relevant interfaces. Prime Collaboration collects PM flow statistics through MIBs. If this is configured, Prime Collaboration does not require the CLI access to routers.  
-
== Supported Software Versions for the Cisco Medianet Feature<br> ==
+
== Supported Software Versions for the Cisco Medianet Feature<br> ==
-
<br>  
+
<br>
-
{| width="800" cellspacing="1" cellpadding="1" border="1"
+
{| border="1" cellspacing="1" cellpadding="1" width="800"
|-
|-
-
| '''Platform'''<br>  
+
| '''Platform'''<br>
-
| '''Minimum IOS Release'''<br>  
+
| '''Minimum IOS Release'''<br>
-
| '''Minimum Package'''<br>  
+
| '''Minimum Package'''<br>
| '''Feature Support'''<br>
| '''Feature Support'''<br>
|-
|-
-
| Catalyst 3560<br>  
+
| Catalyst 3560<br>
-
| 15.0(1)SE2<br>  
+
| 15.0(1)SE2<br>
-
| IP Base<br>  
+
| IP Base<br>
| Mediatrace, Performance Monitor, IPSLA-VO<br>
| Mediatrace, Performance Monitor, IPSLA-VO<br>
|-
|-
-
| Catalyst 3750<br>  
+
| Catalyst 3750<br>
-
| 15.0(1)SE2<br>  
+
| 15.0(1)SE2<br>
-
| IP Base<br>  
+
| IP Base<br>
| Mediatrace, Performance Monitor, IPSLA-VO<br>
| Mediatrace, Performance Monitor, IPSLA-VO<br>
|-
|-
-
| Catalyst 4500E Supervisor 7-E/7L-E<br>  
+
| Catalyst 4500E Supervisor 7-E/7L-E<br>
-
| XE 3.3.0SG<br>  
+
| XE 3.3.0SG<br>
-
| IP Base<br>  
+
| IP Base<br>
| Mediatrace, Performance Monitor, IPSLA-VO<br>
| Mediatrace, Performance Monitor, IPSLA-VO<br>
|-
|-
-
| Catalyst 4500E Supervisor 6-E/6L-E<br>  
+
| Catalyst 4500E Supervisor 6-E/6L-E<br>
-
| 15.1(1)SG<br>  
+
| 15.1(1)SG<br>
-
| IP Base<br>  
+
| IP Base<br>
| Mediatrace, Performance Monitor, IPSLA-VO<br>
| Mediatrace, Performance Monitor, IPSLA-VO<br>
|-
|-
-
| Catalyst 6500 Supervisor 2T<br>  
+
| Catalyst 6500 Supervisor 2T<br>
-
| 15.0(1)SY<br>  
+
| 15.0(1)SY<br>
-
| IP Services<br>  
+
| IP Services<br>
| Mediatrace, Performance Monitor<br>
| Mediatrace, Performance Monitor<br>
|-
|-
-
| ISR 2900 and 3900<br>  
+
| ISR 2900 and 3900<br>
-
| 15.1(3)T<br>  
+
| 15.1(3)T<br>
-
| UC and Data<br>  
+
| UC and Data<br>
| Mediatrace, Performance Monitor<br>
| Mediatrace, Performance Monitor<br>
|-
|-
-
| <br>  
+
| <br>
-
| 15.2(2)T<br>  
+
| 15.2(2)T<br>
-
| UC and DSP<br>  
+
| UC and DSP<br>
| IPSLA-VO Sender<br>
| IPSLA-VO Sender<br>
|-
|-
-
| <br>  
+
| <br>
-
| 15.2(2)T<br>  
+
| 15.2(2)T<br>
-
| IP Base<br>  
+
| IP Base<br>
| IPSLA-VO Responder<br>
| IPSLA-VO Responder<br>
|-
|-
-
| ISR 1900<br>  
+
| ISR 1900<br>
-
| 15.1(3)T<br>  
+
| 15.1(3)T<br>
-
| UC and Data<br>  
+
| UC and Data<br>
| Mediatrace, Performance Monitor<br>
| Mediatrace, Performance Monitor<br>
|-
|-
-
| <br>  
+
| <br>
-
| 15.2(2)T<br>  
+
| 15.2(2)T<br>
-
| IP Base<br>  
+
| IP Base<br>
| IPSLA-VO Responder<br>
| IPSLA-VO Responder<br>
|-
|-
-
| ISR 880 and 890<br>  
+
| ISR 880 and 890<br>
-
| 15.1(3)T<br>  
+
| 15.1(3)T<br>
-
| Universal<br>  
+
| Universal<br>
| Mediatrace, Performance Monitor<br>
| Mediatrace, Performance Monitor<br>
|-
|-
-
| ASR 1000<br>  
+
| ASR 1000<br>
-
| XE 3.5<br>  
+
| XE 3.5<br>
-
| IP Base<br>  
+
| IP Base<br>
| Performance Monitor<br>
| Performance Monitor<br>
|}
|}
-
<br>  
+
<br>
----
----
-
<br>  
+
<br>
-
<br>  
+
<br>
-
<br>  
+
<br>
-
<br>  
+
<br>
-
<br>  
+
<br>
-
<br>  
+
<br>
-
<br>  
+
<br>
-
[[Category:Cisco_Prime_Collaboration_9_0]]
+
[[Category:Cisco_Prime_Collaboration]]

Revision as of 16:43, 18 July 2013

This section describes how to configure devices on the network before you manage them in Cisco Prime Collaboration Assurance.

Contents

Required Protocols for the Devices (Includes Supported Software Versions)

You must configure the endpoints, application managers, call processors, multipoint switches, and network devices with the following protocols:

  • HTTP - Access the device through HTTP to poll system status and meeting information.
  • SNMP - Read Community String and SNMP Authentication Protocol (SNMP V2 or SNMP V3) - Discover and manage the device.
  • CLI - Access the device through CLI to discover media path for troubleshooting.
  • JTAPI - Retrieve the session status information frosm the Cisco Unified CM.
  • CDP - Discover neighboring devices.


Device
Supported Software
SNMP
HTTP
CLI
JTAPI
MSI
CDP
Notes
Analog Gateway
-
Yes
-
-
-
-
-

Contact Center Enterprise
7.0 - 9.0
Yes
-
-
-
-
-

Contact Center Express
4.6 - 9.0
Yes
-
-
-
-
-

Cisco TelePresence Multipoint Switch
1.7 – 1.9
Yes
Yes
-
-
-
-
The HTTP user account must have both the Meeting Manager and Diagnostic Technician roles.
Cisco TelePresence System (CTS)
1.7 – 1.9
Yes
-
Yes
-
-
  • CLI access is required if you want to use the Troubelshooting feature in Prime Collaboration. HTTP access is not required.
  • The HTTP credentials (helpdesk role) are same as the SSH credentials, which are required by Prime Collaboration to troubleshoot.
Cisco TelePresence Manager (CTS-Manager)
1.7 – 1.9
Yes
Yes
-
-
-
-
  • Requires the Reporting API license and the Reporting API role for the Prime Collaboration user.
  • The HTTP user needs to be an exchange mailbox user and its User Group must have Reporting API and Live Desk roles in CTS-Manager.
  • If you have installed a licensed version of Prime Collaboration, it is mandatory to configure the CTS-Manager Reporting API. If this feature is not configured on the CTS-Manager 1.7, 1.8, or 1.9, Prime Collaboration will not manage the CTS-Manager.
Cisco Unified CM
7.1 – 9.1(1)
Yes
Yes
-
Yes
-
-
  • 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 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).
  • 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 session monitoring feature is supported only from Cisco Unified CM 8.5 release onwards.
Cisco Unified Communications Manager Business Edition
7.1 – 9.0
Yes
Yes
-
Yes
-
-

Customer Voice Portal
4.0 - 8.5
Yes
-
-
-
-
-

  • Cisco Codec EX series
  • Cisco TelePresence System Integrator C Series
  • Cisco TelePresence MX Series
  • Cisco TelePresence System Profile Series
  • Cisco TelePresence SX20 Quick Set
  • Cisco TX 9000 series
  • EX series:
    TC 4.2 - 6.0; TE 6.0
  • C, MX, and SX series:
    TC 4.2 - 6.0
  • TX series: TX 6.0
Yes
Yes
Yes
-
Yes
-
  • The HTTP user requires Admin privilege.
  • For TC 6.0 and TE 6.0, use the same HTTP credentials for MSI.
  • For TX 6.0, use the default credentials msiuser and cisco for MSI.
Cisco IP Video Phone E20
TE 4.0 - 6.0
Yes
Yes
Yes
-
Yes
-
  • 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.
  • Use the same HTTP credentials for MSI.
Emergency Responder
1.0 - 9.0
Yes
-
-
-
-
-

Expert Advisor
7.2 - 7.6
Yes
-
-
-
-
-

Finesse
8.0 - 9.0
Yes
-
-
-
-
-

Cisco MCU
4.1 – 4.3
Yes
Yes
-
-
-
-
  • The HTTP user requires Admin privilege.
  • This device also include the MSE8000 blade form factors: MSE-8420, MSE-8510, and MSE-8710.
Cisco TelePresence MSE Supervisor
2.1 – 2.2
Yes
Yes
-
-
-
-
The HTTP user requires Admin privilege.
Mediasense
8.0 - 9.0
Yes
-
-
-
-
-

Meeting Place
7.0 - 8.5
Yes
-
-
-
-
-

Meeting Place Express
2.0 - 2.1
Yes
-
-
-
-
-

Personal Assistant
1.3 -1.4
-
-
-
-
-
-

Cisco TelePresence System MXP series
9.1
Yes
Yes
Yes




Polycom VSX series
Polycom HDX series
2.5 - 3.0
(for HDX series)
9.0
(for VSX series)
Yes
-
-
-
-
-
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.
Cisco Unified Presence
8.0 - 9.1
Yes
Yes
-
-
-
-
Cisco Unified Presence 9.1 is supported through Cisco Prime Collaboration Assurance 9.0 patch 2.
Network devices (routers and switches)

Yes
-
Yes
-
-
Yes
  • CDP needs to be enabled for the video Troubleshooting workflow. The Telnet or SSH access is required for Cisco Medianet features, which is part if the video Troubleshooting workflow.
  • See the table Supported Software Versions for the Cisco Medianet Feature below to view the troubleshooting medianet-related data.
Cisco TelePresence Management Suite (Cisco TMS)
13.0 – 13.2

Yes
Yes
-
-
-
-
  • Requires Booking API license (TMS software version 13.1 or below).
  • The HTTP user for Prime Collaboration needs to be generated through the Booking API on the Cisco TMS windows server.
  • Prime Collaboration supports only the default e-mail template for the Booking Confirm e-mail in Cisco TMS. The session import feature will not work, if the default e-mail template is not used.
Cisco Telepresence Server
2.1 – 2.2
-
Yes
-
-
-
-
  • The HTTP user account should have the API Access privilege.
  • This device also include the MSE8000 blade form factors: MSE-8420, MSE-8510, MSE-8710.
Cisco Telepresence Conductor
1.1 - 1.2
Yes
Yes
-
-
-
-

Cisco Unity 7.0 - 8.6 Yes
-
-
-
-
-

Cisco Unity Connection 7.0 - 9.1 Yes
Yes
-
-
-
-
Cisco Unified Connection 9.1 is supported through Cisco Prime Collaboration Assurance 9.0 patch 2.
Cisco Unity Express 7.0 - 9.0 Yes
-
-
-
-
-

Cisco TelePresence Video Communication Server (Control and Expressway)
6.0 – 7.1
Yes
Yes
-
-
-
-
The HTTP user requires Admin privilege.
Wireless
-
Yes
-
Yes
-
-
-

Third party devices
-
Yes
-
-
-
-
-

Cisco Jabber Video for Telepresence (Movi)
all software versions.
-
-
-
-
-
-
  • The Cisco Jabber endpoints are discovered either through Cisco Unified CM or Cisco VCS (access credentials are not required).
  • 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.
Cisco Cius
all software versions.
-
-
-
-
-
-
  • The Cisco Cius endpoints are discovered either through Cisco Unified CM or Cisco VCS (access credentials are not required). You must enable web access in Cisco Unified CM for these.
  • Credentials are not required for HTTP access.
  • 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.
Cisco IP phones (89xx, 99xx)
all software versions.
-
-
-
-
-
-
  • The Cisco IP Phones endpoints are discovered through Cisco Unified CM. You must enable web access in Cisco Unified CM for these.
  • These video phones require Cisco Unified CM application user to have the additional role Standard CTI Allow Control of Phones supporting Connected Xfer and conf.
  • Credentials are not required for HTTP access.
  • 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.
Border Element, Gatekeeper, H323 Gateway, SIP Gateway MGCP Gateway, SRST Device, Voice Gateway
IOS 12.x or later
-
-
-
-
-
-


Configuring Call Controllers and Processors

Cisco Unified Communications Manager

All CTS endpoints must be added as controlled devices in Cisco Unified CM to facilitate call detection. You must configure a HTTP and JTAPI user on the call processor.

Note: The procedures described below are applicable for Cisco Unified CM 8.5. If you are using any other supported versions, see the Cisco Unified CM guides to understand how to create groups, users and assign roles to them.

Enable HTTP

You do not have to create a new user if you want to allow Cisco Prime Collaboration to use admin credentials to log in. Alternatively, if you want to allow Cisco Prime Collaboration Manager to use the right credentials to log in to Cisco Unified Communications Manager, you must create a new HTTP user group and a corresponding user that Cisco Prime Collaboration can use to communicate.

To create a user:

  1. Create a user group with sufficient privileges. Log in to the Cisco Unified Communications Manager Administration web interface using the administrator role.
  2. Navigate to User Management > User Groups and create a new group with a suitable name, PC_HTTP_Users in this case.
  3. Click Role.
  4. Click Assign Role to Group and select the following roles:
    • Standard AXL API Access
    • Standard CCM Admin Users
    • Standard SERVICEABILITY Administration
  5. Click Save.
  6. From the main menu, navigate to User Management > Application Users > Create a new user.
    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 to monitor all devices.
  7. In the Permission Information section, click Add to User Group and select the group that was created in Step 1. (PC_HTTP_Users, for instance).
  8. Click Save. The page is refreshed and the right privileges are displayed.

Enable SNMP

SNMP is not enabled in Cisco Unified Communications Manager by default.

To enable SNMP:

  1. Log in to the Cisco Unified Serviceability view in the Cisco Unified Communications Manager web GUI.
  2. From the main menu in the Cisco Unified Serviceability view, navigate to SNMP > v1/v2c > community string.
  3. Select a Server and click Find.
    If the community string is already defined, the Community String Name is displayed in the Search Results.
  4. Click Add new to add a new string if no results are displayed.
  5. Specify the required SNMP information and save the configuration.

Enable JTAPI

JTAPI (Java Telephony API) is used to retrieve the session status information from the device. You must create a JTAPI user in the call processor with the required permission to receive JTAPI events on endpoints. Prime Collaboration manages multiple call processor clusters. You must ensure that the cluster IDs are unique. Create a new JTAPI user to help Cisco Prime Collaboration get the required information.

To create a new JTAPI user:

  1. Log in to the Cisco Unified Communications Manager administration web interface using administrator role.
  2. Navigate to User Management > User Groups and create a new group with a suitable name, PC_HTTP_Users in this case.
  3. Move all endpoint devices (for example, Cisco TelePresence codecs) to the Controlled Devices table.
  4. Click Roles.
  5. Click Assign Role to Group and select the following roles:
    • Standard CTI Allow Call Monitoring
    • Standard CTI Enabled
    • Standard CTI Allow Control of Phones supporting Connected Xfer and conf
  6. Click Save.
  7. From the main menu, navigate to User Management > Application Users > Create a new user.
    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 to monitor all devices.
    Note: The password must not contain a semicolon (;) or equals (=).
  8. In the Permission Information section, click Add to User Group and select the group that was created in step 1. (PC_HTTP_Users, for instance).
  9. Click Save. The page is refreshed and the right privileges are displayed.
Note:
*Ensure the following services are activated and started: 
 **Cisco CTIManager 
 **Cisco AXL Web Service
 See the Cisco Unified Communications Manager guide for details about how 
 to configure the application user.

You can access the log files to verify whether the endpoints are assisned with the CTI-controlled roles in the Unified CM
and for the JTAPI-related issues using https://<primecollaboration-ip>/emsam/log/Tomcat/CUCMJTAPIDiag.log

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.

  1. Launch Unified Communications Manager Serviceability.
  2. Choose Tools > CDR Management.
  3. Scroll down to Application Billing Server Parameters and click Add New.
    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.
      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.
  4. 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.

  1. Launch Unified Communications Manager Serviceability.
  2. Select Tools > CDR Manageability.
  3. Scroll down to Application Billing Server Parameters and double-click the link for Prime Collaboration.
    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.
  4. Click Update.

Cisco TelePresence Video Communication Server

Cisco VCS serves as a call-control appliance for the Cisco TelePresence C Series, E Series, and other similar video endpoints.

Enable HTTP

You can access Cisco VCS through a web browser: http://<vcs_serveraddress>, where <vcs_serveraddress> is the IP address or hostname of your VCS appliance. The default password for administrator user admin is TANDBERG. If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully manage the VCS. Ensure the password field is not blank as it is not recommended.

Enable SNMP

You can easily enable SNMP from the Cisco VCS web GUI: Navigate to System > SNMP and enter the SNMP information.

Configuring Endpoints

Cisco TelePresence System Video Endpoints

Enable HTTP

You can access Cisco TelePresence system video endpoints through a web browser (preferably using Internet Explorer, if possible) by pointing the browser to:https://<serveraddress> where <serveraddress> is the IP address or hostname of the Cisco TelePresence system video endpoint.

Enable SNMP

SNMP for Cisco TelePresence system devices is configured using Cisco Unified Communications Manager phone configuration. To change the SNMP community string:

  1. Navigate to Cisco Unified Communications Manager Administration.
  2. Navigate to Device > Phone and search for Cisco TelePresence system endpoints.
  3. Click the Device Name link to go to the phone configuration page.
  4. Edit the SNMP Configuration Parameters.
  5. Click Save and Apply Config.

Enable CLI Access

SSH access to the Cisco TelePresence system devices is also controlled through Cisco Unified Communications Manager Phone Configuration.

Note:
If the value of SSH admin Life and SSH helpdesk Life field is zero, the password never 
expires (recommended for lab testing scenarios). 
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 
in the device including Cisco Prime Collaboration. 

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

Enable HTTP

By default, HTTP is enabled for Cisco TelePresence Endpoints. Point the web browser to http://<ip_address>, where <ip_address> is the IP address or hostname of the video endpoint. The default password for the administrator user admin is " ", blank space.

Enable SNMP

To enable SNMP access for Cisco Prime Collaboration from the web interface:

Navigate to Configuration > Adv Configuration > Network Services > SNMP and click the value to edit.

Enable CLI Access

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.

Configuring Call Management Applications

Cisco TelePresence Management Suite

HTTP and SNMP access are required to successfully monitor Cisco TMS.

Enable HTTP

Cisco TMS is accessed through a web browser (http://<serveraddress>/TMS), where <serveraddress> is the IP address or hostname of your server. The default password for the administrator user admin is TANDBERG.

If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully monitor Cisco TMS.

Enable SNMP

By default, public and Public are enabled as SNMP Read Only (RO) community strings for Cisco TMS. This string is used by Cisco TMS to poll other devices.

If you need to add or change these strings:

Go to the web GUI and navigate to Administrative Tools > Configuration > Network Settings and change the SNMP settings.

In addition to the Web GUI, SNMP service on the Cisco TMS server must be enabled.

To enable SNMP:

  1. Go to Start on the server console.
  2. Click Run and specify services.msc.
    A Service window will pop open on the server console.
  3. Right-click SNMP Service and select Properties.
  4. Click Security and select Add new SNMP string.
    Do not modify the default selection: Accept SNMP packets from any host unless you want only specific hosts polling SNMP from Cisco TMS.
  5. Optionally, click Traps to add the IP address of Cisco Prime Collaboration and a community string. This address is used in SNMP traps.
  6. Optionally, click Agent to specify SNMP contact and location for Cisco TMS. The Cisco Prime Collaboration uses this information to display the location of Cisco TMS in the inventory.
  7. Restart the SNMP Service after the necessary modifications.

Reporting API for CTS-Manager

For Prime Collaboration server to retrieve scheduled meetings from from CTS-Manager, 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.

Note:
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 
of the Reporting API.

Note: The procedures described below are applicable for CTS-Manager 1.8. If you are using any other supported versions, see the CTS-Manager Reporting API related documents.

To enable Prime Collaboration server to retrieve scheduled meetings from from CTS-Manager 1.8:

  1. In the LDAP server, create a user group. For example,create a group named pc_group.
  2. In the group that you created in the LDAP server, create a user. For example, create a user named pc_user.
    You must ensure that a valid mailbox is configured for the user created in the group in the LDAP server.
  3. In CTS-Manager, in the Access Management page, assign the Live Desk role and the Reporting API User role for the group you created in the LDAP server, for example, pc_group created in Step 1.
  4. Discover the CTS-Manager in Prime Collaboration with the user that you created in the LDAP server. For example, use pc_user.

For more information about the Reporting API, see Cisco Telepresense Manager Reporting API Developer's Guide for Release 1.8.

For more information about user and group configuration in LDAP server, see Cisco Telepresense Manager 1.8 Administration and Installation Guide.

Note:
After creating the user account in CTS-Manager for the Prime Collaboration application, we recommend 
that you log in with this account in CTS-Manager at least once before you enter the 
credentials in the Prime Collaboration server.

Cisco TMS Third Party Booking API User

For the Prime Collaboration server to retrieve scheduled meetings from Cisco TMS server, you must have one Application Integration License for each server that uses the API.

Note:
*We recommend that you review the Cisco TMS Third Party Booking API document available 
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 Cisco TMS server. In addition, you do not need to install a Booking API License to 
use the API.

To enable Prime Collaboration server to retrieve scheduled meetings from Cisco TMS:

  1. From the Cisco TMS server, go to http://localhost/tms/external/booking/remotesetup/remotesetupservice.asmx.
    The RemoteSetupService page appears. You may replace localhost in the above URL with the IP address of the Cisco TMS server.
  2. Choose GenerateConferenceAPIUser.
  3. Enter the values for the following parameters:
    • userNameBase - The base portion of the user name. For example, pc_user.
    • encPassword - A base64 encoded password that is to be used for the newly created user. To encode the password to base64, we recommend
      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.
    • sendNotifications - To allow the user to receive scheduling notifications. You must enter False in this field since Prime Collaboration
      will be polling from Cisco TMS.
  4. Click Invoke.
  5. In the Cisco TMS application, verify the user name configured in Step 3is listed in the Users page.
  6. In the Cisco TMS application, create a user group. For example, create a group named pc_group.
  7. Add the user created in Step 3 to the group created in Step 6. For example, add pc_user to pc_group.
  8. In the Groups page, for the group created in Step 6, check the Read permission check box for List Conferences-All (under the Booking pane). For example, pc_group must have the read permission to List Conferences-All.
  9. Discover the Cisco TMS in Cisco Prime Collaboration with the user that you created in Step 3. For example, use pc_user.

For more information about the Cisco TMS, see the documents available at TANDBERG site.

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

Configuring MCUs

A Cisco TelePresence MCU MSE 8510 (MCU MSE 8510) cluster consists of a Cisco TelePresence MCU MSE 8050 Supervisor Blade (MCU MSE 8550) and a MCU MSE 8510 blade. After the basic information is configured, HTTP access is enabled by default.

Enable HTTP

The supervisor web interface can be accessed by pointing the browser to http://<MCU_Address>, where <MCU_Address> is the IP address or hostname of your server. The default password for the admin user is a blank space (no password). If you cannot log in to the web GUI, Cisco Prime Collaboration will not be able to successfully manage the MCU MSE Supervisor.

To log in to the web interface of the MCU MSE 8510 blade:

  1. Log in to the supervisor web interface.
  2. Go to Hardware > Blades and click the IP address of the MCU MSE 8510 blade.
  3. Click Log in, and enter the username admin with no password.

Enable SNMP

You can edit SNMP settings by logging in to the MCU Codian Web Interface:

  1. Navigate to Network > SNMP.
  2. Edit the SNMP Read Only and Read Write strings as required.
  3. Click Update SNMP Settings to apply the changes.

Configuring Cisco TelePresence Multipoint Switch

Enable HTTP

A separate HTTP user account must be created with the Meeting Scheduler and Diagnostic Technician roles assigned to it for the Prime Collaboration application. This user can be configured in the Multipoint Switch web user interface when logged in as admin. After the dedicated HTTP user has been created, you must login to CTMS web UI using this user credential and then change the password (the same password can be entered).

An admin user is not required by Cisco Prime Collaboration to manage the Multipoint Switch.

You can access the Multipoint Switch through a web browser (preferably using Internet Explorer) by pointing the browser to: https://<ctms_serveraddress>, where <ctms_serveraddress> is the IP address or hostname of the Multipoint Switch.

Enable SNMP

SNMP is enabled by default and it monitors the Multipoint Switch system status (navigate to Troubleshoot > System Resources for system status details). You can designate a particular server where SNMP trap messages are gathered and stored. You configure all SNMP settings through the Multipoint Switch CLI commands.

The following SNMP settings are enabled by default:

  • SNMPv3 username set to mrtg: This name is for internal use of the system and should not be deleted.
  • SNMPv2c username set to public: This name is for internal use of the system and should not be deleted.
  • No trap receiver is configured. Use Multipoint Switch CLI commands to configure SNMP trap receiver information.

Use SSH in the Multipoint Switch to configure SNMP using the CLI. The CLI commands to configure SNMP Read Only and Read/Write are as follows:

  • set snmp user add 2c snmpro r
  • set snmp user add 2c snmprw rw
Note:
Replace snmpro and snmprw with your SNMP Read and Read/Write community strings.
After creating the user account in CTMS for the Prime Collaboration application, we recommend 
that you log in with this account in CTMS at least once before you enter the 
credentials in the Prime Collaboration server.

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

If you have enabled Cisco Mediatrace on your network nodes, Prime Collaboration 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:

  • Enable the initiator and/or responder roles on relevant routers and switches using the following commands:
    For Mediatrace Initiator:


mediatrace initiator source-ip ''IP Address''


For Mediatrace Responder:


mediatrace responder


  • 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. See Web Services Management Agent (WSMA) Configuration Guide for details on the configuration commands.

Local Auth Example:

username <username> priv 15 secret <username_enable_password>
ip http authentication local

For WSMA (HTTP) Configuration:

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

For WSMA (HTTPS) Configuration:


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

For WSMA SSH Configuration:

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

For Cisco IOS IP Service Level agreement (SLA):

  • Enable the responder role using the command:
ip sla responder

  • The initiator role is not required.
  • Configure a Telnet local login user with privilege 15 on the IP SLA initiators.

You can verify whether these roles are enabled on the device by using Prime Collaboration Inventory (Operate > Device Work Center > Current Inventory table).

For Performance Monitoring (PM) Configuration:

Configure the Performance Monitor policy on the relevant interfaces. Prime Collaboration collects PM flow statistics through MIBs. If this is configured, Prime Collaboration does not require the CLI access to routers.

Supported Software Versions for the Cisco Medianet Feature


Platform
Minimum IOS Release
Minimum Package
Feature Support
Catalyst 3560
15.0(1)SE2
IP Base
Mediatrace, Performance Monitor, IPSLA-VO
Catalyst 3750
15.0(1)SE2
IP Base
Mediatrace, Performance Monitor, IPSLA-VO
Catalyst 4500E Supervisor 7-E/7L-E
XE 3.3.0SG
IP Base
Mediatrace, Performance Monitor, IPSLA-VO
Catalyst 4500E Supervisor 6-E/6L-E
15.1(1)SG
IP Base
Mediatrace, Performance Monitor, IPSLA-VO
Catalyst 6500 Supervisor 2T
15.0(1)SY
IP Services
Mediatrace, Performance Monitor
ISR 2900 and 3900
15.1(3)T
UC and Data
Mediatrace, Performance Monitor

15.2(2)T
UC and DSP
IPSLA-VO Sender

15.2(2)T
IP Base
IPSLA-VO Responder
ISR 1900
15.1(3)T
UC and Data
Mediatrace, Performance Monitor

15.2(2)T
IP Base
IPSLA-VO Responder
ISR 880 and 890
15.1(3)T
Universal
Mediatrace, Performance Monitor
ASR 1000
XE 3.5
IP Base
Performance Monitor










Rating: 2.4/5 (5 votes cast)

Personal tools