Cisco Systems OL-1089-11 manual Tag Values, CDB TLV Record Format

Chapter 1 Billing Interfaces

Billing Capabilities Overview

Figure 1-1 CDB TLV Record Format

Tag

Length

Tag

Length

Value

57859

Sub-TLV messages

The CDB message has both mandatory fields and optional fields. The following fields are mandatory in each CDB message.

•Unique Call ID

•Version

•CDB Timestamp

All other fields in the CDB message are considered optional. The optional fields do not appear in any sort of predefined order. The TLV format allows the application to be insensitive to the order of the message data. For example, in a 1010 Answer CDB message, the Call Reference ID tag (4002) could appear as the first optional field, whereas in another CDB message, such as 1040 Release, the Call Reference ID tag could appear as the last optional field.

Note The mandatory fields exist in each CDB message, with their associated values and locations. The optional fields can have no value. Optional fields with no value are not included in the CDB message, to improve performance.

Tag Values

As shown in Figure 1-2, the tags are divided into categories. The first tag category is assigned to the CDB message ID(s), the second category is assigned to CDB format fields, and the third category is assigned to miscellaneous usage.

Each category is divided into two or more sections. One section is the MGC range, and another section is the customer-definedrange. Customer-defined ranges (for each category) can be used to further process the CDB records as required by the customer.

For example, in Figure 1-2, a Cisco MGC message ID range defined by a customer (1900 through 1999) can be used for generating customer-specific CDB auditing records. The auditing records can be for beginning and ending the CDR file. The field tag range can also use the customer-defined range for the field category (5900 through 5999) to define new fields in the CDB auditing records.

Cisco Media Gateway Controller Software Release 9 Billing Interface Guide

OL-1089-11 1-3