The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Create software phone devices so that users can send and receive audio and video on their computers. Create desk phone devices that users can control with Cisco Jabber. Learn how to enable different audio and video features. Understand which server profiles you should create and which user associations you must assign.
On Cisco Unified Communications Manager version 9.x and higher you can also set up CTI remote devices to provision users with Extend and Connect capabilities.
Software phones let users send and receive audio and video through their computers.
Complete the steps in this task to create CSF devices.
Add a directory number to the device and apply the configuration.
Binary Floor Control Protocol (BFCP) provides video desktop sharing capabilities for software phone devices, also known as CSF devices. Cisco Unified Communications Manager handles the BFCP packets that users transmit when using video desktop sharing capabilities. On Cisco Unified Communications Manager version 9.0(1) and later, BFCP presentation sharing is automatically enabled. For this reason, you do not need to perform any steps to enable video desktop sharing on CSF devices.
Tip |
You can optionally set up secure phone capabilities for CSF devices. Secure phone capabilities provide secure SIP signaling, secure media streams, and encrypted device configuration files.
To use secure phone capabilities, you must configure the Cisco Unified Communications Manager security mode using the Cisco CTL Client. You cannot use secure phone capabilities with the nonsecure security mode. At a minimum, you must use mixed mode security.
See the Cisco Unified Communications Manager Security Guide for instructions on configuring mixed mode with the Cisco CTL Client.
The first step to setting up secure phone capabilities is to create a phone security profile that you can apply to the device.
Configure the Cisco Unified Communications Manager security to use mixed mode.
After you add a phone security profile, you must configure it to suit your requirements.
Add the phone security profile to the devices and complete other configuration tasks for secure phone capabilities.
Step 1 | Open the CSF
device configuration window.
|
Step 2 | Select Allow Control of Device from CTI in the Device Information section. |
Step 3 | Select Save. |
Step 4 | Locate the Protocol Specific Information section. |
Step 5 | Select the phone security profile from the Device Security Profile drop-down list. |
Step 6 | Select Save. |
At this point in the secure phone set up, existing users can no longer use their CSF devices. You must complete the secure phone set up for users to be able to access their CSF devices.
What to Do Next
Specify the certificate settings and generate the authentication string for users.
Specify certificate settings in the CSF device configuration and generate the authentication strings that you provide to users.
Provide users with the authentication string.
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.
SIP connections between CSF devices and Cisco Unified Communications Manager are over TLS.
If you select Authenticated as the value for the Device Security Mode field on the phone security profile, the SIP connection is over TLS using NULL-SHA encryption.
If you select Encrypted as the value for the Device Security Mode field on the phone security profile, the SIP connection is over TLS using AES 128/SHA encryption.
Mutual TLS ensures that only CSF devices with the correct certificates can register to Cisco Unified Communications Manager. Likewise, CSF devices can register only to Cisco Unified Communications Manager instances that provide the correct certificate.
If you enable secure phone capabilities for users, their CSF device connections to Cisco Unified Communications Manager are secure. If the other end point also has a secure connection to Cisco Unified Communications Manager, then the call can be secure. However, if the other end point does not have a secure connection to Cisco Unified Communications Manager, then the call is not secure.
Media Stream | Encryption |
---|---|
Main video stream |
Can be encrypted |
Main audio stream |
Can be encrypted |
Presentation video stream Refers to video desktop sharing using BFCP. |
Can be encrypted |
BFCP application stream
Refers to BFCP flow control. |
Not encrypted |
You enable media encryption for user A and user B. In other words, Device Security Mode is set to Encrypted on the phone security profile for the users' CSF devices.
You do not enable media encryption for user C. In other words, Device Security Mode is set to Authenticated on the phone security profile for the user's CSF device.
User A calls user B. The client encrypts the main video stream and audio stream.
User A calls user C. The client does not encrypt the main video stream and audio stream.
User A, user B, and user C start a conference call. The client does not encrypt the main video stream or audio stream for any user.
Note | However, not all versions of Cisco Unified Communications Manager provide the ability to display the lock icon. If the version of Cisco Unified Communications Manager you are using does not provide this ability, the client cannot display a lock icon even when it sends encrypted media. |
You configure a user's CSF device for secure phone capabilities.
That user connects to the internal corporate network through Expressway for Mobile and Remote Access.
The client notifies the user that it cannot use secure phone capabilities instead of prompting the user to enter an authentication string.
Media is encrypted on the call path between the Cisco Expressway-C and devices that are registered to the Cisco Unified Communications Manager using Expressway for Mobile and Remote Access.
Media is not encrypted on the call path between the Cisco Expressway-C and devices that are registered locally to Cisco Unified Communications Manager.
Note | If you change the phone security profile while the client is connected through Expressway for Mobile and Remote Access, you must restart the client for that change to take effect. |
The client downloads and stores certificate trust lists whenever you configure Cisco Unified Communications Manager security as mixed mode. Certificate trust lists enable the client to verify the identity of Cisco Unified Communications Manager nodes.
Note | The client encrypts the private key before saving it to the file system. |
The client stores these files in the following folder: %User_Profile%\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\Security
Because the client stores the files in the user's Roaming folder, users can sign in to any Microsoft Windows account on the Windows domain to register their CSF devices.
On conference, or multi-party, calls, the conferencing bridge must support 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.
CSF device security reverts to the lowest level available on multi-party calls. For example, user A, user B, and user C join a conference call. User A and user B have CSF devices with secure phone capabilities. User C has a CSF device without secure phone capabilities. In this case, the call is not secure for all users.
Clients that do not support secure phone capabilities cannot register to secure CSF devices.
For example, you set up secure phone capabilities on a CSF device to which both Cisco Jabber for Windows version 9.2 and Cisco Jabber for Windows version 9.1 register. However, Cisco Jabber for Windows version 9.1 does not support secure phone capabilities. In this scenario, you must create two different CSF devices, one secure CSF device for Cisco Jabber for Windows version 9.2 and another CSF device that is not secure for Cisco Jabber for Windows version 9.1.
Multiple users can have unique credentials for the client and share the same Windows account. However, the secure CSF devices are restricted to the Windows account that the users share. Users who share the same Windows account cannot make calls with their secure CSF devices from different Windows accounts.
You should ensure that multiple users who share the same Windows account have CSF devices with unique names. Users cannot register their CSF devices if they share the same Windows account and have CSF devices with identical names, but connect to different Cisco Unified Communications Manager clusters.
For example, user A has a CSF device named CSFcompanyname and connects to cluster 1. User B has a CSF device named CSFcompanyname and connects to cluster 2. In this case, a conflict occurs for both CSF devices. Neither user A or user B can register their CSF devices after both users sign in to the same Windows account.
The client caches the certificates for each user's secure CSF device in a location that is unique to each Windows user. When a user logs in to their Windows account on the shared computer, that user can access only the secure CSF device that you provision to them. That user cannot access the cached certificates for other Windows users.
You must add directory numbers to devices in Cisco Unified Communications Manager. This topic provides instructions on adding directory numbers using the 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 documentation for more information about different options to configure directory numbers.
Step 1 | Locate the Association Information section on the Phone Configuration window. |
Step 2 | Select
Add a
new DN.
The Directory Number Configuration window opens. |
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:
|
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. |
Users can control desk phones on their computers to place audio calls.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select . The Find and List Phones window opens. |
Step 3 | Select Add New. |
Step 4 | Select the appropriate device from the Phone Type drop-down list and then select Next. The Phone Configuration window opens. |
Step 5 | Complete the following steps in the Device Information section: |
Step 6 | Set the Owner User ID field to the appropriate user. On Cisco Unified Communications Manager version 9.x, the client uses the Owner User ID field to get service profiles for users. For this reason, each user must have a device and the User Owner ID field must be associated with the user. If you do not associate users with devices and set the Owner User ID field to the appropriate user, the client cannot retrieve the service profile that you apply to the user. |
Step 7 | Complete the following steps to enable desk phone video capabilities: See Desk Phone Video Configuration for more information about desk phone video. |
Step 8 | Specify all other configuration settings on the Phone Configuration window as appropriate. See the Cisco Unified Communications Manager documentation for more information about the configuration settings on the Phone Configuration window. |
Step 9 | Select Save. An message displays to inform you if the device is added successfully. The Association Information section becomes available on the Phone Configuration window. |
Add a directory number to the device and apply the configuration.
Desk phone video capabilities let users receive video transmitted to their desk phone devices on their computers through the client.
Physically connect the computer to the computer port on the desk phone device.
You must physically connect the computer to the desk phone device through the computer port so that the client can establish a connection to the device. You cannot use desk phone video capabilities with wireless connections to desk phone devices.
Tip | If users have both wireless and wired connections available, they should configure Microsoft Windows so that wireless connections do not take priority over wired connections. See the following Microsoft documentation for more information: An explanation of the Automatic Metric feature for Internet Protocol routes. |
Enable the desk phone device for video in Cisco Unified Communications Manager.
Install Cisco Media Services Interface on the computer.
Note | Download the Cisco Media Services Interface installation program from the download site on Cisco.com. |
You cannot use desk phone video capabilities on devices if video cameras are attached to the devices, such as a Cisco Unified IP Phone 9971. You can use desk phone video capabilities if you remove video cameras from the devices.
You cannot use desk phone video capabilities with devices that do not support CTI.
Video desktop sharing, using the BFCP protocol, is not supported with desk phone video.
It is not possible for endpoints that use SCCP to receive video only. SCCP endpoints must send and receive video. Instances where SCCP endpoints do not send video result in audio only calls.
7900 series phones must use SCCP for desk phone video capabilities. 7900 series phones cannot use SIP for desk phone video capabilities.
If a user initiates a call from the keypad on a desk phone device, the call starts as an audio call on the desk phone device. The client then escalates the call to video. For this reason, you cannot make video calls to devices that do not support escalation, such as H.323 endpoints. To use desk phone video capabilities with devices that do not support escalation, users should initiate calls from the client.
A compatibility issue exists with Cisco Unified IP Phones that use firmware version SCCP45.9-2-1S. You must upgrade your firmware to version SCCP45.9-3-1 to use desk phone video capabilities.
Some antivirus or firewall applications, such as Symantec EndPoint Protection, block inbound CDP packets, which disables desk phone video capabilities. You should configure your antivirus or firewall application to allow inbound CDP packets.
See the following Symantec technical document for additional details about this issue: Cisco IP Phone version 7970 and Cisco Unified Video Advantage is Blocked by Network Threat Protection.
You must not select the Media Termination Point Required checkbox on the SIP trunk configuration for Cisco Unified Communications Manager. Desk phone video capabilities are not available if you select this checkbox.
You must add directory numbers to devices in Cisco Unified Communications Manager. This topic provides instructions on adding directory numbers using the 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 documentation for more information about different options to configure directory numbers.
Step 1 | Locate the Association Information section on the Phone Configuration window. |
Step 2 | Select
Add a
new DN.
The Directory Number Configuration window opens. |
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:
|
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. |
The client uses video rate adaptation to negotiate optimum video quality. Video rate adaptation dynamically increases or decreases video quality based on network conditions.
Note | RTCP is enabled on software phone devices by default. However, you must enable RTCP on desk phone devices. |
You can enable RTCP on a common phone profile to enable video rate adaptation on all devices that use the profile.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select . The Find and List Common Phone Profiles window opens. |
Step 3 | Specify the appropriate filters in the Find Common Phone Profile where field and then select Find to retrieve a list of profiles. |
Step 4 | Select the appropriate profile from the list. The Common Phone Profile Configuration window opens. |
Step 5 | Locate the Product Specific Configuration Layout section. |
Step 6 | Select Enabled from the RTCP drop-down list. |
Step 7 | Select Save. |
You can enable RTCP on specific device configurations instead of a common phone profile. The specific device configuration overrides any settings you specify on the common phone profile.
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 and then select Find to retrieve a list of phones. |
Step 4 | Select the appropriate phone from the list. The Phone Configuration window opens. |
Step 5 | Locate the Product Specific Configuration Layout section. |
Step 6 | Select Enabled from the RTCP drop-down list. |
Step 7 | Select Save. |
The CTI service lets users control devices.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select . The Find and List UC Services window opens. |
Step 3 | Select Add New. The UC Service Configuration window opens. |
Step 4 | In the Add a UC Service section, select CTI from the UC Service Type drop-down list. |
Step 5 | Select Next. |
Step 6 | Provide details for the instant messaging and presence service as follows: |
Step 7 | Select Save. |
Add the CTI service to your service profile.
After you add a CTI service on Cisco Unified Communications Manager, you must apply it to a service profile so that the client can retrieve the settings.
Create a service profile if none already exist or you require a separate service profile for CTI.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select . The Find and List Service Profiles window opens. |
Step 3 | Find and select your service profile. The Service Profile Configuration window opens. |
Step 4 | In the CTI Profile section, select up to three services from the following drop-down lists: |
Step 5 | Select Save. |
CTI remote devices let users control calls on devices other than software phone devices or desk phone devices such as Cisco IP phones.
Cisco Unified Communications Manager Extend and Connect capabilities let users control calls on devices such as public switched telephone network (PSTN) phones and private branch exchange (PBX) devices.
Note | Cisco recommends that you use extend and connect capabilities with Cisco Unified Communications Manager 9.1(1) and later only. |
You can provision users with dedicated CTI remote devices. For example, each user has a PSTN phone at their workstation. You want to allow the users to make calls with their PSTN phones using the client. You do not plan to provision users with software phone devices or desk phone devices.
To provision CTI remote devices as dedicated devices, you should add remote destinations through the Cisco Unified CM Administration interface. This ensures that users can automatically control their phones and place calls when they start the client.
You can provision CTI remote devices so that users can specify an alternative phone number to their software phone device or desk phone device. For example, each user can work remotely from home. In this case, users can specify their home phone numbers as remote destinations. This allows the users to control home phones with the client.
If you plan to provision CTI remote devices as an alternative device, you should not add remote destinations. Users can add, edit, and delete remote destinations through the client interface.
When a user logs in, the client retrieves the user's device list from Cisco Unified Communications Manager.
If that device list contains a software phone device or desk phone device, the client automatically lets users add, edit, and delete remote destinations through the client interface.
If that device list contains only a CTI remote device, the client does not let users add, edit, and delete remote destinations. You must enable users to add, edit, and delete remote destinations in the client configuration.
If a user is signed in to the client and sets a remote device as active, that device rings when the user receives incoming calls. Additionally, the client routes outgoing calls to the active device when the user is signed in.
If a user is not signed in to the client, and that user receives an incoming call to the directory number, all devices set as remote destinations ring.
This section describes limitations and known issues that currently exist for Cisco Unified Communications Manager extend and connect capabilities.
You can create only one remote destination per user. Do not add two or more remote destinations for a user.
Users cannot use the same remote destination for multiple devices.
You cannot provision extend and connect capabilities for devices that you configure as endpoints on the Cisco Unified Communications Manager cluster.
A user adds a number for a remote destination.
Cisco Unified Communications Manager routes incoming calls to that remote destination. The user can control the call session with the client.
The user changes their phone. For example, the user selects their software phone.
Cisco Unified Communications Manager routes incoming calls to the user's software phone. However, if the user does not answer incoming calls on the software phone within 4 or 5 seconds, the user's remote destination also rings.
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.
Step 1 | Select . The Find and List Users window opens. |
Step 2 | Specify the appropriate filters in the Find User where field to and then select Find to retrieve a list of users. |
Step 3 | Select the user from the list. The End User Configuration window opens. |
Step 4 | Locate the Mobility Information section. |
Step 5 | Select Enable Mobility. |
Step 6 | Select Save. |
CTI remote devices are virtual devices that monitor and have call control over a user's remote destination.
Step 1 | Open the Cisco Unified CM Administration interface. | ||
Step 2 | Select . The Find and List Phones window opens. | ||
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 opens. | ||
Step 5 | Select the appropriate user ID from the Owner User ID drop-down list.
Cisco Unified Communications Manager populates the Device Name field with the user ID and a CTIRD prefix; for example, CTIRDusername | ||
Step 6 | Edit the default value in the Device Name field, if appropriate. | ||
Step 7 | 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 re-routing and ensures that users can send and receive calls from the CTI remote device. | ||
Step 8 | Specify all other configuration settings on the Phone Configuration window as appropriate. See the CTI remote device setup topic in the Cisco Unified Communications Manager documentation for more information. | ||
Step 9 | Select Save. The fields to associate directory numbers and add remote destinations become available on the Phone Configuration window. |
You must add directory numbers to devices in Cisco Unified Communications Manager. This topic provides instructions on adding directory numbers using the 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 documentation for more information about different options to configure directory numbers.
Step 1 | Locate the Association Information section on the Phone Configuration window. |
Step 2 | Select
Add a
new DN.
The Directory Number Configuration window opens. |
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:
|
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. |
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. |
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
The CTI service lets users control devices.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select . The Find and List UC Services window opens. |
Step 3 | Select Add New. The UC Service Configuration window opens. |
Step 4 | In the Add a UC Service section, select CTI from the UC Service Type drop-down list. |
Step 5 | Select Next. |
Step 6 | Provide details for the instant messaging and presence service as follows: |
Step 7 | Select Save. |
Add the CTI service to your service profile.
After you add a CTI service on Cisco Unified Communications Manager, you must apply it to a service profile so that the client can retrieve the settings.
Create a service profile if none already exist or you require a separate service profile for CTI.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select . The Find and List Service Profiles window opens. |
Step 3 | Find and select your service profile. The Service Profile Configuration window opens. |
Step 4 | In the CTI Profile section, select up to three services from the following drop-down lists: |
Step 5 | Select Save. |
You can set up additional audio path functions for devices such as silent monitoring and call recording.
Note | This feature is currently supported on Cisco Jabber for Windows only. |
To enable silent monitoring and call recording, you configure Cisco Unified Communications Manager. See the Monitoring and Recording section of the Cisco Unified Communications Manager Features and Services Guide for step-by-step instructions.
Cisco Jabber does not provide any interface to initiate silent monitoring or call recording. You must use the appropriate software to silently monitor or record calls.
Cisco Jabber does not currently support monitoring notification tone or recording notification tone.
You can use silent monitoring and call recording functionality only. Cisco Jabber does not support other functionality such as barging or whisper coaching.
You can enable URI dialing on Cisco Unified Communications Manager version 9.1(2) and later.
URI dialing allows users to make calls and resolve contacts with Uniform Resource Identifiers (URI). For example, a user named Adam McKenzie has the following SIP URI associated with his directory number: amckenzi@example.com. URI dialing enables users to call Adam with his SIP URI rather than his directory number.
For detailed information on URI dialing requirements, such as valid URI formats, as well as advanced configuration including ILS setup, see the URI Dialing section of the Cisco Unified Communications Manager System Guide.
When users make URI calls, Cisco Unified Communications Manager routes the inbound calls to the directory numbers associated to the URIs. For this reason, you must associate URIs with directory numbers. You can either automatically populate directory numbers with URIs or configure directory numbers with URIs.
When you add users to Cisco Unified Communications Manager, you populate the Directory URI field with a valid SIP URI. Cisco Unified Communications Manager saves that SIP URI in the end user configuration.
When you specify primary extensions for users, Cisco Unified Communications Manager populates the directory URI from the end user configuration to the directory number configuration. In this way, automatically populates the directory URI for the user's directory number. Cisco Unified Communications Manager also places the URI in the default partition, which is Directory URI.
The following task outlines, at a high level, the steps to configure Cisco Unified Communications Manager so that directory numbers inherit URIs:
Verify that the directory URIs are associated with the directory numbers.
After you specify primary extensions for users, you should complete the following steps to verify that the directory URIs are associated with the directory numbers.
The primary directory URI for the directory number should correspond to the end user with whom you associated the device.
The partition should be Directory URI. This partition is the default into which Cisco Unified Communications Manager places URIs.
You can specify URIs for directory numbers that are not associated with users. You should configure directory numbers with URIs for testing and evaluation purposes only.
To configure directory numbers with URIs, do the following:
Step 1 | Open the Cisco Unified CM Administration interface. | ||
Step 2 | Select
.
The Find and List Directory Numbers window opens. | ||
Step 3 | Find and
select the appropriate directory number.
The Directory Number Configuration window opens. | ||
Step 4 | Locate the Directory URIs section. | ||
Step 5 | Specify a valid SIP URI in the URI column. | ||
Step 6 | Select the
appropriate partition from the
Partition column.
| ||
Step 7 | Add the partition to the appropriate calling search space so that users can place calls to the directory numbers. | ||
Step 8 | Select Save. |
You must associate the default partition into which Cisco Unified Communications Manager places URIs with a partition that contains directory numbers.
To enable URI dialing, you must associate the default directory URI partition with a partition that contains directory numbers.
If you do not already have a partition for directory numbers within a calling search space, you should create a partition and configure it as appropriate.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select . The Enterprise Parameters Configuration window opens. |
Step 3 | Locate the End User Parameters section. |
Step 4 | In the Directory URI Alias Partition row, select the appropriate partition from the drop-down list. |
Step 5 | Select Save. |
The default directory URI partition is associated with the partition that contains directory numbers. As a result, Cisco Unified Communications Manager can route incoming URI calls to the correct directory numbers.
You should ensure the partition is in the appropriate calling search space so that users can place calls to the directory numbers.
To enable contact resolution with URIs, you must ensure that Cisco Unified Communications Manager uses the fully qualified domain name (FQDN) in SIP requests.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select
.
The Find and List SIP Profiles window opens. |
Step 3 | Find and
select the appropriate SIP profile.
You cannot edit the default SIP profile. If required, you should create a copy of the default SIP profile that you can modify. |
Step 4 | Select Use Fully Qualified Domain Name in SIP Requests and then select Save. |
Associate the SIP profile with all devices that have primary extensions to which you associate URIs.
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 the appropriate service profile for the user from the UC Service Profile drop-down list. |
Step 7 | Locate the Device Information section. |
Step 8 | Select Device Association. The User Device Association window opens. |
Step 9 | Select the devices to which you want to associate the user. |
Step 10 | Select Save Selected/Changes. |
Step 11 | Select Find and List Users window. and return to the |
Step 12 | Find and select the same user from the list. The End User Configuration window opens. |
Step 13 | Locate the Permissions Information section. |
Step 14 | Select Add to Access Control Group. The Find and List Access Control Groups dialog box opens. |
Step 15 | 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 16 | Select Add Selected. The Find and List Access Control Groups window closes. |
Step 17 | Select Save on the End User Configuration window. |
The client gets device configuration from the TFTP server. For this reason, you must specify your TFTP server address when you provision users with devices.
If the client gets the _cisco-uds SRV record from a DNS query, it can automatically locate the user's home cluster. As a result, the client can also locate the Cisco Unified Communications Manager TFTP service.
You do not need to specify your TFTP server address if you deploy the _cisco-uds SRV record.
If you are using Cisco Unified Communications Manager Version 8.x, complete the steps to specify the address of your TFTP server on Cisco Unified Communications Manager. If you are using Cisco Unified Communications Manager Version 9.x, then you do not need to follow the steps below.
Step 1 | Open the Cisco Unified CM IM and Presence Administration interface. |
Step 2 | Select . The Legacy Client Settings window opens. |
Step 3 | Locate the Legacy Client Security Settings section. |
Step 4 | Specify the IP address of your primary and backup TFTP servers in the following fields: |
Step 5 | Select Save. |
If the client connects to the Cisco WebEx Messenger service, you specify your TFTP server address with the Cisco WebEx Administration Tool.
Step 1 | Open the Cisco WebEx Administration Tool. |
Step 2 | Select the Configuration tab. |
Step 3 | Select Unified Communications in the Additional Services section. The Unified Communications window opens. |
Step 4 | Select the Clusters tab. |
Step 5 | Select the appropriate cluster from the list. The Edit Cluster window opens. |
Step 6 | Select Advanced Server Settings in the Cisco Unified Communications Manager Server Settings section. |
Step 7 | Specify the IP address of your primary TFTP server in the TFTP Server field. |
Step 8 | Specify the IP address of your backup TFTP servers in the Backup Server #1 and Backup Server #2 fields. |
Step 9 | Select Save. The Edit Cluster window closes. |
Step 10 | Select Save in the Unified Communications window. |
After you create and associate users with devices, you should reset those devices.
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 and then select Find to retrieve a list of devices. |
Step 4 | Select the appropriate device from the list. The Phone Configuration window opens. |
Step 5 | Locate the Association Information section. |
Step 6 | Select the appropriate directory number configuration. The Directory Number Configuration window opens. |
Step 7 | Select Reset. The Device Reset dialog box opens. |
Step 8 | Select Reset. |
Step 9 | Select Close to close the Device Reset dialog box. |
The client gets device lists for users from the CCMCIP server.
If the client gets the _cisco-uds SRV record from a DNS query, it can automatically locate the user's home cluster and discover services. One of the services the client discovers is UDS, which replaces CCMCIP.
Step 1 | Open the Cisco Unified CM IM and Presence Administration interface. |
Step 2 | Select
.
The Find and List CCMCIP Profiles window opens. |
Step 3 | Select
Add
New.
The CCMCIP Profile Configuration window opens. |
Step 4 | Specify
service details in the CCMCIP profile as follows:
|
Step 5 | Add users to
the CCMCIP profile as follows:
|
Step 6 | Select Save. |
You configure dial plan mapping to ensure that dialing rules on Cisco Unified Communications Manager match dialing rules on your directory.
Application dial rules automatically add or remove digits in phone numbers that users dial. Application dialing rules manipulate numbers that users dial from the client.
For example, you can configure a dial rule that automatically adds the digit 9 to the start of a 7 digit phone number to provide access to outside lines.
Directory lookup dial rules transform caller ID numbers into numbers that the client can lookup in the directory. Each directory lookup rule you define specifies which numbers to transform based on the initial digits and the length of the number.
For example, you can create a directory lookup rule that automatically removes the area code and two-digit prefix digits from 10-digit phone numbers. An example of this type of rule is to transform 4089023139 into 23139.
Cisco Unified Communications Manager version 8.6.1 or earlier does not automatically publish dial rules to the client. For this reason, you must deploy a COP file to publish your dial rules. This COP file copies your dial rules from the Cisco Unified Communications Manager database to an XML file on your TFTP server. The client can then download that XML file and access your dial rules.
You must deploy the COP file every time you update or modify dial rules on Cisco Unified Communications Manager version 8.6.1 or earlier.
Step 1 | Open the Cisco Unified OS Administration interface. |
Step 2 | Select . |
Step 3 | Specify the location of cmterm-cupc-dialrule-wizard-0.1.cop.sgn in the Software Installation/Upgrade window. |
Step 4 | Select Next. |
Step 5 | Select cmterm-cupc-dialrule-wizard-0.1.cop.sgn from the Available Software list. |
Step 6 | Select Next and then select Install. |
Step 7 | Restart the TFTP service. |
Step 8 | Open the dial
rules XML files in a browser to verify that they are available on your TFTP
server.
If you can access AppDialRules.xml and DirLookupDialRules.xml with your browser, the client can download your dial rules. |
Step 9 | Repeat the preceding steps for each Cisco Unified Communications Manager instance that runs a TFTP service. |
After you repeat the preceding steps on each Cisco Unified Communications Manager instance, restart the client.