Table Of Contents
Firmware Release Notes Version 5.1.20 for Cisco Universal Access Server 56K 12-Port Modem Modules
May 11, 1999
These release notes contain the most current status of the 56K modem firmware for the 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.
This document includes the following sections:
•"Firmware Features"—Identifies supported features with specific versions of the firmware.
•"Differences Between Firmware Versions 5.1.20 and 5.0.40"—Describes changes to default settings or behavior, and new features that were introduced in 5.1.20.
•"Differences Between Firmware Versions 5.0.40 and 5.0.20"—Describes changes to default settings or behavior, and new features that were introduced in 5.0.40.
•"Differences Between Firmware Versions 5.0.20 and 3.3.20"—Describes changes to default settings or behavior, and new features that were introduced in 5.0.20.
•"Differences Between Firmware Versions 3.3.20 and 3.2.10"—Describes changes to default settings or behavior introduced in 3.3.20.
•"Differences Between Firmware Versions 3.2.10 and 3.1.30"—Describes changes to default settings or behavior introduced in 3.1.30.
•"Revision History"—Describes changes to default settings or behavior, and new features that were introduced in 5.1.20.
•"Known Problems with Firmware Version 5.1.20"—Lists known bugs with the released version of firmware, including DDTS numbers.
•"Notices"—Lists general information that applies to more than one specific version of firmware.
•"Changing Country Codes on Microcom Modems"—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.2(9)XA and higher, 11.3(x), 11.3(T), 12.0(x), and 12.0(x)T.
•"Downloading Modem Code"—Describes downloading code on Cisco AS5200 running Cisco IOS Release 11.2(8)P and 11.2(9)P.
•"Fax DialOut"—Information about Fax DialOut.
•"Modem Compatibility"—Compatibility for V.90 and Legacy modems.
•"Cisco Connection Online"—Describes Cisco Connection Online (CCO), Cisco Systems' primary, real-time support channel.
•"Documentation CD-ROM"—Describes Cisco documentation and additional literature available in the CD-ROM package that ships with the product.
Table 1 lists feature content by modem firmware version.
Table 1 Feature Content by Modem Version
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.
Differences Between Firmware Versions 5.0.40 and 5.0.20
Firmware version 5.0.20 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.
•Also see the Revision History for bug fixes.
Differences Between Firmware Versions 5.0.20 and 3.3.20
Note Firmware version 5.1.20 is the official FCS release and should be used instead of version 5.0.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 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.
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.
This section describes bug fixes to all 56K modem firmware updates.
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 charater.
•CSCdk86050—Rate Regotiation Requests & Disconnects in V.34.
•CSCdk24518—Bell212 MNP broken on 5.0.24 code.
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 filure-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.
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.
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.
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.
Known Problems with Firmware Version 5.1.20
This section describes known problems with this firmware release. If a workaround is not provided, the problem requires further investigation or a solution is being developed.
Note Because V.90 technology is still a very new technology, all client modems should be upgraded to the latest code to ensure optimum performance and interoperability.
•Some country codes (such as UK) default to X3 preventing dialout from the Cisco AS5x00.
Cisco recommends using one of the following workarounds:
•Change the country code to X4 or set the modem to a country that defaults to X4. In the next release, all countries will default to X4.
•Add X4 in the server modemcap and apply with the modem autoconfigure.
•Insert X4 in the ATDT dial string as ATX4DT for the dialers.
•Under certain conditions, some V.34 clients may experience excessive Retrains and RREN during the connection. This is currently under investigation and should be resolved in the next release.
Note See your Cisco engineering account representative or contact Cisco Connection Online if you experience any instances of excessive rate shifting.
There are no severe issues at this time.
•CSCdm21267—V.34 link retrain failures.
•CSCdm05446—K56Flex PCM rates over RBS reported incorrectly.
•CSCdk89958—Lucent to Mcom death spiral and disconnect.
•CSCdk89965—Firmware lockup - recovery.
•CSCdk89976—Non-EC connections occur in V.90.
•CSCdk48763—Call drops occur during V.42bis full duplex transfers.
•CSCdk51417—High call drop rate occurs with Microcom 5.0.30 firmware.
•CSCdk60800—33.6K throughput degradation compared to 3.3.20.
•CSCdk90934—DPC enable/disable - Pending.
•CSCdk92717—Lucent DIL revision failures.
•CSCdm01814—Xircom MNP link failures.
•CSCdm05446—K56Flex rates over RBS are incorrect.
•CSCdk08395—B2B falling to 2400 bps.
•CSCdj50593—+FDCC and +FDIS in Fax mode fail to retain bit rate.
•CSCdk28164—B2B testing Brasil to Rio fails.
•CSCdk76533—Modem autobaud with DTE rate is unlocked.
•CSCdj66798—Digital modems fail B2B with errors on T1.
•CSCdk48722—High failure to connect rate in Bell212 V.42bis.
•CSCdm29789—Dial Out Aborted with UK Country Code.
There are no minor issues in this release.
•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 later. Cisco recommends Cisco IOS Release 11.3(4)T and later 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 later.
•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:
See Changing Country Codes on Microcom Modems for configuration instructions. For later Cisco IOS releases, use the modem country microcom_hdms command as described in the "Modem Country Microcom_hdms" section in the Cisco publication, New and Changed Commands for the Cisco AS5300.
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 Argentinaaustralia Australiaaustria Austriabelgium Belgiumcanada Canadachile Chilechina Chinacolumbia Columbiaczech-republic Czech/Slovak Republicdenmark 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.
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.
Configure the system as follows:
Step 1 Enter global configuration mode:Router> enableRouter# config termEnter 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 2. 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 2 Country Code Attributes
Country Country Code Country Code Displayed in Banner
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)# exitRouter(config)# exitRouter#
Step 6 Save the configuration changes to NVRAM:Router# copy running-config startup-config[OK]
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_czechModemcap values for mcom_czechFactory 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): -i18zTemplate 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/0You are now entering AT command mode on modem (slot 2 / port 0).Please type CTRL-C to exit AT command mode.at \s1IDLE 000:14:14LAST DIALNET ADDR: FFFFFFFFFFFFMODEM HW: OEM 2W Czech/Slovak Republic4 RTS 5 CTS 6 DSR - CD 20 DTR - RIMODULATION IDLEMODEM T/R BPS ***** *****MODEM BPS 56000 AT%G0MODEM FLOW OFF AT\G0MODEM MODE AUT AT\N3BASE MODE K56 AT%M3V.23 OPR. OFF AT%F0AUTO ANS. ON ATS0=1SERIAL BPS 115200 AT%U1BPS ADJUST OFF AT\J0SPT BPS ADJ. 0 AT\W0ANSWER MESSGS ON ATQ0SERIAL FLOW BHW AT\Q3PASS XON/XOFF OFF AT\X0PARITY 8N ATBREAK 5 AT\K5EXIT CHAR 043 ATS2=43ANS DUMB MODE ON AT#E1CMD ECHO ON ATE1RESULTS ON ATQ0RESULT TYPE MNPX ATV1\V2CONNECT MSG MDM ATW2CONN MNP- 0 AT-M0SPEED MATCH 1 AT%L1EQUALIZER 1 AT:E1FALLBACK 2 AT-Q2DATA ECHO OFF AT\E0INACT TIMER 00 AT\T0AUTO RETRAIN ON AT%E1COMPRESSION ALL AT%C3MAX BLK SIZE 256 AT\A3AUTO BUFF 0 AT\C0AUTO CHAR 000 AT%A0EMULATING HP OFF AT\H0PAUSE TIME 002 ATS8=2DTR 3 AT&D3MABP ADDRESS 001 AT^P1CARR DET 1 AT&C1DSR 0 AT\D0RING IND 1 AT\R1SPKR CTRL 1 ATM1SPKR VOL 2 ATL2LNG SPC DISC OFF ATY0DISC DELAY 000 AT%D0RDLB ENABLE OFF AT&T5DIAL MODE 4 ATX4PULSE DIAL 60% AT&P0PULSE MODE N AT%W0V23 HD EQU ON AT%O1GUARD TONE 2 AT&G2DATA CALL TONE ON AT-C12ND FC OFF AT-F0NM BIT VALUE 0 AT-E0PAR CHK 0 AT-P0MANUAL DIAL 0 AT:D0UPSHIFT BPS OFF AT*H0CELLULAR OFF AT)M0LINETYPE 000 AT@M0DETECT PHASE ON AT-J1MNP EXT SVC 1 AT-K1UNIV V.23 0 AT-V0CONNECT MSG 1ST AT@C0DUMB MODE OFF AT-H0BELL OFF ATB0CALL ABT DISAB OFF AT-Y0REVERSE ANS OFF AT-W0MIN CONN SPD 300 AT@UOK
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 Cisco Connection Online.
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, see Appendix A, "Managing Modems," in the Cisco AS5300 Universal Access Server Software Configuration Guide. A complete explanation can be found in the Cisco publication, New and Changed Commands for the Cisco AS5300. 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
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 will use the two separate modem code files described above, and Cisco IOS Release 11.3(2)T will use the single modem code file described in the "Downloading Modem Code" section that follows.
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 below. It is important to note that the current Flash-based file system does not support the erasing or deleting of individual files.
Figure 1 Copy Command Flow
For complete information, including the procedure for downloading the DSP software, see the "56K 12-Port Modem Cards for the Cisco AS5200 Universal Access Server" section in the Feature Guide for Cisco IOS Release 11.2(P). See the Related Documentation section for more information.
Downloading Modem Code—Cisco AS5300
In order to support K56flex modulation, Cisco AS5300 56K 12-port modules require a single modem code file that contains two modem code images: controller firmware and DSP software.
In addition to residing on the 12-port module, modem code also resides on the access server: one version is bundled with Cisco IOS software, and another version can exist in system Flash memory. The modem code residing in the access server is a single file comprised of the modem firmware image combined with the DSP software image.
After power on, Cisco IOS software uses its bundled modem code file or the existing mapped modem code file in system Flash memory to automatically update the DSP software. Cisco IOS software ensures that the system uses matching DSP software and modem firmware—which may include overriding the current firmware on the modem.
In some circumstances you may decide to manually update the modem code after the automatic download process completes. For details about how to download modem code and how to control the version used by the modems, see the Cisco publication, Installing 56K 12-Port Modem Modules in Cisco AS5300 Universal Access Servers, that shipped with your 56K modem card. See the Related Documentation section for more information.
For information about Fax DialOut, see the Cisco DialOut Utility User Guide at the following URL:
FAX DialOut is possible with the FAX firmware available in Cisco IOS Release 3.2.10 and with Cisco IOS Release 11.3(1). However there is a serious bug (CSCdj61765) with Abnormal Disconnects in Cisco IOS software. This is being worked on and a fix is expected shortly in an interim Cisco IOS Release 11.3(1.x).
Compatibility matrixes can be located at the following URLs:
Note See your account representative for a list of tested modems.
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,
•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
Cisco Connection Online
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
•Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.
For a copy of CCO's Frequently Asked Questions (FAQ), contact firstname.lastname@example.org. For additional information, contact email@example.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or firstname.lastname@example.org. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or email@example.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.