Cisco Unified Communications Manager Features and Services Guide, Release 9.1(1) - Extend and Connect [Cisco Unified Communications Manager (CallManager)]

Contents
Extend and Connect
Extend and Connect
Overview of Extend and Connect
Features and Benefits
Use Cases
System Architecture
Call Flow
System Requirements
Software Components
Licensing Requirements
Interactions and Restrictions
Interactions
Directory URI Dialing
Restrictions
Presence Information
CallerID Information
Performance and Scalability
Extend and Connect Setup
Set Up User Account
Add User Permissions
Create CTI Remote Devices
Add Directory Number to Device
Associate User to Device
Add Remote Destination
Create CCMIP Profile
Extend and Connect

This chapter provides information about the Extend and Connect feature. This chapter contains the following information:

Extend and Connect
System Requirements
Interactions and Restrictions
Presence Information
CallerID Information
Performance and Scalability
Extend and Connect Setup

Extend and Connect

Overview of Extend and Connect

Changes in personal device preferences and an increasing number of mobile and remote workers necessitates a flexible solution that extends Unified Communications (UC) features with a Bring Your Own Device (BYOD) philosophy. Extend and Connect provides this solution.

Extend and Connect is a feature that allows administrators to rapidly deploy UC Computer Telephony Integration (CTI) applications which interoperate with any endpoint. With Extend and Connect, users can leverage the benefits of UC applications from any location using any device. This feature also allows interoperability between newer UC solutions and legacy systems, so customers can migrate to newer UC solutions over time as existing hardware is deprecated.

Features and Benefits

Features
The Extend and Connect feature for Unified CM provides the following UC features:

Receive incoming enterprise calls

Make Call

Disconnect

Hold and Retrieve

Redirect and Forward

Call Forward All

Do Not Disturb

Play DTMF (out-of-band)

Consult Transfer, Conference

Add, edit, and delete Remote Destinations

Set Remote Destination as Active or Inactive

Benefits
The Extend and Connect feature for Unified CM provides the following benefits to its users:

Standardized call control across the Enterprise

Centralized applications

Simplified integration points and network topology

Centralized licensing

Centralized call-detail records for accounting and billing

Accelerated application deployment

Existing investments in legacy PBXs and devices are preserved

Migration to Cisco IP devices over time is enabled

Use Cases

Cisco Jabber for Customers with a Third-Party PBX

Customers want to deploy Cisco Jabber for Windows as the desktop standard for IM and Presence capability, but they have not yet decided to adopt Cisco IP devices. They plan to migrate to Cisco IP devices over time, or they need to maintain a hybrid device environment.

Cisco Jabber for Mobile Workers
Users want to use Cisco Jabber for Windows to make and receive calls using a home or hotel phone, because their PC hardware or available network connection does not support VoIP. they want the convenience of Jabber click-to-call features to work with the device they are sitting next to at that moment.

Users want to use Cisco Jabber for Windows because they want the convenience of Jabber click-to-call features to work with the device they are sitting next to at that moment.

Users already have a Cisco Unified IP Phone, Jabber Softphone, or both, but they also want to use Jabber with a home or hotel phone.

System Architecture

Figure 1. Extend and Connect System Architecture. The following graphic represents the system architecture for the Extend and Connect feature.

A CTI Remote Device is registered to Unified CM. For example, directory number (DN) 2000 is the internal and external extension, of the user, represented as +1 408 200 2000 or 2000.

Remote Destinations represent the off-cluster devices of a user.

Off-cluster devices are registered to the PBX or PSTN.

CTI applications receive call events and can perform call operations.

Trunks connect Unified CM with the PSTN or PBX. Supported types include PRI , BRI , SIP, and FXO.

Note

When you use remote destinations across MGCP gateways, the display name, the display number, and the call information that is passed across the gateway cannot be updated after the call is answered. This is a limitation of the MGCP protocol.

Call Flow

This section describes the flow of events for Extend and Connect from a system perspective. Understanding the call flow helps you troubleshoot problems that you may have with the feature.

Unified CM and Cisco Unified Communications Manager Session Management Edition (Unified CM SME) control the Enterprise PSTN trunking and dial-plan.

Administrators add users to Unified CM and assign them a new CTI Remote Device type.

Each CTI Remote Device is configured with the user work number directory number (DN) (for example, 2000) and a remote destination which represents any off-cluster device (for example, a PBX phone with the number +1 408 555 5555).

Administrators can configure remote destinations using the Cisco Unified Communications Manager Administration interface, Administrative XML (AXL) interface, or the Bulk Administration Tool (BAT), and end users can configure remote destinations using the Jabber client.

Users sign in to Jabber and select Use my other device.

Users may add a new remote destination (for example, home office, +1 415 777 7777) or can select from previously configured remote destinations.

The Jabber client marks the selected remote destination as Active.

Incoming calls to the work DN (+1 408 200 2000) are automatically routed to the active destination (+1 415 777 7777).

Outbound call requests follow a Dial Via Office reverse call flow, as follows:
The user clicks to call.

A server call is placed to the active remote destination.

The user answers the server (DVO) call.

The call is immediately redirected to the desired number.

During calls, midcall features are available through the Jabber client, such as Hold and Resume, Consult, Conference, and Transfer.

When users shut down or sign out of the Jabber client, the remote destination is marked Inactive.

When remote destinations are inactive, calls to the DN are routed to voicemail or all remote destinations based on their schedule (for Single Number Reach).

Figure 2. Incoming Call from PBX. The following illustration shows a sample incoming call from the PBX.

Figure 3. Outgoing Call to PBX. The following illustration shows a sample outgoing call to the PBX.

System Requirements

Software Components

To operate correctly, this version of Extend and Connect requires the following software components:
Cisco Unified Communications Manager, Release 9.1(1)

Cisco Jabber for Windows, Release 9.1(1)
The initial release supports the third-party PBX use case.

The maintenance Release adds support for the mobile worker use case.

For more information and use cases, see the Cisco Jabber for Windows Install and Upgrade Guides.

Licensing Requirements

Extend and Connect operates under the following licenses:

CUWL Standard

CUWL Professional

UCL-Enhanced

Interactions and Restrictions

This section describes the interactions and restrictions for Extend and Connect.

Interactions
Restrictions

Interactions

Directory URI Dialing

A Directory URI is the SIP address of a user that takes the form user@host, where user specifies a phone number or user name and host specifies the IP address, domain, or hostname where the user is available. You can assign multiple URIs to a single DN. End user Directory URIs are automatically associated to the primary extension for the user.

You can configure a Directory URI as the DN, remote destination, or both for the CTI remote device.

Restrictions

The following restrictions apply to Extend and Connect:

You can configure up to ten remote destinations for each CTI remote device.

Note
The default maximum is four per device.

Remote destination numbers must represent off-cluster devices.

Remote destinations can be off-cluster URIs.

Directory numbers cannot be configured as remote destination numbers.

Remote destinations that are configured using Cisco Jabber for Windows are verified to be routable by the configured dial plan before they are saved.

Remote destination numbers are validated using the CTI remote device reroute calling search space.

Remote destinations that are configured using the Cisco Unified Communications Manager Administration interface and AXL interface are not validated.

Application Dial Rules are applied to all remote destinations that are configured on the CTI remote device through the Cisco Unified Communications Manager Administration interface and Cisco Jabber for Windows.

Note
Advise end users which number formats the Application Dial Rules are configured to support (for example, nn-nnn-nnnn, E.164, both).

Each remote destination number must be unique within the cluster.
The same remote destination number cannot be used by two or more users.

The same remote destination number cannot be used by the same user on two or more different device types (for example, Remote Destination Profile + CTI Remote Device). .

Presence Information

The presence status "on a call" is displayed for a user in the following situations:
Outgoing Calls
The user initiates a call from Cisco Jabber for Windows in Extend and Connect mode.

The user initiates a call from a device that is configured as a remote destination which is routed using Unified CM or Unified CM with Unified CM SME.

Incoming Calls
The user answers a call on a device configured as a remote destination routed using Unified CM or Unified CM with Unified CM SME.

The user answers a call routed to a device configured as a remote destination using Cisco Single Number Reach.

The presence status "on a call" is not displayed for a user in the following situations:

When the user initiates a call from a device that is configured as a remote destination; the call is not routed using Unified CM or Unified CM with Unified CM SME.

When the user answers a call on a device that is configured as a remote destination; the call is not routed using Unified CM or Unified CM with Unified CM SME.

CallerID Information

The follow information explains the CallerID behavior for Extend and Connect:

The incoming CallerID information (name and number) is displayed in the Jabber client.

This information may also be displayed on the device, depending on your carrier and trunk configuration.

Outbound Dial Via Office calls to the remote destination display Voice Connect as the name and the trunk DID as the number.

Configure the trunk DID in the Unified CM Trunk Pattern, Route Pattern, or Cisco Gateway. This configuration may also be assigned by the carrier. The number field may display as blank if the trunk DID is not configured.

Outbound calls to the desired party display the CTI Remote Device Display Name and Directory Number (DN) as configured in Unified CM.

Remote destination numbers are never displayed to the called party.

Performance and Scalability

This section details performance and scalability information that relates to Extend and Connect resources.

Busy Hour Call Attempts
Add 1 to the Busy Hour Call Attempts (BHCA) for each outbound call. BHCA is the number of attempted calls at the busiest hour of the day.
A Dial via Office call to the active remote destination is one call.

A redirect from the active remote destination to the desired called party is one call.

Trunk Usage
Incoming calls may consume one or more outbound trunks.
An internal call that is routed to the active remote destination uses one external trunk.

A received external call that is routed to the active remote destination uses two external trunks: one trunk for the incoming leg and one trunk for the outgoing leg.

Outgoing calls follow a Dial via Office flow that may consume one or more outbound trunks per call.
A call to a cluster directory number uses one external trunk for a Dial via Office call to an active remote destination.

A call to an external party uses one external trunk for a Dial via Office call to an active remote destination, as well as one external trunk for a redirect to an external called party.

CTI Device Weight

The weight of each CTI remote device is the same as a standard Cisco Unified IP Phone (SIP) device.
An MCS-7845- I3 / H3 subscriber that is running Cisco Unified Communications Manager Release 9.1(1) can support a maximum of 10,000 Cisco Unified IP Phones when each phone is a CTI remote device.

Each CTI remote device can be configured with five lines using five concurrent CTI applications.

Note

Use the Cisco Unified Communications Sizing Tool when sizing production clusters.

Extend and Connect Setup

This section describes the procedures that you must complete to provision Cisco Unified Communications Manager users with Extend and Connect capabilities.

For information about provisioning Cisco Jabber for Windows users with Extend and Connect, see the Cisco Jabber for Windows Environment Configuration Guide.

Set Up User Account
Create CTI Remote Devices
Add Directory Number to Device
Associate User to Device
Add Remote Destination
Create CCMIP Profile

Set Up User Account

For a new or existing user in Unified CM, you must enable user mobility to provision CTI remote devices. If you do not enable mobility for users, you cannot assign those users as owners of CTI remote devices.

Procedure
Step 1   Select User Management > End User.
The Find and List Users window appears.

Step 2   Perform one of the following:
To configure a new user, select Add New.

To select an existing user, specify the appropriate filters in the Find User Where field, select Find to retrieve a list of users, and then select the user from the list.

Note
You may add the new end user account via LDAP integration or local configuration.

The End User Configuration window appears.

Step 3   Locate the Mobility Information section.

Step 4   Select Enable Mobility.

Step 5   Select Save.

What to Do Next
Add user permissions.

Add User Permissions

After the end user is active in Unified CM, add access control group permissions.

Procedure
Step 1   Select User Management > End User.
The Find and List Users window appears.

Step 2   Specify the appropriate filters in the Find User where field, and then select Find to retrieve a list of users.

Step 3   Select the user from the list.
The End User Configuration window appears.

Step 4   Locate the Permissions Information section.

Step 5   Select Add to Access Control Group.
The Find and List Access Control Groups window appears.

Step 6   Select Find.
The Access Control Group list for Standard Users appears.

Step 7   Check the check boxes next to the following permissions:
Standard CCM End-Users

Standard CTI Enabled

Standard CCMUSER Administration

Step 8   Select Add Selected.
The window closes and the access control groups are added to the user account.

Step 9   Select Save.

What to Do Next
Create CTI remote devices.

Create CTI Remote Devices

A CTI remote device is a new device type that represents off-cluster phones that users can use with Cisco UC applications. The device type is configured with one or more lines (directory numbers) and one or more remote destinations.

Unified CM provides Extend and Connect capabilities to control calls on devices such as public switched telephone network (PSTN) phones and private branch exchange (PBX) devices.

Procedure
Step 1   Open the Cisco Unified Communications Manager Administration interface.

Step 2   Select Device > Phone.
The Find and List Phone Window appears.

Step 3   Select Add New.

Step 4   Select CTI Remote Device from the Phone Type drop-down list and then select Next.
The Phone Configuration window appears.

Step 5   Select the appropriate user ID from the Owner User ID drop-down list.
Note
Only users for whom you enable mobility are available from the Owner User ID drop-down list.

Unified CM populates the Device Name field with the user ID and a CTRID prefix, for example, CTRIDusername.

Step 6   Edit the default value in the Device Name field, if appropriate.

Step 7   Enter a meaningful description in the Description field.
Tip
Cisco Jabber for Windows displays device descriptions to users. If Cisco Jabber for Windows users have multiple devices of the same model, the descriptions from Unified CM help users tell the difference between them.

Step 8   Ensure you select an appropriate option from the Rerouting Calling Search Space drop-down list in the Protocol Specific Information section.
The Rerouting Calling Search Space drop-down list defines the calling search space for rerouting and ensures that users can send and receive calls from the CTI remote device.

Step 9   Specify all other configuration settings on the Phone Configuration window as appropriate.
For more information, see "CTI Remote Device Setup" in the Cisco Unified Communications Manager Administration Guide.

Step 10   Select Save.
The fields to associate directory numbers and add remote destinations become available on the Phone Configuration window.

What to Do Next
Add a directory number to the device.

Add Directory Number to Device

A directory number (DN) is a numerical address that is configured as a line on the CTI remote device. A DN typically represents the primary work number of a user (for example, 2000 or +1 408 200 2000).

You must add directory numbers to devices in Unified CM. This procedure provides instructions for adding directory numbers using the Device > Phone menu option after you create your device. Under this menu option, only the configuration settings that apply to the phone model or CTI route point display. See the Cisco Unified Communications Manager Administration Guide for more information about different options to configure directory numbers.

Procedure
Step 1   Locate the Association Information section on the Phone Configuration window.

Step 2   Select Add a new DN.
The Directory Number Configuration window appears.

Step 3   Specify a directory number in the Directory Number field.

Step 4   Specify all other required configuration settings as appropriate.

Step 5   Associate end users with the directory number as follows:
Locate the Users Associated with Line section.

Select Associate End Users.
The Find and List Users dialog box appears.

Specify the appropriate filters in the Find User Where field and then select Find to retrieve a list of users.

Select the appropriate users from the list.

Select Add Selected.
The selected users are added to the voicemail profile.

Step 6   Select Save.

Step 7   Select Apply Config.
The Apply Configuration window opens.

Step 8   Follow the prompts on the Apply Configuration window to apply the configuration.

What to Do Next
Associate a user to the device.

Associate User to Device

Before You Begin
You must create or modify an end user account and enable it for mobility. You must also create a CTI device.

Procedure
Step 1   Navigate to the end user account.

Step 2   Locate the Device Information section.

Step 3   Select Device Association.

Step 4   Find and select the CTI remote device.

Step 5   Verify that the selected device appears as a controlled device for the user.

What to Do Next
Add a remote destination.

Add Remote Destination

A remote destination is a numerical address that represents the other phones that the user owns (for example, a home office line or other PBX phone). A remote destination may be any off-cluster device.

This procedure to add a remote destination is optional.

Note

Administrators can determine which remote destination the Jabber client has set as Active from the Cisco Unified Communications Manager Administration interface.

Note
Unified CM users can add remote destinations through the Cisco Jabber for Windows interface. For more information, see the Cisco Jabber for Windows Environment Configuration Guide.

Unified CM automatically verifies whether it can route remote destinations that Cisco Jabber for Windows users add through the client interface.

Unified CM does not verify whether it can route remote destinations that you add through the Cisco Unified CM Administration interface.

Note
Unified CM automatically applies application dial rules to all remote destination numbers for CTI remote devices. For more information about application dial rules, see "Application Dial Rule Setup" in the Cisco Unified Communications Manager Administration Guide.

Procedure
Step 1   From Cisco Unified Communications Manager Administration, select Device > Phone
The Find and List Phones window appears.

Step 2   Specify the appropriate filters in the Find Phone Where field to and then select Find to retrieve a list of phones.

Step 3   Select the CTI remote device from the list.
The Phone Configuration window appears.

Step 4   Locate the Associated Remote Destinations section.

Step 5   Select Add a New Remote Destination.
The Remote Destination Information window appears.

Step 6   Enter the destination number in the Destination Number field and specify all other values as appropriate.
To use the remote destination with Cisco Jabber clients, you must configure the destination name as JabberRD.

For more information about configuring remote destinations, see "Remote Destination Setup" in the Cisco Unified Communications Manager Administration Guide.

Step 7   Select Save.

What to Do Next
Complete the following steps to verify the remote destination and apply the configuration to the CTI remote device:
Repeat the steps to open the Phone Configuration window for the CTI remote device.

Locate the Associated Remote Destinations section.

Verify that the remote destination is available.

Select Apply Config.

Note
The Device Information section on the Phone Configuration window contains an Active Remote Destination field.

Create CCMIP Profile

Cisco Jabber for Windows requires a Cisco Unified Communications Manager IP Phone (CCMCIP) profile to retrieve device names and settings from Unified CM. For more information about CCMIP profiles, see related topics in the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager.

Procedure
Step 1   Open the Cisco Unified CM IM and Presence Administration or Cisco Unified Presence Administration interface.

Step 2   Select Application > Cisco Jabber > CCMCIP Profile. In some versions of Cisco Unified Presence, this path is as follows: Application > Cisco Unified Personal Communicator > CCMCIP Profile.

Step 3   Select Add New.

Step 4   Specify a name for the profile in the Name field.

Step 5   Specify the hostname or IP address of your primary Unified CM instance in the Primary CCMCIP Host field.

Step 6   Specify the hostname or IP address of your backup Unified CM instance in the Primary CCMCIP Host field.

Step 7   Leave the default value for Server Certificate Verification.

Step 8   Select Add Users to Profile.

Step 9   Add the appropriate users to the CCMCIP gateway profile.

Step 10   Select Add Selected.

Step 11   Select Save.