[Asterisk-Users] Problem with T1 PRI line resetting/droppingcalls.

[Steven Critchfield]

On Fri, 2004-06-04 at 14:02, Gary Franczyk wrote:
> I don't think the question you answered is the same as the one I asked.  The
> problem with mine is the dropping of all the lines/calls.   It resets all
> the lines.
> 
> I get those mystery notices on occasion also, but they don't drop all the
> lines until I see the "Detected Alarm" messages for each line.


Verify with zttool that you are getting the timing from the correct
span. If you are not, I suggest you find a time to actually turn off and
then back on that machine as I have noticed some timing changes only
take place after the card has been powered down. This should help with
your red-alarm problem. Then you can tackle any performance issues that
cause the 500 error if they persist afterwords.

> -----Original Message-----
> From: asterisk-users-admin at lists.digium.com
> [mailto:asterisk-users-admin at lists.digium.com]On Behalf Of Eric Wieling
> Sent: Friday, June 04, 2004 2:00 PM
> To: asterisk-users at lists.digium.com
> Subject: Re: [Asterisk-Users] Problem with T1 PRI line
> resetting/droppingcalls.
> 
> 
> On Fri, 2004-06-04 at 12:09, Gary Franczyk wrote:
> > I am having a serious problem with my Asterisk system.  Every few days, my
> > PRI line resets and drops all calls.  I get these errors in the messages
> > log:
> >
> > Jun  3 02:41:11 WARNING[11276]: PRI: Read on 39 failed: Unknown error 500
> > Jun  3 02:41:11 NOTICE[11276]: PRI got event: 6 on span 1
> > Jun  3 02:41:11 WARNING[12301]: Detected alarm on channel 1: Red Alarm
> 
> I answered this same question *today*:
> 
> 
> 
>      From:
> Eric Wieling <eric at fnords.org>
>  Reply-To:
> eric at fnords.org
>        To:
> asterisk-users at lists.digium.com
>   Subject:
> Re: [Asterisk-Users] Mystery PRI NOTICEs & WARNINGs
>      Date:
> Fri, 04 Jun 2004 10:53:42 -0500
> 
> On Fri, 2004-06-04 at 09:07, Bruce Komito wrote:
> > Since connecting a PRI to a Digium T100P, I have been seeing the
> > following messages in syslog every few minutes:
> >
> > Jun  4 06:51:54 pbx asterisk[13435]: WARNING[1209214400]: chan_zap.c:6176
> in zt_pri_error: PRI: Read on 56 failed: Unknown error 500
> > Jun  4 06:51:54 pbx asterisk[13435]: NOTICE[1209214400]: chan_zap.c:6913
> in pri_dchannel: PRI got event: 8 on span 1
> 
> The new Zaptel has the "zttest" program, which will tell you if
> interrupts are being locked for too long.  This can cause the Error 500
> messages you are seeing.  Causes of interrupts being locked for too long
> can be: graphics, frame buffer, IDE DMA.  There might be other things
> that cause this error, I don't know.
> 
> 
> --
>           Eric Wieling * BTEL Consulting * 504-899-1387 x2111
> "In a related story, the IRS has recently ruled that the cost of Windows
> upgrades can NOT be deducted as a gambling loss."
> 
> _______________________________________________
> 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
-- 
Steven Critchfield  <critch at basesys.com>