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.
BFs are output from the Lotus Sametime Unified Telephony in an ASCII comma delimited format. The Record Type (field no. 2) defines the basic structure for CDRs. The layout for each type is presented in this section.
By default, a BF is closed and made available for delivery to an external billing server when one of the following occurs:
The number of individual CDRs reaches 2,500 or, Note:
The BF has been open for 5 minutes.
If you require modification to these defaults, please contact the authorized BLS (Back Level Support) for assistance in changing the RTP (Real-time Transport Protocol) parameter controlling this function.
Lotus Sametime Unified Telephony CDRs/BFs use the following filename format:
<System Hostname>-<YYYYMMDDTHHMMSS-/+HHMM><File Sequence Number>.BF
<System Hostname> the name configured in the node.cfg file. This consists of a customer-assigned hostname of up to 14 characters. This supports the use of Telcordia-assigned CLLI (Common Language Location Identifier) codes as switch hostnames for identifying each Lotus Sametime Unified Telephony.
<YYYYMMDDTHHMMSS-/+HHMM> consists of a 20-character date/time stamp, indicating the date and time at which the Lotus Sametime Unified Telephony created the billing file. This time format conforms to the UTC (Universal Time Coordinated) standard.
<File Sequence Number> consists of a six-digit integer that increments with each new file the Lotus Sametime Unified Telephony generates.
Lotus Sametime Unified Telephony CDRs/BFs are formatted with header and trailer information and can contain Call, Audit, and Feature Activation / Deactivation Records.
Table 1 defines the elements that comprise the header and trailer used in Lotus Sametime Unified Telephony BFs. These fields and format must exist inside the ASCII files. All fields must be followed by the “<NL>” character.
Figure 1. Billing File Format
The example below shows a billing file (*.BF) consisting of two records (record 0 and record 1).
DEVICE: Lotus Sametime Unified Telephony
Parent topic: Call Detail Record (CDR)