Release Notes for Cisco Unified SIP Proxy Release 9.1.x
First Published: September 21, 2015
Last Revised: December 14, 2020
This document describes the new features, system requirements, licensing information, and caveats for Cisco Unified SIP Proxy Release 9.1.x. Use this document in conjunction with the caveats listed in Caveats for the respective releases.
Cisco Unified SIP Proxy is a high-performance, highly available Session Initiation Protocol (SIP) server for centralized routing and SIP signaling normalization. By forwarding requests to call-control domains, Cisco Unified SIP Proxy provides the means for routing sessions within enterprise and service provider networks. Cisco Unified SIP Proxy provides multiple features, including SIP trunk aggregation, name resolution, routing, load balancing, scalability, and high availability.
Cisco Unified SIP Proxy 9.1.x is delivered as an Open Virtual Appliance (OVA) and can be installed as a virtual machine on Cisco UCS platform. Cisco Unified SIP Proxy Release 9.1.x supports CISCO-USP-MIB through SNMP.
Cisco Unified SIP Proxy Release 9.1 supports SNMP MIBs and traps for monitoring its status using the Cisco-USP-MIB and CISCO-PROCESS-MIB.
Added an inactivity timer configuration that provides a GUI option to configure activity timeout in the range of 10 minutes to 24 hours.
Introduced fd count command that provides an option to change the default file descriptor count value from 1024 to 2048.
The default value of the file descriptor count was enhanced from 1024 to 25000.
Introduced show fd statistics command that provides information on the maximum file descriptor count and the current open file descriptor count. See show fd statistics.
Added tcp and tls options to the show sip command that displays the active Transmission Control Protocol (TCP) and Transport Layer Security (TLS) connections at the Cisco Unified SIP Proxy application level. See show sip.
Introduced show tcp connections command that displays the status of Transmission Control Protocol (TCP) connections at the operating system level. See show tcp connections.
NoteCLI Command Reference for Cisco Unified SIP Proxy Release 9.1.x is not updated with the CLI updates for Cisco Unified SIP Proxy Release 9.1.4.
Introduced server-group sip ping-503 command that checks whether the SIP application service in the remote server element is up or down by monitoring the response. Cisco Unified SIP Proxy GUI is also enhanced to include the “Ping 503" parameter in the Server Groups settings.
Introduced Packet Capture check box in the Cisco Unified SIP Proxy GUI to capture the network traffic on Cisco Unified SIP Proxy interfaces. Each packet capture request is limited to 40 MB.
Cisco Unified SIP Proxy Release 9.1.5 adds support for Cisco Smart Software Manager satellite version 3.0.0.
In Smart Licensing, if the Smart Agent Client is disabled via GUI or CLI, none of the calls are processed. Cisco Unified SIP Proxy should have another successful authorization with Cisco Smart Manager to process calls in the AuthorizedPeriodExpired or EvalExpired mode.
Introduced show license smart agent-version command that displays the smart agent version.
Introduced additional traps in this release. Now vCUSP sends TRAP alert when SIP queue is full or when CPU intensive debug is enabled.
The Cisco Unified SIP Proxy Smart Licensing agent is enhanced to support TLS 1.2.
Limitations and Restrictions
Note Cisco Unified SIP Proxy Release 9.1.x does not support installation of VMware Tools or any third-party tools in a Linux environment.
In a rare scenario, the configuration file may become read only and prevent you from saving the configuration changes using Command Line Interface (CLI) and Graphical User Interface (GUI). The impact is momentary and the file system tries to recover itself in most of such cases. In more persistent scenarios, reload the Cisco Unified SIP Proxy to recover the configuration file, edit, and save the configuration.
Cisco Unified SIP Proxy Release 9.1.1 has the following restrictions:
No Support for SNMP Version 3 (SNMPv3).
Certain MIB objects in the Cisco Unified SIP Proxy MIB tree are not supported. For list of MIB objects that are not supported, see CLI Configuration Guide for Cisco Unified SIP Proxy Release 9.1.
There are no limitations in Cisco Unified SIP Proxy Release 9.1.2.
There are no limitations in Cisco Unified SIP Proxy Release 9.1.3.
The show sip tcp connections detail and show sip tls connections detail commands will not have the filter options available for the Cisco Unified SIP Proxy Release 9.1.4. For example, you cannot use “pipe - |” to filter the various connection details.
There are no limitations in Cisco Unified SIP Proxy Release 9.1.5.
There are no limitations in Cisco Unified SIP Proxy Release 9.1.6.
There are no limitations in Cisco Unified SIP Proxy Release 9.1.7.
There are no limitations in Cisco Unified SIP Proxy Release 9.1.8.
There are no limitations in Cisco Unified SIP Proxy Release 9.1.9.
Caveats describe unexpected behavior in Cisco Unified SIP Proxy Release 9.1.x. To see the caveats associated with Cisco Unified SIP Proxy Release 9.1.x, use the Bug Search Tool at: https://tools.cisco.com/bugsearch/search.
The following issues were resolved in Cisco Unified SIP Proxy Release 9.1.1.
CUSP 9.0 SNMP feature request
Warning message should be associated with CPU intensive debugs
Thread dump generation support for Cisco Unified SIP Proxy
Caveats Resolved in Release 9.1.2
The following issues were resolved in Cisco Unified SIP Proxy Release 9.1.2.
CUSP routing trigger sequences lost after reload
3xx response support and correct response for 380
JVM caching issue for domain name lookup
False element down notifications and thread leak
Thread leak with proactive options ping for TCP and UDP elements
CUSP retransmissions for 15 times (10 min) on a dead socket to VXML Gateway
Network create using GUI not loading defaults for TCP connection setup timeout
sip-wire-log is not capturing SIP messages on using TCP
Normalization of user portion using URI manipulation truncates SIP
Route table missing after reload
Web GUI - Inactivity timer configuration
CUSP 9.1 device does not provide the sysObjectID on snmpwalk
Note Though JVM level caching is removed as part of the caveat CSCuv79510, a non-configurable DNS look up caching of approximately 15 minutes is maintained at the OS level. For DNS cache look up at OS level, you can clear the cache using the command clear ip dns cache.
Caveats Resolved in Release 9.1.3
The following issues were resolved in Cisco Unified SIP Proxy Release 9.1.3.
CUSP does not retain Lite-Mode cps after reboot
CUSP shows trace size CLI defect
Evaluation period to be cleared when using SMART license in vCUSP 9.1.0
New CLI introduced to change file descriptor count
vCUSP 9.1.0 drops into evaluation mode even if SMART licensing is registered
Caveats Resolved in Release 9.1.4
The following issues were resolved in Cisco Unified SIP Proxy Release 9.1.4.
Serviceability changes for TCP/TLS connections
CUSP is silently discarding SIP messages on established TCP connections
Preemption of CLI "show sip tcp connection detail"
Caveats Resolved in Release 9.1.5
The following issues were resolved in Cisco Unified SIP Proxy Release 9.1.5.
Ping - 503 handling
Add support for Smart Software Manager Satellite for Smart Licensing
Evaluation of unified-sip-proxy for struts2-jakarta rce vulnerability
Display a given number of lines from the end of the log.
Send the output to another command.
Display the most recent entries in the log and keep updating them.
Displays the SIP TCP connections at the application level.
Displays the SIP TLS connections at the application level.
Displays the SIP TCP or TLS connections summary at the application level.
Displays the SIP TCP or TLS connections details at the application level.
NoteDetail option has impact on the CPU usage. Hence, it is recommended not to use this option during peak loads. Dumptofile is the recommended option.
Dumps all SIP TCP or TLS connection table logs to the trace.log file at “pfs://cusp/log/trace/” directory at the application level.
Cisco Unified SIP Proxy EXEC (cusp)
Cisco Unified SIP Proxy Version
This command was introduced.
This command was modified to include keywords: tls and tcp.
The SIP message log file rotates every 10 MB or every night and is located at pfs://cusp/log/sipmsg. The SIP peg-counting log file rotates every 10 MB or every night also and is located at pfs://cusp/log/pegcount.
You can use the dumptofile option to get details on the production systems. However, use the summary option to get the current information of the SIP TCP or TLS connections.
Note The show sip tcp connections detail and show sip tls connections detail commands will not have the filter options available for the Cisco Unified SIP Proxy Release 9.1.4. For example, you cannot use “pipe - |” to filter the various connection details.
The following example shows sample output from the show sip message log command:
se-10.0.0.0(cusp)# show sip message log
Request received at Wed, 19 Nov 2008 21:01:25,081 GMT on 192.168.20.101 on port 6060 from the Remote IP 192.168.20.25 on port 6080
The following example shows sample output from the show sip tcp connections detail command:
se-10.0.0.0(cusp)# show sip tcp connections detail
No of connections:166
Fetching connection information will have performance impact, it is recommend to choose the option of dumping the information to log file Do you want to continue? (yes/no) [no]: yes
Local IP Local Port Remote IP Remote Port
10.64.86.198 6061 10.105.34.180 63549
10.64.86.198 6061 10.105.34.180 63570
10.64.86.198 6061 10.105.34.180 63609
10.64.86.198 6061 10.105.34.180 63658
10.64.86.198 6061 10.105.34.180 63619
10.64.86.198 6061 10.105.34.180 63598
10.64.86.198 6061 10.105.34.180 63555
10.64.86.198 6061 10.105.34.180 63718
10.64.86.198 6061 10.105.34.180 63717
10.64.86.198 6061 10.105.34.180 63566
10.64.86.198 6061 10.105.34.180 63755
10.64.86.198 6061 10.105.34.180 63723
10.64.86.198 6061 10.105.34.180 63750
10.64.86.198 6061 10.105.34.180 63707
10.64.86.198 6061 10.105.34.180 63652
10.64.86.198 6061 10.105.34.180 63674
10.64.86.198 6061 10.105.34.180 63608
10.64.86.198 6061 10.105.34.180 63663
10.64.86.198 6061 10.105.34.180 63728
10.64.86.198 6061 10.105.34.180 63706
10.64.86.198 6061 10.105.34.180 63696
10.64.86.198 6061 10.105.34.180 63614
10.64.86.198 6061 10.105.34.180 63722
10.64.86.198 6061 10.105.34.180 63691
10.64.86.198 6061 10.105.34.180 63560
10.64.86.198 6061 10.105.34.180 63615
10.64.86.198 6061 10.105.34.180 63582
10.64.86.198 6061 10.105.34.180 63729
10.64.86.198 6061 10.105.34.180 63565
10.64.86.198 6061 10.105.34.180 63680
10.64.86.198 6061 10.105.34.180 63734
10.64.86.198 6061 10.105.34.180 63712
10.64.86.198 6061 10.105.34.180 63592
10.64.86.198 6061 10.105.34.180 63587
10.64.86.198 6061 10.105.34.180 63679
10.64.86.198 6061 10.105.34.180 63593
10.64.86.198 6061 10.105.34.180 63733
10.64.86.198 6061 10.105.34.180 63620
10.64.86.198 6061 10.105.34.180 63685
10.64.86.198 6061 10.105.34.180 63653
10.64.86.198 6061 10.105.34.180 63576
10.64.86.198 6061 10.105.34.180 63669
10.64.86.198 6061 10.105.34.180 63603
10.64.86.198 6061 10.105.34.180 63604
10.64.86.198 6061 10.105.34.180 63581
10.64.86.198 6061 10.105.34.180 63745
10.64.86.198 6061 10.105.34.180 63690
10.64.86.198 6061 10.105.34.180 63571
10.64.86.198 6061 10.105.34.180 63701
10.64.86.198 6061 10.105.34.180 63554
<<Enter for MORE>> [confirm]
The following example shows sample output from the show sip tls connections detail command:
se-10.0.0.0(cusp)# show sip tls connections detail
No of connections:412
Fetching connection information will have performance impact, it is recommended to choose the option of dumping the information to log file Do you want to continue? (yes/no) [no]: yes
Local IP Local Port Remote IP Remote Port
10.65.125.148 5061 10.105.34.180 48014
10.65.125.148 5061 10.105.34.180 48166
10.65.125.148 5061 10.106.3.105 15221
10.65.125.148 5061 10.105.34.180 48123
10.65.125.148 5061 10.106.3.105 15300
10.65.125.148 5061 10.64.86.70 43748
10.65.125.148 5061 10.105.34.180 48161
10.65.125.148 5061 10.106.3.105 15330
10.65.125.148 5061 10.64.86.70 43726
10.65.125.148 5061 10.106.3.105 15348
10.65.125.148 5061 10.106.3.105 15288
10.65.125.148 5061 10.105.34.180 48177
10.65.125.148 5061 10.105.34.180 48090
10.65.125.148 5061 10.64.86.70 43655
10.65.125.148 5061 10.64.86.70 43623
show tcp connections
To display the status of Transmission Control Protocol (TCP) connections, use the show tcp connections command in module EXEC mode.
show tcp connections [ summary ]
(Optional) Displays the summary statement for all the tcp connections for the Cisco Unified SIP Proxy module.
Cisco Unified SIP Proxy Version
This command was introduced.
The show tcp connections command displays detailed connection information at the operating system level. To obtain information at the application level, use the show sip tcp connections detail command.
The following example shows the current active tcp connections available on the operating system:
se-10-64-86-198# show tcp connections
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
To enable the use of ping-503 option to check whether the SIP application service in the remote server element is running or not, use the server-group sip ping-503 command in Cisco Unified SIP Proxy configuration mode. Cisco Unified SIP Proxy can identify the type of response from the remote server element and decrement the retry count if the response is 503. To restore the SIP ping 503 option to the default value, use the no form of this command.
server-group sip ping-503
no server-group sip ping-503
This command has no arguments or keywords.
Response 503 from any elements is treated as a successful response.
Use this command to identify whether the sip element is down or not. If the server-group sip ping-503 command is not configured, the 503 response is treated as successful response. If this command is configured, Cisco Unified SIP Proxy considers the 503 response as remote element down. Ping 503 mode must first exist before you can use the no command.
The following example enables the server group sip ping 503 command:
To display the smart agent version, use the show license smart agent-version command in module EXEC mode.
show license smart agent-version
This command has no arguments or keywords.
Module EXEC (>)
Cisco Unified SIP Proxy Version
This command was introduced.
The following example shows the smart agent version:
se-10-65-125-184# show license smart agent-version
SmartAgent Version: 1.3.4
show license smart summary
Displays the current state of the Cisco Unified SIP proxy licensing application.
show license smart udi
Displays the Unique Device Identifier (UDI) of Cisco Unified SIP Proxy.
show license smart status
Displays the current state of the licensing agent.
Migration to Cisco Unified SIP Proxy 9.1.x
You can migrate from existing Cisco Unified SIP Proxy 8.x releases to Cisco Unified SIP Proxy Release 9.1.x. However, the following are the limitations during the migration:
Cisco Unified SIP Proxy Release 9.1.x cannot be installed on SRE Module. You require a virtual machine on VMWare ESXi platform to install Cisco Unified SIP Proxy Release 9.1.x.
Existing Cisco Unified SIP Proxy 8.x SWIFT licenses cannot be migrated to Cisco Unified SIP Proxy 9.1.x. Contact Cisco sales to enquire about the purchase of current Cisco Unified SIP Proxy licenses.
The backup configuration files from Cisco Unified SIP Proxy 8.x release does not have network related configuration as Cisco SRE module gets the relevant information through RBCP protocol from the host router when it powers up. Cisco Unified SIP Proxy 9.1.x does not support RBCP communication. So, if a backup configuration from Cisco Unified SIP Proxy 8.5.x release is restored in Cisco Unified SIP Proxy 9.1.x, you must manually enter and configure the IP address, subnet mask, and gateway details during reload.
Cisco Unified SIP Proxy 8.x release configuration has multiple sub-interfaces. The sub-interface format in Cisco Unified SIP Proxy Release 9.1.x is different from that in Cisco Unified SIP Proxy Release 8.x. You must configure these interfaces manually after the reload is complete.
Listen points are not restored if the IP address of the Cisco Unified SIP Proxy on SRE module and Cisco Unified SIP Proxy 9.1.x are different. You must manually configure the listen points.
To migrate from any of the existing Cisco Unified SIP Proxy Releases to Cisco Unified SIP Proxy Release 9.1.x, follow the below steps:
Note Smart licensing details are reset if smart licensing is configured before restore of configuration. It is always recommended to restore the configuration before enabling smart licensing.
Note After configuration restore, you must manually create a user with administrator privileges for accessing SSH.
Note When you migrate from Cisco Unified SIP Proxy Release 8.x to Cisco Unified SIP Proxy Release 9.1.x, if there are no Sub-Interfaces or VLANs defined on the Virtual Machine, remove the VLAN 0 tag from packets at the ESXi switch side or network side. If not, packets with VLAN 0 tag are dropped.
Table 1-1 lists the documentation available for Cisco Unified SIP Proxy Release 9.1.x:
Table 1-1 Related Documentation
Installation Guide for Cisco Unified SIP Proxy Release 9.1.x
Describes how to install the Cisco Unified SIP Proxy software, including licenses. Also includes information about moving from Release 1.x to Release 9.1.x.
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 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.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1721R)
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.