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 MSet "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 not expect."
Please re-evaluate what I wrote previously. Again, this is not a
problem with MSet. You can see this for yourself if you do an inline
MSet(Tracker=${CDR(uniqueid)}); this will work fine.
Just because the documentation says that MSet should not be used, it's
not appropriate to blame all undesirable behaviors on MSet(), since
clearly MSet() is not the problem here.
Let me correct myself. The documentation doesn't say it shouldn't be
used... it's making you aware of possible side-effects. It's perfectly
legitimate to use MSet() if you prefer the assumptions/behaviors of
MSet() as opposed to the assumptions/behaviors of Set().
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
Check out the new Asterisk community forum at: https://community.asterisk.org/
New to Asterisk? Start here:
https://wiki.asterisk.org/wiki/display/AST/Getting+Started
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
