Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
3.
Cisco TMS parses and processes the call item and creates a CDR from it. Most values are taken verbatim from
the call item posted to Cisco TMS; some values, such as cause codes, can be discarded by Cisco TMS and set
to "unknown" if they do not follow ITU-T standards.
the call item posted to Cisco TMS; some values, such as cause codes, can be discarded by Cisco TMS and set
to "unknown" if they do not follow ITU-T standards.
No CDRs from Cisco TelePresence Server
Basic Steps
Verify that:
1.
TelePresence Server is running a software version supported by Cisco TMS.
2.
Cisco TMS IIS has Anonymous Authentication enabled for /tms/public, and that an Active Directory group
policy is not restricting the IUSR account.
policy is not restricting the IUSR account.
No CDRs from Cisco TelePresence MCU
Basic Steps
Make sure you are running software version 4.3 or later, which supports asynchronous processing of CDRs.
No CDRs from Polycom Endpoints
Basic steps
Verify that:
■
The Polycom endpoint is on a software version supported by Cisco TMS.
■
The Polycom endpoint has the correct management address.
■
The Cisco TMS server's operating system has either MSXML 4.0 or MSXML 6.0 installed.
■
The Cisco TMS server's IIS has Anonymous Authentication enabled for /pwx, and that an Active Directory
group policy is not restricting the IUSR account.
group policy is not 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 Polycom, you should then see this sequence of events:
1.
When the call is set up, the endpoint POSTs a status to /pwx/nx_status.asp on the Cisco TMS server so that
Cisco TMS starts monitoring the call.
Cisco TMS starts monitoring the call.
2.
When the call is ended, the endpoint POSTs a status that includes “type=disconnected”. Example status
message posted to /pwx:
message posted to /pwx:
id=sa_sabre&event=sa_cxn_state&serial=1234567890123456&conf_id=14948&cxn_
id=1&direction=incoming&display_name=endpoint@example.com&number=123456&rate=512&cxn_
type=h323&type=disconnected&hangup_type=local&cause_code=16&rollover_cod
id=1&direction=incoming&display_name=endpoint@example.com&number=123456&rate=512&cxn_
type=h323&type=disconnected&hangup_type=local&cause_code=16&rollover_cod
3.
Cisco TMS then GETs a /localcdr.csv file from the endpoint. The .csv file is parsed and processed by Cisco
TMS, which creates its own CDR based upon the data received from the Polycom.
TMS, which creates its own CDR based upon the data received from the Polycom.
Note that some data cannot be received from Polycom endpoints and will therefore be reported as Unknown.
An administrator can manually filter unused Polycom feedback, when the load balancer receives feedback through an
HTTP connection. You will not be able to filter HTTP content on a HTTPS connection, as the content would be
encrypted on HTTPS connetcion. The HTTP content filter can be set to block, if feedback is sent from a Polycon
devices where the HTTP content contains id=sa_sabre&event=sa_exchangeSrvr_state or id=sa_sabre&event=sa_
HTTP connection. You will not be able to filter HTTP content on a HTTPS connection, as the content would be
encrypted on HTTPS connetcion. The HTTP content filter can be set to block, if feedback is sent from a Polycon
devices where the HTTP content contains id=sa_sabre&event=sa_exchangeSrvr_state or id=sa_sabre&event=sa_
299
Cisco TelePresence Management Suite Administrator Guide
Troubleshooting