Guest

Cisco Network Modules

Release Notes for Cisco Unified SIP Proxy 1.1.4

Table Of Contents

Release Notes for Cisco Unified SIP Proxy 1.1.4

Contents

Introduction

System Requirements

Hardware Supported

Software Compatibility

Determining the Software Version

New Features and Enhancements

Installation Notes

Limitations and Restrictions

Caveats

Open Caveats

Resolved Caveats

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Unified SIP Proxy 1.1.4


First Published: May 21, 2009
Last Revised: October 9, 2009
OL-19828-03

This document describes the new features, system requirements, and caveats for Cisco Unified SIP Proxy 1.1.4. Use this document in conjunction with the documents listed in the "Related Documentation" section.

Contents

This document includes the following sections:

Introduction

System Requirements

New Features and Enhancements

Installation Notes

Limitations and Restrictions

Caveats

Related Documentation

Obtaining Documentation and Submitting a Service Request

Introduction

Cisco Unified SIP Proxy is designed to help connect and manage SIP networks. The Cisco Unified SIP Proxy module is designed to be an integrated solution in Cisco 3800 Series Integrated Services Routers (Cisco ISRs). The module provides multiple features including SIP trunk aggregation, name resolution, routing, scalability, and high availability.

System Requirements

Hardware Supported

The Cisco Unified SIP Proxy module runs on the NME-522 module. The part number of the Cisco  Unified SIP Proxy module is NME-CUSP-522-K9. The module has 2 GB of RAM and 160 GB HDD. This module installs only on the Cisco 3825 or 3845 ISRs.

Software Compatibility

The Cisco Unified SIP Proxy module requires Cisco IOS Release 12.4(22)T or a later release on the Cisco ISR with k9 feature set.

Determining the Software Version

To determine the software version and the license used, perform the following steps:


Step 1 Open a Telnet session.

Step 2 Telnet to the router by entering telnet ip-address.

Step 3 Enter the user ID and password of the router.

Step 4 Enter the following command to enter the command environment:

enable

<router password>

service-module service-engine slot/port session

Step 5 Enter the following command to display the Cisco Unified SIP Proxy software version:

show software versions

Step 6 Enter the following command to enter Cisco Unified SIP Proxy execution mode:

cusp

Step 7 Enter the following command to display the Cisco Unified SIP Proxy software license:

show license


For information about IOS open source licensing, see the Notices section in the About Cisco IOS Release Notes at:

http://www.cisco.com/en/US/docs/ios/12_4/12_4x/12_4xy15/ReleaseNote.html#wp398419

New Features and Enhancements

This section contains new features or enhancements added in this release.

New configuration commands have been added to configure the maximum size that a UDP datagram can be on a network. For more details, see the Cisco Unified SIP Proxy Command Reference.

New exec commands have been added to show the calls per second data that the CUSP is handling. For more details, see the Cisco Unified SIP Proxy Command Reference.

Tracing for specific components (for example, normalization) is now enabled. For more details, see the Cisco Unified SIP Proxy Command Reference.

The "TO" header is now an available option for route lookup policies. For more details, see the Cisco Unified SIP Proxy Command Reference.

Installation Notes

The software is already loaded at the factory, and you can install it using the command:

software install clean url ftp://x.x.x/cusp-k9.nme.x.x.pkg

There are three software files, all of which you should save to the FTP directory. You need to load the .pkg file, the other files are downloaded automatically. See Table 1.

Table 1 Software Files

Name
Size

cusp-k9.nme.x.x.pkg

100 KB

cusp-full-k9.nme.x.x.prt1

87 MB

cusp-installer-k9.nme.x.x.prt1

128 KB


Limitations and Restrictions

This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer, and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute, or use encryption. Importers, exporters, distributors, and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html.

If you require further assistance send an email to export@cisco.com.

Voice and router functions may co-reside in the same router with Cisco Unified SIP Proxy with two exceptions:

Cisco Unified SIP Proxy may not co-reside in the same router when Cisco Unified Communications Manager Express (Cisco Unified CME) or Cisco Unified Survivable Remote Site Telephony (Cisco Unified SRST) are configured for SCCP phones.

Cisco Unified SIP Proxy may not co-reside in the same router with time division multiplex (TDM) gateways or configuration of H.323 dial peers (including Cisco Unified Border Element).

Cisco Unified CME, Cisco Unified SRST, and Cisco Unified Border Element (Cisco UBE) configured for SIP may co-reside in the same router.

Caveats

This section contains open and resolved caveats for Cisco Unified SIP Proxy 1.1.4.

Open Caveats

Resolved Caveats

These caveats describe unexpected behavior in Cisco Unified SIP Proxy 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.


Note If you have an account on Cisco.com, you can use Bug Toolkit to find caveats of any severity. The Bug Toolkit is at: http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl


Open Caveats

This section contains open caveats for Cisco Unified SIP Proxy 1.1.4.

CSCsx18654

Symptom    When multiple IPs are configured on Cisco Unified SIP Proxy, SIP messages source from wrong source ip.

Conditions   Cisco Unified SIP Proxy is configured with multiple ip interfaces.

CSCta74132 

Symptom    SIP messages in the Cisco Unified SIP Proxy SIP message log may appear out of order. It may appear that Cisco Unified SIP Proxy has sent a message and then received a message, where the reverse is what has actually occurred.

Conditions   Typically, the messages that are out of order are responses to other messages, where the response appears before the initial message. This is because of the the asynchronous method of writing to the logs.

Workaround   The timestamps are accurate, and can be checked to confirm the actual order of events.

CSCtb04626 

Symptom    Certificate Subject Alternate Name (SubjectAltName) may not be correct on imported certificates.

Conditions   Import a certificate using the cut-and-paste method (that is, use the following command:

module(config)> crypto key import trustcacert label <trustpoint-name> terminal)

Workaround   Import the certificate using the "url" option instead of the "terminal" option.

CSCtb12771

Symptom    There is no command-line interface (CLI) command available to disable FTP or PFS services.

CSCtc17438

Symptom    When attempting to boot after a clean installation, the message "corrupted bzImage detected" appears. The boot then halts.

Conditions   Unknown. This occurs occasionally after issuing a software install clean command.

Workaround   Boot the helper image, and reinstall. The service module will now boot.

Resolved Caveats

This section contains resolved caveats for Cisco Unified SIP Proxy 1.1.4.

CSCsw43287

Symptom    When using the show configuration active | page command, if you issue a q to exit the configuration from displaying any more pages, you are removed from the CUSP mode and returned to the module level exec mode of the CLI.

CSCsw97690

Symptom    There are two symptoms of this bug. The first is that pinging of all elements (TCP/TLS/UDP) will be delayed. Therefore, their status may not be accurately reflected by the show server-group status command. The second is that committing a configuration can cause the CLI to hang for several minutes.

CSCsx10996

Symptom    CUSP DNS SRV based call routing does not work after rebooting CUSP.

CSCsx38761

Symptom    When trying to make a call to the SRV defined device, CUSP cannot establish a connection and issues a 502 message to the calling device.

CSCsx48124

Symptom    The maddr parameter in the request-uri is not handled properly.

CSCsx62364

Symptom    Invites from the Avaya PBX are rejected with a 404 "no matching algorithm found" message.

CSCsx65522

Symptom    Normalization on user portion of request-uri fails, NullPointerException is thrown during normalization operation. (This can be seen by looking at the trace.log file)

Related Documentation

For Cisco Unified SIP Proxy documentation and configuration white papers, see:

http://cisco.com/en/US/products/ps10140/tsd_products_support_model_home.html

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, 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

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.