Cisco Cisco Prime Collaboration Manager 1.2 Release Notes

For more information, see the following in the 

“Introducing Cisco Prime Collaboration Manager”—For links to relevant topics that describe these 
new and enhanced features.

“Usage Scenarios” and “Best Practices”—To help you to use Prime CM effectively.

Cisco Prime Collaboration Manager 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.

If the IP address of a Cisco TelePresence System (CTS) endpoint is changed, Prime CM raises two 
alarms: Unregistered and Unreachable. The Prime CM server clears the Unregistered alarm within 
a few minutes, but the Unreachable alarm is not cleared.

You can clear the Unreachable alarm manually; otherwise, the Prime CM server clears the alarm 
after 24 hours, if there are no updates.

When you have scheduled a multipoint session using the Cisco TelePresence Server but have not 
entered either the Call-out or Call-in Match parameter for the endpoint in the Cisco TelePresence 
Server, Prime CM does not change the status of the scheduled multipoint session to in-progress. 

Whenever you schedule a session using the Cisco TelePresence Server, we recommend that you add 
the endpoint in the Cisco TelePresence Server along with the Call-out and Call-in Match parameter 
details. Also, the endpoint name in the Cisco TelePresence Server must be the same in the 
CTS-Manager, if CTS-Manager is used as the management system in your network.

The Prime CM Session Monitoring feature does not support endpoints, which are configured with 
multiple lines in Cisco Unified CM. However, you can manage these endpoints in the Prime CM 
inventory database.

On the Session Monitoring page, Prime CM does not display past session information and session 
statistics for Cisco Cius and Cisco IP phones. This applies only if you have set real-time visibility 
to Full for Cisco Cius and Cisco IP phones.

If the IP address of a DHCP-enabled endpoint registered to Cisco Unified CM changes, Prime CM 
may not be able to automatically discover this endpoint. The endpoints registered to 
Cisco TelePresence Video Communication Server (Cisco VCS) are always automatically discovered 
when their IP address changes.

The endpoints registered to the Cisco VCS Expressway may be displayed as unknown endpoints in 
the Session Topology pane. This is because these endpoints are behind the firewall. 

Only the Peripherals and Session details are displayed on the Session Monitoring page, if there is a 
session between a TelePresence and an audio endpoint (such as a WebEx call). This session is 
identified as an Inlocalconference session.

The endpoint statistics may not be displayed in this scenario:

A TelePresence endpoint (endpoint A) calls another TelePresence endpoint (endpoint B).

Details for all endpoint statistics are displayed on the Session Monitoring page.

The same endpoint A conferences with another endpoint (endpoint C). 

Details for all endpoint statistics are displayed on the Session Monitoring page.

Endpoint A conferences again with another endpoint (endpoint D) and disconnects from 
endpoint C.