[asterisk-bugs] [Asterisk 0016514]: Asterisk causes crosstalk between inbound and random channels

[Asterisk Bug Tracker]

The following issue has been set as RELATED TO issue 0016549. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16514 
====================================================================== 
Reported By:                jmthomas
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16514
Category:                   Channels/chan_zap
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           Older 1.4 - please test a newer version 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-12-24 15:08 CST
Last Modified:              2010-01-06 08:42 CST
====================================================================== 
Summary:                    Asterisk causes crosstalk between inbound and random
channels
Description: 
This issue occurs approximately every 2 weeks.  A reboot of Asterisk seems
to resolve the issue for another 10-14 days.  There are no other related
errors, warnings or failures in the Asterisk logs.  ZTTOOL indicates no
alarms or issues with the PRI.  All vendors involved have checked line
attenuation to our demarcation point - passed without error.

When the following appears in the full log - the audio from this inbound
caller is broadcast to random channels: 

<snip>
chan_zap.c: Ring requested on channel 0/4 already in use or previously
requested on span 1.  Attempting to renegotiating channel.
</snip>

In the above example, this inbound caller was then negotiated to channel
0/5.  His/her audio was then broadcast to everyone in an ongoing
meetme-conference.  
Periodic automatic Zap clearing is set to 1800 seconds.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0016549 Conference Calls
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-06 08:42 lmadsen        Relationship added       related to 0016549  
======================================================================