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.
Applies to: Cisco Jabber for Android, Cisco Jabber for iOS
You can use call park to place a call on hold and pick it up from another phone in a Cisco Unified Communication Manager system. Call park must be enabled and extension numbers must be defined on each Cisco Unified Communication Manager node in a cluster. You can define either a single directory number or a range of directory numbers for use as call park extension numbers.
Complete the following tasks to enable call park. For detailed instructions, see the Feature Configuration Guide for Cisco Unified Communications Manager.
To set up Cisco Unified Communications Manager to support Dial via Office-Reverse ( DvO-R), perform the following procedures:
Complete one or both of the following procedures.
Complete the Verify Device COP File Version procedure.
If necessary, create application dial rules to allow the system to route calls to the Mobile Identity phone number to the outbound gateway. Ensure that the format of the Mobile Identity phone number matches the application dial rules.
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.
Reserve a Direct Inward Dial (DID) number to use as the Enterprise Feature Access Number (EFAN). This procedure is optional if you already set up a mobility profile.
Determine the required format for this number. The exact value you choose depends on the phone number that the gateway passes (for example, 7 digits or 10 digits). The Enterprise Feature Access Number must be a routable number.
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.
Use the following procedure to verify that you are using the correct device COP file for this release of Cisco Jabber.
Applies to: Cisco Jabber for Android, Cisco Jabber for iOS
User-controlled voicemail avoidance, which can be used in conjunction with the DvO 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.
You can make DvO-R calls over Expressway for Mobile and Remote Access when you are outside corporate network. DvO-R is supported on Cisco Expressway X8.7 and Cisco Unified Communications Manager 11.0(1a)SU1.
The DvO feature allows users to initiate Cisco Jabber outgoing calls with their work number using the mobile voice network for the device.
Cisco Jabber supports DvO-R (DvO-Reverse) calls, which works as follows:
User initiates a DvO-R call.
The client notifies Cisco Unified Communications Manager to call the mobile phone number.
Cisco Unified Communications Manager calls and connects to the mobile phone number.
Cisco Unified Communications Manager calls and connects to the number that the user dialed.
Cisco Unified Communications Manager connects the two segments.
The user and the called party continue as with an ordinary call.
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:
Set up the Cisco Unified Communications Manager to support DvO-R. See the Set Up Cisco Unified Communications Manager to Support DvO topic for more information.
Enable DvO on each Cisco Dual Mode for iPhone device. See the Set Up Dial via Office for Each Device topic for more information.
Enable DvO on each Cisco Dual Mode for Android device. See the Set Up Dial via Office for Each Device topic for more information.
Use the following procedures to set up Dial via Office - Reverse for each TCT device.
Use the following procedures to set up Dial via Office - Reverse for each BOT 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.
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.
Applies to: Cisco Jabber for Android, Cisco Jabber for iOS
Mobile connect, formerly known as Single Number Reach (SNR), allows the native mobile phone number to ring when someone calls the work number if:
Cisco Jabber is not available—After Cisco Jabber becomes available again and connects to the corporate network, Cisco Unified Communications Manager returns to placing VoIP calls rather than using mobile connect.
The user selects the Mobile Voice Network calling option.
The user selects the Autoselect calling option and the user is outside of the Wi-Fi network.
Command or Action | Purpose | |
---|---|---|
Step 1 | Enable Mobile Connect | |
Step 2 | Add Mobility Identity | To configure the mobile device phone number. |
Step 3 | Add Remote Destination (Optional) | To configure an alternate phone number. |
Step 4 | Test your settings. |
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 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.
You must be able to rout the number to an outbound gateway. Generally, the number is the full E.164 number. |
Step 5 | Enter the
initial values for the following 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. |
Step 6 | Do one of the following: |
Step 7 | Set up the schedule for routing calls to the mobile number. |
Step 8 | Select Save. |
Applies to: Cisco Jabber for Android, Cisco Jabber for iOS
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.
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. Select Disabled for the Transfer to Mobile Network option in the Product Specific Configuration Layout section of the BOT 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.
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 BOT 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 | In the Cisco Unified CM Administration interface, go to the BOT Device page, and select Use Handoff DN Feature for the Transfer to Mobile Network option. |
Step 3 | On the iOS device, tap to verify that Caller ID is on. |
Step 4 | On some Android device and operating system combinations, you can verify that the Caller ID is on. On the Android device, open the Phone application and tap . |
Step 5 | 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.