|
|
Table Of Contents
Release Notes for the Cisco H.323 Signaling Interface, Release 2.21 and Related Patches
Installing HSI Software Patches
New Features in Release 2.21 Patch 1
Known Issues and Operational Recommendations
Obtaining Technical Assistance
Release Notes for the Cisco H.323 Signaling Interface, Release 2.21 and Related Patches
October 14, 2004
Introduction
The Cisco H.323 Signaling Interface (HSI) interoperates with the Cisco PSTN Gateway 2200 (PGW 2200) to enable calls between the Public Switched Telephone Network (PSTN) and the H.323 network. The HSI provides:
•
Translation of signaling protocols for establishing, controlling, and releasing calls
•
•
•
•
•
•
Contents
•
•
•
•
•
Platform Support
Hardware
The Cisco HSI is targeted to run on a Sun Netra V120 platform with two 36 GB hard disk drives.
Software
The Cisco HSI runs on the Solaris 8 operating system.
Related Documentation
Before Installation
Before you install the Cisco HSI software, consult the Cisco H.323 Signaling Interface User Guide at:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/hsi221/index.htm
After Installation
After you install the Cisco HSI software, consult the following related documentation for information on configuring and provisioning your system:
•
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/hsi221/index.htm•
General Purpose Documents
•
•
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/swinstl/index.htm
•
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/omts/index.htm
•
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/prvgde/index.htm
Installation Requirements
Installation Checklist
Before you attempt to install the HSI application software, you must obtain the following information:
•
•
•
•
•
•
•
•
•
•
•
•
•
Installing HSI Software Patches
When you install an HSI software patch, the included updated binary, provisioning, library, and script files will be updated in the following directories depending on the type of file being delivered:
•
•
Before installing a patch, you must shut down the Cisco HSI application, as the affected programs are part of the running system. To ensure that the HSI application has been shutdown, execute the following command:
# /etc/init.d/CiscoGW stopManual Patch Installation
Complete the following procedure to install a software patch:
Step 1
Step 2
mkdir /export/PATCHESStep 3
Note
Step 4
uncompress hsi-2_21_p<n>.tar.Ztar xvf hsi-2_21_p<n>.tarStep 5
Step 6
cd ./2.21_P<n>./install_patch.shStep 7
/etc/init.d/CiscoGW startPatch Removal
Complete the following procedure to remove a software patch:
Step 1
Step 2
/etc/init.d/CiscoGW stopStep 3
cd /export/PATCHES/2.21_P<n>./uninstall_patch.sh
Note
Step 4
/etc/init.d/CiscoGW start
Cisco HSI 2.21 Patch 8
This section includes information pertaining to Cisco HSI 2.21 Patch 8:
•
Caveats Resolved by Patch 8
CSCef43673
2.21
3
CCM-HSI-PGW2200 H323 to PSTN A-side cannot hear announcement.
Symptoms: On calls from H323 to PSTN, the Cisco HSI should start H245 negotiation on CPG. This allows PSTN network announcements to be passed back to the originating endpoint. Currently, the HSI opens the path at alert. In this case, the CCM did not open the H.245 connection when it received the H.225 Progress message with a PI-8 IE. The HSI did not put the H.245 address into the H.225 Progress message.
Resolution: This problem is resolved in the HSI 2.21 Patch 8. The PSTN A-side can now hear the announcement.
Cisco HSI 2.21 Patch 7
This section includes information pertaining to Cisco HSI 2.21 Patch 7:
•
Caveats Resolved by Patch 7
The following anomalies identified in the operation of the Cisco HSI are resolved by Patch 7.
CSCec81352
2.21
3
The HSI should send CPG (w/ Inband info) upon receiving Alerting (PI=8).
Symptoms: HSI does not send CPG with Inband info upon receiving Alerting with PI=8.
Resolution: The HSI now Maps H.323 Alerting with PI=8 to EISUP CPG.
CSCed42451
2.21
3
The HSI does not send SDP-Notification with blind call transfer.
Symptoms: Muted call.
Resolution: The HSI now sends an SDP-Notification message with a blind call transfer.
Cisco HSI 2.21 Patch 6
This section includes information pertaining to Cisco HSI 2.21 Patch 6:
•
Caveats Resolved by Patch 6
The following anomalies identified in the operation of the Cisco HSI are resolved by Patch 6.
CSCuk45307
2.21 P5
3
The HSI ignored SDP information in NOTIFICATION messages.
Symptoms: The HSI ignored SDP information in NOTIFICATION messages.
Resolution: The HSI software is modified to process SDP information appropriately.
CSCeb54635
2.21
2
A Notification message is not sent upon receiving a CPG message with inband information.
Symptoms: An MDCX is not sent to the NAS when Inband Information is available in a CPG message. An MDCX is sent to the NAS when Inband Information is sent in the ACM message.
Resolution: The HSI software is modified to map the inband indicator in the ISUP CPG message to a PI-8 IE. If required, the HSI will send an H.225 Progress message to initiate the H.245 negotiation.
CSCeb72113
4.1
3
The HSI did not send an INFO message to CallManager if the originator initiated a blind call transfer.
Symptoms: The HSI did not send an INFO message to CallManager if the originator initiated a blind call transfer.
Resolution: The HSI software is modified to support an information signal in the state H323StOutgoing.
Cisco HSI 2.21 Patch 5
This section includes information pertaining to Cisco HSI 2.21 Patch 5:
•
Caveats Resolved by Patch 5
The following anomalies identified in the operation of the Cisco HSI are resolved by Patch 5.
CSCuk44964
2.21
3
HSI sends incorrect Cause value when channel is disconnected.
Symptoms: The HSI detects the disconnection of the media channel during its handling of the H.225 RLC message and thus attempts to release the call with a default cause value instead of the Release Cause value received in the H.225 RLC message.
Resolution: The HSI now checks to see if it has received a H.225 RLC message when it is processing the Channel Disconnect from the stack. It will use the release cause from the RLC if it is available; otherwise, it will use a default release cause to clear the call.
CSCuk45202
2.21
3
The HSI core dumps if a Notification is received during the release sequence.
Symptoms: If the HSI receives an EISUP NOTIFICATION message during a release sequence, the HSI can core occasionally.
Resolution: The HSI has been modified so that it will not core when it receives an EISUP NOTIFICATION message during a release sequence.
CSCuk44554
2.21
3
A race condition on release leads to hung calls on the HSI.
Symptoms: A race condition in the release sequence causes the HSI to hang the call. The call remains on the active call list even though the calling/called parties have released.
This is an intermittent issue that occurs when the HSI receives a release from both legs of the call.
Resolution: HSI has been modified so that the race condition does not occur.
CSCuk44110
2.21
2
HSI fails to transit DTMF digits for H.323 tunnelled calls.
Symptoms: The HSI fails to send a DTMF digit for PSTN->H.323 tunnelled calls.
Resolution: The HSI now sends a DTMF digit for PSTN to HSI tunnelled calls.
CSCuk32615
2.21
3
The MML command rtrv-ne-health displays an incorrect number of setup calls.
Symptoms: The MML command rtrv-ne-health returns incorrect information about the number of setup calls.
Resolution: The MML command rtrv-ne-health displays the number of setup calls correctly.
Symptoms: A release race condition caused the HSI to crash intermittently.
Resolution: The state machine has been modified to handle the release race condition that caused the HSI to crash intermittently.
Cisco HSI 2.21 Patch 4
This section includes information pertaining to Cisco HSI 2.21 Patch 4:
•
Caveats Resolved by Patch 4
The following anomalies identified in the operation of the Cisco HSI are resolved by Patch 4.
CSCuk43665
2.21
3
Incorrect coding of the Progress Indicator IE.
Symptoms: The HSI currently codes the Progress Indicator informational element to 1F. This does not conform to the Q.931 specification, which states that the coding for this IE should be 1E.
Resolution: The H.323 stack is updated to code the Progress Indicator IE as 1E.
CSCea84049
2.21
2
HSI originated calls fail over an inter-PGW EISUP Link.
Symptoms: The Call Progress message generated by the ISUP transparency feature causes HSI originated calls to fail.
Resolution: The Call Progress message is handled correctly.
CSCuk43428
2.21
3
HSI should send the Progress message for ACM with no indication + inband indicator.
Symptoms: The HSI fails to send the H.225 Progress message when it receives an ACM message with no indication + inband indicator (see H.246 Annex C).
Resolution: The HSI is updated to support sending the H.225 Progress message when it receives an ACM with no indication + inband indicator.
CSCea71610
2.21
3
A Cause Code on the H.323 side was incorrectly translated to an EISUP cause code.
Symptoms: The HSI incorrectly maps the calledPartyNotRegistered reject reason in the AdmissionReject message to Normal Call Clearing (Q.850 - 16).
Resolution: The HSI now correctly maps the calledPartyNotRegistered reject reason to the appropriate Q.850 Release Cause value.
CSCea71703
2.21
3
HSI translates H.225 rel 16 (normal) to EISUP 42 (congestion).
Symptoms: For H.323 fast start calls, the HSI sends the incorrect release cause for calls in which the H.323 calling party releases the call prior to answer.
Resolution: The HSI sends the correct release cause for this call scenario.
Cisco HSI 2.21 Patch 3
This section includes information pertaining to Cisco HSI 2.21 Patch 3:
•
Caveats Resolved in Patch 3
The following anomalies identified in the operation of the Cisco HSI are resolved by Patch 3.
CSCuk41577
2.21
3
Change HSI property permissions to Dynamic.
Symptoms: The user is unable to provision the property A_CC_oIsdnPref due to permission issues.
Resolution: Change the property permission to allow the user to provision this property.
CSCea52746
2.21
3
HSI does not support call manager calls hairpinned pstn-pstn.
Symptoms: There is no speech path for PSTN to Call Manager calls with the Call Forward Service activated on the CM phone (forwarded to a PSTN destination).
Resolution: The HSI uses the H.245 address in the H.225 Progress message to open the H.245 connection to the CallManager.
CSCea52755
2.21
3
Unconditionally forwarded Cisco CallManager calls fail through HSI.
Symptoms: Unconditionally forwarded calls fail when using Cisco CallManager with the HSI. This occurs for calls which ingress from PSTN and are forwarded back out to the PSTN. HSI version 2.21 patch 2 introduced this problem.
Resolution: Modified the stack to open the H.245 connection when it receives the H.245 address in the H.225 Alerting message.
CSCuk42694
2.21
3
The HSI sends the incorrect release cause.
Symptoms: The HSI sends the incorrect release cause, Switch Equipment Congestion, for calls where the H.323 calling party releases the call prior to answer.
Resolution: The HSI sends the correct cause, Normal Call Clearing, for this call scenario.
CSCuk42842
2.21
2
There is a resource allocation leak during T.38 negotiation; this causes instabilities within the system after long periods.
Symptoms: The HSI has a resource leak in the T.38 negotiation functionality. This leads to instability in the product after an extended performance run.
Resolution: The resource leak is resolved.
Cisco HSI 2.21 Patch 2
This section includes the following information pertaining to Cisco HSI 2.21 Patch 2:
•
Caveats Resolved in Patch 2
The following anomalies identified in the operation of the Cisco HSI are resolved by Patch 2.
CSCdz46087
2.21
3
The prov-exp command generates a file owned by root, not the user.
Symptoms: When the configuration for an HSI element is exported using the MML command prov-exp:<dirname>, the directory that is created, and the config.mml file, are set with permissions that prevent the user mgcusr from reading the config.mml file.
Resolution: The code is modified to change the permissions on the exported directory.
CSCdz63128
2.21
3
HSI sends hostname in DISPLAY IE. This is displayed on CM IP phones.
Symptoms: When calls are made from Call Manager to the HSI, the HSI returns a DISPLAY IE in the connect message. This IE contains the hostname of the HSI and is displayed on the IP phone.
Resolution: The HSI does not send the DISPLAY IE in the H.225 Connect message.
CSCdz63215
2.21
3
HSI should open speech path on alerting to pass ring tone.
Symptoms: For H.323 to PSTN calls, the HSI does not send its H.245 address to the H.323 endpoint until the H.225 Connect message. This delay to the H.245 negotiation stops the opening of the media stream for Slow Start calls until after connect; therefore, no PSTN in-band tones/announcements are made available to the H.323 endpoint.
Resolution: The HSI now sends it's H.245 address in the H.225 Call Proceeding message. This allows the H.323 endpoint to initiate the H.245 negotiation at an earlier stage in the call, which makes the PSTN in-band tones/announcements available to the H.323 endpoint.
CSCea06011
2.21
3
Cause code on H323 side is incorrectly translated to an EISUP message code.
Symptoms: The HSI fails to transit the H.323 release cause to the PSTN according to the H.246 Annex C specification
Resolution: The HSI now correctly maps the Q.931 Release Cause and the H.225 Release Reason according to the H.246 Annex C specification.
CSCuk40377
2.21
3
Information message featurette fails occasionally.
Symptoms: The HSI does not correctly process the Information message in certain call scenarios.
Resolution: The HSI now supports the Information message in the failing call scenarios.
CSCuk40427
2.21
3
HSI fails to re-register after loss of Gatekeepers.
Symptoms: The HSI sends a GRQ message (multi-cast message) when it receives a RRJ message with the reason DiscoveryRequired. Multi-casting is restricted in many customer networks; therefore, the GRQ message is not received by the relevant Gatekeepers. The HSI fails to get a registration confirmation and rejects all new PSTN to H.323 calls.
Resolution: The HSI does not send a GRQ message when it receives a RRJ message with the reason DiscoveryRequired. It continues to send RRQ messages. This functionality is enabled by default. The user may disable this functionality (revert to GRQ messaging) by using the following MML command:
prov-add:name=sys_config_static,grqmsgenabled="True"
CSCuk40666
2.21
3
ECS should not prompt TCS exchange from HSI.
Symptoms: The HSI no longer initiates a TCS after responding to an ECS.
Resolution: The HSI no longer initiates a TCS after responding to an ECS.
CSCuk41261
2.21
3
ST. Transfer two PSTN calls from CM with HSI fails.
Symptoms: Neither party sends the H.245 Open Logical Channel (OLC) message after the ECS exchange.
Resolution: The HSI now sends a OLC message to the CCM after the ECS exchange.
Cisco HSI 2.21 Patch 1
This section includes the following information pertaining to Cisco HSI 2.21 Patch 1:
•
•
•
New Features in Release 2.21 Patch 1
The following features are added to the HSI by Patch 1:
•
•
HSI INFORMATION Message Support
Cisco CallManager uses the H.225 INFORMATION message during transfer to indicate that ringback tone is on or off. The Cisco HSI now supports this message to correctly interoperate with Cisco CallManager.
Support for the H.225 INFORMATION message is enabled by default. A craftsperson can disable H.255 INFORMATION message support through a new property called Information MsgDisabled by issuing the following MML command:
prov-add:name=sys_config_static,informationmsgdisabled = "True"HSI Support for Tech Prefixes
The Cisco HSI now maps the '*' (asterisk, or star) and '#' (number sign, or hash) H.225 prefixes to the PGW for H.323 to PSTN calls as follows:
•
•
•
•
The craftsperson can change these values by issuing the following MML command:
prov-ed:name=ccpackage,hash='C'Cisco HSI now maps the EISUP 'B' to '*' and 'C' to '#' (Called Party Number) for PSTN to H.323 calls.
Caveats Resolved in Patch 1
The following anomalies identified in the operation of the Cisco HSI are resolved by Patch 1.
CSCdy87465
2.20
2
IE should be sent in Alert for all calls from H323 through HSI.
Symptoms: There is no backward speech path currently if the PSTN network does not notify the HSI that inband is available via the OBCI parameter (The HSI maps the inband indicator in this parameter to the PI=8 information element in H.225).
Resolution: The craftperson can now inject the PI=8 IE into the H.225 Alerting message by a new provisioning property—InjectPI8. The new MML command to provision the information element is:
prov-add:name=sys_config_static,injectpi8 = "Enabled"
CSCuk31395
2.20
2
Goldwing fails to unregister properly when it is stopped.
Symptoms: When stopping the Goldwing application, Goldwing fails to send an URQ message to the gatekeeper, and fails to respond to the URQ message sent by the gatekeeper.
Resolution: The HSI now sends an URQ (UnRegistration Request) RAS message to the gatekeeper as part of its shutdown procedure.
Symptoms: Occasionally ECS fails with CallManager. This is due to CallManager messaging being asynchronous.
Resolution: The HSI has resolved the race condition that may occur due to asynchronous messaging from the Cisco CallManager.
CSCdy64021
2.20
3
BTNUP-Bearcap of 3.1Khz and SPEECH calls both being mapped to SHP=0.
Symptoms: Call attempts from H323/HSI to SS7 BTNUP, with bearer capability of 3.1 kHz or Unrestricted Digital Data, are being mapped to speech (SHP = 0) across the C7 links from the SLTs.
Resolution: The HSI now maps the H.225 Bearer Capability IE into the EISUP TMR parameter (and vice-versa) using the H.246 Annex C specification.
Symptoms: Calls to or from Netmeeting fail because it cannot understand the T38 information that is contained within the TCS message, which the HSI sends to Netmeeting.
Resolution: The T.38 feature is disabled automatically for Netmeeting calls as this endpoint does not support this feature. The craftsperson can disable the T.38 feature on the HSI by using the new property T38Disabled. The MML command to disable the T.38 feature is:
prov-add:name=sys_config_static,t38disabled = "True"
CSCdz14525
2.21
3
Screen calls based on bearer cap in H.225 setup message.
Symptoms: Call setup from the H.323 network through HSI to the PGW fails with unrestricted digital data. Failure occurs at codec analysis.
Resolution: The HSI now maps the H.225 Bearer Capability IE into the EISUP TMR parameter (and vice-versa) using the H.246 Annex C specification.
New Features In Release 2.21
The following new features are introduced in release 2.21 of the Cisco HSI:
•
•
•
•
Asymmetric Codec Treatment
The Asymmetric Codec Treatment feature averts the potential for inconsistencies in codec selection, which can result when endpoints attempt to use different codecs for the transmission path.
See the Cisco H.323 Signaling Interface User Guide for release 2.21 for information on configuring the Asymmetric Codec Treatment feature on the HSI.
Empty Capability Set
Empty Capability Set support enables the HSI to close opened logical channels, without releasing the call. Subsequently, a new logical channel can be opened, potentially to a different endpoint, or to use a different codec.
The Empty Capability Set feature requires no provisioning on the HSI.
H.323 Hairpin
The H.323 Hairpin feature can be used to connect a call between two H.323 endpoints without using resources on the media gateway. For example, the PGW can respond to the dialled number in an incoming H.323 call by routing the call to another HSI (perhaps the same HSI) rather than routing the call to the PSTN. In this case, the originating and terminating HSIs will establish the call normally but will pass the H.245 address of the H.323 endpoints. This enables the two endpoints to use H.245 to negotiate media channels with each other directly, independent of the HSI.
T.38 Fax
The T.38 Fax feature enables the HSI to alter a call, initially established for voice, to support a fax transmission.
When a fax call is initiated, a voice call is established. When the terminating gateway detects the fax tone generated by the terminating fax machine, the gateway initiates a T.38 mode request using H.245 procedures from the terminating gateway. If the opposite end of the call acknowledges the T.38 mode request, the initial audio channel is closed and a T.38 Fax Relay channel is opened.
See the Cisco H.323 Signaling Interface User Guide for release 2.21 for information on configuring T.38 Fax Negotiation on the HSI.
Caveats
This section lists the caveats for Cisco H.323 Signaling Interface, Release 2.21.
Resolved Caveats
This section lists caveats identified in the operation of HSI 2.20 that are resolved by HSI 2.21.
CSCdy63982
2.20
3
HSI Uses GUID instead of Conf-ID when passing Gbl Call ID to PGW/CDR.
Symptoms: Problem is that the Global Call ID's in PGW CDR and Radius billing records do not match. This is considered to be due to HSI using the CallIdentifier (GUID) value instead of ConferenceID in RAS/call signaling messages for PGW CDR Global Call ID value.
The Global Call ID values in the PGW CDR's and Radius Billing Records are very similar, except that they differ slightly in the 10th octet.
Resolution: A new property is created on the HSI to specify the precedence of extracting the Global Call ID from the Conf ID or the GUID.
Name: UseConfID
Package: SYS_CONFIG_STATIC
Range: String
Example:
prov-ed:name=sys_config_static,useconfid="Enabled"The property will be set to "Enabled" in the default config - precedence to the Conf ID field.
To set the precedence to the GUID field, the craftperson can either delete the property from the config or set it to "".
Example:
prov-ed:name=sys_config_static,useconfid=""
Symptoms: Incoming H.323 Calls have the Nature of Address field in the outgoing called address field defaulted and NOT mapped from the incoming H225 called party number type (as required by Q699 and H.246 annex C).
Resolution: The NOA (Type of Number in H.225) value for the Called, Calling and Additional Calling party number are now transmitted through the HSI application.
CSCuk36602
2.20
1
All IOS 12.2(11)T H.323 GW calls via HSI fail.
Symptoms: All calls will fail between HSI and an IOS Gateway running release 12.2(11)T because this IOS release conforms to H.323 v4 which states that if a Facility is specified, it should not have an Empty reason but should use reason transportedInformation. Previous versions of IOS would send a Facility reason of Empty. The HSI does accept this method of operation.
Resolution: The HSI now handles the changes to the FACILITY message in the 12.2(11)T IOS release. The HSI ignores the facility UUIE in the H.225 FACILITY message.
CSCuk35318
2.20p2
3
HSI does not release call with correct cause when not Registered
Symptoms: The HSI is not able to provision the release cause for calls that fail because the HSI is not being registered with a Gatekeeper.
Resolution: The HSI will release all calls with the provisioned Q.850 release cause when it failed to register with a Gatekeeper after 3 attempts.
Property: RegFailureReleaseCause
Package: SYS_CONFIG_DYNAMIC
Range: 1 - 127
Description: This property specifies the Q.850 release cause the HSI will use for the scenario where the HSI has failed to register to a Gatekeeper (after 3 failed attempts).
Example:
prov-ed:name=sys_config_dynamic, regfailurereleasecause=44Open Caveats
This section lists unresolved caveats identified in the operation of HSI 2.21.
CSCuk31567
2.20
3
Bearer Capability should be transparent on HSI.
Symptoms: The HSI does not map the Bearer Capability IE in the H.225 SETUP message to the ISUP Transmission Medium Requirement parameter (and vice-versa) as specified in the H.246 Annex C specification.
Workaround: For now, all calls sent to H323 are with Speech Bearer Capability.
CSCuk31395
2.20
2
Goldwing fails to unregister properly when being stopped.
Symptoms: When stopping the Goldwing application, Goldwing fails to send an URQ message to the Gatekeeper, and fails to respond to the URQ message sent by the Gatekeeper.
Workaround: None.
CSCdx05888
2.20
3
AlternateGatekeeper GKID not set correctly result in RRJ.
Symptoms: If primary gatekeeper is down and HSI reboots, it may fail to register to the alternateGatekeeper configured because it uses an empty or incorrect GKID.
Workaround: None
CSCuk33095
2.20p1
3
When the overload level 1 is reached, an internal alarm is not raised.
Symptoms: When the Overload level 1 is reached, an internal alarm is not raised (rtrv-alms) but an SNMP trap is generated.
Workaround: None
CSCuk35555
2.20p3
3
Incoming H323 calls should have early H245 information.
Symptoms: For incoming H323 calls, we should send early H245 information at the first available opportunity (for example, a call proceeding message).
Currently we only send the H245 address in the Connect message (that is, not early H245 information).
Workaround: None
Known Issues and Operational Recommendations
There are no known issues or operational recommendations at this time.
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:
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:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
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-9883We 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
•
•
•
•
•
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
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:
•
•
•
•
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:
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.
Copyright © 2004 Cisco Systems, Inc. All rights reserved.
Printed in the USA on recycled paper containing 10% postconsumer waste.
Posted: Thu Oct 14 12:17:32 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
