Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Reporting scenarios
This section covers troubleshooting scenarios related to Cisco TMS reporting functionality.
Bridge Utilization report
Data inconsistencies
Past data inconsistencies
A bridge that was replaced with a bridge of a different capacity, or reconfigured in the past, for example from
HD to Full HD, will lead to inaccurate past data and could lead to more than 100% usage being reported.
HD to Full HD, will lead to inaccurate past data and could lead to more than 100% usage being reported.
Purging bridges does not delete their historical Bridge Utilization data. The same applies when transitioning
to a TelePresence Conductor-managed bridge.
to a TelePresence Conductor-managed bridge.
If the ETL job fails, a TMS ticket will be generated: check the ETL log that is available in the Download
Diagnostic Files zip in
Diagnostic Files zip in
TMS Server Maintenance
.
Reconnected bridge call
In some scenarios, if participants in a multipoint conference lose connection to a bridge and reconnect, the
new connection may use a different port on the bridge. If the initial port has not yet been released, the
participant can occupy two ports. This results in the bridge reporting a misleading participant count to Cisco
TMS.
new connection may use a different port on the bridge. If the initial port has not yet been released, the
participant can occupy two ports. This results in the bridge reporting a misleading participant count to Cisco
TMS.
Port usage imprecision
Depending on port availability, participants may have their connection downgraded (video to audio) or
upgraded (audio to video) during a conference.
upgraded (audio to video) during a conference.
Any participant that has used a video port at any point during a conference will be reported as a video
participant when the conference ends. This means that a conference could be reported to have more video
participants than the available video ports on the bridge.
participant when the conference ends. This means that a conference could be reported to have more video
participants than the available video ports on the bridge.
No CDRs from endpoints running Cisco TC and TE software
Basic steps
Verify that:
n
The endpoint is on a software version supported by Cisco TMS.
n
The endpoint has the correct management address
n
The Cisco TMS server's IIS has Anonymous Authentication enabled for /tms/public, and that an Active
Directory group policy isn’t restricting the IUSR account.
Directory group policy isn’t restricting the IUSR account.
Advanced steps
Capture a Wireshark trace on the Cisco TMS server, and pre-filter it on the endpoint's IP address. To
successfully get a CDR from a Cisco endpoint, you should then see this sequence of events:
successfully get a CDR from a Cisco endpoint, you should then see this sequence of events:
Cisco TelePresence Management Suite Administrator Guide (14.6)
Page 334 of 344
Troubleshooting
Reporting scenarios