Patton electronics SmartWare R.3.20, Software Configuration Manual

Page: 547 / 573

Debugging call signaling
547
SmartWare Software Configuration Guide
42 • VoIP debugging
• 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 Ring-
ing
indicate 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 negative 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
Explanation:
• The line
18:59:07 SIP_TR> Sent INVITE sip:60@172.16.32.33 SIP/2.0
indicates that the INVITE
was sent. Thus, call routing worked in context CS and the message left to the SIP network.
•
18:59:07 SIP_TR > Received SIP/2.0 100 Trying
indicate that responses are received from the SIP
network. This means that IP connectivity is OK and the remote gateway can be reached. If there are no
responses, or negative ones, continue debugging the remote SIP gateway.
Using SmartWare’s internal call generator
The SmartWare has a powerful internal call generator that creates calls from the center of context CS. It is very
useful to debug call signaling or call routing problems to verify the correct working of one call signaling proto-
col at a time. Calls can be placed towards any interface on context CS, or any routing table within context CS.
Example : Debug ISDN protocol using the call generator. Create a call from context CS to an ISDN interface
called TERMINAL.
unit(cfg)#debug ccisdn signaling
unit(cfg)#debug ccisdn error
unit(cfg)#debug isdn error
unit(cfg)#call 55 dial 50 dest-interface TERMINAL
unit(cfg)#19:17:38 ICC > [TERMINAL] Added endpoint TERMINAL-00df2760
19:17:38 ICC > [TERMINAL] NEW CALL. Allocated Endpoint TERMINAL-00df2760
19:17:38 ICC > [TERMINAL-00df2760] >> SETUP (DSS1 Ntwk)
Bearer capability : speech - CCITT
Command Purpose
call
calling-party
{accept | alerting |
dial|drop | inband-info | offer-state |
proceeding | reject-all | resume | sus-
pend | user-input } ....
Manipulates calls locally generated from the center
of context CS. To create a call, use “call
calling-
party dial called-party”, to manipulate this call
afterwards use the same calling party. See the
examples below for usage.