I had a similar situation. Reporting on the CALLED party did not show the CDRs where it went to voice mail. But when I reported from the perspective of the CALLING party, I could see the call end up in voicemail port. Unfortunately, this isn't helpful if you need to report on a called number.
If extension 1000 gets and inbound call that is not answered and then goes to voice mail (CTI Route Point that reports as extension 2000), there is CDR generated. In this case, the originalcalledpartynumber would be 1000 and the finalcalledpartynumber would be 2000.
You should see a CDR for the call terminating on the voice mail port.
If your cdr program is not reporting the call it may be because the record to the original called number does not show any time elapsed for that call and/or the system may be discarding calls that are not to known extensions or users.
The best way to verify this is to go to the CDR Analysis and Reporting page, (need to have administrator rights)
Select CDR -> Search by User/Extension.
Enter the extension of the user that received the call and it should show you all of the records for that user.
In the record you should see the Called number being the extension that was called, the Dest. no where the call was actually answered (voicemail) and then the redirecting number which should be the same as the called number.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...