Release Notes for Cisco Unified SIP Proxy Release 10.1

Virtual Machine Requirements for Cisco Unified SIP Proxy 10.1

Cisco Unified SIP Proxy Release 10.1 software is packaged as an OVA and requires VMware ESXi 5.5 and above. Table 1 provides the information on hardware recommendation for virtualized Cisco Unified SIP Proxy. For more information about deployment and configuration, refer Installation Guide for Cisco Unified SIP Proxy Release 10.1.

Note CPU speed is greater than or equal to 2.99 GHz

Note CPU speed is less than 2.99 GHz.

Caution Changing the default log file size impacts the performance of Cisco Unified SIP Proxy.

---

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

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

File Packages for Cisco Unified SIP Proxy Release 10.1

The following package is available for Cisco Unified SIP Proxy Release 10.1:

• cusp-k9.vmw.10.1.0.ova

Cisco Smart Software License

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 refer to GUI Configuration Guide for Cisco Unified SIP Proxy Release 10.1 and CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.1.

Open Source Licensing

Some components of the software created for Cisco Unified SIP Proxy Release 10.1 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.

New Features and Enhancements for Cisco Unified SIP Proxy Release 10.1

The following features and enhancements are introduced in Cisco Unified SIP Proxy Release 10.1:

• HTTPS is enabled by default. You need not manually generate a crypto key and pass it to the web session security to enable HTTPS. However, you should be able to import a signed certificate that you generated externally, and update the web session with this new key label. The command no web session security keylabel labelname is disabled. Therefore all the HTTP requests will be redirected to HTTPS. Only the latest connection is retained and the remaining connections are logged out.
• Smart Agent is upgraded to latest version 3.0.9.

New and Modified CLI Commands in Cisco Unified SIP Proxy Release 10.1

The following command is modified in Cisco Unified SIP Proxy Release 10.1:

• no web session security keylabel labelname— This command is disabled. The following sample output indicates the behavior of Cisco Unified SIP Proxy Release 10.1 when trying to run the command no web session security keylabel labelname.

Migration from Cisco Unified SIP Proxy 8.x

You can migrate from existing Cisco Unified SIP Proxy 8.x releases to Cisco Unified SIP Proxy Release 10.1. However, the following are the limitations during the migration:

• Cisco Unified SIP Proxy Release 10.1 cannot be installed on SRE Module. You require VMWare ESXi platform to install Cisco Unified SIP Proxy Release 10.1.
• Existing Cisco Unified SIP Proxy 8.x SWIFT licenses cannot be migrated to Cisco Unified SIP Proxy 10.1.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.1 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.1, you must manually enter and configure the IP address, subnet mask, and default gateway details during the reload as follows:

a. Ensure that you have console access to the VM of virtual Cisco Unified SIP Proxy 10.1, while you are restoring the configuration of 8.X on 10.1.

b. After the restore is completed, reload the module as per the instructions on the screen.

c. Immediately after the reboot is completed, access the console with your username and password.

d. Configure the IP address, subnet mask, and default gateway as follows:

e. After the Cisco Unified SIP Proxy is online, re-associate the users to groups with password reset and try to ssh.

• Cisco Unified SIP Proxy 8.x release configuration has multiple sub-interfaces. The sub-interface format in Cisco Unified SIP Proxy Release 10.1 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.1 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.1:

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.

2. Deploy the Cisco Unified SIP Proxy Release 10.1 OVA on a virtual machine. For more information, see Cisco Unified SIP Proxy 10.1 Installation Guide.

3. Configure the Smart licenses. For more information, see GUI Configuration Guide for Cisco Unified SIP Proxy Release 10.1 and CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.1.

4. Restore the configuration backup of Cisco Unified SIP Proxy 8.x in Cisco Unified SIP Proxy 10.1. For more information, see CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.1.

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.1, 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.1. Following are the steps to migrate from any of the existing Cisco Unified SIP Proxy Releases to Cisco Unified SIP Proxy Release 10.1:

1. Copy the running configuration to the startup configuration.

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

3. Deploy the Cisco Unified SIP Proxy Release 10.1 OVA on the virtual machine. For more information, see Cisco Unified SIP Proxy 10.1 Installation Guide for more information.

4. Configure the Smart licenses. For more information, see GUI Configuration Guide for Cisco Unified SIP Proxy Release 10.1 and CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.1.

5. Restore the configuration backup of Cisco Unified SIP Proxy 9.x in Cisco Unified SIP Proxy 10.1. For more information, see CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.1.

6. Reset the password for all the restored users (administrators, pfs-privusers, and pfs-readonly). Follow the steps mentioned under the section “Changing your password” in the chapter “Configuring Users” in GUI Configuration Guide for Cisco Unified SIP Proxy Release 10.1.

7. Re-associate the restored users to the corresponding groups. Follow the steps mentioned under the section “Displaying or Changing Group Subscriptions” in the chapter “Configuring Users” in GUI Configuration Guide for Cisco Unified SIP Proxy Release 10.1.

Migration from Cisco Unified SIP Proxy 10.0.x

You can upgrade from the existing Cisco Unified SIP Proxy 10.0.x releases to Cisco Unified SIP Proxy Release 10.1. Following are the steps to migrate from any of the existing Cisco Unified SIP Proxy Releases to Cisco Unified SIP Proxy Release 10.1:

1. Copy the running configuration to the startup configuration.

2. Take a backup of the existing Cisco Unified SIP Proxy 10.0.x configuration. For more information, see CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.0.

3. Deploy the Cisco Unified SIP Proxy Release 10.1 OVA on the virtual machine. For more information, see Cisco Unified SIP Proxy 10.1 Installation Guide for more information.

4. Configure the Smart licenses. For more information, see GUI Configuration Guide for Cisco Unified SIP Proxy Release 10.1 and CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.1.

5. Restore the configuration backup of Cisco Unified SIP Proxy 10.0.x in Cisco Unified SIP Proxy 10.1. For more information, see CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.1.

6. Reset the password for all the restored users (administrators, pfs-privusers, and pfs-readonly). Follow the steps mentioned under the section “Changing your password” in the chapter “Configuring Users” in GUI Configuration Guide for Cisco Unified SIP Proxy Release 10.1.

7. Re-associate the restored users to the corresponding groups. Follow the steps mentioned under the section “Displaying or Changing Group Subscriptions” in the chapter “Configuring Users” in GUI Configuration Guide for Cisco Unified SIP Proxy Release 10.1.

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.

Copyright © 2020, Cisco Systems, Inc. All rights reserved.