Release Notes for Cisco Unified SIP Proxy Release 10.2.3
Available Languages
Virtual Machine Requirements for Cisco Unified SIP Proxy 10.2.x:
Determining the Software Version
File Packages for Cisco Unified SIP Proxy Release 10.2.x
New and Modified CLI Commands in Cisco Unified SIP Proxy Release 10.2
Caveates Resolved in 10.2.1_v1
Caveates Resolved in 10.2.1_v2
Caveates Resolved in 10.2.1_v3
Migration to Cisco Unified SIP Proxy 10.2.x
Migration from Cisco Unified SIP Proxy 8.x
Migration from Cisco Unified SIP Proxy 9.x
Migration from Cisco Unified SIP Proxy 10.x
This document describes the new features, system requirements, licensing information, and caveats for Cisco Unified SIProxy Release 10.2.x. Use this document in conjunction with the caveats listed in Caveats
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 10.2.x is delivered as an Open Virtual Appliance (OVA) and can be installed as a virtual machine on VMware ESXi platform. For more information on virtual machine requirements to install Cisco Unified SIP Proxy Release 10.2.x, see Virtual Machine Requirements for Cisco Unified SIP Proxy 10.2 Cisco Unified SIP Proxy Release 10.2.x supports CISCO-USP-MIB through SNMP.
· Virtual Machine Requirements for Cisco Unified SIP Proxy 10.2.x
· Determining the Software Version
· File Packages for Cisco Unified SIP Proxy Release 10.2.x
Virtual Machine Requirements for Cisco Unified SIP Proxy 10.2.x:
Cisco Unified SIP Proxy Release 10.2.x software is packaged as an OVA. Refer to the table Compatibility Matrix for compatibility of VMware ESXi with CUSP release.
The table Virtual Machine Requirements for UCS Platform provides the information on hardware recommendation for virtualized Cisco Unified SIP Proxy.
Note: Since VMware has declared end of general support for VMware ESXi version 6.0 and below, we recommend vCUSP 10.2.x users to migrate to ESXi version 6.5 or above.
Compatibility Matrix
| CUSP Release |
VMware ESXI Release |
| 10.2.0 |
5.5 and above |
| 10.2.1 |
6.5 and above |
| 10.2.2 |
6.5 and above |
| 10.2.3 |
6.5 and above |
For more information about deployment and configuration, see Installation Guide for Cisco Unified SIP Proxy Release 10.2.
Virtual Machine Requirements for UCS Platform
| 60 CPS |
100 CPS |
200 CPS |
300 CPS |
400 CPS |
|
| vCPU |
1 |
2 |
4 |
4 |
4 |
| RAM |
6 GB |
6 GB |
6 GB |
6 GB |
6 GB |
| DISK |
80 GB |
80 GB |
80 GB |
80 GB |
80GB |
Note: CPU speed is greater than or equal to 2.99 GHz.
Virtual Machine Requirements for Low Speed Cisco UCS and Cisco UCS (E) Platforms
| CPS |
60 CPS |
100 CPS |
200 CPS |
300 CPS |
400 CPS |
| vCPU |
1 |
2 |
4 |
4 |
4 |
| RAM |
6 GB |
6 GB |
6 GB |
6 GB |
6 GB |
| DISK |
80 GB |
80 GB |
80 GB |
80 GB |
80GB |
Note :
· CPU speed is greater than or equal to 2.99 GHz.
· Changing the default log file size impacts the performance of Cisco Unified SIP Proxy.
· Over subscription of hardware by virtual machines running on hypervisor is not supported.
Determining the Software Version
To determine the software version and the license used, perform the following steps:
Step 1:
Enter the following command to display the Cisco Unified SIP Proxy software version:
show software versions
Step 2 :
Enter the following command to display the Cisco Unified SIP Proxy software license:
show license smart summary
File Packages for Cisco Unified SIP Proxy Release 10.2.x
The following package is available for Cisco Unified SIP Proxy Release 10.2.x:
· cusp-k9.vmw.10.2.0.ova
The following package is available for Cisco Unified SIP Proxy Release 10.2.1:
· cusp-k9.vmw.10.2.1.ova
The following package is available for Cisco Unified SIP Proxy Release 10.2.1_v1:
· vCUSP_10.2.1_v1.cop.sha512
Note: Ensure to follow the installation steps from the README file that is available with the vCUSP_10.2.1_v1.cop.sha512 patch.
The following package is available for Cisco Unified SIP Proxy Release 10.2.1_v2:
· vCUSP_10.2.1_v2.cop.sha512
Note: Ensure to follow the installation steps from the README file that is available with the vCUSP_10.2.1_v2.cop.sha512 patch.
The following package is available for Cisco Unified SIP Proxy Release 10.2.1_v3:
· vCUSP_10.2.1_v3.cop.sha512
Note:
· Each successive patch includes all of the updates from previous patches for this release.
· Ensure to follow the installation steps from the README file that is available with the vCUSP_10.2.1_v3.cop.sha512 patch.
The following package is available for Cisco Unified SIP Proxy Release 10.2.2:
· cusp-k9.vmw.10.2.2.ova
The following package is available for Cisco Unified SIP Proxy Release 10.2.3:
· cusp-k9.vmw.10.2.3.ova
· Cisco Smart Software License
· Open Source Licensing
Cisco Smart Software Licensing is a standardized licensing platform that facilitates you to deploy and manage Cisco software licenses easily and quickly. Cisco Smart Software Licensing establishes a pool of software licenses that can be used across your network in a flexible and automated manner. It also provides visibility to your purchased and deployed licenses in your network. Cisco Smart Software Licensing removes the need for Product Activation Keys (PAKs) and reduces your license activation and registration time.
For more information on configuring smart licensing using GUI and CLI, see GUI Administration Guide for Cisco Unified SIP Proxy Release 10.2 and CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.2.
Some components of the software created for Cisco Unified SIP Proxy Release 10.2.x are provided through open source or commercial licensing. These components and the associated copyright statements can be found at:
https://www.cisco.com/c/en/us/about/legal/open-source-documentation-responsive.html.
· Release 10.2
The following features and enhancements are introduced in Cisco Unified SIP Proxy Release 10.2.x:
· Patch Upgrade—You can install a patch file on an existing major release version of Cisco Unified SIP Proxy starting with Cisco Unified SIP Proxy Release 10.2.x. This helps you upgrade to a newer patch version of the Cisco Unified SIP Proxy within the same major release version without any modifications to your existing virtual machine. For example, you can upgrade from Cisco Unified SIP Proxy Release 10.2.x to Cisco Unified SIP Proxy Release 10.2.1_v1 or Cisco Unified SIP Proxy Release 10.2.1_v1 to Cisco Unified SIP Proxy Release 10.2.1_v2.
For detailed information on patch upgrade, see Installation Guide for Cisco Unified SIP Proxy Release 10.2. For details on installing patch using CLI, see CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.2. For details on installing patch using GUI, see GUI Administration Guide for Cisco Unified SIP Proxy Release 10.2.
· Updates to minimum password length and password policy—Passwords should be at least 8 to 64 alphanumeric characters in length. However, there is no limit on the maximum length of the password. The administrator has the privileges to provision a user with password length that is higher than the minimum length. For example, a user can have password of length 65 alphanumeric characters.
· SFTP File Transfer— The Cisco Unified SIP Proxy now uses Secure File Transfer Protocol (SFTP) for transferring device configuration and templates to and from external networks. Functions such as patch upgrade, back up and restore, upload and copy of system configuration files and logs between CUSP server and external servers are performed only through secured FTP. Please note that FTP is deprecated from release 10.2.x.
· GUI SIP Logging - As a general guideline enabling the SIP message logging feature can have a significant performance impact on your system. Cisco advises not to enable it for extended periods and recommends using SIP CLI logging instead.
Cisco Unified SIP Proxy Release 10.2.3 onwards, while enabling GUI SIP logging, a prompt will appear stating Enabling SIP Logging will impact performance of CUSP Do you want to continue?- If all system resources are in good condition(CPU, Disk Space & Memory), GUI SIP logging can be enabled.
However, if any of the system resources are insufficient, a warning prompt will appear stating System Resources are not at good state to proceed this action!!. The same is applicable for Failed Calls Log as well.
Note:
· Cisco Unified SIP Proxy Release 10.2.3 onwards, to facilitate GUI SIP logging, the application performs validations to assess system resources (CPU, Disk space, Memory Utilizations) and If any one of these metrics goes beyond the threshold value, GUI SIP Logging cannot be enabled.
· If GUI sip logging enabling fails because of high memory utilization metric, it could also be a false alarm attributed by Linux Operating System Memory management design which allows buffer and cache component to grow until total utilization reaches 97-98%. it may indirectly cause Total Memory Utilization metric to spike and may prevent a user to leverage GUI SIP Logging. Total Memory utilization metric here also includes memory used by Buffer & Cache, which is under Operating System purview and not CUSP application.
· In such cases, it is recommended to continue using SIP logging via CLI. Additionally, Admin is advised to monitor CUSP application-specific Active Memory (via “show memory” command in EXEC mode) instead to ensure it doesn't keep growing and exceeds a certain threshold. Active Memory provides a more accurate CUSP centric memory utilization metric to monitor.
· If an Admin has a strong dependency over GUI SIP Logging, or the CUSP centric Active Memory metric continues to grow beyond a certain threshold (seen via “show memory” command in EXEC mode), it is advised to work with Cisco Support to evaluate and vet CUSP’s system health and overall resource utilizations.
New and Modified CLI Commands in Cisco Unified SIP Proxy Release 10.2
The following new commands are introduced in Cisco Unified SIP Proxy Release 10.2:
· software download url<url> username<username> password<password>
· software upgrade
For more details on these commands, see the Module Commands for Cisco Unified SIP Proxy section of the CLI Command Reference for Cisco Unified SIP Proxy Release 10.2.
New CLI Commands in Cisco Unified SIP Proxy Release 10.2.2 release
The following new commands are introduced in Cisco Unified SIP Proxy Release 10.2.2 and are applicable only for 10.2.2 version and above:
· show cpu-usage history[60-minutes | 60-seconds | 72-hours]
· show cps history[60-minutes | 72-hours]
· show memory-usage history[60-minutes | 60-seconds | 72-hours]
· show 5-minutes cps-history72-hours
· show disk-usage
New CLI Commands in Cisco Unified SIP Proxy Release 10.2.3 release
The following new commands are introduced in Cisco Unified SIP Proxy Release 10.2.3 and are applicable only for 10.2.3 version and above:
· clear tomcat-log
· show sip peg-count log
· show sip peg-count log <number of lines>
Ex: show sip peg-count log 40.
clear tomcat-log
To remove rotated tomcat log files (catalina.out-timestamp), use the clear tomcat-log command in Cisco Unified SIP Proxy configuration EXEC mode.
clear tomcat-log
Syntax Description
This command has only keywords and no arguments.
Command Modes
Module EXEC
Usage Guidelines
Use this command to remove rotated tomcat log files (catalina.out-timestamp) when the disk utilization is greater than 80%, in order to keep the system disk utilization under control. If disk utilization is less than 80%, rotated tomcat log files cannot be removed from the system.
The following examples show the clearing of rotated tomcat log files.
Scenario 1: Below example is applicable if disk utilization is greater than 80%.
se-10-0-0-0# clear tomcat-log
!!!WARNING!!!:Before clearing the log files , it is recommended to take back up of rotated tomcat log files from SFTP Server if not taken!!
Those log files are necessary for troubleshooting!!!
Are you sure you want to clear rotated tomcat log files?[confirm]y
Successfully removed rotated tomcat log files
Scenario 2: Below example is applicable if the disk utilization is less than 80% and rotated tomcat log files can’t be removed in this scenario from the system.
se-10-0-0-0# clear tomcat-log
Disk Utilization is 5%
Rotated Tomcat log files can not be removed if disk utilization is less than 80%
show sip peg-count log
To display SIP peg-counting log, use the show sip peg-count log command in module CUSP mode
show sip peg-count log
Syntax Description
This command has only keywords and no arguments.
Command Modes
Module CUSP
Usage Guidelines
The SIP peg-counting log file rotates every 10 MB or every night also and is located at pfs://cusp/log/pegcount.
The following example shows sample output from the show sip peg-count log command:
se-10-0-0-0(cusp)# show sip peg-count log
| Mon, 13 Mar 2023 15:01:03,096 IST |
||||||||
|
|
Delta In Initial |
Delta Out Initial |
Delta In Retrans |
Delta Out Retrans |
Total In Initial |
Total Out Initial |
Total In Retrans |
Total Out Retrans |
| Message |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| INVITE |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| ACK |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| CANCEL |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| BYE |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| OPTIONS |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| REGISTER |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| SUBSCRIBE |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| NOTIFY |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| PRACK |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| REFER |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| UPDATE |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| PUBLISH |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| INFO |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| 100 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| 180 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| 181 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| 182 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| 183 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| 485 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| 200 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
show sip peg-count log <number of lines >
To display SIP peg-counting log with number of lines to be printed, use the show sip peg-count log <number> command in module CUSP mode.
show sip peg-count log 30
Syntax Description
This command has only keywords and no arguments.
Command Modes
Module CUSP
The following example shows sample output from the show sip peg-count log 20 command:
se-10-0-0-0(cusp)# show sip peg-count log 20
| Mon, 13 Mar 2023 15:01:03,096 IST |
||||||||
|
|
Delta In Initial |
Delta Out Initial |
Delta In Retrans |
Delta Out Retrans |
Total In Initial |
Total Out Initial |
Total In Retrans |
Total Out Retrans |
| Message |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| INVITE |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| ACK |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| CANCEL |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| BYE |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| OPTIONS |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| REGISTER |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| SUBSCRIBE |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| NOTIFY |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| PRACK |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| REFER |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| UPDATE |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| PUBLISH |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| INFO |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| 100 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| 180 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| 181 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
| 182 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
Modified CLI Commands in Cisco Unified SIP Proxy Release 10.2.3 release
The following commands are no longer available in Cisco Unified SIP Proxy Release 10.2.3 and are applicable only for 10.2.2 version and below:
· show sip peg-counting log <number of lines>
Limitations and Restrictions
Cisco Unified SIP Proxy Release 10.2 has the following restrictions:
· Changing the default log file size impacts the performance of Cisco Unified SIP Proxy.
· High availability of Cisco Unified SIP Proxy virtual machine on both Cisco UCS and Cisco UCS-E platform is not supported.
· Cisco Unified SIP Proxy Release 10.2 does not support installation of VMware Tools or any 3rd party tools in a Linux environment.
· Configuring Fast Ethernet 02 Interface is not supported.
· From Cisco Unified SIP Proxy Release 10.0 onwards, the directory structure presented to the FTP users is changed. As a result, importing route table from an XML file will not work. We recommend users to utilize the Add Route function in the vCUSP GUI for this purpose.
Caveats
Caveats describe unexpected behavior in Cisco Unified SIP Proxy Release 10.2.x. To see the caveats associated with Cisco Unified SIP Proxy Release 10.2.x, use the Bug Search Tool at: https://tools.cisco.com/bugsearch/search.
The following issues were resolved in Cisco Unified SIP Proxy Release 10.2:
| Caveat |
Description |
| CSCvt27743 |
Evaluation of unified-sip-proxy for Apache Tomcat Ghostcat vulnerability |
| CSCvr40548 |
CIAM Alerts on BIND component |
| CSCvs28900 |
Super thread crash due to memory leak caused by DNS Java |
| CSCvs48121 |
User cannot SSH into CUSP after the user is assigned for FTP access and removed from same |
| CSCvs54756 |
Timezone is not updated on changing Country in Time Zone Settings GUI page |
| CSCvs79888 |
Changing the CUSP to LITE mode for CUSP 10.0 is not available |
| CSCvs88460 |
CUSP 10.1 login not working via RADIUS |
| CSCvt45242 |
CUSP 10.0 and 10.1 SIP logs show GMT time zone instead of local time zone synched from NTP server |
| CSCvt76985 |
Missing Trace Log File header in 10.x version |
| CSCvu40336 |
Multiple Vulnerabilities in bind |
| CSCvu47993 |
vCUSP 10.1: Post reload ping/SSH/GUI stop working until CLI is accessed through ESXi console |
| CSCvs65917 |
Restore operation does not work when only 1 entry is present in the table |
| CSCvs77007 |
Domain Name Config in Setup Wizard not taking effect |
| CSCvs78604 |
Cannot clear the trace log file from the CUSP GUI interface |
| CSCvs78774 |
Enable Tracing triggers when you clear tracelogs from CLI |
| CSCvi81740 |
vCUSP JConsole access |
| CSCvq02490 |
vCUSP should support SFTP for all file transfers along with backup and restore |
| CSCvt53483 |
Enable kdump configuration in vCUSP 10.1 |
| CSCvq48163 |
Checkboxes in CUSP UI not functioning correctly on Firefox 63.0.3 and newer versions |
The following are the open caveats for Cisco Unified SIP Proxy Release 10.2:
| Caveat |
Description |
| CSCvu13653 |
Multiple vulnerabilities in OpenLDAP |
| CSCvv03282 |
Getting bad request while clearing 100 calls from the failed call search list |
| CSCvv23379 |
Guest OS and ESXi compatibility are showing older version for CUSP 10.2 |
| CSCvv23410 |
CUSP online help should be updated with the correct steps for configuring the backup parameters |
The following issues were resolved in Cisco Unified SIP Proxy Release 10.2.1:
| Caveat |
Description |
| CSCvu13653 |
Multiple vulnerabilities in OpenLDAP |
| CSCvv03282 |
Getting bad request while clearing 100 calls from the failed call search list |
| CSCvv23379 |
Guest OS and ESXi compatibility are showing older version for CUSP 10.2 |
| CSCvv23410 |
CUSP online help should be updated with the correct steps for configuring the backup parameters |
| CSCvv87871 |
CUSP 10.2 unable to subscribe users as member to non-default (new) groups |
Caveates Resolved in 10.2.1_v1
The following issues were resolved in Cisco Unified SIP Proxy Release 10.2.1_v1:
| Caveat |
Description |
| CSCvx70719 |
Restore on CUSP 10.2.1 is failing |
| CSCvw86510 |
License Disable after Network Connectivity failure |
| CSCvx61008 |
CUSP 10.2 restricting Certificate validity between 2-5 years |
| CSCvx72402 |
User is logged out automatically upon a configuration change in the Pre-Normalization section |
| CSCvx72443 |
CUSP: Pages become inaccessible with 500 Internal Sever Error after changing Inactivity Timer |
| CSCvy58640 |
Terminal Length command no longer available on vCUSP V10 |
| CSCvs47162 |
Tomcat and messages logs rotation issues in vCUSP |
| CSCvw79158 |
No alert is shown to user/administrator, when an incorrect path is selected for upgrade or patch |
Caveates Resolved in 10.2.1_v2
The following issues were resolved in Cisco Unified SIP Proxy Release 10.2.1_v2:
In addition to the caveats resolved in Cisco Unified SIP Proxy 10.2.1_v1, the following issue was resolved in Cisco Unified SIP Proxy Release 10.2.1_v2:
| Caveat |
Description |
| Evaluation of Cisco Unified SIP Proxy for Log4jRCE(Log4Shell) Vulnerability |
Caveates Resolved in 10.2.1_v3
The following issues were resolved in Cisco Unified SIP Proxy Release 10.2.1_v3:
| Caveat |
Description |
| QuoVadis Root Certificate Decommission on Cisco Unified SIP Proxy release |
The following issues were resolved in Cisco Unified SIP Proxy Release 10.2.2:
| Caveat |
Description |
| CSCwa39323 |
OVA File only allocates 4GB of RAM instead of 6 GB |
| CSCwb39228 |
CUSP - Apache Tomcat NIO+OpenSSL vulnerability CVE-2021-41079 in tomcat 8.5.56 |
| CSCwb28821 |
In BIND 9.8.5 - > 9.8.8, 9.9.3 - > 9.11.29, 9.12.0 - > 9.16.13, and above versions |
| CSCwb67440 |
After restore from backup install user admin on newly created CUSP will become hidden |
| CSCwb76531 |
Cisco Unified SIP Proxy RMI Registry Bypass |
| CSCwa18667 |
Issue with cusp webpage after configuring time policy |
| CSCwb06998 |
Patch install failing: vCUSP_10.2.1_v2 |
| CSCvt77007 |
vCUSP10.x: Make Tech Support from GUI provide same information as "show tech-support" from CLI |
| CSCvv42008 |
Accessing Pre or Post Normalization in CUSP GUI gives 404 Not Found or refused to connect |
| CSCvy96653 |
The pre existing log entries are being flushed out , when patch installation is triggered from CLI |
| CSCvy99857 |
Patch installation with version 10 on a 10.2.1 vCUSP from CLI is getting failed |
The following issues were resolved in Cisco Unified SIP Proxy Release 10.2.3:
| Caveat |
Description |
| CSCwc74711 |
Remove Apache Tomcat Default Files |
| CSCwe10080 |
CLI hung issue due to File Descriptors getting exhausted |
| CSCwd82505 |
Digicert certificate expiration in CUSP 10.2.2 |
| CSCwd75313 |
Enabling SIP logging via GUI will cause tomcat/Catalina logs to consume disk space |
| CSCwe02034 |
Upgrade Smart Agent Version to 3.1.17 |
| CSCwe02041 |
Upgrade of log4j version to v2.17 |
| CSCwd32043 |
In ISC DHCP 1.0 -> 4.4.3, ISC DHCP 4.1-ESV-R1 -> 4.1-ESV-R16-P1 a sy ... |
| CSCwe52162 |
Nexpose scanner catching old vulnerability CVE-2015-4000 |
Migration to Cisco Unified SIP Proxy 10.2.x
Note: Data and configuration from an earlier release must be restored from an SFTP server using the absolute path to the backup files. For more details on how to configure the backup server, see Backup and Restore Data section of the CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.2
Migration from Cisco Unified SIP Proxy 8.x
You can migrate from an existing Cisco Unified SIP Proxy 8.x releases to Cisco Unified SIP Proxy Release 10.2. However, the following are the limitations during the migration:
· Cisco Unified SIP Proxy Release 10.2 cannot be installed on SRE Module. You require VMWare ESXi platform to install Cisco Unified SIP Proxy Release 10.2.x.
· Existing Cisco Unified SIP Proxy 8.x SWIFT licenses cannot be migrated to Cisco Unified SIP Proxy 10.2.x. Contact your Cisco partner or reseller to enquire about the purchase of current licensing.
· The backup configuration files from Cisco Unified SIP Proxy 8.x release do not have the network-related configuration as the Cisco SRE module gets the relevant information through RBCP protocol from the host router when it powers up. Cisco Unified SIP Proxy 10.2.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 10.2.x, you must manually enter and configure the IP address, subnet mask, and default gateway details during the reload as follows:
o Ensure that you have console access to the VM of virtual Cisco Unified SIP Proxy 10.2.x, while you are restoring the configuration of 8.x on 10.2.x.
o After the restore is completed, reload the module as per the instructions on the screen.
o Immediately after the reboot is completed, access the console with your username and password.
o Configure the IP address, subnet mask, and default gateway as follows:
cusp#configure terminal
Enter configuration command, one per line. End with CNTL/Z.
cusp(config)#interface FastEthernet 0
cusp(config-interface)#ip address 10.65.125.187 255.255.255.128
cusp(config)#ip default-gateway 10.65.125.129
SYSTEM ONLINE
cusp(config)#exit
cusp#wr mem
· After the Cisco Unified SIP Proxy is online, re-associate the users to groups with password reset and test remote access using SSH.
cusp#configure terminal
cusp#username cisco group Administrators
cusp#username cisco password cisco
cusp#wr mem
· Cisco Unified SIP Proxy 8.x release configuration has multiple sub-interfaces. The sub-interface format in Cisco Unified SIP Proxy Release 10.2.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 as it requires the IP address of the virtual Cisco Unified SIP Proxy. So, you must manually configure the listen points after restoring the back up from the Cisco Unified SIP Proxy 8.x release.
· SIP Ping configuration is not restored as it requires the IP address of the virtual Cisco Unified SIP Proxy. So, you must manually configure SIP Ping configuration on Cisco Unified SIP Proxy 10.2.x release after restoring the backup from the Cisco Unified SIP Proxy 8.x release.
Following are the steps to migrate from any of the existing Cisco Unified SIP Proxy Releases to Cisco Unified SIP Proxy Release 10.2.x:
Step 1:
Take a backup of the existing Cisco Unified SIP Proxy 8.x configuration. For more information, see CLI Configuration Guide for Cisco Unified SIP Proxy CLI Release 8.5 or GUI Administration Guide for Cisco Unified SIP Proxy Release 8.5.
Step 2:
Deploy the Cisco Unified SIP Proxy Release 10.2.x OVA on a virtual machine. For more information, see Cisco Unified SIP Proxy 10.2 Installation Guide.
Step 3:
Configure the Smart licenses. For more information, see GUI Administration Guide for Cisco Unified SIP Proxy Release 10.2 and CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.2.
Step 4:
Restore the configuration backup of Cisco Unified SIP Proxy 8.x in Cisco Unified SIP Proxy 10.2.x. For more information, see CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.2 and GUI Administration Guide for Cisco Unified SIP Proxy Release 10.2.
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: When you migrate from Cisco Unified SIP Proxy Release 8.x to Cisco Unified SIP Proxy Release 10.2.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.
Migration from Cisco Unified SIP Proxy 9.x
You can upgrade from the existing Cisco Unified SIP Proxy 9.x releases to Cisco Unified SIP Proxy Release 10.2.x. Following are the steps to migrate from any of the existing Cisco Unified SIP Proxy Releases to Cisco Unified SIP Proxy Release 10.2.x:
Step 1:
Copy the running configuration to the startup configuration. For more information, see “Maintaining the Cisco Unified SIP Proxy System” chapter in CLI Configuration Guide for Cisco Unified SIP Proxy Release 9.x.
Step 2:
Unregister CUSP 9.x from CSSM if you are using Smart Licensing.
Step 3:
Take a backup of the existing Cisco Unified SIP Proxy 9.x configuration. For more information, see CLI Configuration Guide for Cisco Unified SIP Proxy Release 9.x CLI Configuration Guide for Cisco Unified SIP Proxy Release 9.x and GUI Administration Guide for Cisco Unified SIP Proxy Release 9.x.
Step 4:
Deploy the Cisco Unified SIP Proxy Release 10.2 OVA on the virtual machine. For more information, see Cisco Unified SIP Proxy 10.2 Installation Guide for more information.
Step 5:
Configure the Smart licenses. For more information, see CLI Configuration Guide for Cisco Unified SIP Proxy Release 9.x and GUI Administration Guide for Cisco Unified SIP Proxy Release 9.x.
Step 6:
Restore the configuration backup of Cisco Unified SIP Proxy 9.x in Cisco Unified SIP Proxy 10.2. For more information, see CLI Configuration Guide for Cisco Unified SIP Proxy Release 9.x and GUI Administration Guide for Cisco Unified SIP Proxy Release 9.x.
Step 7:
Reregister to CSSM.
Migration from Cisco Unified SIP Proxy 10.x
You can upgrade from the existing Cisco Unified SIP Proxy 10.x releases to Cisco Unified SIP Proxy Release 10.2.x. Following are the steps to migrate from any of the existing Cisco Unified SIP Proxy Releases to Cisco Unified SIP Proxy Release 10.2.x:
Step 1:
Copy the running configuration to the startup configuration. For more information, see “Maintaining the Cisco Unified SIP Proxy System” chapter in CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.x.
Step 2:
Unregister CUSP 10.x from CSSM if you are using Smart Licensing.
Step 3:
Take a backup of the existing Cisco Unified SIP Proxy 10.x configuration. For more information, see CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.x and GUI Administration Guide for Cisco Unified SIP Proxy Release 10.x.
Step 4:
Deploy the Cisco Unified SIP Proxy Release 10.2 OVA on the virtual machine. For more information, see Cisco Unified SIP Proxy 10.2 Installation Guide for more information.
Step 5:
Configure the Smart licenses. For more information, see GUI Administration Guide for Cisco Unified SIP Proxy Release 10.2 and CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.2.
Step 6:
Restore the configuration backup of Cisco Unified SIP Proxy 10.x.x in Cisco Unified SIP Proxy 10.2.x. For more information, see CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.2 and GUI Administration Guide for Cisco Unified SIP Proxy Release 10.2.
Step 7:
Reregister to CSSM.
The below table lists the documentation available for Cisco Unified SIP Proxy Release 10.2.x:
Related Documentation
| Document |
Description |
| Installation Guide for Cisco Unified SIP Proxy Release 10.2.x |
Describes how to install the Cisco Unified SIP Proxy software, including licenses. Also includes information about moving from Release 1.x to Release 10.2.x. http://www.cisco.com/en/US/products/ps10475/prod_installation_guides_list.html
|
| CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.2.x |
Contains administrator information, such as maintenance and troubleshooting, for tasks that are performed from the CLI. http://www.cisco.com/en/US/products/ps10475/products_installation_and_configuration_guides_list.html
|
| CLI Command Reference for Cisco Unified SIP Proxy Release 10.2.x |
Contains descriptions of all the Cisco Unified SIP Proxy Release 10.2.x-specific CLI commands. http://www.cisco.com/en/US/products/ps10475/prod_command_reference_list.html
|
| GUI Administration Guide for Cisco Unified SIP Proxy Release 10.2.x |
Contains administrator information, such as maintenance and troubleshooting, for tasks that are performed from the GUI. Includes online help. http://www.cisco.com/en/US/products/ps10475/products_installation_and_configuration_guides_list.html
|
| Commercial Open Source Information for Cisco Unified SIP Proxy Release 10.2.x |
Lists all the open source software used in this project. https://www.cisco.com/c/en/us/about/legal/open-source-documentation-responsive.html
|
Feedback