|
|
Table Of Contents
Configuring Interoperability with External Services
Information About Interoperability with External Services
Interoperability with Unified CCX
How to Configure Interoperability with External Services
Configuring Cisco Unified CME to Enable Interoperability with Unified CCX
Identifying Agent Directory Numbers in Cisco Unified CME for Session Manager
Verifying Registrations and Subscriptions in Cisco Unified CME
Re-creating a Session Manager in Cisco Unified CME
Reconfiguring a Cisco CRS Route Point as a SIP Endpoint in Cisco Unified CME
Configuration Examples for Interoperability with Unified CCX
Feature Information for Interoperability with External Services
Configuring Interoperability with External Services
Last Updated: July 5, 2007
First published: June 18, 2007This chapter describes features in Cisco Unified Communications Manager Express (Cisco Unified CME) that provide support for interoperability between Cisco Unified CME and external feature services, such as Cisco Customer Response Solutions (CRS) with Cisco Unified Contact Center Express (Unified CCX).
Finding Feature Information in This Module
Your Cisco Unified CME version may not support all of the features documented in this module. For a list of the versions in which each feature is supported, see the "Feature Information for Interoperability Feature" section.
Contents
•
Information About Interoperability with External Services
•
How to Configure Interoperability with External Services
•
Configuration Examples for Interoperability with Unified CCX
•
Feature Information for Interoperability with External Services
Information About Interoperability with External Services
To configure interoperability, you should understand the following concepts:
•
Interoperability with Unified CCX
Interoperability with Unified CCX
Cisco Unified CME 4.2 and Cisco IOS Release 12.4(11)XW2 and later versions supports interoperability between Cisco Unified CME and Cisco Customer Response Solutions (CRS) 5.0 and later versions with Cisco Unified Call Center Express (Unified CCX), including enhanced call processing, device and call monitoring, unattended call transfers to multiple call center agents and basic extension mobility, and IP IVR applications.
The Unified CCX application uses the CRS platform to provide a multimedia (voice, data, and web). Cisco IP IVR functionality is available with Unified CCX and includes prompt-and-collect and call treatment.
The following functions are provided in Cisco Unified CME 4.2 and later versions:
•
Support of Unified CCX Cisco Agent Desktop for use with Cisco Unified CME
•
Configuration query and update between Unified CCX and Cisco Unified CME.
•
SIP-based simple and supplementary call control services including:
–
Call routing between Cisco Unified CME and Unified CCX using SIP-based route point
–
First-party call control for SIP-based simple and supplementary calls
–
Call monitoring and device monitoring based on SIP presence and dialog event package
•
Unified CCX session management of Cisco Unified CME
•
Unified CCX device and call monitoring of agent lines and call activities in Cisco Unified CME
Provisioning and configuration information in Unified CCX is automatically provided to Cisco United CME. If the configuration from Unified CCX is deleted or must be modified, you can configure the same information in Cisco Unified CME by using Cisco IOS commands.
For first party call control, a route point for Cisco CRS is a peer device to Cisco Unified CME through a SIP trunk. An incoming call to Cisco Unified CME that is targeted to a call center phone is routed to Unified CCX through the route point. The call is placed in a queue and redirected to the most suitable agent by Unified CCX.
Supplementary services such as call hold, blind transfer, and semi-attended transfer are initiated by Unified CCX. Existing SIP-based simple and supplementary service call flow applies except for blind transfers. For blind transfers with Unified CCX as the transferrer, Unified CCX will stay in the active state until the transfer target answers. It drops out only after the transferred call is successfully answered. If the transfer target does not answer when ringing times out, the call is pulled back by Unified CCX and rerouted to another agent. This mechanism also applies when the transfer target is configured with call-forward all or forward no-answer. The forward configuration is ignored during blind transfer.
When a call moves between Unified CCX and Cisco Unified CME because of redirect, transfer, and conference, the SIP Call-ID continues to change. For call control purposes, Cisco Unified CME issues a unique Global Call ID (Gcid) for every outbound call leg. A Gcid remains the same for all legs of the same call in the system, and is valid for redirect, transfer, and conference events, including 3-party conferencing when a call center phone acts as a conference host.
Table 63 contains a list of tasks required to enable operability between Cisco Unified CME and Unified CCX, presented in the order in which the tasks are to be completed. This section contains information about performing tasks in the first 2 steps in this table and procedures for completing step 3.
For configuration information, see the "How to Configure Interoperability with External Services" section.
Table 63 Tasks to Configure Interoperability between Cisco CRS and Cisco Unified CME
Step Task Name of Document1
Verify that Cisco Unified Communications Manager Express (Cisco Unified CME) 4.2 or a later version is installed on the router.
—
2
Configure the Cisco Unified CME router.
TipNote the AXL user ID, password, and router's IP address.
3
Configure Cisco Unified CME to enable interoperability with Unified CCX.
4
Install Cisco Unified Contact Center Express (Unified CCX) for Cisco Unified CME.
Cisco CRS Installation Guide at http://www.cisco.com/en/US/products/sw/custcosw/ps1846/prod_installation_guides_list.html.
5
Perform the initial setup of Cisco CRS for Cisco Unified CME.
TipWhen setup launches, you are asked for the AXL user ID and password that you created in Cisco Unified CME. You also need to enter the router IP address.
6
Configure CME Telephony Subsystem to enable interoperability with Unified CCX.
Cisco CRS Administration Guide at http://www.cisco.com/en/US/products/sw/custcosw/ps1846/prod_maintenance_guides_list.html.
7
Create users and assign the agent capability in Cisco CRS.
How to Configure Interoperability with External Services
This section contains the following procedures:
•
Configuring Cisco Unified CME to Enable Interoperability with Unified CCX (required)
•
Identifying Agent Directory Numbers in Cisco Unified CME for Session Manager (required)
•
Verifying Registrations and Subscriptions in Cisco Unified CME (optional)
•
Re-creating a Session Manager in Cisco Unified CME (optional)
•
Reconfiguring a Cisco CRS Route Point as a SIP Endpoint in Cisco Unified CME (optional)
Configuring Cisco Unified CME to Enable Interoperability with Unified CCX
To configure Cisco Unified CME to enable interoperability between Cisco Unified CME and Unified CCX, perform the following steps.
Note
A single Cisco Unified CME can support multiple session managers.
Prerequisites
•
Cisco Unified CME 4.2 or a later version
•
Cisco IOS Release 12.4(11)XW2 or a later version
•
XML API must be configured to create a username for Unified CCX access. For configuration information, see "Configuring the XML API" on page 1005. Make note of the user ID, password, and router's IP address for using during the initial setup of Cisco CRS for Cisco Unified CME.
•
Phones to be connected in Cisco Unified CME must be configured. When configuring a Unified CCX agent phone, use the keep-conference endcall command to enable conference initiators to exit from conference calls and end the conference for the remaining parties. For configuration information, see "Configuring Conferencing" on page 665.
•
The Cisco Unified CME router must be configured to accept incoming presence requests. For configuration information, see "Configuring Presence Service" on page 843.
Restrictions
•
Interoperability between Cisco Unified CME and Unified CCX is restricted to one Unified CCX per Cisco Unified CME.
•
Maximum number of active Unified CCX agents supported: 50.
•
Support for Multi-Party Ad Hoc and Meet-Me Conferencing features is not provided.
•
Only incoming calls from PSTN trunk are supported for deployment of the interoperability feature. Other trunks, such as SIP and H.323, are supported as usual in Cisco Unified CME, however, not for customer calls to Unified CCX.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
voice call send-alert
4.
voice service voip
5.
callmonitor
6.
gcid
7.
allow-connections sip-to-sip
8.
no supplementary-service sip moved-temporary
9.
no supplementary-service sip refer
10.
sip
11.
registrar server [expires [max sec] [min sec]
12.
end
DETAILED STEPS
Identifying Agent Directory Numbers in Cisco Unified CME for Session Manager
To specify which directory numbers, associated with phone lines on Unified CCX agent phones, can be managed by a session manager, perform the following steps.
Prerequisites
•
Up to eight session managers must be configured in Cisco Unified CME.
•
Directory numbers associated with Unified CCX agent phones must be configured. Directory numbers for agent phones must be configured as dual lines to allow an agent to make two call connections at the same time using one phone line button. For configuration information, see "Configuring Phones to Make Basic Calls" on page 165.
Restrictions
•
Only SCCP phones can be configured as agent phones in Cisco Unified CME. The Cisco VG224 Analog Phone Gateway and analog and SIP phones are supported as usual in Cisco Unified CME, however, not as Unified CCX agent phones.
•
Cisco Unified IP Phone 7931 cannot be configured as an agent phone in Cisco Unified CME. Cisco Unified IP Phone 7931s are supported as usual in Cisco Unified CME, however, not as Unified CCX agent phones.
•
Shared-line appearance is not supported on agent phones. A directory number cannot be associated with more than one physical agent phone at one time.
•
Overlaid lines are not supported on agent phones. More than one directory number cannot be associated with a single line button on an agent phone.
•
Monitored mode for a line button is not supported on agent phones. An agent phone cannot be monitored by another phone.
•
For call forward and call pickup, the directory number of an agent cannot forward to a Cisco CRS route point.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ephone-dn dn-tag
4.
allow watch
5.
session-server {session-tag[,...session-tag]}
6.
end
DETAILED STEPS
Verifying Registrations and Subscriptions in Cisco Unified CME
Before using the system, verify registrations and subscriptions for Unified CCX endpoints.
Step 1
Use the show sip status registrar command to verify whether session manager and Cisco CRS route points are registered.
Step 2
Use the show presence subscription summary command to verify whether Cisco CRS route points and Unified CCX agent directory numbers are subscribed.
The following is sample output from the show presence subscription summary command. The first two rows show the status for two route points. The next two are for logged in agent phones.
Router# show presence subscription summaryPresence Active Subscription Records Summary: 15 subscriptionWatcher Presentity SubID Expires SibID Status======================== ======================== ====== ======= ====== ======CRScontrol@10.4.171.81 8101@10.4.171.34 4 3600 0 idleCRScontrol@10.4.171.81 8201@10.4.171.34 8 3600 0 idleCRScontrol@10.4.171.81 4016@10.4.171.34 10 3600 0 idleCRScontrol@10.4.171.81 4020@10.4.171.34 12 3599 0 idleRe-creating a Session Manager in Cisco Unified CME
Note
Provisioning and configuration information in Unified CCX is automatically provided to Cisco United CME. The following task is required only if the configuration from Unified CCX is deleted or must be modified.
To re-create a session manager in Cisco Unified CME for Unified CCX, perform the following steps.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
voice register session-server session-server-tag
4.
register-id name
5.
keepalive seconds
6.
end
DETAILED STEPS
Reconfiguring a Cisco CRS Route Point as a SIP Endpoint in Cisco Unified CME
Note
Provisioning and configuration information in Unified CCX is automatically provided to Cisco United CME. The following task is required only if the configuration from Unified CCX is deleted or must be modified.
To reconfigure a Cisco CRS route point as a SIP endpoint in Cisco Unified CME, perform the following steps.
Prerequisites
•
Directory numbers associated with Cisco CRS route points must be configured in Cisco Unified CME. For configuration information for directory numbers associated with SIP endpoints, see "Configuring Phones to Make Basic Calls" on page 165.
•
Directory numbers associated with Cisco CRS route points must be enabled to be watched. For configuration information, see "Configuring Presence Service" on page 843.
•
The mode cme command must be enabled in Cisco Unified CME.
Restrictions
•
Each Cisco CRS route point can be managed by only one session manager.
•
Each session manager can manage more than one Cisco CRS route point.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
voice register dn dn-tag
4.
number number
5.
allow watch
6.
refer target dial-peer
7.
exit
8.
voice register pool pool-tag
9.
number tag dn dn-tag
10.
session-server session-tag
11.
codec codec-type [bytes]
12.
dtmf-relay rtp-relay sip-notify
13.
end
DETAILED STEPS
Configuration Examples for Interoperability with Unified CCX
The following output from the show running-configuration command shows the configuration on a Cisco Unified CME router that will interoperate with Unified CCX.
!version 12.4service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname sb-sj3-3845-uut1!boot-start-markerboot-end-marker!card type t1 0 2card type t1 0 3logging buffered 1000000no logging consoleenable password password!no aaa new-modelnetwork-clock-participate wic 2network-clock-participate wic 3ip cef!!no ip dhcp use vrf connected!!ip dhcp excluded-address 192.0.2.250 192.0.2.254!ip dhcp pool ephonesnetwork 192.0.2.0 255.255.255.0option 150 ip 192.0.2.254default-router 192.0.2.254!!no ip domain lookup!isdn switch-type primary-5essvoice-card 0no dspfarm!!!!voice service voipgcidcallmonitorallow-connections h323 to h323allow-connections h323 to sipallow-connections sip to h323allow-connections sip to sipno supplementary-service sip moved-temporarilyno supplementary-service sip refersipregistrar server expires max 120 min 60!!voice class codec 1codec preference 1 g711ulawcodec preference 2 g729r8!!!!!!!!!!voice register globalmode cmesource-address 192.0.2.254 port 5060max-dn 720max-pool 240authenticate presenceauthenticate registerdialplan-pattern 1 511.... extension-length 4voicemail 9001create profile sync 0000347600391314!voice register session-server 1keepalive 300register-id SB-SJ3-UCCX1_1164774025000!voice register dn 1session-server 1number 8999allow watchrefer target dial-peer!voice register dn 2session-server 1number 8001allow watchrefer target dial-peer!voice register dn 3session-server 1number 8101allow watchrefer target dial-peer!voice register dn 11number 2011name ep-sip-1-11mwi!voice register dn 12number 2012name ep-sip-1-12mwi!voice register dn 16number 5016name rp-sip-1-16label SIP 511-5016mwi!voice register dn 17number 5017name rp-sip-1-17label SIP 511-5017mwi!voice register dn 18number 5018name rp-sip-1-18label SIP 511-5018mwi!voice register pool 1session-server 1number 1 dn 1number 2 dn 2number 3 dn 3dtmf-relay sip-notifycodec g711ulaw!voice register pool 11id mac 1111.0711.2011type 7970number 1 dn 11dtmf-relay rtp-ntevoice-class codec 1username 5112011 password 5112011!voice register pool 12id mac 1111.0711.2012type 7960number 1 dn 12dtmf-relay rtp-ntevoice-class codec 1username 5112012 password 5112012!voice register pool 16id mac 0017.0EBC.1500type 7961GEnumber 1 dn 16dtmf-relay rtp-ntevoice-class codec 1username rp-sip-1-16 password pool16!voice register pool 17id mac 0016.C7C5.0660type 7971number 1 dn 17dtmf-relay rtp-ntevoice-class codec 1username rp-sip-1-17 password pool17!voice register pool 18id mac 0015.629E.825Dtype 7971number 1 dn 18dtmf-relay rtp-ntevoice-class codec 1username rp-sip-1-18 password pool18!!!!!!!controller T1 0/2/0framing esfclock source internallinecode b8zspri-group timeslots 1-4,24!controller T1 0/2/1framing esfclock source internallinecode b8zspri-group timeslots 1-4,24!controller T1 0/3/0framing esfclock source internallinecode b8zsds0-group 0 timeslots 1-4 type e&m-immediate-start!controller T1 0/3/1framing esfclock source internallinecode b8zsds0-group 0 timeslots 1-4 type e&m-immediate-startvlan internal allocation policy ascending!!!!interface GigabitEthernet0/0ip address 209.165.201.1 255.255.255.224duplex autospeed automedia-type rj45!interface GigabitEthernet0/1ip address 192.0.2.254 255.255.255.0duplex autospeed automedia-type rj45!interface Serial0/2/0:23no ip addressencapsulation hdlcisdn switch-type primary-5essisdn protocol-emulate networkisdn incoming-voice voiceno cdp enable!interface Serial0/2/1:23no ip addressencapsulation hdlcisdn switch-type primary-5essisdn protocol-emulate networkisdn incoming-voice voiceno cdp enable!interface Service-Engine1/0ip unnumbered GigabitEthernet0/0service-module ip address 209.165.202.129 255.255.255.224service-module ip default-gateway 209.165.201.1!ip route 192.0.0.30 255.0.0.0 192.0.0.55ip route 209.165.202.129 255.255.255.224 Service-Engine1/0ip route 192.0.2.56 255.255.255.0 209.165.202.2ip route 192.0.3.74 255.255.255.0 209.165.202.3ip route 209.165.202.158 255.255.255.224 192.0.0.55!!ip http serverip http authentication localip http path flash:!!ixi transport httpresponse size 64no shutdownrequest outstanding 1!ixi application cmeno shutdown!!!control-plane!!!voice-port 0/0/0!voice-port 0/0/1!voice-port 0/2/0:23!voice-port 0/3/0:0!voice-port 0/1/0!voice-port 0/1/1!voice-port 0/2/1:23!voice-port 0/3/1:0!!!!!dial-peer voice 9000 voipdescription ==> This is for internal calls to CUEdestination-pattern 9...voice-class codec 1session protocol sipv2session target ipv4:209.165.202.129dtmf-relay rtp-nte sip-notify!dial-peer voice 9001 voipdescription ==> This is for external calls to CUEdestination-pattern 5119...voice-class codec 1session protocol sipv2session target ipv4:209.165.202.129dtmf-relay rtp-nte sip-notify!dial-peer voice 521 voipdestination-pattern 521....voice-class codec 1max-redirects 5session protocol sipv2session target ipv4:209.165.201.2dtmf-relay rtp-nte sip-notify!dial-peer voice 531 voipdestination-pattern 531....voice-class codec 1max-redirects 5session protocol sipv2session target ipv4:209.165.201.3dtmf-relay rtp-nte sip-notify!!presencepresence call-listwatcher allallow subscribe!sip-uamwi-server ipv4:209.165.202.128 expires 3600 port 5060 transport udppresence enable!!telephony-serviceno auto-reg-ephonexml user axluser password axlpass 15max-ephones 240max-dn 720ip source-address 192.0.2.254 port 2000system message sb-sj3-3845-uut1url services http://192.0.2.252:6293/ipphone/jsp/sciphonexml/IPAgentInitial.jspurl authentication http:192.0.2.252:6293/ipphone/jsp/sciphonexml/IPAgentAuthenticate.jspcnf-file perphonedialplan-pattern 1 511.... extension-length 4voicemail 9001max-conferences 8 gain -6call-forward pattern .Tmoh flash:music-on-hold.wavmulticast moh 239.10.10.1 port 2000transfer-system full-consulttransfer-pattern .Tcreate cnf-files version-stamp 7960 Jun 18 2007 07:44:25!!ephone-dn 1 dual-linesession-server 1number 1001name ag-1-1allow watchmwi sip!!ephone-dn 2 dual-linesession-server 1number 1002name ag-1-2allow watchmwi sip!!ephone-dn 3 dual-linesession-server 1number 1003name ag-1-3allow watchmwi sip!!ephone-dn 4 dual-linesession-server 1number 1004name ag-1-4allow watchmwi sip!!ephone-dn 5session-server 1number 1005name ag-1-5allow watchmwi sip!!ephone-dn 11 dual-linenumber 3011name ep-sccp-1-11mwi sip!!ephone-dn 12number 3012name ep-sccp-1-12mwi sip!!ephone-dn 16 dual-linenumber 4016label SCCP 511-4016name rp-sccp-1-16mwi sip!!ephone-dn 17 dual-linenumber 4017label SCCP 511-4017name rp-sccp-1-17mwi sip!!ephone-dn 18 dual-linenumber 4018label SCCP 511-4018name rp-sccp-1-18mwi sip!!ephone-dn 19 dual-linenumber 4019label SCCP 511-4019name rp-sccp-1-19mwi sip!!ephone-dn 20 dual-linenumber 4020label SCCP 511-4020name rp-sccp-1-20mwi sip!!ephone-dn 21 dual-linenumber 4021label SCCP 511-4021name rp-sccp-1-21mwi sip!!ephone-dn 22 dual-linenumber 4022label SCCP 511-4022name rp-sccp-1-22mwi sip!!ephone 1mac-address 1111.0711.1001type 7970keep-conference endcallbutton 1:1!!!ephone 2mac-address 1111.0711.1002type 7970keep-conference endcallbutton 1:2!!!ephone 3mac-address 1111.0711.1003type 7970keep-conference endcallbutton 1:3!!!ephone 4mac-address 1111.0711.1004type 7970keep-conference endcallbutton 1:4!!!ephone 5mac-address 1111.0711.1005type 7970keep-conference endcallbutton 1:5!!!ephone 11mac-address 1111.0711.3011type 7970keep-conference endcallbutton 1:11!!!ephone 12mac-address 1111.0711.3012type 7960keep-conference endcallbutton 1:12!!!ephone 16mac-address 0012.D916.5AD6type 7960keep-conference endcallbutton 1:16!!!ephone 17mac-address 0013.1AA6.7A9Etype 7960keep-conference endcallbutton 1:17!!!ephone 18mac-address 0012.80F3.B013type 7960keep-conference endcallbutton 1:18!!!ephone 19mac-address 0013.1A1F.6282type 7970keep-conference endcallbutton 1:19!!!ephone 20mac-address 0013.195A.00D0type 7970keep-conference endcallbutton 1:20!!!ephone 21mac-address 0017.0EBC.147Ctype 7961GEkeep-conference endcallbutton 1:21!!!ephone 22mac-address 0016.C7C5.0578type 7971keep-conference endcallbutton 1:22!!!line con 0exec-timeout 0 0stopbits 1line aux 0stopbits 1line 66no activation-characterno exectransport preferred nonetransport input alltransport output pad telnet rlogin lapb-ta mop udptn v120line vty 0 4password lablogin!scheduler allocate 20000 1000!endWhere to Go Next
If you are done modifying parameters for phones in Cisco Unified CME, generate a new configuration file and restart the phones. See "Generating Configuration Files for Phones" on page 265.
Additional References
The following sections provide references related to Cisco Unified CME features.
Related Documents
Related Topic Document TitleCisco Unified CME configuration
•
Cisco Unified CME Command Reference
•
Cisco Unified CME documentation roadmap
Cisco Unified Contact Center Express (Unified CCX)
•
Cisco Unified Contact Center Express documentation road map
Cisco Customer Response Solutions (CRS)
•
Cisco CRS Installation Guide
Cisco IOS commands
•
Cisco IOS Voice Command Reference
Cisco IOS configuration
•
Cisco IOS Voice Configuration Library
Phone documentation for Cisco Unified CME
Technical Assistance
Feature Information for Interoperability with External Services
Table 64 lists the features in this module and enhancements to the features by version.
To determine the correct Cisco IOS release to support a specific Cisco Unified CME version, see the Cisco Unified Communications Manager Express and Cisco IOS Software Version Compatibility Matrix at http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_documentation_roadmap09186a0080189132.html.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 64 lists the Cisco Unified CME version that introduced support for a given feature. Unless noted otherwise, subsequent versions of Cisco Unified CME software also support that feature.
Posted: Wed Aug 15 14:23:51 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.