We're having issues getting 100% match between CMR & CDR data. This behavior is regardless of whether it's a standalone cucm server or cluster. The cdr & cmr data from the billing server/sftp server is processed separate and saved into separate DB tables. When trying to match cmr info to cdr, there isnt a 100% match...there is a retry process that continues to check for match for abt 8hrs. Still a match is not found.
This is the logic used to match cmr to a cdr.
call identifier of cmr = origLegCallIdentifier or destLegCallIdentifier in cdr
Are there any issues in the match logic or is this a known issue?
One example where I saw this happen is with SNR (single number reach) but it's random.
A calls B. B has snr configured.
B's Jabber device rings.
Since B didnt pick up after 2 rings B's cell phone rings but B decides to answer the call via Jabber
For the above scenario,
CMR is generated for B's cell phone, B's Jabber & A (assuming it's an internal call)
CDR is generated for A-B (Device info is B's Jabber)
The cmr generated for B's cell phone does not match the origCallLegIdentifier or destLegCallIdentifier of the cdr record. Hence this file is left behind on the ftp server. There is atleast 5-10 cmr files left behind each day.