Cisco Unified Contact Center Express IPv6 Configuration
First Published: July 2, 2014
Last Updated: Feb 11, 2016
The purpose of this document is to describe the configuration of Cisco Unified Contact Center Express (Unified CCX), Cisco Unified Communications Manager (Unified Communications Manager), Cisco Unified Communications Manager IM and Presence Service (IM and Presence Service), Phones, Gateway, and Cisco Unified Border Element (CUBE) in a dual stack environment.
To test the various call flow combinations, change the common device configuration to V4 & V6, V6 only, and V4 only for phones. The trunk to Unified Communications Manager and IM and Presence Service is set as V4 & V6 for all combinations.
For information about design considerations and guidelines to deploy Cisco Unified Contact Center Express, see:
■ Cisco Unified Contact Center Express Design Guide, Release 10.5(1), IPv6 Support
■ Cisco Unified Contact Center Express Design Guide, Release 10.5(1), Deployment Models chapter
This section provides information about the Cisco Unified Contact Center Express deployment. In the test bed, various components were tested. The deployment adheres to principles and designs documented in the Cisco Unified Contact Center Express Design Guide, Release 10.5(1).
Software Versions Used
The Unified CCX IPv6 deployment uses the following software versions for testing:
■ Unified Communications Manager: 10.5.1.10000-7
■ Unified CCX: 10.5.1.10000-20
■ IM and Presence Service: 10.5.1.10000-9
■ Cisco IOS: 15.3(3)M2.9,15.3(3)M3
Call Flow Diagram
Customer Call > PRI Gateway > Voice Gateway or Unified Border Element > Unified Communications Manager > Unified CCX > Cisco Finesse Agent or Phone
This section provides the high-level tasks and related information for configuring a Unified CCX deployment for IPv6:
The following table provides this information:
■ Configure IOS
■ Configure Unified CCX
■ Configure Unified Communications Manager
Step 1 Enable IPv6 on the gateway.
ipv6 multicast rpf use-bgp
description "connected to PBL-DC1-c6506-gig3/14"
ip address 10.31.11.67 255.255.255.192
ipv6 address 2001:10:31:11::67/122
ipv6 eigrp 23
ipv6 router eigrp 23
Step 2 Enable dual stack on the gateway.
voice service voip
call service stop
protocol mode dual-stack preference ipv6
voice service voip
no call service stop
Step 3 Add Unified CM IPv6 and ANAT configuration in dial peer configuration.
dial-peer voice 32 voip
description automation connection of sip-trunk-to-uccx
translation-profile outgoing change-to-7-digit
session protocol sipv2
session target ipv6:[2001:10:31:11::75]:5068 session transport udp/tcp
voice-class codec 4 [i.e. codec preference g711ulaw]
voice-class sip anat
voice-class sip bind control source-interface GigabitEthernet0/0
voice-class sip bind media source-interface GigabitEthernet0/0
dtmf-relay rtp-nte h245-signal h245-alphanumeric
no supplementary-service sip refer
Configure Unified CCX
For information on how to configure IPv6 for Unified CCX, see Cisco Unified Communications Operating System Administration Guide for Cisco Unified CCX and Cisco Unified IP IVR, Release 10.5(1).
Configure Unified Communications Manager
Step 1 To enable IPv6 from Cisco Unified Operating System Administration, choose Settings > IP > Ethernet IPv6. Check the Enable IPv6 check box and enter IPv6 information. Click Save.
Step 2 To add IPv6 to all servers in Unified Communications Manager cluster, from Cisco Unified CM Administrator, choose System > Server. Add IPv6 address to all Unified Communications Manager and IM and Presence Service nodes as shown in images.
Step 3 To set the media and signaling preferences, choose System > Enterprise Parameters. Complete IPv6 information as shown in image.
Step 4 To create common device configuration, choose Device > Device Settings > Common Device Configuration. Complete Common Device Configuration Information as shown in image.
Step 5 Associate Common Device Configuration to phones, CTI route point, trunk, CTI ports, and so on. Complete Device Information as shown in image.
Step 6 From the Cisco Unified IM and Presence Operating System Administration page, check the Enable IPv6 check box. Then click Manual Entry and enter the IPv6 Address for IM and Presence Service as shown in image.
Note: If DHCP is configured, you can use it as the Address Source.
Step 7 To create and enable ANAT SIP profile for Unified Communications Manager, choose Device > Device Settings > SIP Profile. Complete SIP Profile Information as shown in image.
Step 8 To associate the ANAT SIP profile to the trunk, from Trunk Configuration page, add the V4 and V6 IPs of the gateway or Unified Border Element to the trunk in Unified Communications Manager as shown in image. Also, choose the ANAT SIP Profile from the SIP Profile drop-down list.
■ Cisco Unified Contact Center Express Design Guide, Release 10.5(1)
■ Cisco Unified Communications Operating System Administration Guide for Cisco Unified CCX and Cisco Unified IP IVR, Release 10.5(1)
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)
© 2016 Cisco Systems, Inc. All rights reserved.