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 over their mobile devices. Learn how to enable various features to enhance the audio and video experience for users.
Software phones let users send and receive audio and video through their mobile devices.
TCT devices provide capabilities for Cisco Jabber for iPhone to send and receive audio and video through an iOS device.
To make Cisco Jabber available as a device in Cisco Unified Communications Manager, you must install a device-specific Cisco Options Package (COP) file on all your Cisco Unified Communications Manager servers.
Perform this procedure at a time of low usage; it can interrupt service.
General information about installing COP files is available in the “Software Upgrades” chapter in the Cisco Unified Communications Operating System Administration Guide for your release.
This procedure is required only when you use Cisco Unified Communications Manager Version 9 or lower.
If you use Cisco Unified Communications Manager Version 9 or lower, the first step in creating a software phone device is to create a SIP profile that allows Cisco Jabber to stay connected to Cisco Unified Communications Manager while Cisco Jabber runs in the background.
If you use Cisco Unified Communications Manager Version 10, you can use the following default profile for mobile devices instead: Standard SIP Profile for Mobile Device. You select this default profile when you configure the device. For more information, see the TCT Device Configuration Settings topic.
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.
Cisco Jabber must be running to receive work calls.
Complete the steps in this task to create TCT devices for Cisco Jabber for iPhone 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.
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 Cisco Dual Mode for iPhone from the Phone Type drop-down list and then select Next. |
Step 5 |
Specify configuration settings on the Phone Configuration window as appropriate. See the TCT Device Configuration Settings topic below for information about the specific settings that are required for TCT devices.
Multiple lines are not supported on TCT devices. |
Step 6 |
Select Save. A message displays to inform you if the device is added successfully. The Association Information section becomes available on the Phone Configuration window. |
Step 7 | Select Apply Config. |
Use the following tables to set up TCT devices on the Phone Configuration window.
Restrictions and requirements that are not specific to Cisco Jabber may apply to these values. If you require additional information about any option on the Phone Configuration window, see the online help in the Cisco Unified CM Administration interface.
Setting | Description | ||
---|---|---|---|
Device Name | The Device Name:
Cisco recommends that the device name include the username of the user so it is easy to remember (for example, the recommended device name of user jsmith is TCTJSMITH). |
||
Phone Button Template | Select Standard Dual Mode for iPhone. | ||
Media Resource Group List | Set up the on-hold music to ensure that if a user puts a call on hold, the other party hears on-hold music. This step prevents confusion for the other party.
These settings are not specific to this device. For more information about these settings, see the Cisco Unified Communications Manager documentation. |
||
User Hold MOH Audio Source | |||
Network Hold MOH Audio Source | |||
Primary Phone | If this user has a desk phone, select the desk phone. Selecting the primary phone sets the device as an adjunct in the Cisco Unified Communications Manager for licensing purposes. |
Setting | Description |
---|---|
Device Security Profile | Select Cisco Dual Mode for iPhone - Standard SIP Non-Secure Profile. |
SIP Profile |
|
Other settings in the preceding sections | As appropriate to your deployment. Values that are not described in this document are not specific to Cisco Jabber but you may need to enter them for the device to work properly. |
Setting | Description |
---|---|
Emergency Numbers | Numbers that, when dialed on an iPhone, connect using the native phone application and the mobile network of the device. If dialed on an iPod, these numbers connect using VoIP calling. For example, 911, 999, 112. These numbers are prepopulated. Update if necessary. |
Preset Wi-Fi Networks | The SSIDs for Wi-Fi networks. Cisco Jabber triggers Connect on Demand to Cisco AnyConnect Secure Mobility Client if users are not on a Wi-Fi network listed in this field, or if they are on a mobile data network. Separate multiple SSIDs with forward slash (/). Example: SalesOffice1/CorporateWiFi |
On-Demand VPN URL | Enter the URL that you want to use to initiate on-demand VPN. |
Default Ringtone | Select Loud or Normal. |
Video Capabilities | Default is set to Enabled, which allows users to make and receive video calls. |
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. This can be a new DN. A desk phone with the same DN is not required. |
||
Step 4 |
Set the No Answer Ring Duration (seconds) to 24 seconds to allow time for Cisco Jabber to ring before calls go to voicemail.
If you increase the No Answer Ring Duration (seconds) setting, see related cautions for this setting in the online help in Cisco Unified Communications Manager. |
||
Step 5 | In the Multiple Call/Call Waiting Settings on Device section, in the Busy Trigger field, ensure that the value is set to 3. | ||
Step 6 | Specify all other required configuration settings as appropriate. | ||
Step 7 | Select Save. |
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 Device Information section. |
Step 6 |
Select Device Association. The User Device Association window opens. |
Step 7 | Select the devices to which you want to associate the user. |
Step 8 | Select Save Selected/Changes. |
Step 9 | Select Find and List Users window. and return to the |
Step 10 |
Find and select the same user from the list. The End User Configuration window opens. |
Step 11 | Locate the Permissions Information section. |
Step 12 |
Select Add to Access Control Group. The Find and List Access Control Groups dialog box opens. |
Step 13 |
Select the access control groups to which you want to assign the user.
|
Step 14 |
Select Add Selected. The Find and List Access Control Groups window closes. |
Step 15 | 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.
Complete the steps to specify the address of your TFTP server on Cisco Unified Communications Manager IM and Presence.
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.
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. |
To set up Mobile Connect, perform the following procedures:
Use the following procedure to enable Mobile Connect for an end user.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Search for and delete any existing Remote Destination or Mobility Identity that is already set up with the mobile phone number as follows: |
Step 3 | Configure the end user for Mobile Connect as follows: |
Step 4 |
Configure the device settings for Mobile Connect as follows:
|
Use this procedure to add a Mobility Identity to specify the mobile phone number of the mobile device as the destination number. This destination number is used by features such as Dial via Office or Mobile Connect.
You can specify only one number when you add a mobility identity. If you want to specify an alternate number such as a second mobile phone number for a mobile device, you can set up a remote destination. The Mobility Identity configuration characteristics are identical to those of the Remote Destination configuration.
Step 1 | Open the Cisco Unified CM Administration interface. | ||||||||||
Step 2 | Navigate to the device that you want to configure as follows: | ||||||||||
Step 3 | In the Associated Mobility Identity section, select Add a New Mobility Identity. | ||||||||||
Step 4 |
Enter the mobile phone number as the Destination Number. This number must be routable to an outbound gateway. Generally, the number is the full E.164 number.
|
||||||||||
Step 5 |
Enter the initial values for call timers. These values ensure that calls are not routed to the mobile service provider voicemail before they ring in the client on the mobile device. You can adjust these values to work with the end user's mobile network. For more information, see the online help in Cisco Unified Communications Manager. Example:
|
||||||||||
Step 6 | Do one of the following: | ||||||||||
Step 7 |
If you are setting up the Dial via Office feature, in the Mobility Profile drop-down list, select one of the following options.
|
||||||||||
Step 8 | Set up the schedule for routing calls to the mobile number. | ||||||||||
Step 9 | Select Save. |
Use this procedure to add a Remote Destination to specify any alternate number as the destination number. The Mobility Identity configuration characteristics are identical to those of the Remote Destination configuration.
Alternate numbers can be any type of phone number, such as home phone numbers, conference room numbers, desk phone numbers, or multiple mobile phone numbers for additional mobile devices. You can add more than one remote destination.
Step 1 | Open the Cisco Unified CM Administration interface. | ||||||||||
Step 2 | Navigate to the device that you want to configure as follows: | ||||||||||
Step 3 | In the Associated Remote Destinations section, select Add a New Remote Destination. | ||||||||||
Step 4 |
Enter the desired phone number as the Destination Number. This number must be routable to an outbound gateway. Generally, the number is the full E.164 number. |
||||||||||
Step 5 |
Enter the initial values for call timers. These values ensure that calls are not routed to the mobile service provider voicemail before they ring in the client on the mobile device. For more information, see the online help in Cisco Unified Communications Manager. Example:
|
||||||||||
Step 6 | Do one of the following: | ||||||||||
Step 7 | Set up the schedule for routing calls to the mobile number. | ||||||||||
Step 8 | Select Save. |
Users can transfer an active VoIP call from Cisco Jabber to their mobile phone number on the mobile network. This feature is useful when a user on a call leaves the Wi-Fi network (for example, leaving the building to walk out to the car), or if there are voice quality issues over the Wi-Fi network. This Cisco Jabber feature is called Move to Mobile.
Implementation Method | Description | Instructions |
---|---|---|
Handoff DN | The mobile device calls Cisco Unified Communications Manager using the mobile network. This method requires a Direct Inward Dial (DID) number. The service provider must deliver the DID digits exactly as configured. Alternately, for Cisco IOS gateways with H.323 or SIP communication to Cisco Unified Communications Manager, you can use Cisco IOS to manipulate the inbound called-party number at the gateway, presenting the digits to Cisco Unified Communications Manager exactly as configured on the handoff DN. This method does not work for iPod Touch devices. |
See the Enable Handoff from VoIP to Mobile Network topic. |
Mobility Softkey | Cisco Unified Communications Manager calls the phone number of the PSTN mobile service provider for the mobile device. |
See the Enable Transfer from VoIP to Mobile Network topic. |
None of the above | Disable this feature if you do not want to make it available to users. | Select Disabled for the Transfer to Mobile Network option in the Product Specific Configuration Layout section of the TCT device page. |
Set up a directory number that Cisco Unified Communications Manager can use to hand off active calls from VoIP to the mobile network. Match the user's caller ID with the Mobility Identity to ensure that Cisco Unified Communications Manager can recognize the user. Set up the TCT device and mobile device to support handoff from VoIP to the mobile network.
Determine the required values. The values that you choose depend on the phone number that the gateway passes (for example, seven digits or ten digits).
Step 1 | Open the Cisco Unified CM Administration interface. | ||
Step 2 | Select . | ||
Step 3 |
Enter the Handoff Number for the Direct Inward Dial (DID) number that the device uses to hand off a VoIP call to the mobile network. The service provider must deliver the DID digits exactly as configured. Alternately, for Cisco IOS gateways with H.323 or SIP communication to Cisco Unified Communications Manager, you can use Cisco IOS to manipulate the inbound called-party number at the gateway, presenting the digits to Cisco Unified Communications Manager exactly as configured on the handoff number.
|
||
Step 4 |
Select the Route Partition for the handoff DID. This partition should be present in the Remote Destination inbound Calling Search Space (CSS), which points to either the Inbound CSS of the Gateway or Trunk, or the Remote Destination CSS. This feature does not use the remaining options on this page. |
||
Step 5 | Select Save. |
To ensure that only authorized phones can initiate outbound calls, calls must originate from a phone that is set up in the system. To do this, the system attempts to match the caller ID of the requesting phone number with an existing Mobility Identity. By default, when a device initiates the Handoff feature, the caller ID that is passed from the gateway to Cisco Unified Communications Manager must exactly match the Mobility Identity number that you entered for that device.
However, your system may be set up such that these numbers do not match exactly. For example, Mobility Identity numbers may include a country code while caller ID does not. If so, you must set up the system to recognize a partial match.
Be sure to account for situations in which the same phone number may exist in different area codes or in different countries. Also, be aware that service providers can identify calls with a variable number of digits, which may affect partial matching. For example, local calls may be identified using seven digits (such as 555 0123) while out-of-area calls may be identified using ten digits (such as 408 555 0199).
Set up the Mobility Identity. See the Add Mobility Identity topic.
To determine whether you need to complete this procedure, perform the following steps. Dial in to the system from the mobile device and compare the caller ID value with the Destination Number in the Mobility Identity. If the numbers do not match, you must perform this procedure. Repeat this procedure for devices that are issued in all expected locales and area codes.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select . |
Step 3 | Select the active server. |
Step 4 | Select the Cisco CallManager (Active) service. |
Step 5 | Scroll down to the Clusterwide Parameters (System - Mobility) section. |
Step 6 | Select Matching Caller ID with Remote Destination and read essential information about this value. |
Step 7 | Select Partial Match for Matching Caller ID with Remote Destination. |
Step 8 | Select Number of Digits for Caller ID Partial Match and read the essential requirements for this value. |
Step 9 | Enter the required number of digits to ensure partial matches. |
Step 10 | Select Save. |
Step 1 |
In the Cisco Unified CM Administration interface, go to the TCT Device page, and select Use Handoff DN Feature for the Transfer to Mobile Network option. Do not assign this method for iPod Touch devices. Use the Mobility Softkey method instead. |
Step 2 | On the iOS device, tap to verify that Caller ID is on. |
Step 3 | Test this feature. |
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 |
For system-level settings, check that the Mobility softkey appears when the phone is in the connected and on-hook call states.
|
Step 3 | Navigate to the device that you want to configure as follows: |
Step 4 |
For the per-user and per-device settings in Cisco Unified Communications Manager, set the specific device to use the Mobility softkey when the device transfers calls to the mobile voice network. Ensure that you have set up both Mobility Identity and Mobile Connect for the mobile device. After the transfer feature is working, users can enable and disable Mobile Connect at their convenience without affecting the feature. If the device is an iPod Touch, you can configure a Mobility Identity using an alternate phone number such as the mobile phone of the user. |
Step 5 | In the User Locale field, choose English, United States. |
Step 6 | Select Save. |
Step 7 | Select Apply Config. |
Step 8 | Instruct the user to sign out of the client and then to sign back in again to access the feature. |
Test your settings by transferring an active call from VoIP to the mobile network.
User-controlled voicemail avoidance, which can be used in conjunction with the Dial via Office feature, is available only on Cisco Unified Communications Manager Release 9.0 and later. Timer-controlled voicemail avoidance is available on Cisco Unified Communications Manager Release 6.0 and later.
The Dial via Office feature is not supported with the Extension Mobility feature.
The Dial via Office (DVO) feature allows users to initiate Cisco Jabber outgoing calls with their work number using the voice plan for the device.
Cisco Jabber supports Dial via Office-Reverse (DVO-R) calls. DVO-R works as follows:
Incoming calls use either Mobile Connect or the Voice over IP, depending on which Calling Options the user sets on the client. Dial via Office does not require Mobile Connect to work. However, we recommend that you enable Mobile Connect to allow the native mobile number to ring when someone calls the work number. From the Cisco Unified Communications Manager user pages, users can enable and disable Mobile Connect, and adjust Mobile Connect behavior using settings (for example, the time of day routing and Delay Before Ringing Timer settings). For information about setting up Mobile Connect, see the Set Up Mobile Connect topic.
Connection | Calling Options | |||||
---|---|---|---|---|---|---|
Voice over IP | Mobile Voice Network | Autoselect | ||||
Corporate Wi-Fi |
Outgoing: VoIP | Incoming: VoIP | Outgoing: DVO-R | Incoming: Mobile Connect | Outgoing: VoIP | Incoming: VoIP |
Noncorporate Wi-Fi |
||||||
Mobile Network (3G, 4G) |
Outgoing: DVO-R | Incoming: Mobile Connect | ||||
Phone Services are not registered | Outgoing Native Cellular Call | |||||
Incoming Mobile Connect |
To set up Dial via Office-Reverse (DVO-R), you must do the following:
To set up Cisco Unified Communications Manager to support DVO-R, perform the following procedures:
Use this procedure to set up an Enterprise Feature Access Number for all Cisco Jabber calls that are made using Dial via Office-Reverse.
The Enterprise Feature Access Number is the number that Cisco Unified Communications Manager uses to call the mobile phone and the dialed number unless a different number is set up in Mobility Profile for this purpose.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select . |
Step 3 | Select Add New. |
Step 4 |
In the Number field, enter the Enterprise Feature Access number. Enter a DID number that is unique in the system. To support dialing internationally, you can prepend this number with \+. |
Step 5 |
From the Route Partition drop-down list, choose the partition of the DID that is required for enterprise feature access. This partition is set under Clusterwide Parameters (System - Mobility) section, in the Inbound Calling Search Space for Remote Destination setting. This setting points either to the Inbound Calling Search Space of the Gateway or Trunk, or to the Calling Search Space assigned on the Phone Configuration screen for the device. , in theIf the user sets up the DVO Callback Number with an alternate number, ensure that you set up the trunk Calling Search Space (CSS) to route to destination of the alternate phone number. |
Step 6 | In the Description field, enter a description of the Mobility Enterprise Feature Access number. |
Step 7 | (Optional) Check the Default Enterprise Feature Access Number check box if you want to make this Enterprise Feature Access number the default for this system. |
Step 8 | Select Save. |
Use this procedure to set up a mobility profile for Cisco Jabber devices. This procedure is optional if you already set up an Enterprise Feature Access Number.
Mobility profiles allow you to set up the Dial via Office-Reverse settings for a mobile client. After you set up a mobility profile, you can assign it to a user or to a group of users, such as the users in a region or location.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select . |
Step 3 | In the Mobility Profile Information section, in the Name field, enter a descriptive name for the mobility profile. |
Step 4 | In the Dial via Office-Reverse Callback section, in the Callback Caller ID field, enter the caller ID for the callback call that the client receives from Cisco Unified Communications Manager. |
Step 5 | Click Save. |
Use the following procedure to verify that you are using the correct device COP file for this release of Cisco Jabber.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Select . |
Step 3 | Click Add New. |
Step 4 | From the Phone Type drop-down list, choose Cisco Dual Mode for iPhone. |
Step 5 | Click Next. |
Step 6 |
Scroll down to the Product Specific Configuration Layout section, and verify that you can see the Video Capabilities drop-down list. If you can see the Video Capabilities drop-down list, the COP file is already installed on your system. If you cannot see the Video Capabilities drop-down list, locate and download the correct COP file. For more information, see the Cisco Jabber Installation and Configuration Guide for your release. |
Use the following procedures to set up Dial via Office - Reverse for each TCT device.
Use this procedure to add a Mobility Identity to specify the mobile phone number of the mobile device as the destination number. This destination number is used by features such as Dial via Office or Mobile Connect.
You can specify only one number when you add a mobility identity. If you want to specify an alternate number such as a second mobile phone number for a mobile device, you can set up a remote destination. The Mobility Identity configuration characteristics are identical to those of the Remote Destination configuration.
Step 1 | Open the Cisco Unified CM Administration interface. | ||||||||||
Step 2 | Navigate to the device that you want to configure as follows: | ||||||||||
Step 3 | In the Associated Mobility Identity section, select Add a New Mobility Identity. | ||||||||||
Step 4 |
Enter the mobile phone number as the Destination Number. This number must be routable to an outbound gateway. Generally, the number is the full E.164 number.
|
||||||||||
Step 5 |
Enter the initial values for call timers. These values ensure that calls are not routed to the mobile service provider voicemail before they ring in the client on the mobile device. You can adjust these values to work with the end user's mobile network. For more information, see the online help in Cisco Unified Communications Manager. Example:
|
||||||||||
Step 6 | Do one of the following: | ||||||||||
Step 7 |
If you are setting up the Dial via Office feature, in the Mobility Profile drop-down list, select one of the following options.
|
||||||||||
Step 8 | Set up the schedule for routing calls to the mobile number. | ||||||||||
Step 9 | Select Save. |
Use this procedure to enable Dial via Office on each device.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Navigate to the device that you want to configure as follows: |
Step 3 | In the Device Information section, check the Enable Cisco Unified Mobile Communicator check box. |
Step 4 | In the Protocol Specific Information section, in the Rerouting Calling Search Space drop-down list, select a Calling Search Space (CSS) that can route the call to the DVO callback number. |
Step 5 | In the Product Specific Configuration Layout section, set the Dial via Office drop-down list to Enabled. |
Step 6 | Select Save. |
Step 7 | Select Apply Config. |
Step 8 | Instruct the user to sign out of the client and then to sign back in again to access the feature. |
Test this feature.
Voicemail avoidance is a feature that prevents calls from being answered by the mobile service provider voice mail. This feature is useful if a user receives a Mobile Connect call from the enterprise on the mobile device. It is also useful when an incoming DVO-R call is placed to the mobile device.
You can set up Voicemail Avoidance in one of two ways:
If you deploy DVO-R, Cisco recommends that you also set user-controlled Voicemail Avoidance. If you set user-controlled Voicemail Avoidance, this feature applies to both DVO-R and Mobile Connect calls.
For more information about voicemail avoidance, see the Confirmed Answer and DVO VM detection section in the Cisco Unified Communications Manager Features and Services Guide for your release.
Timer-controlled voicemail avoidance is supported on Cisco Unified Communications Manager Release 6.0 and later.
Set up the timer control method by setting the Answer Too Soon Timer and Answer Too Late Timer on either the Mobility Identity or the Remote Destination. For more information, see the Add Mobility Identity or Add Remote Destination (Optional) topics.
User-controlled voicemail avoidance is available on Cisco Unified Communications Manager Release 9.0 and later.
Set up User-Controlled Voicemail Avoidance as follows:
Cisco does not support user-controlled voicemail avoidance when using DVO-R with alternate numbers that the end user sets up in the client. An alternate number is any phone number that the user enters in the DVO Callback Number field on the client that does not match the phone number that you set up on the user's Mobility Identity.
If you set up this feature with alternate numbers, the Cisco Unified Communications Manager connects the DVO-R calls even if the callback connects to a wrong number or a voicemail system.
Use this procedure to set up the Cisco Unified Communications Manager to support user-controlled Voicemail Avoidance.
Step 1 | Open the Cisco Unified CM Administration interface. | ||
Step 2 | Select . | ||
Step 3 | In the Server drop-down list, select the active Cisco Unified Communications Manager. | ||
Step 4 | In the Service drop-down list, select the Cisco Call Manager (Active) service. | ||
Step 5 |
Configure the settings in the Clusterwide Parameters (System - Mobility Single Number Reach Voicemail) section.
|
||
Step 6 | Click Save. |
Use this procedure to enable user-controlled voicemail avoidance for the end user's mobility identity.
Step 1 | Open the Cisco Unified CM Administration interface. | ||
Step 2 | Navigate to the device that you want to configure as follows: | ||
Step 3 |
In the Associated Mobility Identity section, click the link for the Mobility Identity.
|
||
Step 4 |
Set the policies as follows:
|
||
Step 5 | Click Save. |
Use this procedure to enable user-controlled voicemail avoidance for the end user's remote destination.
Step 1 | Open the Cisco Unified CM Administration interface. |
Step 2 | Navigate to the device that you want to configure as follows: |
Step 3 | In the Associated Remote Destinations section, click the link for the associated remote destination. |
Step 4 |
Set the policies as follows:
|
Step 5 | If using Cisco Unified Communications Manager Version 10 with the Dial via Office feature, |
Step 6 | Click Save. |