|
|
mdmcfgcheck is found in /usr/lib/uucp.
/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........................ErrorThis 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 : correctModem 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