similar to: Originate from the Dialplan

Hi All, I am in the process of migrating from 1.4.20 to 1.6.2.x and have stumbled across a number of "differences" between the 2 versions that are forcing me to use local channels in my dialplan (mainly centered around the different behavior of CDR fields in the 2 versions) . Previously, I would place a call via an AMI Originate action similar to: action:.Originate..

On Tue, Sep 22, 2020 at 7:37 AM Antony Stone < Antony.Stone at asterisk.open.source.it> wrote: > Hi. > > (Asterisk 16.2.1) > > I'm using AMI Originate to initiate calls, and I'm passing some additional > data in to the dialplan context using the Variable: parameter. Works fine. > > >

On Tuesday 22 September 2020 at 13:27:27, Joshua C. Colp wrote: > On Tue, Sep 22, 2020 at 7:37 AM Antony Stone wrote: > > Hi. > > > > (Asterisk 16.2.1) > > > > I'm using AMI Originate to initiate calls, and I'm passing some > > additional data in to the dialplan context using the Variable: > > parameter. Works fine. > > > >

Hi. (Asterisk 16.2.1) I'm using AMI Originate to initiate calls, and I'm passing some additional data in to the dialplan context using the Variable: parameter. Works fine. https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+ManagerAction_Originate Now I need to do the same thing but from another context in my dialplan, so I was expecting to use the Originate() dialplan command,

Sorry for the simple question. I'm trying to match "sipprovider.nocredit" but the following doesn't execute NoOp (it runs "context" but not "context-custom"). What am I doing wrong? [context] include => context-custom exten => _.,1,Set(GROUP()=1) exten => _.,n,Goto(destcontext,${EXTEN},1) [context-custom] exten => sipprovider.nocredit,1,NoOp(No

Hi, I would have thought that when spawning a channel using the Originate() dialplan command, variables prefixed with two underscores would be preserved. However this does not work in the following case. Dialplan code: [intern] exten => 200,1,Set(__myvar="foo") exten => 200,n,Originate(Local/123 at test_orig,exten,dummy) [test_orig] exten => 123,1,NoOp(${myvar}) exten =>

Hello, I'd like to use the AMI interface to originate a call to a context in a dialplan, and handoff the dial control to the context. Whenever I execute the below action, the recipient does ring, but when I answer it dials the recipient again. I believe this is because once answered the system is going to execute the Context/Exten/Prio in the Originate action? Action: Originate Channel:

Dear all, as you know, we can use Originate Command to auto-dial a out-bound call to a extention or app since 1.6.2. but when i Originate a call, and hangup. the cdr of this call has no CDR(clid) and CDR(src). Could you tell me how to set the Callerid to cdr from an Originate call? I use Originate directly in the dialplan not AMI, so i can't set the callerid property like AMI use

Gang, I'm wondering if anyone has run into this problem and found a solution. When I use the manager interface to generate a call, I don't get very much information in my CDR records when the dial status is BUSY, FAILED, NOANSWER, etc. I am putting the dialed number into the CDR Userfield in my dialplan, but the field doesn't populate the CDR record unless the Originate action is

Hi We have the following test .call file and test dialplan: I can't set a custom CDR var to a value on one channel leg, and another value on the connected channel leg? Is there a way I can woraround this issue? ## test call file Channel: Local/queue at TiagoGeada CallerID: teste-geada:0:210332450: MaxRetries: 0 RetryTime: 1 WaitTime: 8640 Account: teste-geada Context: TiagoGeada

I'm currently working on a perl script convert csv logs to a http log equiv: LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" Right now I have output something similar to this: 111 - - [02/Aug/2003:16:39:15 -0500] "GET /300 HTTP/1.0" 200 6144 "sipext" "ANSWERED" INCOMING - -

Hi, I'm getting errors while originating a call through AMI. [Dec 12 21:18:35] ERROR[8661]: utils.c:1236 ast_careful_fwrite: fwrite() returned error: Broken pipe [Dec 12 21:18:35] ERROR[8661]: utils.c:1236 ast_careful_fwrite: fwrite() returned error: Broken pipe [Dec 12 21:18:35] ERROR[8661]: utils.c:1236 ast_careful_fwrite: fwrite() returned error: Broken pipe Asterisk version 11.0.1

Hi, There's a quite complex dialplan scenario and I found out that CDR of main channel is flushed right after hangup on Local channel. I will try to simplify my scenario: [incoming] exten => 555,1,Noop(do something before using local channel, fill some variables, play IVR menus and so on) same => n,Dial(Local/555 at office/n,,g) same => n,Noop(Notice the option "/n" and

Hello, I'm using Asterisk with Realtime extensions and ODBC CDR. And I'm have some trouble with the CDR userfield that is not changed when using the SET command in the realtime dialplan. In my dialplan (extensions.conf, the file) I'm setting the userfield like this : exten => s,n,Set(CDR(userfield)="X") Later, my dialplan switches to the realtime part and this is an

My PHP script is using AMI's Originate command to make two-way calls. The originate connects the first leg of the calls, plays a file to the first called party, and then uses Dial() from the dialplan to dial the other leg of the call. I'm noticing that only about 30% of the calls make it through successfully. In looking at Asterisk's CDR's, I have noticed a lot of "NO

Hi List, We are trying to make a click 2 call button, we have a PHP script that passes the 1st phone number of the 1st leg to a manager script, that then dials the 1st call, then the 2nd call gets placed inside of Asterisk using a normal dial command. Problem is, we get no status codes, we cannot see if their was a hangup, a answer anything, and also once the callers hangs up, it's killed and

Hey, I just found this in ML archives. I have pretty the same situation - i had very well written CDR processing engine on asterisk, making use of ResetCDRs, however now when we're migrating to 1.4, it's a bit pain to deal with extra CDR records. My engine is built so that MYSQL CDR can be used directly for reports (imagine - you get whatever report you need immediately). So, this way i

Hello all, I'm trying to develop a dialer interface from my application, basically to originate calls on asterisk using the Manager Interface. During this development I came across a situation and I realized that the asterisk Originate command could be a little better than it is actually. Anyone who tried Originate for a "commercial" use will

2013/3/26 Richard Mudgett <rmudgett at digium.com> > > On 03/25/2013 05:17 PM, Olivier wrote: > > > Hello, > > > > > > I'm giving hangup-handlers a try on a new Asterisk 11.2.1 setup. > > > My plan is to use this handler to update my CDRs with values such > > > as > > > Asterish and Tech cause (see function HANGUP_CAUSE). >

Hi All, I have been running a environment with asterisk 1.4.20.1 for some time now with no issue but have recently added some extra functionality (enabled call recording via MixMonitor) and ran into some deadlock issues which seem to be well documented with earlier 1.4.x releases so have decided to take the plunge and upgrade. I decided to start testing with 1.6.2 but have run into a couple