[asterisk-bugs] [LibPRI 0012595]: Asterisk stops accepting calls from Zap and responds with fast busy

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12595 
====================================================================== 
Reported By:                dawebber
Assigned To:                
====================================================================== 
Project:                    LibPRI
Issue ID:                   12595
Category:                   Channels/chan_zap
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-05-06 14:49 CDT
Last Modified:              2008-12-08 09:18 CST
====================================================================== 
Summary:                    Asterisk stops accepting calls from Zap and responds
with fast busy
Description: 
This issue occurs approximately every 2 weeks on a slightly loaded box
(average 6 simultaneous incoming calls 24/7), but the issue once occurs on
a channel, will reoccur at any time, even with one incoming call. This box
doesn't place any outgoing calls. Periodic automatic Zap channel clearing
is set to 1800 seconds. The error in the asterisk logs looks like this:

<snip>
[May  5 09:17:45] DEBUG[17999] chan_zap.c: Ring requested on channel 0/1
already in use or previously requested on span 1.  Attempting to
renegotiating channel.
[May  5 09:17:45] DEBUG[17999] chan_zap.c: Ring requested on channel 0/1
already in use or previously requested on span 1.  Attempting to
renegotiating channel.
<snip>


The errors always occur in pairs as shown above. This error is similar to
the one described here:
http://www.trixbox.org/forums/trixbox-forums/help/inbound-calls-over-pri-get-fast-busy

I've also noticed that the error always occurs on channel 1 of the span.
After the error had occured several times, the calls might still go through
on the channel.

Eventually, the asterisk process will crash and restarting Asterisk takes
care of the issue. the snippet of log data above occured right before
crash.

Memory consumption and CPU level stay relatively low. No IRQ conflicts
with Digium Card are detected.


====================================================================== 

---------------------------------------------------------------------- 
 (0095946) dawebber (reporter) - 2008-12-08 09:18
 http://bugs.digium.com/view.php?id=12595#c95946 
---------------------------------------------------------------------- 
No, I'm actually on a TimeWarner PRI.
Actually, the issue seems to have gone away after a series of upgrades to
1.4.21.
I also changed my CDR config from using csv to Postgres. It seems that the
locks were due to bugs within Asterisk itself that were squashed around
1.4.20 as well as the fact that if the CDR routines don't complete in time,
a similar condition will exist. So, frankly not sure which of the two was
to blame, but hopefully this entry will help someone with their similar
issues.
Otherwise, we can go ahead and close this one. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-08 09:18 dawebber       Note Added: 0095946                          
======================================================================