- Jabber Overview
- Workflows for Cloud and Hybrid Deployments
- Configure Policies
- Configure Clusters
- Create Users for Cloud Deployment
- Create Users for Hybrid Deployment
- Configure Deskphone Control
- Configure Softphone
- Configure Extend and Connect
- Configure Service Discovery for Remote Access
- Set Up Certificate Validation
- Configure the Clients
- Deploy Cisco Jabber Applications
- Remote Access
- Troubleshooting
Configure Softphone
Configure Softphones Workflow
Command or Action | Purpose | |
---|---|---|
Step 1 | Create and Configure Cisco Jabber Devices
|
Create at least one device for every user that will access Cisco Jabber. |
Step 2 | Configure User Associations
| |
Step 3 | Create Mobile SIP Profiles. |
Complete this task if you have Cisco Unified Communications Manager release 9 and plan to configure devices for mobile clients. |
Step 4 | Configure the Phone Security Profile
|
Complete this task to set up secure phone capabilities for all devices. |
Step 5 | Provide Users with Authentication Strings
|
Create and Configure Cisco Jabber Devices
Create at least one device for every user that accesses Cisco Jabber. A user can have multiple devices.
Note | Users can only remove participants from a conference call when using the softphone(CSF) device for calls. |
-
Install COP files.
-
Enable mobility for each user for whom you plan to assign to a CTI remote device.
-
Create SIP profiles if you have Cisco Unified Communications Manager release 9 or earlier and plan to configure devices for mobile clients.
-
Create the Phone Security Profile if you plan to set up secure phone capabilities for all devices.
-
For Cisco Unified Communications Manager release 10 or later, ensure that the Cisco Certificate Authority Proxy Function (CAPF) service parameters value for Certificate Issuer to Endpoint is Cisco Certificate Authority Proxy Function, this is the only option supported by Cisco Jabber. For information on configuring the CAPF service parameter see the Update CAPF Service Parameters topic in the Cisco Unified Communications Manager Security Guides.
Before you create TCT devices, BOT devices, or TAB devices for Cisco Jabber for mobile users, specify the organization top domain name to support registration between Cisco Jabber and the Cisco Unified Communications Manager. In Unified CM Administration interface, select
. Under the Clusterwide Domain Configuration section, enter the organization top domain name. For example, cisco.com. This top domain name is used by Jabber as the DNS domain of the Cisco Unified Communications Manager servers for phone registration. For example, CUCMServer1@cisco.com.
What to Do Next
Add a Directory Number to the device.
Add a Directory Number to the Device
After you create and configure each device, you must add a directory number to the device. This topic provides instructions on adding directory numbers using the
menu option.Create a device.
Step 1 | Locate the Association Information section on the Phone Configuration window. |
Step 2 | Click Add a new DN. |
Step 3 | In the Directory Number field, specify a directory number. |
Step 4 | In the Users Associated with Line section, click Associate End Users. |
Step 5 | In the Find User where field, specify the appropriate filters and then click Find. |
Step 6 | From the list that appears, select the applicable users and click Add Selected. |
Step 7 | Specify all other required configuration settings as appropriate. |
Step 8 | Select Apply Config. |
Step 9 | Select Save. |
Add a Remote Destination
Remote destinations represent the CTI controllable devices that are available to users.
You should add a remote destination through the Cisco Unified CM Administration interface if you plan to provision users with dedicated CTI remote devices. This task ensures that users can automatically control their phones and place calls when they start the client.
If you plan to provision users with CTI remote devices along with software phone devices and desk phone devices, you should not add a remote destination through the Cisco Unified CM Administration interface. Users can enter remote destinations through the client interface.
Note |
|
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select . The Find and List Phones window opens. |
Step 3 | Specify the appropriate filters in the Find Phone where field to and then select Find to retrieve a list of phones. |
Step 4 | Select the CTI remote device from the list. The Phone Configuration window opens. |
Step 5 | Locate the Associated Remote Destinations section. |
Step 6 | Select Add a New Remote Destination. The Remote Destination Information window opens. |
Step 7 | Specify JabberRD in the Name field. You must specify JabberRD in the Name field. The client uses only the JabberRD remote destination. If you specify a name other than JabberRD, users cannot access that remote destination. |
Step 8 | Enter the destination number in the Destination Number field. |
Step 9 | Specify all other values as appropriate. |
Step 10 | Select Save. |
What to Do Next
The Device Information section on the Phone Configuration window contains a Active Remote Destination field. When users select a remote destination in the client, it displays as the value of Active Remote Destination.
Note
Configure User Associations
When you associate a user with a device, you provision that device to the user.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select
.
The Find and List Users window opens. |
Step 3 | Specify the appropriate filters in the Find User where field and then select Find to retrieve a list of users. |
Step 4 | Select the
appropriate user from the list.
The End User Configuration window opens. |
Step 5 | Locate the Service Settings section. |
Step 6 | Select Home Cluster. |
Step 7 | Select the appropriate service profile for the user from the UC Service Profile drop-down list. |
Step 8 | Locate the Device Information section. |
Step 9 | Select
Device
Association.
The User Device Association window opens. |
Step 10 | Select the devices to which you want to associate the user. Jabber only supports a single softphone association per device type. For example, only one TCT, BOT, CSF, and TAB device can be associated with a user. |
Step 11 | Select Save Selected/Changes. |
Step 12 | Select Find and List Users window. and return to the |
Step 13 | Find and select
the same user from the list.
The End User Configuration window opens. |
Step 14 | Locate the Permissions Information section. |
Step 15 | Select
Add to
Access Control Group.
The Find and List Access Control Groups dialog box opens. |
Step 16 | Select the
access control groups to which you want to assign the user.
If you are provisioning users with secure phone capabilities, do not assign the users to the Standard CTI Secure Connection group. |
Step 17 | Select
Add
Selected.
The Find and List Access Control Groups window closes. |
Step 18 | Select Save on the End User Configuration window. |
Create Mobile SIP Profiles
This procedure is required only when you use Cisco Unified Communication Manager release 9 and are configuring devices for mobile clients. Use the default SIP profile provided for desktop clients. Before you create and configure devices for mobile clients, you must create a SIP profile that allows Cisco Jabber to stay connected to Cisco Unified Communication Manager while Cisco Jabber runs in the background.
If you use Cisco Unified Communication Manager Release 10, choose the Standard SIP Profile for Mobile Device default profile when you create and configure devices for mobile clients.
Setting up System SIP Parameters
If you are connected to a low-bandwidth network and finding it difficult to take an incoming call on your mobile device, you can set the system SIP parameters to improve the condition. Increase the SIP Dual Mode Alert Timer value to ensure that calls to the Cisco Jabber extension are not prematurely routed to the mobile-network phone number.
This configuration is only for mobile clients.
Cisco Jabber must be running to receive work calls.
Step 1 | Open the Cisco Unified CM Administration interface. | ||
Step 2 | Select . | ||
Step 3 | Select the node. | ||
Step 4 | Select the Cisco CallManager (Active) service. | ||
Step 5 | Scroll to the Clusterwide Parameters (System - Mobility) section. | ||
Step 6 | Increase the SIP Dual Mode Alert Timer value to 10000 milliseconds. | ||
Step 7 | Select
Save.
|
Configure the Phone Security Profile
You can optionally set up secure phone capabilities for all devices. Secure phone capabilities provide secure SIP signaling, secure media streams, and encrypted device configuration files.
If you enable secure phone capabilities for users, device connections to Cisco Unified Communications Manager are secure. However, calls with other devices are secure only if both devices have a secure connection.
-
Configure the Cisco Unified Communications Manager security mode using the Cisco CTL Client. At minimum, select mixed mode security.
For instructions on how to configure mixed mode with the Cisco CTL Client, see the Cisco Unified Communications Manager Security Guide.
-
For conference calls, ensure that the conferencing bridge supports secure phone capabilities. If the conferencing bridge does not support secure phone capabilities, calls to that bridge are not secure. Likewise, all parties must support a common encryption algorithm for the client to encrypt media on conference calls.
Step 1 | In Cisco Unified Communications Manager, select . | ||
Step 2 | Select Add New. | ||
Step 3 | From the
Phone
Type drop-down list, select the option that is applicable to the
device type you are configuring and then select
Next.
| ||
Step 4 | In the Name field of the Phone Security Profile Configuration window, specify a name for the phone security profile. | ||
Step 5 | For Device Security Mode, select one of the following options: | ||
Step 6 | For Transport Type, leave the default value of TLS. | ||
Step 7 | Select the
TFTP
Encrypted Config check box to encrypt the device configuration file
that resides on the TFTP server.
| ||
Step 8 | For
Authentication Mode, select
By
Authentication String or
By
Null String.
| ||
Step 9 | For
Key
Size (Bits), select the appropriate key size for the certificate.
Key size refers to the bit length of the public and private keys that the
client generates during the CAPF enrollment process.
The Cisco Jabber clients were tested using authentication strings with 1024-bit length keys. The Cisco Jabber clients require more time to generate 2048-bit length keys than 1024-bit length keys. As a result, if you select 2048, expect it to take longer to complete the CAPF enrollment process. | ||
Step 10 | For
SIP
Phone Port, leave the default value.
The port that you specify in this field takes effect only if you select Non Secure as the value for Device Security Mode. | ||
Step 11 | Click Save. |
Provide Users with Authentication Strings
Users must specify the authentication string in the client interface to access their devices and securely register with Cisco Unified Communications Manager.
Note | The time it takes for the enrollment process to complete can vary depending on the user's computer or mobile device and the current load for Cisco Unified Communications Manager. It can take up to one minute for the client to complete the CAPF enrollment process. |
-
Users enter an incorrect authentication string.
Users can attempt to enter authentication strings again to complete the CAPF enrollment. However, if a user continually enters an incorrect authentication string, the client might reject any string the user enters, even if the string is correct. In this case, you must generate a new authentication string on the user's device and then provide it to the user.
-
Users do not enter the authentication string before the expiration time you set in the Operation Completes By field.
In this case, you must generate a new authentication string on the user's device. The user must then enter that authentication string before the expiration time.
Users must not belong to the Standard CTI Secure Connection user group.