/mcptransfers to an application billing server. From Release 14 onwards, CDR/CMR files sends upto eight customer billing servers via FTP/SFTP. CDR Management uses the following services: • CDR Agent—This network service transfers the CDR files that the call processing nodes generate from the call processing nodes to the CDR Repository node via SFTP. After the file transfer is completed, the CDR Agent deletes the local CDR file from the call processing node. This service is enabled by default. • CDR Repository Manager—This service must be running on at least one node in the cluster (typically, the publisher node). The CDR Repository Manager maintains copies of the generated CDR and CMR files on the repository node and purges the files after a specified expiration passes, or when the disk usage exceeds the high water mark. If an application billing server is deployed, the CDR Repository Manger initiates an SFTP transfer of the CDR and CMR files to the billing servers. This network service is on by default. • CDR onDemand Server—This feature service must be activagted on the CDR Repository node if you are using an application billing server. This service uses a SOAP/HTTPS-based service, which receives SOAP requests for a particular CDR filename based on a user-specified time interval and returns all files via SFTP that fit the parameters. SFTP File Transfers The CDR Agent checks at 6-second intervals for CDR and CMR files to transfer from call processing nodes to the CDR Repository server via SFTP. After a successful transfer, the local file is deleted from the call processing node. Each delivery failure results in the immediate change of the sleep interval to 1 minute, then says at 1-minute intervals until successful delivery. After the first successful delivery of files, the 6-second interval resumes. If any files remain on call processing nodes without being transferred, they may be deleted by the Cisco Log Partition Monitoring Tool if the disk usage exceeds a configured threshold. For information on the Log Partition Monitoring Tool, see the Cisco Unified Real-Time Monitoring Tool Administration Guide. The CDR Repository Manager checks at 6-second intervals for CDR and CMR files to send to any deployed billing servers. If the billing server does not respond, the system doubles the interval before making another attempt. Each delivery failure results in double the sleep time until 2 minutes, then stays at 2 minutes until successful delivery is reached. After a successful delivery, the 6-second interval resumes. This process continues unless you delete the billing server, or if the files fall outside the preservation window and are deleted. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 9 CDR Analysis and Reporting CDR Management