[Asterisk-Users] Zaptel/PRI problem

willy at yponeinc.com willy at yponeinc.com
Sat Apr 10 09:22:51 MST 2004 

To the list ...
The problem appears to be fixed.  Short answer: interrupts.
When looking at cat /proc/interrupts
it was seen that the wct1xxp card was sharing interrupts
with a.o. the eth0 main ethernet driver.
The solution we simple: move the T1 card to another PCI
slot.
Upon checking cat /proc/interrupts again, the card now had
its very own interrupt.  So far I have NOT seen any PRI
notices or warnings.  User experience has been limited due
to a light workload on Friday, and, of course, this being
Easter weekend.
Since this is such a recurring problem (from witnessing list
postings), perhaps digium should have a notice or something
about this when they ship the cards out.  Especially a
relative newbie (first T1 on an asterisk box) like me is
likely to even look at this interrupts situation. 
Especially when there are other issues (zaptel.conf and
zapata.conf) to get a functional system.  
Maybe this deserves a wiki input.  In any case,
Happy Easter
WW
 
----- Original Message Follows -----
> Dimitri,
> I just got off the phone with digium. Here's what I (from
> my notes) the event codes mean
> Event 4: Alarm detected
> Event 5: Alarm cleared
> Event 6: Abort HDLC Frams
> Event 8: Bad HCS
> The 6 & 8 which occur sporadically are possibly causing
> the observed symptoms.
> Now ... what causes 6 & 8 is the question.
> Interrupt conflicts was one suggested possibility. 
> Another possibility is 'stuff' from the Telco which is not
> understood / mis-understood by the driver.
> I'll keep the list posted.
> Willy
> 
> ----- Original Message Follows -----
> > Dear Willy
> >     i notice the same problem with my E100P using the
> > latest cvs zaptel driver i  have try every type of
> > config in /etc/zaptel.conf to check if i have missed 
> > something in timing conf but nothing... Digium help...
> > :-) thanks in advance Dimitri
> > 
> > On Thursday 08 April 2004 23:07, willy at yponeinc.com
> > > wrote: Chris,
> > > Thank you for posting this.  Since it concerns my
> > > 'production' system, let me comment.  After
> > > 'downshifting' to a previous release (for no good
> > > reason other than desperation and teh fact that an
> > > earlier list entry had commented that it cleared up
> > > the problems) I am sad to report that the system
> > > failed again. Miscellaneous throughout the day:
> > > Apr  8 13:41:27 WARNING[-1210639440]: PRI: Read on 32
> > > failed: Unknown error 500
> > > Apr  8 13:41:27 NOTICE[-1210639440]: PRI got event: 8
> > > on span 1
> > > Apr  8 13:41:27 WARNING[-1210639440]: PRI: Read on 32
> > > failed: Unknown error 500
> > > Apr  8 13:41:27 NOTICE[-1210639440]: PRI got event: 6
> > > on span 1
> > > Apr  8 13:42:07 WARNING[-1210639440]: PRI: Read on 32
> > > failed: Unknown error 500
> > > Apr  8 13:42:07 NOTICE[-1210639440]: PRI got event: 8
> > > on span 1
> > > Apr  8 16:44:01 WARNING[-1210631248]: PRI: Read on 34
> > > failed: Unknown error 500
> > > Apr  8 16:44:01 NOTICE[-1210631248]: PRI got event: 6
> > > on span 1
> > > Apr  8 16:44:01 WARNING[-1210631248]: PRI: Read on 34
> > > failed: Unknown error 500
> > > Apr  8 16:44:01 NOTICE[-1210631248]: PRI got event: 6
> > > on span 1
> > >
> > > Then this -- possibly not related ?
> > >
> > > Apr  8 16:51:45 WARNING[-1137157200]: Maximum retries
> > > exceeded on call a642d825c89f2f78 at 192.168.5.188 for
> > > seqno 102 (Request)
> > > Apr  8 16:51:45 WARNING[-1137157200]: Maximum retries
> > > exceeded on call a642d825c89f2f78 at 192.168.5.188 for
> > > seqno 103 (Request)
> > > Apr  8 16:51:45 WARNING[-1137157200]: Maximum retries
> > > exceeded on call a642d825c89f2f78 at 192.168.5.188 for
> > > seqno 104 (Request)
> > > Apr  8 16:51:46 WARNING[-1137157200]: Maximum retries
> > > exceeded on call a642d825c89f2f78 at 192.168.5.188 for
> > > seqno 105 (Request)
> > >
> > > And finally, I'll show you a RESTART log
> > >
> > > Apr  8 17:41:32 WARNING[-1085030272]: Ignoring port
> > > for now Apr  8 17:41:33 WARNING[-1085030272]: XXX I
> > > don't work right with non-full duplex sound cards XXX
> > > Apr  8 17:41:33 WARNING[-1189983312]: Read error on
> > > sound device: Resource temporarily unavailable
> > > Apr  8 17:41:33 ERROR[-1085030272]: Unable to load
> > > config iax1.conf
> > > Apr  8 17:41:38 NOTICE[-1221452880]: Alarm cleared on
> > > channel 1
> > > Apr  8 17:41:38 NOTICE[-1221452880]: Alarm cleared on
> > > channel 2
> > > Apr  8 17:41:38 NOTICE[-1221452880]: Alarm cleared on
> > > channel 3
> > > Apr  8 17:41:38 NOTICE[-1221452880]: Alarm cleared on
> > > channel 4
> > > Apr  8 17:41:38 NOTICE[-1221452880]: Alarm cleared on
> > > channel 5
> > > Apr  8 17:41:38 NOTICE[-1221452880]: Alarm cleared on
> > > channel 6
> > > Apr  8 17:41:38 NOTICE[-1221452880]: Alarm cleared on
> > > channel 7
> > > Apr  8 17:41:38 NOTICE[-1221452880]: Alarm cleared on
> > > channel 8
> > > Apr  8 17:41:38 NOTICE[-1221452880]: Alarm cleared on
> > > channel 9
> > > Apr  8 17:41:38 NOTICE[-1221452880]: Alarm cleared on
> > > channel 10
> > > Apr  8 17:41:38 NOTICE[-1221452880]: Alarm cleared on
> > > channel 11
> > > Apr  8 17:41:38 WARNING[-1210963024]: PRI: Read on 32
> > > failed: Unknown error 500
> > > Apr  8 17:41:38 NOTICE[-1210963024]: PRI got event: 5
> > > on span 1
> > > Apr  8 17:49:10 WARNING[-1221452880]: Detected alarm
> > > on channel 1: Red Alarm
> > > Apr  8 17:49:10 WARNING[-1221452880]: Detected alarm
> > > on channel 2: Red Alarm
> > > Apr  8 17:49:10 WARNING[-1221452880]: Detected alarm
> > > on channel 3: Red Alarm
> > > Apr  8 17:49:10 WARNING[-1221452880]: Detected alarm
> > > on channel 4: Red Alarm
> > > Apr  8 17:49:10 WARNING[-1221452880]: Detected alarm
> > > on channel 5: Red Alarm
> > > Apr  8 17:49:10 WARNING[-1221452880]: Detected alarm
> > > on channel 6: Red Alarm
> > > Apr  8 17:49:10 WARNING[-1221452880]: Detected alarm
> > > on channel 7: Red Alarm
> > > Apr  8 17:49:10 WARNING[-1221452880]: Detected alarm
> > > on channel 8: Red Alarm
> > > Apr  8 17:49:10 WARNING[-1221452880]: Detected alarm
> > > on channel 9: Red Alarm
> > > Apr  8 17:49:10 WARNING[-1221452880]: Detected alarm
> > > on channel 10: Red Alarm
> > > Apr  8 17:49:10 WARNING[-1221452880]: Detected alarm
> > > on channel 11: Red Alarm
> > > Apr  8 17:49:10 WARNING[-1210963024]: PRI: Read on 32
> > > failed: Unknown error 500
> > > Apr  8 17:49:10 NOTICE[-1210963024]: PRI got event: 4
> > > on span 1
> > > Apr  8 17:49:18 NOTICE[-1221452880]: Alarm cleared on
> > > channel 1
> > > Apr  8 17:49:18 NOTICE[-1221452880]: Alarm cleared on
> > > channel 2
> > > Apr  8 17:49:18 NOTICE[-1221452880]: Alarm cleared on
> > > channel 3
> > > Apr  8 17:49:18 NOTICE[-1221452880]: Alarm cleared on
> > > channel 4
> > > Apr  8 17:49:18 NOTICE[-1221452880]: Alarm cleared on
> > > channel 5
> > > Apr  8 17:49:18 NOTICE[-1221452880]: Alarm cleared on
> > > channel 6
> > > Apr  8 17:49:18 NOTICE[-1221452880]: Alarm cleared on
> > > channel 7
> > > Apr  8 17:49:18 NOTICE[-1221452880]: Alarm cleared on
> > > channel 8
> > > Apr  8 17:49:18 NOTICE[-1221452880]: Alarm cleared on
> > > channel 9
> > > Apr  8 17:49:18 NOTICE[-1221452880]: Alarm cleared on
> > > channel 10
> > > Apr  8 17:49:18 NOTICE[-1221452880]: Alarm cleared on
> > > channel 11
> > > Apr  8 17:49:18 WARNING[-1210963024]: PRI: Read on 32
> > > failed: Unknown error 500
> > > Apr  8 17:49:18 NOTICE[-1210963024]: PRI got event: 5
> > > on span 1
> > >
> > > Can someone PLEASE interpret these messages?
> > > BTW: Calls & messages to digium support have gone
> > unanswered >
> > > :(
> > >
> > > TIA
> > > Willy
> > >
> > >
> > > ----- Original Message Follows -----
> > >
> > > > Just a note to the list, this problem still seems to
> > > > exist as late as  2004-04-07.
> > > >
> > > > Symptoms as we have seen it are this.  System runs
> > > > along just fine, no  errors.  At some random
> > > > interval, not based upon time, and not apparently 
> > > > based upon call load, sound drops out on all calls
> > > > made over the Zap (T1  PRI interface in our case
> > > > T100P card).  Any new calls made or received from 
> > > > this time forward have no sound.  The problem is
> > > > temporarily fixed by a  shutdown and restart of the
> > > asterisk code. >
> > > > This will be a major issue for anyone who is
> > > > installing or upgrading a  system using a T1 card
> > > > (our experience is with the single port digium card,
> > > >  but previous postings concerning this issue
> > > > indicate the problem exists  with the 4 port as
> > > well). >
> > > > A temporary work around has been to fall back to the
> > > > CVS version 2004-03-05  10:28 for zaptel and
> > > >  asterisk. We've just upgraded (downgraded) from the
> > > >  current versions to the march 5th versions and will
> > > > be watching to see if  the problem goes away.
> > > >
> > > > Here are some of the error messages we are seeing:
> > > >
> > > > Apr  5 07:57:01 WARNING[-1200284752]: PRI: Read on
> > > > 31 failed: Unknown error 500 Apr  5 07:57:01
> > > > NOTICE[-1200284752]: PRI got event: 8 on span 1
> > > >
> > > > Apr  6 07:10:28 WARNING[-1200215120]: PRI: Read on
> > > > 29 failed: Unknown error 500 Apr  6 07:10:28
> > > > NOTICE[-1200215120]: PRI got event: 5 on span 1
> > > >
> > > > Apr  6 14:22:23 WARNING[-1200260176]: PRI: Read on
> > > > 29 failed: Unknown error 500 Apr  6 14:22:23
> > > > NOTICE[-1200260176]: PRI got event: 6 on span 1
> > > >
> > > > Apr  6 14:53:17 WARNING[-1200165968]: PRI: Read on
> > > > 30 failed: Unknown error 500 Apr  6 14:53:17
> > > > NOTICE[-1200165968]: PRI got event: 5 on span 1
> > > >
> > > > Apr  7 15:00:26 WARNING[-1210471504]: PRI: Read on
> > > > 64 failed: Unknown error 500 Apr  7 15:00:26
> > > > NOTICE[-1210471504]: PRI got event: 5 on span 1
> > > >
> > > > Apr  7 20:33:52 WARNING[-1210508368]: PRI: Read on
> > > > 55 failed: Unknown error 500 Apr  7 20:33:52
> > > > NOTICE[-1210508368]: PRI got event: 8 on span 1
> > > >
> > > > Apr  8 09:42:15 WARNING[-1210725456]: PRI: Read on
> > > > 32 failed: Unknown error 500 Apr  8 09:42:15
> > > > NOTICE[-1210725456]: PRI got event: 5 on span 1
> > > >
> > > > -Chris
> > > >
> > > > On 03:14 AM 3/30/2004, Tais M. Hansen wrote:
> > > >  >-----BEGIN PGP SIGNED MESSAGE-----
> > > >  >Hash: SHA1
> > > >  >
> > > >  >Hi.
> > > >  >
> > > >  >I'm getting the following error at random
> > > intervals on >
> > > > my TE410P with  Asterisk
> > > >
> > > >  >CVS-03/30/04-11:49:01-CEST.
> > > >  >
> > > >  >I have two spans active, one connected to my Telco
> > > , the >
> > > > other to a Siemens
> > > >
> > > >  >PABX. Both spans display this behavior at random
> > > >
> > > > intervals.
> > > >
> > > >  >All calls are dropped when this happens. Spans are
> > > not >
> > > > necessarily in use  when
> > > >
> > > >  >this happens.
> > > >  >
> > > >  >
> > > >  >Mar 30 12:01:41 WARNING[81926]: chan_zap.c:6017
> > > >
> > > > zt_pri_error: PRI: Read  on 72
> > > >
> > > >  >failed: Unknown error 500
> > > >  >Mar 30 12:01:41 NOTICE[81926]: chan_zap.c:6733
> > > >
> > > > pri_dchannel: PRI got  event: 4
> > > >
> > > > <snip>
> > > >
> > > > _______________________________________________
> > > > 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
> > > > Willy Wouters
> > > ypOne Publishing
> > >
> > > _______________________________________________
> > > 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
> 
> Willy Wouters
> ypOne Publishing
> 
> _______________________________________________
> 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

Willy Wouters
ypOne Publishing

More information about the asterisk-users mailing list