Re: [asterisk-dev] Asterisk 18 Planning: Codec Negotiation

2020-02-03 Thread Kevin Harwell
On Fri, Jan 31, 2020 at 1:06 AM Michael Maier wrote: > On 30.01.20 at 23:20 Kevin Harwell wrote: > ... > > No worries it's my bad. I can see how what I wrote was ambiguous. What I > > meant was "if *either* remote *or* local is chosen". As in it doesn't > > matter which option value you choose.

Re: [asterisk-dev] Asterisk 18 Planning: Codec Negotiation

2020-01-30 Thread Michael Maier
On 30.01.20 at 23:20 Kevin Harwell wrote: > On Thu, Jan 30, 2020 at 3:01 PM Michael Maier wrote: > >> . 2. outgoing_sdp_send_prefs The list can be created on base of the callees allow line and list 1 (option local ...). Or: The list can be

Re: [asterisk-dev] Asterisk 18 Planning: Codec Negotiation

2020-01-30 Thread Kevin Harwell
On Thu, Jan 30, 2020 at 3:01 PM Michael Maier wrote: > . > >> 2. outgoing_sdp_send_prefs > >>The list can be created on base of the callees > >>allow line and list 1 (option local ...). > >> > >>Or: > >> > >>The list can be created on base of list 1 > >>(option remote

Re: [asterisk-dev] Asterisk 18 Planning: Codec Negotiation

2020-01-30 Thread Michael Maier
Hello Kevin, thanks for your clarification. Anyway, I think I don't understand it completely right now. Please see question below. Thanks Michael On 30.01.20 at 16:49 Kevin Harwell wrote: > On Thu, Jan 30, 2020 at 4:55 AM Michael Maier wrote: > >> >> >> Could the planned codec handling

Re: [asterisk-dev] Asterisk 18 Planning: Codec Negotiation

2020-01-30 Thread Kevin Harwell
On Thu, Jan 30, 2020 at 4:55 AM Michael Maier wrote: > > > Could the planned codec handling globally described like this: > > Overall I think you have the gist of it. See below, though, for a couple of clarifications. > > The codec handling is based on 4 lists. > > 1.

Re: [asterisk-dev] Asterisk 18 Planning: Codec Negotiation

2020-01-30 Thread Michael Maier
On 29.01.20 at 22:44 Kevin Harwell wrote: > Ugh I used the wrong keyboard shortcuts and the message sent before I was > done. Below is the rest :-) > > On Wed, Jan 29, 2020 at 3:42 PM Kevin Harwell wrote: > >> On Wed, Jan 29, 2020 at 3:12 PM Michael Maier >> wrote: >> >>> >>> >> >>> >>>

Re: [asterisk-dev] Asterisk 18 Planning: Codec Negotiation

2020-01-29 Thread Kevin Harwell
Ugh I used the wrong keyboard shortcuts and the message sent before I was done. Below is the rest :-) On Wed, Jan 29, 2020 at 3:42 PM Kevin Harwell wrote: > On Wed, Jan 29, 2020 at 3:12 PM Michael Maier > wrote: > >> >> > >> >> >> From my point of view, it should always be possible to

Re: [asterisk-dev] Asterisk 18 Planning: Codec Negotiation

2020-01-29 Thread Joshua C. Colp
On Wed, Jan 29, 2020 at 5:12 PM Michael Maier wrote: > Hello Kevin, > > On 29.01.20 at 20:22 Kevin Harwell wrote: > > Greetings! > > > > Over the years there have been numerous requests to improve the codec > > negotiation process in Asterisk. Specifically, regarding what codecs are > > offered,

Re: [asterisk-dev] Asterisk 18 Planning: Codec Negotiation

2020-01-29 Thread Kevin Harwell
On Wed, Jan 29, 2020 at 3:12 PM Michael Maier wrote: > > > Will Asterisk 18 be a LTS version? > I'll defer the answer to that question to others :-) > > > From my point of view, it should always be possible to prevent > transcoding as long as there is one codec which can be used on

Re: [asterisk-dev] Asterisk 18 Planning: Codec Negotiation

2020-01-29 Thread Michael Maier
Hello Kevin, On 29.01.20 at 20:22 Kevin Harwell wrote: > Greetings! > > Over the years there have been numerous requests to improve the codec > negotiation process in Asterisk. Specifically, regarding what codecs are > offered, in what order, how Asterisk chooses which codec(s) to use, and of >

[asterisk-dev] Asterisk 18 Planning: Codec Negotiation

2020-01-29 Thread Kevin Harwell
Greetings! Over the years there have been numerous requests to improve the codec negotiation process in Asterisk. Specifically, regarding what codecs are offered, in what order, how Asterisk chooses which codec(s) to use, and of course how transcoding is affected by that. Well hopefully that