[asterisk-bugs] [JIRA] (ASTERISK-27056) codec_opus responds with incorrect RTP Payload Type

[Jared Hull (JIRA)]

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

Jared Hull edited comment on ASTERISK-27056 at 6/14/17 11:47 AM:
-----------------------------------------------------------------

Attached our debug+verbose log, interestingly we could not reproduce this on 14.4.1 and 14.5.0

Line 10284:
rtp_engine.c: Setting tx payload type 107 based on m type on 0x7f0e02057c90


was (Author: fortytwo):
Attached our debug+verbose log, interestingly we could not reproduce this on 14.4.1

Line 10284:
rtp_engine.c: Setting tx payload type 107 based on m type on 0x7f0e02057c90

> codec_opus responds with incorrect RTP Payload Type
> ---------------------------------------------------
>
>                 Key: ASTERISK-27056
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27056
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.16.0
>         Environment: x64 CentOS
>            Reporter: Luke Escude
>            Assignee: Unassigned
>         Attachments: asterisk_opus.txt, asterisk.pcap, grandstream.pcap
>
>
> A phone call to an Opus extension works just fine (Asterisk sends an invite with 107 opus). Two-way audio and all that jazz.
> However, if the Asterisk endpoint puts the call on hold, then retrieves the call (the endpoint sends an INVITE to retrieve the call with 123 opus) Asterisk agrees to use 123 opus, however it continues to send 107 opus instead.



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