We are installing a standalone CME which will log CDR to an external CADS server (phoneware product) at customer central site.
In case of WAN link failure, I suppose we can save the CDR somewhere local (eg. syslog console or router buffer) during the outage.
The question is, when the WAN link recovers, how do we upload the CDR from local syslog / buffer to the CADS server at central site?
I have queried with phoneware, I was advised that it would be up to cisco CME config. (The CADS central server is in a permanent passive open state waiting for remote site (CME in this case) to poll and upload CDR files.)
If there is no automated uploading of missing parts when link recovers, will i be able to mannually upload the missing parts to central server when WAN link is normalised, and what is the best way of doing that?
I guess this question also applies to our other two sites which will be implemented with Cisco SRSTs.
Customer needs to have a complete CDR report in the central database at the end of the day.
The centralized CDR collector (CADS server) uses Secure FTP. It is "passive", it just sits there to wait for Cisco CME or CallManager Cluster to initiate FTP sessions and send out call records to it.
When a site goes into SRST or the CME site becomes isolated, Phoneware advised that it would be completely up to Cisco SRST / CME configuration to upload the missing parts to the central server, as the FTP sessions are always initiated from remote client sites.
I can image you can have a scheduled script (now it's possible to have TCL scripts natively residing on the router) that does that. Of course all the login to decide what to send and in which cases has to be in the script, again CME does not know anything about that.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...