Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 1 - Troubleshooting
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.
1. Log in to Cisco VCS Control as admin using an SSH or Telnet connection.
call or initiate a presence action.
1. Log in to Cisco VCS Control as admin using an SSH or Telnet connection.
2. At the prompt type:
syslog 1
3. To turn off tracing, at the prompt type:
syslog off
Information displayed between typing syslog 1 and syslog off contains 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
1. Log in to Cisco VCS Control as admin using an SSH or Telnet connection.
1. Log in to Cisco VCS Control as admin using an SSH or Telnet connection.
2. At the prompt type:
syslog 2
3. To turn off tracing, at the prompt type:
syslog off
Information displayed between typing syslog 2 and syslog off contains the SIP and H.323
messaging received and sent out by the Cisco VCS.
messaging received and sent out by the Cisco VCS.
Information displayed by syslog 2 includes the key event and error message information reported by
syslog 1
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.
My MXP will not create a Multiway™ call
Whether the MXP uses H.323 signaling or SIP signaling to call the Multiway™ Conference Factory
Alias is defined by the Multiway URI configured on the MXP.
Alias is defined by the Multiway URI configured on the MXP.
If the Multiway URI is prefixed with “sip:”, e.g. sip:multiway@domain then the MXP will always make
the call to the Multiway™ Conference Factory Alias using SIP signaling; if it does not have the ‘sip:’
prefix e.g. multiway@domain or has an h323: prefix, e.g. h323:multiway@domain then the MXP will
always make the call to the Multiway™ Conference Factory Alias using H.323 signaling.
the call to the Multiway™ Conference Factory Alias using SIP signaling; if it does not have the ‘sip:’
prefix e.g. multiway@domain or has an h323: prefix, e.g. h323:multiway@domain then the MXP will
always make the call to the Multiway™ Conference Factory Alias using H.323 signaling.
Note: The Multiway™ Conference Factory Alias must be in URI format name@domain as the
underlying Conference Factory operation is SIP based and operates on SIP URIs.
underlying Conference Factory operation is SIP based and operates on SIP URIs.
The MXP must therefore be registered to the Cisco VCS, or be configured so that it can route calls to
the Cisco VCS using the appropriate protocol (H.323 or SIP). Otherwise although “Join” will be
presented on the screen, when pressed the Multiway™ call will fail.
the Cisco VCS using the appropriate protocol (H.323 or SIP). Otherwise although “Join” will be
presented on the screen, when pressed the Multiway™ call will fail.
If the Multiway URI has a “sip:” prefix, ensure that SIP calls can be made from the MXP to the
Cisco VCS.
Cisco VCS.
If the Multiway URI does not have a “sip:” prefix, ensure that H.323 calls can be made from the
MXP to the Cisco VCS.
MXP to the Cisco VCS.
Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X5)
Page 18 of 25