[asterisk-bugs] [JIRA] (ASTERISK-21863) RTP Native Bridge Codec Change Handling - Appears to compare immediately after setting equal

[David Woolley (JIRA)]

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

David Woolley commented on ASTERISK-21863:
------------------------------------------

Joshua Colp's response on the asterisk-dev:

I *think* you are correct and I believe this stems from the UPDATE_RTP_PEER frame. It is used to indicate explicitly that the remote peer has changed. Removing the code that you mention I think should do it... although I think this really shows another issue which is, the code doesn't handle codecs changing to a non-joint situation so a joint check should also probably be added in.
                
> RTP Native Bridge Codec Change Handling - Appears to compare immediately after setting equal
> --------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21863
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21863
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/RTP
>    Affects Versions: 11.4.0
>            Reporter: David Woolley
>            Severity: Minor
>         Attachments: more_complete_analysys_and_code_extract.txt
>
>
> ast_bridge_result remote_bridge_loop sets the old codec capabilities equal to the current ones immediately before testing whether they differ on the next iteration of the loop, thus meaning it will fail to act on many changes.

--
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