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

Debugging call signaling

SmartWare Software Configuration Guide 

•

: The phone went off-hook and thus accepted 

the call. The state of the CS interface goes to CONNECTED. The call is now established.

Overview: H.323 debug monitors

S

 on page 558 for further informations on debugging H.323. There are more 

than 40 debug monitors, such as q931, ras, or signaling. For a list of all available debug monitors, refer to the 
CLI online help.

Verify an incoming call
Make sure an incoming call is entering correctly context CS. In this example, a VoIP gateway or VoIP phone 
on the network makes a call to your unit using a gatekeeper. The debug output below shows a normal (work-
ing) call setup sequence

unit#enable
unit#configure
unit(cfg)#debug gateway h323 error
unit(cfg)#debug gateway h323 signaling
unit#debug gateway h323 ras
unit(cfg)#show gateway h323 status
H.323 Gateway: h323
===================

 State:                                 UP
 Stack Handle:                          0x193ce44

 RAS Engine

Prints all signaling operations on H.323 interfaces.

General purpose error monitor of H.323. Always 
enable this when debugging H.323.

Prints operations on the H.323 part of the voice 
data path. Use this monitor if you experience prob-
lems in the data path (no speech connectivity, 
speech only in one direction). This monitor is not 
needed to debug signaling.

Shows the state of the H.323 gateway. Among 
others: enabled/disabled, RAS registration state.

unit#show gateway h323 call name 
[detail detail]

Shows all calls ongoing on the H.323 interface on 
context CS with name name.

Shows the status of an H.323 interface in context 
CS (call control part of H.323 signaling). Shown 
are all calls currently ongoing on the interface, 
with their call states, signaling peers and voice 
data path parameters.
name is the name of the H.323 interface. Use 
detail 5 for most verbose output.