Cisco Unified SIP Proxy 9.0 on Virtual Machine Configuration

First Published: September 10, 2015

Introduction

This page provides configuration information for Cisco Unified SIP Proxy (Unified SIP Proxy) 9.0 on a Virtual Machine in a Cisco Unified Contact Center Enterprise (Unified CCE) environment.

The intended audience should be familiar with Cisco Collaboration products and be able to perform system-level configuration of Cisco Collaboration components and deployments.

The configuration information is based primarily on system testing performed on Unified CCE during Cisco Collaboration Systems Release 11.0(1).

This topic does not contain detailed step-by-step procedures. For detailed information about installing, configuring, and administering Unified CCE, Cisco Unified Customer Voice Portal (Unified CVP), Cisco Unified Communications Manager (Unified Communications Manager), Cisco Unified Communications Manager Session Management Edition (Unified CM SME), or Unified SIP Proxy refer to the respective product documentation.

Design

For information on design considerations and guidelines for deploying Unified SIP Proxy on a Virtual Machine in a Unified CCE environment:

Release Notes for Cisco Unified SIP Proxy Release 9.0

Topologies

This section provides information about Unified SIP Proxy on a Virtual Machine in a Unified CCE environment.

For information on specific deployments and sites where Unified SIP Proxy testing was performed, see Cisco Unified Contact Center Enterprise Test Bed for Collaboration Systems Release 11.0(1).

 

Figure 1. Collaboration Systems Release 11.0(1): Unified CCE Test Architecture

Component Deployment

Data Center A (PST time zone) and Data Center (EST time zone) are separated over WAN.

■        Unified CCE: Logger, Router, AW, and PG are installed in duplex mode on each of the data center across WAN

■        Unified CVP: six call servers + OAMP are distributed over WAN

■        Unified Communications Manager: 11 node cluster with dedicated nodes for MoH and TFTP, distributed across WAN

■        Unified CM SME: 4-node cluster distributed across WAN

■        Unified SIP Proxy: vCUSP 9.0 is deployed on UCS-B server on both the data centers.

Incoming calls are from IP (CUBE), PSTN customers, and enterprise callers. A service provider (SP) cloud provides a dedicated Unified Communications Manager cluster for SP endpoints. There is a separate Unified Communications Manager cluster with two nodes for enterprise caller scenarios.

 Call Flow

Automated regression and manual testing was executed on the following call flows.

■        Customer->CUBE->Unified SIP Proxy->Unified CVP->Unified SIP Proxy->SME->Leaf cluster->Agent

■        Customer->PSTN GW->Unified SIP Proxy->Unified CVP->Unified SIP Proxy->Unified CM SME->Leaf Cluster->Agent

■        Enterprise Unified CM cluster->Unified SIP Proxy->Unified CVP->Unified SIP Proxy-> Unified CM SME->Leaf Cluster->Agent

■        Enterprise Unified CM cluster-> Unified CM SME->CUBE->Unified SIP Proxy->Unified CVP->Unified SIP Proxy->SME->Leaf Cluster->Agent

■        Enterprise Unified CM cluster-> Unified CM SME->CUBE->Unified SIP Proxy->Unified CVP->Unified SIP Proxy->Unified CM->Agent

Testing included:

■        Route point transfer and conference

■        DN-based transfer and conference

■        Hold-resume and check for tones

■        Agent Greeting and Whisper Announcement

■        Agents as Mobile Agents

■        Default offer (early) in Unified CVP 10.5

Configuration

This section provides the high-level tasks and related information for configuring Unified SIP Proxy 9.0 on a Virtual Machine in a Unified CCE environment.

The following table provides this information:

■        Configuration Tasks: List of high-level configuration tasks

■        System Test Specifics: System test variations from procedures and settings documented in the product documentation.

■        More Information: Links to product documentation for detailed configuration information related to the high-level tasks.

Note: Default and recommended values specified in the product documentation were used during system testing, unless otherwise noted in the System Test Specifics column.

Table 1. CUSP on Virtual Machine Configuration

Unified SIP Proxy Configuration Example

This configuration example is for Unified SIP Proxy 9.0.1 on UCS-B with local domain settings with Record-Route turned on.

 Caveats

The following table lists known caveats, grouped by severity, related to Unified SIP Proxy 9.0 on virtual machine testing. Click the linked caveat number in the Identifier column to access more caveats details in the Bug Search Tool.

Table 2. Caveats Related to Unified SIP Proxy 9.0 on Virtual Machine Configuration

Related Documentation

■        Release Notes for Cisco Unified SIP Proxy Release 9.0

■        Cisco Unified SIP Proxy Software Configuration Guides

■        System Release Notes for Contact Center: Cisco Collaboration Systems Release 11.0(1)

■        For information on the IOS commands used to configure infrastructure components, see Configuration Command Files for Unified CCE.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.

Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.

 

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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.

All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version should be referred to for latest version.

Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices.

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

© 2015 Cisco Systems, Inc. All rights reserved.