Worldwide [change] |Account |Register |About Cisco
Guest

Hierarchical Navigation

Cisco AS5300 Series Software

Firmware RNs - Ver 5.3.30 for 56K 12-Port Modem Modules

Downloads

Table Of Contents

Firmware Release Notes Version 5.3.30 for Cisco Universal Access Server 56K 12-Port Modem Modules

Firmware Version 5.3.30 Requirements and Features

Requirements

Features

Modem Compatibility

Bugs in Version 5.3.30

Notices

Revision History

Differences Between Firmware Versions 5.3.30 and 5.2.30

Differences Between Firmware Versions 5.2.30 and 5.1.20

Bugs Fixed in 5.2.30

Differences Between Firmware Versions 5.1.20 and 5.0.40

Bugs Fixed In 5.1.20

Differences Between Firmware Versions 5.0.40 and 5.0.20

Bugs Fixed In 5.0.40

Differences Between Firmware Versions 5.0.20 and 3.3.20

Differences Between Firmware Versions 5.0.20 and 3.3.20

Bugs Fixed In 5.0.20

Differences Between Firmware Versions 3.3.20 and 3.2.10

Bugs Fixed In 3.3.20

Differences Between Firmware Versions 3.2.10 and 3.1.30

Bugs Fixed In 3.2.10

Changing Country Codes on Microcom Modems

Configure

Verify

Changing Country Codes on Microcom Modems—Cisco AS5300

Downloading Modem Code

Cisco AS5200 or AS5300 56K Systems Running Cisco IOS Release 12.0(4)XI1

SPE Range Description

Troubleshooting SPE

Cisco AS5200 V.34/V.110 or AS5300 V.34 Systems Running Cisco IOS Release 12.0(4)XI1

Cisco AS5200 or AS5300 Running Cisco IOS Releases Earlier Than 12.0(4)XI1

Cisco AS5200 Running Cisco IOS Release 11.2(8)P and 11.2(9)P

Fax DialOut

Related Documentation

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center


Firmware Release Notes Version 5.3.30 for Cisco Universal Access Server 56K 12-Port Modem Modules

File updated February 26, 2002

The release notes for Cisco Microcom Firmware Version 5.3.30 contain the most current status of the 56K modem firmware for Cisco universal access server 12-port modules. This firmware is supported on both Cisco AS5200 and Cisco AS5300 universal access servers and supports the store and forward fax feature on the Cisco AS5300.

Cisco 56K Microcom Firmware Version 5.3.30 is a maintenance release that uses Cisco IOS software (see "Modem Compatibility"). This is the final Cisco 56K Microcom firmware version release.

This document contains the following sections:

•"Firmware Version 5.3.30 Requirements and Features"

•"Modem Compatibility"

•"Bugs in Version 5.3.30"

•"Notices"

•"Revision History"

•"Changing Country Codes on Microcom Modems"

•"Downloading Modem Code"

•"Fax DialOut"

•"Related Documentation"

•"Obtaining Documentation"

•"Obtaining Technical Assistance"

Firmware Version 5.3.30 Requirements and Features

The following section contains updated requirements and features.

Requirements

•Cisco IOS Software. See the 56K Digital 12-Port Modem Module Compatibility Matrix (56K Modem) for Cisco AS5200/AS5300 for complete Cisco IOS/firmware compatibility:

•Boot code:

–mcom-modem-code.5.3.30.bin

Features

•AT command changes:

–Register :T52 is used for V.90 transmit levels and is set to 12 by default; transmit levels for 56Kflex connections are locked at -12dB.

–Register :T89 has been created for PoS Quick Connect with a revised bit map.

–Register :T20, :T21, and :T127 have been augmented.

For information about AT commands, see the Cisco document, AT Command Set and Register Summary for V.34, 56K, and V.90 12-Port Modules:

There are no new features with this final release. However, this release supports the following Cisco Microcom Firmware Version 5.2.30 features:

•Firmware updates may be performed with established copy flash modem commands or with Service Processing Element (SPE) configuration commands. (See "Downloading Modem Code.")

Note spe commands are supported on Cisco IOS software release 12.0(4)X11 and higher.

•Modemcaps are not required.

Table 1 lists feature content by modem firmware version.

Table 1 Feature Content by Modem Version 

Firmware Version
Feature Content 

5.3.30

Final V.90 maintenance release

5.2.30

V.90 maintenance release; store and forward fax

5.1.20

V.90 and fax maintenance release

5.0.20

Modulation

Pre-final V.90 release (available on CCO only)

•ITU-T V.90 Draft at 28000 to 56000 bps in 1333 bps increments

3.3.20

Data Modulation

•Rockwell/Lucent K56flex at 56000 to 32000 bps in 2000 bps increments

•Rockwell V.FC at 28800, 26400, 24000, 21600, 19200, 16800, and 14400 bps

Fax Modulation

•ITU-T V.27ter at 2400 and 4800 bps

•ITU-T V.29 at 7200 and 9600 bps

•ITU-T V.17 at 12000 and 14400 bps

Negotiation

•V.8bis

Features

•Point of Sale (POS) Configuration support

•Fax Class 2 operation according to standards proposal 2388 (8/20/90)

•Fax Class 2.0 operation as defined in EIA-592

3.2.10

Note Not recommended for general use.

3.1.30

Modulation

•Rockwell K56flex at 56000 to 32000 in 2000 bps increments

•ITU-T V.34 Annex 12 at 33600 and 31200 bps

•ITU-T V.34 at 28800, 26400, 24000, 21600, 19200, 16800, 14400, 12000, 9600, 7200, 4800, and 2400 bps

•ITU-T V.32bis at 14400, 12000, 9600, 7200, and 4800 bps

•ITU-T V.32 at 9600 and 4800 bps

•ITU-T V.23 in two modes: split speed and half-duplex 1200 bps

•ITU-T V.22bis at 2400 bps

•ITU-T V.22 at 1200 and 600 bps

•ITU-T V.21 at 300 bps

•Bell 212A at 1200 bps

•Bell 103A at 0 to 300 bps

Protocols

•MNP 10

•ITU-T V.42 (including MNP 2-4 and LAPM) Error Correction

•ITU-T V.42bis (1K nodes) and MNP 5 Data Compression

Modem Standards

•ITU V. 25—Automatic calling or answering equipment on dial-up lines. This standard includes the procedures for disabling echo control devices for calls that are established manually and automatically


Modem Compatibility

The complete compatibility matrixes can be found on the following index:

Compatibility information for the Cisco AS5300

Note See your account representative for a list of tested modems.

Bugs in Version 5.3.30

The following problems were found with firmware version 5.3.30.

• CSCdm01814 — Xircom - MNP link failures

• CSCdk89976 — Non-EC connections in V.90

•CSCdm21267 — V.34 Link retrain failures

•CSCdm92669 — Failures to connect with some Ameritec devices

Notices

•Fax DialOut running with a minimum of Cisco IOS Release 11.3(6)T is possible with the fax firmware available in 3.2.10 and with Cisco IOS Release 11.3(1) and higher. Cisco recommends Cisco IOS Release 11.3(4)T and higher because there was a serious bug (CSCdj61765) with abnormal disconnects in earlier versions, which was fixed in Cisco IOS Release 11.3(4)T and higher.

•Only RAM based K56flex client modems are supported because the early ROM based K56flex implementations were not stable and are not currently supported by Rockwell.

•Because of a reliability problem with back-to-back tests (CSCdj74085), it is recommended that no modem startup be configured.

•Defaults for 5.0.xx:

–:T124 = 43

–:T110 = 44

•Disable K56flex/K56plus in the following 5.0.xx images:

–:T110 - 38 (decimal). Disables K56flex by disabling V.8bis negotiation.

–:T124 = 11 (decimal). Disables K56plus.

•You must change the country code setting if you are using your modems in a country other than those included in the USA country code. The USA country code is used for the following:

–Argentina

–Brazil

–Canada

–Chile

–China

–Columbia

–Hong Kong

–India

–Indonesia

–Korea

–Malaysia

–Mexico

–Peru

–Philippines

–Singapore

–Taiwan

–Thailand

See Changing Country Codes on Microcom Modems for configuration instructions. For higher Cisco IOS releases, use the modem country microcom_hdms command as described in the "Configure the Modems and Lines" section in the Cisco publication, Configuring Modem Support and Other Asynchronous Features.

To see the list of the supported countries, use the modem country microcom_hdms. The following is an example of a list of supported countries: 

Example: 

router(config)# modem country microcom_hdms?

argentina       Argentina

australia       Australia

austria         Austria

belgium         Belgium

canada          Canada

chile           Chile

china           China

columbia        Columbia

czech-republic  Czech/Slovak Republic

denmark         Denmark

...

•The K56flex DSP code must be stored in the Cisco AS5200 access server's boot Flash memory with the new 56K modems. See Downloading Modem Code for more information.

Note The current Flash file system does not support removing individual files when the Flash is full. The Flash memory must be erased and then restored with the required files in order to free up Flash memory space. Therefore, it is highly recommended that copy operations to the boot Flash memory be limited to an absolute minimum.

Revision History

This section describes all Cisco Microcom 56K modem firmware updates.

Differences Between Firmware Versions 5.3.30 and 5.2.30

Note Firmware version 5.3.30 is a maintenance release and should be used instead of previous versions. This is the final Cisco Microcom release.

Firmware version 5.3.30 supports the same features as version 5.2.30.

Differences Between Firmware Versions 5.2.30 and 5.1.20

Firmware version 5.2.30 supports the following changes over version 5.1.20:

•Maintenance fixes on the previous baseline. Some minor enhancements were included that may resolve issues regarding reporting incorrect speeds reported by the modem by way of the Out-of-Band Port (OOBP), which is used for modem management. Additional Cisco proprietary design features were also incorporated.

•The following registers were revised:

–:T52 revised to support independent V.90 Tx Power Level Adjust.

–:T127 revised to support server Rx aggression/nonaggression rate control.

–:T110 revised to default 0d36 matching server-client reported rates over Robbed bit signaling (RBS).

Bugs Fixed in 5.2.30

•CSCdm35014—Data loss/corruption during V.21 and Bell 103 300 bps connection. The DSP was set to synchronous mode although the connection was asynchronous. The DSP is notified of the configuration change by a set bit.

•CSCdm05446— K56flex PCM Rates over RBS report incorrectly. Register:t110 default is now set to 0d36 to report K56 Tx rates to be equal to client Rx rates over RBS. To disable V.8bis, set the register to 0d38. RBS counter will be reported in the @E report for flex connections only. RBS counter now reports as N/A for all other modulations.

•CSCdk93866—ModemSurfr V2.083 has error correction problems in V.90 with some circuits. Register:T52 is now used only for V.90 transmit levels. It is set to 12 by default. Register :T51 still defaults to 13 and effects V.34 connections. Transmit levels for flex connections are locked at -12 dB. This change alleviates many if not all of the Retrains and Rate Renegotiations problems reported by some V.90 and V.34 modems under certain conditions. It also has the effect of increasing the client V.90 connect rates on certain lines an average of 1.333 kbps.

•CSCdk89980—Cases of speed throttling or excessive V.42 receive errors on marginal circuits. Register :T127 has 3 new bits defined that fix this bug. (The default is still 0.) Bits 2 and 3 are used to reduce the receive speeds for V.90, flex, and V.34 modulations. This is one of the enhanced Cisco Access Server features incorporated under CSCdk89980. Nonaggressive settings are described in Table 2.

Table 2 New Bits for Register :T127 (Nonaggressive Settings)

Bit 3
Bit 2
Meaning

0

0

Do not reduce speed (default)

0

1

Reduce speed by 1 rate (2400 bps)

1

0

Reduce speed by 2 rates (4800 bps)

1

0

Reduce speed by 3 rates (7200 bps)


• CSCdk90934—Digital Pad compensation disable. You can now set Register :T127 bit 4 = 1 to disable compensation.

•CSCdm25849— MABP character counter errors. The modems now correctly report the number of transmitted and received characters during a connection by way of the Out-Of-Band (MABP) port in all modes.

•CSCdm29789—Inability to dial out when set to certain countries. All countries now default to ATX4.

•CSCdk76533—Modems miss the first AT command sent after returning from fax mode to data mode.

•CSCdk56444—Data errors during 33.6K normal mode connections.

Differences Between Firmware Versions 5.1.20 and 5.0.40

Firmware version 5.1.20 supports the following changes over version 5.0.40:

•Maintenance fixes on the previous baseline.

Bugs Fixed In 5.1.20

•CSCdk39344—Power level reduction in K56flex with Lucent modem.

•CSCdm21172—Some client initiated rate renegotiations cause receive rates to spiral down to low V.34 levels.

•CSCdk52911—Motorola VoiceSurfr inter-op problem.

•CSCdk90101—Back-to-Back does not work reliably with a 28.8K Cap.

•CSCdk91863—Mcom OOB Spewing Connection Update Messages.

•CSCdk93866— ModemSurfr V2.083 has EC problems in V.90 with some circuits.

•CSCdm02361—3Com-USR Sportster Disconnects under ftp.

•CSCdk65601—Rio cannot originate a V.FC connection when set to %M1.

•CSCdk89956—ATDTR Command Parser no echoing line feed character.

•CSCdk86050—Rate Renegotiation Requests & Disconnects in V.34.

•CSCdk24518—Bell212 MNP broken on 5.0.24 code.

Differences Between Firmware Versions 5.0.40 and 5.0.20

Firmware version 5.0.40 supports the following changes over version 5.0.20:

•A workaround has been added to resolve an issue regarding Lucent-based V.90 clients making excessive (could be as high as 50% depending on client and firmware revision) normal mode connections when the client is set to defaults (S109=1). This client default will negotiate a V.90 or K56flex connection and allow the V.8bis handshake. V.90 was being advertised by the server modem by bit 1 in octet 15 of V.8bis (octet 15 sent as 83). The workaround is to clear this bit (octet 15 sent as 81) which will force a K56flex connection for Lucent clients ONLY. The current K56flex implementation does not have an issue of connecting in Normal mode, therefore connections will be more stable.

•A new register has been added. Bit 1 of :T127 controls this workaround. The default is zero (:T127=0). To disable the workaround, set :T127=2 (set bit 1).

Note Forcing V.90 on the client by setting S109=2 would also disable this workaround while still allowing for V.90 connections. However, if V.90 connections are desired on Lucent modems they should be limited to below 50K for now.

Bugs Fixed In 5.0.40

•CSCdj85485—Older modems can not connect to 56k microcom modems.

•CSCdk08555—High percentage of call drops have been resolved with USR Sportster V90 modem over E1.

•CSCdk19030—Microcom code 5.0.11 cannot connect BELL212 or V.22.

•CSCdk24530—1200 baud modes broken in 5.0.24 code.

•CSCdk24536—V.22bis has high failure-to-connect rate.

•CSCdk28303—POS does not work in version 5.0.25.

•CSCdk27696—Data errors in V.42 data transfers.

•CSCdk27712—5.0.18a carrier loss during V.42 data transfer.

•CSCdk47261—MHz V.90 Client locks on V.8 tones during training.

•CSCdk44733—Trainup problems with Accura288 if AMSTAR 2400 in loop.

•CSCdk65438—Excessive rate renegotiations with some 28.8K clients.

Differences Between Firmware Versions 5.0.20 and 3.3.20

Firmware version 5.0.20 supports the following changes over version 3.3.20:

•Firmware version 5.0.20 introduces support for the Draft ITU-T V.90 modulation at 28000 to 56000 bps in 1333 bps increments.

•Introduced %M4 to control V.90 modulation.

•Additional bug fixes were added to address issues in 3.3.20.

•Q2 was made the new default instead of Q0.

•:T114 defaults to 1 (clear bit 0) - So that Power boosting is no longer tied to A-law.

•-K2 is now the default instead of -K1.

•%G1 is not the default instead of %G0.

•When in a mu-law environment, the server modem will now force a Rockwell client modem set to A-law to go into mu-law.

Differences Between Firmware Versions 5.0.20 and 3.3.20

Firmware version 5.0.20 supports the following changes over version 3.3.20:

•Firmware version 5.0.20 introduces support for the Draft ITU-T V.90 modulation at 28000 to 56000 bps in 1333 bps increments.

•Introduced %M4 to control V.90 modulation.

•Additional bug fixes were added to address issues in 3.3.20.

•Q2 was made the new default instead of Q0.

•:T114 defaults to 1 (clear bit 0) - So that Power boosting is no longer tied to A-law.

•-K2 is now the default instead of -K1.

•%G1 is not the default instead of %G0.

•When in a mu-law environment, the server modem will now force a Rockwell client modem set to A-law to go into mu-law.

Bugs Fixed In 5.0.20

•CSCdj39369—%g1%b9600 does not clamp max at 9600.

•CSCdj45406—%M1 does not work to force V.FC connections.

•CSCdj4541094—94% success rate from Lucent modem into Rio over DPRI.

•CSCdj51206—Sometimes Microcom 56K modems in V.34 mode connects in NORMAL mode.

•CSCdj56628—56K connection attempts fail & 34K Max with as-loop-start config.

•CSCdj65642—Normal connections with V.FC MNP connections.

•CSCdj86149—Excessive Retrains in high-speed (>48K) K56flex connections.

Differences Between Firmware Versions 3.3.20 and 3.2.10

Firmware version 3.3.20 supports the following changes over version 3.2.10:

•3.3.20 is a maintenance release only with bug fixes added.

•No change in functionality was introduced.

•Fax manufacturer changed from Microcom to Compaq.

Bugs Fixed In 3.3.20

•CSCdj72032—V.8bis bug prevents some older modems from connecting to a K56flex server.

•CSCdj26488—RBS Counter & Digital Pad Detected status report not working.

•CSCdj45404—Different xmit levels reported via AT@E and measured with Tas.

•CSCdj45409—Cannot distinguish the latest DSP version (39) from previous version. A workaround is to use AT@E and look at the "DSP Controller Rev" field.

•CSCdj51507—The AT+FREV? command returns an error.

•CSCdj59532—Alternate fax calls at 2400 bps using MSfax do not connect.

Differences Between Firmware Versions 3.2.10 and 3.1.30

Note Firmware 3.2.10 not recommended for general use.

Firmware version 3.2.10 supports the following changes over version 3.130:

•V.FC, fax, Lucent K56flex, and Point of Sale (POS) support were added to the 3.2.10 release

Registers :t89, :t120, :t121 have been allocated to enable V.21/V.22 (300/1200) quick POS connections, error correction, pause for DCD to be true, and tone duration timers.

Note See your Cisco account representative for information about AT commands.

Bugs Fixed In 3.2.10

•CSCdj16565—High rate of no protocol connections in back-to-back call attempts.

•CSCdj16062—V.32 14.4K instead of 56K with Rockwell clients.

•CSCdj17215—Sometimes modem back-to-back test fails with NO CARRIER.

•CSCdj26472—No connection for V.FC modem when running from RAM.

•CSCdj22693—Forced V.34 12K and V.22 1200 bps connections are not stable.

•CSCdj26548—32 Kbps in 56K mode connects in 4800/31200 bps in V.34 mode.

•CSCdj26157—Called side modem reports as V22 for Bell 212 connection.

•CSCdj26482—MABP reports invalid TX speed for lower K56flex connections.

•CSCdj26477—ATI10/ATI11 is overwritten.

•CSCdj26069—48K connections reported by clients but 56K modems report 50K.

Changing Country Codes on Microcom Modems

This section describes how to change the country code on Microcom modems in Cisco AS5200 Universal Access Servers running Cisco IOS Release 11.2(8)P, 11.2(9)P, 11.3(x), 11.3(T), 12.0(x), or 12.0(x)T. See Changing Country Codes on Microcom Modems—Cisco AS5300 for a description of country codes on the Cisco AS5300.

Note With the introduction of Cisco IOS Release 11.2(10)P and Release 11.3(2)T for Cisco AS5200, the system supports changing country codes as described in Changing Country Codes on Microcom Modems—Cisco AS5300.

The default country code is USA. The USA country code is also used for the following countries: Argentina, Brazil, Canada, Chile, China, Columbia, Hong Kong, India, Indonesia, Korea, Malaysia, Mexico, Peru, Philippines, Singapore, Taiwan, and Thailand. If you are using the modems in a different country, you must change the country code.

Note Customers using Cisco IOS Release 12.0(4)XI1 or higher will be prompted to use the Service Processing Element (SPE) command instead of the modem-pool command to download code. The modem-pool command will no longer be available, and the existing modem firmware configurations in the router will be converted to the new spe command format. See the "Downloading Modem Code" section for more information.

Configure

Configure the system as follows:

Step 1 Enter global configuration mode: 

router> enable

router# config term

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

router(config)#

Step 2 Edit the modemcap and specify the country code (-InZ) in the miscellaneous attributes field. Substitute n with one of the country codes listed in the "Country Code" column of Table 3. In the following example, the country code is set to "18" for the Czech/Slovak Republic: 

Router(config)# modemcap edit mcom_czech misc -i18z

Table 3 Country Codes

Country
Country Code
Country Code Displayed in Banner

Australia

20

49

Austria

22

92

Belgium1

23

67

Czech/Slovak Republic1

18

91

Denmark

10

63

Finland

9

71

France1

25

32

Germany

17

68

Israel

15

16

Italy

3

21

Ireland

24

97

Japan

13

14

Netherlands

5

04

New Zealand

11

55

Norway

8

72

Poland

19

93

Portugal

27

94

Spain

6

76

South Africa

16

69

Sweden

7

09

Switzerland1

14

66

UK2

2

12

USA3

1

85

1 The s-register is set to s0=2 (that is, answer on the second ring) by default. Additional configuration is required.

2 The UK country code is also used for Greece, Hungary, and Saudi Arabia.

3 The USA country code also applies to Argentina, Brazil, Canada, Chile, China, Columbia, Hong Kong, India, Indonesia, Korea, Malaysia, Mexico, Peru, Philippines, Singapore, Taiwan, and Thailand.


Step 3 Specify the lines on which to apply the new modemcap. In the following example, lines 1 through 48 are specified: 

Router(config)# li 1 48

Step 4 Turn on autoconfig to the selected lines: 

Router(config-line)# modem auto type mcom_czech


Step 5 Exit line configuration mode, exit global configuration mode, and return to enable mode: 

Router(config-line)# exit

Router(config)# exit

Router#

Step 6 Save the configuration changes to NVRAM: 

Router# copy running-config startup-config

[OK]

Verify

You can verify the changes to the modemcap in many ways. This section describes two ways: from the router command prompt and from the AT command prompt during the call.

The following example shows verification from the router command prompt: 

Router# show modemcap mcom_czech


Modemcap values for mcom_czech

Factory Defaults (FD):  [not set]

Autoanswer (AA):  [not set]

Carrier detect (CD):  [not set]

Drop with DTR (DTR):  [not set]

Hardware Flowcontrol (HFL):  [not set]

Lock DTE speed (SPD):  [not set]

DTE locking speed (DTE):  [not set]

Best Error Control (BER):  [not set]

Best Compression (BCP):  [not set]

No Error Control (NER):  [not set]

No Compression (NCP):  [not set]

No Echo (NEC):  [not set]

No Result Codes (NRS):  [not set]

Software Flowcontrol (SFL):  [not set]

Caller ID (CID):  [not set]

On-hook (ONH):  [not set]

Off-hook (OFH):  [not set]

Miscellaneous (MSC):  -i18z		

Template entry (TPL):  [not set]

Router#

Note The Miscellaneous (MSC) field is the only field set in the modemcap. All other fields have default values.

The following example shows verification from the AT command prompt. Make sure that you issue the AT command during the call. Note that the following display shows factory default settings for version 3.1.30 except for the country code. 

Router#

Router# mod at 2/0

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

Please type CTRL-C to exit AT command mode.

at \s1


IDLE           000:14:14

LAST DIAL      


NET ADDR:      FFFFFFFFFFFF

MODEM HW: OEM 2W Czech/Slovak Republic

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

MODULATION     IDLE

MODEM T/R BPS  *****  *****

MODEM BPS      56000  AT%G0   

MODEM FLOW     OFF    AT\G0

MODEM MODE     AUT    AT\N3

BASE MODE      K56    AT%M3

V.23 OPR.      OFF    AT%F0

AUTO ANS.      ON     ATS0=1

SERIAL BPS     115200 AT%U1   

BPS ADJUST     OFF    AT\J0

SPT BPS ADJ.   0      AT\W0

ANSWER MESSGS  ON     ATQ0   

SERIAL FLOW    BHW    AT\Q3

PASS XON/XOFF  OFF    AT\X0

PARITY         8N     AT

BREAK          5      AT\K5

EXIT CHAR      043    ATS2=43

ANS DUMB MODE  ON     AT#E1

CMD ECHO       ON     ATE1

RESULTS        ON     ATQ0

RESULT TYPE    MNPX   ATV1\V2

CONNECT MSG    MDM    ATW2

CONN MNP-      0      AT-M0

SPEED MATCH    1      AT%L1

EQUALIZER      1      AT:E1

FALLBACK       2      AT-Q2

DATA ECHO      OFF    AT\E0

INACT TIMER    00     AT\T0

AUTO RETRAIN   ON     AT%E1

COMPRESSION    ALL    AT%C3

MAX BLK SIZE   256    AT\A3

AUTO BUFF      0      AT\C0

AUTO CHAR      000    AT%A0

EMULATING HP   OFF    AT\H0

PAUSE TIME     002    ATS8=2

DTR            3      AT&D3

MABP ADDRESS   001    AT^P1

CARR DET       1      AT&C1

DSR            0      AT\D0

RING IND       1      AT\R1

SPKR CTRL      1      ATM1

SPKR VOL       2      ATL2

LNG SPC DISC   OFF    ATY0

DISC DELAY     000    AT%D0

RDLB ENABLE    OFF    AT&T5

DIAL MODE      4      ATX4   

PULSE DIAL     60%    AT&P0

PULSE MODE     N      AT%W0

V23 HD EQU     ON     AT%O1

GUARD TONE     2      AT&G2

DATA CALL TONE ON     AT-C1

2ND FC         OFF    AT-F0

NM BIT VALUE   0      AT-E0

PAR CHK        0      AT-P0

MANUAL DIAL    0      AT:D0

UPSHIFT BPS    OFF    AT*H0

CELLULAR       OFF    AT)M0

LINETYPE       000    AT@M0

DETECT PHASE   ON     AT-J1

MNP EXT SVC    1      AT-K1

UNIV V.23      0      AT-V0

CONNECT MSG    1ST    AT@C0

DUMB MODE      OFF    AT-H0

BELL           OFF    ATB0

CALL ABT DISAB OFF    AT-Y0

REVERSE ANS    OFF    AT-W0

MIN CONN SPD   300    AT@U


OK

Press Ctrl-C to exit the direct-connect session.

This concludes the procedure for changing the country code.

Country codes that are set manually, not following the procedure just described, will remain in effect until one of the following events occur:

•Another -I command is sent.

•The firmware is reloaded (firmware reloads will always reset the country code to USA).

•The access server is power cycled.

•The access server is reloaded.

If you have questions or need assistance, refer to Obtaining Documentation.

Changing Country Codes on Microcom Modems—Cisco AS5300

Cisco IOS Release 11.2(9)XA and higher introduced a new command to change the country code. This section describes how to change the country code in the Cisco AS5300 Universal Access Server with the new command.

Note The new command is updated for Cisco AS5200 access servers running Cisco IOS Release 11.2(10)P and Release 11.3(2)T.

To change the country code on Microcom modems in Cisco AS5300 universal access servers, use the following command from global configuration mode:

5300(config)# modem country microcom_hdms <country name>

This command specifies the country to set the modem parameters (including encoding) for Microcom modems. The default is usa. Note that the access server will reset the Microcom modems for the command to take effect.

For additional details on this feature including country codes, refer to the Cisco AS5300 Universal Access Server Software Configuration Guide and the Updates to Cisco AS5300 Universal Access Server Module Installation and Software Configuration Guides. See the "Related Documentation" section for more information.

Note If you previously set the country code by editing the modemcap file (that is, by following the procedure described in Changing Country Codes on Microcom Modems), you must edit the file again to delete the country code entry (-i18z). Otherwise, you will not be able to use the modem country command.

Downloading Modem Code

Use the following information to download modem code. For 56K systems running Cisco IOS Release 12.0(4)XI1and 12.0(5)T, the spe command is available. When you enter the copy xxxx modem command on a 56K system, an error message appears, and you are prompted to use the spe command.

Note V.34 modems can only use the copy xxxx modem command and will not support the spe commands. See downloading modem code on Cisco AS5200 V.34/V.110 or AS5300 V.34 Systems Running Cisco IOS Release 12.0(4)XI1.

Cisco AS5200 or AS5300 56K Systems Running Cisco IOS Release 12.0(4)XI1

To download modem portware/firmware using the spe command, use the following steps:

Step 1 Enter the spe command, one configuration command per line, in the following format: 

Router# configure terminal

Router(config)#spe <slot>/<spe_begin> <slot>/<spe_end>

Router(config-spe)#firmware location <the_filesystem:filename>

For example, the following example shows an SPE download loading Slot 1 (that is, all modems on the feature card). The modem code resides on the Flash memory, and the modem code filename is mcom-modem-code.5.3.30.bin. 

Router(config)# spe 1/0 1/23

Router(config-spe)# firmware location flash:mcom-modem-code.5.3.30.bin

Step 2 Press CNTL Z (^Z) to complete the configuration and return to the router prompt: 

Router(config-spe)# CNTL z

Router#

Step 3 Copy the configuration from NVRAM into running RAM: 

Router# copy running-config startup-config

Download occurs when the modems become available.

Note The spe command is a configuration command—save it by using the write memory command; otherwise, the configuration is not saved and the specified firmware will not download after the next reboot.

SPE Range Description

•SPE ranges cannot span across the following parameters:

–Empty slots.

–Empty SPE units.

–SPEs of different firmware attributes in adjacent slots.

Note The typical T1 system for the Cisco AS5300 uses only 8 MICA modules, so even adjacent slots having MICA modems appear with a 2 SPE range entry (they typically have 8 modules; slots 9 and 10 are empty).

•SPE ranges must represent the same hardware.

•New SPEs inserted in place of old ones with higher SPE capacity:

–Break the SPE range if the original SPE is non-default.

–Expand the range if the original SPE is the default.

•New SPEs inserted in place of old ones with lower SPE capacity shrink the SPE range.

•Entering "no firmware location" triggers a download of the default firmware.

Troubleshooting SPE

To troubleshoot the SPE function, use the following information: 

Router(config)# spe 2/12 2/14

Router(config-spe)# firmware location flash:mcom-fw-dsp.5.3.3_47.22.bin

Please use 'copy' command, firmware download not supported for this type of SPE 2/12

Please use 'copy' command, firmware download not supported for this type of SPE 2/13

Please use 'copy' command, firmware download not supported for this type of SPE 2/14

Example display where the copy command displays an error message on MICA modems and 56K Microcom modems: 

Router# copy flash modem

Source filename [firmware]? flash:portware.2620.ios

Modem Numbers (<slot>/<port> | group <number> | all)? 1/14

'Copy' command is no longer valid for this type of port hardware, please use SPE 
configuration command


Router# copy system:ucode/mica_port_firmware modem:

Modem Numbers (<slot>/<port> | group <number> | all)? 1/0 1/5

'Copy' command is no longer valid for this type of port hardware, please use SPE 
configuration command


Router# copy flash modem

Source filename [portware.2620.ios]? flash:mcom-fw-dsp.5.3.3_47.22.bin

Modem Numbers (<slot>/<port> | group <number> | all)? 2/7

'Copy' command is no longer valid for this type of port hardware, please use SPE 
configuration command


!

resource-pool enable

!

resource-pool group resource rg_ss7_digital

 range limit 96

!

resource-pool group resource rg_ss7_v120

 range limit 96

!

resource-pool group resource rg_ss7_mica

 range port 1/0 1/47

!

resource-pool group resource rg_ss7_v24_analog

 range port 2/0 2/23

!

resource-pool group resource cisco_tac

 range limit 20

resource-pool aaa protocol group aaa-server

!

modem call-record terse

modem country mica usa

modem recovery action none


<snip config>

....

Router # 

Router# conf t

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

Router(config)# spe 1/2 1/4

Router(config-spe)# no firmware location flash:portware.2620.ios

Router(config-spe)#

*Jan  1 00:06:17.959:%MODEM-5-DL_START:Modem (1/12) started firmware download

*Jan  1 00:06:17.959:%MODEM-5-DL_START:Modem (1/13) started firmware download

*Jan  1 00:06:17.959:%MODEM-5-DL_START:Modem (1/14) started firmware download

*Jan  1 00:06:17.959:%MODEM-5-DL_START:Modem (1/15) started firmware download

*Jan  1 00:06:17.959:%MODEM-5-DL_START:Modem (1/16) started firmware download

*Jan  1 00:06:17.959:%MODEM-5-DL_START:Modem (1/17) started firmware download

Router(config-spe)# exit

Router(config)# exit

Router#

*Jan  1 00:06:22.995:%SYS-5-CONFIG_I:Configured from console by console.

Cisco AS5200 V.34/V.110 or AS5300 V.34 Systems Running Cisco IOS Release 12.0(4)XI1

Access servers with V.34 modems or V.110 Microcom terminal adapters must continue to use the copy xxxx modem command. When the spe command is entered, it displays a message that the command is not supported. On boot up, because these modems do not require download, the command displays the location of the firmware as "feature_card_flash." For example:
spe 1/0 2/23
firmware location feature_card_flash

For firmware download procedures using the copy xxxx modem command, see the URLs in the following section.

Cisco AS5200 or AS5300 Running Cisco IOS Releases Earlier Than 12.0(4)XI1

For the Cisco AS5300, refer to the "Managing Modems" section of the Cisco AS5300 Software Configuration Guide:

For the Cisco AS5200, refer to the Cisco AS5200 Universal Access Server Software Configuration Guide

Cisco AS5200 Running Cisco IOS Release 11.2(8)P and 11.2(9)P

In order to support K56flex modulation, Cisco AS5200 access servers running Cisco IOS Release 11.2(8)P and 11.2(9)P require two files that represent two modem code images: controller firmware and DSP software. Versions of the firmware and DSP software must be compatible. To determine compatibility, compare the filenames. For example, notice the similarity in the filenames for version 3.1.30 that follow:

•mcom-modem-fw-3.1.30-1.1.0.bin (controller firmware filename)

•mcom-modem-dsp-3.1.30-1.1.0.bin (DSP software filename)

Note Cisco IOS Release 11.3(1)T uses the two separate modem code files described above, and Cisco IOS Release 11.3(2)T uses the single modem code file.

The firmware is stored in the modem Flash memory, and the DSP software is stored in the access server's boot Flash memory. The procedure for downloading the DSP code is outlined in Figure 1. It is important to note that the current Flash-based file system does not support the erasing or deleting of individual files.

Figure 1 illustrates the flow of supported copy commands in the Cisco AS5200 running Cisco IOS Release 11.2(9)P and 11.2(8)P.

Figure 1 Copy Command Flow

For complete information, including the procedure for downloading the DSP software, refer to the
Cisco AS5200 Universal Access Server Software Configuration Guide.

For detailed information on the spe command, refer to the SPE and Firmware Download Enhancements:

Fax DialOut

For information about Fax DialOut, see the Cisco DialOut Utility User Guide.

For Fax DialOut, use firmware versions 3.3.2 0 with Cisco IOS Release 11.3(2) or higher.

Related Documentation

For more information about Cisco firmware, see the following indexes and documentation:

•Configuration documents for Cisco AS5300

•Cisco AS5300 Universal Access Server Software Configuration Guide, Appendix A,
"Managing Modems"

•Feature Guide for Cisco IOS Release 11.2(P), in the following sections:

–"56K 12-Port Modem Cards for the Cisco AS5200 Universal Access Server" section

–"Installing 56K 12-Port Modem Modules in Cisco AS5300 Universal Access Servers"

•SPE and Firmware Download Enhancements

•Cisco IOS release notes index page

•Cisco IOS Voice, Video, and Fax Configuration Guide, Release 12.2

•Cisco IOS Release 12.2 index

Obtaining Documentation

The following sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following URL:

http://www.cisco.com

Translated documentation is available at the following URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

•Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

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

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Leave Feedback at the bottom of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to

•Streamline business processes and improve productivity

•Resolve technical issues with online support

•Download and test software packages

•Order Cisco learning materials and merchandise

•Register for online skill assessment, training, and certification programs

You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Inquiries to Cisco TAC are categorized according to the urgency of the issue:

•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:

http://www.cisco.com/register/

If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.

.