Patton electronic SmartNode 4110 Series ユーザーズマニュアル

Debugging call signaling

SmartWare Software Configuration Guide 

route to host” response) and a successful connection to host 172.16.40.122 (which received and sent packets with 
no loss).

node#ping 192.195.23.1 10 timeout 5
Sending 10 ICMP echo requests to 192.195.23.10, timeout is 5 seconds:
% No route to host
node#
node#ping 172.16.40.122
Sending 5 ICMP echo requests to 172.16.40.122, timeout is 1 seconds:
Reply from 172.16.40.122: Time <10ms
Reply from 172.16.40.122: Time <10ms
Reply from 172.16.40.122: Time <10ms
Reply from 172.16.40.122: Time <10ms
Reply from 172.16.40.122: Time <10ms
Ping statistics for 172.16.40.122:
  Packets: Sent 5, Received 5, Lost 0 (0% loss),
  RTT:     Minimum <10ms, Maximum <10ms, Average <10ms

If calls do not connect, or disconnect during the process of connecting, there is a problem in call signaling. We 
suggest the following steps to debug call signaling:

1. Work from the call source to the call destination.

2. Make sure that the call enters correctly the context CS of your unit (debug the source signaling protocol, 

depending on where the call comes from).

3. Make sure that the call leaves correctly the context CS of your unit (debug the destination signaling proto-

col, depending on where the call goes to).

4. Debug call routing when the call enters the context CS, but it does not leave it. Remember that context CS 

must be activated (“no shutdown”) for call routing to work.

Please make yourself familiar with the context CS concept described in chapter 31,

page 339. The following terminology will be used in this chapter:

•

Incoming call: Call setup attempt from a call signaling protocol towards the context CS

•

Outgoing call: Call setup attempt from the context CS towards a call signaling protocol

A basic call from an ISDN terminal connected to your unit over SIP to another SIP gateway is thus an incom-
ing and outgoing call a the same time, from the context CS perspective: It comes in from ISDN and goes out 
over SIP.

Overview: ISDN debug monitors

Prints all ISDN layer 3 signaling messages, and 
call control related activity of the ISDN interface. 
This is a good monitor to start with when debug-
ging ISDN.