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 29 of 49
Look at “Call history” to check how the call progressed
1. Go to Status > Call history.
The summary shows the source and destination call aliases, the call duration and whether the call
is a SIP, H.323 or SIP< -- >H.323 interworking call.
is a SIP, H.323 or SIP< -- >H.323 interworking call.
2. Select the relevant call attempt.
The entry will show the incoming and outgoing call leg details, the call’s status and the zones that
the Cisco VCS Control used to route the call.
the Cisco VCS Control used to route the call.
Check for errors
Event Log
Check the Event Log which is accessible from the web browser: Status > Logs > Event Log.
Real time detailed event log
To obtain a more detailed log of key events and errors, start up syslog level 1 logging and then try the
call or initiate a presence action.
call or initiate a presence action.
Log in to the Cisco VCS Control as admin using an SSH or Telnet connection.
At the prompt type:
syslog 1
To turn off tracing, at the prompt type:
syslog off
Information displayed between typing syslog 1 and syslog off will contain the key events and error
messages that occurred between those two times.
messages that occurred between those two times.
Tracing calls
Tracing calls at SIP / H.323 level
Log in to the Cisco VCS Control as admin using an SSH or Telnet connection.
At the prompt type:
syslog 2
To turn off tracing, at the prompt type:
syslog off
Information displayed between typing syslog 2 and syslog off will contain the SIP and H.323
messaging received and sent out by the Cisco VCS Control.
messaging received and sent out by the Cisco VCS Control.
Information displayed by syslog 2 includes the key event and error message information reported
by syslog 1. Viewing syslog 1 and syslog 2 information separately can be useful so that syslog 1
messages are not lost within the detailed SIP / H.323 messaging.
by syslog 1. Viewing syslog 1 and syslog 2 information separately can be useful so that syslog 1
messages are not lost within the detailed SIP / H.323 messaging.
H.323 to SIP CUCM calls do not work
422 Session Timer too small
When interworking a call from H.323 to SIP, Cisco VCS in X4 and earlier versions of code would not
handle the SIP “422 Session Timer too small” response from CUCM. If an H.323 call is interworked to
a SIP call to CUCM and CUCM sends the ‘422 Session Timer too small’ message Cisco VCS clears
the call.
handle the SIP “422 Session Timer too small” response from CUCM. If an H.323 call is interworked to
a SIP call to CUCM and CUCM sends the ‘422 Session Timer too small’ message Cisco VCS clears
the call.