Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
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
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_
sip_state. The availability of this function and it's configuration method are dependent upon the network load bal
ancer.
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_
sip_state. The availability of this function and it's configuration method are dependent upon the network load bal
ancer.
No Statistics for Legacy TANDBERG Systems
If Cisco TMS is not displaying statistics for legacy systems, try the steps below.
Basic Steps
■
Make sure no SNMP tool outside of Cisco TMS is running on the server
■
Verify that the system's management address (feedback receiver if an infrastructure system) is set to
http://<FQDNofTMS>/tms/public/feedback/code.aspx. If the address is set up to use HTTPS, this must be
enabled in Cisco TMS IIS.
http://<FQDNofTMS>/tms/public/feedback/code.aspx. If the address is set up to use HTTPS, this must be
enabled in Cisco TMS IIS.
■
Check the logs for symptoms or error messages at C:\Program
Files\TANDBERG\TMS\data\Logs\TMSDebug\log-TMSSNMPservice.txt on the server.
Files\TANDBERG\TMS\data\Logs\TMSDebug\log-TMSSNMPservice.txt on the server.
■
Advanced Steps
Using Wireshark, verify that Cisco TMS is receiving SNMP data from the system.
Cause Codes
Code
Description
0
Cisco specific. Not part of ITU-T standard.
1
This cause indicates that the destination requested by the calling user cannot be reached because,
although the number is in a valid format, it is not currently assigned.
although the number is in a valid format, it is not currently assigned.
Table 178 Cause codes based on the ITU-T standard
284
Cisco TelePresence Management Suite Administrator Guide
Troubleshooting