Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
sip_state. The availability of this function and it's configuration method are dependent upon the network load
balancer.
balancer.
The Polycom CDR configuration files are located at C:\Program Files (x86)\TANDBERG\TMS\pwx when you use
Cisco TMS version 13.0 to 14.5. For Cisco TMS version 14.6 and above, theconfiguration files are located at
C:\Program Files (x86)\TANDBERG\TMS\wwwTMS\public\pwx.
Cisco TMS version 13.0 to 14.5. For Cisco TMS version 14.6 and above, theconfiguration files are located at
C:\Program Files (x86)\TANDBERG\TMS\wwwTMS\public\pwx.
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.
2
This cause indicates that the equipment sending this cause has received a request to route the call through
a particular transit network which it does not recognize. The equipment sending this cause does not
recognize the transit network either because the transit network does not exist or because that particular
transit network, while it does exist, does not serve the equipment which is sending this cause.
a particular transit network which it does not recognize. The equipment sending this cause does not
recognize the transit network either because the transit network does not exist or because that particular
transit network, while it does exist, does not serve the equipment which is sending this cause.
3
This cause indicates that the called party cannot be reached because the network through which the call
has been routed does not serve the destination desired. This cause is supported on a network dependent
basis.
has been routed does not serve the destination desired. This cause is supported on a network dependent
basis.
5
This cause indicates the erroneous inclusion of a trunk prefix in the called party number. This number is
supposed to be stripped from the dialed number being sent to the network by the customer premises
equipment.
supposed to be stripped from the dialed number being sent to the network by the customer premises
equipment.
6
This cause indicates that the channel most recently identified is not acceptable to the sending party for use
in this call.
in this call.
7
This cause indicates that the user has been awarded the incoming call, and that the incoming call is being
connected to a channel already established to that user for similar calls (for example packet-mode x.25
virtual calls.
connected to a channel already established to that user for similar calls (for example packet-mode x.25
virtual calls.
8
This cause indicates the call is being pre-empted.
Table 178 Cause codes based on the ITU-T standard
284
Cisco TelePresence Management Suite Administrator Guide
Troubleshooting