Cisco – Tunnel Async Data
Tunnel Async Data
VER A 7/23/03
As an example, assume that async RS-232 devices are to be connected by leased line modems. Instead, the leased line modems are replaced with Cisco comm servers. Plug the RS-232 devices into async lines on the Cisco comm servers and connect the comm servers via an arbitrary topology IP network. In this sample configuration, one side is the caller and the other side is the called. It is presumed that the caller side is more persistent in its desire to send data.
Assumptions:
The caller side has an IP address of 10.224.8.3 and is using Line 2.
The called side has an IP address of 10.226.x.1 and is using Line 3.
Caller Side
ip host ORDQW 20xx 10.226.x.1 ! ORDQW is just an example, please use city name.
busy-message ORDQW ! ORDQW is just an example, please use city name.
service tcp-keepalives-out
line x ! Whatever Async port you are using.
no motd-banner
no exec-banner
no vacant-message
autocommand telnet ORDQW /stream ! This is have to match the ip host name.
autohangup
no flush-at-activation
no activation-character
escape-character NONE
exec
special-character-bits 8
exec-timeout 0 0
session-timeout 0 o
no modem inout
no autobaud
speed 19200 ! What ever the port speed needs to be.
stopbits 1
flowcontrol NONE
transport input NONE
Called Side
aaa authentication login ORDQW none ! ORDQW is just an example, please use city name.
no banner incoming
service tcp-keepalives-in
line x ! Whatever Async port you are using.
no exec
no exec-banner
no vacant-message
login authentication ORDQW ! Have to be the same as the login name above
modem DTR-active
no autobaud
speed x ! What ever the port speed needs to be.
stopbits 1
flowcontrol NONE
transport input telnet
