There is a problem with using CAR to get CDR/Reports from Extension mobility users due to the lack of fixed device association in the SQL database. The users in the database get associated with a device profile and not a SEPXXXXXX phone record, so CAR has no way to tie the two entities together. There's a couple of Cisco Bug ID's related to this, but I don't have them to hand. I kind of got a work around where you can query the CDR database with an SQL query tool, and do a SQL inner join between the CDR database and the device database to try and pull raw CDR records from the Database and create your own tables. It's messy, and remember the date/time field in the CDR record database is elapsed time since Jan 1 1970. You need to do a field conversion.
Apparently CCM4.0 will have correct CAR/EMobility functionality. Email me if you want the SQL query structure to create your own reports.
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...