You could do the old school method and create and move a .call file from
your dialplan.
exten => writefile,1,NoOP()
same => n,Set(CALLFILE=/var/spool/asterisk/tmp/${FileName}-${ARG1}.call)
same => n,Set(FILE(${CALLFILE},,,al,u)=Channel: SIP/bob)
same => n,Set(FILE(${CALLFILE},,,al,u)=WaitTime:
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:
> >
On Tue, Sep 22, 2020 at 7:37 AM Antony Stone <
antony.st...@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.
>
>
>
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
Hello all,
This may sound an odd question but if you initiate a call using AMI does it
adhere to what has been defined in the dial plan or do we have to write the
logic into the AMI call ?
--
Thanks, Phil
--
_
--
Please ignore as this was a user error!
--
Thanks, Phil
- Original Message -
Hello all,
This may sound an odd question but if you initiate a call using AMI
does it adhere to what has been defined in the dial plan or do we
have to write the logic into the AMI call ?
--
Thanks,
