6. Identify the first indication of failure in protocol traces or internal debugcommandoutput.

7. Look for the cause in configuration files.

Note General troubleshooting of problems affecting basic functionality such as dial peers, digit translation, and IP connectivity is beyond the scope of this chapter. For links to additional troubleshooting help, see the "Additional References" section.

Using show Commands

To verify SIP gateway status and configuration, perform the following steps as appropriate (commands are listed in alphabetical order).

SUMMARY STEPS

1. show sip service

2. show sip-ua register status

3. show sip-ua statistics

4. show sip-ua status

5. show sip-ua timers

DETAILED STEPS

Step 1 show sip service

Use this command to display the status of SIP call service on a SIP gateway.

The following sample output shows that SIP call service is enabled:

Router# show sip service

SIP Service is up

The following sample output shows that SIP call service was shut down with the shutdown command:

Router# show sip service

SIP service is shut globally

under 'voice service voip'

The following sample output shows that SIP call service was shut down with the call service stop command:

Router# show sip service

SIP service is shut

under 'voice service voip', 'sip' submode

The following sample output shows that SIP call service was shut down with the shutdown forced command:

Router# show sip service

SIP service is forced shut globally

under 'voice service voip'

The following sample output shows that SIP call service was shut down with the call service stop forced command:

Router# show sip service

SIP service is forced shut

under 'voice service voip', 'sip' submode

Step 2 show sip-ua register status

Use this command to display the status of E.164 numbers that a SIP gateway has registered with an external primary SIP registrar.

Router# show sip-ua register status

Line peer expires(sec) registered

4001 20001 596 no

4002 20002 596 no

5100 1 596 no

9998 2 596 no

Step 3 show sip-ua statistics

Use this command to display response, traffic, and retry SIP statistics, including whether call redirection is disabled.

The following sample shows that four registers were sent:

Router# show sip-ua statistics

SIP Response Statistics (Inbound/Outbound)

Informational:

Trying 0/0, Ringing 0/0,

Forwarded 0/0, Queued 0/0,

SessionProgress 0/0

Success:

OkInvite 0/0, OkBye 0/0,

OkCancel 0/0, OkOptions 0/0,

OkPrack 0/0, OkPreconditionMet 0/0,

OkSubscribe 0/0, OkNOTIFY 0/0,

OkInfo 0/0, 202Accepted 0/0

OkRegister 12/49

Redirection (Inbound only except for MovedTemp(Inbound/Outbound)) :

MultipleChoice 0, MovedPermanently 0,

MovedTemporarily 0/0, UseProxy 0,

AlternateService 0

Client Error:

BadRequest 0/0, Unauthorized 0/0,

PaymentRequired 0/0, Forbidden 0/0,

NotFound 0/0, MethodNotAllowed 0/0,

NotAcceptable 0/0, ProxyAuthReqd 0/0,

ReqTimeout 0/0, Conflict 0/0, Gone 0/0,

ReqEntityTooLarge 0/0, ReqURITooLarge 0/0,

UnsupportedMediaType 0/0, BadExtension 0/0,

TempNotAvailable 0/0, CallLegNonExistent 0/0,

LoopDetected 0/0, TooManyHops 0/0,

AddrIncomplete 0/0, Ambiguous 0/0,

BusyHere 0/0, RequestCancel 0/0,

NotAcceptableMedia 0/0, BadEvent 0/0,

SETooSmall 0/0

Server Error:

InternalError 0/0, NotImplemented 0/0,

BadGateway 0/0, ServiceUnavail 0/0,

GatewayTimeout 0/0, BadSipVer 0/0,

PreCondFailure 0/0

Global Failure:

BusyEverywhere 0/0, Decline 0/0,

NotExistAnywhere 0/0, NotAcceptable 0/0

Miscellaneous counters:

RedirectRspMappedToClientErr 0

SIP Total Traffic Statistics (Inbound/Outbound)

Invite 0/0, Ack 0/0, Bye 0/0,

Cancel 0/0, Options 0/0,

Prack 0/0, Comet 0/0,

Subscribe 0/0, NOTIFY 0/0,

Refer 0/0, Info 0/0

Register 49/16

Retry Statistics

Invite 0, Bye 0, Cancel 0, Response 0,

Prack 0, Comet 0, Reliable1xx 0, NOTIFY 0

Register 4

SDP application statistics:

Parses: 0, Builds 0

Invalid token order: 0, Invalid param: 0

Not SDP desc: 0, No resource: 0

Last time SIP Statistics were cleared: <never>

The following sample output shows the RedirectResponseMappedToClientError status message. An incremented number indicates that 3xx responses are to be treated as 4xx responses. When call redirection is enabled (default), the RedirectResponseMappedToClientError status message is not incremented.

Router# show sip-ua statistics

SIP Response Statistics (Inbound/Outbound)

Informational:

Trying 0/0, Ringing 0/0,

Forwarded 0/0, Queued 0/0,

SessionProgress 0/0

Success:

OkInvite 0/0, OkBye 0/0,

OkCancel 0/0, OkOptions 0/0,

OkPrack 0/0, OkPreconditionMet 0/0,

OKSubscribe 0/0, OkNotify 0/0,

202Accepted 0/0

Redirection (Inbound only):

MultipleChoice 0, MovedPermanently 0,

MovedTemporarily 0, UseProxy 0,

AlternateService 0

Client Error:

BadRequest 0/0, Unauthorized 0/0,

PaymentRequired 0/0, Forbidden 0/0,

NotFound 0/0, MethodNotAllowed 0/0,

NotAcceptable 0/0, ProxyAuthReqd 0/0,

ReqTimeout 0/0, Conflict 0/0, Gone 0/0,

ReqEntityTooLarge 0/0, ReqURITooLarge 0/0,

UnsupportedMediaType 0/0, BadExtension 0/0,

TempNotAvailable 0/0, CallLegNonExistent 0/0,

LoopDetected 0/0, TooManyHops 0/0,

AddrIncomplete 0/0, Ambiguous 0/0,

BusyHere 0/0, RequestCancel 0/0

NotAcceptableMedia 0/0, BadEvent 0/0

Server Error:

InternalError 0/0, NotImplemented 0/0,

BadGateway 0/0, ServiceUnavail 0/0,

GatewayTimeout 0/0, BadSipVer 0/0,

PreCondFailure 0/0

Global Failure:

BusyEverywhere 0/0, Decline 0/0,

NotExistAnywhere 0/0, NotAcceptable 0/0

Miscellaneous counters:

RedirectResponseMappedToClientError 1,

SIP Total Traffic Statistics (Inbound/Outbound)

Invite 0/0, Ack 0/0, Bye 0/0,

Cancel 0/0, Options 0/0,

Prack 0/0, Comet 0/0,

Subscribe 0/0, Notify 0/0,

Refer 0/0

Retry Statistics

Invite 0, Bye 0, Cancel 0, Response 0,

Prack 0, Comet 0, Reliable1xx 0, Notify 0

SDP application statistics:

Parses: 0, Builds 0

Invalid token order: 0, Invalid param: 0

Not SDP desc: 0, No resource: 0

Step 4 show sip-ua status

Use this command to display status for the SIP user agent (UA), including whether call redirection is enabled or disabled.

Router# show sip-ua status

SIP User Agent Status

SIP User Agent for UDP : ENABLED

SIP User Agent for TCP : ENABLED

SIP User Agent bind status(signaling): DISABLED

SIP User Agent bind status(media): DISABLED

SIP max-forwards : 6

SIP DNS SRV version: 1 (rfc 2052)

Redirection (3xx) message handling: ENABLED

Step 5 show sip-ua timers

Use this command to display the current settings for the SIP user-agent (UA) timers.

The following sample output shows the waiting time before a register request is sent—that is, the value that is set with the timers register command:

Using debug Commands

•Use the debug asnl events command to verify that the SIP subscription server is up. The output displays a pending message if, for example, the client is unsuccessful in communicating with the server.

•Use the debug call fallback family of commands to display details of VoIP call fallback.

•Use the debug cch323 family of commands to provide debugging output for various components within an H.323 subsystem.

•Use the debug ccsip family of commands for general SIP debugging, including viewing direction-attribute settings and port and network address-translation traces. Use any of the following related commands:

•Use the debug rpms-proc preauth command to enable debug tracing on the RPMS process for H.323 calls, SIP calls, or both H.323 and SIP calls.

•Use the debug rtr trace command to trace the execution of an SAA operation.

•Use the debug voip family of commands, including the following:

–debug voip ccapi protoheaders—Displays messages sent between the originating and terminating gateways. If no headers are being received by the terminating gateway, verify that the header-passing command is enabled on the originating gateway.

–debug voip ivr script—Displays any errors that might occur when the Tcl script is run

–debug voip rtp session named-event 101—Displays information important to DTMF-relay debugging, if you are using codec types g726r16 or g726r24. Be sure to append the argument 101 to thecommand to prevent the console screen from flooding with messages and all calls from failing.

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.