Achievement_First
asked on
Cisco Unity Call Records
My company identified an issue where a number of international calls were made on our phone line and we need to determine what phone the calls were coming from. We are currently on Cisco Unity 10.0.1 but are unsure how to pull the relevant call logs to identify where the calls were coming from.
If you can provide any assistance, that would be greatly appreciated.
If you can provide any assistance, that would be greatly appreciated.
You would pull the records from call manager not unity. Check the CDR in reporting
If it has been activated you can get to the CAR page via https://cucm-ip-address/car/
Here's how to activate it and run reports.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/10_0_1/car/CUCM_BK_C885BA46_00_cdr-analysis-reporting-administration-100/CUCM_BK_C885BA46_00_cdr-analysis-reporting-administration-100_chapter_00.html
Here's how to activate it and run reports.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/10_0_1/car/CUCM_BK_C885BA46_00_cdr-analysis-reporting-administration-100/CUCM_BK_C885BA46_00_cdr-analysis-reporting-administration-100_chapter_00.html
ASKER
Thanks - we were able to pull some items from CDR, but do you have a sense/idea of how to read the data to determine what device made the outgoing call?
Please upload the title row so we can see what you are seeing.
So you went to CDR/Search/(By User/Phone Number/SIP URL), gave it a date.
After that view the CDR = CMR Dump and look for origDeviceName .
Now a misconfigured system could allow external inbound calls to have dial tone and dial back out, but lets assume that is not the problem for now and you will see a origDeviceName
After that view the CDR = CMR Dump and look for origDeviceName .
Now a misconfigured system could allow external inbound calls to have dial tone and dial back out, but lets assume that is not the problem for now and you will see a origDeviceName
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The issue wasn't resolved because the basic premise was flawed.