[asterisk-users] UNIQUEID not the same in Dialplan as passed to AGI

Örn Arnarson orn at arnarson.net
Wed Sep 9 07:55:37 CDT 2009


Hi,

I've noticed that the UNIQUEID for a call is not the same in the
Dialplan (when executed e.g. exten => s,n,NoOp(${UNIQUEID}) as it is
when passed via STDIN to an AGI script.
Is this normal, and is this supposed to behave this way?

The UNIQUEID received in the AGI is usually .001 higher than the one
in the dial plan -- but sometimes it is also a second behind.
Here's an example from the dialplan, with the corresponding argument
passed to the AGI:

    -- Executing [s at macro-internal-call:7]
NoOp("SIP/10.0.0.4-082a0658", "1252500374.334") in new stack

agi_uniqueid: 1252500374.335

And here's an example where the UNIQUEID is one second and one
fraction point behind:

    -- Executing [s at macro-internal-call:7]
NoOp("SIP/10.0.0.4-0825ef60", "1252500762.337") in new stack

agi_uniqueid: 1252500763.338

Any advice would be greatly appreciated. Can I use something else as a
unique identifier for a call? I'm trying to tag calls, but it is
proving difficult with the ever-changing UNIQUEID.

I haven't found a rule as to when it is delayed by a second and when it isn't.

Best regards,
Örn



More information about the asterisk-users mailing list