Hello all. We are attempting to consume some data via an AES link to monitor call information. We we see is that the data coming across the link for Call ID does not match what is present subsequently in ECH. For instance we will see a Call ID of "403" via the API but then in ECH it is a much longer callID. Is there a way to match these up or is it by design that call id referenced via AES is not the same as what will be recorded in ECH?

It sounds like ECH is reporting the Universal Call ID (UCID). You can see this in many of the DMCC Call Control events as well.

Martin

No our each has both the ucid and the call id. It is not the same call id that is present in aes feed though and that is the problem.

Example

Communication Manager only reports CallID and UCID to AE Services. I have never come across the other CALLIDs that ECH is using. You will need to query these with somebody who is familiar with ECH.

Martin