Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
3396
Views
0
Helpful
4
Replies

CUCM 7.0 and CDR Billing Server

Kenneth.Nicaise
Level 1
Level 1

‎12-18-2009 09:03 AM - edited ‎03-19-2019 12:10 AM

Hi guys, I have a CUCM 7.0 environment set up where I had a CDR Billing Application Server configured and working through a SFTP connection.  Yesterday there were issues with the Billing Application Server that required a reboot and when the system came back online CDR data files were not being immediately sent to the server so my support person deleted the configuration for the Billing Application Server Parameters on the CDR Management screen in CUCM and re-added it back in with the same configuration.  However, CDR data is still not being sent to the Billing Application Server.

I have confirmed that the SFTP connection to the Billing Application Server is functional by attempting to connect to it from a different source and transfering a file.

RTMT shows the following log entries from around the time that this issue started:

2009-12-17 10:33:25,808 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-17 10:33:27,171 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-17 10:33:30,320 INFO  [Thread-7] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 1
2009-12-17 10:33:31,815 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-17 10:33:33,180 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-17 10:33:34,307 INFO  [ConnectionPoolCleaner] dbl.ConnectionPool (ConnectionPool.java:162) - There are 3 entries in the connection pool
2009-12-17 10:33:34,307 INFO  [ConnectionPoolCleaner] dbl.ConnectionPool (ConnectionPool.java:167) - Auditing connections for pool entry <dblog4j,jdbcurl2>
2009-12-17 10:33:34,308 INFO  [ConnectionPoolCleaner] dbl.ConnectionPool$ConnectionPoolEntry (ConnectionPool.java:441) - There are no available connections in <com.cisco.ccm.dbl.ConnectionPool$ConnectionPoolEntry@1901437>
2009-12-17 10:33:34,308 INFO  [ConnectionPoolCleaner] dbl.ConnectionPool$ConnectionPoolEntry (ConnectionPool.java:448) - There are no used connections in <com.cisco.ccm.dbl.ConnectionPool$ConnectionPoolEntry@1901437>
2009-12-17 10:33:34,308 INFO  [ConnectionPoolCleaner] dbl.ConnectionPool (ConnectionPool.java:167) - Auditing connections for pool entry <dblog4j,jdbcurl>
2009-12-17 10:33:34,308 INFO  [ConnectionPoolCleaner] dbl.ConnectionPool$ConnectionPoolEntry (ConnectionPool.java:441) - There are no available connections in <com.cisco.ccm.dbl.ConnectionPool$ConnectionPoolEntry@1f6226>
2009-12-17 10:33:34,308 INFO  [ConnectionPoolCleaner] dbl.ConnectionPool$ConnectionPoolEntry (ConnectionPool.java:448) - There are no used connections in <com.cisco.ccm.dbl.ConnectionPool$ConnectionPoolEntry@1f6226>
2009-12-17 10:33:34,309 INFO  [ConnectionPoolCleaner] dbl.ConnectionPool (ConnectionPool.java:167) - Auditing connections for pool entry <dbcdrrep,jdbcurl2>
2009-12-17 10:33:34,309 INFO  [ConnectionPoolCleaner] dbl.ConnectionPool$ConnectionPoolEntry (ConnectionPool.java:441) - There are no available connections in <com.cisco.ccm.dbl.ConnectionPool$ConnectionPoolEntry@64ea66>
2009-12-17 10:33:34,309 INFO  [ConnectionPoolCleaner] dbl.ConnectionPool$ConnectionPoolEntry (ConnectionPool.java:448) - There are no used connections in <com.cisco.ccm.dbl.ConnectionPool$ConnectionPoolEntry@64ea66>
2009-12-17 10:33:36,326 INFO  [Thread-7] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 1
2009-12-17 10:33:37,821 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-17 10:33:39,187 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-17 10:33:42,333 INFO  [Thread-7] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 1
2009-12-17 10:33:43,311 INFO  [Thread-6] cdrrep.FileMonitor (FileMonitor.java:131) - 1 file(s) found under /var/log/active/cm/cdr_repository/tmp
2009-12-17 10:33:43,313 INFO  [Thread-6] cdrrep.FileMonitor (FileMonitor.java:260) - Processed file: /var/log/active/cm/cdr_repository/tmp/cdr_IL106VOX50-Cluster_03_200912171633_10683
2009-12-17 10:33:43,830 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-17 10:33:45,193 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-17 10:33:48,340 INFO  [Thread-7] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 1
2009-12-17 10:33:49,837 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-17 10:33:51,200 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-17 10:33:55,844 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-17 10:33:57,207 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-17 10:34:01,849 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-17 10:34:03,214 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-17 10:34:07,856 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-17 10:34:09,220 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-17 10:34:13,321 INFO  [Thread-6] cdrrep.FileMonitor (FileMonitor.java:131) - 1 file(s) found under /var/log/active/cm/cdr_repository/tmp
2009-12-17 10:34:13,323 INFO  [Thread-6] cdrrep.FileMonitor (FileMonitor.java:260) - Processed file: /var/log/active/cm/cdr_repository/tmp/cdr_IL106VOX50-Cluster_02_200912171634_7388
2009-12-17 10:34:13,863 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2

And today, this is all that it shows:

2009-12-18 09:29:15,786 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-18 09:29:15,841 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-18 09:29:21,796 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-18 09:29:21,848 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-18 09:29:27,803 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-18 09:29:27,858 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-18 09:29:33,809 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-18 09:29:33,864 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-18 09:29:39,816 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-18 09:29:39,871 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-18 09:29:45,826 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-18 09:29:45,879 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-18 09:29:51,833 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3
2009-12-18 09:29:51,886 INFO  [Thread-8] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 2
2009-12-18 09:29:57,840 INFO  [Thread-9] cdrrep.CDRSender (CDRSender.java:103) - CDRSender wakes up for destination 3

I noticed that it's no longer attempting to connect to "Destination 1" which is my Billing Application Server.

Any idea how to clear this up?

Regards,,,

Labels:
0 Helpful
4 Replies 4

htluo
Level 9
Level 9

‎12-18-2009 09:25 AM

Have you tried to restart the "CDR Repository Manager" service on CUCM?

Could you set the trace level to "debug".  Restart Repository Manager and collect traces?

Thanks!

Michael

http://htluo.blogspot.com

0 Helpful

Kenneth.Nicaise
Level 1
Level 1
In response to htluo

‎12-18-2009 10:05 AM

Michael, that did it thanks.

I deleted the Billing Application Server Paramaters then restarted the "CDR Repository Manager" service. Then re-entered the Billing Application Server parameters and everything appear to be working again.

Much appreciated......

0 Helpful

prakashar
Level 1
Level 1
In response to Kenneth.Nicaise

‎03-26-2013 04:46 AM

Hi,

CUCM has been working for 1 month and recently we did a billing server integration. The CDR that is available on billing server is post the date of "billing server integration" and any record prior to that date is not being fetched. Is that the way it behaves

0 Helpful

Jaime Valencia
Cisco Employee
Cisco Employee
In response to prakashar

‎03-26-2013 08:34 AM

That's WAD, just as when you enable CDR, you cannot expect data to be generated/sent before you configured the feature.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate
0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents