Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 1 – Troubleshooting
Cisco VCS Deployment Guide: CUCM v6.1, 7 and 8 with Cisco VCS X6 using a SIP trunk
Page 31 of 49
CUCM 7
When CUCM is not configured to connect to Cisco VCS, CUCM responds to the OPTIONS pings that
Cisco VCS sends to it with a 503 “Service unavailable”.
Cisco VCS sends to it with a 503 “Service unavailable”.
The 503 message contains a warn header which should be constructed as:
“Warning” 3 digit warn code <space> warn agent <space> warn text
“Warning” 3 digit warn code <space> warn agent <space> warn text
CUCM wrongly misses out the warn agent.
Cisco VCS correctly reports this as an illegal construct.
In-call problems
Calls remain up for a maximum of 15 minutes.
If a call is made from CUCM (version 8.0 or earlier) to a Cisco VCS FindMe that has CallerID set to
FindMe ID, CUCM does not handle the session refresh messages Cisco VCS sends to it (the
message has an updated From: header) and so session refreshes fail and the call is cleared by the
session refresh timer.
FindMe ID, CUCM does not handle the session refresh messages Cisco VCS sends to it (the
message has an updated From: header) and so session refreshes fail and the call is cleared by the
session refresh timer.
This is not a problem in CUCM versions later than 8.0.
Calls clear down when a call transfer from a video phone on CUCM
transfers a call to Cisco VCS
transfers a call to Cisco VCS
Even if use of a media termination point (MTP) is not requested on the SIP trunk between CUCM and
Cisco VCS, if DTMF signaling method is configured as “No preference” on the SIP trunk on CUCM,
CUCM will try and use a Media Transfer Point and the call will fail.
Cisco VCS, if DTMF signaling method is configured as “No preference” on the SIP trunk on CUCM,
CUCM will try and use a Media Transfer Point and the call will fail.
To resolve this, ensure that DTMF signaling method is configured as “RFC 2833” on CUCM on the
SIP trunk from CUCM to Cisco VCS.
SIP trunk from CUCM to Cisco VCS.
Taking a trace on CUCM using RTMT
RTMT is a tool that lets you monitor system health, view graphs and collect logs from CUCM. There
are versions for both Linux and Windows. CUCM must also be configured to specify what can be
traced.
are versions for both Linux and Windows. CUCM must also be configured to specify what can be
traced.
Configure CUCM to enable tracing
1. Log in to CUCM.
2. In the Navigation drop-down select Cisco Unified Serviceability and click Go.
3. Go to the Troubleshooting Trace Settings page (Trace > Troubleshooting Trace Settings).
4. Select the Check All Services check box.
5. Click Save.
Installing RTMT – Real Time Monitoring Tool
1. Log in to CUCM using a Linux or Windows PC.
2. Go to Application > Plugins.
3. Select Find with ‘Name begins with <blank>’ and ‘Plugin Type equals Installation’.
4. Scroll down to the entry for ‘Cisco Unified CM Real-Time Monitoring Tool – Linux’ or ‘Cisco
Unified CM Real-Time Monitoring Tool – Windows’, as required.
5. Click on the
Download
6. When downloaded, run the downloaded install file.
link.
7. Follow the instructions in the install wizard.