McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 104

↗ View in doc context
page
104
source
cucm/v15/feature-config-guide/feature-config-guide.md
chunk_id
cucm::v15::feature-config-guide::feature-config-guide::60

Extend and Connect Interactions Table 9: Extend and Connect Interactions Interaction Feature Configure a Directory URI as the DN, remote destination, or both for the CTI remote device. Directory URI Dialing 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. Unified Mobility The Extend and Connect feature allows users to receive hunt calls on remote destination phones under the following conditions: • The user has a Cisco Unified IP Phone. • The Cisco Unified IP Phone is available to answer hunt calls (logged-in/HLog). • Cisco Jabber is running in Extend and Connect mode. Hunt List • The incoming caller ID information (name and number) is displayed on 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 Communications Manager. • Remote destination numbers are never displayed to the called party. CallerID Information Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 62 Remote Worker Features Extend and Connect Interactions