Release Notes for Cisco Unified SIP Proxy Release 1.1.3

First Published: May 21, 2009

Last Revised: December 12, 2011

OL-19828-01

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

Contents

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.

Therefore, if you need to change the license, you must first back up your configuration. After you change the license, you must restore the configuration. Otherwise, you will lose all of your system's configuration data.

Caution You must back up your system's configuration data before changing the license or you will lose all of your system's configuration data.

Cryptographic Features

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.

Open Caveats

CDETS

Description

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.

Conditions Invalid or down TCP elements are listed in server-group status.

Workaround Only use UDP or TLS elements in server-group configurations.

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

Conditions This problem only occurs if the network is of type NAT.

Workaround Use a different network type, standard, for example.

CSCsx48124

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

Conditions Cisco Unified SIP Proxy fails to remove the maddr parameter if it is pointing to Cisco Unified SIP Proxy on incoming requests. Cisco Unified SIP Proxy fails to forward the message based on the maddr address on outgoing requests.

CSCsx62364

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

Conditions An Avaya PBX is used.

Workaround Use a different model PBX.

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.)

Conditions The user portion of the request-uri is empty.

Workaround Normalize the entire request-uri to add/update the user portion.

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 Cisco Unified SIP Proxy mode and returned to the module level exec mode of the CLI.

Conditions Only occurs for show commands within Cisco Unified SIP Proxy mode.

Workaround Avoid using q or ctrl-c. If you do, type cusp to get back into Cisco Unified SIP Proxy mode. To get into configure mode, type configure.

CSCsy80883

Symptom In some scenarios, when Cisco Unified SIP Proxy fails to successfully route the message based on the first SRV record (destination is unavailable), it is not trying the next record in the list even when one exists.

Conditions Only when routing is configured to use SRV and failover is done based on SRV records.

Workaround Use server groups instead of SRV for failover and load balancing.

Related Documentation

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:

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.

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. (0812R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.