Guest

Cisco Unified SIP Proxy Software

Release notes for Cisco Unified SIP Proxy 1.1.3

  • Viewing Options

  • PDF (125.1 KB)
  • Feedback
Release Notes for Cisco Unified SIP Proxy Release 1.1.3

Table Of Contents

Release Notes for Cisco Unified SIP Proxy Release 1.1.3

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

System Requirements

Installation Notes

Limitations and Restrictions

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

Software Compatibility

Determining the Software Version

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

Procedure


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.

Cisco Unified SIP Proxy uses Netconf to perform IOS configuration validation at startup. Netconf over SSH is the only supported mechanism. Support for Netconf over BEEP has been removed. See configuration examples and tech notes for details at http://cisco.com/en/US/docs/voice_ip_comm/cusp/rel1_1_3/configuration/guide/cuspgd113.html

New configuration commands have been added to configure IP routes to facilitate support for multiple network interfaces. See the command reference for details at http://cisco.com/en/US/docs/voice_ip_comm/cusp/rel1_1_3/command/reference/cuspcmdref_book.html

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

Changing Licenses Requires Backing Up Your Configuration

Whenever you change the license for Cisco Unified SIP Proxy Release 1.1.3, the system restores the software to its factory default settings, thereby deleting your system's configuration data.

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.

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 Coresidency Restrictions

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 configured for SIP may co-reside in the same router.

Caveats

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

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.

CSCsx10996

Symptom    Cisco Unified SIP Proxy DNS SRV based call routing does not work after rebooting Cisco Unified SIP Proxy.

Workaround   There are two workarounds. The first is to toggle off, then on the sip dns-srv command. The second is to configure route tables with server-group based routing.

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.

CSCsx38761

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.


Resolved Caveats

CDETS
Description

CSCsx65091

Symptom    CLI access to Cisco Unified SIP Proxy goes to unresponsive mode when executing show trace log command.

CSCsu48446

Symptom    When attempting to boot after doing a clean install, a message displays:

corrupted bzImage detected

The boot then stops.


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.