Table Of Contents
Release Notes for the Cisco SIP Proxy Server Version 1.1 on Solaris
Known Problems in this Release
Admendments to the Documentation
Installing the Cisco SIP Proxy Server Software
Obtaining Technical Assistance
Release Notes for the Cisco SIP Proxy Server Version 1.1 on Solaris
May 2001
This document lists the known problems in the Cisco SIP Proxy Server Version 1.1 and contains information about the Cisco SIP Proxy Server that was not included in the Cisco SIP Proxy Server Administrator Guide.
Sections in this document include the following:
•
Known Problems in this Release
•
•
Related Documentation
In addition to this release note, use the following publications to learn how to install and use the Cisco SIP Proxy Server:
•
•
Recommended Sun Platforms
The following two Sun Microsystems' platforms are the recommended platforms on which to run the Cisco SIP Proxy Server:
•
–
–
–
–
–
•
–
–
–
–
Known Problems in this Release
This section lists the currently known problems in the Cisco SIP Proxy Server, Version 1.1.
Problem: shmem segment tmpnam files are not deleted (CSCdr61706)
Problem Description: Each time the Cisco SIP Proxy Server is started, a file named filexxxxx.sem (where xxxxx is a random string) is created in the /tmp directory. These files do no cause any operational problems but one might want to occasionally delete the files to eliminate clutter.
Recommended Action: None.
Problem: The Cisco SIP Proxy Server does not support SIP and HTTP simultaneously (CSCdr67142)
Problem Description: The Cisco SIP Proxy cannot establish a TCP connection or initiate a HTTP transfer regardless of the specifications for Apache-specific configuration directives that would allow it to do so.
Recommended Action: None. If HTTP support is required, a separate copy of Apache Web Server must be loaded. However, to provide adequate performance and ease of administration, we recommend that you run the Apache Web Server (httpd) and the Cisco SIP Proxy Server (sipd) on separate machines.
Problem: Static Registry entry configuration problems (CSCds07314)
Problem Description:
–
If an action is specified against Static_Registry_Contact as follows, the contact information of the entry will be interpreted as it is "user@host" inside the code.
<StaticRegistry 11>
the Static_Registry_User 222
Static_Registry_Contact user@host;action=redirect ....
The interpretation should be:
"<sip:user@host;user=phone>;action=redirect"
Recommended Action: Only enter a Static_Registry_Contact as user@host. Do not add any additional parameters.
–
Misspelling the value in the Contact_Age directive of a Static Registry entry might cause the Registry Entry to not be added. For example, if the value for the Contact_Age directive is specified as "Permat" instead of "Permanent" (a valid value), the Static Registry entry will not be added.
Recommended Action: Verify the spelling of the value specified in the Contact_Age directive.
–
Only one contact can be added for the same Static_Registry_User with different Static_Registry_User_Type. For example, in the sipd.conf or sip_registry.conf file, the following two entries are listed.
<StaticRegistry 10.1>
Static_Registry_User_Type IP
Static_Registry_User 22945
Static_Registry_Contact 0019193922913@lmetzger-linux
Static_Registry_Contact_User_Type PHONE
Static_Registry_ContactPort 5060
Static_Registry_TransportProtocol UDP
Static_Registry_ContactAge Permanent
Static_Registry_Delete_or_Add ADD
</StaticRegistry>
and
<StaticRegistry 10.2>
Static_Registry_User_Type PHONE
Static_Registry_User 22945
Static_Registry_Contact 0019193922914@lmetzger-linux
Static_Registry_Contact_User_Type PHONE
Static_Registry_ContactPort 5060
Static_Registry_TransportProtocol UDP
Static_Registry_ContactAge Permanent
Static_Registry_Delete_or_Add ADD
</StaticRegistry>
The 10.2 entry will overwrite the 10.1 entry and only 0019193922914@lmetzger-linux will be returned during Registry lookup for user 22945 regardless of the user type.
Recommended Action: None.
Problem: Cisco SIP Proxy Server does not support SIP message lines that exceed 1024 bytes (CSCds22652)
Problem Description: If an incoming SIP message has a header or Request-URI that exceeds 1024 bytes, the message might be rejected by the server with a "400 Bad Request" response.
Recommended Action: Ensure that messages with headers or Request-URIs greater than 1024 are not sent.
Problem: Parsing problems occurring with sipd.conf directives (CSCds32514)
Problem Description: Various sipd.conf file directives are not properly range checked. When configuring these parameters, care must be taken to configure them correctly.
Please be aware of the following when configuring the sipd.conf file:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Recommended Action: None.
Problem: TCB age-off timer bug might exist during requests or response retransmission (CSCds42804)
Problem Description: During the retransmission of requests or responses, a sipd child process with a Transaction Control Block (TCB) lock could crash after the age-off timer for that TCB has started. While this problem has never occurred, it is possible. If this problem should occur, the process that handles the age-off timer for the TCB will hang until it is restarted by the child process. There is no method of identifying a process that is in this state.
Recommended Action: None.
Problem: Syntax error message line number is incorrect and only the first syntax error is reported (CSCds52504)
Problem Description: When a syntax error occurs in the sipd.conf file, the line number reported in the syntax error message is incorrectly reported. The number that appears in the syntax error message is always the last line of the sipd.conf file and not the line in which the error occurred. In addition, only the first syntax error in the sipd.conf file is reported.
Recommended Action: None.
Problem: Static routes targets that are not resolvable are not processed (CSCds73342)
Problem Description: If a static route entry is not resolvable, it is not processed. For example, if two static routes to a target are configured as gw1.domain.com and gw2.domain.com and the gw1.domain.com route has a higher priority and weight, it is selected. However, if the attempt to resolve gw1.domain.com fails, the Cisco SIP Proxy server does not try the second route, gw2.domain.com. However, if gw1.cisco.com is resolvable but down, the Cisco SIP Proxy Server will try the route until it has exhausted its retransmission attempts and then it will try gw2.domain.com.
Recommended Action: Ensure that the static route target entries are resolvable. Static routes should be IP address or FQDNs that can be resolved via a DNS lookup.
Problem: The "include" directive does not work for some block configuration directives (CSCds73530)
Problem Description: Block configuration directives (for example, <StaticRouteID> and <StaticRegistryID>) cannot be placed in a separate file and "included" in the sipd configuration file. Static routes and static registry entries must be defined in the main sipd.conf file.
Recommended Action: None.
Problem: Signal "Bus error" in Solaris (CSCdu09270)
Problem Description: when running the Cisco SIP Proxy Server under stress (100 cps) on Sun Solaris prior to release 2.8, the Cisco SIP Proxy Server child process can exit due to the receipt of a "Bus error" signal. The frequency of the child exit is found to be once every several hours under stress. This problem only occurs on Solaris and not on Linux platform. It is not reproducable when running on Solaris 8.
This is a possible problem with the libc shipped with the Sun OS prior to Solaris 8.
Recommended Action: Upgrade the server to run on Solaris 8 platform.
Problem: Duplicate Contacts in first REGISTER for a user undetected (CSCds50145)
Problem Description: This problem occurs if the first REGISTER for a user/device has more than one identical Contact header.
For example, a user named "abc" sends the first REGISTER with duplicate Contacts:
REGISTER sip:domain.com SIP/2.0
To: abc@domain.com
Contact: sip:abc@machine1.domain.com:5055
Contact: sip:abc@machine1.domain.com:5055
If the Cisco SIP Proxy Server does receive duplicate Contacts in the first REGISTER, it will not fork duplicate branches when it handles a call for the user.
REGISTER sip:domain.com SIP/2.0
To: abc@domain.com
CSeq:1 REGISTER
Contact: <sip:abc@machine1.domain.com:5055>;expires=3600
REGISTER sip:domain.com SIP/2.0
To: abc@domain.com
CSeq: 2 REGISTER
Contact:<sip:abc@machine1.domain.com:5055>;expires=60
Recommended Action: Do not send duplicate Contacts in the first REGISTER for a user. If an user agent do send duplicate Contacts, this does not hurt or affect call forwarding to that user.
Problem: Start Sip_Services after a Farm DBs Old entries are deleted (CSCds56981)
Problem Description: If the proxy server has been down for more than the value in Cisco_Routing_Max_DB_Age_on_Boot or Cisco_Registry_Max_DB_Age_On_Boot, the ServerRoot/logs/*.db files will be removed or cleaned. Otherwise, these values may be re-used if a farm member tries to "sync" in a farm mode.
Recommended Action: None.
Problem: Add better handling for a non-responsive Sip_Services daemon (CSCdt11551)
Problem Description: The sipd maintains a tcp connection to Sip_Services. This is normally attempted when trying to lock the registry and routing database. If this fails, Sip_Services may exist and a connect should be re-tried.
Development efforts are made to "kill" and restart Sip_Services when the connection failure is detected. The connection failure currently generates error messages.
Recommended Action: None.
Problem: Add Registry/Routing Code changes to support TEL URL (CSCdt35294)
Problem Description: Proxy parses tel Urls completely based on the rules specified in RFC 2806. At this point, there are no routing changes based on tel:url additional fields. For example:
In "tel:1111;phone-context=919;phone-context=456", only 1111 is used for routing the call, like in sip:url. The additional fields are not used.
Also, tel url is transformed to a sip:Url as follows.
sip:1111@whatever-proxy.com SIP/2.0
RecordRoute:<sip:1111@whatever-proxy.com;parameters including phone-context>
Recommended Action: Currently, there is no intelligence to change the number from "tel:392-8076;phone-context=919" to "tel:+1-919-392-8076".
Problem: Log file check and verification needed for proxy server (CSCdt50814)
Problem Description: When the Cisco SIP Proxy Server is started, it writes the logs to the error_log and access_log files in the logs subdirectory by default. The log files can be deleted manually while the server is still running, the Cisco SIP Proxy Server will continue to run but no logs will be logged due to the deletion of the log files.
Recommended Action: After the deletion of the log files, you can "graceful restart" the server, so new log files can be created and the server can then continue the logging process.
Problem: Looped Contact headers in 302 are forwarded upstream (CSCdt60611)
Problem Description: When the Cisco SIP Proxy Server receives a Contact header in a 3xx response that has already been tried before, it detects it but does not invalidate that Contact. It forwards this Contact upstream, if it happens to be the best branch.
This occurs only if the proxy server is in non-recursive mode, that is, value of directive Recursive is Off.
Recommended Action: Run the proxy server in Recursive mode.
Problem: sipdctl & sipd should use relative paths for conf, logs & libraries (CSCdt65349)
Problem Description: The sipdctl tool contains absolute paths to various file locations such as sipd.pid, Sip_Services.pid, sip_registry.conf and sip_routing.conf. They will need to be manually modified if different file locations will be used.
Also, the sipd process looks for the sipd.conf file at the pre-configured path <CmdBold>ServerRoot<CmdBold><CmdArg>/conf/sipd.conf<noCmdAr>. These tags are markup languages and should be removed if the editor you use does not support these tags.
Recommended Action: To use a different configuration file, one can use the "-f" switch to force sipd to look for a different configuration file.
For example, to force sipd to read in the sipd.conf file from the user's home directory. Use <CmdArg>sipd -f ~/sipd.conf<noCmdArg>
Problem: Route Farm - 500 Internal Server Error (CSCdt74891)
Problem Description: When multiple nodes of Cisco SIP Proxy Server are sharing static routes in a farm mode, "500 Internal Server Error" response can be generated by the Cisco SIP Proxy Server.
A "500 Internal Server Error" message is created at around the 800th call when 7,000 static routes shared by two Cisco SIP Proxy Server farm members with incoming calls alternating between them.
Recommended Action: None.
Problem: Proxy will crash if SharedMemorySize too small for call rate (CSCdt87934)
Problem Description: The Cisco SIP Proxy Server can crash if it is not configured with enough shared memory to handle the call rate.
Recommended Action: Increase the value of SharedMemorySize directive in sipd.conf file.
To configure the total usable shared memory segment size on Linux or Solaris platform, please follow the instructions in the README.cisco file.The Cisco SIP Proxy Server proxy can stop processing calls if not enough shared memory is allocated to handle the traffic load.
Problem: 8k shared memory leak per graceful restart (CSCdu00628)
Problem Description: When "sipdctl graceful" is issued, the master sipd leaks about 8K of shared memory. The master sipd has a parent process ID of 1 and the leak can be observed in the output of top command.
Recommended Action: None.
Problem: Rolling No space left on device (CSCdu01816)
Problem Description: When the Cisco SIP Proxy Server box runs out of disk space, the following rolling messages prints on the screen.
(10025|1) malloc:No space left on device
(10025|1) /opt/sip/libexec/../logs/registry_db:No space left on device
Recommended Action: None.
Problem: sipdctl configtest does not work properly (CSCds53849)
Problem Description: The "sipdctl configtest" command is not supported. It does not accurately detect many syntax errors. Also, an incorrect line number is reported when a syntax error is detected.
Examples of errors that are not detected include misconfigurations in the <StaticRoute ID> and <StaticRegistry ID> block directives, and illegal values given in non-boolean directives.
Recommended Action: None. The sipd.conf configuration file can only be verified by successfully loading the server.
Problem: "expires" parameter/header not generated in 3xx response (CSCds85488)
Problem Description: When the server is running in redirect mode and it returns a 3xx response, it does not put an "expires" parameter in the Contact header or a separate Expires header. This means all Contacts generated by the proxy have an expiration of 1 hour by default. This can cause a problem if upstream user agent is caching the Contact information, based on their life.
Recommended Action: None.
Problem: Radius should attempt alternate server if primary unreachable (CSCds91174)
Problem Description: The radius module should attempt to contact the secondary radius server if the primary radius server is unreachable.
If the primary radius server is unavailable, the call will continue after a short delay, but no accounting records will be written.
Recommended Action: None.
Problem: External entity failure causes reduced performance (CSCdt35155)
Problem Description: Server child processes have no means to communicate failures of external entities to the other child processes. A failure of an external entity such as radius, dns, subscriber database, is not communicated to all child processes.
Server performance can drop significantly, depending on the number of child processes being executed.
Recommended Action: Reduce the number of child processes.
Problem: Forking to static registry entries fails after restart (CSCdt46712)
Problem Description: After the proxy server is restarted via "./sipdctl graceful", subsequent requests are not forked to all Static_Registry_Contact(s) in StaticRegistry entries. Only the last entry found in sipd.conf for that particular Static_Registry_User is used when proxying requests.
Recommended Action: Restart the server by doing the following:
–
–
–
Note
Problem: User agents on same box/different port disallowed (CSCdu00398)
Problem Description: Proxy will not terminate calls to a user agent that runs on the same box but different port.
Recommended Action: User agents should not be running on the same box as the proxy.
Problem: Static routes need to have unique tags (CSCdu05953)
Problem Description: When more than one route is assigned the same tag/number, only the first route is used. Subsequent routes with the same tag/number is ignored. An error message is printed only if DebugFlag directive under Cisco_Routing module is On.
For example the following two routes have a tag value of 10.
<StaticRoute 10>
Static_Route_DestinationPattern 919.......
Static_Route_Type PHONE
Static_Route_NextHop tisu-view1.cisco.com
Static_Route_NextHopPort 5060
Static_Route_TransportProtocol UDP
Static_Route_Priority 1
Static_Route_Weight 5
Static_Route_Delete_or_Add ADD
</StaticRoute>
<StaticRoute 10>
Static_Route_DestinationPattern 919.......
Static_Route_Type PHONE
Static_Route_NextHop grigio.cisco.com
Static_Route_NextHopPort 5060
Static_Route_TransportProtocol UDP
Static_Route_Priority 1
Static_Route_Weight 5
Static_Route_Delete_or_Add ADD
</StaticRoute>
The second route (with Static_Route_NextHop value of grigio.cisco.com) is ignored.
Recommended Action: The sysadmin_csps_regroute tool can be used to add/update routes and the system administrator does not need to enter route tags. See the Administrator guide for more detail on the sysadmin_csps_regroute tool.
Problem: sysadmin_csps_regroute export says cannot access file (CSCdu10003)
Problem Description: When the Cisco SIP Proxy Server is installed from the root user, the registry and routing database are created in logs subdirectory with file ownership re-assigned to the "User" and "Group" directives in sipd.conf file.
After this installation, if the Cisco SIP Proxy Server is run as the root user, sysadmin_csps_regroute can only "export" to a directory owned by the "User" and "Group" specified in sipd.conf file. The eXport function is not allowed to access the registry and routing database created earlier.
Recommended Actions:
If sipd is installed from the root user and sysadmin_csps_regroute is being run also from the root user afterwards, sysadmin_csps_regroute can only eXport to a directory owned by the User and Group specified in sipd.conf."
Problem: Permission denied in sysadmin_csps_regroute (CSCdu10017)
Problem Description: When the Cisco SIP Proxy Server is started by "root" user, the sysadmin_csps_regroute tool cannot be run by any user other than the root or the one specified in the "User" and "Group" directives in sipd.conf file. This is because the file ownership of registry and routing database is replaced by the user specified in the sipd.conf file when the Cisco SIP Proxy Server is run by root user.
Recommended Action: Run the sysadmin_csps_regroute as root user or the one specified in the sipd.conf file. This is only needed when the Cisco SIP Proxy Server is to be started by root user.
Problem: Sip_services get "killed" when sysadmin_csps_regroute exits (CSCdu12370)
Problem Description: When starting sysadmin_csps_regroute and sipd with the following sequence, the Sip_Services daemon can be "killed" while the Cisco SIP Proxy Server is still running. However, the Sip_Services daemon will be started again once the Cisco SIP Proxy Server discovers that the process does not exist.
Recommended Action:
Do the following to solve this problem.
–
Note
> ./sysadmin_csps_regroute
Starting Sip Services . Success
Cisco SIP Proxy Server Command Line Interface V1.112
--------------------------------------------------------
Main Menu
Using Registry Database
--------------------------------------------------------
Choose an option below:(Items in <> are required input.)
<S> Select registry (default) or routing database
<D> query, add to, or delete from the Database
<I> Import a configuration <file> with route/registry entries
<X> eXport current database entries to a configuration <file>
<Q> or ^C (exit)
–
lab 27760 1 0 15:12 pts/0 00:00:00
/usr/local/sip/bin/Sip_Services
–
Version of CSPS :1.07 - Experimental Version
Version in Config file :1.07 - Experimental Version
../bin/sipdctl start:sipd started
–
lab 27760 1 0 15:12 pts/0 00:00:00
/usr/local/sip/bin/Sip_Services
lab 27767 1 2 15:16 ? 00:00:00 /usr/local/sip/bin/sipd
lab 27768 27767 0 15:16 ? 00:00:00 /usr/local/sip/bin/sipd
lab 27769 27767 0 15:16 ? 00:00:00 /usr/local/sip/bin/sipd
lab 27770 27767 0 15:16 ? 00:00:00 /usr/local/sip/bin/sipd
lab 27771 27767 0 15:16 ? 00:00:00 /usr/local/sip/bin/sipd
lab 27772 27767 0 15:16 ? 00:00:00 /usr/local/sip/bin/sipd
–
–
lab 27767 1 0 15:16 ? 00:00:00 /usr/local/sip/bin/sipd
lab 27768 27767 0 15:16 ? 00:00:00 /usr/local/sip/bin/sipd
lab 27769 27767 0 15:16 ? 00:00:00 /usr/local/sip/bin/sipd
lab 27770 27767 0 15:16 ? 00:00:00 /usr/local/sip/bin/sipd
lab 27771 27767 0 15:16 ? 00:00:00 /usr/local/sip/bin/sipd
lab 27772 27767 0 15:16 ? 00:00:00 /usr/local/sip/bin/sipd
Sip_Services is gone.
Problem: access_log and error_log file size (CSCdu12376)
Problem Description: When the error_log or the access_log file size grows to 2147483647 bytes (~2.1GB), the Cisco SIP Proxy Server stops logging to the file.
Recommended Action: Use "logrotation" to avoid this problem.
Problem: Server does not print log if it fails to start (CSCdu05913)
Problem Description: When a syntax error occurs while parsing the RAS module config in sipd.conf, sipd may not start up, and does not print any error messages. Also, error_log file will not be written if the log rotation is turned on.
Recommended Action: Avoid syntactical mistakes in RAS module configuration and use the top and/or ps commands to check the status of sipd and Sip_Services processes.
Problem: sysadmin_csps_regroute import parsing is case-sensitive (CSCdu16323)
Problem Description: The import function of the sysadmin_csps_regroute tool only accepts case-sensitive directives names from sip_registry.conf. and sip_routing.conf. files.
Recommended Action: Following are examples of directives names that the tool recognizes.
<StaticRegistry 10.1>
Static_Registry_User_Type IP
Static_Registry_User lmetzger
Static_Registry_Contact 0019193922913@lmetzger-linux
Static_Registry_Contact_User_Type PHONE
Static_Registry_ContactPort 5060
Static_Registry_TransportProtocol UDP
Static_Registry_ContactAge Permanent
Static_Registry_Delete_or_Add ADD
</StaticRegistry>
<StaticRoute 10>
Static_Route_DestinationPattern 001919392....
Static_Route_Type PHONE
Static_Route_NextHop sip_gw1.cisco.com
Static_Route_NextHopPort 5060
Static_Route_TransportProtocol UDP
Static_Route_Priority 1
Static_Route_Weight 5
Static_Route_Delete_or_Add ADD
</StaticRoute>
Problem: sysadmin_csps_regroute treats the directives in sipd.conf as case-sensitive and it exports two registry directives with incorrect case (CSCdu16227)
Problem Description: sysadmin_csps_regroute treats the directives in sipd.conf as case-sensitive. When using sysadmin_csps_regroute and the eXpport function is chosen for registry db, sysadmin_csps_regroute generates the following two directives with incorrect case: Static_Registry_User_Type and Static_Registry_Contact_User_Type. These are not stored in the database and do not seem to have a direct impact on call processing,
Recommended Action: If a user decides to import an exported registryconfiguration file using sipd.conf, then nothing needs to be done. If a user decides to import an exported registry configuration file using sysadmin_csps_regroute, these two directives (Static_Registry_User_type and Static_Registry_Contact_User_type) need to be manually modified to Static_Registry_User_Type and Static_Registry_Contact_User_Type respectively to insure correctness.
Admendments to the Documentation
This section contains information that was not included in the Cisco SIP Proxy Server Version 1.1 Administrator Guide or the CD Installation Guide for the Cisco SIP Proxy Server on Solaris.
Installing the Cisco SIP Proxy Server Software
The installation procedure documented in the "Installing the Cisco SIP Proxy Server Software" section describes how to install the Cisco SIP Proxy Server in such a manner that it will run as root when started.
The Cisco SIP Proxy Server needs to be installed by root user. After the server is installed, the root user can change the ownership of the sipd.conf file in the conf subdirectory so that a permitted user can change the server configuration. By default, the directory permission tologs subdirectory is set to 777, this allows any user to run the CSPS.The server administrator can change the permission by issue the Unix command "chmod" .
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.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0104R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
Guest
