Hi.
https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Application_Originate
I need to use Originate() in a dialplan, pointing to another location in the
same extension of the same context, so for example:
Originate(Local/${Dest}@Dialout,exten,${CONTEXT},${EXTEN},158);
I don't seem to be a
On 8/29/22 08:31, Antony Stone wrote:
Hi.
https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Application_Originate
I need to use Originate() in a dialplan, pointing to another location in the
same extension of the same context, so for example:
Originate(Local/${Dest}@Dialout,exten,${CONTEX
On 8/29/22 08:48, Mark Murawski wrote:
On 8/29/22 08:31, Antony Stone wrote:
Hi.
https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Application_Originate
I need to use Originate() in a dialplan, pointing to another location
in the
same extension of the same context, so for example:
O
On Monday 29 August 2022 at 14:51:27, Mark Murawski wrote:
> On 8/29/22 08:48, Mark Murawski wrote:
> >
> > Hi Antony,
> >
> > I love to hear about AEL use-cases. I'm happy that AEL is working out
> > for you.
It is, although there are ways I think it can be improved - I'm wondering how
best
On Mon, Aug 29, 2022 at 10:30 AM Antony Stone <
antony.st...@asterisk.open.source.it> wrote:
> On Monday 29 August 2022 at 14:51:27, Mark Murawski wrote:
>
> > On 8/29/22 08:48, Mark Murawski wrote:
> > >
> > > Hi Antony,
> > >
> > > I love to hear about AEL use-cases. I'm happy that AEL is worki
On Monday 29 August 2022 at 15:35:09, Joshua C. Colp wrote:
> MSet is not deprecated.
https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Application_MSet
includes the sentence "MSet behaves in a similar fashion to the way Set worked
in 1.2/1.4 and is thus prone to doing things that you may
On Mon, Aug 29, 2022 at 10:53 AM Antony Stone <
antony.st...@asterisk.open.source.it> wrote:
> On Monday 29 August 2022 at 15:35:09, Joshua C. Colp wrote:
>
> > MSet is not deprecated.
>
> https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Application_MSet
> includes the sentence "MSet behaves
On 8/29/22 09:53, Antony Stone wrote:
On Monday 29 August 2022 at 15:35:09, Joshua C. Colp wrote:
MSet is not deprecated.
https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Application_MSet
includes the sentence "MSet behaves in a similar fashion to the way Set worked
in 1.2/1.4 and is thu
On 8/29/22 10:15, Antony Stone wrote:
But! What specific reason do you have for wanting Set() instead of
MSet() for all assignments that can't be otherwise just written as an
in-line Set() instead?
I *am* currently writing inline Set() everywhere, but surely the syntax "a=1;"
instead of "Set(a=
On Monday 29 August 2022 at 16:19:17, Mark Murawski wrote:
> On 8/29/22 10:15, Antony Stone wrote:
> >> But! What specific reason do you have for wanting Set() instead of
> >> MSet() for all assignments that can't be otherwise just written as an
> >> in-line Set() instead?
> >
> > I *am* current
On 8/29/22 09:30, Antony Stone wrote:
It is, although there are ways I think it can be improved - I'm wondering how
best to go about proposing these.
The most obvious for now are:
- please can "a=1;" be converted to use Set() instead of MSet() (especially
since MSet is officially deprecated)
On 8/29/22 14:00, aster...@phreaknet.org wrote:
This is a mockup of what the new-style if/else processor would output
26. NoOp(AEL IF("\${DIALSTATUS}" == "BUSY") --
extensions.ael:1405)
27. GotoIf($["${DIALSTATUS}" == "BUSY"]?28:30)
On Monday 29 August 2022 at 17:00:23, Mark Murawski wrote:
> On 8/29/22 09:30, Antony Stone wrote:
> > It is, although there are ways I think it can be improved - I'm wondering
> > how best to go about proposing these.
> >
> > The most obvious for now are:
> > - please can "a=1;" be converted t
On Monday 29 August 2022 at 16:29:42, Antony Stone wrote:
> On Monday 29 August 2022 at 16:19:17, Mark Murawski wrote:
>
> > what specific situation prevents you from using a=1; style syntax? Why are
> > you feeling the need to use Set(a=1) instead of a=1. What are specific
> > examples where th
On 8/30/22 11:16, Antony Stone wrote:
If I write in my AEL dialplan:
Set(Tracker=${CDR(uniqueid)});
this results in executing:
Set(Tracker=eagle.domain.com-1661872057.2349)
Just what I want.
However writing:
Tracker=${CDR(uniqueid)};
results in:
MSet(Tracke
On Tuesday 30 August 2022 at 18:17:08, Mark Murawski wrote:
> On 8/30/22 11:16, Antony Stone wrote:
> > If I write in my AEL dialplan:
> > Set(Tracker=${CDR(uniqueid)});
> >
> > this results in executing:
> > Set(Tracker=eagle.domain.com-1661872057.2349)
> >
> > Just what I want.
> >
>
On 8/30/22 12:34, Antony Stone wrote:
I want.
However writing:
Tracker=${CDR(uniqueid)};
results in:
MSet(Tracker=-1661872057.2349)
systemname is missing.
Hi Antony,
This is not a problem with MSet.
No, it is indeed the documented behaviour of MSet "MSet behaves in a similar
On 8/30/22 17:51, Mark Murawski wrote:
On 8/30/22 12:34, Antony Stone wrote:
I want.
However writing:
Tracker=${CDR(uniqueid)};
results in:
MSet(Tracker=-1661872057.2349)
systemname is missing.
Hi Antony,
This is not a problem with MSet.
No, it is indeed the documented behaviour of
On Tuesday 30 August 2022 at 23:51:34, Mark Murawski wrote:
> On 8/30/22 12:34, Antony Stone wrote:
> >>> Tracker=${CDR(uniqueid)};
> >>>
> >>> results in:
> >>> MSet(Tracker=-1661872057.2349)
> >>>
> >>> systemname is missing.
>
> Please re-evaluate what I wrote previously. Again, this i
On 8/31/22 05:29, Antony Stone wrote:
What I am suggesting is that Tracker=${CDR(uniqueid)} should be converted
by AEL into Set(Tracker=${CDR(uniqueid)}) in order to avoid this sort of
surprise.
On the flip-side... anyone who currently relies on purely
numeric/boolean handling of the current i
On Wednesday 31 August 2022 at 15:01:57, Mark Murawski wrote:
> On 8/31/22 05:29, Antony Stone wrote:
> >
> > I realise that a better solution might be to wrap assignments (inside
> > Set() or MSet(), no matter) with $[..] *only* if the expressions contain
> > arithmetic operators + - * / and not
On 8/31/22 09:25, Antony Stone wrote:
If I simply do
Tracker="${CDR(uniqueid)}";
it works as required.
It's just not the sort of syntax I've seen in any other language, and it feels
(to me) weird.
^^^ Yup! This is what I was suggesting in my last email. Just add quotes.
Think
22 matches
Mail list logo
