[Home]

Summary:ASTERISK-14481: HDLC Bad FCS (8) on PRI and call was failed
Reporter:Jay Vaidya (vdyjay)Labels:
Date Opened:2009-07-18 08:30:22Date Closed:2011-06-07 14:08:10
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_zap
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I have asterisk 1.4.21.2 and zaptel version Zaptel Version: 1.4.12.1

I am running this system since last year basically i am doing outbound dialling on server.

Since last 2 week i got following error in my asterisk /var/log/asterisk/message
==========================================================================
[Jul 18 10:29:09] NOTICE[3272] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
[Jul 18 10:29:09] WARNING[3272] chan_zap.c: No D-channels available!  Using Primary channel 16 as D-channel anyway!

[Jul 18 10:29:09] NOTICE[14483] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409906
[Jul 18 10:29:09] NOTICE[14761] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409918
[Jul 18 10:29:09] NOTICE[14482] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409907
[Jul 18 10:29:09] NOTICE[14756] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409917
[Jul 18 10:29:09] NOTICE[14522] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409908
[Jul 18 10:29:09] NOTICE[15016] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409928
[Jul 18 10:29:09] NOTICE[15015] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409927
[Jul 18 10:29:09] NOTICE[14520] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409909
[Jul 18 10:29:09] NOTICE[14575] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409910
[Jul 18 10:29:09] NOTICE[15064] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409930
[Jul 18 10:29:09] NOTICE[14579] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409912
[Jul 18 10:29:09] NOTICE[14879] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409923
[Jul 18 10:29:09] NOTICE[15065] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409929
[Jul 18 10:29:09] NOTICE[14398] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409905
[Jul 18 10:29:09] NOTICE[14929] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409925
[Jul 18 10:29:09] NOTICE[15121] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409932
[Jul 18 10:29:09] NOTICE[14641] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409914
[Jul 18 10:29:09] NOTICE[14931] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409924
[Jul 18 10:29:09] NOTICE[14698] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409916
[Jul 18 10:29:09] NOTICE[14822] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409920
[Jul 18 10:29:09] NOTICE[14310] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409899
[Jul 18 10:29:09] NOTICE[14882] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409921
[Jul 18 10:29:09] NOTICE[14637] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409913
[Jul 18 10:29:09] NOTICE[15124] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409931
[Jul 18 10:29:09] NOTICE[14969] pbx_spool.c: Call failed to go through, reason (1) Hangup  Zap/g2/9275409926
[Jul 18 10:29:10] NOTICE[14444] pbx_spool.c: Call completed to Zap/g3/9277203520
==========================================================================

and then after so many "reason (8) Congestion (circuits busy)"
This issue reproduce regular interval...

Due to this I have so many call loss since last two week..

I earlier post this error( ID 13391) but at that time i closed issue because i found server have limited capacity...but this time server is fully capable...

I dont know why this happen ... I have many log ...if you require i upload here.

Waiting for best reply.



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

zaptel configuration

#span 1

bchan=1-15

dchan=16

bchan=17-31

#span 2

bchan=32-46

dchan=47

bchan=48-62

#span 3

bchan=63-77

dchan=78

bchan=79-93

#span 4

bchan=94-108

dchan=109

bchan=110-124


I am using tormenta Zap 4 E1 PRI card

i am ready for more testing
Comments:By: Leif Madsen (lmadsen) 2009-09-18 08:15:59

I'm not too sure why I can ask you here to provide. Zaptel isn't really all that maintained anymore as DAHDI is the new preferred hardware driver. I'm going to close this issue for now and ask that you open a new issue after you've tested DAHDI; presuming you get the same issue.

If you don't get the same issue, then great! :)