System Management Guide: Communications and Networks

Modems

Modems provide serial communications across ordinary telephone lines. This section discusses modem standards, general modem setup, and specific configuration tips for popular modems.

Modem Overview

A modem is a device that allows you to connect one computer to another across ordinary telephone lines. The current telephone system is incapable of carrying the voltage changes required for a direct digital connection. A modem overcomes this limitation by modulating digital information into audio tones for transmission across the phone line, and by demodulating those tones back into digital information on reception. Modems are commonly used with Basic Network Utilities (BNU) or other implementations of the UNIX-to-UNIX Copy Program (UUCP). A high-speed (14,400 bps or greater) modem can be used with Serial Line Interface Protocol (SLIP) to provide Transmission Control Protocol/Internet Protocol (TCP/IP) connectivity as well.

Often, the term baud is used to refer to modem speed instead of bps. Baud is actually a measurement of the modulation rate. In older modems, only 1 bit was encoded in each signal change, so modem baud rate was equal to modem speed. Modems that operate at higher speeds, however, still generally operate at 2,400 (or even 1,200) baud, and encode two or more bits per signal change. A modem's bps rate is calculated by multiplying the number of data bits per signal with the baud (for example, 2,400 baud x 6 bits per signal change = 14,400 bits per second). Most modern modems can communicate at a variety of speeds (for example, 28,800, 14,400, 9,600, 7,800, 4,800, and 2,400 bps).

Telecommunications Standards

The older speeds of 300, 1,200, and 2,400 bps were well defined. However, as modem manufacturers began to devise methods for gaining higher speeds, each modem manufacturer started to use a proprietary method incompatible with modems from other manufacturers. Today, the ITU-TSS (formerly the United Nations Consultative Committee for International Telephony and Telegraphy, abbreviated CCITT) defines standards for most high-speed communications.

Even high-speed modems are much slower than other methods of computer communication. A high-speed modem can operate at 28,800 bps, but an Ethernet connection operates at 10,000,000 bps. To boost data throughput, high-speed modems typically offer one or more data compression algorithms. These algorithms can boost the throughput of a high-speed modem to speeds of 57,600 bps (if the data rate is 14,400 bps) or 115,200 bps (if the data rate is 28,800 bps). Note that these compression algorithms are sensitive to the data being transmitted. If the data has already been compressed (for example, with the compress command), the data compression methods of high-speed modems offer little or no benefit, and might even reduce data throughput. When using a modem with data compression technology, the speed of the data terminal equipment/data circuit-terminating equipment (DTE/DCE) connection between the computer and the modem is equal or greater than the nominal data rate of the connection between modems. For example, with a V.32bis modem with V.42bis data compression, the data rate of the modem (the speed at which the modem communicates across telephone lines) is 14,400 bps. When the V.42bis compression is active, actual data throughput can reach 57,600 bps. To accommodate the greater throughput offered by data compression, the speed of the link between the computer and the modem should be set to 57,600 bps.

The ITU-TSS defines standards for high-speed communications, including data compression algorithms. ITU-TSS standards are usually named V.nn, where nn is a number. Another, slightly less common standard is the Microcom Networking Protocol (MNP). Available in versions (called classes) 1-9, MNP is a high-performance, high-speed protocol that was available relatively early, and became something of a de facto standard before the advent of the CCITT standards.

ITU-TSS Communications Standards

Following is a list of some common communications standards defined by the ITU-TSS. Note that this only a partial list. For a complete list, refer to the Internet website for the International Telecommunication Union.

MNP Communications Standards

Generic Modem Setup

To set up a modem:

1. Create a TTY device on the Operating System
2. Attach the Modem with Appropriate Cables
3. Add a TTY for the Modem
4. Configure the Modem

Create a TTY device on the Operating System

Use the System Management Interface Tool (SMIT) to define a tty port for the device attachment. Most fields are for the general device type. The only field that can affect the modem is the Enable LOGIN field with the following values:

Fields specific to the 128-port asynchronous adapter:

Attach the Modem with Appropriate Cables

The first step in setting up a modem is to attach the modem with the appropriate cables. Part numbers and their descriptions are listed below.

6323741

Async Cable, EIA-232; used to attach all asynchronous devices; sometimes used with other cable assemblies.

59F3740

10 to 25-pin D-shell connector used to attach asynchronous cable 6323741 to native serial ports S1 and S2 as shown in the following figure.

Figure 29. 10 to 25-Pin Connector. This illustration shows a 10 to 25-pin connector.

59F3432

Cable P used to connect to 16-port concentrator. Part number includes four RJ45-to-DB25 converter cables.

Following are some examples of cable connections:

1. To attach a modem to native serial port S1, use the following cables:
   Figure 30. Modem to Native Serial Port Cable Assembly. This illustration shows a 59F3740 cable on the serial port end and a 6323741 on the modem end.
2. To attach a modem to an 8-port async adapter (EIA-232) interface cable assembly, use the following cables:
   Figure 31. 8-Port Interface to Modem Cable Assembly. This illustration shows an 8-port interface connected to a modem with a 6323741 cable.
3. To attach a modem to a 16-port concentrator on a 64-port adapter, use the following cables:
   Figure 32. 16-Port Interface to Modem Cable Assembly. This illustration shows a 59F3432 cable on the serial port end and a 6323741 on the modem end.

Add a TTY for the Modem

First, ensure that the system is turned on and that the modem is turned off. Use the Web-based System Manager, wsm, or the SMIT fast path smit mktty.

Configure the Modem

Use only one of the two methods presented in this section for configuring the modem. If you have Basic Networking Utilities (BNU) installed, see Sending AT Commands with the cu Command. If you do not have BNU installed, see Sending AT Commands Using a C Program. For information on installing BNU, see Basic Networking Utilities.

Sending AT Commands with the cu Command

If you have the Basic Network Utilities (BNU) installed, use the cu command to configure a modem as follows. The commands and settings discussed in this section configure a Hayes-compatible modem with the basic parameters needed for operation on the server's serial ports.

1. Add the following line to your /usr/lib/uucp/Devices file. Do not add the line if it is already in the file. (Replace # with the number for your port.)

   Direct tty# - Any direct

2. Verify that the tty is disabled by typing the following::

   pdisable tty#

3. Type the following command:

   cu -ml tty#

   You should see a message that says Connected.
4. Verify that you have the attention of the modem by typing the following:

   AT

   The modem should respond with OK. If it didn't, refer to Troubleshooting Modem Problems.

   For additional AT commands and their descriptions, see AT Command Summary.

5. Depending on which getty option you selected, enter one of the following commands. Substitute the tty device for n.
   • penable ttyn
   • pshare ttyn
   • pdelay ttyn
   • pdisplay ttyn

   The modem is now configured with the basic commands needed to perform most of the operating system's serial communications needs. If you have problems, invoke the cu -dl to start a diagnostic trace on the connection.

Sending AT Commands Using a C Program

If the previous method failed, or if you do not have BNU installed, try running the following C program. Create a file called motalk.c containing the following code. Save the file. Compile and run it according to the instructions in the program comments.

/*************************************************************/
/*  MoTalk - A "C" program for modem setup.                */
/*           This program is meant as an aid only and is   */
/*           not supported by IBM.                       */
/*                  compile:  cc -o motalk motalk.c       */
/*                  Usage:  motalk /dev/tty? [speed]      */
/*************************************************************/
#include <errno.h>
#include <stdio.h>
#include <signal.h>
#include <fcntl.h>
#include <termio.h>
FILE *fdr, *fdw;
int fd;
struct termio term_save, stdin_save;
void Exit(int sig)
{
   if (fdr) fclose(fdr);
   if (fdw) fclose(fdw);
   ioctl(fd, TCSETA, &term_save);
   close(fd);
   ioctl(fileno(stdin), TCSETA, &stdin_save);
   exit(sig);
}
main(int argc, char *argv[])
{
   char *b, buffer[80];
   int baud=0, num;
   struct termio term, tstdin;
   if (argc < 2 || !strcmp(argv[1], "-?"))
   {
      fprintf(stderr, "Usage: motalk /dev/tty? [speed]\n");
      exit(1);
   }
   if ((fd = open(argv[1], O_RDWR | O_NDELAY)) < 0)
   {
      perror(argv[1]);
      exit(errno);
   }
   if (argc > 2)
   {
      switch(atoi(argv[2]))
      {
         case   300: baud = B300;
                     break;
         case  1200: baud = B1200;
                     break;
         case  2400: baud = B2400;
                     break;
         case  4800: baud = B4800;
                     break;
         case  9600: baud = B9600;
                     break;
         case 19200: baud = B19200;
                     break;
         case 38400: baud = B38400;
                     break;
         default:    baud = 0;
                     fprintf(stderr, "%s: %s is an unsupported baud\n", argv[0],argv[2]);
                     exit(1);
         }
      }
   /* Save stdin and tty state and trap some signals */
   ioctl(fd, TCGETA, &term_save);
   ioctl(fileno(stdin), TCGETA, &stdin_save);
   signal(SIGHUP, Exit);
   signal(SIGINT, Exit);
   signal(SIGQUIT, Exit);
   signal(SIGTERM, Exit);
   /*  Set stdin to raw mode, no echo */
   ioctl(fileno(stdin), TCGETA, &tstdin);
   tstdin.c_iflag = 0;
   tstdin.c_lflag &= ~(ICANON | ECHO);
   tstdin.c_cc[VMIN] = 0;
   tstdin.c_cc[VTIME] = 0;
   ioctl(fileno(stdin), TCSETA, &tstdin);
   /*  Set tty state */
   ioctl(fd, TCGETA, &term);
   term.c_cflag |= CLOCAL|HUPCL;
   if (baud > 0)
   {
      term.c_cflag &= ~CBAUD;
      term.c_cflag |= baud;
   }
   term.c_lflag &= ~(ICANON | ECHO); /* to force raw mode */
   term.c_iflag &= ~ICRNL; /* to avoid non-needed blank lines */
   term.c_cc[VMIN] = 0;
   term.c_cc[VTIME] = 10;
   ioctl(fd, TCSETA, &term);
   fcntl(fd, F_SETFL, fcntl(fd, F_GETFL, 0) & ~O_NDELAY);
   /*  Open tty for read and write */
   if ((fdr = fopen(argv[1], "r")) == NULL )
   {
      perror(argv[1]);
      exit(errno);
   }
   if ((fdw = fopen(argv[1], "w")) == NULL )
   {
      perror(argv[1]);
      exit(errno);
   }
   /*  Talk to the modem */
   puts("Ready... ^C to exit");
   while (1)
   {
      if ((num = read(fileno(stdin), buffer, 80)) > 0)
         write(fileno(fdw), buffer, num);
      if ((num = read(fileno(fdr), buffer, 80)) > 0)
         write(fileno(stdout), buffer, num);
      Exit (0);
   }
} 

Hayes and Hayes-Compatible Modems

1. Change the tty settings, if necessary, using the Web-based System Manager, wsm, or the SMIT fast path, smit chtty. For example, you might want to change the Enable LOGIN field to Share or Enable.
2. Add the following line to /usr/lib/uucp/Systems file:

   hayes Nvr HAYESPROG 2400

3. Add this to /usr/lib/uucp/Devices file:

   # For programming the  hayes modem only:
   HAYESPROG tty0 - 2400 HayesProgrm2400
   #regular ACU entry:
   ACU tty0 - Any hayes
    

4. Add this to /usr/lib/uucp/Dialers file:

   # This Entry is used to PROGRAM the modem ONLY:
   # the next 3 lines should be made into one:
   HayesProgrm2400     =,-,     "" \d\dAT\r\c OK AT&F\r\c OK ATM1\r\c OK
   AT&D3\r\c OK AT&K3&C1\r\c OK ATL0E0Q2\r\c OK ATS0=1\r\c OK AT&W\r\c
   OK
   hayes     =,-,     "" \dAT\r\c OK ATDT\T\d\r\c CONNECT

5. To program the modem, enter the command cu -d hayes. This command uses the cu command to program the modem. Because no connection is made to another system, the command will fail. The modem is programmed if sendthem AT&W and then OK got it appear in the output.

   If you are not doing binary file transfers or using BNU, leave out the &K3 command, and set XON as the flow control to be used. However, it is more efficient to use hardware flow control (as opposed to XON-XOFF handshaking). To do that, use the settings and the Dialers entries from the next step.

6. After the modem is programmed, you can configure the system device driver to use hardware flow control. Using Web-based System Manager, wsm or SMIT (smit chtty fast path), change the flow control to RTS. Check your modem manuals to find out whether your modem supports hardware flow control.

Troubleshooting Modem Problems

This section attempts to identify common problems when using a modem with your computer. Keep in mind the following points:

• Some modems are case-sensitive. Use uppercase letters for the AT commands.
• In normal operation, it is preferable for the modem to reset when the DTR is dropped (&D3 setting). When the modem is being set up for the first time, however, it is advisable not to have the modem reset if the DTR is dropped (&D2 setting). If the modem resets itself, all programmed settings that are not saved in the modem's memory will be lost.

  Not having the modem reset also protects changes when &C1 is set. Changing the Carrier Detect status may cause the carrier detect line to toggle on some modems, which causes the cu command to drop the line. You may want to set up the modem to &D3 after the final setup is made.

• Although the commands given in this manual are standard for most Hayes-compatible modems, there is no guarantee that they are standard for your modem. Compare the commands with your modem manual before proceeding.

Software Services Modem Questionnaire

Before calling for assistance with modem problems, please collect the following information:

• Level of the operating system. How long have you been at this level of the operating system?
• Has the modem ever worked before?
• What type of modem are you using? What type of modem is on the other end of the telephone connection?
• To what adapter type (64-port, 128-port, S1,...) is the modem attached?
• To which port number is the modem attached?
• To which tty number is the modem attached?
• What type of cabling are you using?
• What is the login setting (share, delay, enable)?
• Can the modem connect to other modems?
• Can other modems connect to your modem?
• What are the following values in Web-based System Manager, SMIT, modem, or port?
  • XON/XOFF?
  • RTS/CTS?
  • BPS rate?
• Include the following in your problem description:
  • Does the port lock intermittently?
  • Can you dial out? Can others dial in?
  • Any other specific and descriptive error conditions.
• Are there errors on the console? What are they?
• Are there errors in the error report? (errpt or errpt -a)
• What command are you using to dial out?
• What software is involved on the system?

AT Command Summary

The following is a summary of the Hayes Smartmodem command set. These commands comprise the AT command set used by many popular modems. This information comes from the Hayes Smartmodem 2400 Quick Reference Card, published by Hayes Microcomputer Products, Inc. Consult the modem documentation for a list of relevant AT commands.

S-Register Summary

Result Codes Summary

Dial modifiers

The following lists and describes dial modifiers: