mdmcfgcheck(1M)

mdmcfgcheck -- checks modem configuration file

Synopsis

mdmcfgcheck [-t timeout] [-f] [/dev/devicename] modem_cfg_file

Description

mdmcfgcheck can be used as a troubleshooting command. It can check that the modem is capable of understanding the different AT commands sent to it and described in the configuration file. mdmcfgcheck is intended to allow quick checking of the configuration file. This is done by sending all the commands to the modem and checking that the commands are correctly recognized. mdmcfgcheck also does a sanity check on the configuration file if the device name is omitted.

mdmcfgcheck is found in /usr/lib/uucp.

Options

The following options are available:

-t timeout: The duration the program should wait (in seconds) before deciding the modem is not responding. The default is 5 seconds.
-f: Discard extra answer from the modem which could interfere with the checking (rarely necessary).

/dev/devicename must be the full pathname of the modem, for example /dev/term/01m.

modem_cfg_file must be the full pathname of the modem configuration file. For example, /etc/uucp/Modems/Hayes_Accura_56K_Ext_Speakerphone_Modem_5670.

If /dev/devicename is specified, mdmcfgcheck goes through the commands and checks the modem replies. For example:

/usr/lib/uucp/mdmcfgcheck /dev/term/01m \
/etc/uucp/Modems/ Hayes_Accura_56K_Ext_Speakerphone_Modem_5670

produces the following output:

   Configuration standard:
   -----------------------
   Init........................Ok
   Reset.......................Ok
   Hangup......................Ok
   Answer......................Skipped
   Monitor.....................Ok
   CallSetupFailTimeout........Ok
   InactivityTimeout...........Ok
   Blind_Off...................Ok
   Blind_On....................Ok
   Compression_Off.............Ok
   Compression_On..............Ok
   SpeakerVolume_Low...........Ok
   SpeakerVolume_Med...........Ok
   SpeakerVolume_High..........Ok
   SpeakerMode_On..............Ok
   SpeakerMode_Off.............Ok
   SpeakerMode_Dial............Ok
   SpeakerMode_Setup...........Ok
   FlowControl_Off.............Ok
   FlowControl_Soft............Ok
   FlowControl_Hard............Ok
   Modulation_CCITT............Ok
   SpeedNegotiation_Off........Ok
   SpeedNegotiation_On.........Ok
   ErrorControl_Off............Ok
   ErrorControl_On.............Ok
   ErrorControl_Forced.........Ok

The ``Answer'' configuration is never tested, because it results in a ``No response'' error.

A ``No response'' error means that the modem has not responded to the program within the time limit set by the timeout option. An ``Ok'' means that the modem response is correct and an ``Error'' means the modem response is incorrect.

If the Init configuration result is not ``Ok'', other commands are not tested. For example:

   Configuration `V120':
   ---------------------
   Init........................Error

This is because the ``Init'' string is used to put the modem into a known stable state so it does not make sense to test the other strings.

If no options are set, mdmcfgcheck provides a sanity check on the configuration file. For example:

/usr/lib/uucp/mdmcfgcheck \
/etc/uucp/Modems/Hayes_Accura_56K_Ext_Speakerphone_Modem_5670

produces the following output:

File name : Hayes_Accura_56K_Ext_Speakerphone_Modem_5670 Syntax : correct

Modem name: Hayes Accura 56K Ext Speakerphone Modem 5670 Vendor : Hayes Created : 2000-01-01 Origin : SCO Certified : Yes

Vendor homepage : n/a Modem homepage : n/a Email support : n/a

Files

/usr/lib/uucp/mdmcfgcheck
/etc/uucp/Modems

Diagnostics

The exit codes are:

0: OK (EXIT_OK).
1: Fatal error (EXIT_ERR_FATAL).
2: Error in command line (EXIT_ERR_CMDLINE).
3: Error opening or reading configuration file (EXIT_ERR_CFGFILE).
4: Error communicating with the modem (EXIT_ERR_MODEM).
5: Modem is busy (EXIT_ERR_BUSY).
6: Killed by SIGTERM or SIGINT (EXIT_ERR_SIGNAL).

References

ati(1M), mdmcfg(1M)