[Asterisk-Users] zt_rec: Unknown error 500

[Michiel Betel]

My Zap channels having the problems are on a T1 connected to a CAC 
channelbank, But it looks like the zt_rec in chan_zap error uses the 
lowlevel zaptel ioctl's which are the same for T1 & PRI...

Scott Stingel wrote:

>Hi Michiel-
>
>This may be related to a PRI frame buffer overflow problem that I get in
>high-volume IVR applications.  I get a lot of these errors mixed in with
>frame errors.   In my case its load related.  Mark and Martin at Digium have
>said they'll be looking into improving the buffering mechanism.
>  
>
>>-----Original Message-----
>>From: asterisk-users-admin at lists.digium.com 
>>[mailto:asterisk-users-admin at lists.digium.com] On Behalf Of 
>>Michiel Betel
>>Sent: Tuesday, November 25, 2003 1:43 PM
>>To: asterisk-users at lists.digium.com
>>Subject: [Asterisk-Users] zt_rec: Unknown error 500
>>
>>
>>I have a number of Zap/ extensions defined in a queue with ringall 
>>strategy. When this queue is called sometimes Asterisk seems to think 
>>that one of these channels is busy, while it is NOT. The following is 
>>shown on the console:
>>     --Called 44
>>    -- Called 36
>>    -- Called 41
>>    -- Called 35
>>    -- Called 38
>>    -- Zap/44-1 is ringing
>>    -- Zap/36-1 is ringing
>>    -- Zap/41-1 is ringing
>>    -- Zap/35-1 is ringing
>>    -- Zap/38-2 is ringing
>>    -- Zap/44-1 is ringing
>>    -- Zap/36-1 is ringing
>>    -- Hungup 'Zap/35-1'
>>    -- Zap/41-1 is ringing
>>    -- Zap/44-1 is ringing
>>    -- Zap/36-1 is ringing
>>While a
>>WARNING[165916]: File chan_zap.c, Line 3331 (zt_read): 
>>zt_rec: Unknown 
>>error 500
>>is generated in /var/log/asterisk/messages
>>Any ideas on how to fix this?? Thanks!
>>
>>Michiel
>>
>>    
>>
>