Summary:ASTERISK-21944: Bridge API Enhancements - implement IAX2 native bridging (again)
Reporter:Matt Jordan (mjordan)Labels:Asterisk12
Date Opened:2013-06-21 11:51:51Date Closed:
Status:Open/NewComponents:Channels/chan_iax2 Core/Bridging
Versions:Frequency of
Description:When Asterisk moved to the new bridging architecture, things that natively bridged became ... no longer natively bridging. In order to restore native bridge capabilities, channel drivers must provide (or have provided for them) a bridging technology that can perform the native bridging tasks.

This was already taken care of for RTP capable channel drivers, and will be taken care of for DAHDI. IAX2 is another channel driver that has its own native bridging capabilities.

With IAX2 native bridging, media is directed out of the signalling path, similar to RTP "directmedia" options in {{chan_sip}} and elsewhere. This requires a bridging 'module' to be registered with the bridging core to handle this.

Since adding this as a separate module would require (a) module dependency nightmares and (b) exporting of public functions from {{chan_iax2}} (ew), {{chan_iax2}} should instead implement a bridging 'module' internally in its own file. The loading of the {{chan_iax2}} module should cause it to register a bridging module with the bridging core.
Comments:By: Richard Mudgett (rmudgett) 2013-08-14 18:15:39.669-0500

Be sure to remove the todo comment at the top of chan_iax2.c.

By: Richard Mudgett (rmudgett) 2013-09-24 15:01:40.941-0500

Native bridging allows chan_iax2 to try eliminating a tromboned call by transferring it to the peer.

By: Xiaofan Lee (Xiaofan) 2018-09-08 08:48:05.603-0500

Yes, is there some patch for this? I noticed the newer version than11(from 12), the IAX2's TXREQ/TXREL cmd have not used.  But if you want transfer, the setup start from asterisk's chan_iax2. Is there some news about this question?

By: Richard Mudgett (rmudgett) 2018-09-08 09:12:28.009-0500

There is no patch.  I'm not aware of anyone working on this.