20 Configuring PAD/ATPAD Ports
PAD Port Configuration
PAD Port Configuration for Autocalling
Introduction
You must configure several parameters within the PAD port record specifically for
autocalling.
• Call Control (set to AUTO or AUTC)
• Autocall Mnemonic (this must be defined in the Mnemonic Table)
• Autocall Timeout (sec)
• Maximum Number of Autocall Attempts
Initiating an
AutoCall
An autocall is initiated in one of two ways.
a)
The terminal connects to the port (Call Control = AUTO and Connection Type
is not SIMP). If the call attempt fails, then the PAD initiates another call after
a time specified in the parameter Autocall Timeout. The parameter Number of
Autocall Tries specifies the number of times the PAD tries to make a
connection. The PAD then stops the process until the EIA input signals are
lowered and then raised.
b)
A call is initiated when the terminal connects to the port and you press
<CR>
(Call Control = AUTC).
If the call attempt fails, you must reenter
<CR>
before
the PAD can attempt another call.
Mnemonic
Addressing
You can configure a port for autocalling to have the call automatically placed at
power up and routed with a mnemonic. This capability is useful when you are
limited to a single host application and are always calling the same address.
Autocalling uses the PathBuilder S200 series switch mnemonic addressing function.
As with normal mnemonic addressing:
• A Mnemonic Table entry must have a corresponding Route Selection Table
entry.
• In addition, the port that is initiating the call must be configured for
Autocalling. This is done by configuring the parameter Call Control (in the
Port Record) to either AUTO or AUTC.
- AUTO specifies that the call is attempted when the EIA handshake is
complete. When Connection Type=SIMP, autocalls are made on power up
or port boot.
- AUTC specifies that the call is attempted when the EIA handshake is
complete and a
<CR>
is entered.
