Sangoma A101D PRI d-chan not working

Clean install 5.211.65-3 32bit Asterisk 8 (I also tried 11). D-Channel won’t link up. Messages from Asterisk don’t appear to make it to the hardware. Intense debug in Asterisk shows messages coming and going, but wanpipemon trace only shows incoming packets.

Run Wanpipe In DAHDI Mode: YES
Run Wanpipe In DIGIUM Mode: TRUE

Signalling: PRI-NET
Switchtype: Q.SIG

[[email protected] ~]# wanpipemon -i w1g1 -c trd
Starting trace…(Press ENTER to exit)
INCOMING Len=3 TimeStamp=26594 Jan 06 09:15:00 69519 [1/100s]
Raw (HEX) 00 01 7F

INCOMING Len=3 TimeStamp=28096 Jan 06 09:15:01 572150 [1/100s]
Raw (HEX) 00 01 7F

INCOMING Len=3 TimeStamp=29597 Jan 06 09:15:03 72778 [1/100s]
Raw (HEX) 00 01 7F

INCOMING Len=1 TimeStamp=31096 Jan 06 09:15:04 571269 [1/100s]
Raw (HEX) FE

INCOMING Len=3 TimeStamp=31190 Jan 06 09:15:04 665642 [1/100s]
Raw (HEX) 00 01 7F

INCOMING Len=3 TimeStamp=32650 Jan 06 09:15:06 125295 [1/100s]
Raw (HEX) 00 01 7F

INCOMING Len=3 TimeStamp=34151 Jan 06 09:15:07 626901 [1/100s]
Raw (HEX) 00 01 7F

[[email protected] ~]# wanpipemon -i w1g1 -c Ta
***** w1g1: T1 Rx Alarms (Framer) *****
ALOS: OFF | LOS: OFF
RED: OFF | AIS: OFF
LOF: OFF | RAI: OFF

***** w1g1: T1 Rx Alarms (LIU) *****
Short Circuit: OFF
Open Circuit: OFF
Loss of Signal: OFF

***** w1g1: T1 Tx Alarms *****
AIS: OFF | YEL: OFF

***** w1g1: T1 Performance Monitoring Counters *****

Line Code Violation : 0
Bit Errors (CRC6/Ft/Fs) : 0
Out of Frame Errors : 0
Sync Errors : 0

Rx Level : > -2.5db

localhost*CLI> pri show span 1
Primary D-channel: 24
Status: Up, Active
Switchtype: Q.SIG switch
Type: Network
Remote type: CPE
Overlap Dial: 0
Logical Channel Mapping: 0
Timer and counter settings:
N200: 3
N202: 3
K: 7
T200: 1000
T201: 1000
T202: 10000
T203: 10000
T303: 4000
T305: 30000
T308: 4000
T309: 6000
T312: 6000
T313: 4000
T-HOLD: 4000
T-RETRIEVE: 4000
T-RESPONSE: 4000
T-RETENTION: 30000
CC-T1: 30000
CCBS-T2: 3600000
CCNR-T2: 11700000
CC-T3: 30000
Q931 RX: 0
Q931 TX: 0
Q921 RX: 150109
Q921 TX: 150221
Q921 Outstanding: 0 (TEI=0)
Total active-calls:0 global:0
CC records:
Overlap Recv: No

localhost*CLI> pri set debug 2 span 1
Enabled debugging on span 1
PRI Span: 1
PRI Span: 1 < TEI: 0 State 7(Multi-frame established)
PRI Span: 1 < V(A)=0, V(S)=0, V®=0
PRI Span: 1 < K=7, RC=3, l3_initiated=1, reject_except=0, ack_pend=0
PRI Span: 1 < T200_id=0, N200=3, T203_id=8192
PRI Span: 1 < [ 00 01 7f ]
PRI Span: 1 < Unnumbered frame:
PRI Span: 1 < SAPI: 00 C/R: 0 EA: 0
PRI Span: 1 < TEI: 000 EA: 1
PRI Span: 1 < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
PRI Span: 1 < 0 bytes of data
PRI Span: 1 TEI=0 Got SABME from cpe peer.
PRI Span: 1 TEI=0 Sending UA
PRI Span: 1
PRI Span: 1 > TEI: 0 State 7(Multi-frame established)
PRI Span: 1 > V(A)=0, V(S)=0, V®=0
PRI Span: 1 > K=7, RC=3, l3_initiated=1, reject_except=0, ack_pend=0
PRI Span: 1 > T200_id=0, N200=3, T203_id=8192
PRI Span: 1 > [ 00 01 73 ]
PRI Span: 1 > Unnumbered frame:
PRI Span: 1 > SAPI: 00 C/R: 0 EA: 0
PRI Span: 1 > TEI: 000 EA: 1
PRI Span: 1 > M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
PRI Span: 1 > 0 bytes of data
PRI Span: 1 TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
PRI Span: 1 – T200 requested to stop when not started
PRI Span: 1 T203 requested to start without stopping first
PRI Span: 1 – Starting T203 timer
PRI Span: 1 Done handling message for SAPI/TEI=0/0
PRI Span: 1
PRI Span: 1 < TEI: 0 State 7(Multi-frame established)
PRI Span: 1 < V(A)=0, V(S)=0, V®=0
PRI Span: 1 < K=7, RC=3, l3_initiated=1, reject_except=0, ack_pend=0
PRI Span: 1 < T200_id=0, N200=3, T203_id=8192
PRI Span: 1 < [ 00 01 7f ]
PRI Span: 1 < Unnumbered frame:
PRI Span: 1 < SAPI: 00 C/R: 0 EA: 0
PRI Span: 1 < TEI: 000 EA: 1
PRI Span: 1 < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
PRI Span: 1 < 0 bytes of data
PRI Span: 1 TEI=0 Got SABME from cpe peer.
PRI Span: 1 TEI=0 Sending UA
PRI Span: 1
PRI Span: 1 > TEI: 0 State 7(Multi-frame established)
PRI Span: 1 > V(A)=0, V(S)=0, V®=0
PRI Span: 1 > K=7, RC=3, l3_initiated=1, reject_except=0, ack_pend=0
PRI Span: 1 > T200_id=0, N200=3, T203_id=8192
PRI Span: 1 > [ 00 01 73 ]
PRI Span: 1 > Unnumbered frame:
PRI Span: 1 > SAPI: 00 C/R: 0 EA: 0
PRI Span: 1 > TEI: 000 EA: 1
PRI Span: 1 > M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
PRI Span: 1 > 0 bytes of data
PRI Span: 1 TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
PRI Span: 1 – T200 requested to stop when not started
PRI Span: 1 T203 requested to start without stopping first
PRI Span: 1 – Starting T203 timer
PRI Span: 1 Done handling message for SAPI/TEI=0/0
PRI Span: 1
PRI Span: 1 < TEI: 0 State 7(Multi-frame established)
PRI Span: 1 < V(A)=0, V(S)=0, V®=0
PRI Span: 1 < K=7, RC=3, l3_initiated=1, reject_except=0, ack_pend=0
PRI Span: 1 < T200_id=0, N200=3, T203_id=8192
PRI Span: 1 < [ 00 01 7f ]
PRI Span: 1 < Unnumbered frame:
PRI Span: 1 < SAPI: 00 C/R: 0 EA: 0
PRI Span: 1 < TEI: 000 EA: 1
PRI Span: 1 < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
PRI Span: 1 < 0 bytes of data
PRI Span: 1 TEI=0 Got SABME from cpe peer.
PRI Span: 1 TEI=0 Sending UA
PRI Span: 1
PRI Span: 1 > TEI: 0 State 7(Multi-frame established)
PRI Span: 1 > V(A)=0, V(S)=0, V®=0
PRI Span: 1 > K=7, RC=3, l3_initiated=1, reject_except=0, ack_pend=0
PRI Span: 1 > T200_id=0, N200=3, T203_id=8192
PRI Span: 1 > [ 00 01 73 ]
PRI Span: 1 > Unnumbered frame:
PRI Span: 1 > SAPI: 00 C/R: 0 EA: 0
PRI Span: 1 > TEI: 000 EA: 1
PRI Span: 1 > M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
PRI Span: 1 > 0 bytes of data
PRI Span: 1 TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
PRI Span: 1 – T200 requested to stop when not started
PRI Span: 1 T203 requested to start without stopping first
PRI Span: 1 – Starting T203 timer
PRI Span: 1 Done handling message for SAPI/TEI=0/0

The fact that all communications on a PRI are carried in the D (data) channel suggests that you DO have a D channel. Please post the issue of:-

dahdi show status

and

dahdi show channels

You use PRI-NAT so presumable a PBX connection, is your “other end” set up to speak qsig properly?

I reinstalled distro with Asterisk 11 and ran /usr/sbin/wancfg_dahdi instead of using the DAHDi Config Module and the D-Channel synced up properly. Appears that the DAHDi Config Module is configuring something incorrectly.

This config works:

/etc/dahdi/system.conf
#autogenerated by /usr/sbin/wancfg_dahdi do not hand edit
#autogenrated on 2014-01-06
#Dahdi Channels Configurations
#For detailed Dahdi options, view /etc/dahdi/system.conf.bak
loadzone=us
defaultzone=us

#Sangoma A101 port 1 [slot:4 bus:4 span:1]
span=1,1,0,esf,b8zs
bchan=1-23
echocanceller=mg2,1-23
hardhdlc=24

This config does not work:

/etc/dahdi/system.conf

Autogenerated by /usr/sbin/dahdi_genconf on Mon Jan 6 10:49:23 2014

If you edit this file and execute /usr/sbin/dahdi_genconf again,

your manual changes will be LOST.

Dahdi Configuration File

This file is parsed by the Dahdi Configurator, dahdi_cfg

Span 1: WPT1/0 “wanpipe1 card 0” (MASTER) ESF/B8ZS

span=1,1,0,esf,b8zs

termtype: te

bchan=1-23
dchan=24
echocanceller=oslec,1-23

Global data

loadzone = us
defaultzone = us

DAHDi status looks the same with either system.conf file. The other end is a Meridian Option11 and the D-Channel and Trunks will only go in-service when hardhdlc=24 instead of dchan=24.

localhost*CLI> dahdi show status Description Alarms IRQ bpviol CRC Fra Codi Options LBO wanpipe1 card 0 OK 0 0 0 ESF B8ZS 0 db (CSU)/0-133 feet (DSX-1) localhost*CLI> dahdi show channels Chan Extension Context Language MOH Interpret Blocked State Description pseudo default default In Service 1 from-internal default In Service 2 from-internal default In Service 3 from-internal default In Service 4 from-internal default In Service 5 from-internal default In Service 6 from-internal default In Service 7 from-internal default In Service 8 from-internal default In Service 9 from-internal default In Service 10 from-internal default In Service 11 from-internal default In Service 12 from-internal default In Service 13 from-internal default In Service 14 from-internal default In Service 15 from-internal default In Service 16 from-internal default In Service 17 from-internal default In Service 18 from-internal default In Service 19 from-internal default In Service 20 from-internal default In Service 21 from-internal default In Service 22 from-internal default In Service 23 from-internal default In Service

Let me clarify. The trunks only go In-Service on the Nortel end when hardhdlc=24 instead of dchan=24. They show In-Service in Asterisk either way.

I don’t use the dahdi module and have generally used national2 with nortel’s and never a problem with setting the D-channel to 24. But if it works don’t mess with it :wink: