Release Notes for Cisco 800 Series Routers
Available Languages
Table Of Contents
Release Notes for Cisco 800 Series Routers
Supplementary Telephone Services for the Net3 Switch
Requirements for Supplementary Telephone Services Support
Configuring Caller ID for the Net3 Switch
Call Forwarding for the Net3 Switch
Configuring the Call Forwarding Method
Configuring the Call Forwarding Service
Cisco 800 Series Router Enhancements
TinyROM Version 1.3(1) Enhancements
TinyROM and Cisco IOS Behavior
Workaround for Earlier Versions of TinyROM
Upgrading TinyROM and IOS Software
Correction to Modem Support Information
Caller ID on the Cisco 813 Router
Activating the POTS Dial Feature
Call Scenarios for the POTS Dial Feature
Restricting Access to Your Network
PPP over Frame Relay Support (RFC-1973)
ROM Monitor set stop-bits Parameter
Obtaining Technical Assistance
Release Notes for Cisco 800 Series Routers
This document describes new and changed information for the Cisco 800 Series Routers Software Configuration Guide, Cisco 800 Series Routers Hardware Installation Guide, Quick Start Guide: Setting Up Cisco 800 Series Routers, Cisco 811 and Cisco 813 Routers Hardware Installation Guide, and Quick Start Guide: Setting Up Cisco 811 and Cisco 813 Routers.
Remote CAPI Default Setting
The default setting for the Remote Common Application Programming Interface (CAPI) feature has been changed. By default, this feature is disabled. To enable this feature, use the IOS rcapi server port command in global configuration mode:
rcapi server port [number]
no rcapi server port
where number is an optional parameter for the port number. If you do not enter a port number, the default port 2578 is used.
For more information, see the "Configuring Remote CAPI" chapter in the Cisco 800 Series Software Configuration Guide.
Supplementary Telephone Services for the Net3 Switch
The Cisco 800 series routers now support the following plain old telephone service (POTS) features for the European Telecommunications Standards Institute (ETSI) Net3 switch type:
•
Caller ID presentation and restriction are available for Denmark and Finland. For more information, see "Configuring Caller ID for the Net3 Switch."
•
•
•
Requirements for Supplementary Telephone Services Support
You must subscribe to the following Net3 switch services for these supplementary telephone services to work:
•
•
•
•
•
•
Configuring Caller ID for the Net3 Switch
To enable caller ID on the Net3 switch, configure the country type by using the IOS pots country command in global configuration mode:
pots country {dk|fi}
Note
To verify whether caller ID is enabled, use the show pots status command. The following is an example of the output from that command:
router# show pots statusPOTS Global Configuration:Country:DenmarkDialing Method:Overlap, Tone Source:Local, CallerId Support:YES----------------------Out Going Hunt:DisabledCall Forwarding for the Net3 Switch
The following types of call forwarding services (for voice calls only) are supported on the Net3 switch:
•
•
•
You can select one or more call forwarding services at a time. However, CFU has the highest precedence, CFB the next highest, and CFNR the lowest. The default setting is that no forwarding type is selected.
Note
To enable and configure this feature, follow these steps:
Step 1
Step 2
•
•
Configuring the Call Forwarding Method
You can select the method by which the call forwarding feature is controlled:
•
•
To enable the call forwarding method, use the IOS pots forwarding-method command in global configuration mode:
pots forwarding-method {functional | keypad}
[no] pots forwarding-method
Note
The following example configures the call forwarding feature to give control to the router:
router# configure terminalrouter(config)# pots forwarding-method functionalConfiguring the Call Forwarding Service
Table 1 shows the DTMF keypad command sequence that you enter to configure the call forwarding service.
You should hear a dial tone after you enter the DTMF commands if the call forwarding service is successfully configured. If you hear a busy signal, either the command is invalid or the switch does not support that service.
Displaying POTS Status
Use the show pots status command to display details of the call forwarding type. This status is not stored when you reboot. The following is an example of the screen output:
router# show pots statusPOTS Global Configuration:Country:DenmarkDialing Method:Overlap, Tone Source:Local, CallerId Support:YESOut Going Hunt:DisabledForwarding Method:functional method-------------------------------------Call Forwarding status:The Forwarding Method Enabled is CFUThe forwarded to Address is :33236877The served user Number(s) are :33795742The Forwarding Method Enabled is CFBThe forwarded to Address is :33236877The served user Number(s) are :ALL -> Will work for all numbers allocated to the terminal.Configuring CLIR
Configure CLIR by following these steps:
Step 1
Step 2
Step 3
Step 4
Debug POTS Commands
Use the following commands to debug problems with caller ID configuration:
•
•
Use the following commands for problems configuring other supplementary telephone features:
•
•
•
For more information about using debug commands, see the IOS documentation.
Prefix Dialing
Cisco 803 and Cisco 804 routers now support prefix dialing. You can add a telephone prefix and create a prefix filter to the dialed number for analog telephone calls. When a telephone number is dialed through the telephone port, the router checks for prefix filters. If the router finds a match, no prefix is added to the dialed number. If no filter match is found, the router adds the user-defined prefix to the called number.
Configuring a Prefix Number
To set a prefix to be added to a telephone number called, use the Cisco IOS pots prefix number command in global configuration mode:
pots prefix number number
no pots prefix number
where number is a prefix number from one to five digits in length. Only one prefix can be configured at a time, and configuring a new number will overwrite the existing one.
The following example sets the prefix number to 12345:
router# configure terminalrouter(config)# pots prefix number 12345Configuring a Prefix Filter
You can configure a prefix filter that is compared to the digits that you dial. If a match occurs, the prefix number is not added to the called number. To create a prefix filter, use the pots prefix filter command in global configuration mode:
pots prefix filter number
no pots prefix filter number
where number is a prefix filter from one to eight digits in length. You can define up to ten filters for your router. If you have reached the maximum number of filters defined, no new filter configurations are accepted until you remove at least one existing filter number using the no pots prefix filter number command.
The following are examples of how to set prefix filters:
router# configure terminalrouter(config)# pots prefix filter 192router(config)# pots prefix filter 1router(config)# pots prefix filter 9router(config)# pots prefix filter 0800router(config)# pots prefix filter 08456Cisco 800 Series Router Enhancements
Cisco 800 series routers now support the following features:
•
•
•
•
•
•
For more information about these features, see the Cisco IOS documentation set.
TinyROM Version 1.3(1) Enhancements
TinyROM performs the following functions for Cisco 800 series routers:
•
•
•
TinyROM has been enhanced to handle multiple Cisco IOS boot system commands, to ensure that your Cisco 800 series router boots with the IOS software.
The behavior of the IOS boot system command depends on which versions of TinyROM and IOS software you have installed on your router. The following section describes the behavior of various combinations of TinyROM and IOS software.
To view which versions of TinyROM and IOS are installed on your router, use the show version command in Exec mode.
Note
TinyROM and Cisco IOS Behavior
Table 2 summarizes the behavior of different versions of TinyROM and the IOS software.
Workaround for Earlier Versions of TinyROM
If you have TinyROM version 1.2(2) or later, you can rely on the boot fallback capability to ensure that IOS is booted, provided that you have at least one IOS image stored in Flash memory that is not marked for deletion.
Note
If you have TinyROM version 1.2(1) or earlier, ensure that IOS will be booted by following these steps:
Note
You should have only one boot system command in your configuration that specifies which file to boot. To verify your configuration, use the show running-config command. To obtain a list of filenames, use the dir command. Files marked with -r-x are valid IOS boot file images. For more information, see the output example following these steps.
The following examples show the screen output for the show run and dir commands:
router# show runBuilding configuration...Current configuration:!version 12.1!boot config flash:backup-configboot system flash c800-nsy6-mwlogging buffered 4096 debugging!...router# dirDirectory of flash:/0 ---- 49088 Jan 20 2000 05:11:57 TinyROM-1.2(1)1 ---- 49088 May 12 2000 04:43:56 TinyROM-1.3(1)2 -r-x 3664268 May 19 2000 22:07:32 c800-nsy6-mw58 -r-- 750 <no date> backup-config12582912 bytes total (8716288 bytes free)router#Upgrading TinyROM and IOS Software
If you wish to upgrade TinyROM and IOS software, do the following:
•
•
•
•
boot# copy flash:full-config running-config
Note
Correction to Modem Support Information
Cisco 803, 804, and 813 routers do not support the use of any modem that is connected to telephone ports. The sections describing the installation and troubleshooting of analog telephones, fax machines, and modems in the following documents apply only to analog telephones and fax machines:
•
•
•
•
•
Caller ID on the Cisco 813 Router
The caller ID command syntax documented in "Configuring Caller ID Display" (page 8-3) in
Chapter 8, "Configuring Enhanced Voice Features," of the Cisco 800 Series Routers Software Configuration Guide is incorrect. The correct information is as follows:By default, the caller ID feature is disabled. To enable this feature, use the IOS caller-id command in the dial-peer configuration command mode.
caller-id
[no] caller-id
POTS Dial Feature
The Cisco 813 router supports the plain old telephone service (POTS) dial feature for Japanese telephones. This feature can be activated by a dial application on your workstation that dials a telephone number for the POTS port on the Cisco 813 router. The telephone connected to the port can be on- or off-hook when the dial command is issued. If the telephone is on-hook, the router rings the telephone, waits until the telephone is taken off hook, then dials the number requested. If the telephone is off-hook when the command is issued, the router dials the number requested, provided the telephone is receiving a dial tone.
Activating the POTS Dial Feature
Each time you wish to activate this feature using your dial application, enter the following IOS command in Exec mode:
test pots port dial number[#]
where port is the port number 1 or 2, and number is the telephone number to dial.
Note
The following example shows the POTS dial command:
router# test pots 1 dial 4085551234#Displaying POTS Call State
To show the current state of POTS calls and the most recent event received by the call switching module (CSM), use the show pots csm command in Exec mode.
show pots csm port
where port is port number 1 or 2.
Output Example
The following is an example of the show pots csm command screen output:
router# show pots csm 1POTS PORT: 1CSM Finite State Machine:Call 0 - State: idle, Call Id: 0x0Active: noEvent: CSM_EVENT_NONE Cause: 0Call 1 - State: idle, Call Id: 0x0Active: noEvent: CSM_EVENT_NONE Cause: 0Call 2 - State: idle, Call Id: 0x0Active: noEvent: CSM_EVENT_NONE Cause: 0router#Disconnecting a POTS Call
To disconnect a telephone call for the POTS port on the router, use the test pots port disconnect command in Exec mode.
test pots port disconnect
where port is the port number 1 or 2.
The following example disconnects a telephone call from POTS port 1:
router# test pots 1 disconnectrouter#POTS Debug Command
To display the status of calls made to and from the POTS ports, enter the following command in Exec mode:
debug pots csm
Entering this command activates events by which your dial application can determine the progress of calls to and from the ports.
Debug Message Formats
Debug messages are displayed in one of two formats that are relevant to the POTS dial feature:
hh:mm:ss: CSM_STATE: CSM_EVENT, call id = ??, port = ?
or
hh:mm:ss: EVENT_FROM_ISDN:dchan_idb=0x???????, call_id=0x????, ces=? bchan=0x????????, event=0x?, cause=0x??
where:
•
•
•
•
•
•
•
•
•
•
CSM States
The following table shows the values for CSM states.
CSM Events
The following table shows the values for CSM events.
Events
The following table shows the values for events that are translated into CSM events.
Cause
This table shows cause values that are assigned only to call-progressing events.
Call Scenarios for the POTS Dial Feature
This section describes three call scenarios and shows examples of the IOS command output for each scenario. The output examples for the debug and disconnect commands show the sequence of events that occur during a POTS dial call.
Call Scenario 1
In this call scenario, port 1 is on-hook, the application dial is set to call 4085552221, and the far end successfully connects. The following example shows the IOS command:
router# test pots 1 dial 4085552221#router#The following screen output shows an event indicating that port 1 is being used by the dial application:
01:58:27: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 1The following screen output shows events indicating that the CSM is receiving the application digits of the number to dial:
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1The following screen output shows that the telephone connected to port 1 is off hook:
01:58:39: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1The following screen output shows a call-proceeding event pair indicating that the router ISDN software has sent the dialed digits to the ISDN switch:
01:58:40: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0x0, event=0x3, cause=0x001:58:40: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id =0x8004, port = 1The following screen output shows the call-progressing event pair indicating that the telephone at the far end is ringing:
01:58:40: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF, event=0x5, cause=0x001:58:40: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8004, port = 1The following screen output shows a call-connecting event pair indicating that the telephone at the far end has answered:
01:58:48: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF, event=0x4, cause=0x001:58:48: CSM_PROC_CONNECTING: CSM_EVENT_ISDN_CONNECTED, call id = 0x8004, port = 1The following screen output shows a call-progressing event pair indicating that the telephone at the far end has hung up, and the calling telephone is receiving an in-band tone from the ISDN switch:
01:58:55: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF, event=0x5, cause=0x1001:58:55: CSM_PROC_CONNECTED: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8004, port = 1The following screen output shows that the telephone connected to port 1 has hung up:
01:58:57: CSM_PROC_CONNECTED: CSM_EVENT_VDEV_ONHOOK, call id = 0x8004, port = 1The following screen output shows an event pair indicating that the call has been terminated:
01:58:57: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF, event=0x0, cause=0x001:58:57: CSM_PROC_NEAR_END_DISCONNECT: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8004, port = 1813_local#Call Scenario 2
In this scenario, port 1 is on-hook, the application dial is set to call 4085552221, and the destination number is busy. The following example shows the IOS command:
router# test pots 1 dial 4085552221#router#The following screen output shows that your dial application is using port 1:
01:59:42: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 1The following screen output shows the events indicating that the CSM is receiving the application digits of the number to call:
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1The following screen output shows an event indicating that the telephone connected to port 1 is off-hook:
01:59:52: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1The following screen output shows a call-proceeding event pair indicating that the telephone at the far end is busy:
01:59:52: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0x0, event=0x3, cause=0x1101:59:52: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 0x8005, port = 1The following screen output shows a call-progressing event pair indicating that the calling telephone is receiving an in-band busy tone from the ISDN switch:
01:59:58: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0xFFFFFFFF, event=0x5, cause=0x001:59:58: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8005, port = 1The following screen output shows an event indicating that the calling telephone has hung up:
02:00:05: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_VDEV_ONHOOK, call id = 0x8005, port = 1The following screen output shows an event pair indicating that the call has terminated:
02:00:05: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0xFFFFFFFF, event=0x0, cause=0x002:00:05: CSM_PROC_NEAR_END_DISCONNECT: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8005, port = 1Call Scenario 3
In this call scenario, port 1 is on-hook, the application dial is set to call 4086661112, the far end successfully connects, and the command test pots disconnect terminates the call.
router# debug pots csmrouter# test pots 1 dial 4086661112router#The following screen output follows the same sequence of events as shown in Call Scenario 1:
1d03h: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 11d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1bchan=0x0, event=0x3, cause=0x01d03h: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 0x8039, port = 11d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1bchan=0xFFFFFFFF, event=0x5, cause=0x01d03h: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8039, port = 1router# test pots 1 disconnectThe test pots disconnect command disconnects the call before you have to put the telephone back on hook.
1d03h: CSM_PROC_CONNECTING: CSM_EVENT_VDEV_APPLICATION_HANGUP_CALL, call id = 0x8039, port = 11d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1bchan=0xFFFFFFFF, event=0x0, cause=0x01d03h: CSM_PROC_DISCONNECTING: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8039, port = 11d03h: CSM_PROC_DISCONNECTING: CSM_EVENT_TIMEOUT, call id = 0x8039, port = 1Restricting Access to Your Network
In Chapter 4, "Configuring Advanced Networks," in the Cisco 800 Series Routers Software Configuration Guide, the configuration example for preventing IP spoofing in the "Restricting Access to Your Network" section is incorrect.
The correct configuration example shown in step 6 (on page 4-36) should be:
router(config)# access-list 100 deny ip 192.168.1.0 0.0.0.255 anyTACACS+ with AAA
Cisco 800 series routers now support the Terminal Access Controller Access Control System Plus (TACACS+) protocol through Telnet. TACACS+ is a Cisco proprietary authentication protocol that provides remote access authentication and related network security services, such as event logging. User passwords are administered in a central database, rather than in individual routers. TACACS+ also supports separate modular authentication, authorization, and accounting (AAA) facilities that are configured at individual routers.
For information on how to configure TACACS+, refer to the "Configuring TACACS+" chapter in the Security Configuration Guide. For information on TACACS+ commands, refer to the "TACACS, Extended TACACS, and TACACS+ Commands" chapter in the Security Command Reference.
Cisco 800 series routers do not support the following protocols:
•
•
PPP over Frame Relay Support (RFC-1973)
Cisco 800 series routers do not support PPP protocol over Frame Relay.
CiscoView Application Support
The CiscoView application supports the Cisco 800 series routers. The CiscoView application provides dynamic status, statistics, and comprehensive configuration information for Cisco switches, routers, concentrators, and adapters. It displays a graphical view of Cisco devices. This network management tool also provides configuring and monitoring functions and offers basic troubleshooting tips.
ROM Monitor set stop-bits Parameter
This release supports only the setting of 1 for the ROM monitor set stop-bits parameter. The display in the "Configuring Basic Configuration Parameters" section in Appendix D, "ROM Monitor," of the Cisco 800 Series Routers Software Configuration Guide incorrectly implies that you can set the console port stop bits to 1 or 2.
Obtaining Documentation
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Obtaining Technical Assistance
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the Web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco Connection Online
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
•
•
•
–
–
You can e-mail questions about using CCO to cco-team@cisco.com.
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC Web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following Web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate and value your comments.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)