[asterisk-users] I can do alaw, ulaw and gsm; remote can do g729 and alaw; asterisk wants to translate g729 -> alaw. WHY?

[Michael L. Young]

> From: "John Hughes" <john at calva.com>
> To: "Asterisk Users Mailing List, Non-Commercial Discussion"
> <asterisk-users at lists.digium.com>
> Sent: Thursday, May 14, 2020 2:10:45 AM
> Subject: [asterisk-users] I can do alaw, ulaw and gsm; remote can do g729 and
> alaw; asterisk wants to translate g729 -> alaw. WHY?

> I am having a problem with one of my callers who is using either g729 or alaw. I
> can do alaw but not g729 so asterisk should negotiate alaw right? In fact from
> the sip debug it looks like it does, but then I get the dreaded "channel.c:5630
> set_format: Unable to find a codec translation path: (g729) -> (alaw)" and the
> call hangs up. Why?

> Last minute thought: Is it possible that the caller is sending g729 in RTP even
> though the SIP negotiation clearly chooses alaw? Maybe I need some RTP
> debugging.

> Asterisk 13.14.1 on Debian, using chan_sip.
Hi John, 

Maybe a newer version of Asterisk would help? The latest release for 13 is version 13.33. The version you are on was released 3 years ago. 

Here is an issue which looks like what you describe and was fixed in 13.16 
[ https://issues.asterisk.org/jira/browse/ASTERISK-26143 | https://issues.asterisk.org/jira/browse/ASTERISK-26143 ] 

Not sure if this is the answer to your problem but thought that I would throw that out there. 

Michael L. Young 

(elguero) 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20200514/0089aafe/attachment.html>