CDR not working

[Guilherme Mascarenhas]

Hi all,

I'm looking into a problem i never saw it before. CDR Flags are true in all cluster, the cdr ftp server is up and configured correctly, CDR Agent service is up and running in all servers and all calls are working fine in all cluster but i'm not receiving cdr from the cucm.

If i look into the log of Subscriber "Cisco CDR files on CM Server", the CDR are correctly generated; but when I look into the subscriber CDR agent , there isn't files to delivery.

all log looks the same:

Subscriber CDR Agent log:

2012-04-17 11:41:11,433 INFO  [main] cdragent.cdrAgent (cdrAgent.java:353) - handleCDRFiles -->

2012-04-17 11:41:11,433 DEBUG [main] cdragent.cdrAgent (cdrAgent.java:250) - No files found for transfer

2012-04-17 11:41:11,433 DEBUG [main] cdragent.cdrAgent (cdrAgent.java:361) - No files to handle

2012-04-17 11:41:11,434 DEBUG [main] cdragent.cdrAgent (cdrAgent.java:206) - Sleeping for 6 seconds 2012-04-17 11:41:11,433 INFO  [main] cdragent.cdrAgent (cdrAgent.java:353) - handleCDRFiles -->
2012-04-17 11:41:11,433 DEBUG [main] cdragent.cdrAgent (cdrAgent.java:250) - No files found for transfer
2012-04-17 11:41:11,433 DEBUG [main] cdragent.cdrAgent (cdrAgent.java:361) - No files to handle
2012-04-17 11:41:11,434 DEBUG [main] cdragent.cdrAgent (cdrAgent.java:206) - Sleeping for 6 seconds

Does anybody have any idea on what’s is happening?

Any help will be really appreciated.

Best Regards,

Publisher cdr repository logs:

2012-04-17 10:48:34,074 DEBUG [Thread-7] cdrrep.CDRSender (CDRSender.java:125) - destination 1 is active

2012-04-17 10:48:34,074 DEBUG [Thread-7] cdrrep.ServiceParameter (ServiceParameter.java:616) - getFtpLocationChangeFlag()

2012-04-17 10:48:34,075 DEBUG [Thread-7] cdrrep.CDRSender (CDRSender.java:196) - 32 folders found under /var/log/active/cm/cdr_repository/destination1

2012-04-17 10:48:34,077 DEBUG [Thread-7] cdrrep.CDRSender (CDRSender.java:223) - no files found under /var/log/active/cm/cdr_repository/destination1

2012-04-17 10:48:36,954 DEBUG [Thread-6] cdrrep.FileMonitor (FileMonitor.java:113) - FileMonitor wakes up

2012-04-17 10:48:36,954 DEBUG [Thread-6] cdrrep.FileMonitor (FileMonitor.java:120) - No new file found

2012-04-17 10:48:37,782 DEBUG [main] cdrrep.CDRRepClass (CDRRepClass.java:190) - Check for the Publisher change flag status and also demoteLater flag

2012-04-17 10:48:37,782 DEBUG [main] cdrrep.CDRRepClass (CDRRepClass.java:214) - We have to be in loop to check for any publisher demotion

2012-04-17 10:48:34,074 DEBUG [Thread-7] cdrrep.CDRSender (CDRSender.java:125) - destination 1 is active

2012-04-17 10:48:34,074 DEBUG [Thread-7] cdrrep.ServiceParameter (ServiceParameter.java:616) - getFtpLocationChangeFlag()

2012-04-17 10:48:34,075 DEBUG [Thread-7] cdrrep.CDRSender (CDRSender.java:196) - 32 folders found under /var/log/active/cm/cdr_repository/destination1

2012-04-17 10:48:34,077 DEBUG [Thread-7] cdrrep.CDRSender (CDRSender.java:223) - no files found under /var/log/active/cm/cdr_repository/destination1

2012-04-17 10:48:36,954 DEBUG [Thread-6] cdrrep.FileMonitor (FileMonitor.java:113) - FileMonitor wakes up

2012-04-17 10:48:36,954 DEBUG [Thread-6] cdrrep.FileMonitor (FileMonitor.java:120) - No new file found

2012-04-17 10:48:37,782 DEBUG [main] cdrrep.CDRRepClass (CDRRepClass.java:190) - Check for the Publisher change flag status and also demoteLater flag

2012-04-17 10:48:37,782 DEBUG [main] cdrrep.CDRRepClass (CDRRepClass.java:214) - We have to be in loop to check for any publisher demotion

[David Vasquez]

Had the same exact problem and fixed it by restarting the following CDR services via Cisco Unified Serviceability>Tools>Control Center-Network Services:

Cisco CDR Repository Manager

Cisco CDR Agent

Cisco CAR Scheduler

Then deleted current Billing Application Server and recreated with the same parameters. The Billing Application Server can be found in Cisco Unified Serviceability>Tools>CDR Management. The "No files found for transfer" error message was replaced with the actual CDR/CMR files that started to flow in to my Call Processing Application.

Hope that works for you also.