Re: [Asterisk-Users] TE410P zaptel Driver Situation

2004-04-21 Thread Nicolas Bougues
On Wed, Apr 21, 2004 at 01:17:23PM -0700, Scott Stingel wrote:
> 
> 
> >Dear Scott
>   the "reject" warning is a bug? I must put in bug track?
> >Thanks in advance
> >Dimitri
> 
> No, not a bug I don't think.  A warning that the framer driver was not able
> to keep up with the PRI bit stream. 
> 

Zaptel hardware handles HDLC framing in software. Thus, if for some
reason a Zaptel frame (8 bytes) is lost, a full HDLC frame will be
lost, and it will be detected on the next one, thus the error
message.

The main reason it can happen is probably because of the server
load. The driver can't poll the zaptel device fast enough. However,
it's not clear to me how it can happen on busmaster devices such as
T405P and T410P. Maybe a double buffering issue, or PCI bus load. Or
maybe an interrupt fault; the Zaptel hardware provides a kHz interrupt
to the driver for polling, and an interrupt might get lost
(particularly if the IRQ line is shared). However, it seems to be
detected by the driver (and it should print a warning).

-- 
Nicolas Bougues
Axialys Interactive
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


RE: [Asterisk-Users] TE410P zaptel Driver Situation

2004-04-21 Thread Scott Stingel


>Dear Scott
the "reject" warning is a bug? I must put in bug track?
>Thanks in advance
>Dimitri

No, not a bug I don't think.  A warning that the framer driver was not able
to keep up with the PRI bit stream. 


Scott M. Stingel 
Emerging Voice Technology Inc.
Palo Alto, California and London, England

URL:www.evtmedia.com  

___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] TE410P zaptel Driver Situation

2004-04-21 Thread reseaux
Dear Scott
the "reject" warning is a bug? I must put in bug track?
Thanks in advance
Dimitri
On Wednesday 21 April 2004 07:44 pm, Scott Stingel wrote:
> Dimitri-
> I'm not sure about the message "Unable to forward voice" - I don't get that
> one on my systems.
>
> The frame "reject" messages are the same ones I was talking about - these
> are load related, I'm pretty sure.
>
> Regards,
>
>
> Scott M. Stingel
> President,
> Emerging Voice Technology, Inc.
> Palo Alto California & London England
> www.evtmedia.com
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of reseaux
> Sent: Wednesday, April 21, 2004 9:48 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Asterisk-Users] TE410P zaptel Driver Situation
>
> Dear Scott
>   i have notice the same type of warning plus another with my TE410P
> with not very high load 30 IN/OUT line, i use only two span in this moment.
> What is only warning? or not?
> Thanks in advance
> Dimitri
> 
> Apr 21 10:27:35 WARNING[966674]: Unable to forward voice Apr 21 10:28:41
> WARNING[999442]: Unable to forward frame Apr 21 10:30:11 WARNING[1048594]:
> Unable to forward frame Apr 21 10:32:02 WARNING[1130515]: Unable to forward
> frame Apr 21 10:34:56 WARNING[1212434]: Unable to forward frame Apr 21
> 10:35:45 WARNING[1245202]: Unable to forward frame Apr 21 10:36:34
> WARNING[1277970]: Unable to forward frame Apr 21 10:37:02 WARNING[1294354]:
> Unable to forward frame Apr 21 10:40:03 WARNING[1359891]: Unable to forward
> frame Apr 21 10:45:51 WARNING[1441811]: Unable to forward frame Apr 21
> 10:47:15 WARNING[1474579]: Unable to forward frame Apr 21 10:47:21
> WARNING[1490963]: Unable to forward frame Apr 21 10:49:57 WARNING[1540115]:
> Unable to forward frame Apr 21 10:50:26 WARNING[1572883]: Unable to forward
> frame Apr 21 10:51:25 WARNING[1622035]: Unable to forward voice Apr 21
> 11:11:42 WARNING[1851410]: Unable to forward frame Apr 21 11:19:20
> WARNING[2097170]: Unable to forward frame Apr 21 11:29:17 WARNING[2228243]:
> Unable to forward voice Apr 21 11:31:39 WARNING[2375700]: Unable to forward
> frame Apr 21 11:45:30 WARNING[2588692]: Unable to forward frame Apr 21
> 11:53:00 WARNING[2686995]: Unable to forward frame Apr 21 11:56:14
> WARNING[2752531]: Unable to forward frame Apr 21 11:58:31 WARNING[2850837]:
> Unable to forward voice Apr 21 11:59:13 WARNING[2867219]: Unable to forward
> voice Apr 21 12:01:41 WARNING[3047443]: Unable to forward frame Apr 21
> 12:02:21 WARNING[3112979]: Unable to forward voice Apr 21 12:03:27
> WARNING[3145747]: Unable to forward voice Apr 21 12:07:49 WARNING[3325970]:
> Unable to forward frame Apr 21 12:13:49 WARNING[3506198]: Unable to forward
> frame Apr 21 12:18:32 WARNING[3686422]: Unable to forward frame Apr 21
> 12:27:03 WARNING[3768339]: Unable to forward frame Apr 21 12:29:35
> WARNING[3899413]: Unable to forward frame Apr 21 12:29:40 WARNING[3932181]:
> Unable to forward voice Apr 21 12:43:15 WARNING[4177942]: Unable to forward
> voice Apr 21 12:45:21 WARNING[4194322]: Unable to forward frame Apr 21
> 12:46:34 WARNING[4227090]: Unable to forward frame Apr 21 12:47:24
> WARNING[4243474]: Unable to forward frame Apr 21 13:05:48 WARNING[4653074]:
> Unable to forward frame Apr 21 13:06:20 WARNING[4685843]: Unable to forward
> frame Apr 21 13:21:57 WARNING[5062678]: Unable to forward frame Apr 21
> 13:36:04 WARNING[5390360]: Unable to forward frame Apr 21 13:38:55
> WARNING[5521428]: Unable to forward frame Apr 21 13:42:15 WARNING[5783576]:
> Unable to forward frame
> -
> Apr 20 17:42:45 WARNING[163851]: PRI: !! Got reject for frame 112,
> retransmitting frame 11
> 2 now, updating n_r!
> Apr 20 17:42:45 WARNING[163851]: PRI: !! Got reject for frame 112,
> retransmitting frame 11
> 3 now, updating n_r!
> Apr 20 18:38:48 WARNING[40583199]: Unable to forward frame Apr 20 18:39:02
> WARNING[163851]: PRI: !! Got reject for frame 44, retransmitting frame 44
> now, updating n_r!
> Apr 20 18:39:02 WARNING[163851]: PRI: !! Got reject for frame 44,
> retransmitting frame 45 now, updating n_r!
> Apr 20 18:39:40 WARNING[40812585]: Unable to forward voice Apr 20 18:40:08
> WARNING[40878111]: Unable to forward frame Apr 20 18:41:26
> WARNING[41025576]: Unable to forward voice Apr 20 18:41:30
> WARNING[41091112]: Unable to forward frame Apr 20 18:41:55 WARNING[147466]:
> PRI: !! Got reject for frame 76, retransmitting frame 76 now, updating n_r!
> Apr 20 18:41:55 WARNING[147466]: PRI: !! Got reject for frame 76,
> retransmitting frame 77 now, updating n_r!
> --
>
> On Wednesda

RE: [Asterisk-Users] TE410P zaptel Driver Situation

2004-04-21 Thread Scott Stingel
Dimitri-
I'm not sure about the message "Unable to forward voice" - I don't get that
one on my systems.

The frame "reject" messages are the same ones I was talking about - these
are load related, I'm pretty sure.

Regards, 


Scott M. Stingel
President,
Emerging Voice Technology, Inc.
Palo Alto California & London England
www.evtmedia.com 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of reseaux
Sent: Wednesday, April 21, 2004 9:48 AM
To: [EMAIL PROTECTED]
Subject: Re: [Asterisk-Users] TE410P zaptel Driver Situation

Dear Scott
i have notice the same type of warning plus another with my TE410P
with not very high load 30 IN/OUT line, i use only two span in this moment.
What is only warning? or not?
Thanks in advance
Dimitri

Apr 21 10:27:35 WARNING[966674]: Unable to forward voice Apr 21 10:28:41
WARNING[999442]: Unable to forward frame Apr 21 10:30:11 WARNING[1048594]:
Unable to forward frame Apr 21 10:32:02 WARNING[1130515]: Unable to forward
frame Apr 21 10:34:56 WARNING[1212434]: Unable to forward frame Apr 21
10:35:45 WARNING[1245202]: Unable to forward frame Apr 21 10:36:34
WARNING[1277970]: Unable to forward frame Apr 21 10:37:02 WARNING[1294354]:
Unable to forward frame Apr 21 10:40:03 WARNING[1359891]: Unable to forward
frame Apr 21 10:45:51 WARNING[1441811]: Unable to forward frame Apr 21
10:47:15 WARNING[1474579]: Unable to forward frame Apr 21 10:47:21
WARNING[1490963]: Unable to forward frame Apr 21 10:49:57 WARNING[1540115]:
Unable to forward frame Apr 21 10:50:26 WARNING[1572883]: Unable to forward
frame Apr 21 10:51:25 WARNING[1622035]: Unable to forward voice Apr 21
11:11:42 WARNING[1851410]: Unable to forward frame Apr 21 11:19:20
WARNING[2097170]: Unable to forward frame Apr 21 11:29:17 WARNING[2228243]:
Unable to forward voice Apr 21 11:31:39 WARNING[2375700]: Unable to forward
frame Apr 21 11:45:30 WARNING[2588692]: Unable to forward frame Apr 21
11:53:00 WARNING[2686995]: Unable to forward frame Apr 21 11:56:14
WARNING[2752531]: Unable to forward frame Apr 21 11:58:31 WARNING[2850837]:
Unable to forward voice Apr 21 11:59:13 WARNING[2867219]: Unable to forward
voice Apr 21 12:01:41 WARNING[3047443]: Unable to forward frame Apr 21
12:02:21 WARNING[3112979]: Unable to forward voice Apr 21 12:03:27
WARNING[3145747]: Unable to forward voice Apr 21 12:07:49 WARNING[3325970]:
Unable to forward frame Apr 21 12:13:49 WARNING[3506198]: Unable to forward
frame Apr 21 12:18:32 WARNING[3686422]: Unable to forward frame Apr 21
12:27:03 WARNING[3768339]: Unable to forward frame Apr 21 12:29:35
WARNING[3899413]: Unable to forward frame Apr 21 12:29:40 WARNING[3932181]:
Unable to forward voice Apr 21 12:43:15 WARNING[4177942]: Unable to forward
voice Apr 21 12:45:21 WARNING[4194322]: Unable to forward frame Apr 21
12:46:34 WARNING[4227090]: Unable to forward frame Apr 21 12:47:24
WARNING[4243474]: Unable to forward frame Apr 21 13:05:48 WARNING[4653074]:
Unable to forward frame Apr 21 13:06:20 WARNING[4685843]: Unable to forward
frame Apr 21 13:21:57 WARNING[5062678]: Unable to forward frame Apr 21
13:36:04 WARNING[5390360]: Unable to forward frame Apr 21 13:38:55
WARNING[5521428]: Unable to forward frame Apr 21 13:42:15 WARNING[5783576]:
Unable to forward frame
-
Apr 20 17:42:45 WARNING[163851]: PRI: !! Got reject for frame 112,
retransmitting frame 11
2 now, updating n_r!
Apr 20 17:42:45 WARNING[163851]: PRI: !! Got reject for frame 112,
retransmitting frame 11
3 now, updating n_r!
Apr 20 18:38:48 WARNING[40583199]: Unable to forward frame Apr 20 18:39:02
WARNING[163851]: PRI: !! Got reject for frame 44, retransmitting frame 44
now, updating n_r!
Apr 20 18:39:02 WARNING[163851]: PRI: !! Got reject for frame 44,
retransmitting frame 45 now, updating n_r!
Apr 20 18:39:40 WARNING[40812585]: Unable to forward voice Apr 20 18:40:08
WARNING[40878111]: Unable to forward frame Apr 20 18:41:26
WARNING[41025576]: Unable to forward voice Apr 20 18:41:30
WARNING[41091112]: Unable to forward frame Apr 20 18:41:55 WARNING[147466]:
PRI: !! Got reject for frame 76, retransmitting frame 76 now, updating n_r!
Apr 20 18:41:55 WARNING[147466]: PRI: !! Got reject for frame 76,
retransmitting frame 77 now, updating n_r!
--

On Wednesday 21 April 2004 04:40 pm, Scott Stingel wrote:
> 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 ca

Re: [Asterisk-Users] TE410P zaptel Driver Situation

2004-04-21 Thread reseaux
aused by heavy load.
>
> Regards
> Scott
>
>
> Scott M. Stingel
> President,
> Emerging Voice Technology, Inc.
> Palo Alto California & London England
> www.evtmedia.com
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Darren
> Nickerson Sent: Wednesday, April 21, 2004 6:10 AM
> To: [EMAIL PROTECTED]
> 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[-132995

RE: [Asterisk-Users] TE410P zaptel Driver Situation

2004-04-21 Thread Scott Stingel
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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darren Nickerson
Sent: Wednesday, April 21, 2004 6:10 AM
To: [EMAIL PROTECTED]
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,
retrans

Re: [Asterisk-Users] TE410P zaptel Driver Situation

2004-04-21 Thread Darren Nickerson
]: 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" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
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: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of reseaux
> Sent: Tuesday, April 20, 2004 12:38 PM
> To: [EMAIL PROTECTED]
> 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
> [EMAIL PROTECTED]
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>
> ___

Re: [Asterisk-Users] TE410P zaptel Driver Situation

2004-04-20 Thread reseaux
Dear Scott
i notice also this warning but seems no problem... :-) This type of message 
happen when a call is hangup by the caller when the dial try to call the 
remote phone.
Thanks
Dimitri
--
Apr 20 17:24:41 WARNING[31883293]: Unable to forward frame
Apr 20 17:24:54 WARNING[31850523]: Unable to forward voice
Apr 20 17:24:58 WARNING[31932443]: Unable to forward voice
Apr 20 17:25:00 WARNING[31801365]: Unable to forward frame
Apr 20 17:25:20 WARNING[31948821]: Unable to forward frame
Apr 20 17:25:23 WARNING[31916057]: Unable to forward frame
Apr 20 17:25:35 WARNING[31965204]: Unable to forward voice
Apr 20 17:26:07 WARNING[32096280]: Unable to forward frame
Apr 20 17:26:22 WARNING[32112664]: Unable to forward frame
Apr 20 17:27:11 WARNING[32145432]: Unable to forward frame
Apr 20 17:27:21 WARNING[32227353]: Unable to forward frame
Apr 20 17:27:34 WARNING[32260125]: Unable to forward frame
Apr 20 17:27:56 WARNING[32342045]: Unable to forward frame
Apr 20 17:28:29 WARNING[32374808]: Unable to forward voice
Apr 20 17:29:00 WARNING[147466]: PRI: !! Got reject for frame 127, 
retransmitting frame 12
7 now, updating n_r!
Apr 20 17:29:00 WARNING[147466]: PRI: !! Got reject for frame 127, 
retransmitting frame 0
now, updating n_r!
Apr 20 17:29:00 WARNING[32440341]: Unable to forward frame
Apr 20 17:29:42 WARNING[32505872]: Unable to forward frame
-
On Tuesday 20 April 2004 10:14 pm, Scott Stingel wrote:
> 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: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of reseaux
> Sent: Tuesday, April 20, 2004 12:38 PM
> To: [EMAIL PROTECTED]
> 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
> [EMAIL PROTECTED]
> 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
> [EMAIL PROTECTED]
> 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
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


RE: [Asterisk-Users] TE410P zaptel Driver Situation

2004-04-20 Thread Scott Stingel
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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of reseaux
Sent: Tuesday, April 20, 2004 12:38 PM
To: [EMAIL PROTECTED]
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
[EMAIL PROTECTED]
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
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[Asterisk-Users] TE410P zaptel Driver Situation

2004-04-20 Thread reseaux
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
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users