Callid Vs conn Id

[kamesh]

Need to understand the difference between the callid and the connid. Will the combination of callid and connid guaranteed to be unique across multiple restarts of Tserver?

Thanks
Kamesh

[René]

Hi Kamesh,

CallId - call identifier generated by switch
ConnectionId - call identifier generated by TServer

ConnectionId shouldn't be treated as an unique identifier as it could be reused e.g after restart. Singleness of CallId - not able to confirm it is unique or not as it depends on switch.

R.

[persmen]

Hi Kamesh,

both of callid and connid pair rotated large numbers. Rotating period can changed pbx to pbx. If you want, you may learn from your pbx guy this technical information.

I think callid and connid pair unique for a long time. (Pratically) But this combined value not always gurantee to unique info for call.

If you think this combination for logging i prefer add datetime value to info.

[victor]

Kamesh,

unless you have millions of calls, ConnID should last you for a very very very very long time. Our CallID is flipping at least 4 times a day on one of the call centers, while I have yet to see a new ConnID.

The cool thing about ConnID is that it is unique multi-site! I do not think that even restarting PBX would reset your ConnID - wasn't one of the parameters it is based  is datetime (and why do I feel like there are way too many "is"?)

Vic

[René]

Vic,

You can see "duplicated" ConnID after restart of TServer in case of having high call volume. I've seen it already...

The same ConnID could be assigned by TServer to consultation call if TServer is configured to do so (option "use-data-from")...

R.

[gururajs]

I would like to know the maximum connids a call can have.
For ex: If a call is transferred to another agent or conferenced, will the connid of the call
change? or will Tserver attach the same connid to the call?

[JGMG]

Hello Kamesh:

[b]Uniqueness:[/b]

Since neither connid or callid are guaranteed to be unique, technically the combination therof is not guaranteed to be unique either.  Connids are unlikely to repeat given that the connid is generally a combination of the timestamp, server-id T-Server option and callid from the switch (precise format varies from T-Server to T-Server I belive)

[b]Number connids/call[/b]

A call will have a primary connid which will survive the life of the call, but it may have many associated Consult connids if there are many two-step transfers or conferences.  I do not believe there is a hard limit to the number of consult connids a call can have during it's lifetime.