Sending Billing Records; Xml Interface - Nomadix Universal subscriber gateway User Manual

U S
NIVERSAL UBSCRIBER

Sending Billing Records

When there is a message (billing record) in the message queue, the system "wakes up"
and performs the following tasks:
Stores the billing record in the flash
1.
Create an XML packet, based on the new billing record
2.
Send the billing record to the carbon copy server(s)
3.
Transmit the data currently stored in the flash, based on the specified
4.
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 USG™ 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 USG 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.
The XML string built from the billing mirror record is in the following format:
USG to External Server:
<USG RMTLOG_COMMAND="ADD_REC">
<REC_NUM>
<USG_ID>
<PROPERTY_ID>
<DATE>
<TIME>
<ROOM_NUM>
<AMOUNT>
<TRANS_TYPE>
<SIGNATURE>
</USG>
Quick Reference Guide
G ™
ATEWAY
max 5 characters
max 6 characters
max 64 characters
max 10 characters
max 8 characters
max 20 characters
max 10 characters
max 5 characters
max 16 characters
</REC_NUM>
</USG_ID>
</PROPERTY_ID>
</DATE>
</TIME>
</ROOM_NUM>
</AMOUNT>
</TRANS_TYPE>
</SIGNATURE>
217