Configuring and Managing Integrated Modems
Download this chapter
Configuring and Managing Integrated ModemsConfiguring and Managing Integrated Modems
give_us_feedback

Table Of Contents

Configuring and Managing Integrated Modems

Modems and Modem Feature Support

V.90 Modem Standard

V.110 Bit Rate Adaption Standard

V.120 Bit Rate Adaptation Standard

Managing Modems

Managing SPE Firmware

Configuring Modems in Cisco Access Servers

Configuring Modem Lines

Verifying the Dial-In Connection

Troubleshooting the Dial-In Connection

Configuring the Modem Using a Modemcap

Configuring the Modem Circuit Interface

Comparison of NextPort SPE and MICA Modem Commands

Configuring Cisco Integrated Modems Using Modem Attention Commands

Using Modem Dial Modifiers on Cisco MICA Modems

Changing Configurations Manually in Integrated Microcom Modems

Configuring Leased-Line Support for Analog Modems

Configuring Modem Pooling

Creating a Modem Pool

Verifying Modem Pool Configuration

Configuring Physical Partitioning

Creating a Physical Partition

Physical Partitioning with Dial-In and Dial-Out Scenario

Configuring Virtual Partitioning

Configuring Call Tracker

Verifying Call Tracker

Enabling Call Tracker

Configuring Polling of Link Statistics on MICA Modems

Configuring MICA In-Band Framing Mode Control Messages

Enabling Modem Polling

Setting Modem Poll Intervals

Setting Modem Poll Retry

Collecting Modem Statistics

Logging EIA/TIA Events

Configuring a Microcom Modem to Poll for Statistics

Troubleshooting Using a Back-to-Back Modem Test Procedure

Clearing a Direct Connect Session on a Microcom Modem

Displaying Local Disconnect Reasons

Removing Inoperable Modems

Busying Out a Modem Card

Monitoring Resources on Cisco High-End Access Servers

Enabling DS0 Busyout Traps

Enabling ISDN PRI Requested Channel Not Available Traps

Enabling Modem Health Traps

Enabling DS1 Loopback Traps

Verifying Enabled Traps

Troubleshooting the Traps

NAS Health Monitoring Example

Configuration Examples for Modem Management

NextPort Modem Log Example

Modem Performance Summary Example

Modem AT-Mode Example

Connection Speed Performance Verification Example


Configuring and Managing Integrated Modems

The Cisco IOS software provides commands that manage modems that reside inside access servers or routers in the form of modem cards. This chapter describes the modem management tasks. It includes the following main sections:

•Modems and Modem Feature Support

•Managing Modems

•Configuration Examples for Modem Management

For additional instructions for configuring Cisco access servers, see the chapter "Configuring and Managing Cisco Access Servers and Dial Shelves" in this publication.

To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.com to search for information about the feature or refer to the software release notes for a specific release. For more information, see the "Identifying Supported Platforms" section in the "Using Cisco IOS Software" chapter.

Modem initialization strings are listed in the "Modem Initialization Strings" appendix. For a complete description of the commands mentioned in this chapter, refer to the Cisco IOS Dial Technologies Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.

Modems and Modem Feature Support

The Cisco IOS software supports three types of integrated modems for Cisco access servers and access routers:

•Modem ISDN channel aggregation (MICA) digital modem

•NextPort digital modem

•NM-AM network module analog modem

Table 6 lists device support for each of the Cisco access server hardware platforms.

Table 6 Cisco IOS Modems and Modem Feature Support 

Device Support
Cisco AS5300
Cisco AS5350
Cisco AS5400
Cisco AS5800
Cisco 2600/3600 Series Routers

Integrated modems

6- and 12-port MICA

60-port NextPort CSM v6DFC

108-port NextPort CSM v6DFC

72- and 144-port MICA

324-port NextPort CSM v6DFC

6-port, 12-port, 18-port, 24-port, or 30-port MICA NM-DM

8- and 16-port analog NM-AM

V.90

Yes

Yes

Yes

Yes

Yes with NM-DM

V.110

Yes

Yes

Yes

Yes

Yes with NM-DM

V.120

No, CPU only

Yes

Yes

Yes with 324-port NextPort1 CSM v6DFC

No, CPU only

1 For more detailed information regarding the V.120 functionalities that are supported both by NextPort and Cisco IOS software, see the section "V.120 Bit Rate Adaptation Standard."


Note If the platform is using MICA technologies modems, the V.120 rate adaptation is done by CPU on vty lines like protocol translation sessions.

Note Typically, parity and databits commands have no effect on modem lines without UART. However, since modem lines such as WIC-1AM and WIC-2AM are implemented though UART and use an internal UART, the parity and databits commands can be used to set async parity framing. The following commands may be used on WIC-AM modem cards although changing the DTE speed and stopbits on these lines have no effect: parity, databits, stopbits, flowcontrol, speed, rxspeed, and txspeed.

The following sections summarize the standards supported by modems in the Cisco access servers. See Table 7 through Table 10 for a summary and comparison of the Cisco IOS commands used for the MICA and NextPort modems.

V.90 Modem Standard

Study Group 16 of the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) developed the V.90 modem standard for multimedia systems. The V.90 standard describes a digital modem and analog modem pair for use on the public switched telephone network (PSTN). V.90 modems are designed for connections that are digital at one end and have only one digital-to-analog conversion. The V.90 standard is expected to be widely used for applications such as Internet and online service access. Download speeds of up to 56,000 bits per second (bps) are possible, depending on telephone line conditions, with upload speeds of up to 33,600 bps.

V.110 Bit Rate Adaption Standard

V.110 is a bit rate adaptation standard defined by the ITU that provides a standard method of encapsulating data over global system for mobile telecommunication (GSM) and ISDN networks. V.110 allows for reliable transport of asynchronous or synchronous data. V.110 adapts a low-speed connection to an ISDN B channel allowing the remote station or terminal adapter to use the fast call setup times offered by ISDN. This feature allows V.110 calls to be originated and terminated over ISDN. It also enables GSM wireless connectivity.

V.110, as an alternative to V.120, provides DTE with V-series type interfaces with access to ISDN network by bit stuffing. Many V.110 devices are used in Europe and Japan. In Japan, MICA supports the Personal-Handyphone-System Internet Access Forum Standard (PIAFS) protocol, which is similar to V.110.

The V.110 implementation for calls on MICA modems is managed by special boardware and modem code, along with the appropriate Cisco IOS image, in a manner similar to other modulation standards. This MICA V.110 implementation provides V.110 user rates ranging from 600 bps to 38,400 bps.

V.110 is supported on the following Cisco devices and network modules:

•Cisco AS5300-series access servers

•Cisco 3620, 3640, and 3660 access routers

•NM-6DM, NM-12DM, NM-18DM, NM-24DM, and NM-30DM network modules

The digital signal processors (DSPs) on the board can function as either modems or V.110 terminal adapters (or V.120 terminal adapters for NextPort DSPs). Based on the ISDN Q.931 bearer capability information element, the Cisco IOS software configures the DSP to treat the incoming call as a modem call, a V.110 call, or a V.120 call.

Figure 18 shows a dial-in scenario for how V.110 technology can be used with a stack of Cisco AS5300-series access servers.

Figure 18 V.110 Dial-In Scenario Using a Stack of Cisco AS5300-Series Access Servers

V.120 Bit Rate Adaptation Standard

ITU-T Recommendation V.120 revised by the ITU-T Study Group 14. V.120 describes a standard that can be used for adapting terminals with non-ISDN standard network interfaces to an ISDN. It is intended to be used between two terminal adapter (TA) functional groups, between two ISDN terminal (TE1) functional groups, between a TA and a TE1, or between either a TA or TE1 and an interworking facility inside a public or private ISDN.

V.120 allows for reliable transport of synchronous, asynchronous, or bit transparent data over ISDN bearer channels. Cisco provides three V.120 support features for terminal adapters that do not send the low-layer compatibility fields or bearer capability V.120 information:

•Answer all incoming calls as V.120—Static configuration used when all remote users have asynchronous terminals and need to connect with a vty on the router.

•Automatically detect V.120 encapsulation—Encapsulation dynamically detected and set.

•Enable V.120 support for asynchronous access over ISDN.

For terminal adapters that send the low-layer compatibility or bearer capability V.120 information, mixed V.120 and ISDN calls are supported. No special configuration is required.

V.120 is a digital rate adaptation and cannot be done on NM-AM network module analog modems. MICA DSP firmware does not have the code to terminate V.120 calls.

NextPort supports only a subset of V.120 functionalities that are supported by Cisco IOS software. Therefore, certain V.120 calls still will need to be terminated on the CPU, even if the chassis has available NextPort modems.

Managing Modems

To manage modems, perform the tasks in the following sections; the tasks you need to perform depend upon the type and needs of your system:

•Managing SPE Firmware

•Configuring Modems in Cisco Access Servers

•Configuring Cisco Integrated Modems Using Modem Attention Commands

•Configuring Modem Pooling

•Configuring Physical Partitioning

•Configuring Virtual Partitioning

•Configuring Call Tracker

•Configuring Polling of Link Statistics on MICA Modems

•Configuring MICA In-Band Framing Mode Control Messages

•Enabling Modem Polling

•Setting Modem Poll Intervals

•Setting Modem Poll Retry

•Collecting Modem Statistics

•Troubleshooting Using a Back-to-Back Modem Test Procedure

•Clearing a Direct Connect Session on a Microcom Modem

•Displaying Local Disconnect Reasons

•Removing Inoperable Modems

•Busying Out a Modem Card

•Monitoring Resources on Cisco High-End Access Servers

Managing SPE Firmware

You can upgrade your modem firmware to the latest NextPort Service Processing Element (SPE) firmware image available from Cisco. The SPE firmware image is usually retrieved from Cisco.com. You must first copy the SPE image from a TFTP server to flash memory using the copy tftp flash command. You then configure the firmware upgrade using the firmware location and firmware upgrade SPE configuration commands. The firmware location command specifies the location of the firmware file and downloads the firmware to an SPE or a range of SPEs, according to the schedule you selected for the firmware upgrade method using the firmware upgrade command.

The modem firmware upgrade commands must be saved into the system configuration using the write memory command; otherwise, at the next reboot downloading of the specified firmware will not occur.

To upgrade SPE firmware, use the following commands:

 
Command
Purpose

Step 1 

Router# configure terminal

Enters global configuration mode.

Step 2 

AS5400:

Router(config)# spe slot/spe

or

Router(config)# spe slot/spe slot/spe


AS5800:

Router(config)# spe shelf/slot/spe

or

Router(config)# spe shelf/slot/spe shelf/slot/spe

Enters SPE configuration mode. You can choose to configure a range of SPEs by specifying the first and last SPE in the range.

Step 3 

Router(config-spe)# firmware upgrade {busyout | download-maintenance | reboot}

Specifies the upgrade method.

Three methods of upgrade are available. The busyout keyword waits until all calls are terminated on an SPE before upgrading the SPE to the designated firmware. The download-maintenance keyword upgrades the firmware during the download maintenance time. The reboot keyword requests the access server to upgrade firmware at the next reboot.

Step 4 

Router(config-spe)# firmware location [IFS:[/]]filename

Specifies the SPE firmware file in flash memory to use for the selected SPEs. Allows you to upgrade firmware for SPEs after the new SPE firmware image is copied to your flash memory.

The Cisco IOS file specification (IFS) can be any valid IFS on any local file system. Use the dir all-filesystems EXEC command to display legal IFSs. Examples of legal IFS specifications include:

•bootflash:—Loads the firmware from a separate flash memory device.

•flash:—Loads the firmware from the flash NVRAM located within the router.

•system:/—Loads the firmware from a built-in file within the Cisco IOS image. The optional forward slash (/) and system path must be entered with this specification.

•filename—The name of the desired firmware file (for example, mica-modem-pw.2.7.3.0.bin). If the system keyword is specified, enter the path to the filename you want to download.

Step 5 

Router(config-spe)# exit

Exits SPE configuration mode.

Step 6 

Router(config)# exit

Exits global configuration mode.

Step 7 

Router# copy running-config startup-config

Saves your changes.

Note As soon as a firmware file is specified, the downloading begins. Do not specify all modems and then go into an upgrade process on a busy router. The modems that are not busy will all be marked busy and the server will wait until all the modems on each of the given cards are free before upgrading the multiple-port cards. The only way to clear this situation is to start disconnecting users with a clear command. Normally, groups of modems are specified in scripts with the spe slot/spe_begin and slot/spe_end statements, and upgrades are done in a rolling fashion.

Use the show modem version and show spe version commands to verify that the modems are running the portware version you specified.

The following example shows how to enter the SPE configuration mode, set the range of SPEs, specify the firmware file location in flash memory, download the file to the SPEs, and display a status report using the show spe EXEC command: 

Router# configure terminal

Router(config)# spe 7/0 7/17

Router(config-spe)# firmware upgrade busyout

Router(config-spe)# firmware location flash:np_6_75

Started downloading firmware flash:np_6_75.spe

Router(config-spe)# exit

Router(config)# exit

Router# show spe 7

.

.

.

                     SPE          SPE     SPE  SPE   Port         Call

SPE#    Port #       State        Busyout Shut Crash State        Type

7/00    0000-0005    ACTIVE             1    0     0 BBBBBB       ______

7/01    0006-0011    DOWNLOAD           1    0     0 bbbbbb       ______

7/02    0012-0017    DOWNLOAD           1    0     0 bbbbbb       ______

7/03    0018-0023    DOWNLOAD           1    0     0 bbbbbb       ______

.

.

.

For information about upgrading Cisco 3600 Series and Cisco 3700 modems, see the Cisco 3600 Series and Cisco 3700 Series Modem Portware Upgrade Configuration Note at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis3600/sw_conf/portware/5257d56k.htm .

Configuring Modems in Cisco Access Servers

To configure modem support for access servers such as the Cisco AS5300 and AS5800, perform the following tasks. The list describes which tasks are required and which are optional but recommended.

•Configuring Modem Lines (Required)

•Verifying the Dial-In Connection (Optional but Recommended)

•Troubleshooting the Dial-In Connection (Optional but Recommended)

•Configuring the Modem Using a Modemcap (Required)

•Configuring the Modem Circuit Interface (Required for Digital Modems)

Note See the chapter "Configuring and Managing Cisco Access Servers and Dial Shelves" for additional information about configuring Cisco AS5x00 series access servers.

Configuring Modem Lines

You must configure the modem lines and set the country code to enable asynchronous connections into your access server. To configure the modems and line, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

MICA modems

Router(config)# modem country mica country


NextPort SPE modems

Router(config)# spe country country


Microcom modems

Router(config)# modem country microcom_hdms country

Depending on the type of modems loaded in your access server, specifies the modem vendor and country code.1 This step is only for the MICA, NextPort SPE, and Microcom modems in the Cisco AS5000 series access servers.

Table 7 through Table 10 provide a summary and comparison of the Cisco IOS commands used for the MICA and NextPort modems.

Step 2 

Router(config)# line beginning-line-number ending-line-number

Enters the number of modem lines to configure. Usually this range is equal to the number of modems in the access server. Use the show line EXEC command to see which lines are available.

Step 3 

Router(config-line)# transport {input | output} {all | none}

Specifies that connection protocols can be used when connecting to the line. For outgoing calls, choose the output option. For incoming calls, choose the input option. If you do not intend to dial out, choose the none option.

Step 4 

Router(config-line)# autoselect {arap | ppp | slip}

Configures the line to automatically startup an AppleTalk Remote Access (ARA), PPP, and Serial Line Internet Protocol (SLIP) session. You can configure more than one protocol by entering multiple autoselect commands with the appropriate keyword.

Step 5 

Router(config-line)# autoselect during-login

Configures the lines to display the username and password prompt as soon as the line is connected, rather than waiting until the user presses the Enter or Return key at the terminal.

Step 6 

Router(config-line)# login authentication dialin

or

Router(config-line)# login login-name

Router(config-line)# password password

Enables authentication across all asynchronous modem logins.

Use the login authentication dialin command when authentication, authorization, and accounting (AAA) authentication has been enabled.

Use the login and password commands to configure non-AAA user authentication.

Step 7 

Router(config-line)# modem dialin

Configures the modem for only incoming calls.

Step 8 

Router(config-line)# exit

Returns to global configuration mode.

1 For a comprehensive list of modem country codes, see the modem country mica command and the modem country microcom_hdms command in the Cisco IOS Dial Technologies Command Reference.

Verifying the Dial-In Connection

Before configuring any additional protocols for the line such as SLIP, PPP, or ARA, test whether the dial-in connection for the access server and modem are configured correctly for dial-in access,

Note The same configuration issues exist between the client DTE and client modem. Make sure that you have the correct EIA/TIA-232 cabling and modem initialization string for your client modem.

The following is an example of a successful connection from a PC using a known good modem to dial in to a Cisco access server: 

at

OK

atdt9,5550101

CONNECT 14400/ARQ/V32/LAPM/V42BIS

User Access Verification

Username: user1

Password:

Router>

Troubleshooting the Dial-In Connection

Depending upon the problems you experience, take the appropriate action:

•If you are having problems making or receiving calls, make sure that you turned on the protocols for connecting to the lines and configured for incoming and outgoing calls.

•If the calls are not coming up at all, turn on modem debugging. Use the the modem debugging commands as follows:

–The debug modem command enables debugging on the modem line.

–The debug modem csm (or debug csm modem) command enables debugging for lines configured for digital modems.

–The debug isdn q931 command enables debugging for lines configured for the ISDN and Signaling System 7 (SS7) Q.931 protocols.

–The debug cas command enables debugging for lines configured for channel-associated signaling (CAS).

Following is a sample of how to enable and then disable Cisco IOS modem debugging commands on a network access server: 

Router# debug modem

Router# debug modem csm

Router# debug isdn q931

Router# no debug modem

Router# no debug modem csm

Router# no debug isdn q931

•Enter the debug modem ? command for a list of additional modem debugging commands: 

Router# debug modem ?

  b2b          Modem Special B2B

  csm          CSM activity

  maintenance  Modem maintenance activity

  mica         MICA Async driver debugging

  oob          Modem out of band activity

  tdm          B2B Modem/PRI TDM

  trace        Call Trace Upload

•Turn off the messages by entering the no debug modem command.

For more detailed information refer to the TAC Tech Notes document, Troubleshooting Modems, at the following URL: http://www.cisco.com/warp/public/471/index_14280.html

Configuring the Modem Using a Modemcap

Modems are controlled by a series of parameter settings (up to a limit of 128 characters) that are sent to the modem to configure it to interact with a Cisco device in a specified way. The parameter settings are stored in a database called a modem capability (modemcap). The Cisco IOS software contains defined modemcaps that have been found to properly initialize internal modems. Following are the names of some modemcaps available in the Cisco IOS software:

•cisco_v110—Cisco (NEC) internal V.110 TA (AS5200)

•mica—Cisco MICA HMM/DMM internal digital modem

•nextport—Cisco NextPort CSMV/6 internal digital modem

•microcom_hdms—Microcom HDMS chassis

•microcom_mimic—Cisco (Microcom) internal analog modem (NM-AM-2600/3600)

•microcom_server—Cisco (Microcom) V.34/56K internal digital modem (AS5200)

Enter these modemcap names with the modem autoconfigure type command.

For more information on creating and using modemcaps refer to the TAC Tech Notes documentation, Recommended Modemcaps for Internal Digital and Analog Modems on Cisco Access Servers, at the following URL: http://www.cisco.com/warp/public/471/recc_modemcaps.html

If your modem is not on this list and if you know what modem initialization string you need to use with it, you can create your own modemcap; see the following procedure, "Using the Modem Autoconfigure Type Modemcap Feature." To have the Cisco IOS determine what type of modem you have, use the modem autoconfigure discovery command to configure it, as described in the procedure "Using the Modem Autoconfigure Discovery Feature."

Note When configuring an internal modem, avoid using the Modem Autoconfigure Discovery feature because the feature can misdetect the internal modem type and cause the modem to start working in an unpredictable and unreproducable manner.

Using the Modem Autoconfigure Type Modemcap Feature

If you know what modem initialization string you need to use with your modem, you can create your own modemcap by performing the following steps.

Step 1 Use the modemcap edit command to define your own modemcap entry.

The following example defines modemcap MODEMCAPNAME: 

Router(config)# modemcap edit MODEMCAPNAME miscellaneous &FS0=1&D3

Step 2 Apply the modemcap to the modem lines as shown in the following example: 

Router# terminal monitor

Router# debug confmodem

Modem Configuration Database debugging is on

Router#configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)#line 33 34

Router(config-line)#modem autoconfigure type MODEMCAPNAME

Jan 16 18:12:59.643: TTY34: detection speed (115200) response ---OK---

Jan 16 18:12:59.643: TTY34: Modem command:  --AT&FS0=1&D3--

Jan 16 18:12:59.659: TTY33: detection speed (115200) response ---OK---

Jan 16 18:12:59.659: TTY33: Modem command:  --AT&FS0=1&D3--

Jan 16 18:13:00.227: TTY34: Modem configuration succeeded

Jan 16 18:13:00.227: TTY34: Detected modem speed 115200

Jan 16 18:13:00.227: TTY34: Done with modem configuration

Jan 16 18:13:00.259: TTY33: Modem configuration succeeded

Jan 16 18:13:00.259: TTY33: Detected modem speed 115200

Jan 16 18:13:00.259: TTY33: Done with modem configuration

Note The report that is generated by the debug confmodem command can be misleading for the MICA and NextPort internal modems because these modems do not have Universal Asynchronous Receiver/Transmitter (UART) and exchange data with the CPU at speeds of hundreds of kbps.

Using the Modem Autoconfigure Discovery Feature

If you prefer that the modem software use its autoconfigure mechanism to configure the modem, use the modem autoconfigure discovery command.

The following example shows how to configure modem autoconfigure discovery mode: 

Router# terminal monitor

Router# debug confmodem

Modem Configuration Database debugging is on

Router# configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)# line 33 34

Router(config-line)# modem autoconfigure discovery

Jan 16 18:16:17.724: TTY33: detection speed (115200) response ---OK--- 

Jan 16 18:16:17.724: TTY33: Modem type is default 

Jan 16 18:16:17.724: TTY33: Modem command:  --AT&F&C1&D2S0=1H0-- 

Jan 16 18:16:17.728: TTY34: detection speed (115200) response ---OK--- 

Jan 16 18:16:17.728: TTY34: Modem type is default 

Jan 16 18:16:17.728: TTY34: Modem command:  --AT&F&C1&D2S0=1H0-- 

Jan 16 18:16:18.324: TTY33: Modem configuration succeeded 

Jan 16 18:16:18.324: TTY33: Detected modem speed 115200 

Jan 16 18:16:18.324: TTY33: Done with modem configuration 

Jan 16 18:16:18.324: TTY34: Modem configuration succeeded 

Jan 16 18:16:18.324: TTY34: Detected modem speed 115200 

Jan 16 18:16:18.324: TTY34: Done with modem configuration

Configuring the Modem Circuit Interface

The next task to complete before using the integrated modem is to configure the modem circuit interface. The basic steps are outlined next:

•If the integrated modem is an analog modem, no further configuration is required; modem characteristics are set on the line.

•If the integrated modem is a digital modem, you can configure either the ISDN or CAS, as appropriate.

–For ISDN BRI and PRI, you need to select the switch type and whether ISDN accepts incoming voice or data calls. If you configure a PRI, you will need to configure the T1 or E1 controller. See the chapter "Configuring ISDN BRI" in the "ISDN Configuration" part of this guide, and the chapter "Configuring ISDN PRI" in the "Signaling Configuration" part of this guide.

–Configuring CAS is described in the chapter "Configuring ISDN PRI" in the Signaling Configuration part of this guide.

If you want to configure SS7, refer to Appendix G, "Configuring the Cisco SS7/C7 Dial Access Solution System," in the Cisco IOS Voice, Video, and Fax Configuration Guide.

Comparison of NextPort SPE and MICA Modem Commands

Table 7 through Table 10 compare the MICA and SPE commands.

Table 7 EXEC Commands: NextPort to MICA Command Comparison 

NextPort SPE Commands
Purpose
MICA Modem Commands

clear port

Clears specified ports.

clear modem

clear port log

Clears all log entries for specified ports.

clear modem log

clear spe

Reboots all specified SPEs. All calls will be torn down.

none

clear spe counters

Clears all statistics.

clear modem counters

clear spe log

Clears all log entries for specified SPEs.

clear modem log

show port config

Displays configuration parameters for the current active session.

show modem config

show port modem calltracker

Displays port-level information for an active modem.

show modem calltracker

show port modem log

Displays the events generated by the modem sessions.

show modem log

show port modem test

Displays port modem test results.

show modem test

show port operational-status

Displays statistics for the current active session.

show modem operational-status

show spe

Displays the SPE status.

—

show spe log

Displays the SPE system log.

—

show spe modem active

Displays the statistics of all active calls on specified SPEs.

show modem

show spe modem csr

Displays the call success rate (CSR) for the specified SPE.

show modem

show spe modem disconnect-reason

Displays all modem disconnect reasons for the specified SPEs.

show modem call-stats

show spe modem high speed

Displays the total number of connections negotiated within each modulation or coder-decoder (codec) for a specific range of SPEs.

show modem speed

show spe modem high standard

Displays the total number of connections negotiated within each high modulation or codec for a specific range of SPEs or for all the SPEs.

—

show spe modem low speed

Displays the connect-speeds negotiated within each low-speed modulation or codec for a specific range of SPEs or for all the SPEs.

show modem speed

show spe modem low standard

Displays the total number of connections negotiated within each low modulation or codec for a specific range of SPEs or for all the SPEs.

—

show spe modem summary

Displays the modem service history statistics for specific SPEs.

show modem

show spe version

Displays all MICA and NextPort firmware versions stored in flash memory and the firmware assigned to each SPE.

show modem mapping


Table 8 SPE Configuration Commands: NextPort to MICA Command Comparison 

NextPort SPE Commands
Purpose
MICA Modem Commands

busyout

Busies out active calls.

modem busyout

firmware location filename

Specifies the firmware file to be upgraded.

Already implemented on the Cisco AS5300 and Cisco AS5800 platforms.

firmware upgrade

Specifies the upgrade method.

Already implemented on the Cisco AS5300 platform.

port modem autotest1

Enables modem autotest.

modem autotest

shutdown

Tears down all active calls on the specified SPEs.

modem shutdown

spe

Configures the SPE.

Already implemented on the Cisco AS5300 and Cisco AS5800 platforms.

spe call-record

Generates a modem call record at the end of each call.

modem call-record

spe country

Sets the system country code.

modem country

spe log-size

Sets the maximum log entries for each port.

modem buffer-size

spe poll

Sets the statistic polling interval.

modem poll

1 Cisco does not recommend the use of the modem autotest or port modem autotest command. These commands may produce unexpected results including modems being marked out of service and unscheduled reloads. These commands have been removed in Cisco IOS Release 12.3.


Table 9 Port Configuration Commands: NextPort to MICA Command Comparison

NextPort SPE Commands
Purpose
MICA Modem Commands

busyout

Busies out a port.

modem busyout

default

Compares the value of the command to its default value.

default modem

port

Configures the port range.

modem range

shutdown

Shuts down a port.

modem shutdown


Table 10 Global Configuration Commands: NextPort to MICA Command Comparison

NextPort SPE CLI Commands
Purpose
MICA Modem CLI Commands

ds0 busyout-threshold

Defines a threshold to maintain a balance between the number of digital signal level 0s (DS0s) and modems.

modem busyout-threshold


Configuring Cisco Integrated Modems Using Modem Attention Commands

This section provides information about using modem attention (AT) command sets to modify modem configuration. It contains the following sections:

•Using Modem Dial Modifiers on Cisco MICA Modems (As required)

•Changing Configurations Manually in Integrated Microcom Modems (As required)

•Configuring Leased-Line Support for Analog Modems (As required)

Using Modem Dial Modifiers on Cisco MICA Modems

Dial modifiers permit multistage dialing for outbound modem calling through public and private switched telephone networks (PSTNs).

Note For additional information about dial modifiers for the MICA modems, search Cisco.com for the publication AT Command Set and Register Summary for MICA Six-Port Modules.

The Cisco NAS Modem Health feature is enabled by arguments to the ATD AT command. The AT prefix informs the network access server modem that commands are being sent to it, and the D (dial string or dial) suffix dials a telephone number, establishing a connection. With NAS Modem Health feature, you can enter the dial modifiers listed in Table 11 after the D in your dial string: X, W, and the comma (,) character. These modifiers had been previously accepted without error but ignored in Cisco MICA modems on Cisco AS5300 and Cisco AS5800 universal access servers.

Table 11 Dial Modifiers for Cisco MICA Modems 

Dial Modifier
Definition

X

Switches to in-band dual tone multifrequency (DTMF) mode for any subsequent digits remaining in the ATD string. The X dial modifier has been added to serve as a delimiter for the host when the dial string is processed. It allows Cisco MICA portware to be used in many environments that do not support DTMF dialing (for example, PRI).

W

Waits for dial tone and then switches to in-band DTMF mode for any subsequent digits remaining in the ATD string. The W dial modifier also acts as a delimiter between the primary and secondary sections of the dial string, so that no additional X modifier is needed. Once either an X or a W has been parsed in the dial string, any additional X modifiers are ignored. Additional W modifiers cause Cisco MICA modems to wait for a dial tone.

,

Delay: Number of seconds in S8. Default is 2 seconds. The comma (,) dial modifier is treated as a silent DTMF tone for the duration of seconds specified in S8. The comma is acted on only after the call switching module (CSM) has made the transition to DTMF mode, which requires that it either follow an X or a W in the dial string, or that the T1/E1 be configured for DTMF signaling.


In the following example dial string, the portion of the string before the X is dialed for the given line type used in your configuration. All digits after the X generate the appropriate DTMF tones.

atdT5550101x,,567

Changing Configurations Manually in Integrated Microcom Modems

You can change the running configuration of an integrated modem by sending individual modem AT commands. Manageable Microcom modems have an out-of-band feature, which is used to poll modem statistics and send AT commands. The Cisco IOS software uses a direct connect session to transfer information through this out-of-band feature. To send AT commands to a Microcom modem, you must permit a direct connect session for a specified modem, open a direct connect session, send AT commands to a modem, and clear the directly connected session from the modem when you are finished.

Open a direct connect session by entering the modem at-mode slot/port command in privileged EXEC mode. From here, you can send AT commands directly from your terminal session window to the internal Microcom modems. Most incoming or outgoing calls on the modems are not interrupted when you open a direct connect session and send AT commands. However, some AT commands interrupt a call—for example, the ATH command, which hangs up a call. Open and close one direct connect session at a time. Note that multiple open sessions slow down modem performance.

Refer to the AT command set that came with your router for a complete list of AT commands that you can send to the modems.

For Microcom modems, you can clear or terminate an active directly connected session in two ways:

•Press Ctrl-C after sending all AT commands as instructed by the system when you enter AT command mode.

•Enter a second Telnet session and execute the clear modem at-mode slot/port EXEC command. This method is used for closing a directly connected session that may have been mistakenly left open by the first Telnet session.

The following example illustrates use of the modem commands.

AT Mode Example for Integrated Modems

To establish a direct connect session to an internal or integrated modem (existing inside the router), such as the connection required for Microcom modems in the Cisco AS5200 access server, open a directly connected session with the modem at-mode command and then send an AT command to the specified modem. For example, the following example sends the AT command at%v to modem 1/1: 

AS5200# modem at-mode 1/1

You are now entering AT command mode on modem (slot 1 / port 1).

Please type CTRL-C to exit AT command mode.

at%v

MNP Class 10 V.34/V.FC Modem Rev 1.0/85

OK

at\s

IDLE           000:00:00

LAST DIAL      

NET ADDR:      FFFFFFFFFFFF

MODEM HW: SA 2W United States

4 RTS 5 CTS 6 DSR - CD 20 DTR - RI 

MODULATION     IDLE

MODEM BPS      28800  AT%G0   

MODEM FLOW     OFF    AT\G0

MODEM MODE     AUT    AT\N3

V.23 OPR.      OFF    AT%F0

AUTO ANS.      ON     ATS0=1

SERIAL BPS     115200 AT%U0   

BPS ADJUST     OFF    AT\J0

SPT BPS ADJ.   0      AT\W0

ANSWER MESSGS  ON     ATQ0   

SERIAL FLOW    BHW    AT\Q3

PASS XON/XOFF  OFF    AT\X0

PARITY         8N     AT

The modem responds with "OK" when the AT command you send is received.

Configuring Leased-Line Support for Analog Modems

Analog modems on the NM-8AM and NM-16AM network modules in the Cisco 2600 and 3600 series routers provide two-wire leased-line support for enterprise customers who require point-to-point connections between locations and for enterprise customers with medium to high data transfer requirements without access to other technologies or with access to only low-grade phone lines.

This feature works only with leased lines that provide loop current. Each modem used must have an RJ-11 connection to the PSTN.

Several features enhance the analog modem software:

•2-wire leased-line support.

•Modem speeds up to 33.6 kbps with support for all current analog modem protocols, compression, and error correction techniques.

•Power-on autoconnect and loopback testing.

•Support for the maximum number of leased-line users without data transmission loss at distances up to 2 to 5 km.

•In-band and out-of-band monitoring.

•Support on all Cisco 2600 and Cisco 3600 series platforms and upgradability using Cisco IOS software.

•Compatibility with other major leased-line modem vendors.

To configure this support, configure one modem AT command (AT&L) and two AT registers with the modemcap entry command for the appropriate leased lines.

For leased line configuration using the AT&L{0 | 1 | 2}command:

•0—Disables the leased line (enables switched line; default).

•1—Enables the leased line. The modem initiates a leased line when dial and answer commands (ATD and ATA) are issued.

•2—Enables the leased line. The modem goes off hook automatically after T57 number of seconds in:

–Originate mode if ATS0 is 0.

–Answer mode if ATS0 is not equal to 0.

The following AT registers can also be set:

•AT:T57—Number of seconds before going off hook in leased-line mode when the command AT&L2 is used (defaults to 6).

•AT:T79—Number of autoretrains before the modem is disconnected (defaults to 3).

For more information about using the AT command set with the modems on the NM-8AM and NM-16AM network modules in the Cisco 2600 and 3600 series routers, search Cisco.com for the publication AT Command Set and Register Summary for Analog Modem Network Modules.

To configure a modem for leased-line operation, use the following commands in global configuration mode:

 
Command
Purpose

Step 1  

Router(config)# modemcap entry 
modem-type-name:AA=S0=0&L2

Sets the modemcap for leased-line operation for the originating modem.

Step 2  

Router(config)# modemcap entry 
modem-type-name:AA=S0=1&L2

Sets the modemcap for leased-line operation for the answering modem.

The show modemcap command lists all the predefined modem types and any user-defined modemcaps that are currently configured on the router:

•If the leased line has been configured, the modemcap information will be available.

•If the leased line has not been configured, only the predefined modem types will be displayed.

The important setting for leased-line support is what is defined in the modemcap as the key configuration item and its application to the leased line. Consider the following command strings: 

modemcap entry micro_LL_orig:AA=S0=0&L2

modemcap entry micro_LL_ans:AA=S0=1&L2

AA stands for autoanswer:

•The answering modem AA register is set to 1 (AA=S0=1) so that autoanswer is "on".

•The originating modem AA register is set to 0 (AA=S0=0) so that autoanswer is "off".

If the AA feature is used, both the originating and answering modem must be put into leased-line mode with the &L2 AT command.

In the examples, the micro_LL_orig and micro_LL_ans strings are arbitrary text descriptions.

Note For the modemcap entry command, one of the predefined modem types may be used or a completely user-defined modemcap may be created. For leased line, no new modem type was added. Users may create their own modemcaps for leased-line functionality.

To configure the modem for leased-line operation, use the modemcap entry command. For each connection, each modem must be configured as an originator or answerer.

The following example shows modemcaps for a leased-line originator and answerer and their application to specific ports: 

modemcap entry micro_LL_orig:AA=S0=0&L2

modemcap entry micro_LL_ans:AA=S0=1&L2

line 73 

 no exec 

 modem InOut 

 modem autoconfigure type micro_LL_ans

 transport input all 

line 74 

 no exec 

 modem InOut 

 modem autoconfigure type micro_LL_orig

 transport input all

Note When Multilink PPP (MLP) is configured on a dialer interface, the dialer configuration has a default value of 2 minutes for dialer idle timeout. For leased-line connections, set the dialer idle timeout to infinity by adding dialer idle-timeout 0 to the configuration.

Verifying the Analog Leased-Line Configuration

The following information is important for verifying or troubleshooting your configuration. The show modem log command displays the progress of leased-line connections. Here is an example log for a leased-line answerer. Note the "LL Answering" state and "LL Answer" in the "Direction" field of the connection report: 

00:44:03.884 DTR set high

00:44:02.888 Modem enabled

00:43:57.732 Modem disabled

00:43:52.476 Modem State:LL Answering

00:43:52.476 CSM:event-MODEM_STARTING_CONNECT New

State-CSM_CONNECT_INITIATED_STATE

00:43:51.112 Modem State:Waiting for Carrier

00:43:43.308 Modem State:Connected

00:43:42.304 Connection:TX/RX Speed = 33600/33600,

Modulation = V34

Direction = LL Answer, Protocol = MNP, Compression =

V42bis

00:43:42.304 CSM:event-MODEM_CONNECTED New

State-CONNECTED_STATE

00:43:42.300 RS232:noCTS* DSR* DCD* noRI noRxBREAK

TxBREAK*

00:43:41.892 PPP mode active

00:43:41.892 Modem enabled

00:43:39.888 PPP escape maps set:TX map=00000000 RX

map=FFFFFFFF

00:43:39.724 PPP escape maps set:TX map=00000000 RX

map=000A0000

00:43:34.444 RS232:CTS* DSR DCD noRI noRxBREAK TxBREAK

00:43:11.716 Modem Analog Report:TX = -20, RX = -34,

Signal to noise = 61

Cisco 2600 and 3600 Series Analog Modem Leased-Line Support Examples

In the following examples, one Cisco 3620 router and one Cisco 3640 router are connected back-to-back using leased lines. The Cisco 3620 router has the originating configuration, and the Cisco 3640 router has the answering configuration.

In the dialer interface configuration, the dialer idle-timeout 0 command is added to set the dialer idle timeout to be infinity. Otherwise the leased line will go down and up every 2 minutes because the default dialer interface idle timeout is 2 minutes.

Note Except for passwords and logins, the Cisco IOS command-line interface (CLI) is case-insensitive. For this document, an uppercase "L" has been used in the command examples to avoid confusion with the numeral "1".

Leased-Line Originating Configuration 

version 12.1 

service timestamps debug uptime 

service timestamps log uptime 

! 

modemcap entry micro_LL_orig:AA=S0=0&L2 

modemcap entry micro_LL_ans:AA=S0=1&L2 

! 

interface Async33 

  no ip address 

encapsulation ppp 

 no ip route-cache 

 no ip mroute-cache 

 dialer in-band 

 dialer pool-member 1 

 async default routing 

 async dynamic routing 

 async mode dedicated 

 no peer default ip address 

 no fair-queue 

 no cdp enable 

 ppp direction callout 

 ppp multilink 

! 

interface Dialer1 

 ip address 10.1.24.1 255.255.255.0 

 encapsulation ppp 

 no ip route-cache 

 no ip mroute-cache 

 dialer remote-name sara40 

 dialer pool 1 

 dialer idle-timeout 0 

 dialer max-call 4096 

 no cdp enable 

 ppp direction callout 

 ppp multilink 

! 

dialer-list 1 protocol ip permit 

! 

line con 0 

 exec-timeout 0 0 

 transport input none 

 line 33 

 no exec 

 modem InOut 

 modem autoconfigure type micro_LL_orig 

 transport input all 

line aux 0 

 exec-timeout 0 0 

line vty 0 4 

 exec-timeout 0 0 

! 

end

Leased-Line Answering Configuration 

version 12.1 

service timestamps debug uptime 

service timestamps log uptime 

! 

modemcap entry micro_LL_orig:AA=S0=0&L2 

modemcap entry micro_LL_ans:AA=S0=1&L2 

! 

interface Async73 

 no ip address 

 encapsulation ppp 

 no ip route-cache 

 no ip mroute-cache 

 dialer in-band 

 dialer pool-member 1 

 async default routing 

 async dynamic routing 

 async mode dedicated 

 no peer default ip address 

 no fair-queue 

 no cdp enable 

 ppp direction callout 

 ppp multilink 

! 

interface Dialer1 

 ip address 10.1.24.2 255.255.255.0 

 encapsulation ppp 

 no ip route-cache 

 no ip mroute-cache 

 load-interval 30 

 dialer remote-name sara20 

 dialer pool 1 

 dialer idle-timeout 0 

 dialer load-threshold 1 either 

 dialer max-call 4096 

 no cdp enable 

 ppp direction callout 

 ppp multilink 

! 

dialer-list 1 protocol ip permit 

line con 0 

 exec-timeout 0 0 

 transport input none 

line 73 

 no exec 

 modem InOut 

 modem autoconfigure type micro_LL_ans

 transport input all

line aux 0 

 transport input all 

 flowcontrol hardware 

line vty 0 4 

 exec-timeout 0 0