Digium TE131/TE133: Alamrs RED

1

Hello,
We have two Elastix NLX 4000 servers,
with two Digium cards TE131 / TE133, They have all been working fine up
until now. But for two days, we have problems.

Outbound call show:

[2016-06-28 06:13:20] WARNING[10307][C-00000000]: app_dial.c:2437 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 34 - Circuit/channel congestion) == Everyone is busy/congested at this time (1:0/1/0) -- Executing [s@macro-dialout-trunk:23] NoOp("SIP/8000-00000000", "Dial failed for some reason with DIALSTATUS = CONGESTION and HANGUPCAUSE = 34") in new stack

The system shows that cards are detected well and configured (with
the commands dmesg and vim /etc/var/log /messages) but when we make
“dahdi show status” (without having connected the E1 line ) we have:

elx*CLI> dahdi show status Description Alarms IRQ bpviol CRC Fra Codi Options LBO Wildcard TE131/TE133 Card 0 BLU/RED 0 0 0 CCS HDB3 0 db (CSU)/0-133 feet (DSX-1) elx*CLI>
The Alarms must be OK
Our two cards simultaneously had the same problem.

And when we active PRI debug, we have

`elx*CLI> pri set debug on span 1

Enabled debugging on span 1

PRI Span: 1 TEI=0 Sending SABME

PRI Span: 1 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)

PRI Span: 1 Changing from state 5(Awaiting establishment) to 4(TEI assigned)

PRI Span: 1 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)

PRI Span: 1 SAPI/TEI=0/0 Kick starting link

PRI Span: 1 TEI=0 Sending SABME

PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting establishment)

PRI Span: 1 TEI=0 Sending SABME

PRI Span: 1 TEI=0 Sending SABME

PRI Span: 1 TEI=0 Sending SABME

PRI Span: 1 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)

PRI Span: 1 Changing from state 5(Awaiting establishment) to 4(TEI assigned)

PRI Span: 1 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)

PRI Span: 1 SAPI/TEI=0/0 Kick starting link

PRI Span: 1 TEI=0 Sending SABME

PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting establishment)`

We have move the card to another PC but the result is always the same

Thank’s (sorry for my English)

2

http://lists.digium.com/pipermail/asterisk-users/2009-January/225058.html

Blue alarm or AIS (Alarm Indication Signal)

Your T1/E1 port will go into blue alarm when it receives all unframed 1s
on all timeslots from the remote switch. This is a special signal to
indicate that the remote switch is having problems with it’s upstream
connection. As far as I know, dahdi_tool/zttool and Asterisk don’t
correctly indicate a blue alarm (at least I’ve never seen them indicate
one). The easy way to remember this is that streams are blue, so a blue
alarm indicates a problem upstream from the switch you’re connected to.

Maybe your provider is having a bad day :stuck_out_tongue: or the unit that serves the pri lines might have some problem. Contact your provider to debug their side first and then process with the asterisk box.