Transcription

2 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, EPRESS 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 UCBs public domain version of the UNI 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, EPRESSED 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. 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 CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iphone, IP/TV, iq Expertise, the iq logo, iq Net Readiness Scorecard, iquick Study, LightStream, Linksys, MeetingPlace, MG, Networkers, Networking Academy, Network Registrar, PI, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. 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) Copyright 2011 Cisco Systems, Inc. All rights reserved.

7 Preface Purpose This manual describes how to set up, run, and administer the Cisco Unified Contact Center Hosted (Unified CCH) product. It supplements the installation and configuration instructions in the general Cisco Unified Intelligent Contact Management (Unified ICM) software documentation set with specific instructions for installing, configuring, and upgrading software components. Warning: You must have a copy of the Installation Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted available in addition to this manual in order to successfully complete Unified CCH installation and configuration. Many of the details for installation are found only in the Installation Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted. This guide also provides configuration settings to be used with the Cisco Unified Customer Voice Portal (Unified CVP) and Cisco Unified Communications Manager (Unified CM) applications. Note: You must use the documentation provided with those systems to install the Unified CVP and Unified CM software. Audience This document is intended for managers and administrators working in a network service provider environment. Readers of this manual should already have a general understanding of the Unified CCH product. Readers must be familiar with general Unified ICM installation and setup procedures. 1

10 Product Naming Conventions Preface Product Naming Conventions In this release, the product names listed in the table below have changed. The New Name (long version) is reserved for the first instance of that product name and in all headings. The New Name (short version) is used for subsequent instances of the product name. Note: This document uses the naming conventions provided in each GUI, which means that in some cases the old product name is in use. Old Product Name Cisco IPCC Enterprise Edition New Name (long version) Cisco Unified Contact Center Enterprise Cisco System IPCC Enterprise Edition Cisco Unified System Contact Center Enterprise Cisco IPCC Hosted Edition Cisco Unified Contact Center Hosted Cisco Intelligent Contact Management Cisco Unified Intelligent Contact (ICM) Enterprise Edition Management Enterprise Cisco Intelligent Contact Management Cisco Unified Intelligent Contact (ICM) Hosted Edition Management Hosted Cisco CallManager/Cisco Unified CallManager Cisco Unified Communications Manager New Name (short version) Unified CCE Unified SCCE Unified CCH Unified ICME Unified ICMH Unified CM Conventions This manual uses the following conventions: Convention boldface font Description Boldface font is used to indicate commands, such as user entries, keys, buttons, and folder and submenu names. For example: Choose Edit > Find. Click Finish. italic font Italic font is used to indicate the following: To introduce a new term; for example: A skill group is a collection of agents who share similar skills For emphasis; for example: Do not use the numerical naming convention 4

11 Preface Obtaining Documentation and Submitting a Service Request Convention Description A syntax value that the user must replace; for example: IF (condition, true-value, false-value) A book title; for example: Refer to the Cisco CRS Installation Guide window font Window font, such as Courier, is used for the following: Text as it appears in code or that the window displays; for example: <html><title>cisco Systems,Inc. </ title></html> Navigational text when selecting menu options; for example: ICM Configuration Manager > Tools> Explorer Tools > Agent Explorer < > Angle brackets are used to indicate the following: For arguments where the context does not allow italic, such as ASCII output A character string that the user enters but that does not appear on the window such as a password Obtaining Documentation and Submitting a Service Request For information about 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. Documentation Feedback You can provide comments about this document by sending an message to the following address: We appreciate your comments. 5

12 Documentation Feedback Preface 6

13 Introduction to Cisco Unified Contact Center Hosted This chapter provides a brief description of the Unified CCH system and an explanation of its components. This chapter contains the following topics: Chapter 1 About Cisco Unified Contact Center Hosted, page 7 About Cisco Unified Contact Center Hosted Hardware Components, page 8 About Cisco Unified Contact Center Hosted Software Components, page 8 Cisco Unified Contact Center Hosted Installation and Configuration Tasks, page 9 About Cisco Unified Contact Center Hosted Unified CCH allows a network service provider to offer virtual call center services to its customers. Using Cisco Network Applications Manager (NAM), the carrier-class version of the Cisco Unified Intelligent Contact Management (Unified ICM) software, it distributes incoming calls to individual network service customers based on the number dialed, the call s point of origin, and caller-entered digits. The Unified ICM systems that are connected to the NAM are known as Customer ICMs, or CICMs. Often the phrase CICM is used to refer to a deployment where a single computer can host Unified ICM Central Controllers for multiple customers (up to 25, depending on the side of the Unified ICM system). A single Unified CCH NAM can pass route requests to any of several CICMs. Based on the information it has for the call (dialed number, caller-entered digits, and calling line ID), Unified CCH can run a routing script that selects the appropriate CICM and sends it a route request. A Unified CCH deployment usually involves refers to a specific deployment, where a multi-tenant CICM talks to a set of Unified CCH PGs and these PGs all talk to the same Unified CM. (The Unified CM is partitioned so that certain ranges of extensions belong to each customer.) 7

14 About Cisco Unified Contact Center Hosted Hardware Components Chapter 1: Introduction to Cisco Unified Contact Center Hosted Multi-tenancy PG for Cisco Unified Contact Center Hosted The generic PG allows multiple instances of the PG to be installed on the same physical server, each of which is connected to a single instance of Unified CM via JTAPI. Combined with multi-tenancy CTI OS, this feature allows service providers to deploy Unified CCH without the need for dedicated servers for each PG. For example, a service provider desiring to host 10 customers could install 10 instances of the Unified CCH PG and 10 instances of CTIOS all on a single box, and then perform comparable installation on a second box for the purpose of redundancy. (Total of 2 boxes for 10 customers.) Multi-Tenant Outbound Option for Cisco Unified Contact Center Hosted Release 8.0(1) of Outbound Option allows multiple customer instances to run Outbound Option in a Hosted environment. This new feature, known as Outbound Option Multi-Tenant, is available in Outbound Option deployments that use the SIP Dialer. See Also See the "Configuring Outbound Option Multi-Tenant Customer Instances (page 65)" section for more details. About Cisco Unified Contact Center Hosted Hardware Components Refer to the Hardware & System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise & Hosted at custcosw/ps1844/prod_technical_reference_list.html for specifics on hardware requirements. About Cisco Unified Contact Center Hosted Software Components This section briefly describes the software components of the Unified CCH system. For more detailed information regarding software components and Unified CCH architecture, refer to the Cisco Unified Contact Center Enterprise 8.0(x) Solution Reference Network Design (SRND) (http://www.cisco.com/en/us/products/sw/custcosw/ps1844/ products_implementation_design_guides_list.html). Cisco Unified Contact Center Hosted Core Components Table 1: Unified CCH Core Components The following core software components are required in all Unified CCH systems. Unified CCH Component Unified CM Description Unified CM provides features comparable with those of a traditional PB system and handles the switching requirements of the Unified CCH system. 8

21 CICM Installation and Configuration This chapter discusses the procedures you need to perform to install and configure CICM. Note: You must have a copy of the Installation Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted available in addition to this manual in order to successfully complete CICM configuration. If you are installing and configuring CICM systems that will be part of a Multiple-NAM configuration, also refer to the installation and configuration instructions in the Multiple-NAM Setup and Configuration Guide for Cisco Unified ICM Hosted. This chapter contains the following topics: Chapter 2 Introduction to Instances, page 15 Naming Conventions for Instances, page 16 Selecting the CICM Complex, page 16 Assigning an Instance Number to a CICM, page 17 Installing and Configuring CICM Loggers, page 19 Installing and Configuring CICM CallRouters, page 20 Installing a CICM Network Administration & Data Server, page 20 Configuring the CICM's INCRP NIC, page 21 Quality of Service (QoS), page 25 Adding and Upgrading Components for Instances, page 25 Introduction to Instances In a NAM environment, each duplexed CICM system serves up to 25 instances. Each instance is associated with one duplexed CICM system. As mentioned earlier, a CICM complex is a single hardware platform on which multiple CICM instances may reside. Each instance, in turn, can be shared by several customers with limited 15

22 Naming Conventions for Instances Chapter 2: CICM Installation and Configuration functionality. As new instances are added to the system, you must install additional Unified ICM components (Loggers, CallRouters, and Administration & Data Servers) on the CICM machines. Adding a new instance to a CICM complex consists of several tasks. Deciding on the instance name Selecting the CICM complex to service the instance Assigning an instance number Setting up the CICM Loggers Setting up the CICM CallRouters Setting up the CICM instance Administration & Data Server on the NAM Configuring the INCRP NIC The following subsections explain these steps. After completing these steps you can proceed to set up Peripheral Gateways and Administration & Data Servers at the customer premises. Naming Conventions for Instances Select a unique instance name of up to five characters. The first character of the name must be a letter (a z or A Z). Subsequent characters can be letters, digits, or the symbols # or $. The name must not contain spaces. You cannot use case to differentiate instances. For example, you cannot name two instances cus01 and Cus01. When forming database names, the system software converts the instance name to all lowercase. The instance name is used in naming a registry subtree, a subdirectory of the \icm directory, and as a prefix on database names. For an instance named cust1, the CICM databases are named cust1_sidea and cust1_sideb. The local database on an Administration & Data Server is named cust1_awdb. Selecting the CICM Complex Select which CICM complex will service this instance. Consider the current load on each CICM complex and the expected load for the new instance. Usually it is best to roughly balance the overall load among available CICM complexes. If all CICM complexes are nearing capacity, consider adding a new CICM complex. 16

23 Chapter 2: CICM Installation and Configuration Assigning an Instance Number to a CICM Assigning an Instance Number to a CICM Each instance within a CICM complex must have a unique instance number. The same number must be used to identify the instance on each machine in the CICM complex. How to See Instance Numbers Currently in Use Step 1 Step 2 On any Administration & Data Server in the CICM complex, select Start > Run. The Run dialog box appears. Type instanceno.exe in the Open field and click OK. (This executable is installed in the \icm\bin directory on every Administration & Data Server.) The Name Fragment dialog box appears. Figure 1: Name Fragment Dialog Step 3 Specify the machine name fragment that is used in all machines on your site. (For example, if Logger A is named CSOYZLGRA, enter YZ.) Step 4 If the system is simplexed, check the Simplexed option and choose side A or B. Step 5 Click OK. The system checks each CallRouter and Logger to find which instance numbers are in use. It then displays a screen similar to the following: 17

24 Assigning an Instance Number to a CICM Chapter 2: CICM Installation and Configuration Figure 2: Instance Number Values Dialog A value of 1 indicates that the instance is not defined on that machine. The field at the bottom of the window specifies which instance numbers are available for use. Step 6 Step 7 Take note of the available numbers so you can use one of them for the new instance. You must use this same number when adding the instance to each machine. Click Close. How to Add an Instance to a CICM Step 1 Step 2 Step 3 Step 4 Step 5 On a CICM, open the Web Setup tool. Click Instance Management in the left frame, then click Add in the right frame. An Add Instance page appears. From the drop-down lists, select a facility and an instance. Enter the instance number you chose previously. Click Save to add the instance. 18

25 Chapter 2: CICM Installation and Configuration Installing and Configuring CICM Loggers Installing and Configuring CICM Loggers You must perform the following steps to install and configure a Logger in a CICM domain. Note: If a Logger is duplexed, perform these steps on each side. Be careful to use the same instance name and instance number on both sides. How to Install and Configure a CICM Logger (Side A or Side B) Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Create the central database on the Logger machine using the ICMDBA utility. Open the Web Setup tool. Select Component Management > Loggers in the left frame, then click Add in the right frame. The Add Logger Deployments page appears. On this page, be sure to select Hosted > Customer ICM (CICM) for Logger Type. Provide values for the other fields on this page. Click Next. Provide values for the applicable fields on the Central Controller Connectivity and Additional Options page. Clicking Next from the Additional Options page takes you to a NAM page. On the NAM page, select one of the following values for NAM Type: a. Provisioning/Standalone NAM: NAM Logger is either a Standalone NAM or a NAM that provides Slave NAMs with configuration information b. Slave NAM: NAM Logger that obtains configuration information from a Provisioning NAM Step 8 Provide the following values in the NAM Configuration section: a. Provisioning/Standalone Router Side A: Enter the Side A machine name or IP address of the provisioning Router b. Provisioning/Standalone Router Side B: If a Side B machine exists, enter the Side B machine name or IP address of the provisioning Router Step 9 If you specified a NAM Type of Provisioning/Standalone NAM, skip the Slave NAM Configuration section. If you specified a NAM Type of Slave NAM, specify the following information: a. Provisioning NAM Instance Name: The instance name of the Provisioning NAM b. Provisioning NAM Instance Number: The instance number of the Provisioning NAM 19

26 Installing and Configuring CICM CallRouters Chapter 2: CICM Installation and Configuration c. Provisioning Logger Side A: The Side A machine name or IP address of the Provisioning Logger d. Provisioning Logger Side B: If present, the Side B machine name or IP address of the Provisioning Logger e. Slave Router Side A: The Side A machine name or IP address of the Slave Router f. Slave Router Side B: If present, the Side B machine name or IP address of the Slave Router Step 10 Step 11 Click Next. Complete the rest of the Logger setup. Installing and Configuring CICM CallRouters You must perform the following steps to install and configure a CallRouter in a CICM domain. Note: You must set up the instance on the Logger machines before the CallRouter machines. If a CallRouter is duplexed, perform these steps on each side. Be careful to use the same instance name and instance number on both sides. How to Install and Configure CICM CallRouter Software Step 1 Step 2 Step 3 Step 4 Open the Web Setup tool. Select Component Management > Routers in the left frame, then click Add in the right frame. Click Next. Complete the CallRouter setup. Note: If a CallRouter is duplexed, perform these steps on each side. Be careful to use the same instance name and instance number on both sides. Installing a CICM Network Administration & Data Server To create configuration data for an instance, you must add the instance to a CICM Network Administration & Data Server. 20

27 Chapter 2: CICM Installation and Configuration Configuring the CICM's INCRP NIC How to Install a CICM Network Administration & Data Server Step 1 Step 2 Step 3 Step 4 Step 5 Open the Web Setup tool. Select Component Management > Administration & Data Servers in the left frame, then click Add in the right frame. In the first Add Administration & Data Server page, select Hosted for the Deployment Type, and also select Network Administration & Data Server for Customer ICM (CICM). Supply values for the other fields in this window, then click Next. Complete the rest of the Administration & Data Server setup. Configuring the CICM's INCRP NIC The NAM communicates with the CICM by means of an INCRP NIC. To set up the INCRP NIC for each instance on the CICM, you must perform the following tasks: Define the INCRP NIC using the NIC Explorer tool (page 21) Add CallRouter configuration information using the Web Setup tool (page 23) How to Define the INCRP NIC Note: The preferred network for this connection is the Public/Visible or SAN network. When using the SAN network, it must have a WAN link between Side A and B (SAN was originally intended for the CallRouter to Network Gateway connection, which does not cross the A/B boundary). Step 1 Step 2 Step 3 Step 4 Step 5 Access the Select Administration Instance tool by selecting Start > All Programs > Cisco Unified CCE Tools > Administration Tools > Select Administration Instance. The Select Administration Instance window displays. Select the instance you will be configuring. From the Configuration Manager, open the NIC Explorer tool by selecting Tools > Explorer Tools > NIC Explorer. The NIC Explorer window displays. In the Select filter data box, click Retrieve. This enables the Add NIC button. Click Add NIC. A new NIC and its routing client display in the tree window. Next to each is a To Be Inserted icon. 21

28 Configuring the CICM's INCRP NIC Chapter 2: CICM Installation and Configuration On the right of the tree window, tabbed fields also display for the new NIC's and routing client's configuration information. Step 6 Enter the following in the Logical Interface Controller tab fields: Name. An enterprise name that will serve as the NIC name. The name can be up to 32 characters. The valid characters are upper-case and lower-case letters, digits, periods (.) and underlines (_). The first character of the name must be a letter or digit. Client Type (drop-down list). The type of routing client serviced by the NIC. Select INCRP. Note: Selecting a type of routing client automatically places that type's default values in the Routing Client's Timeout Threshold, Late Threshold, Timeout Limit, Use DN/Label Map, and Client Type fields. Figure 3: Logical Interface Controller Tab Step 7 Click the Add Physical Interface Controller button. The Physical Interface Controller dialog displays. Figure 4: Physical Interface Controller Dialog Step 8 Step 9 In the Create Single Physical Interface Controller section, specify an Enterprise Name and, optionally, a Description. Click OK. The Physical Interface Controller tab displays, displaying the information you specified, and an ID value of UNASSIGNED. 22

29 Chapter 2: CICM Installation and Configuration Configuring the CICM's INCRP NIC Step 10 Click the Add Routing Client button, and enter the following on the Routing Client tab fields: Name. An enterprise name that will serve as the NIC Routing Client name. The name can be up to 32 characters. The valid characters are upper-case and lower-case letters, digits, periods (.) and underlines (_). The first character of the name must be a letter or digit. Client Type (drop-down list). The type of routing client that ultimately routes the call on the requesting NAM. Note: This field is enabled only for the routing client associated with an INCRP NIC. If your NAM has multiple routing clients, ensure that each client is defined and that the ClientType field in the Routing Client record matches the client type of the NAM's NIC. In addition, the Configuration Parameter field for each record must contain the parameter: /CustomerID <RCID> where <RCID> is the Routing Client ID of the matching routing client on the NAM, as defined in the SQL table. Note: For instructions on how to update a record in the Configuration Manager, refer to the Configuration Guide for Cisco Unified ICM/Contact Center Enterprise and Hosted. Step 11 Step 12 If desired, define security settings on the records. Click Save. The newly defined NIC is saved in the database, a Physical Controller ID is assigned, and the To Be Inserted icon is removed from the tree window. Note: Make a note of the Physical Controller ID value. You need this value to set up the INCRP NIC on the CallRouter. If the NIC is duplexed, you need both Physical Controller ID values. Step 13 Click Close to exit the NIC Explorer tool. How to Complete the INCRP NIC Setup To provide detailed set-up information for the NIC, do the following: Step 1 Step 2 Step 3 Step 4 Step 5 Open the Web Setup tool. Select Component Management > Routers > Network Interface Controllers in the left frame, then click Add in the right frame. The Add Network Interface Controllers Deployments page displays. Select a value for the Instance. On the Network Interface Controller pull-down menu, select INCRP. Click Next. The Properties page displays. 23

30 Configuring the CICM's INCRP NIC Chapter 2: CICM Installation and Configuration Step 6 Specify the following values: a. Physical Interface Controller ID: Enter one of the physical controller IDs (from the Configuration Manager) for the INCRP NIC on the CICM. If the NIC is duplexed, be sure to enter a different physical controller ID on each side. b. Local Hostname or IP Address: Enter the IP Name (IP Address or hostname) of the local address for incoming NAM connections. (Note that this address/host must be on the same network as the NAM Addresses.) c. Handshake Timeout (ms): Enter the milliseconds to wait for a handshake response from the routing client (the supplied default of 5000 milliseconds is usually appropriate). Step 7 Step 8 Click Next. The Client ICM/CCE/CCH page displays. Enter the following information: a. Enabled: Check the box to enable the Client ICM. b. Description: Enter a description of the Client ICM. c. Client ID: Enter the ID of the Client ICM machine. In this case, that is the same as the NAM ID. d. AppGateway ID: Specify the ApplicationGatewayID for the INCRP NIC as configured in the Client ICM database. e. SCP Side A IP Address/Hostname: Enter the Public Network (or SAN) addresses/hostnames of the NAM on Side A. f. SCP Side B IP Address/Hostname: Enter the Public Network (or SAN) addresses/hostnames of the NAM on Side B. Step 9 Click Next, then click Finish to complete INCRP NIC installation. Note: You need not set up DMP devices for the INCRP NIC, because it is a process on the CallRouter rather than a separate device. Consideration for Multiple NAM/CICM Routing Clients For multiple NAM/CICM routing client configurations that will use CICM Replication, you must associate a routing client on the CICM for each routing client on the NAM for that customer. You cannot use the same name for two different routing clients on the CICM or NAM. For example: A NAM system has two routing clients with enterprise names YZ_NIC_1 and INAP_NIC_1. The YZ_NIC_1 routing client has a network routing client of YZ_NIC, and the INAP_NIC_1 routing client has a network routing client of INAP_NIC. 24

31 Chapter 2: CICM Installation and Configuration Quality of Service (QoS) The associated CICM system has two routing clients with enterprise names INCRP_NIC_1 and INCRP_NIC_2. For these routing clients on the CICM, you must define network routing clients of YZ_NIC and INAP_NIC, respectively. Note: Because routes are not normally defined on the NAM, a default route for a dialed number cannot be set on the NAM. However, labels are defined on both the NAM and the CICM. Therefore, dialed numbers have default labels rather than default routes. Quality of Service (QoS) If you wish to use the optional Unified ICM Quality of Service feature, the appropriate steps are provided in the Installation Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted, with discussion of QoS to be found in the Pre-installation Planning Guide for Cisco Unified ICM Enterprise and Hosted. However, note the following if you are using the Microsoft Packet Scheduler. As all ICM instances of a CICM share, by design, public and private network interfaces, and the Microsoft Packet Scheduler is mapped to an address / interface, it follows that ICM instances hosted in a common physical CICM complex must be uniformly configured when deploying QoS. Note: The configuration settings of the last customer configured via the Web Setup tool will be those in effect. Adding and Upgrading Components for Instances To add or upgrade components for instances, do one of the following: To add a new component for an instance, run the Web Setup tool. From the initial Web Setup page, click Component Management in the left column. Under Component Management, click the type of component you want to add; a List page for the component appears. Click Add on this List page to start the Add wizard for the component. To upgrade all installed components for all instances, rerun the main installation program (setup.exe) from the Release 8.0(1) ICM/CCE/CCH DVD. Refer to the Installation Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted for instructions. Removing an Instance The following steps describe the process for removing an instance. Step 1 Use the Service Control utility to stop the services for that instance on all CICM machines and Administration & Data Servers. 25

32 Adding and Upgrading Components for Instances Chapter 2: CICM Installation and Configuration Step 2 Step 3 Step 4 Step 5 Run the Web Setup tool. Click Instance Management in the left column. An Instance List page appears. Check the check box to the left of the instance(s) you want to remove. Click Remove to remove the instance(s). 26

34 Cisco Unified Communications Manager Configuration Chapter 3: Cisco Unified Communications Manager Configuration Step 3 Step 4 Enable Unified CM PIMs. Verify Unified CM PG PIM services are active. Stopping Cisco Unified Communications Manager Associated PG Services Step 1 On the PG associated with the Unified CM: a. Open Unified CCE Service Control for the CICM. b. Select the PG service associated with the Unified CM. c. Click Stop to stop the service. Step 2 On the CTI Server associated with the Unified CM: a. Open Unified CCE Service Control. b. Select the PG service associated with the Unified CM. c. Click Stop to stop the service. Configuring Agent Phones in Cisco Unified Communications Manager Before you can configure phones in Unified CM, each IP phone that you use with Unified CCH requires an IP address. IP addresses can be assigned either dynamically or manually (statically). Configuring an IP address may also involved assigning a default gateway, assigning a subnet mask, and assigning a Domain Name. Refer to the user documentation for your phone for information on IP address configuration requirements. In Unified CM, you must configure one directory number (extension) for each agent. Multiple extensions for an agent are not currently supported. You must configure an agent phone and then associate the phone with the Unified CM PG user. Step 1 Step 2 Step 3 Step 4 From the Unified CM Administration window, select Device > Phone. On the Find and List Phone page, enter the search criteria to list the registered phones. When the list displays, double-click the phone icon in the Device Name column to display the Phone Configuration window. Check that the Device Information is correct. Click on the Line 1 to configure the Directory Number for the device. You must disable call waiting on all agent phones. This is done to ensure that forward on busy option is available. You can do this most easily by setting the Unified CM system default for Call Waiting Enable to off. If this is not practical due to, for example, other agents that are configured on the Unified CM that require call waiting, then you can set individual agent phones to disable call waiting by selecting the line from the phone configuration page for each phone. 28

36 Cisco Unified Communications Manager Configuration Chapter 3: Cisco Unified Communications Manager Configuration Step 5 Step 6 Select the Enable CTI Application Use checkbox. Click Insert. The window changes. Step 7 To put the user and the route point together you must associate the devices. Click Device Association and then click Select Devices. All the Device names and extensions appear. Step 8 Step 9 Step 10 Select all of the devices that you want this user to control. The Unified CM PG User controls the IP phones; the Unified IP IVR User controls the Route Points for Unified IP IVR DNs and the Ports. Select the No Primary Extension radio button. Click Save. Cisco Unified Communications Manager Multi-tenancy Configuration Unified CM clusters in Unified CCH can be shared across multiple servers. However, special configuration must take place to ensure that calls can not be inadvertently transferred between server instances. Single multiple customer instances can exist on a single Unified CM cluster, so you need to configure Unified CM for multi-tenancy. Multi-tenancy in Unified CM is achieved by using Route Plan Partitions and Calling Search Spaces to restrict direct calls between customer instances. The following sections describe Partitions and Calling Search Spaces, and how they can be used in multi-tenant situations. Partitions and Calling Search Spaces A partition comprises a logical grouping of directory numbers (DNs) and route patterns with similar reachability characteristics. Devices that are typically placed in partitions include DNs and route patterns. These entities associate with DNs that users dial. For simplicity, partition names usually reflect their characteristics, such as NYLongDistancePT, NY911PT, and so on. A calling search space comprises an ordered list of partitions that users can look at before users are allowed to place a call. Calling search spaces determine the partitions that calling devices, including IP phones, soft phones, and gateways can search when attempting to complete a call. When a calling search space is assigned to a device, the list of partitions in the calling search space comprises only the partitions that the device is allowed to reach. All other DNs that are in partitions not in the device calling search space receive a busy signal. Partitions and calling search spaces address three specific problems: 30

37 Chapter 3: Cisco Unified Communications Manager Configuration Cisco Unified Communications Manager Configuration Routing by geographical location Routing by tenant Routing by class of user Partitions and calling search spaces provide a way to segregate the global dialable address space. The global dialable address space comprises the complete set of dialing patterns to which the Unified CM can respond. Partitions do not significantly impact the performance of digit analysis, but every partition that is specified in a calling device search space does require that an additional analysis pass through the analysis data structures. The digit analysis process looks through every partition in a calling search space for the best match. The order of the partitions that are listed in the calling search space serves only to break ties when equally good matches occur in two different partitions. If no partition is specified for a pattern, the pattern goes in the null partition to resolve dialed digits. Digit analysis always looks through the null partition last. In a typical Unified CCH system you will create partitions for your different dialing options, for example: US_National, US_Internation, and US_Emergency, as well as creating a partition for each customer instance, for example: Customer_1, Customer_2, and Customer_3. Once you have created the partitions, you can then create Calling Search Spaces to limit the dialability for each customer. The following table represents a basic Calling Search Space configuration in Unified CCH: CallingSearch Space Customer1_basic_CSS Customer1_manager_CSS Customer2_basic_CSS Customer2_manager_CSS Gateway_CSS Dialable Partitions (highest priority first) customer1_partition, US_Emergency, US_National, US_Emergency customer1_parition, US_Emergency, US_National, US_International customer2_partition, US_Emergency, US_National, US_Emergency customer2_parition, US_Emergency, US_National, US_International customer2_partition, customer2_partition Individual phones are associated with a calling search space. A Manager s phone might be connected to the Customer1_Manager_CSS Calling search space. This allows the user of that phone to make national, international, emergency, and calls to other phones in the search space, but it does not allow for calls to be places directly to phones in the Customer2_Partition Route Plan Partition. When setting up your Unified CM keep in mind the need to create customer-instance specific partitions and Calling Search Spaces that limit interaction between customer instances. For more details on Multi-tenancy configuration, refer to the Cisco Unified Communications Manager System Guide (http://www.cisco.com/en/us/products/sw/voicesw/ps556/ prod_maintenance_guides_list.html). 31

38 Cisco Unified Communications Manager Configuration Chapter 3: Cisco Unified Communications Manager Configuration Multi-tenancy Configuration To enable multi-tenancy you must create separate partitions for each customer instance in addition to the normal partitions required for a Unified CM system. Adding a Partition For more information on this topic, refer to the Cisco Unified Communications Manager Administration Guide (http://www.cisco.com/en/us/products/sw/voicesw/ps556/ prod_maintenance_guides_list.html). Step 1 Step 2 In the Unified CM Administration window, select Call Routing > Class of Control > Partition. Click Add New. The Add Partition window displays. Step 3 Enter a name in the partition name and description box. Ensure each partition name is unique to the route plan. Partition names can contain alphanumeric characters, as well as spaces, hyphens (-), and underscore characters (_). Note: The length of the partition names limits the maximum number of partitions that can be added to a calling search space. Follow the partition name by a comma (,); then, enter a description on the same line as the Partition Name. If you do not enter a description, Unified CM automatically enters the partition name in this field. Use a new line for each partition and description. Step 4 Click Save to add the new partition(s). Note: You can configure multiple partitions. To enter multiple partitions, use one line for each partition entry. You can enter up to 75 partitions; the names and descriptions can have a total of up to 1475 characters. Use a comma (,) to separate the partition name and description on each line. If you do not enter a description, Unified CM uses the name as the description. Adding a Calling Search Space For more information on this topic, refer to the Cisco Unified Communications Manager Administration Guide (http://www.cisco.com/en/us/products/sw/voicesw/ps556/ prod_maintenance_guides_list.html). Step 1 Step 2 In the Unified CM Administration window, select Call Routing > Class of Control > Calling Search Space. Click Add New. 32

39 Chapter 3: Cisco Unified Communications Manager Configuration Cisco Unified Communications Manager Configuration The Add Calling Search Space window displays. a. Calling Search Space Name Enter a name in the Calling Search Space Name field. The name can comprise up to 50 alphanumeric characters and can contain any combination of spaces, periods (.), hyphens (-), and underscore characters (_). Ensure each calling search space name is unique to the plan. The name can comprise up to 50 alphanumeric characters and can contain any combination of spaces, periods (.), hyphens (-), and underscore characters (_). Ensure each calling search space name is unique to the plan. Note: Use concise and descriptive names for your calling search spaces. The CompanynameLocationCalltype format usually provides a sufficient level of detail and is short enough to enable you to quickly and easily identify a calling search space. For example, CiscoDallasMetroCS identifies a calling search space for toll-free, inter-local access and transport area (LATA) calls from the Cisco office in Dallas. b. Description Enter a description in the Description field. The description can comprise up to 50 alphanumeric characters and can contain any combination of spaces, periods (.), hyphens (-), and underscore characters (_). c. Selected Partitions Select the partitions to add to this calling search space from the list of available partitions. You can limit the list of partitions by using the following field. d. Available Partitions Enter the character(s) that are found in the partition name that you are seeking and click Find. Partition names that match the character(s) that you entered display in the Available Partitions box. To add multiple partitions that are not contiguous, hold down the Control (Ctrl) key while clicking on multiple partitions. Click the arrow button between the two list boxes to add the chosen partitions. Step 3 To add the new calling search space, click Save. The message Status: Insert completed displays. Step 4 To add more calling search spaces, click Add New and repeat this procedure. Setting Up Duplicate Extensions in Different Customer Instances You can use duplicate extensions in different instances in a Unified CCH environment. To accomplish this, you must associate the device targets with the appropriate peripheral using the /PID configuration parameter. This ensures that the device target is tied to the peripheral; other peripherals will not recognize it. To associate a device target with a peripheral: 33

40 Cisco Unified Communications Manager Configuration Chapter 3: Cisco Unified Communications Manager Configuration Step 1 Step 2 Step 3 Using the Device Target Explorer on a CICM Administration & Data Server, add or modify single device target entries. Set the Configuration Parameter field to /PID <xxxx>, where <xxxx> is the four-digit Peripheral ID (for example: /PID 5000). Click Save to save the device. Note: When you save this change, it takes effect immediately. You do not need to cycle the Unified CM PG Node services for this to take effect. 34

42 About Cisco Unified Customer Voice Portal Chapter 4: Installing and Configuring Cisco Unified Customer Voice Portal for Cisco Unified Contact Center Hosted About Cisco Unified Customer Voice Portal Cisco Unified Customer Voice Portal (Unified CVP) can be deployed in the Unified CCH system to provide IVR queuing and call treatment. This guide provides basic information about configuring Unified CVP for Unified CCH. The exact manner in which you configure Unified CVP depends on the deployment model of Unified CVP that you are using for your system. For more detailed information on configuring Unified CVP in your deployment model, refer to the Unified CVP Deployment appendix in the Configuration and Administration Guide for Cisco Unified Customer Voice Portal (http:/ /www.cisco.com/en/us/products/sw/custcosw/ps1006/ products_installation_and_configuration_guides_list.html). Also, the Getting Started Guide for Cisco Unified Customer Voice Portal (http://www.cisco.com/en/us/products/sw/custcosw/ ps1006/products_installation_and_configuration_guides_list.html) provides detailed configuration information. About Installing Unified CVP for Cisco Unified Contact Center Hosted Step-by-step installation instructions for Unified CVP are included in the Installation and Upgrade Guide for Cisco Unified Customer Voice Portal (http://www.cisco.com/en/us/ products/sw/custcosw/ps1006/prod_installation_guides_list.html). Also, the Getting Started Guide for Cisco Unified Customer Voice Portal (http://www.cisco.com/en/us/products/sw/ custcosw/ps1006/products_installation_and_configuration_guides_list.html) provides detailed instructions that help a new user get started using the Unified CVP product in one or more test environments. If you are deploying a Unified CCH laboratory system, you can install all of these components on a single machine and must install all components at the same time. If you do not install all components and later decide to add a component, you must uninstall the existing Unified CVP software and perform a complete re-install. If you are deploying a Unified CCH production system, you can install individual components on different machines. See Also Refer to the Cisco Unified Customer Voice Portal (CVP) 8.x Solution Reference Network Design (SRND) (http://www.cisco.com/en/us/products/sw/custcosw/ps1006/ products_implementation_design_guides_list.html) and the Cisco Unified Contact Center Enterprise 8.x Solution Reference Network Design (SRND) (http://www.cisco.com/en/us/ products/sw/custcosw/ps1844/products_implementation_design_guides_list.html) for detailed deployment information. 36

43 Chapter 4: Installing and Configuring Cisco Unified Customer Voice Portal for Cisco Unified Contact Center Hosted About Configuring Unified CVP for Cisco Unified Contact Center Hosted About Configuring Unified CVP for Cisco Unified Contact Center Hosted Refer to the Configuration and Administration Guide for Cisco Unified Customer Voice Portal (http://www.cisco.com/en/us/products/sw/custcosw/ps1006/ products_installation_and_configuration_guides_list.html) for detailed configuration instructions. About Setting Up Cisco Gateways/Gatekeepers to Interact with Unified CVP You must configure Gateway(s) and Gatekeeper(s) in order to properly route inbound calls (calls originating from the caller into Unified CVP) and outbound calls (calls being transferred to an agent through Unified CVP). Refer to the Configuration and Administration Guide for Cisco Unified Customer Voice Portal (http://www.cisco.com/en/us/products/sw/custcosw/ps1006/ products_installation_and_configuration_guides_list.html) and the Getting Started Guide for Cisco Unified Customer Voice Portal (http://www.cisco.com/en/us/products/sw/custcosw/ ps1006/products_installation_and_configuration_guides_list.html) for detailed information about configuring gateways. How to Set Up Cisco NAM Software to Interact with Unified CVP There are several "one time only" steps you need to take to enable interaction between NAM/Unified ICM and Unified CVP software: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Determine what Unified CVP Network VRU types you need to define. Define an Unified CVP Network VRU. Set the Enable Expanded Call Context option. Define expanded call context (ECC) variables for Unified CVP. Define the default Network VRU. Configure the Peripheral Gateway (PG) for the Unified CVP. Note: For more information, refer to the Unified CVP Deployment appendix in the Configuration and Administration Guide for Cisco Unified Customer Voice Portal (http:/ /www.cisco.com/en/us/products/sw/custcosw/ps1006/ products_installation_and_configuration_guides_list.html). How to Set Up Cisco CICM Software to Interact with Unified CVP Do the following to enable interaction between CICM and Unified CVP software: 37

44 Chapter 4: Installing and Configuring Cisco Unified Customer Voice Portal for Cisco Unified Contact Center Hosted About Configuring Unified CVP for Cisco Unified Contact Center Hosted Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Determine what Unified CVP Network VRU types you need to define. Define an Unified CVP Network VRU. Set the Enable Expanded Call Context option. Define expanded call context (ECC) variables for Unified CVP. Define the default Network VRU. Configure the Peripheral Gateway (PG) for the Unified CVP. Associate a Dialed Number, Call Type, and Routing Script to a specific customer instance. How to Configure the Dynamic Routing Client When Unified ICM uses the Translation Route to VRU method to route a call to a type 2 SCI VRU, the VRU becomes the new routing client for the call. This means that the next Connect message is sent to the VRU to connect the call (to an agent, for example). The dynamic routing client feature is required to allow Unified ICM to make a subsequent network transfer using the new VRU routing client. Dynamic routing client capability is required for the following call scenarios: Receiving a call on a converged enterprise network after a carrier pre-route using Unified CVP (release 2.1 and later) to control the call. Using pre-routing for load balancing purposes before the call is sent to an Unified CVP-controlled network with call context and cradle to grave reporting capabilities. Supporting Outbound Option for Unified CCH where a shared Network VRU is used for providing announcements to targeted phones/answer machines. In an environment where the routing client is not capable of Network Transfer, all the pre-route calls must be transferred to Unified CVP via Translation Route To VRU to take advantage of the network transfer feature. To configure Unified CVP as a dynamic routing client: Step 1 Configure the Unified CVP machine used for Dynamic Routing Client like any other, with the following exceptions: In Configuration Manager > Network VRU Explorer, define the machine as a Type 2 VRU. In Configuration Manager > PG Explorer, on the Routing Client tab, de-select Network Transfer Preferred for this peripheral. 38

47 NAM Installation and Configuration for Cisco Unified Contact Center Hosted This chapter discusses the procedures you need to perform to install and configure a NAM system. These instructions assume that Windows including SNMP and, for Windows 2003, WMI and SQL Server are already installed, and that Windows Active Directory services for the system software, including at least one ICM instance, have been set up. Note: You must have a copy of the Installation Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted available in addition to this manual in order to successfully complete NAM installation and configuration. If you are installing and configuring NAM systems that are part of a Multiple-NAM configuration, refer to the installation and configuration instructions in the Multiple-NAM Setup and Configuration Guide for Cisco Unified ICM Hosted. This chapter contains the following topics: Chapter 5 Installing NAM Logger Software, page 41 Post-Installation Setup and Installing Multiple Components, page 43 About Administration & Data Server Types, page 44 NAM Configuration Data, page 45 Defining CICM Instances and Customers on the NAM, page 46 Installing NAM Cisco Unified Customer Voice Portal PG, page 49 Installing and Configuring NAM NICs and PGs, page 55 Upgrading the NAM, page 58 Installing NAM Logger Software The Logger is the process that manages the central database. A Logger process runs on each NAM and CICM in the Unified ICMH system. 41

48 Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Create the central database on the Logger machine using the ICMDBA utility. Open the Web Setup tool. Select Component Management > Loggers in the left frame, then click Add in the right frame. The Add Logger Deployments page appears. On this page, be sure to select Hosted > Network Application Manager (NAM) for Logger Type. Provide values for the other fields on this page, then click Next. Provide values for the applicable fields on the Central Controller Connectivity and Additional Options page. Clicking Next from the Additional Options page takes you to a NAM page. On the NAM page, select one of the following values for NAM Type: a. Provisioning/Standalone NAM: NAM Logger is either a Standalone NAM or a NAM that provides Slave NAMs with configuration information b. Slave NAM: NAM Logger that obtains configuration information from a Provisioning NAM Note: This option is only used in a Multiple-NAM setup. Step 8 Provide the following values in the NAM Configuration section: a. Provisioning/Standalone Router Side A: Enter the Side A machine name or IP address of the provisioning Router b. Provisioning/Standalone Router Side B: If a Side B machine exists, enter the Side B machine name or IP address of the provisioning Router Step 9 If you specified a NAM Type of Provisioning/Standalone NAM, skip the Slave NAM Configuration section. If you specified a NAM Type of Slave NAM, specify the following information: a. Provisioning NAM Instance Name: The instance name of the Provisioning NAM b. Provisioning NAM Instance Number: The instance number of the Provisioning NAM c. Provisioning Logger Side A: The Side A machine name or IP address of the Provisioning Logger d. Provisioning Logger Side B: If present, the Side B machine name or IP address of the Provisioning Logger e. Slave Router Side A: The Side A machine name or IP address of the Slave Router f. Slave Router Side B: If present, the Side B machine name or IP address of the Slave Router 42

49 Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Post-Installation Setup and Installing Multiple Components Step 10 Step 11 Click Next. Complete the rest of the Logger setup. Post-Installation Setup and Installing Multiple Components In cases where you want to install more than one Unified ICM component on a single computerâ for example, to install the CallRouter and Logger software on a single nodeâ you must run the Web Setup tool for each component. Similarly, to install a specific component for more than one customer, you must run the Web Setup tool for each instance. Installing NAM CallRouter Software The CallRouter process contains the call routing logic of the system. The CallRouter runs on each NAM and CICM in the Unified ICMH system. During NAM CallRouter installation you set up the following: Enable Remote Network Routing. This option sets up the NAM to send routing requests to the CICM systems. NAM ID. This value is passed with messages sent to a CICM so that the CICM can identify which NAM in the configuration sent the message. How to Install CallRouter Software on the NAM Step 1 Step 2 Step 3 Step 4 Open the Web Setup tool. Select Component Management > Routers in the left frame, then click Add in the right frame. In the first Add Router window, be sure to check the Enable Remote Network Routing box. In the NAM ID field, do the following: a. If your NAM configuration contains only a single NAM, accept the default value of 0. b. If your NAM configuration contains multiple NAMs that might communicate with a single CICM, specify a unique nonzero value. (The same NAM ID is used for Side A and Side B of a given NAM. However, the NAM ID must be different for different instances in a multiple NAM environment.) Step 5 Step 6 Click Next. Complete the rest of the CallRouter setup. 43

50 About Administration & Data Server Types Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Installing a Network Administration & Data Server The Administration & Data Server provides the user interface to the NAM and Unified ICM software. How to Install Network Administration & Data Server Software for the NAM Step 1 Step 2 Step 3 Step 4 Step 5 Open the Web Setup tool. Select Component Management > Administration & Data Servers in the left frame, then click Add in the right frame. In the first Add Administration & Data Server page, select Hosted for the Deployment Type, and also select Network Administration & Data Server for Customer ICM (CICM). Supply values for the other fields in this window, then click Next. Complete the rest of the Administration & Data Server setup. About Administration & Data Server Types There are four possible types of Administration & Data Servers in the Unified CCH environment: Limited (Single Instance) Administration & Data Server: Used by network service provider customers. This type can access data only for its associated instance; it cannot access data from other instances in the same CICM complex or other CICM complexes. Network Administration & Data Server for Customer ICM (CICM): A network Administration & Data Server associated with the CICM systems. Network Administration & Data Server for Network Application Manager (NAM): Used by network service provider personnel. This type has multiple Administration & Data Servers: one for the NAM instance, and one for each associated CICM instance. Configuration-Only Administration Server: HDS is not enabled and real-time reporting is turned off. This deployment only allows configuration changes with no real-time and historical reporting. Note: A separate Configuration-Only Administration Server is required for each CICM instance being provisioned by Cisco Unified Contact Center Management Portal (Unified CCMP). Note: Refer to the Hardware & System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise & Hosted for hardware requirements and sizing guidelines. 44

51 Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted NAM Configuration Data You have the option of installing the Administration & Data Server as an Administration Server and Real-time Data Server (AW), Administration Server, Real-time and Historical Data Server and Detail Data Server (AW-HDS-DDS), or Administration Server and Real-time and Historical Data Server (AW-HDS). Each of these Administration & Data Server roles run as a Windows service and manage several Unified ICM processes. (Refer to the Administration Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted for more details about these roles.) Note: You can either access the shared Administration & Data Server or your own dedicated Administration & Data Server, but not both. The reporting applications, WebView and Unified IC, are used to report on the stored data. NAM Configuration Data At this point, you can start the NAM Logger, CallRouter, and Administration & Data Server, and set up the NAM configuration data. In a two-tier architecture, the NAM system requires only a subset of the normal Unified ICM configuration data. The following table summarizes the configuration data for a NAM. Table Announcement Application Gateway Business Entity Call Type Call Type Map Dialed Number Dialed Number Map Label Network Interface Controller Peripheral Gateway (PG) Prefix Region Routing Client Script Contents Any announcements used in NAM scripts. A remote ICM gateway for each instance on each associated CICM. The default business entity only. Typically, one for each instance. Associate each NAM call type with a NAM script. All dialed numbers used on associated CICMs, plus those used for direct translation. (No default routes are defined for NAM dialed numbers.) Associates dialed numbers and calling line IDs with NAM call types. All labels that can be returned by associated CICMs, plus those used for direct translation. One required for the Network Interface Controller to the carrier network. One or more for the Peripheral Gateway to the carrier network. Any prefixes used in NAM regions. Any regions used in NAM dialed number map. One or more for the carrier network. One or more for each call type. 45

52 Defining CICM Instances and Customers on the NAM Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Defining CICM Instances and Customers on the NAM A process called the NAM Replication Process (NRP) runs on the NAM Logger system. The NRP monitors configuration changes made on the NAM for items such as the dialed number and label for a customer. Whenever you add a dialed number or label on the NAM, the NRP determines which CICM is affected. The NRP then forwards and automatically applies the change to the appropriate CICM. Note: Because the NRP cannot apply updates to records, modifications to dialed number and label strings are disallowed. Database records do not necessarily share the same ID values between NAM and CICM. For example, when you add a dialed number for a customer into the NAM, the record created in the CICM has the same values for DialedNumberString and EnterpriseName, but not necessarily the same value for DialedNumberID. The Dialed_Number.LabelID on the CICM is set to point to a label that is equivalent to the label on the NAM, although the ID values might not be the same. In order for the NRP to function properly, you must do the following: Configure all associated CICMs as ICM instances and customers on the NAM, so that the NRP can forward changes to the appropriate CICM databases. (For instructions, see the "Configuring CICM Instances on the NAM (page 46)" section.) Configure the Administration & Data Servers for each CICM and the customers to allow the NRP to locate the CICM databases to be updated. (For instructions, see the "Configuring CICM Associated Administration & Data Servers on the NAM (page 48)" section.) Define each customer associated with each CICM instance. Associate the routing client on a CICM with a routing client on the NAM, so that customer data on the NAM and CICM can match up. (For instructions, see the "How to Associate a CICM Routing Client with a NAM Routing Client (page 49)" section.) Configuring CICM Instances on the NAM You must perform the following steps to configure an instance for each associated CICM. Note: CICM instance names and numbers are defined on the CICMs. For information, see the CICM Installation and Configuration chapter. Step 1 Step 2 On the NAM, start the Configuration Manager from the Administration Tools folder. The Configuration Manager window opens. Open the Instance Explorer tool by selecting Configure ICM > Enterprise > ICM Instance > ICM Instance Explorer. The ICM Instance Explorer window appears. 46

54 Defining CICM Instances and Customers on the NAM Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Configuring CICM Associated Administration & Data Servers on the NAM You must perform the following steps to configure the primary and secondary Administration & Data Servers associated with the CICM instances you just defined. How to Configure the Administration & Data Servers Associated with the Instance Step 1 Step 2 Step 3 Step 4 Step 5 On the NAM, start Configuration Manager from the Administration Tools folder. The Configuration Manager window opens. Open the Instance Explorer tool by selecting Configure ICM > Enterprise > ICM Instance > ICM Instance Explorer. The ICM Instance Explorer window appears. Click Retrieve. Click Add ICM Instance. (this button does not display) Specify the following on the ICM Node tab: a. ICM Instance (drop-down list). The name for the instance that contains the node. b. System Domain. The name of the Windows security domain that contains the NAM machine. c. System Name. The name of the computer that runs both instances. d. Node Type (drop-down list). The node type: Primary Administration & Data Server or Backup Administration & Data Server. e. Name. The enterprise name for the node. (The default enterprise name is formed by combining the ICM instance, system name, and node type.) f. Configuration Parameter (optional). A string of configuration parameters to be passed to the node at initialization. g. Description (optional). Additional information about the node. Step 6 Click Apply and Done. Defining CICM Customers You must perform the following steps to define each customer associated with each CICM instance. 48

55 Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Installing NAM Cisco Unified Customer Voice Portal PG How to Define a Customer You must perform the following steps to define a customer: Step 1 Step 2 Step 3 On the NAM, in Configuration Manager, choose Enterprise > Customer > Customer List. The Customer Definition List window appears. Click the Add button. Specify the following in the Attributes tab: Name. The enterprise name for the customer. ICM Instance (drop-down list). The name of the instance associated with the customer. Network VRU (drop-down list). The name of the network VRU (if any) associated with the customer. Description (optional). Additional information about the customer. Step 4 Click Save. How to Associate a CICM Routing Client with a NAM Routing Client Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 On the NAM, double-click the NIC Explorer tool. The NIC Explorer window appears. In the Select filter data box, click Retrieve. The NIC tree window appears. Select a NIC. The Explorer tab fields appear. Click the Routing client tab. Set the Network routing client field on the NAM to the same value to appear on the CICM. (For example, you can set it to the enterprise name of the NAM routing client.) Click Done to apply the changes and close the dialog box. Installing NAM Cisco Unified Customer Voice Portal PG The "Configuring the NAM for a Unified CVP PG (page 50)" section describes the procedures to perform to complete NAM Unified CVP configuration and installation. 49

56 Installing NAM Cisco Unified Customer Voice Portal PG Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Configuring the NAM for a Unified CVP PG Step 1 From the NAM Administration & Data Server Configuration Manager, select Explorer Tools > PG Explorer. The PG Explorer window displays. Step 2 Click Retrieve, then click Add (bottom left). The Logical Controller tab displays in the left-hand pane. Step 3 Step 4 Step 5 Enter a Name for the PG in the Name field. Select VRU as the client type from the Client type drop-down menu. Highlight the Peripheral under the PG that you just created (left-hand pane). The Peripheral and associated tabs appear below the logical controller tab. Step 6 In the Peripheral tab, complete the following: Provide a name for the peripheral in the Name field. Verify the Client Type is VRU. If a Unified CVP Application Server is the routing client, then check Enable Post Routing. Otherwise, verify that it is unchecked. If you checked Enable Post Routing in the previous step, then select the Routing Client tab. The Routing Client tab displays. Step 7 In the Routing Client tab, complete the following: Enter a name for the Routing Client in the Name field. The convention is to use the same name as the peripheral with _rc appended to the end of the name; for example, NAM_PG1_rc. Enter the same name as above in the Network Routing Client field. Verify that the Network Transfer Preferred checkbox is NOT checked. Step 8 Click Save. Note: After you click Save, a Logical Controller ID and Peripheral ID are assigned to the PG and its associated peripheral(s). Note these numbers for the next task. 50

57 Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Installing NAM Cisco Unified Customer Voice Portal PG How to Install a NAM Unified CVP PG You must install and configure at least one Unified CVP PG for your hosted system. You need the following information: Peripheral Gateway DMP Configuration ID, which you specify during Router setup Peripheral Gateway Logical Controller ID, which you specify during Peripheral Gateway configuration Step 1 Step 2 On the machine to be used as the NAM PG, run Peripheral Gateway Setup. Click Add in the Instance Components section and select Peripheral Gateway from the ICM/CCE/CCH Component Selection window. The Peripheral Gateway Properties window displays. Step 3 Step 4 Step 5 Leave Auto Start at System Startup unchecked. The server might need to be rebooted a number of times during installation, and problems could occur if the node starts before Service Releases and/or databases are applied. Specify whether the PG is part of a duplexed pair. In the ID field, select the PG device identifier (as enabled in the CallRouter s DMP Configuration dialog) from the pull-down menu. Note: Each logical PG must have a unique device assignment at the CallRouter. (If a PG is duplexed, both physical machines use the same device assignment.) To add another logical PG, you must enable another PG device for the CallRouter. For example, if you checked only box number 1 during the CallRouter setup, then you must select the ID PG1 from the drop-down list. Step 6 Step 7 If the PG is duplexed, specify whether you are installing Side A or Side B. If the PG is simplexed, select Side A. In the Client Type Selection area, select the type of Peripheral Gateway you want to add. Use the Add and Remove buttons to select or de-select PG types. You can install one PG type and one VRU PG at the same time. Note: For an Unified CVP PG you must select VRU as one of the client types. Step 8 Click Next. The Peripheral Gateway Component Properties window displays. Step 9 In the Peripheral Gateway Configuration section of the window, enter the Logical Controller ID from the Logical_Interface_Controller record for the PG. 51

58 Installing NAM Cisco Unified Customer Voice Portal PG Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Note: You can view the Logical_Interface_Controller record for the PG using the PG Explorer tool from the Configuration Manager on the NAM AW. Step 10 The VRU Reporting options are available only if the PG supports VRUs. Select the option that you want to use for VRU reporting. Note: For a typical application you should select Service Control and check Queue Reporting. Step 11 In the Peripheral Interface Managers section, click Add. The Add PIM dialog displays. Step 12 Step 13 Select VRU for the Client type. Select an available PIM from the Available PIMs list. The list contains only PIM numbers that are not already defined for this PG. Step 14 Click OK. The VRU configuration dialog displays in which you can enter the properties of the peripheral. Step 15 Step 16 Step 17 To put the PIM into service, check the Enabled option. This allows the PIM to communicate with the peripheral when the Peripheral Gateway is running. Enter the peripheral name in the Peripheral name field. In most cases, you will want to use the enterprise name from the associated Peripheral record. Enter the Peripheral ID from the Peripheral record. Note: You can view the Peripheral ID of the PG using the PG Explorer tool in the Configuration Manager on the NAM AW. Step 18 Step 19 In the VRU Host Name field, enter the name or IP Address by which the VRU is known to the network Enter the number of the VRU port that the PG connects to. Typically, port 5000 is the default for a Unified CVP Application server. Step 20 Step 21 In the Reconnect Interval field, specify how often the PG should try to re-establish a lost connection to the VRU. In the Heartbeat Interval field, specify how often the PG should check its connection to the VRU. Note: The defaults for the Reconnect Interval and Heartbeat Interval are usually appropriate. Step 22 Step 23 Click OK to set the values and close the VRU dialog. Click Advanced. 52

59 Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Installing NAM Cisco Unified Customer Voice Portal PG The MDS and DMP Properties dialog displays. Note: Your network design might dictate different settings than the defaults; change as appropriate. (Click Help for more information on this window.) Click OK. Step 24 Click Next. The Device Management Protocol Properties window displays. Step 25 If you prefer that the PG communicate with one side or the other of the Central Controller (for example, if the PG is collocated with one side), indicate the preferred side. Whether you specify a preferred side or not, if the PG cannot communicate with one side, it will automatically switch to the other. Step 26 For the Side A properties, and if applicable the Side B properties, define the following: Indicate whether the PG is local to or remote from each side of the Central Controller. If the PG is remote from either side, specify the maximum amount of bandwidth (in bits per second) the PG can use for communication with the CallRouter. Use this option to prevent the PG from overloading the wide-area network. If the CallRouter is not local, in the Bandwidth fields, input the bandwidth for the WAN link to the CallRouter side A and side B. In the case that QoS is not an intended feature, you do not need to worry about how to divide the link bandwidth into each priority. The sum for the three priorities, however, must be the physical bandwidth you actually have, and the input for each priority must be at least 1K (1024) bps. For QoS connections, you need to enter the appropriate bandwidth value for the High, Medium and Low priority individually. Consult with you network administrator or Cisco representative to determine the bandwidth requirements for your network. Step 27 Step 28 Click Next. The Peripheral Gateway Network Interfaces dialog displays. In the Private Interfaces section, enter the TCP/IP addresses (or host names) of the private network for the PG machines (PG private A, PG private A high) and, if it is duplexed, its pair (PG private B, PG private B high). If the PG is simplexed, enter localhost for the B side addresses. In the Visible Interfaces section, enter the visible network addresses (or host names) for the PG (PG visible A, PG visible B)and CallRouter (Router visible A, Router visible A high, Router visible B, Router visible B high) machines. (Refer to the Pre-installation Planning Guide for Cisco Unified ICM Enterprise and Hosted for detailed information about setting the Central Controller network interfaces.) If simplexed, enter localhost for the B side addresses. Step 29 Step 30 If you want to use the QoS feature for your private interfaces and/or your visible interfaces, click the appropriate QoS button. A QoS Settings dialog displays. Verify that Use Packet Scheduler is checked. 53

60 Installing NAM Cisco Unified Customer Voice Portal PG Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Step 31 Step 32 Set the DSCP (DiffServ Codepoint) marking for each priority of the ICM traffic going to the CallRouter. The defaults are acceptable if your network is Cisco AVVID compliant (Architecture for Voice, Video and Integrated Data). Otherwise, you need to consult your network administrator or Cisco representative for the proper values for these fields. Uncheck the Use Packet Scheduler box, if you plan to use the Microsoft Packet Scheduler utility. This changes the appearance of the PG QoS DMP Properties Advanced Options window. The edit boxes for Medium Priority are grayed out and the Medium Priority always has the same settings as the High Priority. This is because Microsoft Packet Scheduler supports at most two classification levels (except best effort). In addition to DSCP marking, the Class-of-Service (802.1p) marking is supported. The default values are set in compliance with Cisco AVVID recommendations. Consult your network administrator or Cisco representative for changes. Note: Microsoft Packet Scheduler must be installed separately from the setup process, if you uncheck the Bypass Packet Scheduler box. For more information about QoS for the system software, refer to the Pre-installation Planning Guide for Cisco Unified ICM Enterprise and Hosted. Step 33 Click OK. You are returned to the Peripheral Gateway Network Interfaces window. Step 34 Click Next. The Check Setup Information window displays. Step 35 Ensure that the settings displayed are as you intended. If you want to modify any settings before proceeding, click Back. When the settings are correct, click Next to begin copying files. The copying process may take several minutes to complete. You can continue with other work while the setup process operates in the background. Note: For specific information about what the Peripheral Gateway Setup utility installs, refer to the Installation Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted and the Peripheral Gateway Setup online help. Step 36 Step 37 When the setup process successfully copies all the files, it displays the final window and asks whether you want to start the ICM Node Manager now. Do not start the Node Manager until you have completed the entire Unified ICM installation. Click Finish to exit Peripheral Gateway Setup and optionally start the Node Manager. If you choose to start the Node Manager, it automatically starts the other Unified ICM processes on the PG. 54

61 Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Installing and Configuring NAM NICs and PGs Installing and Configuring NAM NICs and PGs This section provides guidelines for configuring network interface controllers (NICs) andperipheral gateways (PGs) for the NAM. Network Interface Controllers Refer to the Installation Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted, and the System Manager Guide Supplement for your particular NICs for guidelines and procedures. Peripheral Gateways To support duplexed operation, the NAM must also communicate with at least one Peripheral Gateway device. (In a duplexed environment, a CallRouter does not route calls when the duplexed partner has nodal or network failure unless it has active connections to a majority of the PGs and it cannot see the other CallRouter. This prevents both CallRouters from trying to route simultaneously.) Therefore, you must define at least one Peripheral Gateway for the NAM. You can run the Peripheral Gateway on one of the Administration & Data Server machines associated with the NAM. The Peripheral Interface Manager (PIM) on the PG need not be enabled. How to Configure Device Management Protocols for NAM PGs Follow the steps described in the Peripheral Gateway Setup online help to set up a Peripheral Gateway. This includes instructions for the Device Management Protocol Properties dialog. Creating a Cisco Unified Intelligent Contact Management Application Gateway to Access CICM Instances After adding the instance components to the CICM, you must configure a Unified ICM Application Gateway in Configuration Manager on an Administration & Data Server associated with the NAM. (The Unified ICM Application Gateway is the path a NAM takes to access a CICM.) After the Unified ICM Application Gateway is configured, you can reference it using a Unified ICM Application Gateway node within a routing script on the NAM. How to Create a Cisco Unified Intelligent Contact Management Application Gateway Step 1 Step 2 Within Configuration Manager on an Administration & Data Server associated with the NAM, select Calls > Application Gateway > Application Gateway List. The Application Gateway List window appears. Click Retrieve. 55

62 Installing and Configuring NAM NICs and PGs Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Step 3 Click Add. The Attributes tab appears. Figure 6: Application Gateway List Window Step 4 Specify the following values on the Attributes tab: Name. Enter a name for the Unified ICM Application Gateway. Type. Select Remote ICM. Preferred Side. Indicates the preferred side of the Unified ICM Application Gateway to use when both are available. If only one side is available, the system software uses that side regardless of preference. This option applies only for Custom Gateways. For Remote ICM systems, the preference is indicated by a suffix on the connection address. Encryption. Indicates whether requests to the Unified ICM Application Gateway are encrypted. Select None. Fault Tolerance. If the Unified ICM Application Gateway is duplexed, specifies the fault-tolerance strategy it uses. Connection. Select whether the Unified ICM Application Gateway is Duplex (has both a Side A and Side B connection), Simplex A (only has a Side A), or Simplex B (only has a Side B). Description (optional). Additional information about the Unified ICM Application Gateway. Step 5 Click Save to create the Unified ICM Application Gateway. 56

63 Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Installing and Configuring NAM NICs and PGs Note: Make a note of the Unified ICM Application Gateway ID value, as you will need it when you run the Web Setup tool to configure the INCRP NIC on the CICM. Step 6 Step 7 To set the connection information, click the Connection Side A tab or the Connection Side B tab. To specify an address, click the Enter Address button. The Enter NAM Addresses dialog box appears. Figure 7: Enter NAM Addresses Dialog Step 8 Specify the following information: NAM Mode. Select Single NAM or Multiple NAMs, depending on the number of NAMs connected to the selected Unified ICM Application Gateway. IP Address/Name. Enter the Public (high priority) IP address of the CICM. Alternatively, the SAN can be used (consult your Cisco certified partner or TAC for assistance). This address must be the same address specified for the INCRP NIC on the CICM. (You can use the hostname in place of the address.) Instance Number. Enter the number of the customer ICM on the CICM (0 through 24). Side. Indicate which side of the NAM prefers this connection: Side A. NAM Side A prefers to use this connection. Side B. NAM Side B prefers to use this connection. None. Neither side of the NAM prefers to use this connection. Both Side A and B. Both sides of the NAM prefer to use this connection. 57

64 Upgrading the NAM Chapter 5: NAM Installation and Configuration for Cisco Unified Contact Center Hosted Note: Consider network traffic in choosing this value. For example, if one side of the NAM is collocated with only one side of the CICM, you can make that the preferred connection in order to avoid unnecessary WAN traffic to the other side. NAM ID. This field appears only if you select a NAM Mode of Multiple NAM. Enter the NAM ID. Step 9 Step 10 Set the In Service field to indicate whether this connection is currently available for use by the system software. When finished, click Save. The bottom half of the connection tab displays a number of timeout and limit values. The defaults for these values as shipped may not be appropriate for a NAM system; these values are highly configuration-dependent. A rough guideline is that the CICMsâ timeout value be less than the timeout value for the NAMâ s NIC. How to Set Default Values for the Cisco Unified Intelligent Contact Management Application Gateway Step 1 Step 2 Within Configuration Manager, select Enterprise > System Information > System Information. The System Information dialog box appears. In the Application Gateway section, select the Remote ICM radio button. Figure 8: System Information Dialog Step 3 Step 4 Use the Timeouts, Sessions, Heartbeats, and Error tabs to set the default values for the Unified ICM Application Gateway connections. (The Unified ICM Application Gateway timeout settings for a CICM must be set keeping in mind the NAM NIC settings for timeout, late, and so on.) When finished, click OK to make the changes and close the dialog box. Upgrading the NAM For instructions on how to upgrade a NAM system, refer to the Upgrade Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted. 58

66 CTI OS Server Installation Guidelines Chapter 6: Installing and Configuring CTI OS Server for Cisco Unified Contact Center Hosted Following are some guidelines to consider when you install CTI OS Server. CTI OS is typically installed in a duplex configuration. Two CTI OS servers installed on separate systems work in parallel to provide redundancy. Installing only one CTI OS server would prevent failover recovery by client systems. Refer to the Startup, Shutdown, and Failover discussions in the CTI OS System Manager's Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted (http://www.cisco.com/en/us/products/sw/custcosw/ps14/ tsd_products_support_series_home.html) for more information on CTI OS failover. CTI OS must be installed on the same server on which the PG/CG is installed, then you can start the CTI OS Service. Ensure that your CTI OS system meets the minimum hardware and software requirements, as listed in the Hardware & System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise & Hosted (http://www.cisco.com/en/us/products/sw/ custcosw/ps5053/tsd_products_support_series_home.html). How to Install the CTI OS Server The CTI OS Server must be installed on the same system where the PG and CG are installed. If you are performing a new install of the CTI OS Server altogether, perform the following steps. Note: For instructions on upgrading the CTI OS Server from a previous version, refer to the CTI OS System Manager's Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted (http://www.cisco.com/en/us/products/sw/custcosw/ps14/ tsd_products_support_series_home.html). Step 1 Step 2 Run the PG Setup tool (accessed from the Unified CCE Tools folder) to install the CTI OS Server. Click Yes on the Software License Agreement window. The CTI OS Instance list dialog displays. Step 3 In the CTI OS Instance List section, click Add. The Add CTI OS Instance dialog displays. Step 4 Specify an Instance Name value by selecting the correct ICM instance name that has already been configured for this instance of CTI OS, and click OK. The CTI OS Instance list dialog redisplays, displaying the new Instance Name. Step 5 In the CTI OS Server List section, click Add. The Add CTI OS Server Instance dialog displays. Step 6 If you are installing CTI OS Server for the first time, a dialog displays. Accept the default installation drive or select another drive from the pulldown list and click OK. 60

67 Chapter 6: Installing and Configuring CTI OS Server for Cisco Unified Contact Center Hosted CTI OS Server Installation Guidelines The CTI Server Information window displays. Step 7 Enter the Name or IP Address and the Port Number for your CTI systems and click Next. The Peripheral Identifier window displays. Step 8 Specify the following information: A Logical Name for your peripheral. This can be any valid logical name that uniquely identifies your peripheral. Note: Only Peripheral Types of Unified CCE, Unified SCCE, and Unified CCH have the Login By group box enabled where you can choose between logging in by Agent ID or by Login Name. The Login By setting determines how CTI Toolkit Agent and Supervisor desktops allow Login and Chat request (either AgentID OR LoginName). This setting does not affect other CTI applications. CTI OS Server itself can service Login requests both ways (by AgentID and by LoginName) for Unified CCH. All other peripheral types will login by Agent ID only, and the choice is disabled. If this is to be a multi-instance environment, select Unified CCH. The Peripheral ID associated with the switch connection. The Peripheral Type of the switch connection. Note: You can specify information for only one peripheral during CTI OS Server setup. To configure additional peripherals, follow the procedure in the section describing Automatic Agent Statistics Grid Configuration in CTI OS Configuration in the CTI OS System Manager's Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted (http:// Step 9 Click Next. The Connection Information dialog displays. Step 10 Enter the port number and heartbeat information for your CTI OS server instance. Note: For an Unified CCH peripheral type, only the first instance can have this port. Subsequent ones must have the port number incremented by 1 (i.e , 42030, etc.), taking care to configure the clients that connect to them with the same port in their installs. (For all non-unified CCH peripheral types, the Listen Port must be left at the default value of ) Step 11 Click Next. The Statistics Information dialog displays. Step 12 Accept the default polling value or enter the polling interval for Skillgroup statistics (in seconds). Note: Since QoS enablement and statistics enablement are mutually exclusive, enabling QoS zeros and disables all of the information relating to statistics. Step 13 Click Next. 61

68 CTI OS Server Installation Guidelines Chapter 6: Installing and Configuring CTI OS Server for Cisco Unified Contact Center Hosted The Peer CTI OS Server window displays. Step 14 Optionally, configure a Peer Server for Chat, Silent Monitoring, and to support fault tolerance and the failover mechanism built into the product: Enable the Duplex CTI OS Install checkbox. Specify a Peer CTI OS Server value. Specify a Port value. Step 15 Click Add Server. The CTI OS Server information is added to the system and the CTI OS Server Security dialog displays. Step 16 Do one of the following: To enable security, select the Enable Security checkbox and click OK. To disable security, click OK. CTI OS Server Security Install Schield Wizard dialog displays. Note: Refer to the CTI OS System Manager's Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted (http://www.cisco.com/en/us/products/sw/custcosw/ps14/ prod_installation_guides_list.html) for detailed security setup information. Step 17 Click Next; when CTI OS Server Security Setup is complete, click Finish. The system asks whether to restart your computer now or later. Step 18 Do one of the following: Select Yes; your machine reboots, then restarts the PG Setup tool. Select No; the CTI OS Instances dialog apears. Step 19 For the Unified CCH peripheral type, click Add and follow the procedure described upon to create additional instances. Note: For any other peripheral type, the Add button under the Instance List is disabled after one instance is created. CTI OS Multi Instance setup does not allow two or more CTI OS Servers to connect to the same CTI Server. Also, it does not allow two or more CTI OS Servers to use the same listen port. Step 20 When finished creating instances, click Exit Setup. 62

69 Chapter 6: Installing and Configuring CTI OS Server for Cisco Unified Contact Center Hosted CTI OS Failover How to Start CTI OS Service After Installation The CTI OS Server runs as a service on the host Windows 2000/2003 computer. The Unified CCE Service Control application is an interface into the Windows platform s service control manager, which start and stops services. To start, stop, or cycle the processes in the CTI OS Server, use the appropriate tabs from the Unified CCE Service Control window. Use the following procedure to start the CTI OS Service: Step 1 Step 2 Step 3 On the CTI OS Server machine, open Unified CCE Service Control. Select CTI OS Service. Click Start. Table 6: CTI OS System Processes When the CTI OS service starts, it launches processes listed in the following table. Some of these processes open and run in console windows. These windows can be minimized, but cannot be closed. Closing the console window in which a process is running forces a restart of that process. Process Name CtiosServerNode NM NMM Process Description The main CTI OS Server process. This process manages all CTI OS objects and listens for and manages client connections The ICM NodeManager (fault tolerance manager). Each ICM service is started by NodeManager, and NodeManager restarts any abnormally terminated processes. The ICM NodeManagerManager (system fault tolerance). Each ICM No Node (that is, CTI OS) starts up a NMM process to handle system-level faults. In the event of a unrecoverable system fault, NMM will restart the host computer. Runs In Console Window Yes No CTI OS Failover The CTI OS Server is a fault-tolerant server. The server processes are managed by a fault tolerance/recovery platform called NodeManager. NodeManager creates and monitors each process running as part of the CTI OS service, and automatically restarts abnormally terminated processes. For more information about CTI OS Failover, see the CTI OS System Manager's Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted (http://www.cisco.com/en/us/ products/sw/custcosw/ps14/tsd_products_support_series_home.html). 63

71 Chapter 7 Installing and Configuring Outbound Option for Cisco Unified Contact Center Hosted Outbound Option is a feature of Unified CCH that provides outbound dialing functionality along with the existing inbound capabilities of Unified CCH. With Outbound Option, contact centers can be configured for automated outbound activities. Agents who are not busy handling inbound requests can perform outbound calls, thereby maintaining a high level of agent productivity. For Unified CCH, a Cisco voice gateway is required to place customer calls. Configuring Outbound Option Multi-Tenant Customer Instances Release 8.0(1) of Outbound Option allows multiple customer instances to run Outbound Option in a Hosted environment. This new feature, known as Outbound Option Multi-Tenant, is available in Outbound Option deployments that use the SIP Dialer. In a Multi-Tenant environment, there are certain configuration values that you must set for each customer instance: You must set the number of agents when configuring each customer instance. Note: For instructions on how to set and configure the number of agents for a customer instance, refer to the Setup and Configuration Guide for Cisco Unified Contact Center Hosted. You must set Port Throttling for each customer instance in the Dialer General tab of the Outbound Option Configuration tool. Note: See the "Configuring the Dialer Component (page?)" section for more details. For the SCCP Dialer, you can optionally enable recording of sessions by turning on the CPARecordWaveFile registry value. For the SIP Dialer, you can enable recording of sessions 65

72 Configuring Outbound Option Multi-Tenant Customer Instances Chapter 7: Installing and Configuring Outbound Option for Cisco Unified Contact Center Hosted in ICM Configuration Manager. On the Outbound Option Campaign Purpose tab, check Call Progress Analysis (CPA), and also check Record CPA. Note: See Appendix A for more details. You must set the Do Not Call List size and the number of Dialer ports for each customer instance using the configlimits tool (see the next section for details). Using the ConfigLimit Tool to Change Multi-Tenant Parameter Limits Each customer instance database contains Configuration Limit scalability records. The two records kept concerning Outbound Option are the size (in Records) of the Do-Not-Call List to be imported, and the maximum number of Dialer Ports available for a specific customer instance of outbound Option. You can change these values with the Configuration Limits (configlimit) tool. Perform the following steps: Step 1 Run the configlimit tool by selecting Start > Run from the Windows menu, then entering configlimit. Note: Run configlimit on the same machine as the Distributor for the instance you want to configure. If more than one instance of the Administraion & Data Server is installed on the Distributor machine, use the Select Administration Server tool to select the instance you want to configure. Step 2 Step 3 If you want to obtain the currently configured multi-tenant parameter limits, run the following command: cl /show To change a multi-tenant parameter limit, enter a command in the following format: cl /id [ConfigLimitID] /value [ConfigLimitCurrentValue] [/update] where: ConfigLimitID = the ID for the multitenant parameter that you want to change. Possible values are: Skill_Groups_Per_Agent MA_DNC_LIST_SIZE MA_SIP_PORTS ConfigLimitCurrentValue = the new limit for the parameter. Note: The configlimit tool only allows the changing of the ConfigLimitCurrentValue. You cannot change the ConfigLimitDefaultValue. 66

79 Advanced Services and Feature Control Advanced Services allows service providers to offer call center routing services to end-customers independent of any end-customer equipment, such as ACDs, PBs, key systems or even simple analogue phone lines. This section describes how to set up and administer an Advanced Services instance. Note: For information about the relationship between Advanced Services and Customer Concept, refer to the Setup and Configuration Guide for Cisco Unified ICM Hosted. This chapter contains the following topics: Chapter 10 Introduction, page 73 Setup and Configuration of an Advanced Services ICM Instance, page 74 Configuration of New Advanced Services Customer, page 76 Introduction There is a special ICM instance that is used for Advanced Services. The Advanced Services ICM is a multi-customer instance. A single Advanced Services ICM can support large numbers of customers. Advanced Services customers have web-based tools to control and manage their call routing, specifically WebView and Unified IC for reporting and Internet Script Editor for call routing. An Advanced Services ICM is an ICM instance just like any other, but it is configured differently. This means that a CICM complex can run a single Advanced Services ICM and a maximum of 24 CICMs. However, for performance reasons it is desirable to run an Advanced Services ICM on its own dedicated hardware. To support multiple subscribers on the same Advanced Services ICM, Advanced Services has a particular concept of a customer. A customer is an organization that uses Unified ICM to manage its call center. Each customer has its own configuration elements, such as dialed numbers, labels, call types, scripts, VRU scripts and scheduled targets. All these configuration elements 73

80 Setup and Configuration of an Advanced Services ICM Instance Chapter 10: Advanced Services and Feature Control are stored in the same Advanced Services ICM database, but the reporting and scripting tools will make sure that a specific customer only has access to his own data. Since Advanced Services customers do not have ACD and Peripheral Gateways there are no configuration elements like peripherals, services, skill groups, and so forth. No special security is applied at the customer level. Any Administration & Data Server user with access to the Advanced Services ICM instance can choose to view data for any or all customers in that instance. So the Service Provider can use the Administration & Data Server to administer the Advanced Services ICM as any other ICM instance. Advanced Services customers must only have access to their data using WebView, Unified IC, and Internet Script Editor. These tools will prevent a customer from accessing other customer data. This is achieved by having a user login with a personal userid and password. The user ID is tied to a specific customer and WebView, Unified IC, and Internet Script Editor will only expose this customer's data. Each individual user also has a profile, called a Feature Set, that determines his or her access rights in detail. The following table provides an overview of the tools used by the Service Provider and the end-customer for day-to-day management tasks. Task Configuration Scripting New scripts Structural script changes Changing script parameters Reporting Defining and running report based on existing template Defining custom reporting template Service Provider (Tool) Configuration Manager Administration & Data Server Script Editor Administration & Data Server Script Editor Administration & Data Server Script Editor WebView and Unified IC, using Call Type reporting and scheduling, exporting and options Using Sybase InfoMaker to define new Call Type templates End-user (Tool) N/A Internet Script Editor in full edit mode Internet Script Editor in full edit mode Internet Script Editor in quick edit mode WebView and Unified IC, using Call Type reporting N/A Setup and Configuration of an Advanced Services ICM Instance The following steps are required to setup and configure an Advance Services ICM instance. These steps assume that a NAM has been setup with at least one Network VRU connected to it. Install a new ICM instance. This includes installing a Logger, Router with INCRP NIC and one or more Administration & Data Servers (Administration & Data Server instances) for the Service Provider to manage the service. Do not configure or install any Peripheral Gateways (PGs), since they are not used by Advanced Services. 74

81 Chapter 10: Advanced Services and Feature Control Setup and Configuration of an Advanced Services ICM Instance Install one or more WebView, Unified IC, and Internet Script Editor Servers that will act as web servers for end-customer use. A WebView or Unified IC server will fetch real-time data for reporting purposes from its local Administration & Data Server (if installed on an Administration & Data Server) or from another Administration & Data Server's real-time Administration & Data Server. Historical data will be fetched from an Administration & Data Server with the Historical Data Server (HDS) option installed. This could be the same or a different Administration & Data Server as the WebView or Unified IC server. The remainder of the setup is identical to setting up a regular Administration & Data Server. Configure the Network VRU. Only Network VRUs of Type 3, 5, 6 or 7 are supported with Advanced Services. Enter customer specific configuration data using Configuration Manager. For each customer this consists of the elements listed in the following table. Data elements Customer Feature Control Set User Call Type Dialed Number Label Label List Scheduled Target Routing Script Required/optional Required Required (although generic, non-customer specific feature control sets can be used) Required (but see the "User (page 77)" section) Required Required 1 Required unless dynamic labels are usedâ which they must not be because of security reasons Optional Optional Required unless performed by the customer using Internet Script Editor Tool used to configure ICM Instance Explorer Feature Control Set List User List Call Type List Dialed Number List Label List Network VRU Script List Scheduled Target Explorer Script Editor The next section describes these steps in detail. Enter customer specific configuration data in the NAM. This is identical to normal ICM instances and is only summarized here. The main customer specific configuration elements in the NAM are: Labels Dialed Numbers 1) Population of Dialed Numbers and Labels in the Advanced Services ICM can be automated when CICM replication is used. See Chapter 4, â œcustomer Concept.â 75

82 Configuration of New Advanced Services Customer Chapter 10: Advanced Services and Feature Control Routing Script to forward route requests to the Advanced Services ICM Customer (required only for CICM replication) Configuration of New Advanced Services Customer For each new Advanced Services customer, the following configuration elements need to be defined by the Service Provider. For more information, refer to the Configuration Guide for Cisco Unified ICM/Contact Center Enterprise and Hosted, the Configuration Manager online help, and the Installation Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted. Feature Control Set Perform the following steps to configure Feature Control Set. Step 1 Step 2 Step 3 Step 4 Access the Select Administration Instance tool by selecting Start > All Programs > Cisco Unified CCE Tools > Administration Tools > Select Administration Instance. The Select Administration Instance window appears. Select the instance you will be configuring. From within the Administration Tools folder, double-click the Configuration Manager. Open the Feature Control Set List tool (Tools > List Tools > Feature Control Set List). The Feature Control Set List window appears. Configure a Feature Control Set that contains the maximum number of elements that this customer can get access to. Since an Advanced Services customer will never use the Configuration Manager, uncheck all check boxes. Under the Script Editor application, click Advanced. Under Edit Options, select either Full Editor, or Quick Edit. This determines what edit mode this user is allowed to use. Under Node Control uncheck each Script Node that this profile must not provide access to. For Advanced Services, the following nodes must always be unchecked, since they are not permissible with Advanced Services: Agent Agent to Agent DB Lookup Enterprise Service Enterprise Skill Group 76

83 Chapter 10: Advanced Services and Feature Control Configuration of New Advanced Services Customer Gateway ICM Gateway Queue to Agent Route Select Select Service Skill Group Translation Route to VRU In particular, the DB Lookup and Gateway nodes must not be allowed end-customer access since they might expose other customer data. It is possible for Advance Services Scripts to use these nodes for database lookups. The DB Lookup and Application Gateway configuration must be controlled entirely by the Service Provider and not by the end-customer. An end-customer must not get access to these nodes since it will expose other customers' databases and external applications. This implies that end-customers do not have full edit access to routing scripts containing these nodes, since they will not be able to full edit scripts that include these nodes. Note: Creating a custom DB on the Logger or HDS is not supported. Multiple Feature Control Sets can be defined for a single customer. Feature Control Sets are assigned to a user (not a customer), so that different users can have different levels of access. Customer Using ICM Instance Explorer, configure a new Customer under the Advanced Services ICM Instance. Select a Network VRU to be used by this customer and the customer level Feature Set. This Feature Set is used for users associated with this Customer, unless the user is associated with a different Feature Set in the User List tool. User Note: You only need to use the User List tool if the user will have restrictions (such as Feature Control or Read-only); otherwise, the user can be given access using Domain Manager. Using the User List tool, configure one or more users for this customer. In the Domain name field, select the Active Directory (AD) Domain that this user's AD domain account is going to be created in. This would typically not be the CICM domain, but a separate domain specific to the WebView, Unified IC, and Internet Script Editor servers. The User name for this user. This becomes the AD domain username as well. 77

84 Configuration of New Advanced Services Customer Chapter 10: Advanced Services and Feature Control The user's Password. This becomes the AD domain user's password as well. The Customer created using the ICM Instance Explorer, or All Customers. Select the Feature Control Set that is to be associated with this user. If the setting chosen is <None>, the Customer level feature control set will be used. Checking Configuration gives the user access to Configuration Manager and Script Editor. If you also check Read only, the user cannot make any changes using Configuration Manager or Script Editor. In any case, the user's feature control set determines which routing scripts the user can access. Checking Setup gives the user access to Setup, Configuration Manager, Script Editor, and WebView. Checking WebView gives the user access to WebView. Note: This checkbox is not applicable when deploying Unified IC. Call Type Configure one or more call types for this customer using the Call Type List tool. Select the associated customer from the Customer drop-down menu. Figure 9: Call Type List Dialog Dialed Number Configure one or more Dialed Numbers for this customer using the Dialed Number List tool. On the attributes tab, select the associated customer from the Customer drop-down menu. 78

85 Chapter 10: Advanced Services and Feature Control Configuration of New Advanced Services Customer Figure 10: Dialed Number List Tool On the Dialed Number Mapping tab, select a Call Type mapping for this Dialed Number. The tool will only show Call Types defined for the customer selected on the attributes tab. Scheduled Target Configure one or more Scheduled Targets for this customer using Scheduled Target Explorer. Select the associated customer from the Customer drop-down menu. Figure 11: Scheduled Target Explorer Tool Label You can add one or more Labels for each Scheduled Target using this tool or using the Label List tool. In either case, select the same customer for the Label as selected for the Scheduled Target. Select the associated customer from the Customer drop-down menu. 79

86 Configuration of New Advanced Services Customer Chapter 10: Advanced Services and Feature Control Figure 12: Label List Dialog Observe the following guidelines for labels: If this is a standard Label to be used in a Label or Divert Label node, leave the Target Type and Network Target set to None. If this is a Label for a Scheduled Target Type, select the Scheduled Target from the Network Target drop-down menu. You can configure multiple labels for Scheduled Targets, but for a specific Routing Client only the first label will be used; therefore, when you configure multiple labels, configure each for a different Routing Client. Configuring more than one label for the same Routing Client will have no effect. Network VRU Script Configure one or more Network VRU Scripts for this customer using the Network VRU Script List tool. Select the associated customer from the Customer drop-down menu. Figure 13: Network VRU Script List Tool Routing Script The Service Provider can either create routing scripts for the customer or the customer can use Internet Script Editor to create routing scripts himself. 80

87 Chapter 10: Advanced Services and Feature Control Configuration of New Advanced Services Customer When the Service Provider is creating routing scripts for an end-customer, the scripts are not automatically associated with any specific customer. Use the following action to associate a script with a specific customer, so that the customer can get access to it: Make sure the script is saved. Using Script Editor, select Script Explorer from the File menu. Under All Customers, Default business unit, locate the script(s) to associate with a specific customer and drag them over to the customer's Default business unit. Dragging the mouse pointer to the customer and holding it there briefly will show the default business unit. 81

89 Chapter 11 Scripting Considerations This section covers scripting consideration to use in a Unified CCH system. For more details on scripting in a Unified ICM/NAM environment, refer to the Scripting and Media Routing Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted (http://www.cisco.com/ en/us/products/sw/custcosw/ps1001/products_user_guide_list.html). This chapter contains the following topics: NAM Script Configuration, page 83 CICM Scripting Considerations, page 87 NAM Script Configuration Scripting on the NAM only requires one Dialed Number script per Customer Instance; however, your design might include more. The NAM routing script sends the dialed number to the correct Unified CVP Media Server for treatment, then ultimately to the ICM Gateway of the CICM instance for the particular Dialed Number. 83

91 Chapter 11: Scripting Considerations NAM Script Configuration Figure 15: NetworkTransferEnabled Set Variable Node After you have set the variable for NetworkTransferEnabled you can create a Dialed Number (DN) Node to route to a particular CICM Instance Routing Client. If the Dialed Number node is true, then you typically send the call to the Unified CVP Media Server using another Set Variable node as described below. The first script node after the star should be a set variable node that contains the following: Object Type Call Object (no selection) Variable user.microapp.media_server Value the IP address of the Unified CVP Media Server, enclosed in quotes, for example " " 85

92 NAM Script Configuration Chapter 11: Scripting Considerations Figure 16: ECC Variable user.microapp.media_server Set Variable Node At this point, scripting is conducted on the Unified CVP. (Refer to the Configuration and Administration Guide for Cisco Unified Customer Voice Portal (http://www.cisco.com/en/ US/products/sw/custcosw/ps1006/products_installation_and_configuration_guides_list.html) for details on scripting in Unified CVP.) Finally, the call is sent to the Unified ICM gateway of a particular customer instance. If multiple DNs are used, then you can send the call to a different Unified CVP Media Server based on the different DN, as in the Example NAM Routing Script (page 84) figure preceding. Finally, the call is sent to the Unified ICM gateway of a particular customer instance. Add an ICM Gateway Node and select the customer to which to route the call. Figure 17: ICM Gateway Properties - Send Tab 86

93 Chapter 11: Scripting Considerations CICM Scripting Considerations Note: Do NOT select the Validate returned labels checkbox. If you do so, you will have to provision the NAM with all of the labels that exist on every customer instance. CICM Scripting Considerations Refer to the Scripting and Media Routing Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted at products_user_guide_list.html for general scripting requirements for a CICM Instance. Consult the Configuration and Administration Guide for Cisco Unified Customer Voice Portal at /www.cisco.com/en/us/products/sw/custcosw/ps1006/ products_installation_and_configuration_guides_list.html, for Unified CVP additional scripting considerations. Create CICM VRU Scripts VRU Scripts differ from Unified ICM routing scripts. A configured VRU Script runs only when the system software instructs it to do so from a Unified ICM routing script. A VRU Script on Unified ICM is the configured record for the VRU script that resides on the Unified CVP. A VRU Script executes to collect digits, play hold music, or perform many other common IVR functions. Step 1 From the Configuration Manager, select Targets > Network VRU Script > Network VRU Script List. The Network VRU Script List dialog displays. Step 2 On the Attributes tab, enter the configuration information for the BasicQ script as follows: a. Network VRU Enter isnvru. b. VRU Script Name Enter script name (for example, BasicQ). c. Name Enter the script file name (for example, BasicQ.aef). d. Timeout [seconds] Enter 180. e. Configuration param Leave blank. f. Customer Select the same Unified ICM customer you selected for Call Type from the drop-down list. Step 3 Step 4 Select Interruptible (checkbox). Click Save, then click Close. 87

94 CICM Scripting Considerations Chapter 11: Scripting Considerations CICM VRU Script Considerations Use the CICM Script Editor s SendToVRU node to connect the call to the Network VRU. For more information about creating scripts, see the Configuration and Administration Guide for Cisco Unified Customer Voice Portal (http://www.cisco.com/en/us/products/sw/custcosw/ ps1006/products_installation_and_configuration_guides_list.html). Note: A RunVRU Script or Queue node is an "implicit" SendToVRU node, although error handling is easier if the explicit SendToVRU node is used. RONA and Unified CVP When using Unified CCH with Unified CVP, the ICM Router Requery function is used to take the call away from the non-answering agent and requeue it for service. There are two places in which configuration must occur: in the Agent Desk Settings - the Ring no answer dialed number field must be blank, and a ring no answer time must be set. in the Script (see below): The Queue node for the skill group that selects the first agent must have Target Requery enabled. The priority of the call should be raised so that it goes to the front of the queue. Scripting for RONA When scripting for RONA, you should Enable Requery on the node in the script that selects the first agent. Depending on the type of node used, the Requery mechanism selects a new target from the available agents or requires additional scripting. The Scripting and Media Routing Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted (http://www.cisco.com/ en/us/products/sw/custcosw/ps1001/tsd_products_support_series_home.html) describes how Requery works for the different nodes. 88

95 Chapter 11: Scripting Considerations CICM Scripting Considerations Figure 18: Changing the Queue Type to Enable Requery Figure 19: RONA Scripting in IP Contact Center Hosted-Edition The Queue node selects the longest available agent from the skill groups configured, if there is an available agent. If there is no available agent, the script then queues the call with a priority set in the node and continues down the success exit of the node. When an agent becomes available, Unified ICM will always select the longest queued call from the ones with the highest priority. The RONA mechanism works as follows: 89

96 CICM Scripting Considerations Chapter 11: Scripting Considerations 1. The Queue node selects an agent. 2. If the agent does not answer the call, the script exits through the failure exit of the Queue node. 3. Ihe If node tests the RequeryStatus variable. If it has value of greater than zero, this is a requery call, and the script re-queues the call. 4. In the example above it also sets a flag using a call variable for reporting purposes. 5. Assuming that there are no agents available, the Queue node immediately exits through the success exit. 6. The If node checks if this is a required call. 7. If so, it increases the Queue Priority of the call so that it gets handled before any other calls in queue. 8. It then enters the normal wait loop with RunScripts. 90

97 Chapter 12 Security Considerations The Unified CCH product allows several customers to share the same Central Controller complex. This presents some possible security concerns in the following areas: Relationships between Windows domains Preventing unauthorized access to real-time data Access to historical data This chapter discusses these concerns and the means by which the Unified CCH product addresses them. For a more general discussion of security, refer to the Security Best Practices Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted, Release 9.x(y) (http://www.cisco.com/ en/us/products/sw/custcosw/ps1001/prod_technical_reference_list.html). This chapter contains the following topics: Windows Domains, page 91 Validating Real-Time Clients, page 92 Historical Data Server, page 93 Windows Domains Components in this architecture are divided among several Windows domains. All NAMs and their associated Administration & Data Servers are in a single domain. Each CICM complex and its associated Administration & Data Servers is in a separate domain. Each instance s Administration & Data Servers can be in two different domains: 91

98 Validating Real-Time Clients Chapter 12: Security Considerations CICM instance distributor on the NAM CICM instance distributor on the Customer AW Each CICM domain must have a two-way trust relationship with the NAM domain and a two-way trust relationship with each customer domain that it serves. For more information, refer to the Staging Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted, Release 9.x(y) (http://www.cisco.com/en/us/products/sw/custcosw/ ps1001/prod_technical_reference_list.html). Validating Real-Time Clients To prevent unauthorized access to real-time data, you can configure Unified ICM s Real-Time Server process to validate each connection. This ensures that only expected clients receive the real-time data. To set up this validation, you must edit the Windows Registry on the CallRouter machine. Locate the customer s subtree under the registry tree HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\ICM. The customer s subtree contains either a RouterA or RouterB tree. Under that tree locate RealTimeServer\CurrentVersion\Clients. Figure 20: Registry Editor on CallRouter To allow access for a specific machine or subnet, you must specify an IP address (IP00, IP01, IP02, etc.) and a corresponding mask (IP00Mask, IP01Mask, IP02Mask, etc.). The IP address 92

Cisco OC-3/OC-12/OC-48 SFP Transceiver Modules Compatibility Matrix This publication contains information about the Cisco platforms and software versions that support the OC-3/OC-12/OC-48 Small Form-Factor

Release Notes for the Cisco WAN Modeling Tools, Release 15.4.00 Patch 1 June 2007 Rev. A0 These release notes are for use with the Cisco WAN Modeling Tools, which includes the following subsystems: NMT

VPN Device Manager Client for Cisco IOS Software (XSM Configuration) Note For the primary documentaiton of the latest version of the VPN Device Manager (version 1.2), see the Installation Guide and Release

Upgrading to the Cisco ubr7246vxr Universal Broadband Router This document outlines the process for upgrading an existing Cisco ubr7246 universal broadband router to a Cisco ubr7246vxr chassis, along with

Constraining IP Multicast in a Switched Ethernet Network This module describes how to configure routers to use the Cisco Group Management Protocol (CGMP) in switched Ethernet networks to control multicast

Cisco Unified Communications Manager SIP Line Messaging Guide (Standard) For Cisco Unified Communications Manager Release 8.5(1) These materials are made available by Cisco as a courtesy to provide certain

Terminal Services Overview This chapter provides an overview of Cisco IOS terminal services and includes the following main sections: Cisco IOS Network Access Devices Line Characteristics and s Asynchronous

Calling Name Delivery (CNAM) Document Release History Publication Date June 25, 2007 Comments Initial version of the document. Feature History Release Modification 9.7(3) The Calling Name Delivery (CNAM)

After you have installed Unified Intelligent Contact Management (Unified ICM) and have it running, use the to view and update the configuration information in the Unified ICM database. The configuration

Cisco Smart Services for Small and Medium Business: Solutions for Your Success Realize the Full Potential of Your Network Cisco Smart Services for Small and Medium Business help you realize the full potential

BGP Link Bandwidth The Border Gateway Protocol (BGP) Link Bandwidth feature is used to advertise the bandwidth of an autonomous system exit link as an extended community. This feature is configured for

How to Register, Start, and Access a Cisco Online Exam Lifecycle Services and SMB Exams The process for registering and taking a Cisco online exam is different from the process for registering and taking

Cisco Unified CallConnector for Microsoft Office Troubleshooting Guide First Published: April 2007 Last Updated: April 2007 OL 13005-01 In this document you will find basic information that will help you

FXO, FXS, and E&M Voice Interface Card Support on Cisco 1700 Series Routers This document describes the support on the Cisco 1751 and Cisco 1760 routers for the following new voice interface cards (VICs):

This chapter, intended for system administrators who perform the first installation of Outbound Option, describes what you need to set up and install the Outbound Option platform. This chapter groups installation

Release Notes for Catalyst 6500 Series and Cisco 7600 Series Router MSFC2A ROMMON Software Current Release:12.2(17r)S6 October 28, 2005 This publication describes how to upgrade the ROMMON on your Catalyst