Cisco Systems OL-1089-11 Redundant Cisco MGC Configuration, FTP Interface, Generic Interface

Chapter 1 Billing Interfaces

Redundant Cisco MGC Configuration

•File Transfer Protocol (FTP) interface

•Generic interface

FTP Interface

The FTP interface allows the user to FTP the CDR files from the spool directory. This interface supports users who own a mediation system or data collocation system. Users can process the CDR files on a separate system.

The Cisco MGC runs on Solaris UNIX that provides the standard file transfer capability (FTP). The Cisco MGC can be configured so other systems can download the CDR files from the spool directory. The FTP download can be restricted by establishing user privileges.

The data collector and mediation systems can use this interface by periodically downloading the files. The CDR files provide a sequence number and the timestamp of the file creation. The data collection system or the mediation system can use this information to determine the desired file to download.

The Cisco MGC has several configuration parameters to write the CDR file. The following are the configuration parameters:

•The prefix in the file name (CDR_YYYYMMDDHHMMSS_SeqNo) where SeqNo is in the format (000001 to 999999)

•Spool directory

•Frequent creation of the file

The sequence number provides an audit capability to the data collection system or mediation software. The sequence number is unique and ranges from 1 to 999999. If the system fails or restarts, it uses the next sequence number (last sequence number + 1). When the sequence number reaches 999999, it then restarts at 1.

Generic Interface

The Cisco MGC defines a generic or flexible billing interface. This is an internal interface between the call processing module and the CDR dumper in Cisco MGC. Users cannot modify this interface.

This interface provides a CDB data stream for the CDR dumper. The generic interface is based on the flexible CDB record layout. The record layout uses a tag, length, and value (TLV) encoding mechanism. The detail messages (that is, CDBs) are explained later in this document.

Redundant Cisco MGC Configuration

In a redundant Cisco MGC configuration, the active Cisco MGC creates checkpoint records to synchronize it with the standby Cisco MGC. The standby Cisco MGC creates call objects with appropriate states to allow continued call processing after switchover occurs. When the standby Cisco MGC becomes active, it starts synchronizing with End Offices (circuit audit). Another aspect of the architecture is that the Cisco 2600s buffer messages while failover occurs.

Billing under a redundant configuration is basically limited to the following: The active Cisco MGC generates the CDBs and the standby Cisco MGC does not. When failover occurs, the now active Cisco MGC generates the CDBs.

Cisco Media Gateway Controller Software Release 9 Billing Interface Guide

1-20 OL-1089-11