[Home]

Summary:ASTERISK-15989: All channels get Congestion following PTP MDL can't handle error of type F message
Reporter:Matt King, M.A. Oxon. (kebl0155)Labels:
Date Opened:2010-04-21 03:47:35Date Closed:2011-06-07 14:05:11
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_dahdi
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Hi there,

We have a travel company in the UK experiencing unusually high call volumes.

We upraded their asterisk to SVN versions of LibPri (1.4), Dahdi (2.3 branch) and Asterisk (1.6.1) in order to get a patch for another bug.

This morning the system fell over, with all dial attempts to their PBX giving

Unable to create channel of type 'DAHDI' (cause 34 - Circuit/channel congestion)

Asterisk had to be restarted to restore service.

This was immediately preceded by the following:

[Apr 21 09:03:14] ERROR[17042] chan_dahdi.c: PTP MDL can't handle error of type F
[Apr 21 09:03:14] ERROR[17042] chan_dahdi.c: MDL-ERROR (F), SABME in state 7
[Apr 21 09:03:14] ERROR[17042] chan_dahdi.c: PTP MDL can't handle error of type F
[Apr 21 09:03:14] ERROR[17042] chan_dahdi.c: MDL-ERROR (F), SABME in state 7

They're using a Digium TE205P.  No Alarms were thrown.


****** ADDITIONAL INFORMATION ******

I don't know if it's relevant, but about 20 minutes before, we had:

[Apr 21 08:49:33] ERROR[17042] chan_dahdi.c: !!!!!!!!!!!! Should have only transmitted 0 frames!
[Apr 21 08:49:33] ERROR[17042] chan_dahdi.c: N(R) 41 not within ack window!  Bad Bad Bad!
[Apr 21 08:49:33] ERROR[17042] chan_dahdi.c: PTP MDL can't handle error of type J
[Apr 21 08:49:33] ERROR[17042] chan_dahdi.c: MDL-ERROR (J) in state 7
[Apr 21 08:49:33] ERROR[17042] chan_dahdi.c: Don't know what to do with RR in state 5
[Apr 21 08:49:33] ERROR[17042] chan_dahdi.c: Don't know what to do with RR in state 5
[Apr 21 08:49:33] ERROR[17042] chan_dahdi.c: PTP MDL can't handle error of type F
[Apr 21 08:49:33] ERROR[17042] chan_dahdi.c: MDL-ERROR (F), SABME in state 7

The system did seem to be fine after that though, until we got congestion later.
Comments:By: Leif Madsen (lmadsen) 2010-04-26 11:36:09

I think the PRI debug just prior and following this happening may be useful.
By: Leif Madsen (lmadsen) 2010-04-27 12:37:08

In this case I'm going to refer you to Digium tech support as you have purchased Digium hardware. This will allow you to get in contact with the appropriate people to get this issue resolved. Thanks!
By: Alec Davis (alecdavis) 2010-05-03 23:43:18

Seen it here too:
libpri version: SVN-branch-1.4-r1511M
Asterisk SVN-branch-1.6.1-r250260M
DAHDI Version: SVN-branch-2.2-r7844 Echo Canceller: MG2

[May  4 15:27:28] ERROR[5938] chan_dahdi.c: !!!!!!!!!!!! Should have only transmitted 1 frames!
[May  4 15:27:31] ERROR[5938] chan_dahdi.c: !!!!!!!!!!!! Should have only transmitted 2 frames!
[May  4 15:27:34] ERROR[5938] chan_dahdi.c: !!!!!!!!!!!! Should have only transmitted 3 frames!
[May  4 15:27:38] VERBOSE[5938] chan_dahdi.c: ALEC Fill Ring Event on channel=4, newcr=5687, flexible=0
[May  4 15:27:38] WARNING[5938] chan_dahdi.c: ALEC PRI_EVENT_RING channel 0/4, span 1
[May  4 15:27:38] WARNING[5938] chan_dahdi.c: ALEC SETUP request failed on channel 0/4, span 1
[May  4 15:27:44] ERROR[5938] chan_dahdi.c: !!!!!!!!!!!! Should have only transmitted 3 frames!

CLI 'dahdi restart' fixed it.

Wasn't debugging at the time, so sorry no further information.
By: Leif Madsen (lmadsen) 2010-05-04 16:13:55

Per my note previously, I'm referring anyone with this issue to contact Digium technical support if they have Digium hardware.