Table Of Contents
Release Notes for the Cisco VG224 Analog Gateway for Cisco IOS Release 12.4(4)XC
Determining Your Software Release
Upgrading to a New Software Release
Determining Which Software Images (Feature Sets) Support a Specific Feature
Determining Which Features Are Supported in a Specific Software Image (Feature Set)
New Hardware and Software Features in Release 12.4(4)XC
Resolved Caveats -Cisco IOS Release 12.4(4)XC7
Resolved Caveats -Cisco IOS Release 12.4(4)XC6
Resolved Caveats - Cisco IOS Release 12.4(4)XC5
Resolved Caveats - Cisco IOS Release 12.4(4)XC4
Resolved Caveats—Cisco IOS Release 12.4(4)XC3
Cisco IOS Software Documentation Set
Release 12.4 Documentation Set
Obtaining Documentation, Obtaining Support, and Security Guidelines
Open Source License Acknowledgements
Release Notes for the Cisco VG224 Analog Gateway for Cisco IOS Release 12.4(4)XC
June 9, 2008Cisco IOS Release 12.4(4)XC7OL-12743-02 Seventh ReleaseLast Revised: September 24, 2008These release notes for the Cisco VG224 analog gateway describe the product-related enhancements provided in Cisco IOS Release 12.4(4)XC. These release notes are updated as needed.
For a list of the software caveats that apply to Cisco IOS Release 12.4(4)XC, see the "Caveats" section. See also Caveats for Cisco IOS Release 12.4T, which is updated for every maintenance release and is located on Cisco.com. Use these release notes with the Cross-Platform Release Notes for Cisco IOS Release 12.4T located on Cisco.com.
We recommend that you view the field notices for this release to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/warp/customer/tech_tips/index/fn.html. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/warp/public/tech_tips/index/fn.html.
Contents
These release notes describe the following topics:
•Obtaining Documentation, Obtaining Support, and Security Guidelines
•Open Source License Acknowledgements
Inheritance Information
Cisco IOS Release 12.4(4)XC, an early deployment release, is based on Cisco IOS Release 12.4(4)T, which in turn is based on Cisco IOS Release 12.4. Cisco IOS Release 12.4(4)T is the first early deployment maintenance release of Cisco IOS Release 12.4 T and is based on the mainline Cisco IOS Release 12.4. See Table 1 for more information.
All features in Cisco IOS Release 12.4(4)T are in Cisco IOS Release 12.4(4)XC.
Table 1 References for the Cross-Platform Release Notes for Cisco IOS Release 12.4 T
Topic Location•Determining the Software Version
•Upgrading to a New Software Release
To view information about the topics in the left column, click Cross-Platform System Requirements at: http://http://www.cisco.com/en/US/customer/products/ps6350/prod_release_note09186a0080575f77.html
•New and Changed Information (Feature Descriptions)
•MIBs
•Important Notes
To view information about the topics in the left column for Cisco IOS Release 12.4 T, go to:
http://http://www.cisco.com/en/US/customer/products/ps6350/prod_release_note09186a0080575f82.html
Scroll down and click New Software Features in Cisco IOS Release 12.4(4)T, or MIBs, or Important Notes.
•Related Documentation
•Obtaining Documentation
•Obtaining Technical Assistance
To view information about the topics in the left column, go to:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124relnt/xprn124/124docs.htm
Introduction
Cisco IOS Release 12.4(4)XC supports the Cisco VG224 analog gateway.
The Cisco VG224 series is a family of analog gateways. The Cisco VG224 has 24-port FXS through an RJ-21 connector and two 10/100BaseT interfaces.
For information on new features and Cisco IOS commands supported by Cisco IOS Release 12.4(4)XC, see the "New and Changed Information" section.
Early Deployment Releases
These release notes describe Cisco IOS Release 12.4(4)XC for the Cisco VG224 analog gateway. Cisco IOS Release 12.4(4)XC is an early deployment (ED) release based on Release 12.4(4)T, which in turn is based on Cisco IOS Release 12.4. Early deployment releases contain fixes to software caveats and support for new Cisco hardware and software features. Feature support is cumulative from release to release, unless otherwise noted.
Table 2 lists new features supported by the Cisco VG224 analog gateway in Cisco IOS Release 12.4(4)XC. See the "Inheritance Information" section for a list of the documentation specific to the Cisco VG224 analog gateway.
Table 2 Early Deployment Release New Features for the Cisco VG224 Analog Gateway
ED Release Additional Hardware Hardware
Availability12.4(4)XC
None
Cisco VG224
Yes
1 Only major features are listed.
2 MIB = Management Information Base
System Requirements
This section describes the system requirements for Cisco IOS Release 12.4(4)XC and includes the following sections:
•Determining Your Software Release
•Upgrading to a New Software Release
Memory Requirements
Table 3 lists the memory requirements of the Cisco IOS feature sets for the Cisco VG224 analog gateway for Cisco IOS Release 12.4(4)XC.
The Cisco VG224 analog gateway is available with a 32-MB Flash memory card.
Supported Hardware
Cisco IOS Release 12.4(4)XC supports the following platforms:
•Cisco VG224 analog gateway
For detailed descriptions of the new hardware features, see the "New and Changed Information" section.
For information about supported hardware for this platform and release, see the Hardware/Software Compatibility Matrix in the Cisco Software Advisor:
http://www.cisco.com/cgi-bin/front.x/Support/HWSWmatrix/hwswmatrix.cgi
Determining Your Software Release
To determine the version of Cisco IOS software running on the Cisco VG224 analog gateway, log in to the gateway and enter the show version EXEC command:
Router> show versionCisco IOS Software, vg224 Software (vg224-I6K9S-M), Version12.4(4)XC, RELEASE SOFTWARE (fc1)TAC Support: http://www.cisco.com/tacCopyright (c) 1986-2003 by Cisco Systems, Inc.Upgrading to a New Software Release
For general information about upgrading to a new software release, see the Cisco IOS Upgrade Ordering Instructions located at: http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/957_pp.htm.
Feature Support
Cisco IOS software is packaged in feature sets that consist of software images that support specific platforms. The feature sets available for a specific platform depend on which Cisco IOS software images are included in a release. Each feature set contains a specific set of Cisco IOS features.
To improve the usability of the release notes documentation, Cisco IOS Release 12.4(4)XC release notes no longer contains the feature set tables. The feature-to-image mapping that was provided by the feature set tables is available through Cisco Feature Navigator.
Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or by feature set (software image). Under the release section, you can compare Cisco IOS software releases side by side to display both the features unique to each software release and the features that the releases have in common.
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp
For frequently asked questions about Cisco Feature Navigator, see the FAQs at the following URL:
http://www.cisco.com/support/FeatureNav/FNFAQ.html
Caution Cisco IOS images with strong encryption (including, but not limited to 168-bit (3DES) data encryption feature sets) are subject to U.S. government export controls and have limited distribution. Strong encryption images to be installed outside the United States will probably require an export license. Customer orders may be denied or subject to delay because of U.S. government regulations. When applicable, the purchaser/user must obtain local import and use authorizations for all encryption strengths. Contact your sales representative or distributor for more information, or send an e-mail to export@cisco.com.
Determining Which Software Images (Feature Sets) Support a Specific Feature
To determine which software images (feature sets) in Cisco IOS Release 12.4(4)XC support a specific feature, go to the Cisco Feature Navigator home page, enter your Cisco.com login, and perform the following steps:
Step 1 From the Cisco Feature Navigator home page, click Feature.
Step 2 To find a feature, choose either Search by full or partial feature name or Browse features in alphabetical order. Either a list of features that match the search criteria or a list of features that begin with the number or letter selected from the ordered list appear.
Step 3 Select a feature from the left text box and click Add. Repeat this step to add additional features. You can choose a maximum of 20 features for a single search.
Note To learn more about a feature in the list, click Description.
Step 4 Click Continue.
Step 5 From the Major Release drop-down menu, choose 12.4T.
Step 6 From the Release dropdown menu, choose the appropriate maintenance release.
Step 7 From the Platform Family drop-down menu, choose the appropriate hardware platform. All software images (feature sets) that support the features that you selected appear.
Determining Which Features Are Supported in a Specific Software Image (Feature Set)
To determine which features are supported in a specific software image (feature set) in Cisco IOS Release 12.4(4)XC, go to the Cisco Feature Navigator home page, enter your Cisco.com login, and perform the following steps:
Step 1 From the Cisco Feature Navigator home page, click Compare/Release.
Step 2 In the "Find the features in a specific Cisco IOS release, using one of the following methods:" box, choose 12.4 T from the Cisco IOS Major Release drop-down menu.
Step 3 Click Continue.
Step 4 From the Release drop-down menu, choose the appropriate maintenance release.
Step 5 From the Platform Family drop-down menu, choose the appropriate hardware platform.
Step 6 From the Feature Set drop-down menu, choose the appropriate feature set. All features that are supported by the feature set (software image) that you selected appear.
New and Changed Information
The following sections list the new hardware products and software features supported by the Cisco VG224 analog gateway in Cisco IOS Release 12.4(4)XC.
New Hardware and Software Features in Release 12.4(4)XC
No new hardware products or software features are supported in Cisco IOS Release 12.4(4)XC.
Limitations and Restrictions
See each feature for individual limitations and restrictions.
Current MIBs
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
Supported MIBs
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Field Notices and Bulletins
•Field Notices—We recommend that you view the field notices for this release to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/warp/customer/770/index.shtml. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/warp/public/770/index.shtml.
•Product Bulletins—If you have an account on Cisco.com, you can find product bulletins at http://www.cisco.com/warp/customer/cc/general/bulletin/index.shtml. If you do not have a Cisco.com login account, you can find product bulletins at http://www.cisco.com/warp/public/cc/general/bulletin/iosw/index.shtml.
•What's New for IOS—What's New for IOS lists recently posted Cisco IOS software releases and software releases that have been removed from Cisco.com. If you have an account on Cisco.com, you can access What's New for IOS at http://www.cisco.com/kobayashi/sw-center/sw-ios.shtml or by logging in and selecting Software Center: Cisco IOS Software: What's New for IOS.
Caveats
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only selected severity 3 caveats are included in the caveats document.
This section contains open and resolved caveats for the current Cisco IOS maintenance release.
All caveats in Cisco IOS Release 12.4 and Cisco IOS Release 12.4 T are also in Cisco IOS Release 12.4(4)XC.
For information on caveats in Cisco IOS Release 12.4 and Cisco IOS Release 12.4 T, see Caveats for Cisco IOS Release 12.4 T. These documents lists severity 1 and severity 2 caveats and only selected severity 3 caveats, and are located on Cisco.com.
Caveat numbers and brief descriptions for Release 12.4(4)XC are listed in this section.
Note If you have an account on Cisco.com, you can use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in to Cisco.com and go to: http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl
This section contains the following caveat information:
•Resolved Caveats -Cisco IOS Release 12.4(4)XC7
•Resolved Caveats -Cisco IOS Release 12.4(4)XC6
•Resolved Caveats - Cisco IOS Release 12.4(4)XC5
•Resolved Caveats - Cisco IOS Release 12.4(4)XC4
•Resolved Caveats—Cisco IOS Release 12.4(4)XC3
Resolved Caveats -Cisco IOS Release 12.4(4)XC7
CSCec12299Devices running Cisco IOS versions 12.0S, 12.2, 12.3 or 12.4 and configured for Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) or VPN Routing and Forwarding Lite (VRF Lite) and using Border Gateway Protocol (BGP) between Customer Edge (CE) and Provider Edge (PE) devices may permit information to propagate between VPNs.
Workarounds are available to help mitigate this vulnerability.
This issue is triggered by a logic error when processing extended communities on the PE device.
This issue cannot be deterministically exploited by an attacker.
Cisco has released free software updates that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-vpn.shtml.
CSCsd81407Multiple voice-related vulnerabilities are identified in Cisco IOS software, one of which is also shared with Cisco Unified Communications Manager. These vulnerabilities pertain to the following protocols or features:
–Session Initiation Protocol (SIP)
–Media Gateway Control Protocol (MGCP)
–Signaling protocols H.323, H.254
–Real-time Transport Protocol (RTP)
–Facsimile reception
Cisco has made free software available to address these vulnerabilities for affected customers. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities mentioned in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-voice.shtml
CSCsi80749Multiple voice-related vulnerabilities are identified in Cisco IOS software, one of which is also shared with Cisco Unified Communications Manager. These vulnerabilities pertain to the following protocols or features:
–Session Initiation Protocol (SIP)
–Media Gateway Control Protocol (MGCP)
–Signaling protocols H.323, H.254
–Real-time Transport Protocol (RTP)
–Facsimile reception
Cisco has made free software available to address these vulnerabilities for affected customers. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities mentioned in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-voice.shtml
CSCsg70474Multiple voice-related vulnerabilities are identified in Cisco IOS software, one of which is also shared with Cisco Unified Communications Manager. These vulnerabilities pertain to the following protocols or features:
–Session Initiation Protocol (SIP)
–Media Gateway Control Protocol (MGCP)
–Signaling protocols H.323, H.254
–Real-time Transport Protocol (RTP)
–Facsimile reception
Cisco has made free software available to address these vulnerabilities for affected customers. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities mentioned in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-voice.shtml
CSCsi60004Multiple voice-related vulnerabilities are identified in Cisco IOS software, one of which is also shared with Cisco Unified Communications Manager. These vulnerabilities pertain to the following protocols or features:
–Session Initiation Protocol (SIP)
–Media Gateway Control Protocol (MGCP)
–Signaling protocols H.323, H.254
–Real-time Transport Protocol (RTP)
–Facsimile reception
Cisco has made free software available to address these vulnerabilities for affected customers. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities mentioned in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-voice.shtml
CSCse56501A device running Cisco IOS software that has Internet Protocol version 6 (IPv6) enabled may be subject to a denial of service (DoS) attack. For the device to be affected by this vulnerability the device also has to have certain Internet Protocol version 4 (IPv4) User Datagram Protocol (UDP) services enabled. To exploit this vulnerability an offending IPv6 packet must be targeted to the device. Packets that are routed throughout the router can not trigger this vulnerability. Successful exploitation will prevent the interface from receiving any additional traffic. The only exception is Resource Reservation Protocol (RSVP) service, which if exploited, will cause the device to crash. Only the interface on which the vulnerability was exploited will be affected.
Cisco is providing fixed software to address this issue. There are workarounds available to mitigate the effects of the vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080326-IPv4IPv6.shtml.
CSCsg96319 reverse ssh eliminated telnet authentication on VTYSymptom When a reverse SSH session is established with valid authentication credentials, anyone can obtain unprivileged Telnet access to a system without being authenticated. This situation affects only reverse SSH sessions when a connection is made with the
ssh -l userid :number ip-address command.
Conditions This symptom is observed only when the Reverse SSH Enhancement is configured. This enhancement is documented at the following URL:
http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a00804831b6.html
Workaround Configure reverse SSH by entering the ip ssh port portnum rotary group command. This configuration is explained at the following URL:
http://www.cisco.com/en/US/tech/tk583/tk617/technologies_q_and_a_item09186a0080267e0f.shtml#newq1
CSCsg40567 Memory leak found with malformed tls/ssl packets in http core processSymptom Malformed SSL packets may cause a router to leak multiple memory blocks.
Conditions This symptom is observed on a Cisco router that has the ip http secure server command enabled.
Workaround Disable the ip http secure server command.
CSCsg03449 Etherswitch module VLAN Trunking Protocol VulnerabilitiesSymptom
•VTP Version field DoS
•Integer Wrap in VTP revision
•Buffer Overflow in VTP VLAN name
Conditions The packets must be received on a trunk enabled port.
Further Information: On the 13th September 2006, Phenoelit Group posted an advisory containing three vulnerabilities:
–VTP Version field DoS
–Integer Wrap in VTP revision
–Buffer Overflow in VTP VLAN name
These vulnerabilities are addressed by Cisco IDs:
•CSCsd52629/CSCsd34759 -- VTP version field DoS
•CSCse40078/CSCse47765 -- Integer Wrap in VTP revision
•CSCsd34855/CSCei54611 -- Buffer Overflow in VTP VLAN name
•CSCsg03449 -- Etherswitch module VLAN Trunking Protocol Vulnerabilities. Cisco's statement and further information are available on the Cisco public website at: http://www.cisco.com/warp/public/707/cisco-sr-20060913-vtp.shtml
CSCsj44099 Router crashes if DSPFARM profile description is 128 characters long.Symptom A cisco c3800 router can experience a memory corruption resulting in a crash if the description field under the "dspfarm profile" configuration matches the maximum of 128 characters.
Conditions During configuration of the dspfarm profile through the CLI, a description that is 128 characters will cause a memory copy problem. If the user tries to display the results of the configuration using "show dspfarm profile", the router will crash trying to display the output.
Workaround To prevent this problem configure the dspfarm profile description with 127 characters or less.
CSCse05736 A router running RCP can be reloaded with a specific packetSymptom A router that is running RCP can be reloaded by a specific packet.
Conditions This symptom is seen under the following conditions
–The router must have RCP enabled.
–The packet must come from the source address of the designated system configured to send RCP packets to the router.
–The packet must have a specific data content.
Workaround Put access lists on the edge of your network blocking RCP packets to prevent spoofed RSH packets. Use another protocol such as SCP. Use VTY ACLs.
CSCec12299 Corruption of ext communities when receiving over ipv4 EBGP sessionSymptom EIGRP-specific Extended Community 0x8800 is corrupted and shown as 0x0:0:0.
Conditions This symptom is observed when EIGRP-specific Extended Community 0x8800 is received via an IPv4 EBGP session on a CE router. This occurs typically in the following inter-autonomous system scenario:
ASBR/PE-1 <----> VRF-to-VRF <----> ASBR/PE-2
Workaround Use a configuration such as the following to remove extended communities from the CE router:
router bgp 1address-family ipv4 vrf oneneighbor 1.0.0.1 remote-as 100neighbor 1.0.0.1 activateneighbor 1.0.0.1 route-map FILTER inexit-address-family!ip extcommunity-list 100 permit _RT.*_!!route-map FILTER permit 10set extcomm-list 100 delete!CSCse24889 Malformed SSH version 2 packets may cause processor memory depletionSymptom Malformed SSH version 2 packets may cause a memory leak, causing the platform to operate under a degraded condition. Under rare circumstances, the platform may reload to recover itself.
Conditions This symptom is observed on a Cisco platform that is configured for SSH version 2 after it has received malformed SSHv2 packets.
Workaround As an interim solution until the affected platform can be upgraded to a Cisco IOS software image that contains the fix for caveat CSCse24889, configure SSH version 1 from the global configuration mode, as in the following example:
config tip ssh version 1endAlternate Workaround: Permit only known trusted hosts and/or networks to connect to the router by creating a vty access list, as in the following example:
Workaround
10.1.1.0/24 is a trusted network thatis permitted access to the router, allother access is deniedaccess-list 99 permit 10.1.1.0 0.0.0.255access-list 99 deny anyline vty 0 4access-class 99 inendFurther Problem Description: For information about configuring vty access lists, see the Controlling Access to a Virtual Terminal Line document: http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_chapter09186a0080716ec2.html. For information about SSH, see the Configuring Secure Shell on Routers and Switches Running Cisco IOS document: http://www.cisco.com/warp/public/707/ssh.shtml
CSCsc40493 Lengthy PADR frame could crash PPPoE BRASSymptom A PPPoE aggregation server (BRAS) may reset when receiving a malformed PPPoE message.
Conditions A malformed PPPoE message must be received on an aggregation interface.
Workaround There is no workaround.
CSCsh53643 mbar/isync compiler automationCSCsh77241 Reverting the compiler back to c2.95.3-p11bCSCsi01470A vulnerability in the Cisco implementation of Multicast Virtual Private Network (MVPN) is subject to exploitation that can allow a malicious user to create extra multicast states on the core routers or receive multicast traffic from other Multiprotocol Label Switching (MPLS) based Virtual Private Networks (VPN) by sending specially crafted messages.
Cisco has released free software updates that address this vulnerability. Workarounds that mitigate this vulnerability are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080326-mvpn.shtml.
Resolved Caveats -Cisco IOS Release 12.4(4)XC6
CSCsf30058Multiple voice-related vulnerabilities are identified in Cisco IOS software, one of which is also shared with Cisco Unified Communications Manager. These vulnerabilities pertain to the following protocols or features:
–Session Initiation Protocol (SIP)
–Media Gateway Control Protocol (MGCP)
–Signaling protocols H.323, H.254
–Real-time Transport Protocol (RTP)
–Facsimile reception
Cisco has made free software available to address these vulnerabilities for affected customers. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities mentioned in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-voice.shtml
CSCsb40304Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
Cisco IOS is affected by the following vulnerabilities:
–Processing ClientHello messages, documented as Cisco bug ID CSCsb12598
–Processing ChangeCipherSpec messages, documented as Cisco bug ID CSCsb40304
–Processing Finished messages, documented as Cisco bug ID CSCsd92405
Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.
Note Another related advisory has been posted with this advisory. This additional advisory also describes a vulnerability related to cryptography that affects Cisco IOS. This related advisory is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.
A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.
CSCsd85587A vulnerability has been discovered in a third party cryptographic library which is used by a number of Cisco products. This vulnerability may be triggered when a malformed Abstract Syntax Notation One (ASN.1) object is parsed. Due to the nature of the vulnerability it may be possible, in some cases, to trigger this vulnerability without a valid certificate or valid application-layer credentials (such as a valid username or password).
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
The vulnerable cryptographic library is used in the following Cisco products:
–Cisco IOS, documented as Cisco bug ID CSCsd85587
–Cisco IOS XR, documented as Cisco bug ID CSCsg41084
–Cisco PIX and ASA Security Appliances, documented as Cisco bug ID CSCse91999
–Cisco Unified CallManager, documented as Cisco bug ID CSCsg44348
–Cisco Firewall Service Module (FWSM)
This vulnerability is also being tracked by CERT/CC as VU#754281.
Cisco has made free software available to address this vulnerability for affected customers. There are no workarounds available to mitigate the effects of the vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.
Note Another related advisory is posted together with this Advisory. It also describes vulnerabilities related to cryptography that affect Cisco IOS. A combined software table for Cisco IOS only is available at http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml and can be used to choose a software release which fixes all security vulnerabilities published as of May 22, 2007. The related advisory is published at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.
CSCsd92405Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
Cisco IOS is affected by the following vulnerabilities:
–Processing ClientHello messages, documented as Cisco bug ID CSCsb12598
–Processing ChangeCipherSpec messages, documented as Cisco bug ID CSCsb40304
–Processing Finished messages, documented as Cisco bug ID CSCsd92405
Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.
Note Another related advisory has been posted with this advisory. This additional advisory also describes a vulnerability related to cryptography that affects Cisco IOS. This related advisory is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.
A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml
CSCek48162: TDM cross connects before last call disconnect and assertionsSymptom : Under heavy stress few tdm assertion failures are seen
Conditions :This is seen with SS7 with more than 50 calls per second.
Workaround: There is no workaround
CSCek51075: Assertion failures at tdm_local_endpoints_connect CSCek61570 Trunk dn stuck in seize/seize state and does not recover.Symptom : Few assertions may be seen during bootup and for the first set of calls. This does not have any effect on the system.
Conditions : This may happen in a situation when the calls are cleared as the system goes for a rommon.
Workaround : There is no workaround
CSCsb25337:Unnecessary tcp ports opened in default router config Cisco devices running IOS that support voice and are not configured for Session Initiated Protocol (SIP), are vulnerable to a crash. However, these devices are isolated to traffic destined to User Datagram Protocol (UDP) 5060. Devices which are properly configured for SIP processing are not vulnerable to this issue.Workaround : See the advisory posted at: http://www.cisco.com/warp/public/707/cisco-sa-20070131-sip.shtml
CSCsc72722: CBAC-firewall resets TCP idle timer upon receiving invalid TCP packetsSymptom : TCP connections that are opened through a Cisco IOS Firewall (CBAC) may not timeout.
Conditions : With Cisco IOS Firewall (CBAC) enabled, the TCP idle timer for a session may be reset even by TCP packets that fail TCP inspection and are subsequently dropped. This could lead to the TCP session not timing out.
Workaround : There is no workaround.
CSCsd91454: One way voice traffic due to incorrect IPHC(UDP) Di0: CS 1 IPCRCSymptom : Voice traffic is dropped in one direction due to IPHC IPCRC error.
Conditions :The problem is found some time after the voice call has been established. When the problem is occurring, the logs show IPHC error messages.
Workaround : Use process switching
CSCsd92405: Router crashes on receipt of repeated SSL connection with malformed finished messageSymptom : A router crashes when receiving multiple malformed TLS and/or SSL3 finished messages. A valid user name and password are not required for the crash to occur.
Conditions : This symptom is observed when a router has HTTP secure server enabled and has an open, unprotected HTTP port.
Workaround : There is no workaround, however, user can minimize the chances of the symptom occurring by permitting only legitimate hosts to access HTTP on the router.
CSCse58397: ISDN BRI Dialer Interface is always in up stateSymptom : ISDN B channels are in UP state
Conditions :After reload and after shut/no shut
Workaround : There is no workaround
CSCsf28515: Crashes at mars_default_port_dsp_connectSymptom : Router crashes at mars_default_port_dsp_connect after call passes through the digital voice-port.
Workaround : There is no workaround
CSCsf28711: 5850 reloads unexpectedly on making a single call CSCsf28840 crash due to configured peer type control vectorSymptom : Active eRSC reloads with traceback when first (PRI/SS7)call is made.
Conditions : This issue is seen when 5850tb is working with 12.4(10.5)PI5 image. Gateway come up with this image, when first (PRI/SS7) call is made the active eRSC reloads unexpectedly with traceback. This reload is seen for both H323 and SIP calls. Similar issue is seen in 5400 when MGCP-SIP call is made.
Workaround :There is no workaround
CSCsg16908: IOS FTP Server DeprecationCSCsg46546: Erroneous alerting during pickup with CSCek58324. Call focus is wrong after picking up a trunk dnSymptom : After an attempt to pick up an onhold trunk dn, the call display on the ephone which puts this DN to onhold is messed up. The call can not be picked up successfully by other phone and it becomes the focus one on the phone. The connected trunk dn can not be displayed and other incoming call can not be put on hold.
Conditions : There are two incoming trunk DN calls. The 1st one is answered and then the 2nd one. The 1st one is put onhold automatically when the 2nd one is answered. After the other phone attempts to pick up the 1st call, the pickup fails and the 1st call becomes the focus one on the phone. The softkey is displayed incorrectly.
Workaround : Press the line button to resume the call onhold instead of picking it up from pickup button or fac dialing. However, this workaround can not be applied to a phone which does not have the trunk DN configured.
CSCsg47834: NACK is observed for Open Voice Channel commandSymptom : NACK message may be received from 5510 DSP in response to Open Voice Channel command sent by the IOS.
Conditions : This problem may be observed when a same 5510 DSP is used as a Trans coding and Voice Termination resource.
Workaround : 1) Disable Trans coding (or)
2) Make sure that the Trans coding and Voice Termination are on different DSP(s). This can be performed by configuring the maximum number of trans coding sessions to a value such that it would require a multiple of 240 DSP credits. Example 1:
In the following configuration each trans coding session (complexity=high) will require 40 DSP credits. In order to use a multiple of 240 credits, we need to set the maximum trans coding sessions to 6 (6 * 40 = 240) or any multiple of 6.dspfarm profile 1 trans codecodec g711ulawcodec g729r8associate application SCCPRouter(conf-t)#dspfarm profile 1 transcodeRouter(config-dspfarm-profile)#maximum sessions 6Example 2:
In the following configuration each transcoding session (complexity=medium) will require 30 DSP credits. In order to use a multiple of 240 credits, we need to set the maximum trans coding sessions to 8 (8 * 30 = 240) or any multiple of 8.dspfarm profile 2 trans codecodec g711ulawcodec g711alawcodec g729ar8codec g729abr8associate application SCCPRouter(conf-t)#dspfarm profile 2 transcodeRouter(config-dspfarm-profile)#maximum sessions 8Use "show voice dsp group all" command to verify DSP resource allocation.
Note Each 5510 DSP has 240 Credits. This work-around cannot be implemented if the router has only one PVDM2-16 which has only one DSP.
CSCsg59037: 851/871 cannot upgrade rommon from IOSSymptom : Cisco 851 and 871 routers have no way to remotely upgrade the ROMMON firmware image.
Conditions : Cisco IOS versions for the Cisco 851 and 871 routers did not provide a mechanism to remotely upgrade the ROMMON firmware image.
Workaround : Cisco IOS Release 12.4(11)T1 for the Cisco 851 and 871 router introduces the command upgrade rom-monitor file which allows the ROMMON firmware image to be remotely upgraded. See this link for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124tcr/tcf_r/cf_13ht.htm#wp1032550
CSCsg66096: Privacy ON: call onhold can be intercepted by directed pickup operationCSCsg66846: TNP phones opening new call when selecting shared transferring lineCSCsg68199: Trunk DN offhook is not propagated to a phone already in dial out modeSymptom : Two IP Phones A and B are registered with Cisco CallManager Express; these phones share two trunk DNs 1 & 2. If Phone-A goes offhook on DN-1 and Phone-B immediately goes offhook on DN-2. This condition should show the DN-2 button on Phone-A as busy which is not happening.
Conditions :This happens only when trunk DNs are used and the they go offhook in quick succession on different phones and are in dialing mode.
Workaround : There is no workaround
CSCsg68711: Incoming call in background does not ring after transfer commitSymptom : Phone does not ring for the second incoming call after committing transfer at alert for the first call.
Conditions : While transferring a trunk DN call, a call comes in. After committing the transfer at alert, the incoming call still does not ring on the phone.
Workaround : There is no workaround.
CSCsg70221: DTMF through the hairpin of a trunk DN does not workSymptom : DTMF tones are being suppressed to prevent duplicate DTMF tones from being extended to an SCCP controlled VG224 port. This problem is a direct result of a fix implemented for correct CSCsf98754. The lack of DTMF prevents IVR devices from working correctly.
Conditions : PSTN -- FXO --- CME GATEWAY --- VG224/FXS --- IVR A call comes into a FXO port that is part of a trunk group and gets transferred to an extension that is hanging off of a VG224. DTMF is not relayed to the end point
Workaround : Setting the transfer system to full blind will prevent the DTMF blocking.
CSCsg70355: New default day light savings summer-time rules from Energy Policy Act of 2005 may cause Cisco IOS to generate timestamps that are off by one hourSymptom : Starting in the calendar year 2007, daylight savings summer-time rules may cause Cisco IOS to generate timestamps (such as in syslog messages) that are off by one hour.
Conditions : The Cisco IOS configuration command: clock summer-time zone recurring uses United States standards for daylight savings time rules by default. The Energy Policy Act of 2005 (H.R.6.ENR), Section 110 changes the start date from the first Sunday of April to the second Sunday of March. It changes the end date from the last Sunday of October to the first Sunday of November.
Workaround : A workaround is possible by using the clock summer-time configuration command to manually configure the proper start date and end date for daylight savings time. For example: After the summer-time period for the calendar year 2006 is over, one can configure:
clock summer-time PDT
recurring 2 Sun Mar 2:00 1 Sun Nov 2:00 (This example is for the US/Pacific time zone.)
CSCsg75035: Async Interface not showing up in the IfIndex from a remote NMS machineSymptom : The interface is indexed on the router but the snmpwalk/snmpget keywords do not seem to return the value when the sh snmp mib ifmib ifindex command is used.
Conditions : This happens when loading a 3825 running 3825-adventerprisek9-mz.124-4.XC5.bin
Workaround : There is no workaround
Resolved Caveats - Cisco IOS Release 12.4(4)XC5
CSCse56800Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS that can be exploited remotely to trigger a memory leak or to cause a reload of the Cisco IOS device.
Cisco has released free software updates that address these vulnerabilities. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities addressed in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself, if administrators do not require the Cisco IOS device to provide voice over IP services.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-sip.shtml.
CSCsf04754Multiple Cisco products contain either of two authentication vulnerabilities in the Simple Network Management Protocol version 3 (SNMPv3) feature. These vulnerabilities can be exploited when processing a malformed SNMPv3 message. These vulnerabilities could allow the disclosure of network information or may enable an attacker to perform configuration changes to vulnerable devices. The SNMP server is an optional service that is disabled by default. Only SNMPv3 is impacted by these vulnerabilities. Workarounds are available for mitigating the impact of the vulnerabilities described in this document.
The United States Computer Emergency Response Team (US-CERT) has assigned Vulnerability Note VU#878044 to these vulnerabilities.
Common Vulnerabilities and Exposures (CVE) identifier CVE-2008-0960 has been assigned to these vulnerabilities.
This advisory will be posted at http://www.cisco.com/warp/public/707/cisco-sa-20080610-snmpv3.shtml
CSCsf11855Multiple voice-related vulnerabilities are identified in Cisco IOS software, one of which is also shared with Cisco Unified Communications Manager. These vulnerabilities pertain to the following protocols or features:
–Session Initiation Protocol (SIP)
–Media Gateway Control Protocol (MGCP)
–Signaling protocols H.323, H.254
–Real-time Transport Protocol (RTP)
–Facsimile reception
Cisco has made free software available to address these vulnerabilities for affected customers. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities mentioned in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-voice.shtml
CSCse05642Multiple voice-related vulnerabilities are identified in Cisco IOS software, one of which is also shared with Cisco Unified Communications Manager. These vulnerabilities pertain to the following protocols or features:
–Session Initiation Protocol (SIP)
–Media Gateway Control Protocol (MGCP)
–Signaling protocols H.323, H.254
–Real-time Transport Protocol (RTP)
–Facsimile reception
Cisco has made free software available to address these vulnerabilities for affected customers. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities mentioned in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-voice.shtml
CSCse68138Multiple voice-related vulnerabilities are identified in Cisco IOS software, one of which is also shared with Cisco Unified Communications Manager. These vulnerabilities pertain to the following protocols or features:
–Session Initiation Protocol (SIP)
–Media Gateway Control Protocol (MGCP)
–Signaling protocols H.323, H.254
–Real-time Transport Protocol (RTP)
–Facsimile reception
Cisco has made free software available to address these vulnerabilities for affected customers. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities mentioned in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-voice.shtml
CSCek56688: Change after-hours login timer to 1 min.Symptom : The minimum after-hours login timer is 5 minutes. It is too long. Customer wants to be able to deactivate the login in 1 min.
Conditions : The problem is observed when after-hours call blocking is enabled.
Workaround : There is no workaround.
CSCek58324: Call focus is wrong after picking up a trunk dnSymptom : The call display does not work correctly when attempting to pick up an onhold trunk DN. The call cannot be picked up successfully by any other phone and it becomes the focus one on the single phone. The connected trunk DN cannot be displayed and other incoming calls cannot be put on hold.
Conditions : There are two incoming trunk DN calls. The first one is answered and then the second one. The first one is put onhold automatically when the second one is answered. After the other phone attempts to pick up the first call, the pickup fails and the first call becomes the focus on the single phone. The softkey is displayed incorrectly.
Workaround : Press the line button to resume the call onhold instead of picking it up from pickup button or fac dialing. However, this workaround cannot be applied to a phone that does not have its trunk configured for DN.
CSCsc74157: Pings fails with using ISDN switch-type primary-qsigSymptom : A ping failed when using ISDN switch-type QSIG.
Conditions : This occurs with a Cisco 3725 and a Cisco 3845 back-to-back with ERNST-T2.
Workaround : There is no workaround.
CSCsd47303: Ephone template for ringing stateSymptom : With Cisco CME 4.0, an ephone-template has states for alerting, seized, connected and idle states. The softkey template needs to be defined for the ringing state (of an incoming call).
Workaround : There is no workaround.
CSCsd48251: Held call on shared line shows From Unknown NumberSymptom : After a certain amount of time, some calls that have been received on a shared line and placed on hold will show From Unknown Number.
Workaround : There is no workaround.
CSCse04642: CME GUI can not change ringtype for sidecar lines when log in as userSymptom : When you log in as a user in CME GUI, you cannot change the ringtype for sidecar lines. You can change the lines on the ip phone but not the lines that belong to the sidecar. If a user is logged in the Cisco CME GUI (log in as user) and changes the ringtype via GUI for the sidecar line and then hits save, the action will save successfully but when you go to the line again the previous ringtype still shows.
Conditions : The problem is seen on Cisco IOS 12.3(14)T5 Cisco CME 3.3 and ios 12.4(4)XC1 and Cisco CME 4.0.
Workaround : This will work if the user changes from CLI ro log in GUI ad admin.
CSCse05642: I/O memory corruption crash on AS5850Symptom : A redzone violation causes a Cisco AS5850 to crash.
Conditions : This symptom is observed on a Cisco AS5850 gateway having MGCP-NAS package and outgoing VoIP calls.
Workaround : There is no workaround.
CSCse56800: SIP-3-BADPAIR register timer expiry causes slow memory leakSymptom : SIP Processes causing slow memory leak when there are no active calls on a Cisco 3725. Specifically, the SIP register timer expiry messages are causing this behavior. Reloading the router does not resolve the issue.
Conditions : The message below is what causes this behavior:
007042: Jun 17 15:18:45.024 EDT: %SIP-3-BADPAIR: Unexpected timer 23(SIP_TIMER_REMOVE_TRANSACTION) in state 27 (SIP_STATE_OPTIONS_WAIT) substate 0 (SUBSTATE_NONE)Workaround : There is no workaround
CSCse68138: Handle fragmented packets in VOIP RTP LibSymptom : Router may reload due to fragmented RTP packets. This is a platform independent problem.
Conditions : This problem is likely to happen in networks where VOIP is one of applications and one more segments of network are using low MTU.
Workaround : There is no workaround.
CSCse71162: Change minimum ephone keepalive timer from 10 to 1 secondSymptom : Request to reduce the minimum configurable keepalive timer from 10 to 1 second in CME for SCCP phones.
Workaround : There is no workaround.
CSCse82300: Getting Undefined Tone when we enter a invalid FACSymptom : The CFA feature in the Cisco VG224 is enabled and we are dialing an invalid FAC code via callgen. We expect to get a reorder tone immediately but we are getting only the Undefined_tone.
Workaround : There is no workaround.
CSCse83674: FXS port cannot be recovered when offhook with howler tone at end of callSymptom : Analog FXS port on a Cisco 2800/3800 ISR does not go back to idle if it has been offhook for more than a minute at the end of a call.
Conditions : A and B are two FXS ports on the same router connected to analog phones. A calls B. B answers the call. Once the conversation is done, A hangs up. B does not go onhook. After 60 seconds, B starts hearing offhook alert (howler) tone. Putting B onhook now has no effect. B continues to play offhook alert for the rest of its life until the router is reloaded.
Workaround : There is no workaround.
CSCse87446: Extension assigner defaults provision-tags to 0Symptom : Extension assigner will chose wrong extension if the provision-tag input is zero.
Workaround : Use the ephone-tag.
CSCsf02737: Memory Corruption Crash at chunk_free_callerSymptom : A Cisco 3825 running Cisco IOS 12.4-9.T crashed. The decoded tracebacks is as follows:
abortcrashdumpchunk_free_callerfree_lite_internal__freefreeskinny_send_msg_internalskinny_server_processr4k_process_dispatchConditions : This seems similar to CSCsb80447.
Workaround : Configuring no memory lite seems to alleviate the crashes.
CSCsf07990: CME Dynamic Hunt-Group Login failsSymptom : Ephone-1 has extension 88, which is also added as a monitor line on a 7914. The Ephone-2, which is connected to the 7914 is in DND state. Now when you try to login to a hunt-group on ephone-1, it fails because the ephone with the monitor lines is in DND state.
Aug 14 08:36:07: SkinnyHGJoinByDn: dn(88), join_code(80), join(1)Aug 14 08:36:07: Cannot join 88 to hunt group list with dnd on.Aug 14 08:36:07: ephone-1[13]:SkinnyHGJoinByPhone phone-[7] join 80 failed.Workaround : Ephone with the Cisco IP Phone 7914 should not be in DND state.
CSCsf21007: Ephone hunt-group does NOT present calls to monitored DNsSymptom : When an ephone hunt-group is configured with present-call idle-phone, the ephone hunt-group skips over certain members of the hunt group.
Conditions : The problem is observed when members of the ephone hunt-group are monitored.
Workaround : Do not monitor the members of the hunt-group.
CSCsf21458: SRST Reuses sockets causing phones unregisterSymptom : Registered ephones in SRST mode may unregister and then re register
Conditions : This happens when the phone requests for a socket that has already been used by another ephone.
Workaround : There is no workaround.
CSCsf98754: Inband DTMF should be squelched for calls from POTS to SkinnySymptom : The following scenario is seen:
PSTN === Analog or T1 CAS FXO === CME ------ VG224 ---- Phone or IVRThe analog ports on the Cisco VG224 are SCCP controlled by Cisco CME.
For a call between PSTN and a Cisco VG224 port (or an IP Phone), the DTMF detection is turned ON on the FXO port. Along with this, the DSP channel associated with the FXO port is programmed to pass through the DTMF tone in the RTP path instead of suppressing it.
The above manifests into a double DTMF digit scenario and is very well pronounced when the Cisco VG224 port is connected to an IVR system looking for digits. For the endpoints controlled by Cisco CME via SCCP, the DTMF relay happens through out of band SCCP messages. Since the original DTMF digit coming from PSTN is not suppressed, we see two digits reaching the IVR system - one from the SCCP message from Cisco CME to the Cisco VG224 port and the second one embedded in the RTP path.
Conditions : A simple way to reproduce this problem is as follows:
Phone----FXS=CME----- IP Phone or VG224Make a call from phone on the left to a CME controlled endpoint. Press a digit button on the left phone and hold it for a long time. The user on the CME controlled endpoint on the right can hear: digit beep, silence and continuous digit beep. If the squelching flag was set on the FXS DSP channel, the user would have heard digit beep, silence and back to voice path.
Workaround : There is no workaround.
CSCsf99737: SRST Locale fail over soft keys still display EnglishSymptom : SRST fails over from Cisco Unified CallManager still displays English languages in softkey regardless of the languages that is configured in Cisco Unified CallManager.
Workaround : There is no workaround.
Resolved Caveats - Cisco IOS Release 12.4(4)XC4
CSCse68355Multiple voice-related vulnerabilities are identified in Cisco IOS software, one of which is also shared with Cisco Unified Communications Manager. These vulnerabilities pertain to the following protocols or features:
–Session Initiation Protocol (SIP)
–Media Gateway Control Protocol (MGCP)
–Signaling protocols H.323, H.254
–Real-time Transport Protocol (RTP)
–Facsimile reception
Cisco has made free software available to address these vulnerabilities for affected customers. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities mentioned in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-voice.shtml
CSCsc74783Symptom : Intrusion Prevention System (IPS) signatures that require inspection of TCP flows below port 550 may not be triggered on a Cisco IOS IPS device.
Conditions : This symptom is observed on a Cisco IOS router that is configured for IPS functionality.
Workaround : Apply CBAC (Context Based Access Control) in addition to IPS.
Further Information: On a Cisco IOS router with IPS (Intrusion Prevention System) enabled, all TCP flows should be subject to TCP stateful inspection until the TCP 3-way handshake is complete. This does not work for TCP sessions with a destination port that is less than 550, if it does not match a predefined signature on the router.
CSCek47681: Backplane TDM loss and assertion failuresSymptom : Under heavy stress, time division backplane timeslots may be lost over time.
Conditions : The symptom occurs with SS7 and more than 50 calls per second.
Workaround : There is no workaround.
CSCse06975: Traceback at pak_copy_contiguous_to_contiguous when testing multicastSymptom : The VoIP LMR multicast does not function properly with E&M on the NM-HD-2V network module.
Workaround : There is no workaround.
CSCse16973: show controller call-counters displays negative valuesSymptom : The show controller t1 call-counters command displays negative values for the DSO Active counter.
Conditions : The symptom occurs on the Cisco AS5400XM platform for both voice and data calls.
Workaround : There is no workaround.
CSCse18940: Memory depletes when VoAAL2 traffic is passed.Workaround : There is no workaround.
CSCse27845: One way voice after ringing pickup of transferred at-alert callSymptom : The called party may not be able to hear the caller.
Conditions : Phones A, B, and C are controlled by the same CME. A calls B. B does an at-alert transfer to C. While C is ringing, B does a ringing pickup on C's extension. One-way voice results with B being unable to hear A.
Workaround : There is no workaround.
CSCse47728: Path confirmation failures are observed with VoATMSymptom : Path confirmation failures seen with Voice over ATM traffic.
Conditions : This is seen with only with VoAAL2 traffic.
Workaround : There is no workaround.
CSCse50167: Speed dial line buttons disappear from CME phones after the router reloads.Conditions : The speed dials are configured using an ephone template, which is then applied to the affected phone.
Workaround : Remove and re-apply the ephone template after the router reloads.
CSCse56129: Cisco VG224 erroneously triggers hookflash during CME call pickup interactionSymptom : On the Cisco VG224, a voice port registered to CallManager Express running. 12.4(4)XC may falsely detect a hookflash in the call pickup case.
Conditions : During call pickup, the CME sends an onhook signal to the VG224 port, presents a new call and immediately instructs the port to move to connected state. During these quick steps, the voice port on the VG224 is erroneously reporting a hookflash.
Workaround : Configure no supervisory disconnect lcfo on the Cisco VG224 voice port to avoid the false hookflash detection in the CME call pickup case.
CSCse56660: Inbound calls to fxo port fail (no audio) when caller-id enabledSymptom : Inbound calls to Foreign Exchange Office (FXO) ports on Cisco IOS VoIP gateways connect, but audio is not present.
Conditions : With caller-id enable configured on FXO ports, the call will connect, but no audio is heard. When this occurs, the following error message can be seen at debug level:
Jun 20 01:41:15.855: mbrd_e1t1_vic_connect: setup failedJun 20 01:41:15.855: flex_dsprm_tdm_xconn: voice-port(0/0/1), dsp_channel(/0/2/0)Workaround : Disable caller-id on the voice port.
CSCse59347: CME/SRST IP phone unregister does not down the virtual pots peersSymptom : Using SRST 4.0 with Cisco Unified CallManager Express, calls may fail with a "user busy" signal.
Conditions : When the IP phone must unregister/fall back to the Cisco Unified CallManager, the virtual POTS dial-peers do not disconnect and calls fail with user busy rather than being sent via the H.323 dial-peer to the Cisco Unified CallManager.
Workaround : There is no workaround.
CSCse69235: 871 XC - S&K interface forwarding results in hung interfaceSymptom : VLAN interfaces on Cisco 870 series routers may cease to function under heavy loads.
Conditions : If the 802.1x feature is configured as a layer 3 transport in 12.4(4)XC images and continuous, heavy, and unauthenticated traffic is received on a virtual interface, the router may stop responding.
Workaround : There is no workaround.
CSCse70333: CFwdAll erroneously reconfigured after disabling night serviceSymptom : CFwdAll incorrectly appears after night service is disabled.
Conditions : CFwdAll was initially configured using softkey, and unconfigured through the CLI. On the same DN as CFwdAll was on, night service is enabled and disabled.
Workaround : Remove CFwdAll via softkey or reload the router.
CSCsc42589: Reset msg to TAPI client when phone reset restart by CME.CSCsc72502: The TAPI client may not show the call lines in ringing or connected state for the controlled ephone.Conditions : If the TAPI client registers to the CME while its controlled ephone has some connected or ringing lines, it would not show their status. It would show them all in IDLE state. This problem occurs in any CME releases.
Workaround : There is no workaround.
CSCse06975: Traceback at pak_copy_contiguous_to_contiguous when testing multicastSymptom : VoIP LMR multicast capability does not work on network module NM-HD-2V with E&M.
Workaround : There is no work around.
CSCse15025:Intermittent analog/cas voice port lockup or robotic voiceSymptom : An analog or digital CAS port enters a state in which inbound or outbound calls, or both, may no longer function through the port.
Conditions : This symptom is observed on a Cisco 2800 series and Cisco 3800 series that function as gateways with analog or digital CAS ports that use PVDM2 DSP modules.
When this problem occurs, it impacts multiple ports that share the same signaling DSP. The output of the show voice dsp signaling EXEC command shows which DSP is used by a port for signaling. The symptom may occur more often for ports that use DSP 1 on the PVDM2 module for signaling.
Because this issue impacts the signaling channels, it has been seen that calls either will not connect at all through impacted ports or in some cases when multiple simultaneous calls are present on adjacent voice ports/timeslots, the call may connect momentarily before being disconnected.
If a problem occurs only on a single voice port, there is another problem, not this caveat (CSCse15025). PRI/BRI calls are not affected because PRI/BRI does not utilize the DSP for signaling purposes.
When the symptom occurs with either a VIC2-xFXO or EVM DID/FXS module, enter the terminal monitor command followed by the test voice port port- number si-reg-read 39 1 command for one of the affected ports. The output typically should be a single octet value for register 39. When the symptom occurs, information for Registers 40, 41, and 42 is presented and some of the registers show double- octet information. See the example output (2) below.
When the symptom occurs with FXS or analog E&M modules, enter the terminal monitor command followed by the test voice port port- number codec-debug 10 1 command for one of the affected ports. The output typically should be a single octet value for each register. See the example output (4) below.
Workaround : There is no workaround.
CSCse47338: H245-signal dtmf relay requires signal update to end digitsSymptom : A third party device sends dtmf-relay using a h.245-signal, which includes duration of the digit. The CME gateway sends the digit to CUE, but the digit is not considered done unless another digit is received. This results in %SIP-3-DIGITEND: Missing digit end event messages sages.
Workaround : Send an extra (unnecessary) digit, which indicates the previous digit is ended.
CSCse60250: Support Localization for the Cisco IP Phone 7906 on Cisco Unified CME.CSCse66125: Call-waiting ring in ephone-dn-template fails to hold configurationSymptom : When trying to configure call-waiting ring on an ephone-dn x, the configuration is accepted, but cannot be seen in the configuration.
CSCse75014: CME/SRST not able to make calls to Unity VMSymptom : With CME/SRST, you are able to make calls to Unity VM.VM port DN is not coming to "Idle" state after restarting Unity.
Workaround : There is no workaround
CSCeh69448: SCCP CME need to clean up tftp binding.CSCek43094: Add TNP compatible Network locale tags to cnf file.CSCsc82351:Device ID for the Goped phone is incorrectSymptom : The device ID for the Goped phone is incorrect.
Workaround : There is no workaround.
CSCsc85575: Subsequent call following a conf call by TNP Ph results in 1-way audioSymptom : No audio is received from a Cisco 7931 IP phone.
Conditions : This symptom is observed when a call is made between a Cisco IP phone 7960 and a Cisco IP phone 7931. The user of the CiscoIP phone 7960 experiences one-way audio intermittently while the user of the Cisco IP phone 7931 does not experience this symptom.
Workaround : Reset the Cisco IP phone 7931.
CSCsc99639: CME unable to make call on 2nd line using line button when 1 line busySymptom : The CME is unable to make call on a second line using line button when line 1is busy
Conditions : This occurs when you make a call from Phone A to Phone B on Line 1. Answer the call on Phone B on line 1. Press Line 2 on Phone B. The first call is put on Hold on Line 1 but Line 2 button light does not come up and Line 2 has no dial tone and it does not accept a new call on Line 2 at all. Ideally Line 2 should put the call on Hold and then accept new call with giving out dial tone.
Workaround : There is no workaround.
CSCsd13066: No caller ID displayed for a forwarded call on IP Phone running 7.xSymptom : When release 7.x phoneload is used on a forwarding phone, the forward-to party does not see the forwarded party number on the display.
Workaround : There is no workaround.
CSCsd73435: The button-layout help CLI is unclear.CSCsd86966: Not able to create CTL file for 7906 phone.CSCsd90419: Cisco IP Phone 7941/61/11 does not support localization in SRSTSymptom : The Cisco 7941/61/11 phones display change to English in SRST mode.
Conditions : Phone falls back to SRST CME router.
Workaround : There is now workaround.
CSCse05698: CME 12 build in locales support on 7941/61/11.CSCse08865: Enhance CME locale installer to support 7941/61/11/70/71CSCse16210: 7920 locale support enhancement.CSCse29308: CCME extension assigner extraCSCse35293: CCME extension assigner need to update CNF file.CSCse36127: If a Phone is viewed on the GUI the extensions are marked as normal ring even if they are monitored lines. So every time a change is made all lines have to be corrected via the CLI.Workaround : This defect has been rectified via the CME GUI 4.0.0.1a file package. Download and install this CME GUI file package (or newer) to overcome the problem.
CSCse39419: Some phones XML file does not have correct m_vendorSymptom : Cannot configure the phone through the vendorConfig in the XML file
Further Problem Description:The VendorConfig is missing in the XML file.
Workaround : There is no workaround.
CSCse41295: MOH debugs flood the console when MOH file is unconfiguredCSCse56023:CME extension assigner clean upCSCse62649: Change CME GUI logo to Cisco Unified CallManager ExpressCSCse65819: Reset needed after extension assignment of 7914 attached phoneResolved Caveats—Cisco IOS Release 12.4(4)XC3
All the caveats listed in this section are resolved in Cisco IOS Release 12.4(4)XC3. This section describes only severity 1 and 2 caveats, and select severity 3 caveats.
CSCek37177: The Cisco IOS Transmission Control Protocol (TCP) listener in certain versions of Cisco IOS software is vulnerable to a remotely-exploitable memory leak that may lead to a denial of service condition.Symptom : This vulnerability only applies to traffic destined to the Cisco IOS device. Traffic transiting the Cisco IOS device will not trigger this vulnerability.
Workaround : Cisco has made free software available to address this vulnerability for affected customers. There are workarounds available to mitigate the effects of the vulnerability. See the advisory posted at: http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-tcp.shtml
CSCek38136: Hissing noise heard before ringback tone beginsSymptom : When you deploy VoIP using PVDM2 / 5510 DSP modules, a hissing sound may be heard before the ringback tone starts on the calling side.
Conditions : This symptom is observed only with 5510 DSP modules. The symptom does not occur with 549 DSP modules.
Workaround : There is no workaround.
CSCin96828: On TGW, calls might be reject with Duplicate Setup error messageSymptom : Alternate call retry times out because of no response from the terminating gateway
Conditions : Both originating gateway and terminating gateway are registered to the gatekeeper and gatekeeper returns the same physical gateway as both primary endpoint and alternate endpoint with different DNIS. If terminating gateway receives the alternate call before the primary call is cleaned up, it considers the alternate call as duplicate and ignores the SETUP.
Workaround : When same gateway has to be used as primary and alternate, use two different address of the gateway instead same address.
CSCse44965: Cisco Unity does not register to CME with no auto-reg-ephone.Symptom : Cisco Unity does not register with CME 4.0.
Conditions : When no auto-reg-ephone is configured under telephony-service.
Workaround : Enable auto-reg-ephone under the telephony -service.
CSCse41306: The sound quality of the Music on Hold feed is poor.Workaround : Using ST-TC1 in tandem with TBB-1 may work in some cases.
CSCse23652: 7912 registered to CME 3.3 running Cisco IOS 12.4(3b) is not able to initiate a call when controlled by the TSP client running TSPv.Workaround : There is no workaround.
CSCse23304: When selecting "Extensions" in the Configuration drop-down menu in the Call Manager Express GUI for CME 4.0, extension type "Park-Slot" is erroneously listed as being of the type "MWI" and extensions of the type "Paging" are erroneously listed as being of the type "MOH." All other extension types are listed correctly.Conditions : The symptom occurs on CME 4.0 voice routers using CME GUI version 4.0.0.0.
Workaround : If CME 4.0 features are not needed, use an earlier release of CME and its corresponding GUI version. If the CME 4.0 features are needed, configure ephone-dns and ephones via Cisco IOS CLI.
CSCse20435: Memory runs out and fails the system after extended use.Conditions : The memory usage increases when an ephone falls back from a CME or CCME to a SRST.
Workaround : There is no workaround.
CSCsd99389: The system reloads when call forwarding is invoked.Conditions : The symptom occurs if a dialplan pattern and an invalid call forward number are configured.
Workaround : Verify that all call forward numbers are correct or remove the dialplan pattern.
CSCsd57413: Unhide the 7906G-related CLI.CSCsd46996: A memory leak occurs while upgrading CAPFWorkaround : There is no workaround.
CSCek45370: A dialer interface using VWIC-MFT-2T1/E1 may get an ISDN carrier timeout if the terminating gateway does not have dailer-group configured.Workaround : Configure dialer-group on the terminating gateway.
CSCek40644: One channel of a DN may get stuck and incoming and outgoing calls cannot be made.Workaround : Reset the ephone.
CSCsd19564: Button optimization is required for park-recall, pickup-on-hold and pickup-at-alert functions.CSCsd57096: Configuration is prohibited for certain interfaces through the interface range command.Conditions : This symptom occurs on all platforms if the interface range command is used to attempt to configure a range of interfaces when the last physical interface in the range itself contains the sub-interfaces.
Workaround : Configure each of the interfaces individually and outside of the interface range command. Another option is to remove the subinterfaces from the last interface in the range prior to attempting the configuration through the range command.
CSCse19112: Caller name does not display on all IP phones that have shared lines or overlay lines.Workaround : There is not workaround.
CSCse35506: Secondary dialtone is not heard after FAC standard is configured on CME 4.0Workaround : Call can be placed without the dial tone.
CSCse34614: Caller name does not appear on IP phone display.Conditions : The symptom occurs with IP phones that are registered to CME with IOS 12.4(4)XC (CME 4.0), with IP phones that have overlay DNs with call waiting, and with IP phone that has an active call on the overlay dn and a second call is received.
Workaround : There is no workaround.
CSCeg90328: The router crashes when the user tries to convert an sccp phone to an SIP phone.CSCek34261: A Cisco Integrated SONET/SDH router (ISR) may crash during the "gt96k_mbrd_bri_set_bandwidth" function.Conditions : This symptom is observed on the Cisco 1800, 2800, and 3800 series routers that function as an ISR when an incoming call is placed with 32KB bandwidth. The symptom does not occur when has a call has 56 KB or 64 KB bandwidth.
Workaround : Deny the invalid incoming call by entering the <CmdBold>isdn caller<noCmdBold> command on the ISR router.
Additional References
Use these release notes with the documents listed in the following sections:
Release-Specific Documents
The following documents are specific to Release 12.4 and apply to Cisco IOS Release 12.4(11)XJ. They are located on Cisco.com:
•Cross-Platform Release Notes for Cisco IOS Release 12.4(4)T
•Caveats for Cisco IOS Release 12.4 and Caveats for Cisco IOS Release 12.4(4)T
Note If you have an account with Cisco.com, you can also use the Bug Toolkit to find selected caveats of any severity. To reach the Bug Toolkit, log in to Cisco.com, and go to: http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.
Platform-Specific Documents
Hardware installation guides, configuration and command reference guides, and additional documents specific to the Cisco VG224 are available on Cisco.com at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/access/vg/vg224/index.htm
Cisco IOS Software Documentation Set
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents are available online.
Documentation Modules
Each module in the Cisco IOS documentation set consists of one or more configuration guides and one or more corresponding command references. Chapters in a configuration guide describe protocols, configuration tasks, and Cisco IOS software functionality, and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. Use each configuration guide with its corresponding command reference. The Cisco IOS software documentation set is available on Cisco.com.
Release 12.4 Documentation Set
Table 4 describes the contents of the Cisco IOS Release 12.4 software documentation set, which is available online.
Note Some aspects of the complete Cisco IOS Release 12.4 software documentation set might not apply to the Cisco VG224.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feed-back, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Open Source License Acknowledgements
The following notices pertain to this software license.
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
License Issues
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
OpenSSL License:
Copyright © 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License:
Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".
The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.
4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
Use this document in conjunction with the documents listed in the "Additional References" section.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0705R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007, Cisco Systems, Inc. All rights reserved.