I just had the same exact problem this morning. The only thing I've done in the last couple of days is update update zaptel. I rolled back my zaptel to 2/11/04 from 3/8/04. And kept my libpri from 3/8/04. I never had this error before updated. I had other issues, but not this one. -sb -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of Scott Stingel Sent: Tuesday, March 16, 2004 10:38 AM To: asterisk-users@lists.digium.com Subject: RE: [Asterisk-Users] PRI Errors Hi Andrew- The "unknown error 500" and the frame rejects are somewhat normal - I get thousands of these in a busy IVR system. The underlying cause for these, I think, is that your processor occasionally does not keep up with the frame transmitter on the PRI board - something that will happen from time to time, and asterisk should recover. (although, as previously discussed, asterisk's minimal error handling makes this worse than it should be) The red alarms indicate a loss of synchronisation, or a very high bit error rate. This is a basic problem and should not occur. Are you sure the switch is not shutting down the T1's as part of some housekeeping? Regards, Scott M. Stingel Emerging Voice Technology Inc. Palo Alto, California and London, England Email: scott "at" evtmedia.com URL: www.evtmedia.com>-----Original Message----- >From: asterisk-users-admin@lists.digium.com >[mailto:asterisk-users-admin@lists.digium.com] On Behalf Of >Andrew McRory >Sent: Tuesday, March 16, 2004 6:54 AM >To: asterisk-users@lists.digium.com >Subject: [Asterisk-Users] PRI Errors > > >I've been running Asterisk CVS-02/29/04-12:09:10 for a couple of weeks >with no real incidents... > >LEC-PRI --- T400P ----- * ----- SIP/IAX > | > |----- MicroCom ISPorte (faxserver) > | > |----- Max4004 (dialup) > >This configuration has added some flexibility we didn't have >before and I >love it but two weeks of uptime the following errors appeared >in the logs. >All connections were dropped. Is this an * problem or something on the >PRI? > >It happened at 3AM so it wasn't a big deal this time but I >hate to see it >happen in the middle of the day. > > >==============================================================>=========>Mar 14 03:11:54 WARNING[11276]: PRI: Read on 108 failed: >Unknown error 500 >Mar 14 03:11:54 NOTICE[11276]: PRI got event: 6 on span 1 >Mar 14 03:11:54 WARNING[998419]: PRI: Short write: -1/15 >(Unknown error 500) >Mar 14 03:11:54 WARNING[998419]: Detected alarm on channel 1: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 2: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 4: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 5: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 6: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 7: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 8: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 9: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 10: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 11: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 12: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 13: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 14: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 15: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 16: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 17: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 18: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 19: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 20: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 21: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 22: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 23: Red Alarm >Mar 14 03:11:54 WARNING[836629]: PRI: Short write: -1/15 >(Unknown error 500) >Mar 14 03:11:54 WARNING[836629]: Detected alarm on channel 3: Red Alarm >Mar 14 03:11:54 WARNING[11276]: PRI: Read on 108 failed: >Unknown error 500 >Mar 14 03:11:54 NOTICE[11276]: PRI got event: 4 on span 1 >Mar 14 03:11:55 WARNING[12301]: PRI: !! Got reject for frame >105, retransmitting frame 105 now, updating n_r! >Mar 14 03:11:55 WARNING[12301]: PRI: !! Got reject for frame >105, retransmitting frame 106 now, updating n_r! >Mar 14 03:11:55 WARNING[11276]: PRI: !! Got reject for frame >41, retransmitting frame 41 now, updating n_r! >Mar 14 03:11:55 WARNING[11276]: PRI: !! Got reject for frame >41, retransmitting frame 42 now, updating n_r! >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 1 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 2 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 3 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 4 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 5 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 6 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 7 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 8 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 9 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 10 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 11 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 12 >Mar 14 03:11:59 WARNING[11276]: PRI: Read on 108 failed: >Unknown error 500 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 13 >Mar 14 03:11:59 NOTICE[11276]: PRI got event: 5 on span 1 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 14 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 15 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 16 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 17 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 18 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 19 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 20 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 21 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 22 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 23 > >/etc/zaptel.conf >=======================================================>span=1,1,0,esf,b8zs >span=2,0,0,esf,b8zs >span=3,0,0,esf,b8zs >span=4,0,0,esf,b8zs >bchan=1-23 >dchan=24 >bchan=25-47 >dchan=48 >bchan=49-71 >dchan=72 >bchan=73-95 >dchan=96 > >/etc/asterisk/zapata.conf >==============================================>[channels] >context=pri-01 >signalling=pri_cpe >switchtype=national >usecallerid=yes >group=1 >echocancel = no >echocancelwhenbridged = no >channel => 1-23 >context=max4004-01 >signalling=pri_net >switchtype=national >usecallerid=yes >group=2 >echocancel = no >echocancelwhenbridged = no >channel => 25-47 >context=isporte-01 >signalling=pri_net >switchtype=national >usecallerid=yes >group=3 >channel => 49-71 >context=local >switchtype=national >signalling=pri_net >usecallerid=yes >group=4 >channel => 73-95 > >uptime >=================================================================>[root@lselinux root]# asterisk -r >Asterisk CVS-02/29/04-12:09:10, Copyright (C) 1999-2004 Digium. >Written by Mark Spencer <markster@digium.com> >Connected to Asterisk CVS-02/29/04-12:09:10 currently running >on lselinux >(pid = 4377) > -- Remote UNIX connection >lselinux*CLI> show uptime >System uptime: 2 weeks, 20 hours, 37 minutes, 51 seconds >Last reload: 4 days, 13 hours, 55 minutes, 33 seconds >lselinux*CLI> > > > >Regards, > >-- >Andrew McRory - President/CTO >Linux Systems Engineers, Inc. >PO BOX 3791 >Tallahassee, FL 32315 >(850)224-5737 >(850)294-7567 > > >_______________________________________________ >Asterisk-Users mailing list >Asterisk-Users@lists.digium.com >http://lists.digium.com/mailman/listinfo/asterisk-users >To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >_______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
ooo, sounds like a bug. Maybe a counter is overflowing somewhere! Scott M. Stingel Emerging Voice Technology Inc. Palo Alto, California and London, England Email: scott "at" evtmedia.com URL: www.evtmedia.com>-----Original Message----- >From: asterisk-users-admin@lists.digium.com >[mailto:asterisk-users-admin@lists.digium.com] On Behalf Of >Bisker, Scott (7805) >Sent: Tuesday, March 16, 2004 4:09 PM >To: asterisk-users@lists.digium.com >Subject: RE: [Asterisk-Users] PRI Errors > >I just had the same exact problem this morning. The only >thing I've done in the last couple of days is update update >zaptel. I rolled back my zaptel to 2/11/04 from 3/8/04. And >kept my libpri from 3/8/04. I never had this error before >updated. I had other issues, but not this one. > >-sb > > >-----Original Message----- >From: asterisk-users-admin@lists.digium.com >[mailto:asterisk-users-admin@lists.digium.com]On Behalf Of >Scott Stingel >Sent: Tuesday, March 16, 2004 10:38 AM >To: asterisk-users@lists.digium.com >Subject: RE: [Asterisk-Users] PRI Errors > > >Hi Andrew- > >The "unknown error 500" and the frame rejects are somewhat >normal - I get >thousands of these in a busy IVR system. The underlying cause >for these, I >think, is that your processor occasionally does not keep up >with the frame >transmitter on the PRI board - something that will happen from >time to time, >and asterisk should recover. (although, as previously >discussed, asterisk's >minimal error handling makes this worse than it should be) > >The red alarms indicate a loss of synchronisation, or a very >high bit error >rate. This is a basic problem and should not occur. Are you sure the >switch is not shutting down the T1's as part of some housekeeping? > >Regards, > >Scott M. Stingel >Emerging Voice Technology Inc. >Palo Alto, California and London, England > >Email: scott "at" evtmedia.com >URL: www.evtmedia.com > > > >>-----Original Message----- >>From: asterisk-users-admin@lists.digium.com >>[mailto:asterisk-users-admin@lists.digium.com] On Behalf Of >>Andrew McRory >>Sent: Tuesday, March 16, 2004 6:54 AM >>To: asterisk-users@lists.digium.com >>Subject: [Asterisk-Users] PRI Errors >> >> >>I've been running Asterisk CVS-02/29/04-12:09:10 for a couple >of weeks >>with no real incidents... >> >>LEC-PRI --- T400P ----- * ----- SIP/IAX >> | >> |----- MicroCom ISPorte (faxserver) >> | >> |----- Max4004 (dialup) >> >>This configuration has added some flexibility we didn't have >>before and I >>love it but two weeks of uptime the following errors appeared >>in the logs. >>All connections were dropped. Is this an * problem or something on the >>PRI? >> >>It happened at 3AM so it wasn't a big deal this time but I >>hate to see it >>happen in the middle of the day. >> >> >>==============================================================>>=========>>Mar 14 03:11:54 WARNING[11276]: PRI: Read on 108 failed: >>Unknown error 500 >>Mar 14 03:11:54 NOTICE[11276]: PRI got event: 6 on span 1 >>Mar 14 03:11:54 WARNING[998419]: PRI: Short write: -1/15 >>(Unknown error 500) >>Mar 14 03:11:54 WARNING[998419]: Detected alarm on channel 1: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 2: Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 4: Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 5: Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 6: Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 7: Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 8: Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 9: Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 10: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 11: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 12: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 13: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 14: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 15: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 16: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 17: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 18: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 19: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 20: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 21: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 22: >Red Alarm >>Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 23: >Red Alarm >>Mar 14 03:11:54 WARNING[836629]: PRI: Short write: -1/15 >>(Unknown error 500) >>Mar 14 03:11:54 WARNING[836629]: Detected alarm on channel 3: >Red Alarm >>Mar 14 03:11:54 WARNING[11276]: PRI: Read on 108 failed: >>Unknown error 500 >>Mar 14 03:11:54 NOTICE[11276]: PRI got event: 4 on span 1 >>Mar 14 03:11:55 WARNING[12301]: PRI: !! Got reject for frame >>105, retransmitting frame 105 now, updating n_r! >>Mar 14 03:11:55 WARNING[12301]: PRI: !! Got reject for frame >>105, retransmitting frame 106 now, updating n_r! >>Mar 14 03:11:55 WARNING[11276]: PRI: !! Got reject for frame >>41, retransmitting frame 41 now, updating n_r! >>Mar 14 03:11:55 WARNING[11276]: PRI: !! Got reject for frame >>41, retransmitting frame 42 now, updating n_r! >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 1 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 2 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 3 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 4 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 5 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 6 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 7 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 8 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 9 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 10 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 11 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 12 >>Mar 14 03:11:59 WARNING[11276]: PRI: Read on 108 failed: >>Unknown error 500 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 13 >>Mar 14 03:11:59 NOTICE[11276]: PRI got event: 5 on span 1 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 14 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 15 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 16 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 17 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 18 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 19 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 20 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 21 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 22 >>Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 23 >> >>/etc/zaptel.conf >>=======================================================>>span=1,1,0,esf,b8zs >>span=2,0,0,esf,b8zs >>span=3,0,0,esf,b8zs >>span=4,0,0,esf,b8zs >>bchan=1-23 >>dchan=24 >>bchan=25-47 >>dchan=48 >>bchan=49-71 >>dchan=72 >>bchan=73-95 >>dchan=96 >> >>/etc/asterisk/zapata.conf >>==============================================>>[channels] >>context=pri-01 >>signalling=pri_cpe >>switchtype=national >>usecallerid=yes >>group=1 >>echocancel = no >>echocancelwhenbridged = no >>channel => 1-23 >>context=max4004-01 >>signalling=pri_net >>switchtype=national >>usecallerid=yes >>group=2 >>echocancel = no >>echocancelwhenbridged = no >>channel => 25-47 >>context=isporte-01 >>signalling=pri_net >>switchtype=national >>usecallerid=yes >>group=3 >>channel => 49-71 >>context=local >>switchtype=national >>signalling=pri_net >>usecallerid=yes >>group=4 >>channel => 73-95 >> >>uptime >>=================================================================>>[root@lselinux root]# asterisk -r >>Asterisk CVS-02/29/04-12:09:10, Copyright (C) 1999-2004 Digium. >>Written by Mark Spencer <markster@digium.com> >>Connected to Asterisk CVS-02/29/04-12:09:10 currently running >>on lselinux >>(pid = 4377) >> -- Remote UNIX connection >>lselinux*CLI> show uptime >>System uptime: 2 weeks, 20 hours, 37 minutes, 51 seconds >>Last reload: 4 days, 13 hours, 55 minutes, 33 seconds >>lselinux*CLI> >> >> >> >>Regards, >> >>-- >>Andrew McRory - President/CTO >>Linux Systems Engineers, Inc. >>PO BOX 3791 >>Tallahassee, FL 32315 >>(850)224-5737 >>(850)294-7567 >> >> >>_______________________________________________ >>Asterisk-Users mailing list >>Asterisk-Users@lists.digium.com >>http://lists.digium.com/mailman/listinfo/asterisk-users >>To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users >> >> > >_______________________________________________ >Asterisk-Users mailing list >Asterisk-Users@lists.digium.com >http://lists.digium.com/mailman/listinfo/asterisk-users >To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >_______________________________________________ >Asterisk-Users mailing list >Asterisk-Users@lists.digium.com >http://lists.digium.com/mailman/listinfo/asterisk-users >To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >
Update on this. I had the exact same issue today. At almost exactly the same time as yesterday. Possible telco problem? Timing issue with zaptel? Never had this issue before updating libpri as of 3/8. Here's zaptel.conf span 7 is PRI from Verizon, span 8 is T-1 from Sprint. Dual T400P, SMP.... # span=1,1,0,esf,b8zs span=2,1,0,esf,b8zs span=3,1,0,esf,b8zs span=4,1,0,esf,b8zs span=5,1,0,esf,b8zs span=6,1,0,esf,b8zs span=7,0,0,esf,b8zs span=8,0,0,esf,b8zs e&m=1-12 fxoks=13-24 fxoks=25-48 fxoks=49-72 fxoks=73-96 fxoks=97-120 fxoks=121-144 e&m=145-168 bchan=169-191 dchan=192 -sb -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of Bisker, Scott (7805) Sent: Tuesday, March 16, 2004 11:09 AM To: asterisk-users@lists.digium.com Subject: RE: [Asterisk-Users] PRI Errors I just had the same exact problem this morning. The only thing I've done in the last couple of days is update update zaptel. I rolled back my zaptel to 2/11/04 from 3/8/04. And kept my libpri from 3/8/04. I never had this error before updated. I had other issues, but not this one. -sb -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of Scott Stingel Sent: Tuesday, March 16, 2004 10:38 AM To: asterisk-users@lists.digium.com Subject: RE: [Asterisk-Users] PRI Errors Hi Andrew- The "unknown error 500" and the frame rejects are somewhat normal - I get thousands of these in a busy IVR system. The underlying cause for these, I think, is that your processor occasionally does not keep up with the frame transmitter on the PRI board - something that will happen from time to time, and asterisk should recover. (although, as previously discussed, asterisk's minimal error handling makes this worse than it should be) The red alarms indicate a loss of synchronisation, or a very high bit error rate. This is a basic problem and should not occur. Are you sure the switch is not shutting down the T1's as part of some housekeeping? Regards, Scott M. Stingel Emerging Voice Technology Inc. Palo Alto, California and London, England Email: scott "at" evtmedia.com URL: www.evtmedia.com>-----Original Message----- >From: asterisk-users-admin@lists.digium.com >[mailto:asterisk-users-admin@lists.digium.com] On Behalf Of >Andrew McRory >Sent: Tuesday, March 16, 2004 6:54 AM >To: asterisk-users@lists.digium.com >Subject: [Asterisk-Users] PRI Errors > > >I've been running Asterisk CVS-02/29/04-12:09:10 for a couple of weeks >with no real incidents... > >LEC-PRI --- T400P ----- * ----- SIP/IAX > | > |----- MicroCom ISPorte (faxserver) > | > |----- Max4004 (dialup) > >This configuration has added some flexibility we didn't have >before and I >love it but two weeks of uptime the following errors appeared >in the logs. >All connections were dropped. Is this an * problem or something on the >PRI? > >It happened at 3AM so it wasn't a big deal this time but I >hate to see it >happen in the middle of the day. > > >==============================================================>=========>Mar 14 03:11:54 WARNING[11276]: PRI: Read on 108 failed: >Unknown error 500 >Mar 14 03:11:54 NOTICE[11276]: PRI got event: 6 on span 1 >Mar 14 03:11:54 WARNING[998419]: PRI: Short write: -1/15 >(Unknown error 500) >Mar 14 03:11:54 WARNING[998419]: Detected alarm on channel 1: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 2: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 4: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 5: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 6: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 7: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 8: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 9: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 10: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 11: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 12: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 13: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 14: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 15: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 16: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 17: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 18: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 19: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 20: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 21: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 22: Red Alarm >Mar 14 03:11:54 WARNING[15376]: Detected alarm on channel 23: Red Alarm >Mar 14 03:11:54 WARNING[836629]: PRI: Short write: -1/15 >(Unknown error 500) >Mar 14 03:11:54 WARNING[836629]: Detected alarm on channel 3: Red Alarm >Mar 14 03:11:54 WARNING[11276]: PRI: Read on 108 failed: >Unknown error 500 >Mar 14 03:11:54 NOTICE[11276]: PRI got event: 4 on span 1 >Mar 14 03:11:55 WARNING[12301]: PRI: !! Got reject for frame >105, retransmitting frame 105 now, updating n_r! >Mar 14 03:11:55 WARNING[12301]: PRI: !! Got reject for frame >105, retransmitting frame 106 now, updating n_r! >Mar 14 03:11:55 WARNING[11276]: PRI: !! Got reject for frame >41, retransmitting frame 41 now, updating n_r! >Mar 14 03:11:55 WARNING[11276]: PRI: !! Got reject for frame >41, retransmitting frame 42 now, updating n_r! >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 1 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 2 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 3 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 4 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 5 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 6 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 7 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 8 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 9 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 10 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 11 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 12 >Mar 14 03:11:59 WARNING[11276]: PRI: Read on 108 failed: >Unknown error 500 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 13 >Mar 14 03:11:59 NOTICE[11276]: PRI got event: 5 on span 1 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 14 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 15 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 16 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 17 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 18 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 19 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 20 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 21 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 22 >Mar 14 03:11:59 NOTICE[15376]: Alarm cleared on channel 23 > >/etc/zaptel.conf >=======================================================>span=1,1,0,esf,b8zs >span=2,0,0,esf,b8zs >span=3,0,0,esf,b8zs >span=4,0,0,esf,b8zs >bchan=1-23 >dchan=24 >bchan=25-47 >dchan=48 >bchan=49-71 >dchan=72 >bchan=73-95 >dchan=96 > >/etc/asterisk/zapata.conf >==============================================>[channels] >context=pri-01 >signalling=pri_cpe >switchtype=national >usecallerid=yes >group=1 >echocancel = no >echocancelwhenbridged = no >channel => 1-23 >context=max4004-01 >signalling=pri_net >switchtype=national >usecallerid=yes >group=2 >echocancel = no >echocancelwhenbridged = no >channel => 25-47 >context=isporte-01 >signalling=pri_net >switchtype=national >usecallerid=yes >group=3 >channel => 49-71 >context=local >switchtype=national >signalling=pri_net >usecallerid=yes >group=4 >channel => 73-95 > >uptime >=================================================================>[root@lselinux root]# asterisk -r >Asterisk CVS-02/29/04-12:09:10, Copyright (C) 1999-2004 Digium. >Written by Mark Spencer <markster@digium.com> >Connected to Asterisk CVS-02/29/04-12:09:10 currently running >on lselinux >(pid = 4377) > -- Remote UNIX connection >lselinux*CLI> show uptime >System uptime: 2 weeks, 20 hours, 37 minutes, 51 seconds >Last reload: 4 days, 13 hours, 55 minutes, 33 seconds >lselinux*CLI> > > > >Regards, > >-- >Andrew McRory - President/CTO >Linux Systems Engineers, Inc. >PO BOX 3791 >Tallahassee, FL 32315 >(850)224-5737 >(850)294-7567 > > >_______________________________________________ >Asterisk-Users mailing list >Asterisk-Users@lists.digium.com >http://lists.digium.com/mailman/listinfo/asterisk-users >To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >_______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Oh nooo. Completely missed the boat on this one. I was thinking the exact opposite on this. I thought that if set to 1, then the span would _provide_ timing for the connected circuit. My span 1-6 are channel banks and I thought the 1 was providing the timing for the banks, not the other way around I now see my error. I'm suprised I've not had more issues than this. Thanks. -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of Marcin Kuzmicki Sent: Wednesday, March 17, 2004 3:32 PM To: asterisk-users@lists.digium.com Subject: RE: [Asterisk-Users] PRI Errors Hi, Maybe I'm wrong but you have different oprators - two different switches and you dont synchronize with them you dont use them as your timing source I'd go like like this span=1,0,0,esf,b8zs span=2,0,0,esf,b8zs span=3,0,0,esf,b8zs span=4,0,0,esf,b8zs span=5,0,0,esf,b8zs span=6,0,0,esf,b8zs span=7,1,0,esf,b8zs span=8,2,0,esf,b8zs rgrds Quoting "Bisker, Scott (7805)" <sbisker@harvardgrp.com>:> Update on this. I had the exact same issue today. At almost exactly the > same time as yesterday. Possible telco problem? Timing issue with zaptel? > Never had this issue before updating libpri as of 3/8. > > Here's zaptel.conf span 7 is PRI from Verizon, span 8 is T-1 from Sprint. > Dual T400P, SMP.... > > # > span=1,1,0,esf,b8zs > span=2,1,0,esf,b8zs > span=3,1,0,esf,b8zs > span=4,1,0,esf,b8zs > span=5,1,0,esf,b8zs > span=6,1,0,esf,b8zs > span=7,0,0,esf,b8zs > span=8,0,0,esf,b8zs > > e&m=1-12 > fxoks=13-24 > fxoks=25-48 > fxoks=49-72 > fxoks=73-96 > fxoks=97-120 > fxoks=121-144 > e&m=145-168 > bchan=169-191 > dchan=192 > >_______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
For a few weeks we have been getting errors that drop our PRI. The telco says the the line is clean and that our equipment is the problem. We're currently running "Asterisk CVS-HEAD-12/03/04" but several versions have been tried in an attempt to fix the problem. The * server is based on a supermicro 1U chassis with a PIII 1.266GHz, 512MB RAM and a tor2 4port PCI card. The Tor2 card is on IRQ 11 which IS shared with an *unused* ethernet controller and USB port. It has worked like this for a long while. A single PRI is connected to port 1, a Microcom 4000/ISPorte is on port 2 and a Max 4000 is on port 3. We accept data and voice calls. When PRI drops, all calls are disconnected. If you happen to be on a voice call, you hear a brief PFFFT! as everything goes away. The line resyncs in a minute and everything operates normally until the next error. SIP <--> SIP calls continue to work properly while the PRI is down. Our dialplan is extremely basic (too basic!) and has been in use since March/04. Until now the system has been very stable. The only time * has been down was when one of us botched the dialplan but that was found and fixed months ago. To save list bandwidth I'm linking the errors: http://www.linuxsys.com/files/pritrubbl.txt Before I tell the telco to come out I'd like a little insight to the error messages. Please copy replies to me directly. Thanks, -- Andrew McRory - President/CTO Linux Systems Engineers, Inc. - http://www.linuxsys.com Located in beautiful Tallahassee, Florida Office 850-224-5737 Office 850-575-7213 Mobile 850-294-7567
Dec 8 10:10:54 NOTICE[620]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Dec 8 10:10:54 NOTICE[620]: chan_zap.c:7494 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Dec 8 10:10:54 WARNING[620]: chan_zap.c:7246 zt_pri_error: PRI: Short write: -1/15 (Unknown error 500) Dec 8 10:10:54 WARNING[620]: chan_zap.c:3202 zt_handle_event: Detected alarm on channel 1: Red Alarm -- Hungup 'Zap/25-1' Folks it's getting worse. I have managed to get the USB irq off the tor2 irq but still have eth0. Damn BIOS will not allow me to force the IRQ to the PCI slot.. grrr. This system ran for months without any error and now it's killing me. Do the errors above indicate line or IRQ related problems???? Thanks, Andrew
> On December 7, 2004 11:42 am, Andrew McRory wrote: > > For a few weeks we have been getting errors that drop our PRI. The telco > > says the the line is clean and that our equipment is the problem. We're > > currently running "Asterisk CVS-HEAD-12/03/04" but several versions > > have been tried in an attempt to fix the problem. > > Have you gone back to the version that was known stable?yes> Also have you run zttest (you have to build this explicitly in the zaptel > directory)? What's it showing for accuracy? Can you get it to run while > this problem is occurring?--- Results after 353 passes --- Best: 100.000000 -- Worst: 99.975586 The line dropped twice while this test was going on. accuracy stayed the same during the drop. got 99.975586 only when I ran "updatedb"> What distribution, which kernel? Has anything about these boxes changed in > the last while that you can think of? Software updates of any kind?It's running Fedora Core 1, 2.4.22 based on the nptl src.rpm. No significant change. seems to have the same problem regardless of asterisk version I run so I've stayed with the current CVS. Andrew
OK, it looks like the problem was indeed shared interrupts! Funny thing how this server would run since January 04 without much problem then, overnight, start screwing up all over the place. I disabled the USB and secondary onboard ethernet to get the TDM400 on its own IRQ. Has been perfectly stable for (2) days. BIG thanks to those who responded to this thread! -- Andrew McRory - President/CTO Linux Systems Engineers, Inc. - http://www.linuxsys.com Located in beautiful Tallahassee, Florida Office 850-224-5737 Office 850-575-7213 Mobile 850-294-7567