Specifications

147
TAP Outdial
often “&D0” to cause the modem to ignore the DTR line. You want to use “&D2” to
enable the DTR. This causes the modem to hang up and enter the command state.
Note that the command mode escape sequence can be disabled by setting S2=128, or any
value between 128 and 255. For safety the escape sequence should not be disabled, putting
“S2=43” in an initialization string will enable the standard escape sequence.
If possible, the modem should be configured to not auto-answer incoming calls. For most
Hayes compatible modems this can be done by including “S0=0” in one of the modem
initialization strings. Some modems may have a switch or front panel programming option
to disable auto-answer, these controls may override the “S0=” setting.
Many newer modems support various forms of data compression and error detection.
These modes of operation can interfere with TAP, in particular with the log-in stage, and
so should be disabled. Exactly how this is done will vary from modem to modem. On
some modems “&Q0” within an AT string will disable all error control, special buffering,
and data compression. When checking for such features and commands in the modem's
documentation, you should look for the keywords “MNP”, “V.42”, and “compression”.
Again, a few modems that have front panel programming may have settings that override
the “AT” based commands.
OPARAM CDS Settings
The outdial TAP card has two general classes of option parameters. One set applies to the
programming of the modem, or other interface device, itself. These parameters relate to
the control of the modem itself.
The second set of parameters is used to determine the behavior for a given TAP
destination. There is one set of these parameters per active destination. Some of the
parameters must be filled in for each destination, although many parameters will work
correctly with the default values.
Refer to TAP Outdial OPARAM Codes on page 251, for details of
oparam.cds
programming.
NETWORK.CUS Settings
Besides the oparam.cds settings there must be a way to map from the subscribers'
network destinations, set in ZbaseW, to the outdial TAP destination numbers. This is done
on the paging terminal, using entries in the
network.cus file.
For each unique network destination used in ZbaseW, there should be an “
Outbound”
entry in the
network.cus file. In order to send a page to the outdial TAP card an
“
Outbound” entry should include an outdial TAP destination specification in its list of
actual destinations. To specify a TAP destination use a string of the form “
TAP##D”,
where “
##” is the actual outdial TAP destination number. Currently valid TAP destination
numbers are between 0 and 15 (decimal). The number may be one or two digits long; a
leading zero will be accepted but is not required.