Debugging Fxs Signaling; Verify An Incoming Call - Patton electronics SmartNode Series Software Configuration Manual

42 • VoIP debugging
Layer 2
Permanent Layer 2:
Protocol:
UniSide:
Layer 3
Protocol:
UniSide:
MinChannel:
MaxChannel:
MaxCalls:
Hunt Mode:
Signalling Mode:
EOXGW01#
The line "link state: up" tells you that layer 1 is up. To debug the layers 1-3 state machines, use the command
debug isdn event slot port {all | layer1 | layer2 | layer3}.

Debugging FXS Signaling

Overview: FXS debug monitors
unit #debug ccfxs
unit #debug fxs
unit #debug voip events
unit #show call-control provider name
[detail detail ]

Verify an incoming call

Make sure an incoming call is entering correctly context CS. In this example, a POTS terminal connected to
an FXS port goes off hook and places a call. The port is bound to a context CS interface named PHONE. The
debug output below shows a normal (working) call setup sequence.
unit>enable
unit#configure
unit(cfg)#debug ccfxs
unit(cfg)#debug fxs
unit(cfg)#09:00:11
09:00:11 FXS
09:00:11 FXS
09:00:11 FXS
09:00:11 FXS
09:00:11 CFXS
09:00:11 CFXS
504
Command
FXS > [0 1] Off hook.
> [0 1] Notifying off hook.
> FXS-00/01: state=on-hook, event=off-hook
> [0 1] Set state to 'Active'
> FXS-00/01: new state=filtering-events
> [EP PHONE] Change state to DIAL-TONE.
> [EP PHONE] Change datapath direction to receive-only.
SmartWare Software Configuration Guide
off
PointToMultiPoint
Net
Dss1
Net
0
1
2
Ascending
Etsi
Prints all operations on the FXS interfaces (high-
level).
Prints all operations on the FXS ports (low-level).
Prints the dialed digits.
Shows the status of an FXS interface in context CS
(call control part of FXS signaling). Shown are all
calls currently onging on the interface, with their
call states, signaling peers and voice data path
parameters.
name is the name of the FXS interface. Use detail 5
for most verbose output.
Purpose
Debugging call signaling