[asterisk-dev] Wish: adding intelligent codec negotiation to asterisk / pjsip
Joshua Colp
jcolp at digium.com
Tue Jan 31 11:32:13 CST 2017
On Tue, Jan 31, 2017, at 01:29 PM, Michael Maier wrote:
> On 01/31/2017 at 05:15 PM Joshua Colp wrote:
> > On Tue, Jan 31, 2017, at 12:01 PM, Michael Maier wrote:
>
> [...]
>
> >>> We
> >>> don't pass the information to the other side, we just adjust our formats
> >>> and transcoding.
> >>
> >> Yes. That's not necessary. But it is necessary, that asterisk is able to
> >> identify
> >> - that transcoding between two UAs is currently active.
> >> - the codec used by the peer UA stream and if this codec is allowed (by
> >> configuration) for the other UA, too. If yes: send other UA a reinvite
> >> to ensure both UAs are using the same codec as from now and switch off
> >> transcoding and all other related stuff, which isn't need any more.
> >
> > It's not currently possible to know from a configuration perspective.
> > The bridging core can know what has been currently negotiated on each
> > side only. There is no mechanism to reach across and get the
> > configuration information.
>
> I'm beginning to understand how asterisk works today and why it is not
> as easy as I thought.
> But the planned stream support for 15 fills this gap, which is necessary
> to provide a feature to prevent transcoding if a common codec between
> two legs exists.
>
> Therefore I would be happy if this feature would be provided w/ 15
> instead of adding a lot of time and effort to achieve it by special
> adjusts / expansions of the actual code.
>
Stream support will provide a lot of options for cool functionality. :)
--
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org
More information about the asterisk-dev
mailing list