PRI / Dahdi / Zap issue all calls on PRI get disconnected

Hi all,

we’re running several asterisk installations in our company, most of them are at version 1.2 but we also have two installations which are already on 1.6.
the asterisk servers are connected over E1 to a Siemens Hipath4000 system to work as a voip gateway.
our problem is, that at some point in time all channels on a complete E1 get disconnected. sometimes this happens more than once a day. we found out that it only happend on systems where we have more than 2 PRI interfaces, so either 2 cards with two interfaces or one card with 4 interfaces… all systems that have a card with only 2 spans don’t have this issue…
during debugging we found out, that we always have the following entry in the log when calls got disconnected:

[Apr 27 10:31:53] WARNING[4716] chan_dahdi.c: No D-channels available! Using Primary channel 16 as D-channel anyway!
[Apr 27 10:33:54] WARNING[4716] chan_dahdi.c: No D-channels available! Using Primary channel 16 as D-channel anyway!
[Apr 27 10:36:43] WARNING[4717] chan_dahdi.c: No D-channels available! Using Primary channel 47 as D-channel anyway!
[Apr 27 11:10:30] WARNING[4716] chan_dahdi.c: No D-channels available! Using Primary channel 16 as D-channel anyway!
[Apr 27 11:10:30] WARNING[4716] chan_dahdi.c: No D-channels available! Using Primary channel 16 as D-channel anyway!

this log is now from one of our 1.6 machines, which has the following versions installed:
dahdi-linux-2.1.0.4
dahdi-tools-2.1.0.2
libpri-1.4.7
asterisk-1.6.0.5
asterisk-addons-1.6.0

as I said before we also have the same problem on our 1.2 machines, they have the following versions installed:
asterisk-1.2.23.4
asterisk-addons-1.2.7_1.2.23-1
zaptel-1.2.22-1
libpri-1.2.5-1

the only differences between all our 1.2 installations are the digium interface cards, the other hardware, operating system and so on is completely the same on all machines…

hope anyone can help us to get this fixed
thanks

see ur dahdi system.conf file. if u assaigned the D-channel Properly. which E1 card u r using? can u post ur system.conf and zaptel.conf file?

hi,

we use
Digium, Inc. Wildcard TE410P Quad-Span togglable E1/T1/J1 card 3.3v (rev 02)
cards

see the config-files below from our 1.2 machines…

cat /etc/sysconfig/zaptel
TELEPHONY=yes
DEBUG=yes

Un-comment as per your requirements; modules to load/unload

genzaptelconf will populate this file

#Module Name Hardware

MODULES="$MODULES wct4xxp" # TE405P - Quad Span T1/E1 Card (5v version)
# TE410P - Quad Span T1/E1 Card (3.3v version)

=============================================
cat /etc/zaptel.conf

span=1,1,0,ccs,hdb3,crc4
span=2,2,0,ccs,hdb3,crc4
span=3,3,0,ccs,hdb3,crc4
span=4,4,0,ccs,hdb3,crc4

bchan = 1-15, 17-31
dchan = 16
bchan = 32-46,48-62
dchan = 47
bchan = 63-77,79-93
dchan = 78
bchan = 94-108,110-124
dchan = 109

Global data

loadzone = de
defaultzone = de

Hi,

Does ur telco support CRC4? If not, u have to disable it by

span=1,1,0,ccs,hdb3
span=2,2,0,ccs,hdb3
span=3,3,0,ccs,hdb3
span=4,4,0,ccs,hdb3

and use ztcfg -vv

zttool to see if the E1 is up

hi,

yes… telco supports crc4 and the interface is green…
as i said at the beginning, in general the system works perfect, its just that the E1 brings randomly this d-channel error and then all calls get disconnected which is very bad.
i googled a little bit and found similar problems but all with no solution on that…
some said that this kind of d-channel warning is normal but this is at least not what my experience tells me.

hi
yes that is really unusual. what about ur dahdi configuration? i m running PRI with with telco using sangoma+dahdi. here is the sample of my dahdi system.conf file. what u see on ur asterisk cli using “pri debug span 1” & “pri show spans” & “pri show span 1” ?

span=1,0,0,ccs,hdb3
bchan=1-15,17-31
dchan=16

Hi

Are you getting any other errors ?

ie yellow or red alarms ?

One very remote thing may be that your ISDN is incompatible with the digium card

Taken from my wiki

[quote] UK ISDN from C&W and possibly others

C&W and maybe others such as NTL/TELEwest seem to supply a lesser version of ISDN30 PRI known as type 85 this is not compatible with the digium cards. the symptoms will be the card coming into service then going out again. Only briefly alarming at the * end but the exchange end stays down. So when ordering ISDN30 for Asterisk make sure you specify type 110 etsi other wise you will get type 85 also if replacing a switch make sure the link is changed as well. [/quote]

and if it is type 85 linkswill drop.

also you ay want to do a pattern test to check the cards. cyber-cottage.co.uk/site/index.p … &Itemid=63

Ian

*CLI> pri show spans
PRI span 1/0: Provisioned, Up, Active
PRI span 2/0: Provisioned, Up, Active
PRI span 3/0: Provisioned, Up, Active
PRI span 4/0: Provisioned, Up, Active

*CLI>pri show span 1
Primary D-channel: 16
Status: Provisioned, Up, Active
Switchtype: EuroISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: -1
T200 Timer: 1000
T203 Timer: 10000
T305 Timer: 30000
T308 Timer: 4000
T313 Timer: 4000
N200 Counter: 3

i’ve now also the pri debugging active in the log…
I also get some other strange entries in the log before the d-chans are reset…

May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 5: Yellow Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 5
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 6: Yellow Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 6
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 8: Yellow Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 8
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 9: Yellow Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 9
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 10: Yellow Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 10
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 17: Yellow Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 17
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 19: No Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 19
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 21: No Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 21
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 23: No Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 23
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 24: No Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 25
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 26: No Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 26
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 27: No Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 27
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 29: No Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 29
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 30: No Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 30
May 4 11:23:09 WARNING[5802] chan_zap.c: Detected alarm on channel 31: No Alarm
May 4 11:23:09 WARNING[5802] chan_zap.c: Unable to disable echo cancellation on channel 31
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 63
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 64
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 65
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 66
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 67
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 68
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 69
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 70
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 71
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 72
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 73
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 75
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 87
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 89
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 90
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 91
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 93
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 2
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 3
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 4
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 5
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 6
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 8
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 9
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 10
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 17
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 19
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 21
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 23
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 24
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 25
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 26
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 27
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 29
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 30
May 4 11:23:09 NOTICE[5802] chan_zap.c: Alarm cleared on channel 31
May 4 11:23:09 NOTICE[5800] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 3
May 4 11:23:09 WARNING[5800] chan_zap.c: No D-channels available! Using Primary channel 78 as D-channel anyway!
May 4 11:23:09 NOTICE[5800] chan_zap.c: PRI got event: No more alarm (5) on Primary D-channel of span 3
May 4 11:23:09 VERBOSE[958] logger.c: NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Call Delivered, peerstate Call Received
May 4 11:23:09 VERBOSE[958] logger.c: Write to 130 failed: Unknown error 500
May 4 11:23:09 VERBOSE[958] logger.c: Short write: 0/15 (Unknown error 500)
May 4 11:23:09 VERBOSE[958] logger.c: > Protocol Discriminator: Q.931 (8) len=9
May 4 11:23:09 VERBOSE[958] logger.c: > Call Ref: len= 2 (reference 867/0x363) (Originator)
May 4 11:23:09 VERBOSE[958] logger.c: > Message type: DISCONNECT (69)
May 4 11:23:09 VERBOSE[958] logger.c: > [08 02 81 90]
May 4 11:23:09 VERBOSE[958] logger.c: > Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1)
May 4 11:23:09 VERBOSE[958] logger.c: > Ext: 1 Cause: Normal Clearing (16), class = Normal Event (1) ]
May 4 11:23:09 VERBOSE[958] logger.c: NEW_HANGUP DEBUG: Destroying the call, ourstate Disconnect Request, peerstate Disconnect Indication
May 4 11:23:09 WARNING[958] chan_zap.c: Detected alarm on channel 12: No Alarm
May 4 11:23:09 VERBOSE[958] logger.c: NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Incoming Call Proceeding, peerstate Outgoing call Proceeding
May 4 11:23:09 VERBOSE[958] logger.c: > Protocol Discriminator: Q.931 (8) len=9
May 4 11:23:09 VERBOSE[958] logger.c: > Call Ref: len= 2 (reference 88/0x58) (Terminator)
May 4 11:23:09 VERBOSE[958] logger.c: > Message type: DISCONNECT (69)
May 4 11:23:09 VERBOSE[958] logger.c: > [08 02 81 90]
May 4 11:23:09 VERBOSE[958] logger.c: > Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1)
May 4 11:23:09 VERBOSE[958] logger.c: > Ext: 1 Cause: Normal Clearing (16), class = Normal Event (1) ]
May 4 11:23:09 VERBOSE[958] logger.c: NEW_HANGUP DEBUG: Destroying the call, ourstate Disconnect Request, peerstate Disconnect Indication
May 4 11:23:09 WARNING[958] chan_zap.c: Detected alarm on channel 77: No Alarm
May 4 11:23:09 VERBOSE[25427] logger.c: NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Active, peerstate Active
May 4 11:23:09 VERBOSE[25427] logger.c: Write to 130 failed: Unknown error 500
May 4 11:23:09 VERBOSE[25427] logger.c: Short write: 0/15 (Unknown error 500)
May 4 11:23:09 VERBOSE[25427] logger.c: > Protocol Discriminator: Q.931 (8) len=9
May 4 11:23:09 VERBOSE[25427] logger.c: > Call Ref: len= 2 (reference 15/0xF) (Terminator)
May 4 11:23:09 VERBOSE[25427] logger.c: > Message type: DISCONNECT (69)
May 4 11:23:09 VERBOSE[958] logger.c: > [08 02 81 90]
May 4 11:23:09 VERBOSE[958] logger.c: > Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1)
May 4 11:23:09 VERBOSE[958] logger.c: > Ext: 1 Cause: Normal Clearing (16), class = Normal Event (1) ]
May 4 11:23:09 VERBOSE[958] logger.c: NEW_HANGUP DEBUG: Destroying the call, ourstate Disconnect Request, peerstate Disconnect Indication
May 4 11:23:09 WARNING[958] chan_zap.c: Detected alarm on channel 77: No Alarm
May 4 11:23:09 VERBOSE[25427] logger.c: NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Active, peerstate Active
May 4 11:23:09 VERBOSE[25427] logger.c: Write to 130 failed: Unknown error 500
May 4 11:23:09 VERBOSE[25427] logger.c: Short write: 0/15 (Unknown error 500)
May 4 11:23:09 VERBOSE[25427] logger.c: > Protocol Discriminator: Q.931 (8) len=9
May 4 11:23:09 VERBOSE[25427] logger.c: > Call Ref: len= 2 (reference 15/0xF) (Terminator)
May 4 11:23:09 VERBOSE[25427] logger.c: > Message type: DISCONNECT (69)
May 4 11:23:09 VERBOSE[25427] logger.c: > [08 02 81 90]
May 4 11:23:09 VERBOSE[25427] logger.c: > Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1)
May 4 11:23:09 VERBOSE[25427] logger.c: > Ext: 1 Cause: Normal Clearing (16), class = Normal Event (1) ]
May 4 11:23:09 VERBOSE[25427] logger.c: NEW_HANGUP DEBUG: Destroying the call, ourstate Disconnect Request, peerstate Disconnect Indication