[Asterisk-Dev] MOH and Zombie Transfers

[Matthew Boehm]

Posting again cause its still happening..should I post this as a bug?

-Matthew

> Someone talked about this a while back and provided a patch, but I
> can't seem to find the bug #.
> 
> 
> (Phone A calls Phone B.)
> -- Executing Dial("Zap/2-1", "SIP/3030|15") in new stack
> -- Called 3030
> -- SIP/3030-bf07 is ringing
> -- SIP/3030-bf07 answered Zap/2-1
> 
> (Phone B hits "Transfer". This places caller A on hold (hears music)).
> -- Started music on hold, class 'default', on Zap/2-1
> 
> (Phone B dials Phone C.)
> -- Executing Dial(SIP/3030-9627", "SIP/3087|15")
> -- Called 3087
> -- SIP/3087-cfce is ringing
> -- SIP/3087-cfce answered SIP/3030-9627
> 
> Phone B and Phone C talk.
> Phone B presses "Transfer" again to do the transfer.
> 
> Here is the interesting part:
> 
> Phone C "hears" MOH. But when phone C speaks, Phone A can hear his
> speech. When Phone A speaks, Phone C cannot hear it (C is hearing
> MOH). 
> 
> -- Attempting native bridge of SIP/3030-9627 and SIP/3087-cfce
> -- Started music on hold, class 'default', on SIP/3087-cfce
> -- Stopped music on hold on Zap/2-1
> 
> Why would music be started on 3087? Seems it wasn't released.
> 
> I know you guys really need a SIP debug, but I tried this same thing
> again (to get the debug) and it worked fine except this time I got
> this: 
> 
> -- Executing Dial("Zap/2-1", "SIP/3030|15") in new stack
> -- Called 3030
> -- SIP/3030-f674 is ringing
> -- SIP/3030-f674 answered Zap/2-1
> -- Called 3087
> -- SIP/3087-51e0 is ringing
> -- SIP/3087-51e0 answered SIP/3030-1ba9
> -- Attempting native bridge of SIP/3030-1ba9 and SIP/3087-51e0
> -- Started music on hold, class 'default', on SIP/3087-51e0
> -- Stopped music on hold on Zap/2-1
> -- Stopped music on hold on SIP/3087-51e0
> -- Attempting native bridge of SIP/3030-1ba9<ZOMBIE> and SIP/3030-f674
> WARNING: Can't fine native functions for channel
> 'SIP/3030-1ba9<ZOMBIE>' WARNING: Private bridge between
> SIP/3030-1ba9<ZOMBIE> and SIP/3030-f674 failed.
> 
> Any ideas? I thought this was a problem with the phone, but after
> several phones did it, I figured it can't be.
> 
> -Matthew