[asterisk-dev] Advanced Codec Negotiation: Asymmetric Codecs

[Joshua Elson]

So I am the one responsible for this situation, if I recall the discussion
a few years back. We actually have had to support several phones - Yealink
being the most distinctly memorable - that support asymmetric codecs on a
single call leg, and from our reading, it's legal in the RFC. In some very
high throughput cases, it was preferable to reduce overall transcoding use
in our infrastructure when you did the math on having a few thousand of
these phones in the same situation.

That being said, it's conceivable we could live without that option now,
and some phone vendors do still not properly implement the RFC standard
around this, but we do still run in production with asymmetric codecs on a
single call leg for a slight majority of our devices.

Josh

On Mon, Jun 15, 2020 at 10:42 AM Michael Maier <m1278468 at mailbox.org> wrote:

> Hello George,
>
> in terms of uses cases? I'm not aware of any use case which would need
> asymmetric codecs. The opposite is true: my phones can't handle asymmetric
> codecs at all - therefore it's
> forbidden.
>
> But I'm not the only one using asterisk - others may have an use case.
>
>
> On 15.06.20 at 01:56 George Joseph wrote:
> > Given the earlier discussions, under what conditions is it desirable to
> use
> > a different codec in one direction than the other on the same call leg?
>
>
> Thanks
> Michael
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20200615/c3a8bda8/attachment.html>