[Asterisk-Users] Threeway calling leaves outside trunks bridged

[Steve Rodgers]

I think I found another interesting 'feature' with threeway calling. If you 
hang up while on a 3 way call with both parties on outside lines, Asterisk 
ends up removing the conference initiator and leaving the outside trunks 
bridged together. Is this a good idea? This could cause congestion problems 
on small configurations with limited outgoing lines. Maybe we should add an 
option to zapata.conf which forces 3 way calls to be completely dropped when 
the initiator hangs up on a conference with 2 outside lines bridged. Note:
if one of the conference members is an internal extension, then this
case should not not apply.

Steve Rodgers
San Diego CA


   -- Starting simple switch on 'Zap/3-1'
    -- Executing Dial("Zap/3-1", "Zap/g1/9www8531212") in new stack
    -- Called g1/9www8531212
    -- Zap/1-1 answered Zap/3-1
    -- Attempting native bridge of Zap/3-1 and Zap/1-1
    -- Starting simple switch on 'Zap/3-2'
    -- Started three way call on channel 3
    -- Started music on hold, class 'default', on Zap/1-1
    -- Attempting native bridge of Zap/3-1 and Zap/1-1
    -- Executing Dial("Zap/3-2", "Zap/g1/9www2891212") in new stack
    -- Called g1/9www2891212
    -- Zap/2-1 answered Zap/3-2
    -- Attempting native bridge of Zap/3-2 and Zap/2-1
    -- Building conference on call on Zap/3-1 and Zap/3-2
    -- Stopped music on hold on Zap/1-1
    -- Attempting native bridge of Zap/3-1 and Zap/1-1
    -- Attempting native bridge of Zap/3-2 and Zap/2-1
  == Spawn extension (house-admin, 98531212, 1) exited non-zero on 'Zap/3-1'
    -- Hungup 'Zap/3-1'
    -- Hungup 'Zap/1-1<MASQ>' 
    -- Attempting native bridge of Zap/1-1 and Zap/2-1 -- Why can't we hang up 
everybody in this case?
    -- Starting simple switch on 'Zap/3-1'
    -- Hungup 'Zap/3-1'