similar to: Setting codec on originating (calling) channel with chan_pjsip (SIP_CODEC_INBOUND equivalent)

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

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 logic which is likely a bug. Can you please follow with me through a simple sip call and see if I'm missing

Hello Michael, you are referring to the following behavior - did I get it correctly?: outbound broken: asterisk offers g722 / g711 to provider (callee), callee answers g711. Asterisk now transcodes between caller and callee (g722 <-> g711). inbound works: call from provider: g711 -> asterisk drops g722 and passes g711 to internal callee -> no transcoding. As far as I know,

Well, I'm trying to migrate to chan_pjsip so that I don't have to do that. It's so surprising that the issue so seemingly obvious and trivial hasn't been addressed yet that I wanted to query the collective wisdom of this list to verify my observations. Thanks for github pointer. Michael On 7/5/23 16:46, asterisk at phreaknet.org wrote: > On 7/5/2023 4:19 PM, Michael

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

Oh, that's great. It wasn't clear from that page, 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

I have been seeing errors saying the Asterisk cannot establish an RTP connection, so I did this: lsof -i -n -P | grep asterisk | wc -l 10483 but I have only Asterisk 11 has 1 open calls Asterisk 12 has 21 open calls Asterisk 14 has 19 open calls Asterisk 15 has 22 open calls Asterisk 16 has 15 open calls Asterisk 17 has 15 open calls Asterisk 30 has 71 open calls Total 164 active calls The

hi: when using chan_sip, I can use set SIP_CODEC in dialplan to change the codec of endpoint. this method didn't work with pjsip in asterisk 12/13. I found asterisk 12/13 has a new function PJSIP_MEDIA_OFFER. according to the description, it seems can set codec, but the document didn't offer any example. i try to use something like PJSIP_MEDIA_OFFER(alaw) but didn't work.

Hi, We're holding ourselves back from moving to PJSIP as we don't appear to have figured out how to force codec preference in a dial plan. The 'PJSIP Advanced Codec Negotiation' document (https://wiki.asterisk.org/wiki/display/AST/PJSIP+Advanced+Codec+Negotiation) appears to ultimately be what we're after, but we're not comfortable running Asterisk 18 in production just

On 03.10.19 15:08, Administrator TOOTAI wrote: > Before calling the gatreway add > > same = n,set(SIP_CODEC=alaw) > > [...] > Hey there, that doesn't work as it seems to be implemented for chan_sip only; I'm using chan_pjsip; sorry if I didn't explain myself properly. Anyway, in my case that would not really be an acceptable solution anyway, because I need the

hello, is it possible simultaneously use chan_sip and chan_pjsip? if yes, can you recommend settings i'm thinking about - chan_sip - for sip hardphones/softphones (sip udp 5060) - chan_pjsip - for webrtc -- --------------------------------------- Marek Cervenka =======================================

Dne 13.8.2015 v 17:20 Rusty Newton napsal(a): > On Thu, Aug 13, 2015 at 3:54 AM, Marek ?ervenka <cervajs at fpf.slu.cz > <mailto:cervajs at fpf.slu.cz>> wrote: > > hello, > > is it possible simultaneously use chan_sip and chan_pjsip? > > if yes, can you recommend settings > > i'm thinking about > - chan_sip - for sip

Hi, We have been migrating our PBX system from Asterisk 1.8 and chan_sip to Asterisk 13 and chan_pjsip. Things are mostly, ok, but now I have stumbled on a behaviour difference I don't like. With chan_pjsip when a phone went unexpectedly offline (Ethernet cable disconnected) Asterisk would detect this quickly (through the 'qualify' pings), mark the phone as 'Unavailable' and

Hey all! I recently tried the dtmf_mode "auto_info" on my setup to support endpoints that only understand SIP INFO as a fallback. My setup is the following: Endpoint A (RFC4733) --> Asterisk <-- Endpoint B (SIP INFO) Both are configured with "auto_info" dtmf_mode in pjsip.conf. What I ran into is, that DTMF sent from endpoint A to endpoint B is additionally sent via

Hi: I am useing asterisk 11.12. I use G722 as preferred codec for my ip-phone. and my PSTN DAHDI use alaw. G722 is great when ip-phone talks to each other. but when ip-phone dialout to PSTN DAHDI, G722 is not great, since it is need to transcode to alaw. so I try to change the codec when dial from SIP to DAHDI. I tried to use IP_CODEC/SIP_CODEC_OUTBOUND at dialplan. but the SIP

The Asterisk Development Team would like to announce the release of Asterisk 13.37.0. This release is available for immediate download at https://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 13.37.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following issues are resolved in this release:

The Asterisk Development Team would like to announce the release of Asterisk 16.14.0. This release is available for immediate download at https://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 16.14.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following issues are resolved in this release:

The Asterisk Development Team would like to announce the release of Asterisk 17.8.0. This release is available for immediate download at https://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 17.8.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following issues are resolved in this release:

The Asterisk Development Team would like to announce the release of Asterisk 16.12.0. This release is available for immediate download at https://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 16.12.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following issues are resolved in this release:

The Asterisk Development Team would like to announce the release of Asterisk 16.12.0. This release is available for immediate download at https://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 16.12.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following issues are resolved in this release: