Table Of Contents
Asynchronous Point of Sale-to-IP Conversion
Prerequisites for Asynchronous Point of Sale-to-IP Conversion
Information About Asynchronous Point of Sale-to-IP Conversion
Asynchronous Point of Sale-to-IP Conversion
How to Configure Asynchronous Point of Sale-to-IP Conversion
Configuring APOS on the Serial Interface
Configuring the Line Interface
Configuration Examples for Asynchronous Point of Sale-to-IP Conversion
Asynchronous Point of Sale-to-IP Conversion
The Asynchronous Point of Sale-to-IP Conversion feature modifies the Cisco IOS implementation of block serial tunnel (BSTUN) to support asynchronous point of sale (APOS) to IP conversion of credit and debit card authorization traffic to a LAN-attached host.
Feature History for the Asynchronous Point of Sale-to-IP Conversion Feature
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Information About Asynchronous Point of Sale-to-IP Conversion
•
How to Configure Asynchronous Point of Sale-to-IP Conversion
•
Configuration Examples for Asynchronous Point of Sale-to-IP Conversion
Prerequisites for Asynchronous Point of Sale-to-IP Conversion
The router always functions as a data circuit-terminating equipment (DCE) device when controlling the connection, regardless of the cabling; therefore, a DCE cable or Data Terminal Equipment (DTE) cable with an external null modem connector is required.
Information About Asynchronous Point of Sale-to-IP Conversion
To configure the Asynchronous Point of Sale-to-IP Conversion feature, you must understand the following concept:
•
Asynchronous Point of Sale-to-IP Conversion
Asynchronous Point of Sale-to-IP Conversion
The APOS protocol utilizes asynchronous communications. The APOS connection to the terminal will always be over an asynchronous leased line. The serial interface controlling the POS device is mapped to the host device by the bstun route (APIP) command. APOS to IP conversion (APIP) supports only active (outbound) activation sequences to the host device specified by the bstun route (APIP) command.
Although the connection between the terminal and the router is a leased line, the terminal believes it is still connected to a modem. The terminal sends Hayes AT messages to the router. In this situation, the peer connection follows the state of the asynchronous dial connection. The tunnel is non-persistent and will only be active during the transaction. For terminals that do not send Hayes AT messages on the leased line, the router can be configured for direct mode. In this situation, the peer connection still follows the state of the asynchronous connection. Because the connection is permanent, the tunnel will be persistent.
Because there is only one POS terminal for each asynchronous line, addressing and polling need not be performed. A basic APOS call flow is conducted as follows:
1.
The terminal sends a Hayes AT initialization string.
2.
The router acknowledges with a numeric okay.
3.
The terminal sends a dial string to the router.
4.
The router processes the dial string and activates the peer connection.
5.
If the peer successfully connects, the router sends a connect message for the appropriate line speed. If the peer does not connect, a "no carrier" or "no dial tone" message is sent.
6.
If the peer connects, the router then sends an ENQ(0x05) message requesting data from the terminal.
7.
The terminal starts the communication session by sending a data request.
8.
The host responds to the terminals data request.
9.
When the terminal has finished sending data, it sends an ACK(0x06) message to the router.
10.
The router ends the session with an EOT(0x04) message.
In direct mode, Hayes AT messages are not sent. The router continuously sends ENQ(0x05) messages requesting any data from the terminal.
How to Configure Asynchronous Point of Sale-to-IP Conversion
The following tasks must be completed to configure APOS:
•
Configuring BSTUN (Required)
•
Configuring APOS on the Serial Interface (Required)
•
Configuring the Line Interface (Required)
Configuring BSTUN
In this task, you configure basic BSTUN.
SUMMARY STEPS
1.
enable
2.
configure
3.
bstun peer-name ip-address
4.
bstun protocol-group group-number apos
5.
bstun remote-peer-keepalive seconds
6.
bstun keepalive-count count
DETAILED STEPS
Configuring APOS on the Serial Interface
In this task, you configure BSTUN and APOS on the serial interface.
SUMMARY STEPS
1.
interface serial number
2.
physical-layer async
3.
no ip address
4.
encapsulation bstun
5.
bstun group number
6.
bstun route all apip ip-address [fport port] [tcp-queue-max size] [header {vo | v1 | v2}]
7.
asp role primary {primary | secondary}
8.
asp dcd always
9.
asp direct
10.
asp enq {disable | delay milliseconds}
11.
asp retries number
12.
asp send ack
13.
asp timer {rsp rsp-time | rx rx-time | host host-time | connect connect-time}
DETAILED STEPS
Configuring the Line Interface
In this task, you configure the line interface to support APOS. The settings configured must match those configured on the POS device.
SUMMARY STEPS
1.
enable
2.
configure
3.
line number
4.
databits {5 | 6 | 7 | 8}
5.
parity {none | even | odd | space | mark}
6.
stopbits {1 | 1.5 | 2}
DETAILED STEPS
Configuration Examples for Asynchronous Point of Sale-to-IP Conversion
This sections provide the following configuration example:
APOS Configuration: Example
The following example shows a complete APOS configuration:
bstun peer-name 10.122.2.10bstun protocol-group 20 aposbstun remote-peer-keepalive 100bstun keepalive-count 5!interface serial 1physical-layer asyncno ip addressencapsulation bstunbstun group 20bstun route all apip 10.122.2.1asp role primaryasp dcd always!line 1databits 7parity evenstopbits 1Additional References
The following section provides references related to APIP.
Related Documents
MIBs
MIBs MIBs Link•
CISCO-BSTUN-MIB
•
CISCO-ASPP-MIB
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
Technical Assistance
Command Reference
The following commands are introduced or modified in the feature or features documented in this module. For information about these commands, see the Cisco IOS Bridging Command Reference at http://www.cisco.com/en/US/docs/ios/bridging/command/reference/br_book.html or the Cisco IOS IBM Networking Command Reference at http://www.cisco.com/en/US/docs/ios/ibm/command/reference/ibm_book.html. For information about all Cisco IOS commands, go to the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or to the Cisco IOS Master Commands List.
•
asp dcd always
•
asp direct
•
asp enq
•
asp retries
•
asp send ack
•
asp timer
•
bstun route all apip
•
debug aspp event
•
debug aspp packet
•
bstun protocol-group
•
show bstun
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.