Nomadix AG 2300, Руководство пользователя, Страница: 272 / 294

A
CCESS
G
ATEWAY
260 Quick Reference Guide
Mirroring Billing Records
Multiple Access Gateway units can send copies of billing records to a number of external servers that have
been previously defined by system administrators. The Access Gateway assumes control of billing
transmissions and saving billing records. By effectively “mirroring” the billing data, the Access Gateway can
send copies of billing records to predefined “carbon copy” servers.
Additionally, if the primary and secondary servers are down, the Access Gateway can store up to 2,000
transaction records. The Access Gateway regularly attempts to connect with the primary and secondary
servers. When a connection is re-established (with either server), the Access Gateway sends the cached
information to the server. Customers can be confident that their billing information is secure and that no
transaction records are lost.
This document describes the process used by the Access Gateway for mirroring billing records, and is
organized into the following sections:

Sending Billing Records on page 260

XML Interface on page 260

Establishing Billing Records “Mirroring” {Bill Record Mirroring} on page 82
Sending Billing Records
When there is a message (billing record) in the message queue, the system “wakes up” and performs the
following tasks:
1. Stores the billing record in the flash
2.
Create an XML packet, based on the new billing record
3. Send the billing record to the carbon copy server(s)
4. Transmit the data currently stored in the flash, based on the specified retransmission method (round-
robin: A-B-A-B, or fail-over: A-A-B-B)
The system stores the billing record in the flash so that the record will not be lost (for example, if the Access
Gateway is powered down during transmission attempts.
Billing records are sent to the carbon copy server(s) only after the records are placed in
the message queue. Carbon copy servers will not receive the records again if a task for
retransmitting to the primary or secondary server needs to be performed.
XML Interface
XML for the External Server
The Access Gateway sends a string of XML commands according to specifications. HTTP headers are added
to the XML packets that are built, as the billing “mirroring” information is sent to the external server in HTTP
compliant XML format. Content-length has also been added to the HTTP post.
The XML string built from the billing mirror record is in the following format:
Access Gateway to External Server:
<USG RMTLOG_COMMAND="ADD_REC">
<REC_NUM>max 4 characters </REC_NUM>
<USG_ID>max 6 characters </USG_ID>
<PROPERTY_ID>max 64 characters</PROPERTY_ID>