Hello folks,

the getUCID() method on a JTAPI call returns this UCID:

00001004641602153606

and for the same call I get the following UCID from both Breeze and ClientSDK:

00002000531602153606

Does anybody know why the UCID of the JTAPI is different and only half the digits match? Is there any rule that describes this behaviour?
I expected the UCID to be identical in all Avaya SDKs and platforms.
What would be a safe approach to identify calls between JTAPI and the other platforms?

Philipp

On the surface it would appear that passing UCID from CM to SM (or vice versa) is not properly configured.
You are getting different node ID and different call IDs but the same timestamp.

Please verify your CM trunk configuration, and perhaps get a traceSM to ensure CM is passing UCID data to SM in the SIP Invite across the trunk that the call routes through.

Use this FAQ to check your config.
https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/tsapi/private_data.gsp#30