04-08-2015 07:02 AM
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?
GTG
04-09-2015 11:30 PM
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 .
04-12-2015 11:36 PM
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
MediaSense | Ingress Gateway or CUBE | AAA RADIUS CDR | UCM CDR | TAPI/JTAPI field | UCCE Database | UCCE Script | CTIOS | GED-188 |
---|---|---|---|---|---|---|---|---|
CCID (3) | Cisco-GUID | Cisco-GUID | IncomingProtocolCallRef | TCD.CallGUID | Call.CallGUID | CallReferenceID |
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide