A Call Detail Record (CDR) is a collection of information for each call that is processed by Lotus Sametime Unified Telephony. More complex call scenarios such as transfer, conference, networking, and other Lotus Sametime Unified Telephony features may produce multiple CDRs.
Lotus Sametime Unified Telephony generates and maintains CDRs for usage collection and billing purposes. The UCE maintains CDR information in the active call context, which can follow the call from process to process and, in a redundant system, from node to node.
If you require detailed information on how CDRs are configured and formatted, please contact IBM Support.
Track bill-back accounting (for extension, department, division, or company).
Track and identify special common carrier services (track telephone numbers and call duration to specific locations).
Track client or user identification (track account numbers, or personal identification numbers (PINs)).
Track system traffic for analysis (call patterns, trunk usage, and other routing information).
Track and identify call abuse (Track and identify call abuse (track 900 numbers, unauthorized long distance calls, and personal calls).
Track calls for different states (e.g., answered, unanswered, rejected) and call scenarios (e.g., Transfer, Call Forward, Callback, etc.).
Secure Storage of CDR (Call Detail Record) Password
Passwords for the Lotus Sametime Unified Telephony CLI (Command Line Interface) login are stored encrypted within the Linux OS. Application-level passwords for transferring CDRs (Call Detail Records) from the Telephony Control Server to the billing mediation server are stored via two-way encryption within the Lotus Sametime Unified Telephony database.
Create a CDR (Call Detail Record)
At the end of every call, a CDR (Call Detail Record) is generated. However, intermediate CDRs are also generated once every 30 minutes; CDRs also are generated intermittently for long-duration calls, such as those that pass over midnight more than once. The RTP (Real-time Transport Protocol) ticket manager handles the individual CDRs.
CDR (Call Detail Record) Generation
The CDR (Call Detail Record) generation feature provides comprehensive call accounting data.
Store CDR (Call Detail Record)
The CDRs (Call Detail Records) are first stored on the local hard drive and are then pushed to or pulled from a billing server (for example, Lotus Sametime Unified Telephony Accounting Management or third party billing application) which post-processes the CDRs.
Lotus Sametime Unified Telephony uses a FTP interface to the billing system.
Billing Server Interface
The interface between the Lotus Sametime Unified Telephony and the billing server uses FTP to transfer CDR (Call Detail Record) information. The Lotus Sametime Unified Telephony supports SFTP protection for CDR delivery using a pull from the billing server.
CDR (Call Detail Record) Processing
Each CDR (Call Detail Record) is a RTP (Real-time Transport Protocol) ticket. The CDR client uses the RTP ticket writer to write the ticket (CDR) in a ticket file on local disk (/software/twlocal) in binary format. Ticket files are node-specific; their file name includes the node ID, which means they are unique cluster-wide.
Monitoring CDR (Call Detail Record) Faults
The CDR (Call Detail Record) Fault Management commands enable the user to obtain lists of events related to CDR faults, based upon differing start times, which are consistent with RTP (Real-time Transport Protocol) “register for events then list callbacks”, but which allow for event filtering within the menu selection itself.
Monitoring CDR (Call Detail Record) Performance
The Lotus Sametime Unified Telephony displays CDR (Call Detail Record) counters to monitor the performance of the CDR generation and collection engine.
Standard CDR (Call Detail Record)
The standard CDR (Call Detail Record) is produced at the end of each call.
Call Forwarding CDR (Call Detail Record)
When calls are forwarded, either via telephone-based or Lotus Sametime Unified Telephony-based forwarding, multiple CDRs (Call Detail Records; standard CDRs and call forwarding CDRs) are generated.
Long Call Duration Record
A Long Call Audit CDR (Call Detail Record) is generated for a call whose duration is longer than two consecutive midnights. The record itself is generated at the 2nd midnight and each midnight thereafter. A Standard CDR is generated when the call is released, with field no. 4 containing the total overall call duration.
Intermediate Long Duration Records
The intermediate long duration CDR (Call Detail Record) feature provides the capability to generate intermediate CDRs containing full call information after an administrable time period elapses.
When a call is queued, e.g. in hunt group scenarios, a Queue CDR (Call Detail Record) is generated in addition to the Standard CDR, which contains info about the time and duration of queuing.
Feature Activation / Deactivation Record
Feature Activation / Deactivation Records are produced when a user activates or deactivates certain call features.
Change of Software Audit Record
A Change of Software Audit Record is generated in situations where software modifications have been made on a particular switch (for example, rolling upgrade not new installations).
The usage reporting feature provides for the generation of CDRs (Call Details Records) for all calls, distinguishing between completed and non-completed calls (ring no answer, busy status).
CDR (Call Detail Record) Handler
The CDR (Call Detail Record) handler manages the internal binary billing files through the RTP (Real-time Transport Protocol) API, then makes them available to a billing server. The CDR handler also converts and formats these internal binary billing files. The completed and formatted billing files can be transferred from the Telephony Control Server through FTP or SFTP, depending on the file transfer method and the capabilities of the billing server.
Determining the Call Direction
The call direction (incoming/outgoing/internal) allows a billing application to determine which calls should be charged, for example, outgoing calls to the PSTN (Public Switched Telephone Network). There is no specific field in the CDR (Call Detail Record) for the call direction as this can be determined by the billing application based on other information provided in the CDRs.
Filtering the CDR (Call Detail Records) with the GID (Global Call ID)
Lotus Sametime Unified Telephony provides the GID (Global Call ID) in the CDR (Call Detail Record), which the billing application can use to filter CDRs that belong to the same call.
CDR (Call Detail Record) for BG (Business Group) Features
CDR (Call Detail Record) handling for BG (Business Group) features.
CDR (Call Detail Record) for Group Features
CDR (Call Detail Record) handling for Group features.
CDR (Call Detail Record) for Keyset Telephone User Features
CDR (Call Detail Record) handling for Keyset Telephone User features.
CDR (Call Detail Record) for QSIG (Q-Signaling) Tunneling Features
CDR (Call Detail Record) for QSIG tunneling features applies only between Lotus Sametime Unified Telephony and the HiPath 4000. It does not function between Lotus Sametime Unified Telephony and the HiPath 3000, or between Lotus Sametime Unified Telephony and and other vendors' QSIG PBX.
CDR (Call Detail Record) for Routing and Translation Features
CDR (Call Detail Record) handling for Routing and Translation features.
CDR (Call Detail Record) for User Features
CDR (Call Detail Record) recording offer special handling for user features that reside in Lotus Sametime Unified Telephony. Examples of such features are calling identity delivery and suppression features, abbreviated dialing features, redial and call return features, and display features.
BF (Billing Files)
Lotus Sametime Unified Telephony outputs ASCII CDRs (Call Data Records) to BFs (Billing Files) that use the formatting and file naming conventions described in the following sections.
CDR (Call Detail Record) Decoder Tool
The CDR (Call Detail Record) decoder tool (cdrdecode) which can be run from the command line interface of Lotus Sametime Unified Telephony, takes as input a billing file and outputs the CDRs contained in the file in a readable format, including the field names and their decoded values.
Assistant SIP Endpoints Export to Lotus Sametime Unified Telephony Accounting Management
For Lotus Sametime Unified Telephony AM (Accounting Management) to be able to correctly do call accounting AM needs to have knowledge of all the SIP endpoints (e.g. Lotus Sametime Unified Telephony, gateways) that are configured in the network and how they are interconnected. With this feature Lotus Sametime Unified Telephony Assistant generates the required information in files that Lotus Sametime Unified Telephony AM /COL will import and automatically perform the necessary configuration.