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 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 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 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 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
