Our company are using a CCM5.1 server. Things had been set up and working well. But recently (since 2008-01-29), we cannot get the Call Detail Report using CAR tool.
When browsing the server, I explored that all the CDR files were in /cm/cdr_repository/preserve folder (NOT in /cm/cdr_repository/processed folder as normal). And when viewing Event Log in CAR page, I saw that the status of the job CDR Load was Unsuccessful.
Besides, I couldnot configure a Billing Server in Tools --> CDR management (CCM Service Page).
Could anyone make some explains for this case and give me some help?
During some months CAR has loaded the CDRs of my ccm6.0 cluster without any problem. this was the CDR load configuration in CAR
Load CDR & CMR
Loading interval Every 24hours
Duration 10 minutes
But this Monday I change this configuration. I restarted in the Publisher the 3 services related with CDRs.
Since then no CDR has been loaded in the system.
In CAR --> System --> Log I can see that since the day I changed this the CDR load is tried as I have configured but it is Unsuccessful.
I have tried the Real Time loading for 1hour but it doesn't load any CDR.
I tried to follow the steps that you provided in this conversation. But I don't know how to Restart CDR Repository Manager in all the servers either how to Restart BDL Layer monitor in all the servers .
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...