similar to: SIP 503 instead of SIP 480 in asterisk debug mode

Hi, I was trying to use 2 of asterisk servers and interconnected, one of them as a peer to other sever (configured in sip.conf), so all the calls to server 1 will just be passed to server 2 (has PRI Card, TE 412P, only one PRI connected), i was sending calls to server 1 and that would send to server 2 and then dial out using Dahdi, but the problem that i got was the hangup cause codes, i was not

I got two phones on an ATA-186 (601, 602) and two phones on the TDM22B (603, 604). I have two lines on the TDM22B. I cannot figure out some of the problems: 1. 601 dials via ZAP/3-1 to local phone number at PSTN: ringing pickup on PSTN (empty) still ringing in the phone set 601 2. call from PSTN back: 601 picks up ... everything works !!! No caller id shows up 3. For testing I have only one

I have a Asterisk server (PBX in a Flash) with Aastra 57i phones. When there is an incoming call the phone will display two buttons "answer" and "ignore". If you press "ignore" the call is dropped instead of sent to voice mail. The following is the log: -- Called 111 -- SIP/111-00001c14 is ringing -- Got SIP response 486 "Busy Here" back from

Just throwing this out here, hopefully someone can tell me why. *CLI> show version Asterisk CVS-HEAD-11/17/04-10:16:38 built by root@wanderer on a i686 running Linux Zap/g1 is pri_cpe to Bell Canada 5551234 is a normal POTS line I have busied out (handset offhook) exten => 1234,1,Dial(Zap/g1/5551234,,g) exten => 1234,n,NoOp(HANGUPCAUSE is ${HANGUPCAUSE} and DIALSTATUS is

Hi List, we're calling a sip phone from our Asterisk Server, and try to add logic depending on the dialstatus Stripped down example; exten = 494XXXXXXXXX,n,Dial(SIP/4120089,15,w) exten = 494XXXXXXXXX,n,Goto(98-${DIALSTATUS},1) exten = 494XXXXXXXXX,n,Hangup() ..... exten = 98-BUSY,1,NoOp(Busy) exten = 98-BUSY,n,ExecIf($["${Voicemail}" =

Hello list, Hope all doing well! I've been checking some cases when a Dial fails and dialplan execution continues to handle this. I am finding it a little confusing how we should handle the DIALSTATUS and the HANGUPCAUSE in this situation.... More specifically, I am facing a case in version 13.6.0 where I am getting a DIALSTATUS=BUSY and HANGUPCAUSE=19 after receiving a 480 SIP error. Seems

I'm trying to add a second extension to my setup. The second device is able to successfully connect to the Asterisk server. I am unable to contact extension 101 from 102 and vise-versa. Also are my context setup logically or is there a better fashion to organize them? My error is at the bottom. Here is the extension.conf [default] ; ; By default we include the demo. In a production system,

I have an issue where a particular dialplan works but another doesn't. I'm not sure why. To me they look identical and it has me stumped. This works: [to-test] exten => _X., 1, SetCallerPres(allowed) exten => _X., 2, Monitor(wav,/tmp/test-${UNIQUEID},mb) exten => _X., 3, Ringing exten => _X., 4, Dial(SIP/9330 at a-test,20,ro) exten => _X., 5,

Hi. I'm dialling two numbers - one that's unobtainable, one that's busy. ${DIALSTATUS} is coming back ANSWER each time right before the channels hang up. Am using the following dialplan macro to dial out. [macro-advdial] exten => s,1,Dial(${ARG1},20,g) ; Ring the interface, 20 seconds maximum exten => s,2,Goto(s-${DIALSTATUS},1) ; Jump based on status

Hello all, I am working on a creating some intelligent failover dial-plan logic and I'm running into something that I'd like some feedback on. Basically, it appears that if you place a call to an IAX2 peer that refuses the connection, or is unavailable, a NOANSWER dialstatus is returned. Example: -- Executing Macro("IAX2/cubix-19",

Hi, I'm using the macro below in extensions.conf for most of my outbound calls. One issue with my current configuration is that when I make an outbound call it doesn't properly detect that my PSTN line (Zap/1) is busy with another call and then overflow to my outbound IAX connections. I think the root cause is that DIALSTATUS gets reported as BUSY. The debug output is below. My desired

I can dial from 601 to a public number. The public number rings. I pickup and hear nothing, while on 601 it keeps ringing. (BTW, is it right to say "ringing" on the active phone?) The *CLI> doesn't show me anything useful: Executing Macro("SIP/601-8238", "dial-pstn|88097880|") in new stack Executing SetGlobalVar("SIP/601-8238",

Hi, I'm trying to implement dynamic routing of incoming calls to local extension if previous outgoing call was unanswered. But after I do Goto to s-NOANSWER, variable ${EXTEN} changes to 's-NOANSWER'. I guess this is normal, but I don't understand why ? How to workaround on this one ? Thanks in advance, regards, Rob. [outbound-capi-ISDN] exten => _0.,1,NoOp(Calling ISDN

Hi All! Let me explain the problem. When using the Originate? command from the manager api, the dialstatus variable returns results? for whichever phone picks up first, and in this case it is the IAX/2? connection. It doesn't matter if Zap/G2/XXXXXXX is set as the channel,? or an extension either. What I am ultimately trying to do is get the? dialstatus of the Zap/X/XXXXXXX channel, i.e.,

Dear All Can you please do me favor and let me know what is my problem with my Asterisk VoiceMail configuration as it doesn't work correctly in my case ? Please find below that part of my extensions.conf that I intend to make use of voice mail for No Answer reply : " [line-incoming] exten => _XXXXXXX,1,macro(dialuser,SIP/${EXTEN},${EXTEN}) [macro-dialuser] exten =>

Thanks Dovid! Indeed looks a bug but regardless of this, this problem made me think that the HANGUPCAUSE could be used for this purpose with benefits. I couldn't find an explanation about when DIALSTATUS would actually be better. The HANGUPCAUSE was reworked in version 11 ( https://wiki.asterisk.org/wiki/display/AST/Hangup+Cause) but I didn't find someone actually stating it is a better

I'm trying to write a dialplan that will allow me to "stress" test it. I want to be able to dial an extension, or pretend that the extension is busy or out of order (so that I can see what to do) given the dialplan snippet: [outbound] exten => _X.,1,NoOp(${TEST}) exten => _X.,n,Dial(SIP/${EXTEN}) exten => Busy,1,Busy(2) exten => Busy,n,Hangup() exten =>

Hi All, I'd just like to verify what the correct operation of the timeout parameter is for the dial application. I'm not sure if I've encountered a bug or a configuration issue. When a sip phone is not responding to invites on an outbound call, the dial application still waits the duration of timeout before continuing with dialplan execution. I was under the impression that app_dial

Hi, according to the wiki the value NOANSWER for the channel variable DIALSTATUS means: No answer. The dial command reached its number, the number rang for too long, then the dial timed out. In out dialplan we grap all these events with exten => s-NOANSWER,1,Playback(sometext) exten => s-NOANSWER,2,WAIT(1) exten => s-NOANSWER,3,Hangup() The dial commands for internal and external

On machine A I have something like the following in extensions.conf: [iax-extensions] exten => _9.,1,Dial(IAX2/machineB/${EXTEN:1}@mycontext) exten => _9.,2,NoOp(DIALSTATUS=${DIALSTATUS}) exten => _9.,3,Hangup On machineB I have something like this: [mycontext] exten => 2002,1,Dial(SIP/2002,60) exten => 2002,2,NoOp(DIALSTATUS=${DIALSTATUS}) exten => 2002,3,Hangup If I use a