search for: aceinnovative

Hello, Anyone? I have hard time to believe this is not possible with chan_pjsip. Anyway, may I ask how people handle the following scenario which I imagine should be quite common: - I have internal extensions talk to each other using g722. so their codec setting (with chan_sip now) is "allow=g722,ulaw" - I have carriers trunks that handle ulaw only (allow=ulaw) - calls between

On Thu, Jul 6, 2023 at 1:43 PM Michael Ulitskiy <mulitskiy at acedsl.com> wrote: > Hello, > > After I have re-read the "PJSIP Advanced Codec negotiation" document, it > occurred to me that the desired behavior should actually happen > automatically, just due to the codec negotiation logic, but it looks like > asterisk doesn't actually follow the described

...at least not for me. :-( Having it clearly stated on the document would save me (and probably others) lots of time. Thanks for clarifying it. Any idea on the timeframe of implementation? *Michael Ulitskiy* Ace Innovative Networks, Inc. Main/SMS: 212-868-2366 Direct/SMS: 212-812-1203 https://www.aceinnovative.com On 7/6/23 12:47, Joshua C. Colp wrote: > On Thu, Jul 6, 2023 at 1:43 PM Michael Ulitskiy <mulitskiy at acedsl.com> > wrote: > > Hello, > > After I have re-read the "PJSIP Advanced Codec negotiation" > document, it occurred to me that the desired...

...otiation in the above scenario should be ulaw in both call legs, thus avoiding transcoding, but actual asterisk behavior differs. Am I missing something. What are your thoughts? Thanks, *Michael Ulitskiy* Ace Innovative Networks, Inc. Main/SMS: 212-868-2366 Direct/SMS: 212-812-1203 https://www.aceinnovative.com On 7/5/23 11:58, Michael Ulitskiy wrote: > > Hello, > > Anyone? I have hard time to believe this is not possible with chan_pjsip. > > Anyway, may I ask how people handle the following scenario which I > imagine should be quite common: > > - I have internal extensions...