After you create VMs on the destination system—by golden template or direct-install—you must configure those VMs for customer uer. This chapter contains the procedures you must perform.
Note
Unless otherwise noted, the procedures in this section apply to both golden-template and direct-install options.
For the Unified CVP only, make sure all services are running.
Configure Network Cards
Note
Do this for all the Unified Contact Center Enterprise virtual machines that has two network adapters.
Procedure
Step 1
Select Start and right-click Network and select Properties.
Step 2
Click Change adapter settings.
Step 3
Rename the Local Area Connection to visible. This is the Public network card.
Step 4
Rename the Local Area Connection 2 to private. This is the Private network card.
Step 5
On the Network Connections page, press Alt F to display the Advanced menu.
Step 6
From the Advanced menu, select Advanced Settings.
Step 7
Under Adapters and Bindings , sort the connections so that visible is on top, and click OK.
Step 8
For the Private connection, uncheck File and Printer Sharing for
Microsoft Networks and Client for Microsoft Networks.
Edit Registry Settings and Restart VM
Do this for all the windows based virtual machines that are cloned from Golden Templates using GT Automation tool.
Do not perform this step for direct installs.
Perform this procedure to reset the Local Admin password on the machine.
Procedure
Step 1
Go to Start > Administrative Tools > Computer Management.
Step 2
On the left panel, expand Computer Management (Local) > System Tools > Local Users and Groups > Users.
Step 3
On the right panel, right-click the administrator and choose Set Password.
Step 4
Click Proceed at the warning message, and then enter the new password.
Step 5
Click OK to save.
Step 6
Access the Registry Editor (Start > Run > regedit).
Step 7
For Domain based Virtual Machines, navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft:
Continue to navigate to
Windows
NT > CurrentVersion > Winlogon.
Set AutoAdminLogon to 0.
Add or set DefaultDomainName to the customer domain name.
Add or set DefaultUserName to the customer user name.
Step 8
For non-domain based Virtual Machines, navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft:
Continue to navigate to
Windows
NT > CurrentVersion > Winlogon.
Set AutoAdminLogon to 0.
Add or set DefaultUserName to the customer user name.
Step 9
From the VM client, restart the machine and log in to the domain.
What to Do Next
To synchronize time with the domain controller, open a command prompt and type the command NET TIME /DOMAIN:<domain>.
Configure Unified CCE Encryption Utility
DO THIS FOR the Unified Contact Center Enterprise
Virtual machines. Do not perform this procedure for direct installs.
Procedure
Step 1
Start
All Programs > Cisco
Unified CCE Tools.
Step 2
Select
SSL Encryption Utility.
Step 3
Click the
Certificate Administration tab.
Step 4
Click
Uninstall. Select
Yes.
Step 5
When the uninstallation completes, choose
Install.
You see a stream of messages, ending with SSL Certificate successfully installed.
Step 6
Click
Close.
Configure SQL Server
Procedure
Step 1
Go to
Start > All
Programs > Microsoft SQL Server
2008 R2 > SQL Server Management Studio.
Step 2
Expand Security and then Logins.
Step 3
Use the default settings to log in.
Double-click BUILTIN\Administrators.
Choose Server Roles.
Make sure that public and sysadmin are both checked.
Step 4
If Logins folder does not contain BUILTIN\Administrators:
Right-click Logins and select New Login.
Click Search and then Locations to locate BUILTIN in the domain tree.
Type Administrators and click Check Name and then OK.
Double-click BUILTIN\Administrators.
Expand Server Roles.
Make sure that public and sysadmin are both checked.
Configure a Database Drive
DO THIS FOR Virtual Machines that require an additional hard drive to archive data.
You must perform this procedure for the CCE Data Server and if you deploy the optional CVP Reporting Server.
When you see Select Disks: Disk 1, select the option Use the following partition style for the selected disks: MBR (Master Boot Record).
Step 4
Create a new disk partition as follows: right-click the second disk (marked as uninitialized),
choose
Format.
Enter a name for the Volume Label.
Retain the default file system (NTFS).
Retain the default allocation unit size.
Check the Perform a quick format option.
Click OK.
Click OK at the message about erasing data.
The format is complete when the status changes to Healthy.
The SQL reporting data wlll be stored on this disk.
Configure Domain Manager
DO THIS ONCE, on
the first Unified CCE Call or Data Server that you configure. Configuring Domain Manager for the
Side A Unified CCE Data Server also configures the domain manager for the Side B Unified CCE Data Server
and both Side A and Side B Call Servers.
This procedure creates organizational unit (Cisco_ICM, facility,instance) from any of the Unified CCE servers.
If this is the first instance, add the Cisco Root as Cisco_ICM, :
Under Cisco root, click Add.
Select the organizational unit (OU) under which you want to create the Cisco Root OU, then click OK.
When you return to the Domain Manager dialog box, the Cisco Root OU appears either at the domain root or under the OU you selected. You can now add the facility.
Step 5
Add the facility organizational unit (OU):
Select the Cisco Root OU under which you want to create the Facility OU.
In the right pane, under Facility, click Add.
Enter the name for the Facility. Then click OK.
Step 6
Add the Instance OU:
Navigate to and select the Facility OU under which you want to create the Instance OU.
In the right pane, under Instance, click Add.
Enter the instance name and click OK.
Step 7
Click
Close.
Set Up the Instance
DO THIS ONCE
Note
Ensure that your browser is enabled.
Procedure
Step 1
Launch the
Unified CCE Web Setup.
Step 2
Sign in using as domain user having local Administrator rights.
Step 3
Click
Instance Management, and then click
Add.
Step 4
On the
Add Instance page, configure as follows and
then click
Save:
Choose the customer facility and instance.
In the
Instance Number field, enter 0.
Step 5
Click Save.
Configure the Logger
Configure Logger Database and Log
DO THIS FOR the CCE Data Servers on Side A and Side B.
Procedure
Step 1
Choose
Start > All
Programs > Cisco Unified CCE
Tools > ICMdba. Click Yes at the warnings.
Step 2
Navigate to Server > Instance (logger being installed).
Step 3
Right-click the instance name and choose
Create to create the logger database.
Step 4
In the
Select Component dialog box, choose the logger you are working on ( Logger A or Logger B).
Click
OK.
Step 5
At the prompt, "SQL Server is not configured properly. Do you want
to configure it now?" Click
Yes.
Step 6
On the Configure page, in the SQL Server Configurations pane check
Memory (MB) and Recovery Interval. Click
OK.
Step 7
On the Stop Server page, click
Yes to stop the services.
Step 8
In the
Select Logger Type dialog box, choose
Enterprise. Click
OK
to open the Create Database dialog box.
Step 9
Create the Logger database and log as follows:
In the
DB Type field, choose the Side (A or B).
In the
region field, choose your region.
In the
Storage pane, click
Add.
In the
Create Database dialog box, click
Add to open the Add Device dialog box.
Click
Data
Choose the E drive.
Enter 665600 MB in the
Size field.
Click
OK to return to the
Create Database dialog box.
Click Add again.
In the
Add Device dialog box, click Log.
Choose the E drive.
Enter 3072MB in the Size field.
Click
OK to return to the
Create Database dialog box.
Step 10
In the Create Database dialog box, click Create. Then click Start.
When you see the successful creation message, click OK and then Close.
Configure the Logger Component in Web Setup
DO THIS FOR the CCE Data Servers on Side A and Side B.
Procedure
Step 1
Configure the logger component as follows:
Return to
Unified CCE Web Setup.
You might need to log in again.
Choose
Component
Management > Loggers. Click
Add. Choose the Instance.
On the Deployment page, select the Logger (A or B). Click
Duplexed. Click
Next.
On the Central Controller Connectivity page, enter the host names for Sides A and B for the Router Private Interface and Logger Private Interface.
Click Next.
Step 2
On the Additional Options page, click
Display Database Purge Configuration Steps:
If an external AW-HDS-DDS exists in the deployment, check
Enable Historical/Detail Data Replication.
If no external AW-HDS-DDS exists in the deployment, leave
Enable Historical/Detail Data Replication
unchecked.
Check Display Database Purge Configuration Step.
Click
Next.
Step 3
On the Data Retention page, modify the Database Retention
Configuration table:
For these seven tables, set the retention period to 40.
Application_Event
Event
Network_Event
Route_Call_Detail
Route_Call_Variable
Termination_Call_Detail
Termination_Call_Variable
Set the retention period for all other tables to 400 days.
Click
Next,
Step 4
On the Data Purge page, configure purge for a day of the week and a time when there is low demand on the system.
Step 5
Accept the default Automatic Purge at Percent Full.
Step 6
Click Next.
Step 7
Review the Summary page, and then click
Finish.
Base Configuration on the Logger
Note that after all configuration is complete, you will download the Base Configuration and run it on the Side A logger.
DO THIS FOR the CCE Data Servers on Side A and Side B.
Procedure
Step 1
Choose
Start > All
Programs > Cisco Unified CCE
Tools > ICMdba. Click Yes at the warnings.
Step 2
Navigate to Server > Instance (logger being installed).
Step 3
Right-click the instance name and choose
Create to create the AW database.
Step 4
In the
Select Logger Type dialog box, choose
Enterprise. Click
OK
to open the Create Database dialog box.
Step 5
Create the Logger database and log as follows:
In the
DB Type field, choose AW.
In the
region field, choose your region.
In the
Storage pane, click
Add.
In the
Create Database dialog box, click
Add to open the Add Device dialog box.
Click
Data
Choose the C drive.
Enter 1400 MB in the
Size field.
Click
OK to return to the
Create Database dialog box.
Click Add again.
In the
Add Device dialog box, click Log.
Choose the C drive.
Enter 100 MB in the Size field.
Click
OK to return to the
Create Database dialog box.
Step 6
In the Create Database dialog box, click Create. Then click Start.
When you see the successful creation message, click OK and then Close.
Configure Administration Server and Real-Time Data Server Components
DO THIS FOR the Unified CCE Data Servers on Side A and Side B.
Procedure
Step 1
Go to the
Unified CCE Web Setup.
Step 2
Choose
Component
Management > Administration & Data
Servers. Click
Add.
Step 3
On the Deployment page, choose the current instance.
Step 4
On the Add Administration & Data Servers page, configure as
follows:
Click
Enterprise.
Click
Small to Medium Deployment Size.
Click
Next.
Step 5
On the Server Role in a Small to Medium Deployment page, choose
the option
Administration Server and Real-time Data Server
(AW). Click
Next.
Step 6
On the Administration & Data Servers Connectivity page for Side A:
Click the radio button for
Primary Administration & Data Server.
In the *Secondary Administration & Data Server field, enter the hostname for the Side A server.
In the *Primary Administration & Data Server field, enter the hostname for the Side A server.
In the *Primary/Secondary Pair (Site) Name field, enter AW_SideA.
Click
Next.
OR, on the Administration & Data Servers Connectivity page for Side B:
Click the radio button for
Secondary Administration & Data Server.
In the *Secondary Administration & Data Server field, enter the hostname for the Side A server.
In the *Primary Administration & Data Server field, enter the hostname for the Side A server.
In the *Primary/Secondary Pair (Site) Name field, enter AW_SideB.
Click
Next.
Step 7
On the Database and Options page, configure as follows:
In the
Create Database(s) on Drive field, choose
C.
Do not click the Agent Re-skilling Web Tool.
Note
Supervisors reskill agents in the User Interface, on the Agent tool.
Check
Internet Script Editor (ISE) Server.
Click
Next.
Step 8
On the Central Controller Connectivity page, configure as follows:
For Router Side A, enter the Call Server Side A Public
Interface.
For Router Side B, enter the Call Server Side B Public
Interface.
For Logger Side A, enter the Data Server Side A Public
Interface.
For Logger Side B, enter the Data Server Side B Public
Interface.
Enter the Central Controller Domain Name.
Select
Central Controller Side A Preferred or Central Controller Side B Preferred.
Click
Next.
Step 9
Review the Summary page, and then click
Finish.
Verify Cisco Diagnostic Framework Portico
DO THIS FOR golden templates for the Unified CCE Call Servers and Unified CCE Data Servers on Sides A and B.
Procedure
Step 1
Open the command prompt and enter cd C:\.
Step 2
Enter cd icm\serviceability\diagnostics\bin and press Enter.
Step 3
Enter DiagFwCertMgr /task:CreateAndBindCert /port:7890 and press Enter.
Step 4
Go to Start > Run and enter services.msc to open the Services
tool.
Make sure the Cisco Diagnostic Framework service is running. If it is not, start it.
Step 5
Open Diagnostic Framework Portico: Start > Programs > Cisco Unified CCE Tools > Diagnostic Framework Portico. Then make sure you can log in to the Diagnostic Framework Portico using domain user credentials.
Configure Unified CCE Call Server
This section explains the configuration procedures you must perform
for the Unified Contact Center Enterprise Call Server Sides A and B.
Click
Add in the
Instance Components pane, and from the
Component Selection dialog box choose
Peripheral Gateway.
Step 3
In the
Peripheral Gateway Properties dialog box:
Check
Production mode.
Check
Auto start system startup.
Check
Duplexed Peripheral Gateway.
Choose
PG1 in the
PG node Properties ID field.
Select the appropriate side (Side A or
Side B).
Under Client Type pane, add
CUCM to the selected types.
Under Client Type pane, add
VRU to the selected types.
Click
Next
.
Add PIM1 (CUCM PIM)
In the
Peripheral Interface Manager pane of the
Peripheral Gateway Component Properties dialog
box, click
Add
and configure PIM1 with the Client Type of Unified Communications Manager as follows:
Procedure
Step 1
Check
Enabled.
Step 2
In the
Peripheral name field, enter CM.
Step 3
In the
Peripheral ID field, enter 5000.
Step 4
In the
Agent extension length field, enter
extension length for this deployment.
Step 5
In the
Unified Communications Manager Parameters pane, configure as
follows:
In the
Service field, enter the hostname of
the Unified Communications Manager Subscriber.
In the
User ID field, enter pguser.
In the
User password field, enter your
password.
In the
Mobile Agent Codec field, choose either
G.711 or G.729.
Step 6
Click
OK
.
Add PIM2 (first VRU PIM)
In the
Peripheral Interface Manager pane of
the
Peripheral Gateway Component
Properties dialog box, click
Add and configure PIM2 with the Client Type of VRU as follows:
Procedure
Step 1
Check
Enabled.
Step 2
In the
Peripheral name field, enter CVP1.
Step 3
In the
Peripheral ID field, enter 5001.
Step 4
In the VRU host name, enter the IP address of CVP1 (Side A).
Step 5
In the VRU hostname field, enter the hostname for CVP1.
Step 6
In the
VRU Connect port field, enter
5000.
Step 7
In the
Reconnect interval (sec)
field, enter 10.
Step 8
In the
Heartbeat interval (sec) field,
enter 5.
Step 9
In the
DSCP field, choose CS3(24).
Step 10
Click
OK.
Add PIM3 (second VRU PIM)
In the
Peripheral Interface Manager pane of
the
Peripheral Gateway Component
Properties dialog box, click
Add and configure PIM3 with the Client Type of VRU as follows.
Procedure
Step 1
Check
Enabled.
Step 2
In the
Peripheral name field, enter CVP2.
Step 3
In the
Peripheral ID field, enter 5002.
Step 4
In the VRU host name, enter the IP address of CVP1 (Side B).
Step 5
In the VRU hostname field, enter the hostname for CVP2.
Step 6
In the
VRU Connect port field, enter
5000.
Step 7
In the
Reconnect interval (sec)
field, enter 10.
Step 8
In the
Heartbeat interval (sec) field,
enter 5.
Step 9
In the
DSCP field, choose CS3(24).
Step 10
Click
OK
.
Add PIM4 (third VRU PIM)
In the
Peripheral Interface Manager pane of
the
Peripheral Gateway Component
Properties dialog box, click
Add and configure PIM4 with the Client Type of VRU as follows:
Procedure
Step 1
Check
Enabled.
Step 2
In the
Peripheral name field, enter CVP3.
Step 3
In the
Peripheral ID field, enter 5003.
Step 4
In the VRU host name, enter the IP address of CVP2 (Side A).
Step 5
In the VRU hostname field, enter the hostname for CVP3.
Step 6
In the
VRU Connect port field, enter
5000.
Step 7
In the
Reconnect interval (sec)
field, enter 10.
Step 8
In the
Heartbeat interval (sec) field,
enter 5.
Step 9
In the
DSCP field, choose CS3(24).
Step 10
Click
OK
.
Add PIM5 (fourth VRU PIM)
In the
Peripheral Interface Manager pane of
the
Peripheral Gateway Component
Properties dialog box, click
Add and configure PIM5 with the Client Type of VRU as follows:
Procedure
Step 1
Check
Enabled.
Step 2
In the
Peripheral name field, enter CVP4.
Step 3
In the
Peripheral ID field, enter 5004.
Step 4
In the VRU host name, enter the IP address of CVP2 (Side B).
Step 5
In the VRU hostname field, enter the hostname for CVP4.
Step 6
In the
VRU Connect port field, enter
5000.
Step 7
In the
Reconnect interval (sec)field, enter 10.
Step 8
In the
Heartbeat interval (sec field,
enter 5.
Step 9
In the
DSCP field, choose CS3(24).
Step 10
Click
OK
.
After Creating PIMs
Procedure
Step 1
Enter 5000 in the
Logical Controller ID field.
Step 2
Enter 0 in the
CTI Call Wrapup Data delay field.
Step 3
In the
VRU Reporting pane, click
Service Control and check
Queue Reporting. Click
Next.
Step 4
In the
Device Management Protocol Properties
dialog box, click
Side A Preferred.
Step 5
If you are configuring Side A:
Side A Properties panel =
Call Router is local.
Side B Properties panel =
Call Router is local.
Step 6
If you are configuring Side B:
Side A Properties panel =
Call Router is local.
Side B Properties panel =
Call Router is local.
Step 7
Accept the default value in the
Usable Bandwidth (kbps) field.
Step 8
Enter 4 in the
Heartbeat Interval (100ms)
field. Click
Next.
Step 9
In the
Peripheral Gateway Network Interfaces
dialog box, enter the PG Private Interfaces and the PG Public (Visible)
Interfaces.
Step 10
Click the QoS button in the private interfaces section for Side A. In the PG Private Link QoS Settings, check Enable QoS and click OK.
Step 11
Click the QoS button in the public interfaces section. In the PG Visible Link QoS Settings, check Enable QoS, click OK and click Next.
This step applies only to Side A.
Step 12
In the Peripheral Gateway Network Interfaces dialog box, click Next.
Step 13
In the
Check Setup Information dialog box, click
Next.
Step 14
In the
Setup Complete dialog box, click
Finish.
Configure CTI Server
Follow this procedure to configure the CTI Server for the CUCM PIM.
Procedure
Step 1
In the Instance Components pane of the Components Setup dialog box click Add.
Step 2
In the Component Selection dialog box, click CTI Server.
Check Production mode.
Check Auto start at system startup.
Check Duplexed CTI Server.
Choose CG1 in the CG node properties pane ID field.
Enter 1 in the CG node properties ICM system ID field.
Click the appropriate side (Side A or Side B).
Click Next.
Step 3
In the Server Component Properties dialog box, configure as follows:
For Side A, enter 42027 in the Client Connection Port Number field.
For Side B, enter 43027 in the Client Connection Port Number field.
Step 4
Click Next.
Step 5
In the Network Interface Properties dialog box, enter the private interfaces.
Step 6
Enter the public (visible) interfaces and the CG visible interfaces, and click Next.
Step 7
Under the Check Setup Information page, verify all the settings, and click Next.
Step 8
In the Setup Completed dialog box, click Finish.
Step 9
Click Exit Setup.
Install JTAPI
Note
This procedure is required for the Unified Contact Center Enterprise
Machine having a PG with Unified Communications Manager PIM. However, you must postpone this task until after you
Configure Unified Communications Manager.
Complete the following procedure to install JTAPI on the Unified Contact Center Enterprise
Machine having a PG with Unified Communications Manager PIM for Side A and Side B.
Procedure
Step 1
Launch the Unified Communications Manager in a browser
(https://{callmanager-hostname})
and log in.
Step 2
Navigate to
Application > Plugins.
Click
Find.
Step 3
Download the Cisco JTAPI 32-bit Client for Windows.
Step 4
Install the downloaded file, accepting all of the default
settings.
Step 5
At the prompt, enter the IP address for the Unified Communications Manager TFTP
Server, and click Next.
Step 6
Click Finish.
Configure Media Routing Peripheral Gateway
Complete the following procedures to configure the Unified CCE Media Routing Peripheral Gateway for the call servers on Side A and then repeat for Side B. The Media Routing Peripheral Gateway has two PIMs-the MultiChannel PIM and the Outbound PIM.
You must configure this PG, even if Multichannel and Outbound are not used. In that case, this PG remains idle.
Configure Multichannel and Outbound PIMs
Complete the following procedure to configure the multichannel and outbound PIM:
Click
Add in the
Instance Components pane, and from the
Component Selection dialog box choose
Peripheral Gateway.
Step 3
In the
Peripheral Gateway Properties dialog box:
Check
Production Mode.
Check
Auto start system startup.
Check
Duplexed Peripheral Gateway.
Choose
PG2 in the
PG node Properties ID field.
Click the appropriate side (Side A or
Side B).
Under Client Type pane, add
Media Routing to the selected types.
Click
Next.
Step 4
In the
Peripheral Interface Manager pane of the
Peripheral Gateway Component Properties dialog
box, click
Add and configure PIM1 with the Client Type of
Media Routing as follows:
Check
Enabled.
In the
Peripheral name field, enter MR.
In the
Peripheral ID field, enter 5005.
In the
Application Hostname (1), field, enter the
hostname or the IP address of the Unified WIM and EIM services server machine.
In the
Application Connection Port (1), field,
enter the port number on the Unified WIM and EIM services server machine that the PIM will use
to communicate with the application.
The default port is 38001.
In the
Application Hostname (2), field, leave the field blank.
In the
Application connection port (2), field,
leave the field blank.
In the
Heartbeat interval (sec) field, enter 5.
In the Reconnect interval (sec) field, enter 10.
Click
OK.
Step 5
Click Add and configure PIM2 with the client type of Media
Routing as follows:
Check Enabled.
In the Peripheral name field, enter MR2 or a name of
your choice.
In the Peripheral ID field, enter 5006.
In the Application Hostname(1) field, enter UCCE call server side A
IP.
The Application Connection port (1), retain the default
value.
In the Application Hostname (2), field, enter UCCE Call server side
B IP.
The Application Connection port (2), retain the default
value.
In the Heartbeat interval (sec) field, enter 5.
In the Reconnect interval (sec) field, enter 10, and click OK.
Step 6
Enter 5001 in the
Logical Controller ID field.
Step 7
Enter 0 in the
CTI Call Wrapup Data delay field. Click
Next.
Step 8
In the
Device Management Protocol Properties
dialog box, configure as follows:
Click Side A Preferred, if you are configuring Side A, or click Side B Preferred, if you are configuring Side B.
Choose Call Router is local in the Side A Properties panel.
Choose Call Router is local in the Side B Properties panel.
Accept the default value in the Usable Bandwidth (kbps) field.
Enter 4 in the Heartbeat Interval (100ms) field. Click Next.
Step 9
In the
Peripheral Gateway Network Interfaces dialog
box, enter the PG Private Interfaces and the PG Public (Visible) Interfaces.
Click the QoS button in the private interfaces section. In the PG Private Link Qos Settings, check the check box Enable QoS and click OK.
Click the QoS button in the public interfaces section. In the PG Visible Link Qos Settings, check the check box Enable QoS, click OK and click Next.
Step 10
In the
Check Setup Information dialog box, click
Next.
Step 11
In the
Setup Complete dialog box, click
Finish.
Step 12
Click Exit Setup.
Configure CTI OS Server
Complete the following procedure to configure the CTI OS server for Side A and Side B.
Procedure
Step 1
Mount the CTIOS ISO image or copy the CTIOS installer
to the local drive of Unified CCE Call Server.
Step 2
If a maintenance release for CTIOS is available, copy
the maintenance release to the local drive of Unified CCE Call
Server.
Step 3
Navigate to CTIOS > Installs > CTIOS Server and run setup.exe. Click Yes to the warning that the SNMP service will be stopped and then restarted after the installation completes.
Step 4
Accept the Software License Agreement.
Step 5
Browse to the location for the latest Maintenance Release, if any.
Step 6
In the CTIOS Instances dialog box, click Add in the CTI OS Server List pane. Select the CTIOS Server Name and click OK.
Step 7
In the Enter Desktop dialog box, choose drive C. Click OK.
Step 8
In the CTI Server Information dialog box, enter the IP address of the Call Server and the ports for Side A (42027) and Side B (43027). Then click Next.
Step 9
In the Peripheral Identifier dialog box, accept all defaults. In the Login By pane, select Agent ID and then click Next.
Step 10
In the Connect Information dialog box, accept all defaults and then click Next.
Step 11
In the Statistics Information dialog box, check Polling for Agent Statistics at End Call, and then click Next.
Step 12
In the IPCC Silent Monitor Type dialog box, set Silent Monitor Type to CCM Based and click Next.
Step 13
In the Peer CTIOS Server dialog box, configure as follows:
Check Duplex CTIOS Install.
If you are configuring Side A, set the hostname of the CCE Machine having CTIOS Server Side B. If you are configuring Side B, set the hostname of the CCE Machine having CTIOS Server A.
In the Port field, enter 42028.
Step 14
Click Finish.
Step 15
In the Cisco CTIOS Server Security dialog box, uncheck Enable Security. Click OK.
Step 16
In the CTI OS Security Setup Complete dialog box, click Finish.
Step 17
If prompted to restart the computer, click Yes. If there is a Maintenance Release, its installation begins automatically.
Step 18
Follow all prompts to install the Maintenance Release, if there is one.
Step 19
When the MR install completes, click Finish and follow the prompts to restart.
What to Do Next
Access Registry Editor (Start > Run > regedit).
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems,Inc.\Ctios\CTIOS_<instance name>\CTIOS1\Server\Agent.
Set forceLogoutOnSessionClose Dword to 1.
Configure Cisco Unified CVP
This section explains the procedure to configure Cisco Unified CVP.
Configure and Validate Network Card for Unified CVP
For all Unified CVP servers, configure and validate the Network Cards.
Configure Network Card for Unified CVP
Procedure
Step 1
Choose Start and right-click Network.
Step 2
Select Properties. Then select Change Adapter Settings.
Step 3
Press Alt F from the Network Connections page to display the Advanced menu.
Step 4
From the Advanced menu choose Advanced Settings.
Validate Network Card for Unified CVP
Procedure
Step 1
Right-click Local Area Connection and select Properties.
Step 2
Uncheck Internet Protocol Version 6 (TCP/IPV6).
Step 3
Check Internet Protocol Version 4 and select Properties.
Step 4
Confirm the data for Visible IP addresses, Subnet mask, Default gateway and Preferred and alternate DNS servers for the template.
Step 5
Click OK.
Enable Unified CVP Operations Console
Complete the
following procedure on the Unified CVP OAMP server to enable Unified CVP Operations Console.
Procedure
Step 1
Go to Start > Run and type services.msc.
Step 2
Check that Cisco CVP OPSConsoleServer service is running.
If it is not, right-click that service and click Start.
Step 3
Go to Start > All Programs > Cisco Unified Customer Voice Portal >
Operation Console to open the Unified CVP OPSConsole page.
If you are using Microsoft Internet Explorer, you will need to accept the self-signed certificate.
Configure Unified CVP Call Server
Complete the
following procedure to configure the Call Server component on the Unified
CVP Call/VXML Servers. There are two CVP Call/VXML Servers on Side A and two on
side B.
Procedure
Step 1
In the Unified CVP Operations Console, navigate to Device Management > Unified CVP Call
Server.
Step 2
Click
Add New.
Step 3
On the
General tab, enter the IP address and the
hostname of the Cisco Unified CVP Call/VXML Server. Check
ICM,
IVR, and
SIP. Click
Next.
Step 4
Click the
ICM tab. For each of the Cisco Unified CVP
Call Servers, retain the default port of 5000 for the VRU Connection Port.
Step 5
Click the
SIP tab:
In the
Enable outbound proxy field, select
No.
In the
Use DNS SRV type query field, select
Yes.
Check
Resolve SRV records locally.
Step 6
Click the
Device Pool tab. Make sure the default device pool is selected.
Step 7
(Optional) Click the
Infrastructure tab. In the Configuration
Syslog Settings pane, configure these fields as follows:
Enter the IP address or the hostname of the syslog server.
Enter 514 for the port number of the syslog server.
Enter the name of the backup server to which the reporting
server writes log messages.
In the
Backup server port number field, enter the
port number of the backup syslog server.
Step 8
Click
Save & Deploy.
Step 9
Repeat Steps 1 through 8 for the next three Unified CVP Call Servers.
Configure Unified CVP VXML Server
Complete the
following procedure to configure the VXML Server component on the Cisco Unified
CVP Call/VXML Servers. There are two Unified CVP Call/VXML Servers on Side A and two on
side B.
Procedure
Step 1
In the Unified CVP Operations console, navigate to Device Management > Unified CVP VXML
Server.
Step 2
Click
Add New.
Step 3
On the
General tab, enter the IP address and the
hostname of the Cisco Unified CVP Call/VXML Server.
Step 4
Configure the primary and backup CVP Call Servers as follows:
For CVP-1A, the primary call server is CVP-1A and the backup call server is CVP-1B.
For CVP-2A, the primary call server is CVP-2A and the backup call server is CVP-2B.
For CVP-1B, the primary call server is CVP-1B and the backup call server is CVP-1A.
For CVP-2B, the primary call server is CVP-2B and the backup call server is CVP-2A.
Step 5
Click the
Device Pool tab. Make sure the default device pool is selected.
Step 6
Click
Save & Deploy.
Step 7
Repeat Steps 1 through 6 for all CVP Call Servers.
Configure Gateways
Complete the
following procedure to configure every gateway.
Procedure
Step 1
In the Unified CVP Operations Console, navigate to the
Gateway Device. Choose
Device
Management > Gateway.
Step 2
Click
Add New.
Step 3
On the
General tab, configure as follows:
Enter the IP address of the gateway.
Enter the hostname.
Choose the Device Type.
In the Username and Passwords pane, enter the gateway username and a
password.
Step 4
Click
Save.
Step 5
Do this for every gateway.
Configure Unified CVP Media Server
Procedure
Step 1
Sign in to the
Unified CVP Operations Console.
Step 2
Navigate to the
Media Server Device. Choose
Device Management > Media
Server.
Step 3
Click
Add New.
Step 4
On the
General tab, enter the IP address and the
hostname of the Unified CVP server.
Step 5
Click
Save.
Step 6
Repeat Steps 1 through 5 for all Media Servers.
Step 7
Change Default Media Server from None to any one of the Unified CVP servers. Then click Set.
Transfer Scripts and Media Files
Create the
notification destination and deploy to all of the Unified CVP devices.
Procedure
Step 1
Sign in to the Unified
CVP Operations Console.
Step 2
Navigate to
Scripts & Media. Choose
Bulk
Administration > File
Transfer > Scripts & Media.
Step 3
In the
Select device type field, select the
Gateway.
Step 4
Move all Gateways to
Selected.
Step 5
Click
Default Gateway files.
Step 6
Click Transfer and select OK at the popup window.
Step 7
Click
File Transfer Status to monitor transfer
progress.
File Transfer of Licenses
Procedure
Step 1
Navigate to Bulk Administration > Licensing.
Step 2
Select all servers from the available list and move them to the selected list.
Step 3
Browse to choose your license file to upload.
Step 4
Click Transfer.
Step 5
Click File Transfer Status.
Step 6
Confirm that each of the File Transfers shows "Success" in the Status column.
Step 7
Navigate to System > Control Center.
Step 8
Gracefully shutown and then start each of the VXML and Call Servers in the list.
Complete the
following procedure to configure SNMP.
Procedure
Step 1
Log in to the
Unified CVP Operations Console.
Step 2
Select
SNMP > V1/V2c.
Step 3
Select Community String > Add New.
Name the community string and verify that the default values for other fields are correct.
Select the Devices tab and assign the SNMP community string to a device.
Click Save and Deploy.
Step 4
Create the notification destination and deploy to all of the Unified CVP
devices.
Select Notification Destination > Add New.
Complete the fields.
Select the Devices tab and assign the SNMP notification destination to a device.
Click Save and Deploy.
Configure SIP Server Group
Complete the
following procedure to configure the SIP Server Group.
Before You Begin
The following devices require the SIP Server Group:
Unified Communications
Manager
Gateway
Procedure
Step 1
Log in to the Unified CVP Operations Console.
Step 2
Choose System > SIP Server
Group.
Step 3
Create a server group for the Unified Communications Manager devices:
On the General tab, click
Add New.
In the
SRV Domain Name FQDN field, enter the
service record (SRV) fully qualified domain name (FQDN).
In the
IP Address/Hostname field, enter an IP
address or hostname for the Unified Communications Manager node.
Click
Add.
Repeat Steps c and d for each Unified Communications Manager node. Click
Save.
Note
Do not put the Publisher node in the server group—it is not used for call processing.
The FQDN should match the FQDN configured in the Enterprise Cluster FQDN setting on the Cisco Unified Communications Manager. For more information, see Validate Clusterwide Domain Configuration. For example, cucm.cisco.com. Adding the cluster subscriber nodes will load balance across all sub nodes.
Step 4
Create a server group for the gateway devices:
On the General tab, click
Add New.
In the
SRV Domain Name FQDN field, enter the SRV
Domain Name FQDN. For example vxmlgw.cisco.com.
In the
IP Address/Hostname field, enter an IP
address or hostname for each gateway.
Click
Add.
Repeat Steps c and d for each gateway.
Click
Save.
Add all VXML gateways as appropriate for deployment and branches. Adding all VXML gateways to the server group will load balance calls across all the member server group gateways.
Step 5
Associate these server groups to all Unified CVP Call Servers:
On the
Call Server Deployment tab, move all
Unified CVP Call Servers from the
Available list to the
Selected list.
Click
Save and Deploy.
Step 6
Click
Deployment Status to make sure that you
applied the configuration.
Configure Dialed Number Pattern
Complete the
following procedure to configure a dialed number pattern for CCE PAC M1.
Before You Begin
The following labels require a dialed number pattern:
Agent Device
Network VRU
Ringtone
Error
Procedure
Step 1
Navigate to
System > Dialed Number
Pattern.
Step 2
For each dialed number pattern in the following table:
Click Add New.
In the
Dialed Number Pattern field, enter the
dialed number pattern.
In the
Description field, enter a description for
the dialed number pattern.
In the
Dialed Number Pattern Types pane, check
the specified dialed number pattern type.
Click
Save.
Step 3
After you configure all dialed number patterns, click
Deploy.
Step 4
Click
Deployment Status to make sure that you
applied the configuration.
Dialed Number Pattern
Description
Dialed Number Pattern Types
91*
Ringtone Label
Check Enable Local Static Route.
Route to SIP Server Group and IP Address/Hostname Server Group Name are both VXML Gateway (for example, vxmlgw.cisco.com).
Check Enable Send Calls to Originator.
92*
Error Label
Check Enable Local Static Route.
Route to SIP Server Group and IP Address/Hostname Server Group Name are both VXML Gateway (for example, vxmlgw.cisco.com).
Check Enable Send Calls to Originator.
This must be the agent extension pattern. For example, enter 500* where the range of agent extensions is 5001 to 500999.
Agent Device Label
Check Enable Local Static Route.
Route to SIP Server Group and IP Address/Hostname Server Group Name are both the Unified Communications Manager gateway.
Check Enable RNA Timeout for Outbound Calls. The timeout is 15 seconds.
Route to SIP Server Group and IP Address/Hostname Server Group Name are both VXML Gateway (for example vxmlgw.cisco.com).
Check Enable Send Calls to Originator.
Configure Cisco IOS Enterprise Voice Gateway
Complete the following procedure to configure the Cisco IOS Voice Gateway.
Note
Complete all configuration steps in enable > configuration terminal mode.
Procedure
Step 1
Configure the network interfaces:
interface GigabitEthernet0/0
ip route-cache same-interface
duplex auto
speed auto
no keepalive
no cdp enable
Step 2
Configure global settings:
voice service voip
no ip address trusted authenticate
allow-connections sip to sip
signaling forward unconditional
sip
rel1xx disable
header-passing
options-ping 60
midcall-signaling passthru
# Configure CVP survivability
dial-peer voice 1 pots
description CVP TDM dial-peer
service survivability
incoming called-number .T
direct-inward-dial
# Configure CVP Ringtone
dial-peer voice 919191 voip
description CVP SIP ringtone dial-peer
service ringtone
incoming called-number 9191T
voice-class sip rel1xx disable
dtmf-relay rtp-nte
codec g711ulaw
no vad
# Configure CVP Error
dial-peer voice 929292 voip
description CVP SIP error dial-peer
service cvperror
incoming called-number 9292T
voice-class sip rel1xx disable
dtmf-relay rtp-nte
codec g711ulaw
no vad
#Configure VXML leg where the incoming called-number matches the Network VRU Label
dial-peer voice 9999 voip
description Used for VRU leg
service bootstrap
incoming called-number 777T
dtmf-relay rtp-nte
codec g711ulaw
no vad
#Configure the Switch leg where
# preference is used to distinguish between sides.
# max-conn is used prevent overloading of CVP
# options-keepalive is used to handle failover
# Note: the example below is for gateways located on the A-side of a geographically distributed deployment
dial-peer voice 70021 voip
description Used for Switch leg SIP Direct
preference 1
max-conn 225
destination-pattern xxxx...... # Customer specific destination pattern
session protocol sipv2
session target ipv4:###.###.###.### # IP Address for CVP1, SideA
session transport tcp
voice-class codec 1
voice-class sip options-keepalive up-interval 12 down-interval 65 retry 2
dtmf-relay rtp-nte
no vad
dial-peer voice 70022 voip
description Used for Switch leg SIP Direct
preference 1
max-conn 225
destination-pattern xxxx...... # Customer specific destination pattern
session protocol sipv2
session target ipv4:###.###.###.### # IP Address for CVP2, SideA
session transport tcp
voice-class codec 1
voice-class sip options-keepalive up-interval 12 down-interval 65 retry 2
dtmf-relay rtp-nte
no vad
dial-peer voice 70023 voip
description Used for Switch leg SIP Direct
preference 2
max-conn 225
destination-pattern xxxx...... # Customer specific destination pattern
session protocol sipv2
session target ipv4:###.###.###.### # IP Address for CVP1, SideB
session transport tcp
voice-class codec 1
voice-class sip options-keepalive up-interval 12 down-interval 65 retry 2
dtmf-relay rtp-nte
no vad
dial-peer voice 70024 voip
description Used for Switch leg SIP Direct
preference 2
max-conn 225
destination-pattern xxxx...... # Customer specific destination pattern
session protocol sipv2
session target ipv4:###.###.###.### # IP Address for CVP2, SideB
session transport tcp
voice-class codec 1
voice-class sip options-keepalive up-interval 12 down-interval 65 retry 2
dtmf-relay rtp-nte
no vad
Step 7
Configure the hardware resources (transcoder, conference bridge, and MTP):
# Configure the voice-cards share the DSP resources located in Slot0
voice-card 0
dspfarm
dsp services dspfarm
voice-card 1
dspfarm
dsp services dspfarm
voice-card 2
dspfarm
dsp services dspfarm
voice-card 3
dspfarm
dsp services dspfarm
voice-card 4
dspfarm
dsp services dspfarm
# Point to the contact center call manager
sccp local GigabitEthernet0/0
sccp ccm ###.###.###.### identifier 1 priority 1 version 7.0 (CUCM1)
sccp ccm ###.###.###.### identifier 1 priority 1 version 7.0 (CUCM2)
# Add a SCCP group for each of the hardware resource types
sccp ccm group 1
associate ccm 1 priority 1
associate profile 2 register <gw70mtp>
associate profile 1 register <gw70conf>
associate profile 3 register <gw70xcode>
# Configure DSPFarms for Conference, MTP and Transcoder
dspfarm profile 1 conference
codec g711ulaw
codec g711alaw
codec g729r8
maximum sessions 24
associate application SCCP
dspfarm profile 2 mtp
codec g711ulaw
codec g711alaw
codec g729r8
maximum sessions software 500
associate application SCCP
dspfarm profile 3 transcode
codec g711ulaw
codec g711alaw
codec g729r8
maximum sessions 52
associate application SCCP
Step 8
(Optional) Configure the SIP Trunking:
# Configure the resources to be monitored
voice class resource-group 1
resource cpu 1-min-avg threshold high 80 low 60
resource ds0
resource dsp
resource mem total-mem
periodic-report interval 30
# Configure one rai target for each CVP Server
sip-ua
rai target ipv4:###.###.###.### resource-group1 (CVP1A)
rai target ipv4:###.###.###.### resource-group1 (CVP2A)
rai target ipv4:###.###.###.### resource-group1 (CVP1B)
rai target ipv4:###.###.###.### resource-group1 (CVP2B)
permit hostname dns:%Requires manual replacement - ServerGroup Name defined in CVP.System.SIP Server Groups%
Configure Unified Communications Manager
Follow this sequence of tasks to configure Unified Communications Manager:
Configure Publisher for Unified Communications Manager
This procedure is for golden templates only.
You must customize the Unified Communications Manager publisher before you customize the
subscribers.
Before You Begin
DNS Configuration is mandatory for Unified Communications Manager, Cisco Unified Intelligence Center, and Cisco Finesse. To configure DNS, add the VMs to the forward and reverse lookups of the DNS. For more information, see Configure DNS Server
Procedure
Step 1
In the client computer where the automation tool was run,
navigate to
C:\GoldenTemplateTool_901\PlatformConfigRepository\CUCM.
Step 2
Copy the file named CUCM_PUB_SideA_platformConfig.xml .
Step 3
Paste it to another location and rename it to
platformConfig.xml.
Step 4
Launch WinImage
and
select
File > New > 1.44
MB and click OK.
Step 5
Drag and drop
platformConfig.xml into WinImage.
Step 6
When prompted to inject the file, click
Yes.
Step 7
Select
File > Save As.
Step 8
From the Save as type list, choose Virtual floppy image. Provide the file
name as platformConfig.flp and click Save.
Step 9
Open vSphere infrastructure client and connect to the vCenter. Go
to the customer ESXi host where the VMs are deployed.
Step 10
Navigate to the Configuration tab. In the storage section, right click on the Datastore and choose Browse Datastore, create a folder named
CUCM_PUB.
Step 11
Upload the platformConfig.flp file to the folder CUCM_PUB.
Step 12
Edit the Virtual Machine Settings for the
Unified Communication Manager VM.
Step 13
On the
Hardware tab, click the floppy drive, choose the radio button Use The Existing Floppy Image in Datastore and
mount the platformConfig.flp from the CUCM_PUB folder on the data store and click OK.
Step 14
Ensure that
Connect at Power On is checked for the network
adapters and the floppy drive and click OK.
Step 15
Power on the Publisher. This begins the installation based on the information in the .flp file.
The installation begins automatically and runs with no interaction from you. After an hour or more, a message appears indicating a successful installation.
Step 16
Click the Console tab for the VM. Log in to the publisher machine, using the credentials for the
Administration User. The machine opens to the CLI interface.
Step 17
Edit settings and uncheck Connect at Power on for the
floppy drive.
Note
During the customization of the publisher/primary, the username and the
password are modified as follows. The customer should change the password.
Default Password for OS
Administrator:
pcce@123
Application UserName:
Administrator
Default Password for
Application User:
pcce@123
Sftp password:
pcce@123
IPSec password:
pcce@123
After rebooting, the VM installation is complete with all the
parameters provided in the spreadsheet for the VM.
DNS Configuration is mandatory for Unified Communications Manager. To configure DNS, add the VMs to the forward and reverse lookups of the DNS. See Configure DNS Server
Launch Publisher to Add the Subscriber
To add the subscriber, you must launch the publisher node.
Do this for golden templates only. For direct installs, this procedure was part of the installation of the publisher.
Procedure
Step 1
Launch the Unified
Communications Manager Publisher in a browser (http://<IP Addr of CUCM Publisher>).
Step 2
Enter the username and password and login to the Unified
Communications Manager.
Step 3
Select
System > Server > Add
New.
Step 4
On the Server
Configuration tab, enter the IP address of the subscriber.
Step 5
Click
Save.
Configure Subscriber
Procedure
Step 1
Launch WinImage and select File > New > 1.44 MB and Click OK.
Step 2
In the client computer where the automation tool was run, navigate to
C:\GoldenTemplateTool_901\PlatformConfigRepository\CUCM.
Step 3
Copy the file named CUCM_SUB_SideA_platformConfig.xml.
Step 4
Paste it to another location and rename it to
platformConfig.xml.
Step 5
Drag and drop
platformConfig.xml into WinImage.
Click
Yes at the message asking if you want to
inject the file.
Select
File > Save
as and save the file as a Virtual Floppy Image with the filename platformConfig.flp.
Tip
If drag and drop does not work, select Image > Inject. Then browse to the file.
Step 6
Open vSphere infrastructure client and connect to the vCenter. Go
to the customer ESXi host where the VMs are deployed.
Step 7
Create the folder CUCM_SUB and upload platformConfig.flp to it.
Step 8
Edit the Virtual Machine settings for the Unified Communications Manager Subscriber VM.
Step 9
On the
Hardware tab, click the floppy drive, choose the radio button Use The Existing Floppy Image in Datastore and
mount the platformConfig.flp from the CUCM_SUB folder on the data store.
Step 10
Ensure that Connect at Power On is checked for the network adapters and the floppy drive. Click OK and then power on the VM.
This begins the installation and customizes the installation based on the information in
the .flp file.
Step 11
After you complete
the installation uncheck Connect at Power on for the floppy drive.
Step 12
Repeat this procedure for the second subscriber on Side B.
Unified Communications Manager License
To configure the Unified Communications Manager license, first add a product instance, then generate and register the license, and then install the license.
Add Product Instance
Complete the following procedure to add a product instance.
Procedure
Step 1
Launch Communications Manager publisher in a browser (http://<IP Addr of CUCM Publisher>).
Step 2
Click Cisco Enterprise License Manager.
Step 3
Sign in with the credentials of Unified Communications Manager.
Step 4
Go to Inventory > Product Instances.
Step 5
Click Add to open a popup window.
Step 6
Enter details:
Name and Description
Product Type: Unified CM.
Hostname/IP Address of Unified Communications Manager.
Credentials of the publisher
Step 7
Click Test Connection. Then click OK at the success message.
Step 8
Click OK to add the product instance.
Step 9
Click Home > Inventory > Product Instance.
You can see the newly added product instance.
Step 10
Click Synchronize Now to synchronize with the Unified Communications Manager.
Step 11
Go to Monitoring > License Usage. You can see the number licenses used and required number of licenses.
Note
You must apply the license for the information to appear.
Generate and Register License
Procedure
Step 1
Go to License Management > Licenses. Under Other Fulfillment options, click Generate License Request.
Step 2
When the License Request and Next Steps window opens, copy the test as directed (PAK ID) and save it to a text editor.
Step 3
Click the Cisco License Registration site and proceed with steps in the site. Keep the PAK handy; you will need it.
Step 4
Enter the PAK when prompted.
You will receive the license file in an email message.
Install License
Complete the following procedure to install a license.
Procedure
Step 1
Unzip the license file from the email message.
Step 2
Navigate to License Management > Licenses.
Step 3
Click Install License File and select the unzipped file and then click Install.
Step 4
Navigate to the Monitoring > License Usage page to verify a successful installation.
Validate Clusterwide Domain Configuration
This validation is required for running calls.
Procedure
Step 1
In the Cisco Unified CM Administration, navigate to System > Enterprise Parameters.
Step 2
Scroll down to Clusterwide Domain Configuration.
Cluster Fully Qualified Domain Name should match the Server Group name in the Unified CVP SIP Server Groups Configure SIP Server Group.
Install JTAPI on Unified CCE Call Servers
Now that you configured the Unified Communications Manager, you can
Install JTAPI.
Provision Cisco Unified Communications Manager
This section contains the procedures you must perform to provision Cisco Unified Communications Manager. This section assumes you have added phones (Add Phones).
Complete the
following procedure to activate service.
Procedure
Step 1
Select Cisco Unified Serviceability from the Navigation menu and click Go.
Step 2
Select
Tools > Service
Activation to open the Service Activation window.
Step 3
From the Server drop-down list, choose the server on which you
want to activate the service, and then click
Go. For the server that you chose, the window
displays the service names and activation status of the services.
Step 4
For the Publisher, check the following services to activate and click Save:
Cisco CallManager
Cisco IP Voice
Media Streaming Application
Cisco CTIManager
Cisco Tftp
Cisco Bulk Provisioning Service
Cisco AXL Web
Service
Cisco
Serviceability Reporter
Cisco CTL Provider
Cisco Certificate Authority Proxy Function
Step 5
For the Subscribers, check the follow services to activate and click Save:
Cisco CallManager
Cisco IP Voice
Media Streaming Application
Cisco CTIManager
Cisco AXL Web
Service
Cisco CTL Provider
Configure Cisco Unified Communications Manager Groups
Complete the
following procedure to add a Cisco Unified Communications Manager to the
Unified Communications Manager Group. Make sure that you configured both the
publisher and the subscribers.
Note
Before you configure a Cisco Unified Communications manager group,
you must configure the Cisco Unified Communications Managers that you want to
assign as members to that group.
Procedure
Step 1
Select Cisco Unified CM Administrator from the Navigation menu and click Go.
Step 2
Select System > Cisco Unified CM Group.
Step 3
Click
Find. Then click Default.
Step 4
Move the two subscribers from the Available panel to the Selected panel.
Do not select the publisher; the publisher should not be used for call processing.
Step 5
Click
Save.
Configure CTI Route Point
Complete the
following procedure to add a computer telephony integration (CTI) route point
for agents to use for transfers and conferences.
Procedure
Step 1
In Cisco CM Administration, select Device > CTI Route
Point.
Step 2
Click
Add New.
Step 3
Set a device name that is meaningful; for example, PCCEInternalDNs.
Step 4
For Device Pool, select Default.
Step 5
Click
Save.
Step 6
Click on line 1 to configure the directory number associated with this route point.
This directory number will be a pattern that is intended to match any of the internal Dialed Numbers you configure in Packaged CCE for internally routed calls. (For instance, for Transfers and Conferences).
Important:
Define a pattern that is flexible enough to match all your internal dialed numbers yet restrictive enough not to inadvertently intercept calls intended for other Route Patterns you may have defined for other parts of your dial plan. As a best practice, use a unique prefix for internal calls. For example, if you have internal dialed numbers 1230000 and 1231111, then an appropriate line number to enter for the cti route point would be 123XXXX.
Configure Application User
Complete the
following procedure to configure each application user.
Note
This step assumes you have added users and phones.
Procedure
Step 1
In Cisco CM Administration, select
User
Management > Application User.
Step 2
Click
Add New.
Step 3
Enter the User ID that you entered in Configure the Cisco Unified
CCE Peripheral Gateway and CTI Server (Side A). Unified CCE defines the user ID
as pguser.
Step 4
Enter cisco in the
Password and Confirm Password fields. Note that if you change this
user ID or password in Unified CCE, you must also change the Unified
Communication Manager application user configuration.
Step 5
Click Add to Access Control Group and select Standard CTI Allow Call Monitoring and Standard CTI Enabled.
Complete the
following procedure to configure SIP options.
Procedure
Step 1
Choose
Device > Device
Settings > SIP Profile.
Step 2
Click Add New.
Step 3
Name the option Standard SIP Profile - Early Offer.
Step 4
Scroll to Trunk Specific Configuration, check Early Offer support for voice and video calls (insert MTP if needed).
Step 5
Scroll to the SIP Options Ping panel. Check
Enable OPTIONS Ping to monitor destination
status for Trunks with Service Type
None Default.
Step 6
Click
Save.
Configure Trunk
Complete the
following procedure to configure a trunk for the CVP call servers on Side A,
and a trunk for the CVP call servers on Side B.
In all, you will be adding 4 SIP trunks—one for each CVP server.
Procedure
Step 1
In Cisco CM Administration, select
Device >
Trunk.
Step 2
Click
Add New.
Step 3
From the Trunk Type drop-down list, choose
SIP Trunk, and then click
Next.
This opens the Trunk Configuration window.
Step 4
Enter the following in the Device Information section:
In the
Device Name field, enter a name for the SIP
trunk, for example, sipTrunkCVP.
In the
Device Pool drop-down list, select the device pool that the customer has defined.
Make sure that the
Media Termination Point Required check
box is not checked.
Step 5
Scroll down to the SIP Information section:
In Row 1 of the Destination table, enter the IP address of the first CVP server. Accept the default destination port of 5050.
Click the + button to insert a row for a second destination. Enter the IP address for the second CVP Server, using port 5060.
Repeat twice more to add Destination Addresses for the last two CVP servers.
In the SIP Trunk Security Profile drop-down list, select Non Secure SIP Trunk Profile.
In the SIP Profile drop-down list, select Standard SIP Profile - Early Offer.
In the DTMF Signaling Method drop-down list, select RFC 2833.
Step 6
Click
Save.
Configure Route Pattern
Complete the
following procedure to configure a route pattern.
Procedure
Step 1
In Unified CM Administration, select Call Routing > Route Hunt > Route Group.
Step 2
Configure and save a Route Group with the four CVP sip trunks.
Step 3
Select Call Routing > Route Hunt > Route List.
Step 4
Configure and save a Route List for the Route Group.
Step 5
Add the Route Group to a Route List
Step 6
Select Call Routing > Route Hunt > Route Pattern.
Step 7
Click
Add New.
Step 8
Create one Route Pattern Definition for Route Pattern 888!. Keep all defaults in the Pattern Definition panel.
Step 9
Click
Save.
To load-balance sending calls across all 4 CVP servers, add all 4 CVP servers to the route group/route list.
Configure Conference Bridge
Complete the
following procedure to configure a conference bridge.
Procedure
Step 1
Choose
Media
Resources > Conference bridge.
Step 2
Add a conference bridge for each ingress/VXML combination gateway
in the deployment.
Use type Cisco IOS Conference Bridge.
Step 3
In the
Conference Bridge name field, enter a unique
identifier for the conference bridge name that coincides with the configuration
on the gateway. See Step 7 in
Configure Cisco IOS Enterprise Voice Gateway.
In the example, this is gw70conf.
# Add a SCCP group for each of the hardware resource types
sccp ccm group 1
associate ccm 1 priority 1
associate profile 2 register gw70mtp
associate profile 1 register gw70conf
associate profile 3 register gw70xcode
Step 4
Click
Save.
Step 5
Click
Apply Config.
Configure Media Termination Point
Complete the
following procedure to configure a media termination point.
Procedure
Step 1
Choose
Media Resources > Media
Termination Point.
Step 2
Add a media termination point for each ingress/VXML combo gateway
in the deployment.
Step 3
In the Media Termination Point Name field, enter a media
termination point name for each ingress/VXML combo gateway in the deployment.
See Step 7 in
Configure Cisco IOS Enterprise Voice Gateway.
In the example, this is gw70mtp.
# Add a SCCP group for each of the hardware resource types
sccp ccm group 1
associate ccm 1 priority 1
associate profile 2 register gw70mtp
associate profile 1 register gw70conf
associate profile 3 register gw70xcode
Step 4
Click
Save.
Step 5
Click
Apply Config.
Configure Transcoder
Complete the
following procedure to configure a transcoder.
Procedure
Step 1
Choose
Media Resources >
Transcoder.
Step 2
From the drop-down, select Cisco IOS enhanced media termination point.
Step 3
Add a transcoder for each ingress/VXML combo gateway in the
deployment.
Step 4
In the
Device Name field, enter a unique identifier
for the transcoder that coincides with the configuration on the gateway. See Step 7 in
Configure Cisco IOS Enterprise Voice Gateway.
Step 5
In the Device Pool field, select Default.
Step 6
Click
Save.
Step 7
Click
Apply Config.
Configure Media Resource Group
Complete the
following procedure to configure a media resource group for conference bridge,
media termination point, and transcoder.
Procedure
Step 1
Choose
Media Resources > Media
Resource Group.
Step 2
Add a Media Resource Group for Conference Bridges.
Step 3
Select all the hardware conference bridge resources configured for
each ingress/VXML combination gateway in the deployment and add them to the
group.
Step 4
Click
Save.
Step 5
Choose
Media Resources > Media
Resource Group.
Step 6
Add a Media Resource Group for Media Termination Point.
Step 7
Select all the hardware media termination points configured for
each ingress/VXML combination gateway in the deployment and add them to the
group.
Step 8
Click
Save.
Step 9
Choose
Media Resources > Media
Resource Group.
Step 10
Add a Media Resource Group for Transcoder.
Step 11
Select all the transcoders configured for each ingress/VXML
combination gateway in the deployment and add them to the group.
Step 12
Click
Save.
Configure and Associate Media Resource Group List
Complete the
following procedure to configure and associate a media resource group list. Add
the media resource group list to the following devices and device pool.
Procedure
Step 1
Choose
Media Resources > Media
Resource Group List.
Step 2
Add a Media Resource Group list and associate all of the media
resource groups. Click Save.
Step 3
Choose
System > Device
Pool. Click
Default.
Step 4
From the Media Resource Group List drop-down list, choose the
media resource group added in Step 2.
Step 5
Click
Save. Click
Reset.
Step 6
Choose
Device > CTI Route
Point.
Step 7
Click the configured CTI Route Point. See Configure a CTI Route
Point.
Step 8
From the Media Resource Group List drop-down list, choose the
media resource group added in Step 2.
Step 9
Click
Save. Click
Reset.
Step 10
Choose
Device > SIP
Trunk.
Step 11
Click the configured SIP Trunk for side-A. See Configure a Trunk.
Step 12
From the Media Resource Group List drop-down list, choose the
media resource group added in Step 2.
Step 13
Click
Save. Click
Reset.
Step 14
Click the configured SIP Trunk for side-B. See
Configure Trunk.
Step 15
From the Media Resource Group List drop-down list, choose the
media resource group added in Step 2.
Step 16
Click
Save. Click
Reset.
Add Phones
It is beyond the scope of this document to explain how to add phones and associate them with the Application User. You will, however, need two phones for the agents who will sign in to Finesse to test calls. This is necessary to complete the final step to make a call.
This topic points to the Cisco Unified Communications Manager tools that you access to add phones
Procedure
Step 1
Sign in to the Cisco Unified Intelligence Center Administration Console (http://{hostname}/oamp).
Step 2
Select Device > Phone.
Step 3
Click Find and then Add New.
Step 4
Select the phone type you will use for the agent. Then click Next.
Step 5
Complete all required fields in the Device Information screen and Save.
Step 6
Repeat steps 2 - 4 for the second phone.
Step 7
Select User Management > Application User.
Step 8
Click Find. Then select pguser.
Step 9
Make sure the CTI Route Point (Configure CTI Route Point) and both phones are moved from Available Devices to Controlled Devices.
Configure Unified Intelligence Center
Follow these tasks to configure Unified Intelligence Center.
You must customize the Cisco Unified Intelligence Center publisher before you customize the
subscriber.
Before You Begin
DNS Configuration is mandatory for Unified Intelligence Center. To configure DNS, add the VMs to the forward and reverse lookups of the DNS. See Configure DNS Server.
Procedure
Step 1
In the client computer where the automation tool was run,
navigate to
C:\GoldenTemplateTool_901\PlatformConfigRepository\CUIC.
Step 2
Copy the file named CUICPUB_SideA_platformConfig.xml.
Step 3
Paste it to another location and rename it to
platformConfig.xml.
Step 4
Launch WinImage
and
select
File > New > 1.44
MB and click OK.
Step 5
Drag and drop
platformConfig.xml into WinImage.
Step 6
When prompted to inject the file, click
Yes.
Step 7
Select
File > Save as.
Step 8
From the Save as type list, select Virtual floppy image. Provide the filename as platformConfig.flp and click Save.
Make sure you have selected the correct network adapter.
Step 9
Open vSphere infrastructure client and connect to the vCenter. Go
to the customer ESXi host where the VMs are deployed.
Step 10
Navigate to the Configuration tab. In the storage section, right click on the Datastore and choose Browse Datastore and create a folder named
CUIC_PUB.
Step 11
Upload the platformConfig.flp file to the folder CUIC_PUB.
Step 12
Edit the Virtual Machine Settings for the
Unified Intelligence Center Publisher VM .
Step 13
On the
Hardware tab, click the floppy drive, choose the radio button Use The Existing Floppy Image in Datastore and
mount the platformConfig.flp from the CUIC_PUB folder on the data.store and click OK.
Step 14
Ensure that
Connect at Power On is checked for the network
adapters and the floppy drive and click OK.
Step 15
Power on the Publisher. This begins the installation based on the information in the .flp file.
The installation begins automatically and runs with no interaction from you. After an hour or more, you will see a message indicating a successful installation.
Step 16
Click the Console tab for the VM. Log in to the publisher, using the credentials for the
Administration User. The machine opens to the CLI interface.
Step 17
Edit settings and uncheck Connect at Power on for the
floppy drive.
Note
During the customization of the publisher/primary, the username and the
password are modified as follows. The customer should change the password.
Default Password for OS
Administrator:
pcce@123
Application UserName:
Administrator
Default Password for
Application User:
pcce@123
Sftp password:
pcce@123
IPSec password:
pcce@123
What to Do Next
After rebooting, the VM installation is complete with all the
parameters provided in the spreadsheet for the VM.
Before adding a subscriber, you must upload the license file in the Publisher. DNS Configuration is mandatory for Unified Intelligence Center. To configure DNS, add the VMs to the forward and reverse lookups of the DNS. For more information, see Configure DNS Server.
Launch the Publisher to Add the Subscriber
To add the subscriber, you must launch the publisher node and define the subscriber in the Administration Console.
Do this for golden templates only. For direct installs, this procedure was part of the installation of the publisher.
Procedure
Step 1
Direct a browser to the URL http://<HOST ADDRESS>/oamp where HOST ADDRESS is the IP Address or Hostname of your Cisco Unified Intelligence Center publisher.
Step 2
Sign in using the system application user ID and password that you defined during installation.
Step 3
From the panel in the left, select Device Management > Device Configuration.
Step 4
Click Add Member.
Step 5
On the Device Configuration fields for the Subscriber, enter a name, the hostname or IP address, and a description for the device.
Step 6
Click Save.
Configure Subscriber
Complete the following procedure to configure a subscriber.
Procedure
Step 1
Launch WinImage and select File > New > 1.44 MB.
Step 2
In the client computer where the automation tool was run, navigate to
C:\GoldenTemplateTool_901\PlatformConfigRepository\CUIC.
Step 3
Copy the file named CUIC_SUB_SideA_platformConfig.xml.
Step 4
Paste it to another location and rename it to
platformConfig.xml.
Step 5
Drag and drop
platformConfig.xml into WinImage:
Click
Yes at the message asking if you want to
inject the file.
Select
File > Save
as and save the file as a Virtual Floppy Image with the filename platformConfig.flp.
Tip
If drag and drop does not work, select Image > Inject. Then browse to the file.
Step 6
Open vSphere infrastructure client and connect to the vCenter. Go
to the customer ESXi host where the VMs are deployed.
Step 7
Create the folder CUIC_SUB and upload platformConfig.flp to it.
Step 8
Edit the Virtual Machine settings for the CUIC Subscriber VM.
Step 9
On the
Hardware tab, click the floppy drive, choose the radio button Use The Existing Floppy Image in Datastore and
mount the platformConfig.flp from the CUIC_SUB folder on the data store.
Step 10
Ensure that Connect at Power On is checked for the network adapters and the floppy drive. Click OK and then power on the VM.
This begins the installation and customizes the installation based on the information in
the .flp file.
Step 11
If there is a value in the optional DNS_IP_NIC1 cell of the
automation spreadsheet, configure the DNS server by adding the machine in
forward and reverse lookup.
Note
During the customization of the subscriber node, the username and the
password are modified as follows. The customer should change the password.
Make changes as follows:
Default Password for OS
Administrator:
pcce@123
Application UserName:
Administrator
Default Password for
Application User:
pcce@123
Sftp password:
pcce@123
IPSec password:
pcce@123
Step 12
After you complete the installation uncheck Connect at Power on
for the floppy drive.
Configure Unified Intelligence Center Reporting
Complete the following procedures to configure Unified Intelligence Center Reporting. There are two components to configure:
Scroll to Unified communications and click
Cisco Unified Intelligence Center.
Step 4
Enter your MAC Address, accept the agreement, and enter your
Registrant Information.
The MAC Address appears online at the end of the installation. If
you do not have time to write it down before it disappears, you can find it through the CLI, after the install is complete, as follows:
Sign in to the server node, using the credentials of the
System Administration user.
Enter this CLI command:
show status.
Step 5
Follow prompts to complete the registration windows.
You will receive an email from Cisco that contains your
license file as an attachment. The file format is *.lic.
Step 6
Save the license file in a location where the
System Application User can access
it.
Warning
As a best practice, save a backup copy of this file. You can
open a *.lic. file to look at it, but
do not make any changes to it. Changing the file invalidates
the license.
Sign In to Administration Console
Who can sign in to the administration console: The
System Application User who is the
default
Superuser.
To upload the license, you must sign in to the Unified Intelligence Center
Administration Console. This is the OAMP interface for Unified Intelligence Center. The first
person who signs in to the Administration application must do so using the user
ID and password that were defined for the System Application User during the
installation. This user is the initial Superuser for Unified Intelligence Center
Administration.
Procedure
Step 1
Enter this URL:
http://<HOST ADDRESS>/oamp, where HOST ADDRESS
is the IP address or hostname of your Controller node.
Step 2
Enter the System Application User ID and password that you
defined during installation.
Upload License
Who can upload the license: The
System Application User who is the
default
Superuser.
As soon as the System Application User signs in, the user must upload
the license file. The file is uploaded to the publisher node and, within a
minute, is automatically replicated to all nodes in the cluster.
Procedure
Step 1
In the Administration application, choose
Cluster
Configuration > License
Management.
This opens the License File Management page.
Step 2
Click
Upload license file (Browse).
Step 3
Navigate to the location where the *.lic file was saved.
Step 4
Click
Apply License to load the license.
A message appears indicating that the license file was uploaded
successfully and will be distributed to other nodes (if any) in the cluster in
approximately one minute.
Note
The databases are polled once a minute for changes. The
license replication is not immediate but occurs within a minute.
Configure Cisco Finesse
Note
Finesse will not operate correctly unless you disable the Cisco Security Agent (CSA) after installing the primary node and after installing the secondary node.
Follow this sequence of tasks to configure Cisco Finesse.
You must configure the Finesse primary node before you customize the
secondary node.
Before You Begin
DNS Configuration is mandatory for Cisco Finesse. To configure DNS, add the VMs to the forward and reverse lookups of the DNS. See Configure DNS Server
Procedure
Step 1
In the client computer where the automation tool was run,
navigate to
C:GoldenTemplateTool_901\PlatformConfigRepository\Finesse.
Step 2
Copy the file named FINESSE_PRIMARY_platformConfig.xml.
Step 3
Paste it to another location and rename it to
platformConfig.xml.
Step 4
Launch WinImage
and
select
File > New > 1.44
MB and click OK.
Step 5
Drag and drop
platformConfig.xml into WinImage.
Step 6
When prompted to inject the file, click
Yes.
Step 7
Select
File > Save as.
Step 8
Choose the Save as type list as Virtual floppy image. Provide the filename as platformConfig.flp and click Save.
Step 9
Open vSphere infrastructure client and connect to the vCenter. Go
to the customer ESXi host where the VMs are deployed.
Step 10
Navigate to the Configuration tab. In the storage section, right click on the Datastore and choose Browse Datastore and create a folder named
FINESSE_PRIMARY.
Step 11
Upload the platformConfig.flp file to the folder FINESSE_PRIMARY.
Step 12
Edit the Virtual Machine Settings for the
Finesse Primary VM .
Step 13
On the
Hardware tab, click the floppy drive, choose the radio button Use The Existing Floppy Image in Datastore and
mount the platformConfig.flp from the FINESSE_PRIMARY folder on the data store and click OK.
Step 14
Ensure that
Connect at Power On is checked for the network
adapters and the floppy drive.
Step 15
Power on the Primary Machine. This begins the installation based on the information in the .flp file.
The installation begins automatically and runs with no interaction from you. After an hour or more, you will see a message indicating a successful installation.
Step 16
Click the Console tab for the VM. Log in to the primary machine, using the credentials for the
Administration User. The machine opens to the CLI interface.
Step 17
Edit settings and uncheck Connect at Power on for the
floppy drive.
During the customization of the primary, the username and the
password are modified as follows. The customer should change the password.
Default Password for OS
Administrator:
pcce@123
Application UserName:
Administrator
Default Password for
Application User:
pcce@123
Sftp password:
pcce@123
IPSec password:
pcce@123
After rebooting, the VM installation is complete with all the
parameters provided in the spreadsheet for the VM.
Configure CTI Server Settings in Cisco Finesse Primary Node
Procedure
Step 1
Launch the URL http://hostname or IP address/cfadmin, where hostname or IP address is the hostname or IP address of your primary Finesse server.
Step 2
Go to Home > Contact Center Enterprise CTI Server Settings.
Step 3
Update the following:
A Side Host/IP Address (of Side A CTIOS Server)
A Side Port (CTI Server Port on Side A)—42027
Peripheral ID (of CallManager PIM)—5000
B Side Host/IP Address (of Side B CTIOS Server)
B Side Port (CTI Server Port on Side B)—43027
Step 4
Click Submit.
Configure Unified Contact Center Enterprise Administration and Data Server
Procedure
Step 1
Go to Home > Contact Center Enterprise Administration & Data Server Settings. (This menu structure assumes the default configuration.)
Step 2
Update the following:
Primary Host/IP Address (of Side A AW Server)
Database Port: 1433
Backup Host/Ip Address (of Side B AW Server)
Domain (required field): The name of the Unified CCE to which Finesse connects.
AW Database Name: <ucceinstance_awdb>
UserName: The domain username that is required to sign in to the database. Cannot be SQL user.
Password: The password required to sign in to the database.
Step 3
Click Submit.
Restart Tomcat
After changing and saving any value on Contact Center Enterprise Administration Server Settings, you must restart the Cisco Tomcat Service on the primary Finesse server.
Procedure
Step 1
To stop the Cisco Tomcat service, enter this CLI command: utils service stop Cisco Tomcat .
Step 2
To start the Cisco Tomcat service, enter this CLI command: utils service start Cisco Tomcat .
DNS Configuration is mandatory for Cisco Finesse. To configure DNS, add the VMs to the forward and reverse lookups of the DNS. See Configure DNS Server.
Launch the Finesse Administration Console to Configure the Secondary Finesse
To add the secondary node, you must launch the primary node and add the secondary node to the cluster.
Do this for golden templates only. For direct installs, this procedure was part of the installation of the primary.
Procedure
Step 1
Launch the Cisco Finesse primary node in a browser (http://Primary Node IP Address/cfadmin), where the Primary Node or IP address is that of your host.
Step 2
Go to Home > Cluster Settings. (This is based on the default configuration and assumes you have not changed the page for the Cluster Settings tool.)
Step 3
Add the IP address for the Cisco Finesse secondary node.
Step 4
Click Submit.
Install Cisco Finesse on Secondary Node
Procedure
Step 1
Launch WinImage and select File > New > 1.44 MB.
Step 2
In the client computer where the automation tool was run, navigate
to C:\CCEPAC1_VMAutomation\PlatformConfigRepository\Finesse .
Step 3
Copy the file named FINESSE_SECONDARY_platformConfig.xml .
Step 4
Paste it to another location and rename it to
platformConfig.xml.
Step 5
Drag and drop
platformConfig.xml into WinImage:
When prompted to inject the file, click Yes.
Select
File > Save
as and save the file as a Virtual Floppy Image (.flp).
Tip
If drag and drop does not work, select Image > Inject. Then browse to the file.
Step 6
Open vSphere infrastructure client and connect to the vCenter. Go
to the customer ESXi host where the VMs are deployed.
Step 7
Create a folder FINESSE_SECONDARY in the data store and upload the platformConfig.flp file to that folder FINESSE_SECONDARY.
Step 8
Edit settings for the VM. On the
Hardware tab, click the floppy drive and choose the radio button Use The Existing Floppy Image in Datastore and
mount the platformConfig.flp from the FINESSE_SECONDARY folder on the data store.
Step 9
Ensure that
Connect at Power On is checked for the network
adapters and the floppy drive.
Step 10
Power on the VM. This begins the installation and customizes the installation based on the information in
the .flp file.
During the customization of the secondary node, the username and the
password are modified as follows. The customer may change the password:
Default Password for OS
Administrator:
pcce@123
Application UserName:
Administrator
Default Password for
Application User:
pcce@123
Sftp password:
pcce@123
IPSec password:
pcce@123
Step 11
After you complete the installation, uncheck Connect at Power on
for the floppy drive.
Configure Unified CVP Reporting Server
The optional Unified CVP Reporting VM is required for customers who use Courtesy Callback and who want to run callback application reports. Unified CVP customers must sign in to Cisco Unified Intelligence Center as users.
Follow this sequence of tasks to configure Unified CVP Reporting:
Initially, the
System Application User who is the
default
Superuser.
Eventually, any Superuser.
Unified CVP reporting users can sign in to Unified Intelligence Center only if they
exist in the Administration console as Superusers or if Active Directory (AD) is configured in the Unified Intelligence Center Administration console for their domain:
Superusers who are added are considered to be IP Multimedia Subsystem (IMS) users. For more information, see Create Superusers.
Users who are authenticated through Active Directory are considered to be Lightweight Directory Access Protocol
(LDAP) users. For more information, see Set Up Active Directory Server for LDAP Users.
Both IMS users and LDAP users can log in to Unified Intelligence Center reporting and
are restricted to the limited Login User role until the Unified Intelligence Center reporting
security administrator gives them additional roles and flags them as active
users.
Although you can create a user on the Unified Intelligence Center User List page, an
entry on the User List is not sufficient for that user to sign in to
the Unified Intelligence Center. One reason to create users on the User List page is to expedite the
permissions for users before their Active Directory domain is configured.
Create Superusers
Sign in to Cisco Unified Intelligence Center Administration (http://server/oamp).
To create Superusers, perform the following:
Procedure
Step 1
Log in to the Cisco Unified Intelligence Center Administration Console (http://{hostname}/oamp).
Step 2
Navigate to Admin User Management > Admin User Management to
open the Users page.
Step 3
Click Add New to add and configure a new user or click an existing username to edit the configuration for that user.
This page has three tabs: General, Credentials, and Policy. For information about completing these tabs, see
Administration Console User Guide for Cisco Unified Intelligence
Center or to the Administration console online help.
Step 4
Click Save.
Set Up Active Directory Server for LDAP Users
Configure the Active Directory tab in the Administration console
so that Unified CVP reporting users can log in to the Unified Intelligence Center reporting
application with the user name and password that is defined in their domain.
Who can do set up an active directory for LDAP users:
Initially, the
System Application User who is the
default Superuser.
Eventually, any
Superuser.
Perform the following procedure to set up the Active Directory server for LDAP users:
Procedure
Step 1
In the Administration application, navigate to
Cluster
Configuration > Reporting
Configuration and select the Active Directory tab.
Step 2
Complete all fields on this page, referring to the online help
for guidance.
Step 3
Click
Test Connection.
Step 4
When the connection is confirmed, click
Save.
Sign In to Cisco Unified Intelligence Center Reporting Interface
Who can sign in to the Unified Intelligence Center reporting interface:
Initially, the
System Application User who is the
default Superuser.
Eventually, any Unified CVP user who was
created in the Administration Console as an IMS superuser or an LDAP user.
Perform the following procedure to sign in to the Unified Intelligence Center reporting interface.
Procedure
Step 1
Sign in to the Cisco Unified Intelligence Center Administration Console (http://{hostname}/oamp).
Step 2
Navigate to Control Center > Device Control.
Step 3
Click on the name of the Member node you want to
access. This opens the Cisco Unified Intelligence Center login page for that
member.
Step 4
Enter your user ID and password. The Overview page appears.
Import Unified CVP Report Templates and Set Data Source
Who can do
this:
Initially, the
System Application User who has full
permissions in Unified Intelligence Center Reporting.
Eventually, any
Report Designer who has has full permissions.
Before reporting users can run the Unified CVP report templates in
the Unified Intelligence Center reporting application, a Unified IC reporting user with
permission to do so must import them into Unified IC and associate them with
the Unified CVP Data Source.
Packaged CCE supports the Callback reports only. Do not import other reports.
Procedure
Step 1
Launch the Unified IC web application using the
URL http://<HOST ADDRESS>/cuic, where HOST
ADDRESS is the IP Address or Hostname of your Member node.
This opens the login window.
Step 2
Enter your User Name and Password.
This opens the Overview page.
Step 3
Click the
Reports drawer to open the Available Reports
page.
Step 4
Right-click the top Reports folder and select
Create New Sub-Category.
Step 5
Name the new sub-category as a container for
Unified CVP reports. Click
OK.
Step 6
Click
Import Reports.
Step 7
Browse to the location where you copied the Unified CVP XML
template report templates files.
Step 8
Select a report.
This populates the File Name with the full path for the report.
Step 9
From the Data Source To Use drop-down list, choose the Data Source you
created to access the Unified CVP reporting database.
Step 10
From the Data Source To Use drop-down list, choose the Unified CVP
sub-category folder you created in Step 5.
Step 11
Click
Import.
Step 12
Repeat Steps 6 to 11 for each Unified CVP report template.
Create Data Source for Cisco Unified CVP Report Data
Who can create data source for Cisco Unified Customer Voice Portal report data:
Initially, the
System Application User who has full
permissions in Unified Intelligence Center reporting.
Eventually, any
System Configuration Administrator.
Similar to creating an Open Database Connectivity
(ODBC) connection, this task is necessary to
access the Unified CVP reporting data.
In Unified Intelligence Center, the user must perform this task with the System
Configuration Administrator User Role.
Perform the following procedure to create a data source.
Procedure
Step 1
Select the Data Sources drawer to open the Data Sources page.
Figure 1. Data Sources Page
This page shows three data sources that are installed by Unified Intelligence Center. They are the CUIC data source, the Unified CCE Historical data source, and the
Unified CCE Realtime data source.
The CUIC data source represents the Unified Intelligence Center database on the node that
stores records for reports, dashboards, and users maintained on that node. This
data is replicated across all nodes in the cluster.
The two Unified CCE data sources represent the databases that
populate the stock Cisco Unified CCE reports.
Step 2
Click
Create to open an Add Data Source window.
Step 3
Complete fields on this page as follows:
Field
Value
Name
Enter the name of this data source.
Report Designers and Report Definition Designers do not
have access to the Data Sources page but can see the list of Data Sources when
they create custom reports.
Best Practice: To benefit those users, give a
new Data Source a meaningful name.
Description
Enter a description for this data source.
Type
Options are Informix and SQL server.
Choose Informix.
Note
Type is disabled in Edit mode.
Database Host
Enter the IP address or Domain Name System (DNS) name for the server and
append the port for the Informix database.
Port
Enter the port number. Typically, the port is 1526.
You may have to open this port in the CVP Reporting Server firewall (Window Firewall > Inbound rules > new rule).
Database name
Enter the name of the reporting database on the Unified
CVP reporting server.
Use
the database name callback for stock callback
reports.
Instance
Specify the instance name of the desired database.
By default, this is cvp.
Timezone
Choose the correct time zone for the data stored in the
database. In locations that change from Standard Time to Daylight
Savings Time, this time zone is updated automatically.
Database User ID
Enter the user ID of the Reporting User who is configured in the Operations Console to access the Unified CVP reporting
database.
Password and Confirm Password
Enter and confirm the password for the database user.
Charset
Choose UTF-8 for the Unified CVP Informix database.
Note
If this field is not set correctly, the Unified Intelligence Center cannot
connect.
Default Permissions
View or edit the permissions for this datasource for My
Group and for the All Users group.
Step 4
Click
Test Connection.
If the status is not Online, review the error message to
determine the cause and edit the data source accordingly.
Step 5
Click
Save to close the Add Data Source window.
The new data source
appears on the Data Sources list.
The Unified
CVP reporting template XML files are installed with Unified CVP. Locate them and copy them to a Unified Intelligence Center client
workstation.
For Packaged CCE, import the Callback reports only.
To import Unified CVP report templates complete the following:
Procedure
Step 1
In the Unified CVP
server, locate the Unified CVP template files. These are XML files that reside
on the reporting server in %CVP_HOME%\CVP_Reporting_Templates. You can also
find them on the Installation DVD in \Downloads and Samples\ Reporting
Templates.
Step 2
Choose the files and copy them to
the client computer from which you will launch the Unified IC Reporting web
application.
Set up NTP and Time Configuration at the Customer Site
Any domain controllers at the customer site must be configured to use NTP servers. The two ESXi core servers must point to the same NTP servers as the domain controllers. Additionally, you must review time configuration settings on the ESXi core servers. Doing this prevents a race condition and an incorrect time setting when the server starts or reboots.
Procedure
Step 1
To add an NTP server to the domain controller:
Locate the Microsoft instructions on how to configure an authoritative time server in Windows Server.
Public NTP servers are available on the Internet if you do not have one.
Note down the IP address or domain name of the NTP server that you add.
Step 2
To point the ESXi core servers to the domain controller NTP servers:
For each core server, click the Configuration tab.
Choose Time Configuration > Properties... > Options.
This opens a panel with two sections: General and NTP Settings.
Click NTP Settings. Then click Add.
Enter the IP address or fully qualified domain name of the NTP Servers associated with the domain controller. Click OK. Click Restart.
Step 3
To set the startup policy for the NTP server(s):
Navigate to Time Configuration > Properties... > Options.
Click General.
Select Start and stop with host. Click OK.
Step 4
To review the time settings for the core servers:
Click the Configuration tab.
In the Software panel, select Time Configuration, which shows the Date & Time and the NTP Servers.
Step 5
To adjust the Date & Time if they are incorrect:
Click Properties... This opens the Time Configuration dialog box.