Thanks for the tip, Harry. I will try that when I have exhausted all avenue. My problem is that if I upgrade to 1.4.24 and DAHDI, I'll break other stuffs.
In my current set up, the PRI did work for a long period of time (7 hours) before going into this unreliable mode (up and down). I'm getting the telco technicians to check on this first because I believe the problem comes from their side. During the few hours when it is working, I am able to make and receive calls. So I don't think the issue lies with Asterisk. Regards, Steve Harry Vangberg wrote: > I had the exact same problem and errors some time ago (search the > archives for "PRI dropping #2") using Asterisk 1.4.18, Zaptel and a > Digium TE121. I tried all kind of things, had telco technicians come > out and whatnot. The solution was two-folded - 1) I reinstalled my > server, 2) I updated to Asterisk 1.4.24, replaced Zaptel with latest > DAHDI. In the DAHDI case I even had to use latest Subversion revision > due to some bug (but that was related to the TE121-cards I think). > Since then I haven't had any issues at all, so consider updating > Asterisk and Zaptel->DAHDI > > 2009/3/31 Steven J. Douglas <[email protected]>: > >> Hi Brandon, >> >> When using the current straight cable, it sometimes worked i.e. I can >> make calls from the PSTN into the asterisk. Do you still think that I >> should try a crossover cable? Thanks. >> >> Regards, >> Steve. >> >> Brandon B. wrote: >> >>> Try a T1 crossover cable: >>> >>> http://www.voip-info.org/wiki/view/crossover+T1+cable >>> >>> On Tue, Mar 31, 2009 at 12:37 AM, Steven J. Douglas <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi guys, >>> >>> I've been trying to get my ISDN-10 line up for the past few days, but >>> its been going up and down. I am using OpenVox D110P card on >>> asterisk version 1.4.21. It seems to me like a cable problem. I tried >>> using Ethernet straight cable (12, 45, 36, 78) and also a "straight" >>> cable where the twisted pairs are on 12, 34, 56 and 78. The problem >>> remains the same. >>> >>> /*etc/zaptel.conf* >>> loadzone=sg >>> defaultzone=sg >>> >>> # PRI Span >>> span=1,1,0,ccs,hdb3,crc4 >>> bchan=1-15 >>> dchan=16 >>> bchan=17-31 >>> >>> >>> */etc/asterisk/zapata.conf* >>> language=en >>> progzone=sg >>> musiconhold=default >>> >>> ; PRI Set Up >>> context=inbound-pri1 >>> switchtype=euroisdn >>> signalling=pri_cpe >>> pridialplan=national >>> overlapdial=yes >>> immediate=no >>> faxdetect=both >>> overlapdial=no >>> usecallerid=yes >>> usecallingpres=yes >>> callerid=asreceived >>> group=9 >>> channel => 1-15 >>> channel => 17-31 >>> >>> >>> The following are the messages that keep repeating. >>> >>> == Primary D-Channel on span 1 down >>> Mar 31 14:34:05 WARNING[2361]: chan_zap.c:2682 pri_find_dchan: No >>> D-channels available! Using Primary channel 16 as D-channel anyway! >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 1 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 2 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 3 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 4 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 5 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 6 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 7 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 8 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 9 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 10 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 11 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 12 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 13 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 14 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 15 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 17 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 18 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 19 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 20 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 21 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 22 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 23 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 24 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 25 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 26 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 27 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 28 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 29 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 30 >>> Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm >>> cleared on channel 31 >>> Mar 31 14:34:07 NOTICE[2361]: chan_zap.c:9112 pri_dchannel: PRI got >>> event: No more alarm (5) on Primary D-channel of span 1 >>> == Primary D-Channel on span 1 up >>> == Restart on requested on entire span 1 >>> Mar 31 14:34:08 NOTICE[2361]: chan_zap.c:9112 pri_dchannel: PRI got >>> event: HDLC Abort (6) on Primary D-channel of span 1 >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 1: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 2: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 3: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 4: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 5: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 6: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 7: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 8: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 9: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 10: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 11: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 12: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 13: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 14: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 15: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 17: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 18: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 19: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 20: Red Alarm >>> Mar 31 14:34:08 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 21: Red Alarm >>> Mar 31 14:34:09 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 22: Red Alarm >>> Mar 31 14:34:09 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 23: Red Alarm >>> Mar 31 14:34:09 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 24: Red Alarm >>> Mar 31 14:34:09 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 25: Red Alarm >>> Mar 31 14:34:09 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 26: Red Alarm >>> Mar 31 14:34:09 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 27: Red Alarm >>> Mar 31 14:34:09 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 28: Red Alarm >>> Mar 31 14:34:09 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 29: Red Alarm >>> Mar 31 14:34:09 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 30: Red Alarm >>> Mar 31 14:34:09 WARNING[2362]: chan_zap.c:6899 handle_init_event: >>> Detected alarm on channel 31: Red Alarm >>> Mar 31 14:34:09 NOTICE[2361]: chan_zap.c:9112 pri_dchannel: PRI got >>> event: Alarm (4) on Primary D-channel of span 1 >>> Mar 31 14:34:09 WARNING[2361]: chan_zap.c:2682 pri_find_dchan: No >>> D-channels available! Using Primary channel 16 as D-channel anyway! >>> == Primary D-Channel on span 1 down >>> >>> Any help? >>> >>> Regards, >>> Steve >>> >>> >>> _______________________________________________ >>> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >>> >>> asterisk-users mailing list >>> To UNSUBSCRIBE or update options visit: >>> http://lists.digium.com/mailman/listinfo/asterisk-users >>> >>> >>> >> >> _______________________________________________ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users >> >> _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
