[Asterisk-Users] PRI Errors

Tue Mar 16 09:40:15 MST 2004

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 at lists.digium.com 
>[mailto:asterisk-users-admin at lists.digium.com] On Behalf Of 
>Bisker, Scott (7805)
>Sent: Tuesday, March 16, 2004 4:09 PM
>To: asterisk-users at 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 at lists.digium.com
>[mailto:asterisk-users-admin at lists.digium.com]On Behalf Of 
>Scott Stingel
>Sent: Tuesday, March 16, 2004 10:38 AM
>To: asterisk-users at 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 at lists.digium.com 
>>[mailto:asterisk-users-admin at lists.digium.com] On Behalf Of 
>>Andrew McRory
>>Sent: Tuesday, March 16, 2004 6:54 AM
>>To: asterisk-users at 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 at lselinux root]# asterisk -r
>>Asterisk CVS-02/29/04-12:09:10, Copyright (C) 1999-2004 Digium.
>>Written by Mark Spencer <markster at 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 at 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 at 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 at 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
>
>