[Asterisk-Users] T100P / ZAP / PRI errors

Bisker, Scott (7805) sbisker at harvardgrp.com
Mon Apr 12 10:35:51 MST 2004 

I'm running Zaptel CVS from April 8, LibPRI CVS April 8, and v-1.0 CVS April 7.  With dual T400P cards with no PRI errors at all.  Possibly something driver/config related?  Are you timing from your PRI?  I remember getting some PRI errors when my timing config was hosed.  Could you post your zaptel.conf?  



-----Original Message-----
From: asterisk-users-admin at lists.digium.com
[mailto:asterisk-users-admin at lists.digium.com]On Behalf Of Scott Stingel
Sent: Monday, April 12, 2004 12:09 PM
To: asterisk-users at lists.digium.com
Subject: RE: [Asterisk-Users] T100P / ZAP / PRI errors


Mike-

Do you have access to any kind of PRI test set, like a T-Bird or something.

A red alarm would be easy to capture I imagine - it would be nice to confirm
that it's a problem particular to your site.  The reason I mention software
is that I've noticed a lot of other messages regarding these spurious alarms
that immediately clear.  I've noticed changes in the code having to do with
the timing source.

But maybe you're right about the telco doing something odd!

Cheers
Scott

www.evtmedia.com


-----Original Message-----
From: Mike Sturdee [mailto:sturdee at pathwaynet.com] 
Sent: Monday, April 12, 2004 9:00 AM
To: Scott Stingel
Cc: asterisk-users at lists.digium.com
Subject: RE: [Asterisk-Users] T100P / ZAP / PRI errors

I have been seeing this for over a month, and blaming it on our generally
incompetent telco, so it's definately not a new issue.


On Mon, 12 Apr 2004, Scott Stingel wrote:

> This doesn't appear to be a load issue, since normally in that case I 
> would expect you would get a lot of (usually harmless) "frame reject" 
> messages in your /var/log/asterisk/messages file, and perhaps an 
> occasional "missed/double interrupt" message on the console.
>
> I wonder if there have been new bugs introduced in the PRI code.  I've 
> seen a lot of changes in the timing section of the code at least on the
dev list.
>
> By all means, report it directly to them (a phone call is best).
>
> Cheers
> Scott Stingel
>
> www.evt.media.com
>
>
> -----Original Message-----
> From: asterisk-users-admin at lists.digium.com
> [mailto:asterisk-users-admin at lists.digium.com] On Behalf Of Mike 
> Sturdee
> Sent: Monday, April 12, 2004 8:30 AM
> To: asterisk-users at lists.digium.com
> Subject: [Asterisk-Users] T100P / ZAP / PRI errors
>
> My PRI is being reset at least once a day with the following errors in 
> the logs.
>
> zaptel, zapata, libpri, and asterisk are from CVS this morning.. This 
> has been happening for weeks on all versions (including -stable).
>
> the T100P card appears to NOT be sharing an IRQ.
>
> xenon# cat /proc/interupts
>            CPU0
>   0:    1203977          XT-PIC  timer
>   1:          3          XT-PIC  keyboard
>   2:          0          XT-PIC  cascade
>   5:   12004595          XT-PIC  t1xxp
>   8:          1          XT-PIC  rtc
>   9:    1046347          XT-PIC  eth0
>  14:      21317          XT-PIC  ide0
> NMI:          0
> ERR:          0
> /
>
> Is this something I should be seeking support from Digium on being 
> their card?
>
>
> Apr 12 11:04:59 WARNING[1226062640]: PRI: Short write: -1/15 (Unknown 
> error
> 500) Apr 12 11:04:59 WARNING[1226062640]: Detected alarm on channel 1: 
> Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on 
> channel 2: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to 
> disable echo cancellation on channel 2 Apr 12 11:04:59 
> WARNING[1192491824]: Detected alarm on channel 3: Red Alarm Apr 12 
> 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation on
channel 3 Apr 12 11:04:59 WARNING[1192491824]:
> Detected alarm on channel 4: Red Alarm Apr 12 11:04:59
WARNING[1192491824]:
> Unable to disable echo cancellation on channel 4 Apr 12 11:04:59
> WARNING[1192491824]: Detected alarm on channel 5: Red Alarm Apr 12 
> 11:04:59
> WARNING[1192491824]: Unable to disable echo cancellation on channel 5 
> Apr 12
> 11:04:59 WARNING[1192491824]: Detected alarm on channel 6: Red Alarm 
> Apr 12
> 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation on 
> channel
> 6 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 7: 
> Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo 
> cancellation on channel 7 Apr 12 11:04:59 WARNING[1192491824]: 
> Detected alarm on channel 8: Red Alarm Apr 12 11:04:59 
> WARNING[1192491824]: Unable to disable echo cancellation on channel 8 Apr
12 11:04:59 WARNING[1192491824]:
> Detected alarm on channel 9: Red Alarm Apr 12 11:04:59
WARNING[1192491824]:
> Unable to disable echo cancellation on channel 9 Apr 12 11:04:59
> WARNING[1192491824]: Detected alarm on channel 10: Red Alarm Apr 12 
> 11:04:59
> WARNING[1192491824]: Unable to disable echo cancellation on channel 10 
> Apr
> 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 11: Red 
> Alarm Apr
> 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation 
> on channel 11 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on 
> channel
> 12: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable 
> echo cancellation on channel 12 Apr 12 11:04:59 WARNING[1192491824]: 
> Detected alarm on channel 13: Red Alarm Apr 12 11:04:59 
> WARNING[1192491824]: Unable to disable echo cancellation on channel 13 
> Apr 12 11:04:59
> WARNING[1192491824]: Detected alarm on channel 14: Red Alarm Apr 12 
> 11:04:59
> WARNING[1192491824]: Unable to disable echo cancellation on channel 14 
> Apr
> 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 15: Red 
> Alarm Apr
> 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation 
> on channel 15 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on 
> channel
> 16: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable 
> echo cancellation on channel 16 Apr 12 11:04:59 WARNING[1192491824]: 
> Detected alarm on channel 17: Red Alarm Apr 12 11:04:59 
> WARNING[1192491824]: Unable to disable echo cancellation on channel 17 
> Apr 12 11:04:59
> WARNING[1192491824]: Detected alarm on channel 18: Red Alarm Apr 12 
> 11:04:59
> WARNING[1192491824]: Unable to disable echo cancellation on channel 18 
> Apr
> 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 19: Red 
> Alarm Apr
> 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation 
> on channel 19 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on 
> channel
> 20: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable 
> echo cancellation on channel 20 Apr 12 11:04:59 WARNING[1192491824]: 
> Detected alarm on channel 21: Red Alarm Apr 12 11:04:59 
> WARNING[1192491824]: Unable to disable echo cancellation on channel 21 
> Apr 12 11:04:59
> WARNING[1192491824]: Detected alarm on channel 22: Red Alarm Apr 12 
> 11:04:59
> WARNING[1192491824]: Unable to disable echo cancellation on channel 22 
> Apr
> 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 23: Red 
> Alarm Apr
> 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation 
> on channel 23 Apr 12 11:04:59 WARNING[1184099120]: PRI: Read on 77 failed:
> Unknown error 500 Apr 12 11:04:59 NOTICE[1184099120]: PRI got event: 4 
> on span 1 Apr 12 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 
> 1 Apr 12
> 11:05:04 NOTICE[1192491824]: Alarm cleared on channel 2 Apr 12 
> 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 3 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 4 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 5 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 6 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 7 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 8 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 9 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 10 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 11 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 12 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 13 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 14 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 15 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 16 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 17 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 18 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 19 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 20 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 21 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 22 Apr 12 11:05:04
> NOTICE[1192491824]: Alarm cleared on channel 23 Apr 12 11:05:04
> WARNING[1184099120]: PRI: Read on 77 failed: Unknown error 500 Apr 12
> 11:05:04 NOTICE[1184099120]: PRI got event: 5 on span 1
>
>
> Thanks,
>
> -Mike
>
> _______________________________________________
> 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
>

-Mike

==================================
Network Engineer
Pathway Internet Services
616.774.3131



_______________________________________________
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

More information about the asterisk-users mailing list