<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 14/05/2020 16:41, Joshua C. Colp
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAM0A2Z2bTRpx+MWP=dj3PtfP0X4XxhhveNYSBy_iD27ECSuhdA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Thu, May 14, 2020 at 11:31 AM John Hughes <<a
href="mailto:john@calva.com" moz-do-not-send="true">john@calva.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<div>On 14/05/2020 08:10, John Hughes wrote:<br>
</div>
<blockquote type="cite">
<p>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?</p>
<p>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.<br>
</p>
</blockquote>
And in fact that is exactly what's happening.
<p>And when I look at the RTP debugging I see the data
from the remote is:<br>
</p>
<pre><blockquote type="cite">Got RTP packet from xx.xx.xx.xx:50644 (type 18, seq 001338, ts 610458, len 000020)
</blockquote></pre>
<p>AAArgh! Type 18 is g729. Why on earth is the remote
sending me g729 when I clearly said the only thing I
could do was alaw.</p>
<p>Is this legal?</p>
<p>Is the other side broken?</p>
</div>
</blockquote>
<div><br>
</div>
<div>It shouldn't be sending it, but as well we should be
ignoring it. I believe we do ignore in modern versions, I
can't speak for your old one. As for why... I don't really
have an answer.</div>
</div>
</div>
</blockquote>
<p>Ok, so maybe upgrading my asterisk would be a good idea, but I
don't think it'll fix this problem, they sent me 6 g729 packets
before the communication was cut, I'm pretty sure they've just
ignored the results of the negotiation.</p>
<p>I hope I can get them to fix their system...<br>
</p>
</body>
</html>