[asterisk-bugs] [JIRA] (ASTERISK-27250) asymmetric_rtp_codec=no does not seem to be working anymore with Asterisk 13.17.1

[Richard Mudgett (JIRA)]

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

Richard Mudgett edited comment on ASTERISK-27250 at 9/5/17 11:01 AM:
---------------------------------------------------------------------

Just had time to check: it's not a regression caused by ASTERISK-27013, but it happened somewhere between 13.16 and 13.17 just tested the same scenario with the same devices with:

Asterisk 13.16: OK
Asterisk 13.17: not ok
Asterisk 13.17.1: not ok


was (Author: nappsoft):
Just had time to check: it's not a regression caused by ASTERISK -27013, but it happened somewhere between 13.16 and 13.17 just tested the same scenario with the same devices with:

Asterisk 13.16: OK
Asterisk 13.17: not ok
Asterisk 13.17.1: not ok

> asymmetric_rtp_codec=no does not seem to be working anymore with Asterisk 13.17.1
> ---------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27250
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27250
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.17.1
>            Reporter: nappsoft
>            Assignee: Unassigned
>            Severity: Minor
>
> Description: We had one-way audio on some systems after upgrading to Asterisk 13.17.1 from Asterisk 13.15 or Asterisk 13.16. The traces showed that the Snom700 device was sending G711u while Asterisk was sending G711a (both codecs were offered in the SDP of both sides). Asterisk didn't switch to G711u during the whole conversation.
> Expectation: we'd expect Asterisk to switch to G711u after receiving G711u packets from the other end.
> Conclusion: It seems like Asterisk 13.17.1 would not switch the codec anymore to make the rtp codec symmetric when rtp is running through Asterisk. (Maybe this could be related to change made in ASTERISK-27013? didn't have time to look into the code, but received a SIP trace by mail that is showing the described behavior that was reported to be reproducible)



--
This message was sent by Atlassian JIRA
(v6.2#6252)