HDK Technical Reference

Modems, adding new

This article outlines the procedure for manually adding modem definition files to a SVR5 system for use with the Modem Manager. It also describes how to verify that a modem can be added successfully.

Defining a new modem

Modem dialers in SVR5 are supported with the atdialer configurable dialer program.

To add support for a new modem and its dialer, perform the following steps:

  1. Choose a name (hereafter called a dialer-name) for the dialer. Typically, this should identify the vendor, speed, and model of the modem, for example, ACME-28-8_External_modem.

  2. Create a configuration file for the new modem and place it in a file named dialer-name in the directory /etc/uucp/default/, for example, /etc/uucp/default/ACME-28-8_External_modem. See the atdialer manual page for a description of the format of this file. The files that are already present in /etc/uucp/default contain many examples of such dialers. Note that most of the parameters in this file have a default value so you do not have to specify all of them.

  3. Create a vendor file in /etc/uucp/DBase, such as ACME_Inc. This file defines one model of modem per line using the following format:

    dialer-name {modem description} type {string}

    dialer-name is the name of the dialer file that you created in step 2. modem description is the description of the modem model that the Modem Manager will display. Possible values for the type of modem are:

    external modem

    internal modem

    PCMCIA modem
    The string field is not currently used and can be omitted or set to an arbitrary value.

    The following entry shows an example entry from a vendor file:

    ACME-28-8_External_modem {ACME 28.8K external modem} 01

  4. Edit the /etc/uucp/DBase/Vendors file and add an entry for the modem vendor using the following format:

    vendor-filename {full vendor name}

    vendor-filename is the name of the vendor file that you created in the previous step. full vendor name is a string that the Modem Manager will display as the name of the vendor. For example:

    ACME_Inc {Allied Communication Modem Engineering Inc}

  5. If you want to allow the modem to be autodetected, edit the /etc/uucp/Detect file and add the send/expect command/response sequence that can be used to identify the modem using the following format:

    dialer-name {send expect} {send expect} ...

    For example:

    ACME-28-8_External_modem {ATI1 099} {ATI0 28800}
    This example uses the strings returned by the ATI1 and ATI0 commands to identify the modem. With other modems, you may be able to use commands such as ATI4, ATI2, or ATI3. Consult the documentation supplied by the modem vendor for details of the appropriate commands to use for identification.

Testing the modem

First configure the system to use the new modem:

  1. Invoke the Modem Manager from the Networking section of scoadmin (or enter scoadmin modem from the command line).

  2. The Modem Manager will display the newly added modem in the list of modems to select. You can choose to select the modem manually, or you can autodetect it if you defined the autodetection command sequences to do this.

  3. Click on Configure serial to use the Serial Manager to configure the serial port to which your modem is attached. Select the incoming and outgoing port setting so that you can test connections in either direction.

  4. Having configured the modem and serial port, exit the Serial Manager and Modem Manager.

  5. Run the Dialup Systems Manager from the Networking section of scoadmin (or enter scoadmin dialup from the command line). Use this manager to configure an entry in the /etc/uucp/Systems file for the remote system that you will dial.

  6. Exit the Dialup Systems Manager.
To test the new modem:

  1. Make an outgoing call. Use the cu system command to dialup the system you specified in the Dialup Systems Manager.

  2. Make an incoming call. by selecting the bi-directional option from the serial port configuration, your system is automatically ready to accept incoming calls. Test that this works by making an outgoing call from another system to this system.

© 2005 The SCO Group, Inc. All rights reserved.
OpenServer 6 and UnixWare (SVR5) HDK - June 2005