similar to: why doesn't extension "s" work ?

Displaying 20 results from an estimated 4000 matches similar to: "why doesn't extension "s" work ?"

2015 Dec 02
2
Issues with Twilio number incoming call and context matching
Yes, I have tried that too (i.e, exten => +17775551212,1,Log(WARNING, TWILIO)). It does not work and NO error message in CLI. I have also tried http://orourketech.com/elastix-plus-sign-caller-id-messing-things/ since I first emailed this group, but that does not seem to work either. Here is my log: [Dec 2 15:09:28] NOTICE[26464]: res_pjsip_session.c:1920 new_invite: Call from
2023 May 23
3
Problems Solved, two left
And I think they're both small. Solved: tcpdump showed no packets coming in, so I went to my DID provider's Website to discover to my intense embarrassment that the DID number had been set up forwarded to their voicemail. I got egg on my face for this one. I changed that setting to SIP/IAX and packets now arrive and go where they should. Two problems remain. 1. Still can't
2015 Dec 02
4
Issues with Twilio number incoming call and context matching
Hello, I am running Asterisk 13.6.0 in an AWS instance, and I set it up with Twilio SIP trunk using pjsip_wizard.conf (nice feature!). I see that the calls actually "reach" the PBX, but for some reason, they are not caught by any of my extensions context. Here's what I observe when I test this from a non-PBX connected E164 number (a landline), say 555-666-1212. My Twilio number is
2019 Apr 05
2
pjsip endoint woes
I'm trying to set up pjsip to work with an obi202 and google voice. But I can't configure the endpoint. pjsip: [obi202-auth](!) type = auth auth_type = userpass password = <mypass> [obi202-aor](!) type = aor max_contacts = 2 ; ===== endpoints ======== [gv-voice](obi202-endpoint) auth = gv-voice aors = gv-voice identify_by=auth_username ;identify_by=username ; I also tried
2019 Apr 08
2
pjsip endoint woes
On Sat, Apr 6, 2019, at 10:04 AM, sean darcy wrote: > On 4/5/19 10:36 AM, sean darcy wrote: > > I'm trying to set up pjsip to work with an obi202 and google voice. But > > I can't configure the endpoint. > > > > pjsip: > > > > [obi202-auth](!) > > type = auth > > auth_type = userpass > > password = <mypass> > > >
2018 Dec 10
4
PJSIP_HEADER - Diversion header manipulation
Hi all, I’m trying to rewrite Diversion header when call forwarding is done on the phone. The phone sends "302 Moved Temporarily" response and sets Diversion header to a local number, but before Asterisk sends this call towards TSP provider I need to change Diversion header to a full PSTN number. I am using PJSIP_HEADER in a pre-dial handler (configuration is below). On the same
2015 Oct 06
2
PJSIP: how to retrieve underlying SIP Call-ID
Hello, I've started to play with PJSIP and got stuck at the following problem. I need to retrieve SIP Call-ID associated with PJSIP channel. For inbound channel I can use ${PJSIP_HEADER(read,Call-ID)}, but that doesn't work for outbound channel even in pre-dial or hangup handler. Whatever I do PJSIP_HEADER seem to be unable to read headers for outbound channel. Here's what I do:
2015 Jul 10
2
Can I use PJSIP_HEADER to read the SIP 183 message header?
Hi. The ASTERISK wiki has a page showing the function PJSIP_HEADER(). However, it doesn't explain if such function works only over SIP INVITE messages or if it can be use, for example, to read headers from others types of SIP messages too. So, can I use PJSIP_HEADER to read the SIP 183 message header? Any hint will be very helpful! Best regards. RODRIGO PIMENTA CARVALHO Inatel
2018 Nov 27
2
PJSIP add header on forwarded call
Le 27/11/2018 à 12:13, Joshua C. Colp a écrit : > On Tue, Nov 27, 2018, at 5:49 AM, Administrator TOOTAI wrote:[...] >> >> [TOOTAiAudio] >> ; >> ; Call our gateway >> >> exten = s,1,Set(PJSIP_HEADER(add,X-TOOTAiAudio-CALLED)=${ARG1}) >>  same = n,Dial(PJSIP/${ARG1}@TOOTAiAudio,,T) >>  same = n,Return >> >> exten = h,1,NoOp()
2015 Jul 10
2
RES: Can I use PJSIP_HEADER to read the SIP 183 message header?
Ok Mark Michelson. Thank you very much! You answer tells me that I was in the wrong path trying to access information from SIP 183 message. I need to find a way to let the callee pass information/data to the caller, even before accepting the call. That is, send data during the ringing time. And in my case, there will be more than one callee ringing at same time. As ASTERISK will not forward each
2015 Aug 24
3
PJSIP add
I am trying to set add a SIP Header to a call before adding it to the Queue. The dial plan sends the call to my macro to perform the work. When I use chan_sip, everything works as expected. When I use PSJIP support, it's not adding the SIP header. Looking at the output, I see the macro is called in both cases. In the PJSIP case, the added sip header never is showing up in the asterisk logs
2018 Nov 27
2
PJSIP add header on forwarded call
Hi list, to manage an external queue agent the only solution I found is to connect a local account and redirect calls to this account using forward features from the phone (SNOM). The problem I face is that before calling the agent I would like to set extra header. Dialplan to call external agent is this one with (Gosub): [TOOTAiAudio] ; ; Call our gateway exten =
2017 Jun 05
3
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
On Mon, Jun 5, 2017, at 04:26 PM, Michael Maier wrote: > On 06/05/2017 at 06:29 PM, Joshua Colp wrote: > > On Mon, Jun 5, 2017, at 01:22 PM, Michael Maier wrote: > >> > >> Do you have any idea where to start to look at? Adding additional output > >> in the source code? Which functions could be interesting? I may add own > >> debug code to see why things
2011 Mar 09
6
SIPAddHeader not working
Hello list, I notice that the dialplan method SIPAddHeader is not working : in dialplan : /exten => s,n,SIPAddHeader(Privacy: id)/ in SIP invite no trace of this header : /INVITE sip:0473 at sip.domain.be SIP/2.0 Via: SIP/2.0/UDP 192.168.1.106:5063;branch=z9hG4bK-5b2b1b97 From: "VC" <sip:voip2 at sip.domain.be>;tag=729476652f511c67o2 To: <sip:0473 at sip.domain.be>
2010 Nov 23
2
Function SIP_Header not registered
Hello, I'm trying to use SIP_HEADER function on my dialplan but I receive this message (on the console): pbx.c:3367 ast_func_read: Function SIP_Header not registered Why? Thank's - Bakko
2006 May 18
2
SIP Header Info
I remember seeing something somewhere that described how I could get SIP header information with Asterisk. It was a command or a variable. Anyone know what it is? Thanks. Doug.
2023 Jun 17
1
Get SIP Call-ID from ARI
On Sat, Jun 17, 2023 at 2:55 PM TTT <lists at telium.io> wrote: > Based on postings it should be possible to get the SIP Call-ID header > value from the ARI. At what point is this value available ? As well, how > do I retrieve that value – something like > > > > GET /channels/{channelId}/pjsip_header?key=Call-Id > > > > But that doesn’t work. >
2016 Mar 31
2
Asterisk 13 - Call Bridge issue.
I have the following senerio. Call file calls 1st party. When connected give called party option to connect to second party. Issue Dial to second party. Caller answers and the two are bridged together. My issue is that 4 out of 5 calls fail to bridge the audio. Am I missing something or is there some kind of bug? Here is my test dialplan ;Dialer Base Code Files. ;Variables
2016 Sep 02
3
Trouble getting peer variable (sip username) on 302 Moved Temporarily
Hello when setting a local forward (in this case to extension 23) on a SIP phone, I see the following on the Asterisk CLI : [Aug 31 14:59:34] -- Got SIP response 302 "Moved Temporarily" back from 11.22.33.44:40670 [Aug 31 14:59:34] -- Now forwarding Local/myaccount184 at CallFromQueue-000007f4;2 to 'Local/23 at from-internal' (thanks to SIP/myaccount184-00003729)
2017 Jun 15
2
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
On 06/14/2017 at 10:17 PM, Joshua Colp wrote: > On Wed, Jun 14, 2017, at 05:09 PM, Michael Maier wrote: > > <snip> > >> >> I can now say, that asterisk / pjsip seams to work *mostly* as expected. >> Just one exception - and that's the package in question, which can't be >> seen in tcpdump. >> >> I extended the above patch by adding