![]() INFO cdrrep.CDRSender (CDRSender.java:105) – CDRSender wakes up for destination 2 INFO cdrrep.CDRSender (CDRSender.java:345) – CDRREP before sending the file: JVM status: INFO cdrrep.FtpManager (FtpManager.java:78) – FtpManager constructor 0: Establish server connection to host successfully! I’ve just pulled a new set of CCM traces from the Cluster, and this time I can see the files being sent by FTP see below: I gave it a quick glance and made a note of a few things. – whether the Repository Manager was unable to transfer the files to the Billing ServerĪnother link I stumbled across, though it didn’t have much info that related to the issue was Troubleshooting CallManager 6.x 7.x CDR / CMR & how to fix error 10021. – if the CDR files have been processed by the Publisher – whether the CDR Agent is moving files from the Subs to the Pub Other important info included CLI commands that would let you know the following: The link Troubleshooting CUCM 5.x / 6.x CDR Analysis and Reporting “Data Missing” issues did a good job in explaining a few things. I did a bit of research and found a great link with some very useful info that confirmed what I was thinking:Ĭisco CDR Repository Manager should be running on the First Node ONLY (the Publisher)Ĭisco CAR Scheduler should be running on the First Node ONLY (the Publisher)Ĭisco CDR Agent should be running on all the call processing nodes The information in the traces didn’t show any attempts to send the CDR files via FTP ![]() In order to understand better, I turned to the Cisco Voice Engineer’s best friend –> CallManager Tracee (I actually hate it sometimes :-)!!!!) Some of the services running on the Subscribers were meant to run on the Publisher only. – Cisco CDR Repository Manager was running on all the nodesĪt first glance, this didn’t look right. – Cisco CDR Agent was running on all the nodes – The two other node (Subscribers) were running Cisco CAR Scheduler – Cisco CAR Scheduler wasn’t running on the Publisher, so I started this immediately The customer was recently upgraded from CallManager v6 to v7. The customer reported that they stopped receiving CDRs on the Billing Server right after a Call Manager upgrade. So I asked the customer the usual questions like “when was the last time you got any CDRs via FTP”, “has there been any maintenance”. – issues with the Billing Server (permissions, home folder, wrong path e.t.c) – issues with communication between the CallManager Cluster and the Billing Server (maybe even a firewall) – issues with the CallManager Cluster (cluster consists of 3 nodes) I mapped out three possible issues that could have suddenly caused this: The customer has a remote Billing Server and the files were being sent to the server by FTP. ![]() The customer reported that they haven’t been receiving any CDR from the CallManager Cluster. A few days ago, one of our customers raised an issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |