[asterisk-bugs] [JIRA] (ASTERISK-21944) Bridge API Enhancements - implement IAX2 native bridging (again)

[Richard Mudgett (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209150#comment-209150 ] 

Richard Mudgett commented on ASTERISK-21944:
--------------------------------------------

Be sure to remove the todo comment at the top of chan_iax2.c.
                
> Bridge API Enhancements - implement IAX2 native bridging (again)
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-21944
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21944
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Channels/chan_iax2, Core/Bridging
>            Reporter: Matt Jordan
>              Labels: Asterisk12
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira