[asterisk-bugs] [JIRA] (ASTERISK-28671) Outbound Channel to endpoint that negotiates iLBC mode = 20 produces Warning in CLI and one way audio

[Sean Bright (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Bright updated ASTERISK-28671:
-----------------------------------

    Assignee: Unassigned  (was: Tom Cotton)
      Status: Triage  (was: Waiting for Feedback)

Confirmed with Asterisk 16 from Git with {{res_format_attr_ilbc}} loaded.

> Outbound Channel to endpoint that negotiates iLBC mode = 20 produces Warning in CLI and one way audio
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28671
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28671
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Codecs/codec_ilbc
>    Affects Versions: 16.7.0
>         Environment: Centos 7.6 on VM in datacenter
>            Reporter: Tom Cotton
>            Assignee: Unassigned
>            Severity: Minor
>         Attachments: SIP-126235.txt
>
>
> When I dial a channel with an endpoint that prefers iLBC mode 20 the SDP from asterisk offers mode 20. If the endpoint replies with ans SDP that iLBC mode 20 is accepted and sends RTP packets according to spec, then the CLI reports a warning stating "[2019-12-20 17:59:59] WARNING[2512]: codec_ilbc.c:125 ilbctolin_framein: Huh?  An ilbc frame that isn't a multiple of 50 bytes long from RTP (38)?". iLBC mode 20 packets are not in multiples of 50 rather they are 38 bytes long. So the correct packets are being sent and rejected in error by asterisk. This behavior is only present in outbound channels dialed to the the endpoint. 
> If the called endpoint replies in their SDP that they want iLBC mode 30 everything works just fine.



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