Summary:ASTERISK-02143: Zap channel permanantly in conference after transferring to meetme
Reporter:jonh (jonh)Labels:
Date Opened:2004-07-29 17:13:47Date Closed:2008-01-15 15:04:00.000-0600
Versions:Frequency of
Description:After using 3-way calling to transfer another channel into a meetme  room, the zap channel doing the transfer is from then on thought to be in a conference. Stopping and restarting asterisk is the only way to clear this situation.
The transferred person hears whatever the transferrer does after that - dial tone, dialing, conversations, etc...
Also after this the transferrer can't flash - monitor shows message "Avoiding 3-way call when in an external conference".

Steps to replicate:
My extension is Zap/2
Answer call from Zap/1
Dialtone, Dial 502 (MeetMe Room)
get recording (You are the only.....)
Hangup Zap/2 to transfer Zap/1 to meetme
Zap/2 is now flagged as in a conference that it can't leave.


Using cvs head updated Jul 29 14:58

"zap show channel 2" after hanging up, note Actual Confinfo

Channel: 2
File Descriptor: 19
Span: 1
Dialing: no
Context: internal-pots
Caller ID string:
Destroy: 0
Signalling Type: FXO Kewlstart
Owner: <None>
Real: <None>
Callwait: <None>
Threeway: <None>
Confno: -1
Propagated Conference: -1
Real in conference: 0
DSP: no
Relax DTMF: no
Dialing/CallwaitCAS: 0/0
Default law: ulaw
Fax Handled: no
Pulse phone: no
Echo Cancellation: 0 taps unless TDM bridged, currently OFF
Actual Confinfo: Num/1023, Mode/0x0304
Actual Confmute: No
Actual Hookstate: Onhook
Comments:By: Mark Spencer (markster) 2004-07-29 18:57:24

Can you find me on IRC please (kram, irc.freenode.net, #asterisk)

By: Mark Spencer (markster) 2004-07-30 16:37:03

Fixed in CVS.

By: Digium Subversion (svnbot) 2008-01-15 15:04:00.000-0600

Repository: asterisk
Revision: 3544

U   trunk/channels/chan_zap.c

r3544 | markster | 2008-01-15 15:03:59 -0600 (Tue, 15 Jan 2008) | 2 lines

Reset conferencing on final hangup (bug ASTERISK-2143)