Table Of Contents
AT Commands (Modemcaps) and S-Registers
Configuring V.92 Modem on Hold with RADIUS
Modem Enhancements for V.92 Modem On Hold
Supported Module Firmware and Cisco IOS Software
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Monitoring and Maintaining Modem on Hold
show spe modem disconnect-reason
V.92 Modem on Hold for Cisco AS5350, Cisco AS5400, and Cisco AS5850 Universal Gateways and Cisco AS5800 Universal Access Servers
Feature History
This feature module introduces the V.92 International Telecommunication Union Telecommunication Standardization Sector (ITU-T) standard Modem on Hold (MOH) feature on NextPort/DFC-108NP-bearing platforms for use with Cisco IOS Releases 12.2(2)XB1 and 12.2(11)T.
This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
•
Monitoring and Maintaining Modem on Hold
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. These new modem protocols and standards are implemented at the modem level.
This feature module introduces the V.92 Modem on Hold feature on Cisco AS5350, Cisco AS5400, and Cisco AS5850 universal gateways and Cisco AS5800 universal access servers.
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 AS5350, Cisco AS5400, and Cisco AS5850 Universal Gateways 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.
NextPort firmware provides V.92 capabilities bundled with existing NextPort features. The NextPort Dial Feature Card (DFC-108NP) is responsible for the ITU implementation of V.92 and the collection of statistics related to the new features, including the new Modem States that occur with the additional negotiations for V.92. The statistics are collected by the dial feature card (DFC) but are passed to and stored in Cisco IOS software. Cisco IOS software is responsible for controlling the features and displaying the new statistics.
The Cisco AS5800 uses the NextPort high density dial termination card to implement this feature. Both voice and dial technologies are supported when used in a Cisco 5850 universal gateway.
Note
V.92 is packaged with V.44 in Cisco IOS software. For more information about V.44, refer to theV.44 LZJH Compression for Cisco AS5350, Cisco AS5400, and Cisco AS5850 Universal Gateways and Cisco AS5800 Universal Access Servers feature module.
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, other callers receive a busy signal, and the modem session is not interrupted.
Use of the V.92 Modem on Hold feature for Cisco NextPort firmware 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
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 NextPort 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 NextPort platforms, refer to the AT Command Set and Register Summary for NextPort Platforms.
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 NextPort 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:•
Modem on Hold Link Information Parameters
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 DescriptionDR_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
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 firmware and software:
•
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.
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 NextPort Platforms
•
Cisco AS5350 documentation index
•
Cisco AS5400 documentation index
•
Cisco AS5800 documentation index
•
Cisco AS5850 documentation index
•
Cisco AS5800 Universal Access Server Release Notes
•
Cisco IOS Release 12.2 Master Indexes
•
Comparing NextPort SPE Commands to MICA Modem Commands
•
Managing Port Services on the Cisco AS5400 Universal Gateway
•
Managing and Troubleshooting the NextPort Dial Feature Card
•
New Features in Release 12.2(2)XB
•
NextPort Port Service Management for the Cisco AS5400 Universal Gateway
•
Release Notes for Cisco AS5350 Universal Gateways for Cisco IOS Release 12.2 XA
•
Release Notes for Cisco AS5350 and AS5350HPX Universal Gateways for Cisco IOS Release 12.2 XB
•
Cisco IOS Release 12.2T Cross-Platform Release Notes
•
SPE and Firmware Download Enhancements
•
V.44 LZJH Compression for Cisco AS5350 and Cisco AS5400 Universal Gateways
•
V.92 Quick Connect for Cisco AS5350 and Cisco AS5400 Universal Gateways
Supported Platforms
•
Cisco AS5350
•
Cisco AS5400
•
Cisco AS5800
•
Cisco AS5850
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 quickly 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.
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:
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:
RFCs
No new or changed RFCs are supported by this feature.
Prerequisites
•
Cisco IOS Release 12.2(2)XB1 or 12.2(11)T.
•
Minimum of 32K memory needed for bundled Cisco NextPort firmware
•
Additional data space needed on the modem module (refer to Cisco NextPort documentation)
•
Basic configuration of the Cisco AS5350, Cisco AS5400, Cisco AS5800, or Cisco AS5850
•
Upgraded modem firmware
•
NextPort DFC installed
•
Modems must be capable of supporting Modem on Hold
Configuration Tasks
None
For additional information, refer to the following documents:
•
V.44 LZJH Compression for Cisco AS5350, Cisco AS5400, and Cisco AS5850 Universal Gateways and Cisco AS5800 Universal Access Servers
•
V.92 Quick Connect for Cisco AS5350, Cisco AS5400, and Cisco AS5850 Universal Gateways and Cisco AS5800 Universal Access Servers
Monitoring and Maintaining Modem on Hold
Use the following show commands in privileged EXEC mode.
Command PurposeRouter# show spe modem active
Displays the modem service statistics of all active calls on specified service processing elements (SPEs).
Router# show spe modem disconnect-reasonDisplays the digital disconnect reasons for the specified SPE or SPE range.
Router# show port operational-status
Displays the operational status of the specified ports or the specified port range.
Router# show port modem log
Displays the event log with oldest event first.
Router# show port configuration
Displays the configuration information for specified ports or the specified port range.
Router# show spe modem csr
Displays the call success rate (CSR) for the specified SPEs.
Router# show spe modem summary
Displays the modem service history statistics for specified SPEs.
Router# show call calltracker active
Displays the port level information stored within the Call Tracker active database for all active modem calls.
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 spe modem disconnect-reason
show call calltracker active
To display all information stored within the Call Tracker active database for all active calls, use the show call calltracker active command in privileged EXEC mode.
show call calltracker active [category [isdn | modem | other | v110 | v120]]
Syntax Description
Defaults
Specific activity and configuration information is not displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command allows you to display call activity for a single supported call category type, if desired, by using the category keyword with one of the optional keywords.
The Call Tracker feature is enabled by entering the calltracker enable command. If there is no call on the specified port, the information of the most recent call is displayed. The show calltracker active command shows all calls, regardless of type, unless specified by the category option field.
(For detailed information about the Call Tracker feature, refer to the Cisco IOS Call Tracker feature module.)
Examples
The following example shows Call Tracker activity for modem calls:
Router# show call calltracker active category modem-------------------------- call handle=0000000058 --------------------------status=Active, service=PPP, origin=Answer, category=ModemDS0 slot/cntr/chan=0/0/22, called=71071, calling=6669999userid=maverick5200, ip=172.19.4.2, mask=255.255.255.0setup=10/16/1999 18:29:20, conn=0.10, phys=17.00, service=24.71, authen=24.71init rx/tx b-rate=28800/33600, rx/tx chars=0/0resource slot/port=1/1, mp bundle=0, charged units=0, account id=75idb handle=0x6185B968, tty handle=0x612F8598, tcb handle=0x0----------------------------------------------------------------------------protocol: last=LAP-M, attempted=LAP-Mcompression: last=V.42bis-Both, supported= V.42bis-RX V.42bis-TXstandard: last=V.34+, attempted=V.34+, initial=V.34+snr=35 dB, sq=3, rx/tx level=-16/-15 dBmphase jitter: freq=0 Hz, level=0 degreesfar end echo level=-83 dBm, freq offset=0 Hzphase roll=-99 degrees, round-trip delay=1 msecsdigital pad=None dB, digital pad comp=0rbs pattern=0, constellation=16 pointrx/tx: symbol rate=3429/3429, carrier freq=1959/1959rx/tx: trellis code=0/0, preemphasis index=6/0rx/tx: constellation shape=Off/On, nonlinear encode=Off/Onrx/tx: precode=Off/On, xmit level reduct=2/2 dBmrx/tx: chars=0/0, general info=0x0rx/tx: link layer chars=0/0, NAKs=0/0error corrected: rx/tx=0/0, rx bad=0ec retransmissions=0, retransmitted frames=0rx/tx ppp slip=0/0, bad ppp slip=0rx/tx b-rate: last=28800/33600, lowest=28800/33600, highest=28800/33600phase 2 projected max rx b-rate: client=19200, host=24000phase 4 desired rx/tx b-rate: client=28800/33600, host=28800/33600retrains: local=0, remote=0, failed=0speedshift: local up/down=0/0, remote up/down=0/0, failed=0v110: rx good=0, rx bad=0, tx=0, sync lost=0SS7/COT status=0x00v90: status=No Attempt, client=(n/a), failure=Nonerx/tx: max neg I frame=128/128, neg window=15/15v42bis size: dictionary=1024, string=64T401 timeouts=0, tx window closures=0, rx overruns=0test err=0, reset=0, v0 synch loss=0mail lost: host=0, sp=0duration(sec)=16, disc reason=0x0disc text=(n/a)--------5---------10--------15--------20--------25--------30line shape : 0x1920212120202120202021202020202020202020201F1D191100v8bis capab : 0x00000000000000000000000000000000000000000000v8bis mod sl: 0x00000000000000000000000000000000000000000000v8 jnt menu : 0x01E0C14513942A000000000000000000000000000000v8 call menu: 0x01C14513942A00000000000000000000000000000000v90 training: 0x00000000v90 sgn ptrn: 0x00000000state trnsn : 0x00010203041020404243FF000000000000000000000000000000000000000000portwre diag: 0x00000000000000000000000000000000phase 2 info: 0x010000F4EF221FF37E0001E4EFA21FF2E30001A4EF980101B7CF98003C0000000024EF40000502160AE0304DFFFECE07A707A70D650D6500phase 4 info: 0x01834070808340708000Related Commands
show port configuration
To display the configuration information for specified ports or the specified port range, use the
show port configuration command in privileged EXEC mode.Cisco AS5400 with NextPort DFC
show port config {slot | slot/port}
Cisco AS5800 with Universal Port Card
show port config {shelf/slot | shelf/slot/port}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The port should have an associated active session when the show port configuration command is entered.
Examples
The following example shows output from the show port configuration command on the Cisco AS5400 with NextPort dial feature card (DFC). This example shows port configuration for the modem service port slot 1, port 0.
Router# show port configuration 1/0Service Type :Modem serviceOriginate/Answer Mode :AnswerData Bits Selection :8Parity Selection :No ParityStop bits Selection :1V.42 ODP generation :EnabledEC Autodetect Time-out :5000 msProtocol Negotiation Time-out :10000 msProtocol Negotiation Fallback character :13Protocol Negotiation Retransmission Limit :12EC Min, Max Octets Frame length :256Data Compression :V.44Tx V.44RxARA Error Correction :ARA1.0 & ARA2.0 DisabledV.42 Error Correction :V.42(LAP-M) Originate&Answer enabledMNP Error Correction :MNP Originate&Answer enabledLink Protocol Fallback :Async Framing (Start/Stop/Parity)Calling Tone :DisabledGuard Tone :DisabledModem Standard :V.90 AutomodeMax Non-PCM Connect Rate :33600 bpsMin Non-PCM Connect Rate :300 bpsMax PCM Connect Rate :60000 bpsMin PCM Connect Rate :28000 bpsSignal Quality Threshold :Bit Errors >= 1:1000 cause recoveryFallback/Fallforward Squelch Timer :500 msFall Forward Timer :10000 msFall Back Timer :500 msTerminate Time-out :20 secsWait for Data Mode Time-out :60 secsLost Carrier To Hang-up Delay :1400 msPCM Transmit Level Setting :-13 dBmRetrain Limit :4V.34 Max Symbol Rate :3429 BaudV.34 Min Symbol Rate :2400 BaudV.34 Carrier Frequency :Auto Carrier SelectionV.34 Preemphasis Filter Selection :11+++ Escape Detection :Enabled-in-Originate-Mode-OnlyAT Command Processor :EnabledCall Setup Delay :0 msAutomatic Answer Delay :2 secsEscape 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 secsComma Dial Modifier Time :2 secsMOH Timeout :No limitQC Configuration :Enabled ANSpcm Level -12dBmV.44 Max Tx Codewords :256V.44 Max Rx Codewords :256V.44 Max Tx String Length :32V.44 Max Rx String Length :32V.44 Max Tx History Size :256V.44 Max Rx History Size :256The following example shows port configuration information for a digital service port slot 2, port 23 on the Cisco AS5800 with universal port card.
Router# show port configuration 1/8Shelf/Slot/SPE/Port -- 1/8/27/165Service Type : Modem serviceOriginate/Answer Mode : AnswerData Bits Selection : 8Parity Selection : No ParityStop bits Selection : 1V.42 ODP generation : EnabledEC Autodetect Time-out : 5000 msProtocol Negotiation Time-out : 10000 msProtocol Negotiation Fallback character : 13Protocol Negotiation Retransmission Limit : 12EC Min, Max Octets Frame length : 256Data Compression : V.42bis or MNP5ARA Error Correction : ARA1.0 & ARA2.0 DisabledV.42 Error Correction : V.42(LAP-M) Originate&Answer enabledMNP Error Correction : MNP Originate&Answer enabledLink Protocol Fallback : Async Framing (Start/Stop/Parity)Calling Tone : DisabledGuard Tone : DisabledModem Standard : V.90 AutomodeMax Non-PCM Connect Rate : 33600 bpsMin Non-PCM Connect Rate : 300 bpsMax PCM Connect Rate : 60000 bps
Related Commands
Command DescriptionDisplays the operational status of the specified ports or a specified range of ports.
show port modem log
To display the events generated by the modem sessions, use the show port modem log command in privileged EXEC mode.
Cisco AS5400 with NextPort DFC
show port modem log [reverse slot/port] [slot | slot/port]
Cisco AS5800 with Universal Port Card
show port modem log [reverse shelf/slot/port] [shelf/slot | shelf/slot/port]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The port modem test log displays the results of the service processing element (SPE) diagnostics tests.
Examples
Link Info and States are the affected changes in the modem log with this feature. The states are shown in numeric order. The following example shows port events status on slow 1, port 0.
Router# show port modem logPort 1/0 Events LogModem Static event:Connect Protocol : LAP-MCompression : V.44Connected Standard : V.34+TX,RX Symbol Rate : 3429, 3429TX,RX Carrier Frequency : 1959, 1959TX,RX Trellis Coding : 16/16Frequency Offset : 0 HzRound Trip Delay : 0 msecsTX,RX Bit Rate : 31200, 28800Robbed Bit Signalling (RBS) pattern : 0Digital Pad : NoneDigital Pad Compensation : NoneMNP10EC : MNP10EC not activeQC Configuration : No QC RequestedDC Negotiated Tx,Rx String Length : 142, 142DC Negotiated Tx,Rx Codewords : 2048, 2048DC Negotiated Tx,Rx History Size : 10240, 10240Diagnostic Code : 00 00 00 00 00 00 00 00Modem Dynamic event:Sq Value : 6Signal Noise Ratio : 37 dBReceive Level : -12 dBmPhase Jitter Frequency : 2 HzPhase Jitter Level : 2 degreesFar End Echo Level : -90 dBmPhase Roll : 0 degreesTotal Retrains : 0EC Retransmission Count : 0Characters transmitted, received : 0, 0Characters received BAD : 0PPP/SLIP packets transmitted, received : 0, 0PPP/SLIP packets received (BAD/ABORTED) : 0EC packets transmitted, received OK : 0, 0EC packets (Received BAD/ABORTED) : 0Total Speedshifts : 0MOH Status : MOH OffMOH Count : 0MOH Request Count : 0Total MOH Time : 0 secsCurrent MOH Time : 0 secsCall Waiting Retrains : 0DC Encoder,Decoder Stat : Compressed, CompressedDC Tx,Rx Compression Ratio : 0.00:1, 0.00:1DC Tx,Rx Dictionary Reset Count : 0, 0Diagnostic Code : 00 00 00 00 00 00 00 00Modem End Connect event:Call Timer : 31 secsDisconnect Reason Info : 0x108Type (=4 ): Rx (line to host) data flushing - OKClass (=1 ): DSP conditionReason (=8 ): Modem On Hold cleardown by modemTotal Retrains : 0EC Retransmission Count : 1Characters transmitted, received : 3, 105Characters received BAD : 0PPP/SLIP packets transmitted, received : 0, 0PPP/SLIP packets received (BAD/ABORTED) : 0EC packets transmitted, received OK : 3, 8EC packets (Received BAD/ABORTED) : 0Total Speedshifts : 0MOH Status : MOH OffMOH Count : 0MOH Request Count : 0Total MOH Time : 0 secsCurrent MOH Time : 0 secsCall Waiting Retrains : 0DC Tx,Rx Compression Ratio : 0.00:1, 0.00:1DC Tx,Rx Dictionary Reset Coun : 0, 0Diagnostic Code : 00 00 00 00 00 00 00 00Modem State event:State: IdleState: ConnectState: LinkState: Quick ConnectState: Train UpState: EC NegotiatingState: SteadyState: Steady RetrainState: Steady SpeedshiftState: Steady EscapeState: TerminateState: Modem On HoldState: Steady QCState: V.8bis ExchangeState: RangingState: Ranging ShortState: Half Duplex TrainThe following is sample output for the Cisco AS5800 with universal port card. This example shows the port history event log for slot 8, ports 0 to 6:
Router# show port modem log 1/8/0 1/8/6Port 1/08/00 Events Log09:09:53: Service Type: DATA_FAX_MODEM09:09:53: Service Mode: DATA_FAX_MODEM09:09:53: Session State: FLUSHING09:09:53: Service Type: DATA_FAX_MODEM09:09:53: Service Mode: DATA_FAX_MODEM09:09:53: Session State: IDLE09:09:53: Modem State event:State: Terminate09:09:53: Modem End Connect event:Call Timer : 26 secsDisconnect Reason Info : 0x1F00Type (=0 ): <unknown>Class (=31 ): Requested by hostReason (=0 ): non-specific host disconnectTotal Retrains : 0EC Retransmission Count : 0Characters transmitted, received : 2633, 485Characters received BAD : 0PPP/SLIP packets transmitted, received : 0, 0PPP/SLIP packets received (BAD/ABORTED) : 0EC packets transmitted, received OK : 27, 21EC packets (Received BAD/ABORTED) : 009:09:54:Modem Link Rate event:09:09:55: Service Type: DATA_FAX_MODEM09:09:55: Service Mode: DATA_FAX_MODEM09:09:55: Session State: IDLE09:09:55: Service Type: DATA_FAX_MODEM09:09:55: Service Mode: DATA_FAX_MODEM09:09:55: Session State: ACTIVE09:09:55: Modem State event:State: Connect09:09:55: Modem State event:State: Link09:09:55: Modem State event:State: Train Up09:09:55: Modem State event:State: EC Negotiating09:09:55: Modem State event:State: Steady09:09:55: Modem Static event:Connect Protocol : LAP-MCompression : V.42bisConnected Standard : V.34+TX,RX Symbol Rate : 3429, 3429TX,RX Carrier Frequency : 1959, 1959TX,RX Trellis Coding : 16/16Frequency Offset : 0 HzRound Trip Delay : 1 msecsTX,RX Bit Rate : 31200, 28800Robbed Bit Signalling (RBS) pattern : 0Digital Pad : NoneDigital Pad Compensation : None4 bytes of link info not formatted : 0x00 0x00 0x00 0x00 0x0009:09:56: Modem Dynamic event:Sq Value : 5Signal Noise Ratio : 38 dBReceive Level : -15 dBmPhase Jitter Frequency : 13 HzPhase Jitter Level : 0 degreesFar End Echo Level : -90 dBmPhase Roll : 0 degreesTotal Retrains : 0EC Retransmission Count : 0Characters transmitted, received : 0, 0Characters received BAD : 0PPP/SLIP packets transmitted, received : 0, 0PPP/SLIP packets received (BAD/ABORTED) : 0EC packets transmitted, received OK : 0, 0EC packets (Received BAD/ABORTED) : 009:09:58: Service Type: DATA_FAX_MODEM09:09:58: Service Mode: DATA_FAX_MODEM09:09:58: Session State: FLUSHING09:09:58: Service Type: DATA_FAX_MODEM09:09:58: Service Mode: DATA_FAX_MODEM09:09:58: Session State: IDLE09:09:58: Modem State event:State: Terminate...Table 6 describes the significant fields shown in the displays.
Related Commands
show port operational-status
To display the active session's statistics, use the show port operational-status privileged EXEC command.
Cisco AS5400 with NextPort DFC
show port operational-status {slot | slot/port}
Cisco AS5800 with Universal Port Card
show port operational-status {shelf/slot | shelf/slot/port}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays the operational status of a specific port or range of ports. The port should have an associated active modem session when the command is entered.
Examples
The following example displays operational status for port 1 located in slot 2, with SPE 0 on a Cisco AS5400 with NextPort DFC:
5400# show port operational-status 2/1Slot/SPE/Port -- 2/0/1Service Type :Modem serviceDisconnect Reason Info :0x109Type (=4 ): Rx (line to host) data flushing - OKClass (=1 ): DSP conditionReason (=9 ): Modem On Hold timeout value reachedModulation Standard :V.34+TX/RX Bit Rate :31200/14400Connect Protocol :LAP-MCompression :V.44Call Timer :47 secsLink Signal Quality :7SNR :37 dBTX/RX Symbol Rate :3429/3429TX/RX Carrier Frequency :1959/1959TX/RX Trellis Coding :16/16TX/RX Preemphasis Index :0/1TX/RX Constellation Shaping :On-Active/On-ActiveTX/RX Nonlinear Encoding :On-Active/On-ActiveTX/RX Precoding :On-Active/On-ActiveTX/RX Xmit Level Reduction :3/1 dBmReceive Level :-15 dBmFrequency Offset :0 HzPhase Jitter Frequency :2 HzPhase Jitter Level :2 degreesFar End Echo Level :-90 dBmPhase Roll :0 degreesRound Trip Delay :0 msecsTotal Retrains :0Self Test Error count :0EC Retransmission count :0EC packets transmitted/received OK :11/12EC packets (Received BAD/ABORTED) :0Characters transmitted/received :76/13Characters received BAD :0PPP/SLIP packets transmitted/received :0/0PPP/SLIP packets received (BAD/ABORTED) :0Total Speedshifts : 0Total MOH Time : 0 secsCurrent MOH Time : 0 secsMOH Status : MOH OffMOH Count : 0MOH Request Count : 0Call Waiting Retrains : 0DC Encoder,Decoder State : Compressed, CompressedDC Tx,Rx Compression Ratio : 0.00:1, 0.00:1DC Tx,Rx Dictionary Reset Count : 0, 0Diagnostic Code : 00 00 00 00 00 00 00 00RBS Pattern :0Digital Pad :0Digital Pad Compensation :0The following example displays operational status for a V.110 digital service for the Cisco AS5400 on slot 2, SPE 3, port 23:
Router# show port operational-status 2/23slot/spe/Port -- 2/3/23Service Type : Digital serviceConnect Protocol : V110Data Bits : 8Parity : 0Stop Bits : 1TX/RX Bit Rate : 19200/19200Call Timer : 116 secsEC packets transmitted/received OK : 0/0EC packets (Received BAD/ABORTED) : 0PPP/SLIP packets transmitted, received : 8/8PPP/SLIP packets received (BAD/ABORTED) : 0Sync Loss : 0The following example shows output from the show port operational-status command for the Cisco AS5800 on shelf 1, slot 8:
Router# show port operational-status 1/8Shelf/Slot/SPE/Port -- 1/8/32/194Service Type : Modem serviceDisconnect Reason Info : 0x0Type (=0 ): <unknown>Class (=0 ): OtherReason (=0 ): no disconnect has yet occurredModulation Standard : V.34+TX/RX Bit Rate : 31200/31200Connect Protocol : LAP-MCompression : V.42bisCall Timer : 18 secsLink Signal Quality : 6SNR : 38 dBTX/RX Symbol Rate : 3429/3429TX/RX Carrier Frequency : 1959/1959TX/RX Trellis Coding : 16/16TX/RX Preemphasis Index : 0/1TX/RX Constellation Shaping : Off-None/On-ActiveTX/RX Nonlinear Encoding : Off-None/On-ActiveTX/RX Precoding : Off-None/On-ActiveTX/RX Xmit Level Reduction : 6/5 dBmReceive Level : -15 dBmFrequency Offset : 0 HzPhase Jitter Frequency : 5 HzPhase Jitter Level : 2 degreesFar End Echo Level : -90 dBmPhase Roll : 0 degreesRound Trip Delay : 1 msecsTotal Retrains : 0Self Test Error count : 0EC Retransmission count : 1EC packets transmitted/received OK : 34/14EC packets (Received BAD/ABORTED) : 0Characters transmitted/received : 9393/355Characters received BAD : 0PPP/SLIP packets transmitted/received : 0/0PPP/SLIP packets received (BAD/ABORTED) : 0RBS Pattern : 0Digital Pad : 0Digital Pad Compensation : 0...Table 7 describes the significant fields shown in the displays.
Related Commands
show spe modem active
To display the modem service statistics of all active calls on specified service processing elements (SPEs), use the show spe modem active command in privileged EXEC mode.
Cisco AS5400 with NextPort DFC
show spe modem active {slot | slot/spe}
Cisco AS5800 with Universal Port Card
show spe modem active {shelf/slot | shelf/slot/spe}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show spe modem active command on the Cisco AS5400 with NextPort DFC.This example displays active modem statistics for slot 5, SPE 6:
Router# show spe modem active 5/6SPE 5/06Port Type Prot Comp Duration Tx/Rx Tx/Rx(Lvl) SNR Cfg Retrain37 V.90 LAP-M V.42bis 95 3890/76 --/-11 38 In 0The following is sample output from the show spe modem active command on the Cisco AS5800 with universal port card. This example displays active modem statistics for shelf 1, slot 8:
Router# show spe modem active 1/8SPE 1/08/34Port Type Prot Comp Duration Tx/Rx(bps) Tx/Rx(Lvl) SNR Cfg Retrain209 V.34+ LAP-M V.42bis 23 28800/31200 --/-13 37 In 0SPE 1/08/35Port Type Prot Comp Duration Tx/Rx(bps) Tx/Rx(Lvl) SNR Cfg Retrain215 V.34+ LAP-M V.42bis 12 28800/31200 --/-13 37 In 0SPE 1/08/36Port Type Prot Comp Duration Tx/Rx(bps) Tx/Rx(Lvl) SNR Cfg Retrain216 V.34+ LAP-M V.42bis 24 33600/31200 --/-36 38 In 0217 ## ## ## 0 33600/300 --/19 37 In 0218 ## ## ## 0 33600/300 --/19 37 In 0219 ## ## ## 0 33600/300 --/19 35 In 0Related Commands
Command DescriptionDisplays the operational status of a specific port or range of ports.
show spe
Displays history statistics of all SPEs, a specified SPE, or a specified range of SPEs.
show spe modem csr
To display the call success rate (CSR) for the specified service processing elements (SPEs), use the
show spe modem csr command in privileged EXEC mode.Cisco AS5400 with NextPort DFC
show spe modem csr {summary | slot | slot/spe}
Cisco AS5800 with universal port card
show spe modem csr {summary | shelf/slot | shelf/slot/spe}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show spe modem csr command displays the modem call success rate statistics for a specific SPE, range of SPEs, or all SPEs. The summary keyword displays the call success rate statistics for all SPEs.
Examples
The following example shows output for the show spe modem csr summary command on the Cisco AS5400 with NextPort dial feature card (DFC):
Router# show spe modem csr summaryAvg Hold Inc calls Out calls Failed No SuccTime Succ Fail Avail Succ Fail Avail Dial Answer Pct00:00:44 1 0 216 0 0 216 0 0 100%%The following is sample output from the show spe modem csr summary command on the Cisco AS5800 with universal port card:
Router# show spe modem csr summaryAvg Hold Inc calls Out calls Failed No SuccTime Succ Fail Avail Succ Fail Avail Dial Answer Pct002631 4827 285 93 0 0 93 5 0 94%Related Commands
show spe modem disconnect-reason
To display all modem disconnect reasons for the specified service processing element (SPE), use the
show spe modem disconnect-reason command in privileged EXEC mode.Cisco AS5400 with NextPort DFC
show spe modem disconnect-reason {summary | slot | slot/spe}
Cisco AS5800 with universal port card
show spe modem disconnect-reason {summary | shelf/slot | shelf/slot/spe}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The disconnect reasons are displayed with Class boundaries.
Examples
The following example shows output for the show spe modem disconnect-reason summary command on the Cisco AS5400 with NextPort dial feature card (DFC).
Router# show spe modem disconnect-reason 1/0===CLASS OTHER==== ====CLASS DSP===== ====CLASS HOST==== ===CLASS EC LCL===Software Rst 0 No Carrier 0 Hst NonSpec 0 No LR 0EC Termntd 0 No ABT dtctd 0 Hst Busy 0 LR Param1 0Bad MNP5 Rx 0 Trainup flr 0 Hst No answr 0 LR Incmpt 0DC General 0 Retrain Lt 0 Hst DTR 0 Retrns Lt 0Bad COP stat 0 ABT end flr 0 Hst ATH 0 Inactivity 0ATH 0 COT Ack 0 Hst NoDialTn 0 Protocol Err 0Aborted 0 COT Nak 1 0 Hst No Carr 0 Fallbck Term 0Connect Tout 0 COT Nak 2 0 COT Off 0 No XID 0Reset DSP 0 MOH Clr Down 0 COT Timeout 0 XID Incmpt 0DC Codeword 0 MOH Timeout 0 Hst Ack 0 Disc 0DC Empty Nd 0 DM 0DC Large Tok 0 ===CLASS EC LD==== ==CLASS EC FRMR=== Bad NR 0DC Reserved 0 LD No LR 0 Frmr Bad Cmd 0 SABME Online 0DC Char Size 0 LD LR Param1 0 Frmr Data 0 XID Online 0DC Rx Dict 0 LD LR Incmpt 0 Frmr Length 0 LR Online 0DC Rx Hist 0 LD Retrns Lt 0 Frmr Bad NR 0DC Rx String 0 LD Inactivty 0 =====N O N E======DC Negotiate 0 LD Protocol 0 ===CLASS EC CMD=== None 0DC Compress 0 LD User 0 Bad Cmd 0TOTAL 0The following is sample output from the show spe modem disconnect-reason summary command on the Cisco AS5800 with universal port card:
Router# show spe modem disconnect-reason summary===CLASS OTHER==== =====CLASS DSP==== ===CLASS EC LCL=== ==CLASS EC FRMR===Software Rst 0 No Carrier 21 No LR 0 Frmr Bad Cmd 0EC Termntd 0 No ABT dtctd 0 LR Param1 0 Frmr Data 0Bad MNP5 Rx 0 Trainup flr 26 LR Incmpt 0 Frmr Length 0Bad V42B 12 Retrain Lt 0 Retrns Lt 37 Frmr Bad NR 0Bad COP stat 0 ABT end flr 0 Inactivity 0ATH 0 Protocol Err 5 ===CLASS EC LD====Aborted 0 ====CLASS HOST==== Fallbck Term 22 LD No LR 0Connect Tout 11 Hst NonSpec 799 No XID 5 LD LR Param1 0Reset DSP 0 Hst Busy 0 XID Incmpt 0 LD LR Incmpt 0Hst No answr 0 Disc 2718 LD Retrns Lt 0===CLASS EC Cmd=== Hst DTR 870 DM 0 LD Inactivty 0Bad Cmd 0 Hst ATH 0 Bad NR 0 LD Protocol 0Hst NoDialTn 0 SABME Online 0 LD User 0=====N O N E====== Hst No Carr 0 XID Online 0None 29 Hst Ack 0 LR Online 0 TOTAL 4555Related Commands
show spe modem summary
To display summary of modem statistics for the specified service processing element (SPE) or range of SPEs, use the show spe modem summary command in privileged EXEC mode.
Cisco AS5400 with NextPort DFC
show spe modem summary [slot | slot/spe]
Cisco AS5800 with universal port card
show spe modem summary [shelf/slot | shelf/slot/spe]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example displays the show spe modem summary command on the Cisco AS5400.
Router# show spe modem summaryAsync1/00 - 3/107, TTY216 - 5391 incoming completes 0 incoming failures0 outgoing completes 0 outgoing failures0 failed dial attempts 0 ring no answers 0 autotests0 no carriers 0 dial timeouts 0 autotest fails0 no dial tones 0 link failures 0 fail count0 watchdog timeouts 0 protocol errors 0 recoversTransmit Speed Counters :Speed Calls Speed Calls Speed Calls Speed Calls Speed Calls60000 0 48000 0 38400 0 30666 0 12000 058000 0 46666 0 38000 0 29333 0 9600 056000 0 46000 0 37333 0 28800 0 7200 054666 0 45333 0 36000 0 28000 0 4800 054000 0 44000 0 34666 0 26400 0 2400 053333 0 42666 0 34000 0 24000 0 1200 052000 0 42000 0 33600 0 21600 0 300 050666 0 41333 0 33333 0 19200 050000 0 40000 0 32000 0 16800 049333 0 38666 0 31200 0 14400 0Receive Speed Counters :Speed Calls Speed Calls Speed Calls Speed Calls Speed Calls38400 0 26400 0 16800 0 7200 0 300 033600 0 24000 0 14400 0 4800 031200 0 21600 0 12000 0 2400 028800 0 19200 0 9600 0 1200 0The following is sample output from the show spe modem summary command on the Cisco AS5800.
Router# show spe modem summaryAsync1/2/00 - 1/3/323, TTY972 - 16194827 incoming completes 284 incoming failures0 outgoing completes 0 outgoing failures0 failed dial attempts 0 ring no answers 0 autotests0 no carriers 11 dial timeouts 0 autotest fails0 no dial tones 0 link failures 0 fail count0 watchdog timeouts 2787 protocol errors 0 recoversTransmit Speed CountersSpeed Calls Speed Calls Speed Calls Speed Calls Speed Calls60000 0 48000 432 38400 0 30666 0 12000 14358000 0 46666 0 38000 4 29333 0 9600 556000 15 46000 56 37333 111 28800 700 7200 1154666 0 45333 299 36000 84 28000 5 4800 254000 0 44000 227 34666 0 26400 267 2400 053333 123 42666 0 34000 39 24000 46 1200 352000 563 42000 68 33600 323 21600 27 300 050666 0 41333 38 33333 9 19200 3850000 59 40000 65 32000 20 16800 1249333 371 38666 0 31200 654 14400 5Receive Speed CountersSpeed Calls Speed Calls Speed Calls Speed Calls Speed Calls38400 0 26400 2286 16800 11 7200 1 300 233600 113 24000 267 14400 139 4800 131200 216 21600 56 12000 4 2400 328800 1665 19200 47 9600 16 1200 0Related Commands
Glossary
CLI—command-line interface.
CSMv6—Mindspeed modem hardware solution.
CSR—call success rate.
DFC—dial feature card.
DSP—Digital Signal Processor. Microprocessor on which the modulation/demodulation process is carried out.
ISP—Internet service provider.
ITU-T—International Telecommunication Union Telecommunication Standardization Sector.
LZJH—Lempel-Ziv-Jeff-Heath data compression algorithm used in V.44.
MICA—Modem ISDN channel aggregation. Used as a generic term to describe the Dial Technology Division (DTD) high-density modem technology.
MOH—Modem on Hold functionality specified in V.92.
NextPort—Device driver architecture for Cisco IOS software that supports the NextPort hardware and software interfaces. Supports the Universal Port concept.
PCM—pulse code modulation.
PPP—Point-to-Point Protocol.
PSTN—Public Switched Telephone Network.
SPE—service processing element.
universal port—Concept of a single device that can terminate one digital signaling level zero (DS0) with a data modem, fax modem, ISDN, or voice solution.
QC—Quick Connect functionality specified in V.92.
V.44—ITU modem standard for LZJH data compression algorithm.
V.92—ITU modem standard that contains Quick Connect and Modem On Hold.
VSA—vendor specific attribute (RADIUS).

