[asterisk-bugs] [LibPRI 0012595]: Asterisk stops accepting calls from Zap and responds with fast busy
noreply at bugs.digium.com
noreply at bugs.digium.com
Sat Jul 19 11:04:09 CDT 2008
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: new
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: 05-06-2008 14:49 CDT
Last Modified: 07-19-2008 11:04 CDT
======================================================================
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.
======================================================================
----------------------------------------------------------------------
cripito - 07-19-08 11:04
----------------------------------------------------------------------
Just to let you guys know..
We had this issue for long time in a couple of customers. Verizon t1.
Looks like a common denominator. after a lot of fights they agree to do a
extended review in the t after that no more problems.. We are using 1.4.11
now without a single issue. Yes there is also an issue with the lock of the
channel but what trigger it is a condition coming from Verizon
Issue History
Date Modified Username Field Change
======================================================================
07-19-08 11:04 cripito Note Added: 0090486
======================================================================
More information about the asterisk-bugs
mailing list