asterisk users - Nov 2019 - Avoid transcoding if both ends support same coded

Hi Gang

I offer:

g722
g711a

g711a is mandatory. g722 is becoming more and more popular.

Now if a call originates from a device which support g722 and ends on a
device which does not. I see that asterisk is transcoding between g722
and g711a despite both ends supporting g711a.

Google tells me, that in this scenario asterisk should have selected
g711a as this is the codec common for both sides.

So why is my asterisk instance choosing to transcode instead of trying
to natively and even remotely bridge the calls?

I have nothing in the dial plan which would force asterisk to listen to
the audio and I have set direct_media=yes on both endpoints.

Mit freundlichen Grüssen

-Benoît Panizzon-
-- 
I m p r o W a r e   A G    -    Leiter Commerce Kunden
______________________________________________________

Zurlindenstrasse 29             Tel  +41 61 826 93 00
CH-4133 Pratteln                Fax  +41 61 826 93 01
Schweiz                         Web  http://www.imp.ch
______________________________________________________

On Tue, Nov 26, 2019 at 12:11 PM Benoit Panizzon <benoit.panizzon at
imp.ch>
wrote:
> Hi Gang
>
> I offer:
>
> g722
> g711a
>
> g711a is mandatory. g722 is becoming more and more popular.
>
> Now if a call originates from a device which support g722 and ends on a
> device which does not. I see that asterisk is transcoding between g722
> and g711a despite both ends supporting g711a.
>
> Google tells me, that in this scenario asterisk should have selected
> g711a as this is the codec common for both sides.
>
> So why is my asterisk instance choosing to transcode instead of trying
> to natively and even remotely bridge the calls?
>
> I have nothing in the dial plan which would force asterisk to listen to
> the audio and I have set direct_media=yes on both endpoints.
>
Each call leg is independently negotiated, from Asterisk to the device.
This can yield results such as what you are seeing. There have been
requests to improve this, but noone has taken that on as a project because
it's not as easy as one would initially think (you have to define
configuration options to define behavior in scenarios, go through
everything making it aware, etc).

-- 
Joshua C. Colp
Senior Software Developer
Sangoma Technologies
Check us out at www.sangoma.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20191127/cf903500/attachment.html>