Hello,
since al long time I have used UNIQUEID for identify calls in my dialplan,
statistics...
Now I have had an problem, after I have checked log file I found out following:
calls same time ( hours:seconds) came in.
CallID, DID, channel name (00003cf9 to 00003cfa) are different.
Only UNIQUEID is identical
Is there any known bugs or ist UNIQUEID not unique and can not be used for
identify calls?
[Aug 28 10:14:11] VERBOSE[6413][C-00001f1e] pbx.c: -- Executing
[XXXXXX at patton4970in:1] NoOp("SIP/outbound.patton-00003cf9",
"INFO:
eingehender Anruf Context patton4970in von
SIP/outbound.patton-00003cf9 "" <XXXXXX> zu XXXXXX") in new
stack
UNIQUEID: 1503908051.54095
[Aug 28 10:14:11] VERBOSE[6418][C-00001f1f] pbx.c: -- Executing
[XXXXXX at patton4970in:1] NoOp("SIP/outbound.patton-00003cfa",
"INFO:
eingehender Anruf Context patton4970in von
SIP/outbound.patton-00003cfa "" <XXXXXX> zu XXXXXX") in new
stack
UNIQUEID: 1503908051.54095
thanks..
Joshua Colp
2017-Aug-29 14:03 UTC
[asterisk-users] UNIQUEID not unique in different channels
On Tue, Aug 29, 2017, at 10:57 AM, Thomas wrote:> Hello, > > since al long time I have used UNIQUEID for identify calls in my > dialplan, > statistics... > > Now I have had an problem, after I have checked log file I found out > following: > > calls same time ( hours:seconds) came in. > > CallID, DID, channel name (00003cf9 to 00003cfa) are different. > > Only UNIQUEID is identical > > Is there any known bugs or ist UNIQUEID not unique and can not be used > for > identify calls?There's no known bugs and it is absolutely supposed to be unique. I'd suggest filing an issue[1] with logs and details. Also ensure you are using a currently supported version of Asterisk. [1] https://issues.asterisk.org/jira -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org