Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^
New DevConnect members must have forum permissions in order to post messages.
If the Reply and New Post buttons are not available to you, please request access using a General Support request ticket.
Forum Index » DMCC APIs » Event timestamp   XML
 
Author Message
igladkova.avaya.com



Joined: 15/06/2021 14:38:36
Messages: 2
Offline

Hello support, could you please help with this question?

is there a way to receive an event timestamp using DMCC API?

Or, is there a unique event ID/sequence number?

Or, if we have two arbitrary event payloads, is there a way to detect if they represent the same event?
JohnBiggs



Joined: 20/06/2005 14:06:52
Messages: 883
Location: Thornton, CO
Offline

given your last statement, not really. A call has a universal Call identifier (UCID). If the same call appears at two different devices (or event streams) you can be sure the events are for the same call. But that doesnt extend to any random event. There is no timestamp provided by CM for events, nor sequence number associated with an event. SequenceIds are unique to a session, and have no relationship across two sessions to each other.
[WWW]
igladkova.avaya.com



Joined: 15/06/2021 14:38:36
Messages: 2
Offline

Got it..
Thank you.
JohnBiggs



Joined: 20/06/2005 14:06:52
Messages: 883
Location: Thornton, CO
Offline

I'll add that calls have callIDs and in general the data in the events related to a callID will also line up if the callIDs line up. The events coming from a common AES should be in the same sequence and contain the same data, but there is no guarentee of that in the protocol specification. There is also no stated guarentee that call events will appear in the same order in two different event streams. When you start considering separate event streams coming from separate AESs, all you can be sure of is that the CallIDs and UCIDs will match up.
[WWW]
 
 
Go to: