Cisco Cisco Prime Collaboration Assurance 11.5 Libro bianco

 

 

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. 

Page 17 of 40 

3.  Create two groups (although one group can be used for both): Live Desk group (have accounts but less 

privilege) and Reporting API group. 

4.  Create a dedicated user account to be used for Reporting API in LDAP and Exchange for Cisco Prime 

Collaboration. 

a.  This user needs to have a mailbox. 

b.  This user must be used as an HTTP user in Cisco Prime Collaboration. 

5.  The user group created in step 3 in LDAP and Exchange must have privileges for Reporting API as well as 

Live Desk in Cisco TelePresence Manager. To set these privileges, from the main menu navigate to 

Configuration > Access Mgmt > Add Role and add privileges for Live Desk and for Reporting API. 

Cisco TelePresence Manager can be accessed through a web browser by pointing the browser to 

https://<serveraddress>/adminui/loginAction.do, where <serveraddress> is the IP address or hostname of the 

Cisco TelePresence Manager. 

SNMP community strings can be viewed only through the web interface, but they can be configured and enabled 

only through the CLI with SSH into the Cisco TelePresence Manager. (Refer to the Cisco TelePresence Manager 

1.7 CLI reference guide for more details.) Here is the quick guide to the command for enabling SNMP read only, 
where snmpro is the community string: “set snmp user add 2c snmpro r”. The following shows the complete syntax 

for this command: 

 

The main products that are normally deployed for conferencing needs are Multipoint Control Units (MCUs) for 

Cisco VCS-based devices or the Cisco TelePresence Multipoint Switch for Cisco Unified Communications 

Manager-based video endpoints. This section describes how to configure and prepare each of these conferencing 

components for manageability.