Cisco Cisco Prime Collaboration Assurance 11.5 Weißbuch
© 2016 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 24 of 64
Device
SNMP HTTP CLI JTAPI MSI
CDP
Notes
Mediasense
Yes
Yes
-
-
-
-
If you are using Cisco Prime Collaboration 10.5 or later
versions, you must configure HTTP credentials for Cisco
MediaSense along with SNMP.
versions, you must configure HTTP credentials for Cisco
MediaSense along with SNMP.
Meeting Place
Yes
-
-
-
-
-
Meeting Place Express
Yes
-
-
-
-
-
Personal Assistant
-
-
-
-
-
-
Cisco TelePresence System
MXP series
MXP series
Yes
Yes
Yes
Polycom VSX series
Polycom HDX series
Polycom HDX 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 Cisco Prime
Collaboration.
the path trace can be discovered from the first-hop-router
(FHR) if router CLI access is provided for Cisco Prime
Collaboration.
Cisco Unified Presence
Yes
Yes
-
-
-
-
Network devices (routers and
switches)
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.
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.
troubleshooting Medianet-related data.
Cisco TelePresence
Management Suite (Cisco TMS)
Management Suite (Cisco TMS)
Yes
Yes
-
-
-
-
● Requires Booking API license (TMS software version
13.1 or below).
● The HTTP user for Cisco Prime Collaboration needs
to be generated through the Booking API on the
Cisco TMS windows server.
Cisco TMS windows server.
● Cisco 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 TMS. The session import feature will not work,
if the default e-mail template is not used.
Cisco Telepresence Server
Cisco Telepresence Server on
Virtual Machine (supported by
Cisco Prime Collaboration
Assurance 10.5.1 and later
versions)
Cisco Telepresence Server on
Virtual Machine (supported by
Cisco Prime Collaboration
Assurance 10.5.1 and later
versions)
Cisco TelePresence Server on
Multiparty Media 310 and 320
(supported by Prime
Collaboration Assurance 10.5.1
and later versions)
Multiparty Media 310 and 320
(supported by Prime
Collaboration Assurance 10.5.1
and later versions)
-
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 Meraki MX70 and MX80
-
Yes
-
-
-
-
Cisco Telepresence Conductor
Yes
Yes
-
-
-
-
Cisco Unity
Yes
-
-
-
-
-
Cisco Unity Connection
Yes
Yes
-
-
-
-
Cisco Unity Express
Yes
-
-
-
-
-
Cisco TelePresence Video
Communication Server (Control
and Expressway)
Communication Server (Control
and Expressway)
Yes
Yes
-
-
-
-
The HTTP user requires Admin privilege.
Wireless
Yes
-
Yes -
-
-
Third party devices
Yes
-
-
-
-
-
Cisco Jabber Video for
Telepresence (Movi)
Telepresence (Movi)
-
-
-
-
-
-
● The Cisco Jabber endpoints are discovered either
through Cisco Unified CM or Cisco VCS (access
credentials are not required).
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 Cisco Prime Collaboration.
first-hop-router (FHR) if router CLI access is provided
for Cisco Prime Collaboration.