The Extend and Connect feature allows administrators to deploy Unified Communications (UC) Computer Telephony Integration (CTI) applications that interoperate with any endpoint. With Extend and Connect, users can access UC applications from any location using any device.
The Extend and Connect feature for Unified Communications Manager 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 Dual Tone Multi Frequency (DTMF) (out-of-band and in-band)
Consult Transfer, Conference
Add, edit, and delete remote destinations
Set remote destination as Active or Inactive
Persistent Connection
Play Whisper Announcement
Review Extend and Connect Prerequisites.
Command or Action | Purpose | |
---|---|---|
Step 1 | Configure User Account
| Enable mobility for users so that they can use CTI remote devices. CTI devices are off-cluster phones that work with Cisco UC applications. |
Step 2 | Add User Permissions
| Add access control group permissions. |
Step 3 | Create CTI Remote Devices
| Configure off-cluster phones that users can use with Cisco UC applications. |
Step 4 | Add Directory Number to a Device
| Associate a directory number with the CTI remote device. |
Step 5 | (Optional) Add Remote Destination |
Add a numerical address or directory URI that represents the other phones that the user owns. |
Step 6 | (Optional) Verify Remote Destination |
Verify if the remote destination is successfully added for a user. |
Step 7 | Associate User with Device
| Associate an end user account to the CTI remote device. |
After the end user is active in Unified Communications Manager, add access control group permissions.
Step 1 | From Cisco
Unified CM Administration, choose
.
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 | Click
Add to
Access Control Group.
The Find and List Access Control Groups window appears. |
Step 6 | Click
Find.
The Access Control Group list for Standard Users appears. |
Step 7 | Check the check boxes next to the following permissions: |
Step 8 | Click
Add
Selected.
The window closes and the access control groups are added to the user account. |
Step 9 | Click Save. |
A CTI remote device is a 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 Communications Manager provides Extend and Connect capabilities to control calls on devices such as public switched telephone network (PSTN) phones and private branch exchange (PBX) devices.
Step 1 | From Cisco
Unified CM Administration, choose
.
The Find and List Phone window appears. | ||
Step 2 | Click Add New. | ||
Step 3 | Select
CTI
Remote Device from the
Phone
Type drop-down list and then click
Next.
The Phone Configuration window appears. | ||
Step 4 | Select the
appropriate user ID from the
Owner
User ID drop-down list.
Unified Communications Manager populates the Device Name field with the user ID and a CTRID prefix, for example, CTRIDusername. | ||
Step 5 | Edit the default value in the Device Name field, if appropriate. | ||
Step 6 | Enter a
meaningful description in the
Description field.
| ||
Step 7 | Ensure that
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 8 | Configure the remaining fields in the Phone Configuration window. See the online help for more information about the fields and their configuration options. | ||
Step 9 | Click
Save.
The fields to associate directory numbers and add remote destinations are displayed in the Phone Configuration window. |
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).
![]() Note | The Calling Search Space (CSS) and partition of DN are mandatory on devices. |
![]() Note | The CTI Remote Device should not block its own DN. The CSS is important for the CTIRD device to reach its own DN. |
Follow these steps to add a directory number to a CTI remote device.
Step 1 | Locate the Association Information section in the Phone Configuration window. |
Step 2 | Click
Add a
new DN.
The Directory Number Configuration window appears. |
Step 3 | Specify a directory number in the Directory Number field. |
Step 4 | Configure all other required fields. See the online help for more information about the fields and their configuration options. |
Step 5 | Click Save. |
A remote destination is a numerical address or directory URI 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. Unified Communications Manager automatically applies application dial rules to all remote destination numbers for CTI remote devices. By default, four remote destinations are supported per device. You can set the maximum number to 10 remote destinations per device in End User Configuration window.
![]() Note | You can determine which remote destination the Jabber client has set as Active by opening the Phone Configuration window from the Cisco Unified Communications Manager Administration interface. |
![]() Note | Unified Communications Manager users can add remote destinations through the Cisco Jabber interface. For more information, see the Cisco Jabber for Windows Installation and Configuration Guide at http://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-installation-guides-list.html.
|
Step 1 | From
Cisco Unified
Communications Manager Administration, choose
.
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 | Click
Add a
New Remote Destination.
The Remote Destination Information window appears. |
Step 6 | Enter the
destination number in the
Destination Number field.
To use the remote destination with Cisco Jabber clients, you must configure the destination name as JabberRD. |
Step 7 | Configure the remaining fields in the Remote Destination Information window. See the online help for more information about the fields and their configuration options. |
Step 8 | Click Save. |
Step 1 | From
Cisco Unified
Communications Manager Administration, choose
.
The Find and List Phones window appears. | ||
Step 2 | Specify the appropriate filters in the Find Phone Where field to and then click 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 and verify that the remote destination is available. | ||
Step 5 | Click
Apply
Config.
|
Step 1 | From Cisco Unified CM Administration, choose . |
Step 2 | Specify the appropriate filters in the Find User Where field to and then click 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 Device Information section. |
Step 5 | Click Device Association. The User Device Association window appears. |
Step 6 | Find and select the CTI remote device. |
Step 7 | To complete the association, click Save Selected/Changes. |
Step 8 | From Related Links drop-down list box, choose Back to User, and then click Go. The End User Configuration window appears, and the associated device that you chose appears in the Controlled Devices pane. |
Feature |
Interaction |
---|---|
Directory URI Dialing |
Configure a Directory URI as the DN, remote destination, or both for the CTI remote device. |
Unified Mobility |
Extend and Support does not support moving active calls between a Cisco Unified IP Phone and a remote destination. If you want the capabilities of both Unified Mobility and Extend and Connect, you can configure the same remote destination on the Remote Device Profile and CTI Remote Device types when the Owner ID of both device types is the same. This configuration allows Cisco Mobility features to be used concurrently with Extend and Connect. The ability to configure the same remote destination on both device types is supported using Cisco Unified Communications Manager Release 10.0(1) or later. Do not configure remote destinations that are used with the Cisco Extend and Connect feature on Cisco Dual-mode for iPhone, Cisco Dual-mode for Android, and Carrier-integrated Mobile device types. Do not use prefixes to differentiate the same remote destination address. For example, 91-4085555555 and +1-4085555555 are treated as the same number. |
Hunt List |
The Extend and Connect feature allows users to receive hunt calls on remote destination phones under the following conditions: |
CallerID Information |
|
Restriction |
Description |
||
---|---|---|---|
Maximum number of remote destinations |
You can configure up to ten remote destinations for each CTI remote device.
|
||
Off-cluster devices |
|||
Directory numbers |
You cannot configure directory numbers as remote destination numbers. |
||
Cisco Jabber |
Before you save the remote destinations that are configured using Cisco Jabber, verify if the remote destinations can be routed by the configured dial plan. |
||
Application dial rules |
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.
|
||
Remote destination number |
Each remote destination number must be unique within the cluster.
|
||
Remote destination validation |