The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any configuration.
Step 1. Configure the CTI Remote Device (CTI RD) phone profile for the same user who has Jabber already configured.
When you configure the CTI RD, associate to the same Jabber user. The line configuration will be same as the Jabber Client Services Framework (CSF) device line
Rerouting calling search space needs to be configured correctly for the remote destination calls to work
Step 2. Configure the remote destination.
In this example I have used 3001 as the remote destination number. This remote destination number should be an external number (number external to the CUCM cluster where Jabber is registered, for example another telephony system)
Step 3. Associate the CTI RD profile to the end user.
Step 4. Once you login to Jabber you will see an option to set the Jabber phone services to use the Extend and Connect device (Use other number for calls). When using "Edit number" option there should be a matching route pattern for the new number.
Once we set the Jabber to use Extend and Connect device, the phone icon will display on Jabber as below.
Call flow for an outbound Jabber Extend and Connect call is illustrated in below image
In this example when the remote destination ("other number") rings, it does not have a calling party number displayed. Due to this, they cannot distinguish whether the call is from an external party or from Jabber using Extend and Connect. When using Extend and Connect, CUCM initiates the call to the remote device and does not send calling party information by default.
We can see in the following Digit Analysis excerpt for an Extend and Connect call that the CallingPartyNumber field is empty.