Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
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.
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.
(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.
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.
The report is based on actual call data provided by the managed bridges and does not consider the number of ports
originally scheduled.
originally scheduled.
No CDRs from Endpoints Running Cisco Collaboration Endpoint Software, TC, and TE Software
Basic Steps
Verify that:
■
The endpoint is on a software version supported by Cisco TMS.
■
The endpoint has the correct management address
■
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:
a CDR from a Cisco endpoint, you should then see this sequence of events:
1.
The endpoint POSTs to /tms/public/feedback that it is in a call. The endpoint continuously sends feedback to
Cisco TMS while the call is ongoing.
Cisco TMS while the call is ongoing.
2.
When the call has ended, the endpoint POSTs a call item to /tms/public/feedback. Example call item from
Cisco TelePresence SX20 running TC 5.1.1 software:
Cisco TelePresence SX20 running TC 5.1.1 software:
<Call item="175">
<CallId item="1">48</CallId>
<Protocol item="1">H323</Protocol>
<Direction item="1">Incoming</Direction>
<CallType item="1">Video</CallType>
<RemoteNumber item="1">h323:1234</RemoteNumber>
<CallbackNumber item="1">h323:example@example.com</CallbackNumber>
<DisplayName item="1">example@example.com </DisplayName>
<CallRate item="1">1920</CallRate>
<DisconnectCause item="1">Undefined reason</DisconnectCause>
<DisconnectCauseCode item="1">21</DisconnectCauseCode>
<DisconnectCauseOrigin item="1">Q850</DisconnectCauseOrigin>
<StartTime item="1">2012/05/30 14:45:23</StartTime>
<Duration item="1">11</Duration>
<Encryption item="1">Aes-128</Encryption>
<BookingId item="1"></BookingId>
</Call>
298
Cisco TelePresence Management Suite Administrator Guide
Troubleshooting