[asterisk-dev] iax2 native bridging drops transferred calls repeatably

[Kevin P. Fleming]

----- Thomas Andrews <tandrews at grok.co.za> wrote:
> It would seem to me that the code should pre-check if there is already
> a
> native bridge in place, and if so take some action. What, I don't
> know.

This should not be necessary.

Your description is slightly inaccurate, in that you undercounted the channels involved. When the two FXS phones on server A are talking to each other, there are four channels involved... two Zap, and two IAX2. In an ideal world Asterisk would drop these IAX2 channels completely since they are connected to each other, but that does not happen today.

When one of the phones starts a transfer operation to the phone on server B, there are then six channels involved: three IAX2, and three Zap (two of which are on the same phone). When the transfer operation is completed, one of the IAX2 channels from the original bridge will be pulled out via masquerading and dropped into the new bridge with the IAX2 channel going to server B. This will then cause the remaining IAX2 channel and two Zap channels from the original call to be hung up.

If this is not happening, then it's a bug, and we need a console and IAX2 debug trace on bugs.digium.com to work on it.

-- 
Kevin P. Fleming
Senior Software Engineer
Digium, Inc.