The MediaSense API docs talk about using the Call Correlation ID to link MediaSense recordings to CUCM calls. The MediaSense API for getSessionsByCCID shows the call correlation ID being a GUID. But the only field in a CUCM CDR (That I can see) that could be the GUID is the CDR ID field. But searching on this doesn't return any calls.
What field in the CDRs is MediaSense using for the correlation IDs?
We are using the Call Correlation ID to link MediaSense recordings to CUBE calls.
CCID is not used with CUCM calls as already mentioned CUCM gives Call detail record(CDR) ID field for searching
We are able to search in Mediasense Search And Play(Also hitting the getSessionsByCCID API) using call correlation ID being a GUID .
Please find below some more information:
"Call Correlation for Calls Forked by CUBE" is called IncomingProtocolCallRef in the CUCM CDR
Call Correlation for Calls Forked by CUBE
|Ingress Gateway or CUBE||AAA RADIUS CDR||UCM CDR||TAPI/JTAPI field||UCCE Database||UCCE Script||CTIOS||GED-188|
- In recordings of Unified Communications Manager calls, Cisco MediaSense does in fact receive a Cisco-GUID from UCM, but it is not the same one that is captured by the other solution devices. MediaSense therefore does not even store this value.
- CCID is the Cisco-GUID in decimal form, which is 4 hyphen-separated sets of 10-digit decimal numbers. These can be converted to the hex form by simply converting each 10-digit decimal number to an 8-digit hex number, and removing the hyphens. Where the Cisco-GUID is used in UCCE, it is in its hex form.