System integrating with Genesys can capture call info, the captured Connection ID is in a 16-digit (hexadecimal?) number, and Call UUID is a UUID.

Avaya can capture call info, the captured Connection ID is like Device Id: <ext>:<switchName>:<deviceInstance> Call Id: <callId>, and there are 2 call universal IDs, one in number, one in String.

From the sample data, it seems that both connection ID is in different format and could not match each other, one way which seems to work is to match the Genesys Connection ID (convert to decimal number) and Avaya Call Universal ID (in number).
Is this assumption correct? or is there any recommended (globally unique) call identifier which we could use across those system?

Thanks for the advise.

Thank you very much Martin, checked that CM->AE Service CTI link was incorrect, the problem is resolved after fixing the setting.

We are using DMCC Java SDK, tested we could successfully register our client device on a extension and use Media Service and Call Info Service to capture audio stream and get some meta data.

However, when we have to add Call Control Monitoring (which should be part of the third-party call control service), the response to "addCallControlListener()"/"CSTA_MONITOR_DEVICE") is "GENERIC_OPERATION_REJECTION" (71), and from TSAPI logs, the cause value is CS0/18, and the abort type is 161. We have no luck searching this error code in Java API doc, TSAPI doc, etc. and would like see if anyone can provide some ideas on troubleshooting the issue.

We are using CM 8 and AES 8 with DMCC Java SDK v10.1.0.0.0.12