[Asterisk-Users] TE410P zaptel Driver Situation
Scott Stingel
scott at evtmedia.com
Wed Apr 21 07:40:50 MST 2004
Hi Darren-
In my situation, the frame rejects/retries appear not to cause problems -
even thousands of them, however I found that when I got a lot of "unknown
error 500" messages, they would be associated with "stuck" channels, ie
channels that appeared to be in use when they are not. The stuck channels
get cleared periodically because asterisk clears idle channels automatically
every once in a while.
However, if you get an error 500 during a call, I think the call drops (not
sure).
All of this, of course, only happens during pretty heavy load. It sounds
like formatting a bunch of faxes at the same time would certainly qualify as
heavy load, but I'm not sure if actually trasnmitting them would. Would be
nice to know if the failed faxes correlate to the TE410 errors.
By the way, our theory here from experimentation and looking at the code is
that error 500's are actually unhandled errors from the PRI frame driver,
something like overrun or underrun. This would be consistent with being
caused by heavy load.
Regards
Scott
Scott M. Stingel
President,
Emerging Voice Technology, Inc.
Palo Alto California & London England
www.evtmedia.com
-----Original Message-----
From: asterisk-users-admin at lists.digium.com
[mailto:asterisk-users-admin at lists.digium.com] On Behalf Of Darren Nickerson
Sent: Wednesday, April 21, 2004 6:10 AM
To: asterisk-users at lists.digium.com
Subject: Re: [Asterisk-Users] TE410P zaptel Driver Situation
Scott,
We have 2 PRI spans on a TE405P, and we're sending faxes out 22 channels
concurrently out one span into the other. We were trying to stress our fax
application, but I fear we may have been stressing Asterisk (or the TE405P)
just a little too much as well.
Here's a grep for WARNING from Asterisk's 'messages' log. I have no idea if
any of these are serious, but we definitely saw some failing faxes during
the test. Not sure yet if they correlate with the timing of these errors.
-Darren
Apr 20 18:41:50 WARNING[-1329951824]: PRI: Read on 71 failed: Unknown error
500 Apr 20 18:41:50 WARNING[-1340441680]: PRI: Read on 72 failed: Unknown
error 500 Apr 20 18:46:09 WARNING[-1329951824]: PRI: Read on 71 failed:
Unknown error 500 Apr 20 18:46:10 WARNING[-1340441680]: PRI: Read on 72
failed: Unknown error 500 Apr 20 18:56:58 WARNING[-1329951824]: PRI: Read on
71 failed: Unknown error 500 Apr 20 19:02:22 WARNING[-1340441680]: PRI: Read
on 72 failed: Unknown error 500 Apr 20 19:04:33 WARNING[-1329951824]: PRI:
!! Got reject for frame 69, retransmitting frame 69 now, updating n_r!
Apr 20 19:04:33 WARNING[-1329951824]: PRI: !! Got reject for frame 69,
retransmitting frame 70 now, updating n_r!
Apr 20 19:04:33 WARNING[-1329951824]: PRI: !! Got reject for frame 69,
retransmitting frame 71 now, updating n_r!
Apr 20 19:05:37 WARNING[-1329951824]: PRI: Read on 71 failed: Unknown error
500 Apr 20 19:06:42 WARNING[-1329951824]: PRI: !! Got reject for frame 58,
retransmitting frame 58 now, updating n_r!
Apr 20 19:06:42 WARNING[-1329951824]: PRI: !! Got reject for frame 58,
retransmitting frame 59 now, updating n_r!
Apr 20 19:07:48 WARNING[-1340441680]: PRI: !! Got reject for frame 30,
retransmitting frame 30 now, updating n_r!
Apr 20 19:07:48 WARNING[-1340441680]: PRI: !! Got reject for frame 30,
retransmitting frame 31 now, updating n_r!
Apr 20 19:07:48 WARNING[-1340441680]: PRI: !! Got reject for frame 32, but
we have nothing -- resetting!
Apr 20 19:14:16 WARNING[-1329951824]: PRI: !! Got reject for frame 111,
retransmitting frame 111 now, updating n_r!
Apr 20 19:14:16 WARNING[-1329951824]: PRI: !! Got reject for frame 111,
retransmitting frame 112 now, updating n_r!
Apr 20 19:14:16 WARNING[-1329951824]: PRI: !! Got reject for frame 111,
retransmitting frame 113 now, updating n_r!
Apr 20 19:14:16 WARNING[-1329951824]: PRI: !! Got reject for frame 111,
retransmitting frame 114 now, updating n_r!
Apr 20 19:14:16 WARNING[-1340441680]: PRI: !! Got reject for frame 28,
retransmitting frame 28 now, updating n_r!
Apr 20 19:14:16 WARNING[-1340441680]: PRI: !! Got reject for frame 28,
retransmitting frame 29 now, updating n_r!
Apr 20 19:15:20 WARNING[-1329951824]: PRI: Read on 71 failed: Unknown error
500 Apr 20 19:16:25 WARNING[-1329951824]: PRI: Read on 71 failed: Unknown
error 500 Apr 20 19:16:25 WARNING[-1329951824]: PRI: !! Got reject for frame
32, retransmitting frame 32 now, updating n_r!
Apr 20 19:16:25 WARNING[-1329951824]: PRI: !! Got reject for frame 32,
retransmitting frame 33 now, updating n_r!
Apr 20 19:16:25 WARNING[-1329951824]: PRI: !! Got reject for frame 32,
retransmitting frame 34 now, updating n_r!
Apr 20 19:16:26 WARNING[-1340441680]: PRI: !! Got reject for frame 43,
retransmitting frame 43 now, updating n_r!
Apr 20 19:16:26 WARNING[-1340441680]: PRI: !! Got reject for frame 43,
retransmitting frame 44 now, updating n_r!
Apr 20 19:27:14 WARNING[-1329951824]: PRI: Read on 71 failed: Unknown error
500 Apr 20 19:27:14 WARNING[-1329951824]: PRI: !! Got reject for frame 92,
retransmitting frame 92 now, updating n_r!
Apr 20 19:27:14 WARNING[-1329951824]: PRI: !! Got reject for frame 92,
retransmitting frame 93 now, updating n_r!
Apr 20 19:27:14 WARNING[-1329951824]: PRI: !! Got reject for frame 92,
retransmitting frame 94 now, updating n_r!
Apr 20 19:40:14 WARNING[-1340441680]: PRI: Read on 72 failed: Unknown error
500 Apr 20 19:42:24 WARNING[-1329951824]: PRI: !! Got reject for frame 93,
retransmitting frame 93 now, updating n_r!
Apr 20 19:42:24 WARNING[-1329951824]: PRI: !! Got reject for frame 93,
retransmitting frame 94 now, updating n_r!
Apr 20 19:42:24 WARNING[-1329951824]: PRI: !! Got reject for frame 93,
retransmitting frame 95 now, updating n_r!
Apr 20 19:55:24 WARNING[-1329951824]: PRI: Read on 71 failed: Unknown error
500 Apr 20 20:01:55 WARNING[-1329951824]: PRI: Read on 71 failed: Unknown
error 500 Apr 20 20:05:10 WARNING[-1340441680]: PRI: Read on 72 failed:
Unknown error 500 Apr 20 20:08:25 WARNING[-1329951824]: PRI: Read on 71
failed: Unknown error 500 Apr 20 20:09:30 WARNING[-1340441680]: PRI: !! Got
reject for frame 51, retransmitting frame 51 now, updating n_r!
Apr 20 20:09:30 WARNING[-1340441680]: PRI: !! Got reject for frame 51,
retransmitting frame 52 now, updating n_r!
Apr 20 20:16:00 WARNING[-1329951824]: PRI: Read on 71 failed: Unknown error
500 Apr 20 20:23:36 WARNING[-1329951824]: PRI: Read on 71 failed: Unknown
error 500 Apr 20 20:35:32 WARNING[-1329951824]: PRI: !! Got reject for frame
40, retransmitting frame 40 now, updating n_r!
Apr 20 20:35:32 WARNING[-1329951824]: PRI: !! Got reject for frame 40,
retransmitting frame 41 now, updating n_r!
Apr 20 20:35:32 WARNING[-1340441680]: PRI: !! Got reject for frame 3,
retransmitting frame 3 now, updating n_r!
Apr 20 20:35:32 WARNING[-1340441680]: PRI: !! Got reject for frame 3,
retransmitting frame 4 now, updating n_r!
Apr 20 20:36:03 WARNING[-1340441680]: Call specified, but not found?
Apr 20 20:37:41 WARNING[-1329951824]: PRI: Read on 71 failed: Unknown error
500 Apr 20 20:37:41 WARNING[-1329951824]: PRI: Read on 71 failed: Unknown
error 500 Apr 20 20:37:41 WARNING[-1340441680]: PRI: Read on 72 failed:
Unknown error 500 Apr 20 20:49:37 WARNING[-1329951824]: PRI: Read on 71
failed: Unknown error 500 Apr 20 20:52:52 WARNING[-1340441680]: PRI: !! Got
reject for frame 96, retransmitting frame 96 now, updating n_r!
Apr 20 20:52:52 WARNING[-1340441680]: PRI: !! Got reject for frame 96,
retransmitting frame 97 now, updating n_r!
Apr 20 20:52:53 WARNING[-1329951824]: PRI: !! Got reject for frame 73, retra
nsmitting frame 73 now, updating n_r!
Apr 20 20:52:53 WARNING[-1329951824]: PRI: !! Got reject for frame 73,
retransmitting frame 74 now, updating n_r!
Apr 20 20:52:53 WARNING[-1329951824]: PRI: !! Got reject for frame 73,
retransmitting frame 75 now, updating n_r!
Apr 20 20:52:53 WARNING[-1340441680]: PRI: !! Got reject for frame 97,
retransmitting frame 97 now, updating n_r!
Apr 20 20:52:53 WARNING[-1340441680]: PRI: !! Got reject for frame 97,
retransmitting frame 98 now, updating n_r!
Apr 20 20:52:53 WARNING[-1340441680]: PRI: !! Got reject for frame 97,
retransmitting frame 99 now, updating n_r!
Apr 20 20:52:53 WARNING[-1340441680]: PRI: !! Got reject for frame 98,
retransmitting frame 98 now, updating n_r!
Apr 20 20:52:53 WARNING[-1340441680]: PRI: !! Got reject for frame 98,
retransmitting frame 99 now, updating n_r!
Apr 20 20:52:53 WARNING[-1340441680]: PRI: !! Got reject for frame 100,
retransmitting frame 100 now, updating n_r!
Apr 20 20:52:53 WARNING[-1340441680]: PRI: !! Got reject for frame 101,
retransmitting frame 101 now, updating n_r!
Apr 20 20:52:53 WARNING[-1340441680]: PRI: !! Got reject for frame 102, but
we have nothing -- resetting!
----- Original Message -----
From: "Scott Stingel" <scott at evtmedia.com>
To: <asterisk-users at lists.digium.com>
Sent: Tuesday, April 20, 2004 4:14 PM
Subject: RE: [Asterisk-Users] TE410P zaptel Driver Situation
> Hi Dimitri-
>
> I've gotten lots and lots of these frame-retry messages ever since I put
in
> systems at my customer's sites six months ago (4 very busy IVR systems,
> using both TE410P and E400P cards). It seems to happen with many
different
> versions of asterisk, although I've been shy about switching to the latest
> version recently because of all the changes.
>
> When I discussed this with Mark Spencer a couple months ago, he seemed to
> think that it involved buffer issues (like overflow, underflow) on the PRI
> frame buffer, and so may be load related. I've found that the messages
are
> generally harmless, unless you get a very large number, then they seem to
be
> coorelated with stuck channels.
>
> Do you also get "Unknown error xx" messages as well?
>
> Regards
> Scott Stingel
>
>
> Scott M. Stingel
> President,
> Emerging Voice Technology, Inc.
> Palo Alto California & London England
> www.evtmedia.com
>
> -----Original Message-----
> From: asterisk-users-admin at lists.digium.com
> [mailto:asterisk-users-admin at lists.digium.com] On Behalf Of reseaux
> Sent: Tuesday, April 20, 2004 12:38 PM
> To: asterisk-users at lists.digium.com
> Subject: [Asterisk-Users] TE410P zaptel Driver Situation
>
> Dear List
> i have upgrade my * box with the latest CVS version of Asterisk
> Stable 1.0 and zaptel/libpri my system is MDK9.2 with 1 TE410P and seems
> work well for now but i have a little amount of traffic (25 IN/OUT calls)
i
> only notice this Warning.. What kind of error is?
> -------------------------------
> Apr 20 21:28:49 WARNING[147466]: chan_zap.c:5979 zt_pri_error: PRI: !! Got
> reject for frame 111, retransmitting frame 111 now, updating n_r!
> Apr 20 21:28:49 WARNING[147466]: chan_zap.c:5979 zt_pri_error: PRI: !! Got
> reject for frame 111, retransmitting frame 112 now, updating n_r!
> ---------------------------------------
> Someone know if the timing problem with TE410P is now fixed with a SMP
Xeon
> CPU and works with a lot of call traffic?
> Thank in advance
> Dimitri
> _______________________________________________
> 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
More information about the asterisk-users
mailing list