User`s guide

C-2
ESCALA T610 and PL 600T User’s Guide
Configuration File Selection
1. Does your modem respond to the extended command set (prefixed with &)?
If yes, go to step 3 below.
If no, continue with step 2 below.
2. Does your modem respond to:
a. ATZ reset command, or
b. ATZn reset commands, where n can be 0, 1, etc.?
If ATZ, configuration file modem_z.cfg is recommended.
If ATZn, configuration file modem_z0.cfg is recommended.
Go to step 5 below.
3. Does your modem command set include a test for V.42 error correction at the remote
modem (often called ”Auto–Reliable Mode”)?
If yes, this test must be disabled. Sample configuration files
/usr/share/modem_m0.cfg or /usr/share/modem_m1.cfg can be used as
models to help you create a file for your particular modem. See ”Customizing the Modem
Configuration Files” on page C-3. Go to step 5.
If no, go to step 4 below.
4. Does your modem respond to:
a. AT&F reset command, or
b. AT&Fn reset commands, where n can be 0, 1, etc.?
If AT&F, configuration file modem_f.cfg is recommended.
If AT&Fn, configuration file modem_f0.cfg or modem_f1.cfg is recommended,
depending on which provides the hardware flow control profile.
5. You have completed selection of the configuration file.
If your modem configuration selection is not available in the Service Processor Modem
Configuration Menu, you must access it through the Configure Remote Maintenance
Policy Service Aid.
If you find it necessary to adjust any of these configuration files, use the manual provided
with your modem to accomplish that task. It is recommended you select settings that
enable hardware flow control and respond to DTR.
Note: Some older modems do not respond to the commands X0 or &R1. You should edit
out these commands from the modem configuration file if yours is such a modem.
See your modem manual for more information.
Some modems are not designed for the paging function. Although they can be used for
paging, they return an error message when they do not get the expected response from
another modem. Therefore, even though the paging was successful, the error message
causes the service processor to retry, continuing to place pager calls for the number of
retries specified in the Call–Out Policy Setup Menu. These retries result in redundant pages.