Friday, April 30, 2010

CTS System - Debugging with Cisco IP Phone

Always obtain an accurate problem description

- Phone model
- Current phone firmware
- CUCM version
- Sniffer capture (wireshark), CUCM SDI/SDL detailed traces

  • SSH into the Phone

Create a ssh session to the phone using SSH using CUCM
Login with User and password provided in CUCM

Once you get login, second prompt use:

login:default
passwd:user

  • Debug Interface

Enable debugs depending upon call features, as described below.

To use the debugsh either login in as debug/debug or login as default/user then start the debug shell via 'debugsh'. Type 'help' and '?' for more information.
Enable strace
At the prompt type

strace&

  • Enable JVM debugs

In order to see SIP debugs the JVM logging level must be set to Debug. Enter the debugsh and invoke the following command:

debugsh
jvm logging level DEBUG

The logging level will be saved across a reboot.
Save SIP debug settings across reboot

Use the following command in the debug shell to create a file that will be loaded once the JVM starts.

store sip-debugs

  • Debugs for SIP phone features

show dialplan
show config
debug remote-cc dialplan gsm fsm fim lsm vcm sip-messages sip-state sip-task kpml

Additional debugs based on features

Following are the additional debugs that should be enabled based on features

For Registration issue
show reg
debug sip-reg

For UI related issue

show reg
debug sip-adapter

To disable debugs

debugsh
jvm logging level NONE

  • Example

login: default
password:

sh 3.0 (1.5)
%
% strace&
% debugsh
0013C3E248EA> jvm logging level DEBUG
0013C3E248EA> debug remote-cc dialplan gsm fsm fim lsm vcm sip-messages sip-state sip-task kpml

No comments:

Post a Comment