Patton electronic SmartNode 4110 Series Debugging SIP signaling, Mode Administrator Execution

SmartWare Software Configuration Guide 52 • VoIP debugging

Debugging SIP signaling

Mode: Administrator Execution

Step	Command	Purpose
1	[node]#debug context sip-gateway data-	Logs information related to the media chan-
	path [detail <level>]	nels.
	[node]#debug context sip-gateway error	Logs all errors detected within the Context SIP
	[detail <level>]	Gateway.
	[node]#debug context sip-gateway regis-	Logs information about user registration activ-
	tration [detail <level>]	ities.
	[node]#debug context sip-gateway sig-	Logs call signaling related information.
	naling [detail <level>]
	[node]#debug context sip-gateway	Logs all SIP messages sent or received over
	transport [detail <level>]	the IP network.

Verify an incoming call

Make sure that an incoming call from the SIP network enters correctly context CS. The following sequence shows a working call setup.

unit(cfg)#debug gateway sip error unit(cfg)#debug gateway sip transport

unit(cfg)#18:53:40 SIP_TR> Received INVITE sip:50@172.16.32.32 SIP/2.0 18:53:40 SIP_TR> Sent SIP/2.0 100 Trying

18:53:40 SIP_TR> Sent SIP/2.0 180 Ringing 18:53:43 SIP_TR> Sent SIP/2.0 200 OK

18:53:43 SIP_TR> Received ACK sip:50@172.16.32.32:5060 SIP/2.0

Explanation:

•The line 18:53:40 SIP_TR> Received INVITE sip:50@172.16.32.32 SIP/2.0 indicates that the INVITE

message has been received. This means that the SIP network is functional

•18:53:40 SIP_TR > Sent SIP/2.0 100 Trying and 18:53:40 SIP_TR> Sent SIP/2.0 180 Ringing indi-

cate that responses are sent back to the SIP network. This means that the call routing is working correctly, and the call has found its destination on the gateway that is debugged. If there are no responses, or a nega- tive response, continue debugging call routing and the destination protocol.

Verify an outgoing call

Make sure that an outgoing call from context CS leaves correctly to the SIP network. The following sequence shows a working call setup.

unit(cfg)#debug gateway sip error unit(cfg)#debug gateway sip transport

unit(cfg)#18:59:07 SIP_TR> Sent INVITE sip:60@172.16.32.33 SIP/2.0 18:59:07 SIP_TR> Received SIP/2.0 100 Trying

18:59:07 SIP_TR> Received SIP/2.0 180 Ringing 18:59:10 SIP_TR> Received SIP/2.0 200 OK

18:59:10 SIP_TR> Sent ACK sip:60@172.16.32.33:5060 SIP/2.0

Debugging call signaling 638