TCP to X.25 POS Gateway Appliance for APACS, ISO 8583 and many custom ePOS Transactions
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Typical network configuration using the FarLinX TCP-X25 POS Gateway |
![]() |
The Gateway provides connection establishment and data packetisation services for APACS, ISO 8583, HGEPOS and other systems to allow POS terminals operating over TCP/IP to interface to X.25 connected hosts, flexible general purpose options for mapping and routing TCP to X.25 data are also provided.
A special configuration option is available to support connection to CTL (Card Tech Ltd) Host equipment where the POS terminals are connected by X.25 and the connection to the verifying host is by TCP/IP.
The Gateway provides routing facilities to select the appropriate Host from those available and maintains X.25 sessions to the Host as required. An X.25 session is established for the POS transaction when the TCP session for a transaction is established.
The Gateway can operate in conjunction with an IP dial-up platform device supporting autocommand telnet this permits support for remote POS terminals connected via PSTN or ISDN connections.
APACS connections over X.25 can operate in 2 different ways, TPAD-HOST
Mode and T/T-TPAD Mode. The FarLinX
TCP-X25 POS
Gateway supports both modes and also transparent conversion between the
modes.
TPAD-HOST Mode
APACS messages are sent without a LRC in TPAD-HOST mode, no APACS control frames eg ACK, DLE EOT are required. The transaction consists of a pair of APACS messages. An X.25 virtual circuit is established by the Gateway at the start of each transaction and cleared by the Gateway at the end of the transaction.
T/T-TPAD Mode
APACS messages are sent complete with the LRC. APACS control frames are used to regulate the flow and termination of the APACS message, each message being acknowledged with an ACK frame. An X.25 virtual circuit is established by the Gateway at the start of each transaction and cleared by the Gateway at the end of the transaction.HPAD Conversion
APACS messages on the Host side are handled complete with LRC and control frames to acknowledge and regulate the flow. The messages are extracted and handled on the POS Terminal side as simple messages without the LRC and transmitted without the use of control frames. This provides conversion from TPAD-Host mode on the terminal side to T/T-TPAD mode on the Host side.TPAD Conversion
APACS messages on the Terminal side are handled complete with LRC and control frames to acknowledge and regulate the flow. The messages are extracted and handled on the Host side as simple messages without the LRC and transmitted without the use of control frames. This provides conversion from T/T-TPAD mode on the terminal side to TPAD-Host mode on the Host side.
The POS Gateway can support a wide range of TCP to X.25 data translation
and connection functions, including fixed and dynamic
routing, RFC1006 support and Cisco RBP compatibility. The different modes
of operation can be configured on a per connection basis.
| |
The FarLinX TCP-X25 POS Gateway can be deployed in a wide variety of ways to achieve the level of resilience required by the application. The level will depend on the value of the data traffic and the acceptable degree of user intervention required to rectify any problem. The aim with resilience is to remove single points of failure. Resilient configurations using more than one POS Gateway also allow improved performance by sharing the traffic load between several machines.
Network Line Redundancy
To achieve network line redundancy, a single FarLinX TCP-X25 POS Gateway may operate with two or more X.25 lines. It can route data over any active line connected to the Gateway so that if one line goes out of operation then the other lines continue to be used automatically.
Gateway Redundancy and Load Balancing
For fully resilient operation, two (or more) FarLinX TCP-X25 POS Gateways may be deployed. They can be either configured for simple failover from a primary to a backup machine or for full load balanced operation. In Network Load Balancing (NLB) mode both failover and load balancing of the ePOS transactions are provided thus ensuring there is no single point of failure and that there is no performance bottleneck.
The built in POS Gateway Supervisor checks the state of the X.25 network lines and as these change state between fully operational and faulty it automatically enables/disables the unit from the pool of FarLinX TCP-X25 POS Gateway's, thus managing the availability of that particular POS Gateway machine. Key events such as the loss of an X.25 line are recorded on a daily rotating event log.
| |
The FarLinX TCP-X25 POS Gateway easily handles very high transaction loads. Support for large numbers of X.25 lines and multiple Gateways provides enormous scalable expansion capability and resiliency. The main performance and expansion features of the Gateway are:
The FarLinX TCP-X25 POS Gateway is typically used to route connections to a single acquiring host. It can, however, support routes to 2,000 different X.25 hosts. Similarly, when using the called X.25 address as the routing key, incoming X.25 calls can be routed to thousands of different TCP/IP hosts.
When making connections to the X.25 network, the POS Gateway has the capability of mapping the source IP address to a calling X.25 address, thus allowing the destination X.25 host to identify the connection source uniquely.
The Dynamic routing option allows the X.25 address (NUA) and call parameters to be set by the remote application at the time each X.25 connection is established. X.25 packetisation information is passed to the application.
| |
Technical
Specifications |
|||
| Product Name | FarLinX TCP-X25 POS Gateway-10 | FarLinX TCP-X25 POS Gateway-20 | FarLinX TCP-X25 POS Gateway-MAX |
| Product code | FL2110 | FL2120 | FL2140 |
| Maximum simultaneous transactions | 10 | 20 | 4,000 (2,000 on a single X.25 line) |
| X.25 Line count | 1 line * | 2 lines * | 4 lines * |
| * Upgradeable with an additional 4 X.25 lines by ordering FL2004 | |||
Gateway Features |
|||
| POS transaction protocols | APACS 30, APACS 40, APACS 70, ISO 8583 (various options), HGEPOS | ||
| APACS specific protocol variants handled | TPAD-HOST - just APACS messages, no
LRC |
||
Miscellaneous data options |
Parity conversion for the X.25 datastream CTL (Card Tech Ltd) Online message type Cisco RBP message header format RFC1006 Minimal PAD for operation |
||
| TCP to X.25 translation modes | Yes, Fixed and Dynamic Routing (compatible
with the DRPD module on the FarSync TCP-X25 GP Gateway). Mode list:
|
||
| Transactions per second | Up to 500 per second on each POS Gateway | ||
| Maximum simultaneous transactions | Up to 2,000 on each X.25 line to total of 4,000 across all lines (MAX version) | ||
| Resilient configuration | Yes, from 2 to 32 Gateways | ||
| Load balancing | Yes, from 2 to 32 Gateways | ||
| Logging key events | Events such as the connections being established and dropped, X.25 call fails, X.25 line down, and X.25 lineup are logged on a daily rotating log file | ||
Network connectors |
Connection cables are available with RS232C
(V.24), X.21, V.35 and RS530 connectors. The cables are ordered separately, see the Cable Table. |
||
| Types of X.25 connection | X.25 network, leased line, X.25 dialup | ||
| X.25 feature summary | Speeds up to 8 Mbits/s |
||
| LAN | 3 10/100 BaseT LAN ports, RJ45. Each port is for connection to a separate Network | ||
| Approvals | CE, FCC part 15 class A, UL | ||
| RoHS Compliance | See the RoHS News item | ||
| Power Requirements | Input voltage range: 100v to 240v Typical 60w (0.25amps at 230v), Peak 120w (0.5amps at 230v) |
||
| Physical | Dimensions: metric: 429(W) x 282(D)
x 44(H) mm, imperial: 16.89”(W) x 11.1”(D) x 1.73"(H)
|
||
Product Name |
Description |
Product Code |
| UCR1 | Single RS232C (V.24, X.21bis) cable with male 25 pin D type (DB25) connector, 1.5 metres | FS6061 |
| UCX1 | Single X.21 (V.11, RS422) cable with male 15 pin D type (DB15) connector, 1.5 metres | FS6062 |
| UCV1 | Single V.35 cable with standard MRAC-34 (brick) male connector, 1.5 metres | FS6063 |
| U530 | Single RS530 cable with male 25 pin D type (DB25) connector, 1.5 metres | FS6064 |
| |
|
Information in this document is subject to change without notice.
Other products and companies referred to herein are trademarks or registered
trademarks of their respective companies or mark holders.
Last updated:
18-Mar-2009