Cisco Cisco Prime Collaboration Manager 1.2 Installation Guide

Page of 20
14
A user group must be created for the Prime CM application in Cisco TMS with the List Conferences - All role with the Read 
permission.
For Cisco C-series TelePresence systems running on software version 4.1, the HTTP username must be in lower case.
The HTTP login access must have API privilege for Cisco TelePresence System. It does not require Admin privilege.
A JTAPI application user account is required in addition to HTTP in Cisco Unified CM. You must configure this account 
in the Cisco Unified CM publisher. Cisco Unified CM subscribers must have the same SNMP credentials as the Cisco Unified 
CM publisher.
HTTP login access must have Admin privilege for Cisco VCS, Cisco MCU, Cisco TelePresence EX Series, Cisco Telepresence 
System Integrator C Series, Cisco TelePresence System Quick Set C Series, and Cisco MSE Supervisor.
HTTP login access with Diagnostic Technician and Meeting Manager privileges is required for Cisco TelePresence 
Multipoint Switch.
Prime CM needs to access the Cisco VCS Expressway devices in the Demilitarized Zone (DMZ) using HTTP and SNMP 
protocols. It cannot manage and monitor the Cisco VCS Expressway devices if these protocols are blocked by firewalls.
Prime CM requires CLI login credentials to perform end-to-end path trace troubleshooting (to trigger MTR) in Cisco 
TelePresence System.
Prime CM must be able to ping (ICMP) all devices.
In Cisco VCS, only three servers can be registered for the feedback events. Make sure that there is no server other than the 
Cisco TMS server registered for Cisco VCS feedback events. The Prime CM server is registered as one of the servers for the 
feedback events for each Cisco VCS that is managed by the Prime CM server in the network.
For CTS endpoints, the CLI user account for CPCM can have either Admin or helpdesk privilege. The CLI access is required 
only when troubleshooting functionality is required.
For C/EX/MX/SX and MXP series endpoints, the required CLI user credential will be the same as the HTTP user credential. 
So no additional user account configuration is required for CLI.
For the C/EX/MX/SX and MXP series endpoints, the HTTP admin-level access is required for monitoring and performing 
end-to-end troubleshooting path trace.
No user account is required for Cisco Jabber Video for Telepresence (Movi) endpoints from CPCM.
All devices must be reachable via ICMP ping from CPCM (the ICMP ping can be disabled if necessary but that requires root 
access to CPCM).
Cisco TelePresence Server (TPS) does not support SNMP. Other than that, CPCM 1.2 requires SNMP read-only access for 
all other types of infrastructure devices.
The CTSMAN must have the Reporting API license. The HTTP user account should be an AD user with a mailbox and in 
a user group that has the Reporting API role and the Live Desk role in CTSMAN.
The HTTP admin-level access is not required for TPS. Only the HTTP API access privilege is required.
For VCS, the HTTP user for CPCM should have the read-write privilege.
SNMP v2c or v3 credentials are required for routers and switches if the CPCM capability of troubleshooting network issue 
is desired.
CDP also needs to be enabled on all network devices if troubleshooting path trace is desired.
For routers and switches, CLI login credentials are required if Medianet based troubleshooting is desired.
In Cisco Unified CM, enable the Web Access configuration for Cisco IP phones (89xx, 99xx) and Cisco Cius.
A separate HTTP user account must be created with the Meeting Scheduler and Diagnostic Technician roles assigned to it 
for the Prime CM application in Multipoint Switch.
For Cisco IP phones (89xx, 99xx), HTTP credentials are not required. However, the Prime Collaboration Manager must be 
able to access the IP Phone through HTTP.
In Cisco Unified CM, enable the following roles:
Standard CTI Allow Call Monitoring
Standard CTI Enabled
Standard CTI Allow Control of Phones supporting Connected Xfer and conf
For required protocol configurations, see