Cisco IOS Software Releases 12.2 T

Table Of Contents

V.92 Modem on Hold for Cisco AS5300 and Cisco AS5800 Universal Access Servers

Feature Overview

V.92

Modem on Hold

AT Commands (Modemcaps) and S-Registers

RADIUS Authorization

Configuring V.92 Modem on Hold with RADIUS

Modem Enhancements for V.92 Modem On Hold

Supported Module Firmware and Cisco IOS Software

Benefits

Restrictions

Related Features and Technologies

Related Documents

Supported Platforms

Supported Standards, MIBs, and RFCs

Prerequisites

Configuration Tasks

Monitoring and Maintaining Modem on Hold

Configuration Examples

Command Reference

show modem configuration

show modem log

show modem operational-status

Glossary

V.92 Modem on Hold for Cisco AS5300 and Cisco AS5800 Universal Access Servers

---

Feature History

Release	Modification
12.2(2)XA	This feature was introduced on Cisco AS5350 and Cisco AS5400 universal gateways running NextPort firmware. This feature was introduced on the Cisco AS5300 universal access server running Cisco MICA Portware Version 2.9.1.0.
12.2(2)XB	This feature was supported with Cisco IOS Release 12.2(2)XB.
12.2(2)XB1	This feature was supported on Cisco AS5800 universal access servers.
12.2(11)T	This feature was integrated into Cisco IOS Release 12.2(11)T and support was added for the Cisco AS5300 and Cisco AS5800 platforms.

This feature module introduces the V.92 International Telecommunication Union Telecommunication Standardization Sector (ITU-T) standard Modem on Hold (MOH) feature with Cisco MICA portware for use with Cisco IOS Release 12.2(2)XB1 and 12.2(11)T.

This document includes the following sections:

•Feature Overview

•Supported Platforms

•Supported Standards, MIBs, and RFCs

•Prerequisites

•Configuration Tasks

•Monitoring and Maintaining Modem on Hold

•Configuration Examples

•Command Reference

•Glossary

Feature Overview

V.92

To remain current with industry needs, the ITU-T V.90 modem standard recommendations have been enhanced. The new standard, V.92, meets the need for a digital modem and analog modem pair on the Public Switched Telephone Network (PSTN). V.92 improves the upstream data signaling rate and adds new features that enhance modem usability.

This feature module introduces the V.92 Modem on Hold feature on Cisco AS5300 and Cisco AS5800 universal access servers with Cisco MICA Portware Version 2.9.1.0 and higher.

---

Note The other feature introduced with the new V.92 standard is V.92 Quick Connect, which is documented in the V.92 Quick Connect for Cisco AS5300 and Cisco AS5800 Universal Access Servers feature module. V.92 Modem On Hold and V.92 Quick Connect can be enabled independently of each other.

---

V.92 is implemented at the modem level as new modem protocols and standards. The new V.92 features co-reside with existing portware features and have no impact on the hardware configuration of either the HMM or DMM (including memory requirements). Cisco IOS software is responsible for controlling the features and displaying the new statistics. V.92 and V.44 support is bound with the rest of the Cisco IOS device driver components.

---

Note V.92 is packaged with V.44 in Cisco IOS software. For more information about V.44, refer to the
V.44 LZJH Compression for Cisco AS5300 and Cisco AS5800 Universal Access Servers feature module.

---

---

Note This feature does not support pulse code modulation (PCM) upstream as defined in the V.92 ITU standard. This feature does, however, interoperate with modems that support PCM upstream.

---

Modem on Hold

V.92 Modem on Hold allows a dial-in customer to suspend a modem session to answer an incoming voice call or to place an outgoing call while engaged in a modem session. When the dial-in customer uses Modem on Hold to suspend an active modem session to engage in an incoming voice call, the Internet service provider (ISP) modem listens to the original modem connection and waits for the dial-in customer's modem to resume the connection. When the voice call ends, the modem signals the telephone system to end the second call and return to the original modem connection, then the modem signals the ISP modem that it is ready to resume the modem call. Both modems renegotiate the connection, and the original exchange of data continues.

---

Note This feature is designed for use on telephone lines that are configured for call-waiting service; call-waiting signals trigger the suspension of the modem session. If call-waiting service is not present on the subscriber's line, callers receive a busy signal, and the modem session is not interrupted.

---

Use of the V.92 Modem on Hold feature for Cisco MICA portware can be controlled globally using AT commands (modemcaps) or can be controlled on a per-caller basis using the RADIUS distributed client/server system.

---

Note You are not required to have a RADIUS server to use the Modem on Hold feature.

---

The following sections contain information about controlling the V.92 Modem on Hold feature:

•AT Commands (Modemcaps) and S-Registers

•RADIUS Authorization

AT Commands (Modemcaps) and S-Registers

V.92 Modem on Hold is disabled by default and is controlled with standard AT commands and S-registers. V.92 is enabled and disabled with the S29 S-register (S29 = 12), and Modem on Hold is controlled with the S62 S-register (S62 must be set to enable Modem on Hold). AT commands download the configuration to the modem at the end of every call. The ATSn=v and ATSn? AT commands are used to configure V.92 Modem on Hold on Cisco MICA platforms. Table 1 lists additional S-register parameters used to enable and disable the feature.

To disable V.92 Modem on Hold, you can use a modemcap (for example, s62=0s63=3s21=15s29=12) or set the S29 register to any number other than 12. You can also use the RADIUS vendor-specific attribute (VSA) to disable Modem on Hold if the feature was initially enabled by the default value (modemcap).

---

Note If the feature is enabled using S29=12 and Modem on Hold is disabled using S62=0, statistics for the number of times a dial-in customer requests an on-hold are tracked in the MOH link information parameters. However, completely disabling the feature by setting S29 to a value other than 12 disables the reporting of all MOH statistics.

---

For detailed information about the AT commands and S-registers used to control V.92 on Cisco MICA platforms, refer to the AT Command Set and Register Summary for MICA 6-Port Modules.

Table 1 V.92 Modem on Hold S-Registers 

Name	Register	Index	Default	Description
Modem standard	S29	MICA 19	12 (V.92 enabled)	0 = V.34bis Automode, with V.32ter 1 = V.34bis Automode, without V.32ter 2 = reserved 3 = V.32bis Automode 4 = V22bis Automode 5 = K56Flex 1.1 Automode 6 = V.90 Automode 7 = MICA:SS7/COT 8 = V.110 9 = Reserved 10 = Reserved 11 = Reserved 12 = V.92 Auto-mode
MOH timeout	S62	MICA 63	0	0:   MOH disabled 1:   10 seconds 2:   20 seconds 3:   30 seconds 4:   40 seconds 5:   1 minute 6:   2 minutes 7:   3 minutes 8:   4 minutes 9:   6 minutes 10:  8 minutes 11:  12 minutes 12:  16 minutes 13:  No limit

RADIUS Authorization

Per-user control of Modem on Hold can be configured for caller authorization using a RADIUS server. RADIUS servers use the vendor-specific attribute (VSA) capability to configure Modem on Hold for individual users. The current attribute=value protocol syntax has been extended with the new
Modem on Hold attribute. You can enter the following value for this attribute:

•An unsigned integer in the range 0 through 65,535—Represents the maximum number of seconds that a modem may remain on hold, which can range from ten seconds to an unlimited number of minutes.

---

Note Although the integer attribute values can be specified as any value in a contiguous range, V.92 specifications limit configuration to a limited set of values. Attribute values are rounded down to the next permitted value when they are used to configure a modem.

---

Alternatively, you can enter the inf keyword, which allows the modem to remain on hold indefinitely.

If the Modem on Hold configuration is not present, or if it is not syntactically correct, the modem uses its default configuration for Modem on Hold. The default operation can be modified by using a modemcap string. Following authentication of a dial-in user, an additional control command is sent to the modem if the dial-in user does not have a default Modem on Hold configuration.

---

Note Code space requirements for RADIUS support is less than 2KBs. There are no additional data space requirements.

---

V.92 Modem on Hold running on systems using RADIUS authorization increases the length of RADIUS response packets by approximately 20 bytes. RADIUS databases increase in size by approximately the same amount for each dial-in user with a nondefault Modem on Hold attribute value.

With RADIUS, authentication and authorization occur as part of the same process. When a caller connects to the access server, the caller enters a user ID and password in response to prompts from the access server. This information is formatted as a RADIUS request packet and is sent to the appropriate RADIUS server. If the user ID is valid and the password matches, the RADIUS server responds with a packet containing authorization data for the connection. This authorization data contains the Modem on Hold configuration if it is present in the RADIUS database.

The access server interprets the response from the RADIUS server and performs any actions associated with the authorization data. For Modem on Hold, a command is sent from the Cisco IOS host to the Cisco MICA channel to set the Modem on Hold parameters. No confirmation from the channel is required.

When the client modem requests a Modem on Hold operation, the modem switches to an on-hold state, which prevents further data from being queued to the connection. When the Cisco IOS software receives the request to go on hold, any transmit packets queued to local Cisco IOS queues (packets not already posted to the queues shared between the Cisco IOS software and the modem) are discarded. This mechanism reduces the possibility that stale data will be transmitted to the modem when the connection is reactivated. It also reduces the number of buffer resources that are tied up while a modem is on hold.

---

Note When using a RADIUS server, placement of commas is important. The asterisk in the modem-on-hold attribute indicates that the attribute is optional. If a modem does not support Modem on Hold, then the call might continue anyway. If the asterisk is replaced by an "=", the attribute is required, and modems that do not support Modem on Hold terminate the calls following authentication.
The value of the attribute is the number of seconds allowed for the on-hold state. This value is rounded by the Cisco IOS software to one of the permissible values. The number can be replaced with the inf command, which allows unlimited on-hold time. Case is significant for both attribute names and values.

---

---

Note If your router is configured for RADIUS, the RADIUS server must be accessible to the router. The server must also be capable of responding to authentication requests with VSA attributes.

---

Configuring V.92 Modem on Hold with RADIUS

If you use Radius to configure the Modem on Hold feature, use the modem-on-hold attribute, where the VALUE attribute is a nonnegative integer in seconds for maximum time on hold allowed. VALUE can be one of the following:

•modem-on-hold=VALUE—MOH support is required for call to be accepted.

•modem-on-hold*VALUE—MOH support is optional.

The following example shows RADIUS enabled where Modem on Hold is optional:

vendor-specific=9:1:modem-on-hold*VALUE

---

Note The examples shown below were established on the Cistron open-source server. Your server syntax may vary.

---

# This user can use MOH without time limits. (inf)

# MOH capability is not required for the connection (*)

testi Auth-Type = Local, Password = "test"

Service-Type = Login-User,

Cisco-AVPair = "modem-on-hold*inf"

# This user can use MOH for 30 seconds.

# MOH capability is not required for the connection.

test30 Auth-Type = Local, Password = "test"

Service-Type = Login-User,

Cisco-AVPair = "modem-on-hold*30"

# This user can not use MOH.

# MOH capability is not required for the connection.

test0 Auth-Type = Local, Password = "test"

Service-Type = Login-User,

Cisco-AVPair = "modem-on-hold*0"

# This user can not use MOH.

# But MOH capability IS required for the connection.

# If the user logs on to a device that does not support

# MOH (eg the console), he will be disconnected after

# authentication.

testr	 Auth-Type = Local, Password = "test"

	Service-Type = Login-User,

	Cisco-AVPair = "modem-on-hold=0"

# This user gets the default MOH setting.

# The default setting is disabled, unless overridden

# by a modemcap entry.

testx	 Auth-Type = Local, Password = "test"

	Service-Type = Login-User

# This user can go on hold for 60 seconds

# in a PPP link. The service type determines

# which calls get the MOH setting.

lucy Auth-Type = Local, Password = "test"

	Service-Type = Framed-User,

	Cisco-AVPair = "modem-on-hold*60"

---

Note The service type defines when the AVPair is applied. For different RADIUS servers, the Cisco-AVPair syntax might be different, but the value in quotes does not change. Case is important: The entire text in quotes must be lowercase.

---

For more information about using RADIUS, refer to the Configuring RADIUS documentation.

Modem Enhancements for V.92 Modem On Hold

The following modem enhancements have been made for the implementation of the
V.92 Modem on Hold feature:

•Disconnect Reasons

•Duration Limit Timer

•Modem on Hold Link Information Parameters

•Modem States

•New and Modified MIBs

Disconnect Reasons

V.92 Modem on Hold Disconnect Reasons is the method by which a modem tells the Cisco IOS software (host) why it has terminated its session with a client through the Modem on Hold cleardown by modem and the Modem on Hold timeout values. Table 2 lists the new Modem on Hold Disconnect Reasons.

Table 2 Modem On Hold Disconnect Reasons

Name	Description
DR_MOH_CLRD	Modem On Hold cleardown by modem
DR_MOH_TIMEOUT	Modem On Hold timeout value reached

Duration Limit Timer

The Modem on Hold duration limit timer is supported within dialed number ID service (DNIS), calling line ID (CLID), RADIUS (but not TACACS+), and global resource pool manager server (RPMS) virtual groups. This support permits ISPs to associate the Modem on Hold feature and its timer limit according to customer needs. When the Modem on Hold timer is active (a modem is on hold), it must take precedence over the idle timer. For example, if the idle value is five minutes and the Modem on Hold duration limit is ten minutes, the customer is permitted to be on another call for up to ten minutes without being disconnected after five minutes by the idle timer. The Modem on Hold timer value resets at the end of each on-hold session.

Modem on Hold Link Information Parameters

Table 3 Modem on Hold Link Information Parameters

Name	Description
MOH Status	0: Modem is not on hold 1: Modem is on hold
MOH Count	Number of times the modem is on hold
MOH Request Count	Number of times the modem received Modem on Hold requests.
Total MOH Time	Total holding time: 65,535 seconds maximum
Current MOH Time	Current holding time: 65,535 seconds maximum
Call Waiting Retrains	Number of times a retrain occurred due to a call-waiting signal

Modem States

This feature supports modem states, which are discrete states that a modem transitions through, during, and after negotiation with a client modem. These states include the Modem on Hold input state, the Steady input state, and the Steady, Steady Retrain, and Terminate output states.

New and Modified MIBs

Existing MIBs that show the status of modem settings have been extended to show V.92 Modem on Hold configuration status. New MIBs have been created to report the incidence of V.92 Modem on Hold request calls coming into the server and to monitor on-hold status.

Supported Module Firmware and Cisco IOS Software

V.92 Modem on Hold is supported on the following:

•Module Firmware—The module firmware is a combination of modem (Digital Signal Processor or DSP) firmware and the module controller firmware. It is responsible for the collection of statistics and the actual implementation of V.92, including additional required state transitions.

•Cisco IOS software—The Cisco IOS software is responsible for the control and statistics reporting of the new features, including modemcaps, RADIUS authorization, and command-line interface (CLI) support. See the "Related Documents" section for information about new Cisco IOS Release features.

•Boardware—On the Cisco AS5300 and Cisco AS5800 with Cisco MICA Portware Version 2.9.1.0 only. The boardware runs on the Amazon carrier card and provides the interface between Cisco IOS and the Cisco MICA module.

Benefits

Allows Voice Calls Without Interruption of Existing Modem Connection

V.92 Modem on Hold allows the origination and reception of voice calls without disturbing preexisting modem sessions. With Modem on Hold, calls can ring through to the dial-in user without requiring the expense of a second telephone line.

Per-Use Enabling

Service providers can enable Modem on Hold on a per-user basis for premium service opportunities.

Standard Modem Feature

V.92 is a standard modem feature that is offered as a no-cost upgrade to the installed system.

V.92 Compatibility

Modems that support V.92 are fully compatible with modems that do not support it. If a modem that supports Modem on Hold connects with a modem that does not support it, the modems will connect normally. However, the Modem on Hold function is not available for that call.

Restrictions

•Client modem vendors must supply their own utilities to enable Modem on Hold with each client modem.

•There is no standard method for notifying remote or user applications that a modem session has been placed on hold. Extending timeouts or increasing the maximum number of attempts to perform certain operations might be necessary. No e-mail data should be lost because of on-hold times.

•When a Modem on Hold transaction returns to the data-connected state, it retains the same IP network connection. Any other connected applications might not be returned to their prior state, depending on the application's data transaction requirements during the Modem on Hold active state.

•Configuration of these features using S-registers is carried out by using modemcaps (AT commands). Cisco IOS software does not check these values to guarantee that they are valid. The behavior of invalid values is determined by the module.

•Authorization of Modem on Hold is not provided as a standard service by RADIUS. However, RADIUS provides a vendor-specific attribute (VSA) capability that can be used to extend authorization mechanisms. This capability is already used by Cisco routers to provide other custom services.

•Cisco IOS software is packaged as multiple program image types with varying capabilities. Because not all modem interfaces support Modem on Hold and because images may be built to support specific modem types, not all software images contain functions to control Modem on Hold. In addition, the modems that do support Modem on Hold implement their control functions differently. Therefore, registry functions are used to interface between RADIUS, local authorization, and Modem on Hold control for modems.

•Server-initiated Modem on Hold is not supported.

•During a suspended modem session, some data might be dropped. The ISP idle timer, which disconnects a dial-in user if there is no data exchanged for a period of time, should be reset and suspended while a connection is on hold.

---

Note Many client modems used in Europe are known to have problems with the Modem on Hold feature. The vendors are aware of the issue and are working to correct it. If you are having trouble with the Modem on Hold feature in Europe, it is suggested that the customer contact the client modem vendor to verify that the modem complies with the telephony signaling for call waiting, caller ID, and 3-way calling in their particular country.

---

Related Features and Technologies

•V.92 Quick Connect

•V.44 LZJH data compression service

•Mindspeed CSMv6 hardware solution

Related Documents

•AT Command Set and Register Summary for MICA Six-Port Modules

•Call Tracker plus ISDN and AAA Enhancements for the Cisco AS5300

•Cisco AS5300 documentation index

•Cisco AS5800 documentation index

•Cisco IOS Release 12.2 Master Indexes

•Comparing NextPort SPE Commands to MICA Modem Commands

•New Features in Release 12.2(2)XB

•Release Notes for Cisco AS5300 Universal Access Servers, Cisco IOS Release 12.2(2)XA

•Release Notes for Cisco AS5300 Universal Access Servers, Cisco IOS Release 12.2(2)XB

•Cisco IOS Release 12.2T Cross-Platform Release Notes

•Cisco AS5800 Universal Access Server Release Notes

•Release Notes for Cisco MICA Portware Version 2.9.1.0 on Cisco AS5300 Universal Access Servers

•SPE and Firmware Download Enhancements

•V.44 LZJH Compression for Cisco AS5300 and Cisco AS5800 Universal Access Servers

•V.92 Quick Connect for Cisco AS5300 and Cisco AS5800 Universal Access Servers

Supported Platforms

•Cisco AS5300

•Cisco AS5800

Table 4 Cisco IOS Release and Platform Support for this Feature 

Platform	12.2(2)XA	12.2(2)XB	12.2XB1	12.2(11)T
Cisco AS5300	X	X	X	X
Cisco AS5800	Not supported	Not supported	X	X

Determining Platform Support Through Cisco Feature Navigator

Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.

Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.

To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions at http://www.cisco.com/register.

Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:

http://www.cisco.com/go/fn

Availability of Cisco IOS Software Images

Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.

Supported Standards, MIBs, and RFCs

Standards

•V.44

•V.92 Modem on Hold

•V.92 Quick Connect

MIBs

•CISCO-MODEM-MGMT-MIB

•CISCO-CALL-TRACKER-MODEM-MIB

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://tools.cisco.com/ITDIT/MIBS/servlet/index

If Cisco  MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:

http://www.cisco.com/register

RFCs

No new or changed RFCs are supported by this feature.

Prerequisites

•Cisco IOS Release 12.2(2)XA, 12.2(2)XB, or 12.2(11)T

•V.92 MOH Portware DSP program memory required (in 16-bit words): 500

•Less than 50k bytes needed for CP memory

•Basic configuration of the Cisco AS5300 or Cisco AS5800 universal access server

•Upgraded modem firmware (Cisco MICA portware 2.9.1.0)

•Modems must be capable of supporting Modem on Hold

Configuration Tasks

None

Monitoring and Maintaining Modem on Hold

Use the following show commands in privileged EXEC mode.

Command	Purpose
Router# show modem configuration	Displays the current modem configuration for digital Cisco MICA technologies modems.
Router# show modem log	Displays the event log with oldest event first.
Router# show modem operational-status	Displays the operational status of the specified ports or the specified port range.

Configuration Examples

None

Command Reference

This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.

•show modem configuration

•show modem log

•show modem operational-status

show modem configuration

To display the current modem configuration for digital Cisco MICA technologies modems loaded inside an access server or router, use the show modem configuration command in privileged EXEC mode.

show modem configuration [slot/port]

Syntax Descriptionshow port operational-status {slot | slot/port}

slot/port

(Optional) Specifies the location of a slot and modem port. If this number is not specified, statistics for all connected modems are displayed. Remember to include the forward slash (/) when entering this variable.

Defaults

No default behavior or values.

Command Modes

Privileged EXEC

Command History

Release	Modification
11.2P	This command was introduced on Cisco AS5400 and Cisco 5800 universal access servers running NextPort firmware.
12.1(5)T	This command was enhanced to display information about digital modems on the Cisco 3600 series that support V.110.
12.2(2)XA	This command was supported on Cisco AS5350 and Cisco AS5400 universal access servers running NextPort firmware. This command was supported on Cisco AS5300 universal access servers running Cisco MICA Portware Version 2.9.1.0.
12.2(2)XB	This command was supported with Cisco IOS Release 12.2(2)XB.
12.2(11)T	This command was integrated into Cisco IOS Release 12.2(11)T and support was added for Cisco AS5300 and Cisco AS5800 platforms.

Examples

The following example displays the operational status for modem 0/1 in a Cisco AS5300. This modem resides in slot 0 and is assigned to port number 1.

Router# show modem configuration 2/10 

Modem(2/10) Configuration Block:

 Country Code: 1

 Originate/Answer Mode: Answer

 Data Bits Selection: 8

 Parity Selection: 0

 Stop Bits Selection: 1

 V.42 ODP generation: Generate ODP sequence when originating a call

 Error Correction Autodetect Time-out value: 5000 ms

 Protocol Negotiation Time-out value: 10000 ms

 Protocol Negotiation Fallback Character: 

 Protocol Negotiation Retransmission Limit: 12

 Error Correction Frame Length: 256 bytes

 Data Compression: V.44Tx   V.44Rx

 ARA Error Correction: ARA1.0 & ARA2.0 Disabled

 V.42 Error Correction: V.42(LAP-M) Originate&Answer enabled

 MNP Error Correction: MNP Originate&Answer enabled

 Link Protocol Fallback: Asynchronous Framing (Start/Stop/Parity)

 DSP processor MVIP TDM slice: 0

 Calling Tone: Disabled

 Guard Tone: Disabled

 Modem Standard: V.90 Automode

 Max. Connect Rate: 33600 bps

 Min. Connect Rate: 300 bps

 Signal Quality Threshold: Bit Errors >=1:1000 cause recovery

 Fallback/Fallforward Squelch Timer: 500 ms

 Fall Forward Timer: 10000 ms

 Fall Back Timer: 500 ms

 Terminate Time-out: 20 second(s)

 Wait For Data Mode Time-out: 60 second(s)

 Lost Carrier To Hang-up Delay: 1400 ms

 Transmit Level Setting: -13 dBm

 Retrain Limit: 4

 V.34 Max. Symbol Rate: 3249 Baud

 V.34 Min. Symbol Rate: 2400 Baud

 V.34 Carrier Frequency: Auto Carrier Selection 

 V.34 Preemphasis Filter Selection: 11

 Tx and RX Signaling Type: NULL signaling

 Call Progress Tone Detection: No tone detection

 +++ Escape Detection: Enabled-Originate-Mode-Only

 AT Command Processor: Enabled

 Call Set Up Delay: no delay before link initiation

 Automatic Answer: delay 2 second(s)

 Escape Detection Character: ASCII 43 ('+')

 Carriage Return Character: ASCII 13 (CR)

 Line Feed Character: ASCII 10 (LF)

 Backspace Character: ASCII 8 (BS)

 Pause Before Blind Dialing: 2 second(s)

 Wait For Carrier After Dial: 60 second(s)

 Comma Dial Modifier Time: 2 second(s)

 Bit-mapped Register(S9=0x13D): E1Q2V1&D3X4

 Delay For Hangup After Carrier Loss: 1400 ms

 MOH Timeout: No limit

QC Config: Enabled  ANSpcm Level -12 dBm

V.44 Max Tx Codewords: 256

V.44 Max Rx Codewords: 256

V.44 Max Tx String Length: 32

V.44 Max Rx String Length: 32

V.44 Max Tx History Size: 256

V.44 Max Rx History Size: 256

Table 5 show modem configuration Field Descriptions for MICA Modems 

Field	Description
Modem slot/port	Slot and port for the specified modem.
Country code:	Transmit level limits with respect to the S39 register. Default is 1 (U.S. domestic).
Originate/Answer Mode:	Answer or originate. Default is answer.
Data Bits Selection:	7, 8, or 9 data bits. Default is 8.
Parity Selection:	0 = no parity, 1 = even parity, 2 = odd parity. Default is no parity.
Stop Bits Selection:	1 or 2 stop bits. Default is 1 stop bit.
V.42 ODP generation:	Disabled or generate ODP sequence when originating a V.42 call. Default is Generate ODP sequence when originating a V.42 call.
Error Correction Autodetect Time-out value:	Maximum period during which the modem will run an automated detection machine upon the incoming data. Default is 5000 ms.
Protocol Negotiation Time-out value:	Maximum wait for error correction protocol negotiation before fallback. Default is 10,000 ms.
Protocol Negotiation Fallback Character:	0 to 127. Default is 13.
Protocol Negotiation Retransmission Limit:	0 = Do not disconnect on excessive retransmission; 1 to 255 = number of successive retransmissions to cause disconnect. Default is 12.
Error Correction Frame Length:	Buffer length; 64 to 1024 octets of data. Default is 256.
Data Compression:	Disabled, V.42bis, MNP5, or V.42bis or MNP5 (V.42 has precedence). Default is V.42bis or MNP5 (V.42 has precedence).
ARA Error Correction:	ARA1.0 & ARA2.0 Disabled, Enabled for Answer only, Enabled for Answer originate ARA1.0, and Enabled for Answer originate ARA2.0. Default is Enabled for Answer only.
V.42 Error Correction:	V.42(LAP-M) Disabled, V.42(LAP-M) Originate & Answer enabled. Default is disabled.
MNP Error Correction:	MNP Disabled or MNP Originate and Answer enabled. Default is MNP Originate and Answer enabled.
Link Protocol Fallback:	Asynchronous framing (Start/Stop/Parity), Synchronous framing (Raw 8 bits to DSP), or Disconnect (Hang-up). Default is Asynchronous framing (Start/Stop/Parity).
DSP processor MVIP TDM slice:	0 to 15.
Calling Tone:	Disable or Send calling tone. Default is disable.
Guard Tone:	Guard tone disabled, Use Guard tone (V.22 & V.22bis only). Default is disabled.
Modem Standard:	V.34bis Automode with terbo, V.34bis Automode skip terbo, V.32 terbo Automode, V.32bis Automode, V.22bis Automode, or K56Flex 1.1. Default is V.34bis Automode with terbo.
Max. Connect Rate:	75 to 56000 bps.
Min. Connect Rate:	75 to 56000 bps.
Signal Quality Threshold:	No action on bit errors, Bit Errors >=1:100 cause recovery, Bit Errors >=1:1000 cause recovery, Bit Errors >=1:10000 cause recovery, Bit Errors >=1:100000 cause recovery, or Bit Errors >=1:1000000 cause recovery. Default is 1:1000.
Fallback/Fallforward Squelch Timer:	Time to delay after a speed shift before allowing another speed shift. Default is 500 ms.
Fall Forward Timer:	Elapsed time with continuous good signal quality to cause a fall forward. Default is 10,000 ms.
Fall Back Timer:	Elapsed time with bad signal quality to cause a fallback. Default is 500 ms.
Terminate Time-out:	Elapsed time after a disconnect request before forcing a link disconnect. During this period, the modem sends buffered data and then clears down the link. Default is 20 seconds.
Wait for Data Mode Time-out:	Maximum time during link establishment before disconnection. Default is 40; 60 for K56Flex.
Lost Carrier To Hang-up Delay:	Maximum time without a carrier to cause the link disconnect. Default is 1400 ms.
Transmit Level Setting:	6dBm, 7dBm, 8dBm, -20dBm, or -21dBm. Default is 9 dBm.
Retrain Limit:	Maximum successive failed retrains to cause the link to disconnect. Default is 4.
V.34 Max. Symbol Rate:	2400 baud, 2743 baud, 2800 baud, 3000 baud, 3200 baud, or 3429 baud. Default is 3429 baud.
V.34 Min. Symbol Rate:	2400 baud, 2743 baud, 2800 baud, 3000 baud, 3200 baud, or 3429 baud. Default is 2400 baud.
V.34 Carrier Frequency:	Low Carrier, High Carrier, or Auto Carrier Selection. Default is High Carrier.
V.34 Preemphasis Filter Selection:	0 to 10 = a selected filter; 11 = Automatic Preemphasis Selection. Default is 11.
Tx and Rx Signaling Type:	NULL signaling, MF signaling, DTMF signaling, Lower band R2 signaling, Upper band R2 signaling, or R1 signaling. Default is NULL signaling.
Call Progress Tone Detection:	No tone detection, Dial tone detection, Ring-Back tone detection, or Busy tone detection. Default is no tone detection.
+++ Escape Detection:	Disabled, Enabled, or Enabled-in-Originate-Mode-Only. Default is Enabled-in-Originate-Mode-Only.
AT Command Processor:	Disabled or Enabled. Default is disabled.
Call Set Up Delay:	No delay before link initiation, delay value (1 to 255). Default is no delay.
Automatic Answer:	Answer immediately, delay value (1 to 255 seconds). default is 1 second.
Escape Detection Character:	ASCII value (0 to 127). Default is 43.
Carriage Return Character:	ASCII value (0 to 127). Default is 13.
Line Feed Character:	ASCII value (0 to 127). Default is 10.
Backspace Character:	ASCII value (0 to 127). Default is 8.
Pause Before Blind Dialing:	2 to 255 seconds. Default is 2.
Wait For Carrier After Dial:	Wait for data mode timeout.
Comma Dial Modifier Time:	2 to 255 seconds. Default is 2.
Bit-mapped Register(S9=0x13D):	Bit mapped register.
Delay For Hang-up After Carrier Loss:	Lost carrier to hang-up delay.

Related Commands

Command	Description
show modem log	Displays the modem history event status performed on a manageable modem or group of modems.
show modem operational-status	Displays the statistics of the active session.

show modem log

To display the modem history event status performed on a manageable modem or group of modems, use the show modem log command in privileged EXEC mode.

show modem log [slot/port | group number]

Syntax Descriptionshow port operational-status {slot | slot/port}

slot/port	(Optional) Specifies the location of a slot and modem port. If this number is not specified, statistics for all connected modems are displayed. Remember to include the forward slash (/) when entering this variable.
group number	(Optional) Specifies the location of a specific group of modems. If this number is not specified, statistics for all modems in the access server are displayed. The group number range is between 1 and 200.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release	Modification
11.2	This command was introduced.
12.1(5)T	This command was enhanced to display information about the Cisco 3600 series digital modems that support V.110, and about the Cisco 2600 and Cisco 3600 series modems that support leased-line operation.
12.2(2)XA	Additional link info and states were added.
12.2(2)XB	This command was supported with Cisco IOS Release 12.2(2)XB.
12.2(11)T	This command was integrated into Cisco IOS Release 12.2(11)T and support was added for Cisco AS5300 and Cisco AS5800 platforms.

Examples

The following example displays the operational status for modem 0/1 in a Cisco AS5300. This modem resides in slot 0 and is assigned to port number 1.

Router# show modem log 0/1

Static event: 

    Connect Protocol:  LAP-M

    Compression:  V.44 both

    Connected Standard:  V.90

    TX,RX Symbol Rate:  8000, 3200

    TX,RX Carrier Frequency:  0, 1920

    TX,RX Trellis Coding:  0, 16

    Frequency Offset:  0 Hz

    Round Trip Delay:  0 msecs

    TX,RX Bit Rate:  49333, 31200

    Robbed Bit Signalling (RBS) pattern:  0

    Digital Pad:  0.0   dB,  Digital Pad Compensation: None

    QC Exchange: No QC Requested

    DC TX,RX Negotiated String Length: 32, 32

    DC TX,RX Negotiated Codewords: 256, 256

    DC TX,RX Negotiated History Size: 256, 256

    Diagnostic Code: 00 00 00 00 00 00 00 00

Dynamic event: 

    Sq Value:  3

    Signal Noise Ratio:  28 dB

    Receive Level:  -19 dBm

    Phase Jitter Frequency:  0 Hz

    Phase Jitter Level:  0 degrees

    Far End Echo Level:  -50 dBm

    Phase Roll:  0 degrees

    Total Retrains:  1

    EC Retransmission Count:  1

    Characters transmitted, received:  133, 188

    Characters received BAD:  4

    PPP/SLIP packets transmitted, received:  5, 5

    PPP/SLIP packets received (BAD/ABORTED):  0

    EC packets transmitted, received OK:  11, 19

    EC packets (Received BAD/ABORTED):  1

    V110/PIAFS frames received bad: 0

    V110/PIAFS frames received good: 0

    V110/PIAFS frames transmitted: 0

    V110/PIAFS sync lost: 0

    PIAFS RTF: 0

    Total Speedshifts: 0

    Total MOH Time: 0 secs

    Current MOH Time: 0 secs

    MOH Status: Modem is Not on Hold

    MOH Count: 0

    MOH Request Count: 0

    Retrains due to Call Waiting: 0

    DC Encoder,Decoder State: compressed/compressed

    DC Tx,Rx Compression Ratio                 :  0.00:1, 0.00:1

    DC Tx,Rx Dictionary Reset Count            :  0, 0  

    Diagnostic Code                         :  00 00 00 00 00 00 00 00

End Connect event: 

    Call Timer:  6683 secs

    Disconnect Reason Info:  (0x108)

       Type (=5 ):  Rx (line to host) data flushing, OK

      Class (=1 ):  DSP condition

     Reason (=8 ): Modem On Hold cleardown by modem

    Total Retrains:  24

    EC Retransmission Count:  73

    Characters transmitted, received:  1238, 1319

    Characters received BAD:  4

    PPP/SLIP packets transmitted, received:  18, 18

    PPP/SLIP packets received (BAD/ABORTED):  0

    EC packets transmitted, received OK:  37, 78

    EC packets (Received BAD/ABORTED):  73

    V110/PIAFS frames received bad: 0

    V110/PIAFS frames received good: 0

    V110/PIAFS frames transmitted: 0

    V110/PIAFS sync lost: 0

    TX,RX Bit Rate: 26400, 28800

    Total Speedshifts: 0

    Total MOH Time: 0 secs

    Current MOH Time: 0 secs

    MOH Status: Modem is Not on Hold

    MOH Count: 0

    MOH Request Count: 0

    Retrains due to Call Waiting: 0

    DC Encoder,Decoder State: compressed/compressed

    DC TX,RX Compression Ratio: 0.0/0.0

    DC Tx,Rx Dictionary Reset Count            :  0, 0  

    Diagnostic Code                         :  00 00 00 00 00 00 00 00

Modem State event:

     State: Idle

     State: Call Setup

     State: Connect

     State: Link

     State: Quick Connect

     State: Train Up

     State: EC Negotiating

     State: Steady

     State: Steady Retrain

     State: Steady Speedshift

     State: Steady Escape

     State: Terminate

     State: Modem On Hold

   State: Steady QC

     State: V.8bis Exchange

     State: Ranging

     State: Ranging Short

     State: Half Duplex Train

Table 6 show modem log Field Descriptions for MICA Modems 

Field	Event State	Description
Modem <slot/port> Events Log:		The modem for which log events are currently displayed.
00:00:00:		Identifies the time elapsed since each MICA modem event was performed (for example, 01:02:41 means the modem event occurred 1 hour, 2 minutes, and 41 seconds ago).
Startup event:		Type of specified MICA modem.
Modem firmware:		Modem firmware version.
RS232 event:		Detected modem signaling event.
ISDN outgoing called number:		Outgoing ISDN phone number dialed by the specified MICA modem.
Modem State Event	Current state of the MICA modem, which can be any of the following:
	Connect	Modem is connected to a remote host.
	Open	Open modem event.
	Link	Link protocol event occurred.
	Training	Modem retraining event.
	EC correction	Error correction frames transmitted or received.
	Steady	Steady modem event.
	Bad	Inoperable state, which is configured by the modem bad command.
	Bad*	Inoperable state, which is configured by the modem startup-test command during initial power-up testing.
	Reset	Modem is in reset mode.
	D/L	Modem is downloading firmware.
	Bad FW	Downloaded modem firmware is not operational.
	Busy	Modem is out of service and not available for calls.
	Idle	Modem is ready for incoming and outgoing calls.
Static event:	Current static event of the MICA modem, which can be any of the following:
	Connect protocol	Connection protocol used for the current session, which can be SYNC mode, ASYNC mode, ARA1.0, ARA2.0, LAP-M, or MNP.
	Compression	Type of compression used for the current session, which can be None, V.42bis TX, V.42bis RX, V.42bis both, or MNP5 data compression.
	Connected standard	Standards protocol used to connect, which can be V.21, Bell103, V.22, V.22bis, Bell212, V.23, V.32, V.32bis, V.32terbo, V.34, V.34+, or K56Flex 1.1.
	TX, RX symbol rate	Symbol rate used to send samples to the line or receive samples off of the line.
	TX, RX carrier frequency	Carrier frequency used by the remote service provider.
	TX, RX trellis coding	Trellis coding received and transmitted.
	Frequency offset	+/-32 in 1/8 Hx steps.
	Round trip delay	Total round trip propagation delay of the link, which is expressed in milliseconds.
	TX, RX bit rate	For RX, the bit rate from the remote service provider to the local service provider. For TX, the bit rate from the local service provider to the remote service provider.
Dynamic event:	Current dynamic event of the MICA modem, which can be any of the following:
	Sq value	Signal quality value, which can be between 0 and 7 (0 is the worst possible quality).
	Signal noise ratio	Expressed in decibels, which can be between 0 and 70 dB steps.
	Receive level	Expressed in decibels, which can be between 0 and -128 dBm steps.
	Phase jitter frequency	+/-32 in 1/8 Hz steps.
	Phase jitter level	0 to 90 degrees.
	Far end echo level	0 to -90 in dBm of far end echo level (that portion of the transmitted analog signal that has bounced off the remote modem's analog front end).
	Phase roll	+/-32 in 1/8 Hz steps.
	Total retrains	Count of total retrains.
	EC retransmission	Count of total error correction retransmissions that occurred during the duration of the link.
	Characters received, transmitted	Count of total characters received and transmitted.
	Characters received BAD	A subset of the above total (Characters received, transmitted). Represents the total number of parity error characters.
	PPP/SLIP packets received, transmitted	Total count of PPP/SLIP packets transmitted and received. This total could include all PPP/SLIP packets, including BAD/ABORTED packets.
	PPP/SLIP packets received, (BAD/ABORTED)	Total count of the bad or aborted PPP/SLIP packets, which is a subset of the above (PPP/SLIP packets received, transmitted).
	EC packets transmitted, received	Count of total error correction frames transmitted or received. This total could include all error correction packets, including BAD/ABORTED packets.
	EC packets (received BAD/ABORTED)	Total count of the bad or aborted error correction packets, which is a subset of the above (EC packets transmitted, received).

Related Commands

Command	Description
show modem configuration	Displays the current modem configuration.
show modem operational-status	Displays the statistics of the active session.

show modem operational-status

To display the active session's statistics, use the show modem operational-status command in privileged EXEC mode.

For Cisco 3600 series and Cisco AS5300 universal access servers:

show modem operational-status {slot | slot/port}

For Cisco AS5800 universal access servers:

show modem operational-status [shelf/