
A
CCESS
G
ATEWAY
286
Quick Reference Guide
Mirroring Billing Records
Multiple Access Gateway units can send copies of credit card 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 credit card 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 286
“XML Interface” on page 287
Establishing Billing Records “Mirroring” {Bill Record Mirroring}
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.
Summary of Contents for Access Gateways
Page 1: ......
Page 5: ...ACCESS GATEWAY...
Page 6: ...This page intentionally left blank ACCESS GATEWAY...
Page 36: ...ACCESS GATEWAY 24 Introduction...
Page 62: ...ACCESS GATEWAY 50 Installing the Access Gateway...
Page 136: ...ACCESS GATEWAY 124 System Administration...
Page 156: ...ACCESS GATEWAY 144 System Administration The Network Interfaces screen appears...
Page 250: ...ACCESS GATEWAY 238 The Subscriber Interface...
Page 302: ...ACCESS GATEWAY 290 Quick Reference Guide...
Page 308: ...This page intentionally left blank ACCESS GATEWAY 296 Troubleshooting...
Page 310: ...This page intentionally left blank ACCESS GATEWAY 298...
Page 330: ...ACCESS GATEWAY 318...