Cisco Jabber for Android and iOS Features

Call Park

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.

Procedure
     Command or ActionPurpose
    Step 1Configure cluster wide call park   [Optional] Configure call park for the entire cluster, or use the procedure in Step 3 to configure call park on individual nodes within the cluster. 
    Step 2Configure a partition 

    Create a partition to add a call park number.

     
    Step 3Configure a call park number  

    Configure a call park number to use call park across nodes in a cluster.

    You can define either a single directory number or a range of directory numbers for use as call park extension numbers. You can park only one call at each call park extension number.

     

    Set Up Cisco Unified Communications Manager to Support Dial via Office

    To set up Cisco Unified Communications Manager to support Dial via Office-Reverse ( DvO-R), perform the following procedures:

    1. Complete one or both of the following procedures.

      • Set Up Enterprise Feature Access Number

      • Set Up Mobility Profile

    2. Complete the Verify Device COP File Version procedure.

    3. 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.

    Set Up Enterprise Feature Access Number

    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.

    Before You Begin

    • 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.

    Procedure
      Step 1   Open the Cisco Unified CM Administration interface.
      Step 2   Select Call Routing > Mobility > Enterprise Feature Access Number Configuration.
      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 System > Service Parameters, in the 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 window for the device.

      If 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.

      Set Up Mobility Profile

      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.

      Procedure
        Step 1   Open the Cisco Unified CM Administration interface.
        Step 2   Select Call Routing > Mobility > Mobility Profile.
        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.

        Verify Device COP File Version

        Use the following procedure to verify that you are using the correct device COP file for this release of Cisco Jabber.

        Procedure
          Step 1   Open the Cisco Unified CM Administration interface.
          Step 2   Select Device > Phone.
          Step 3   Click Add New.
          Step 4   From the Phone Type drop-down list, choose Cisco Dual Mode for iPhone.
          Step 5   From the Phone Type drop-down list, choose Cisco Dual Mode for Android.
          Step 6   Click Next.
          Step 7   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.

          Dial via Office

          Applies to: Cisco Jabber for Android, Cisco Jabber for iOS

          Important:
          The following features are not supported if the Dial via Office-Reverse (DvO-R) feature is enabled:

          • URI dialing

          • Secure Phone

          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:

          1. User initiates a DvO-R call.

          2. The client notifies Cisco Unified Communications Manager to call the mobile phone number.

          3. Cisco Unified Communications Manager calls and connects to the mobile phone number.

          4. Cisco Unified Communications Manager calls and connects to the number that the user dialed.

          5. Cisco Unified Communications Manager connects the two segments.

          6. The user and the called party continue as with an ordinary call.

          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.

          Note
          The users do not receive incoming calls on Cisco Jabber in the following situations:

          • If users select the Mobile Voice Network calling option on any network and the Single Number Reach (SNR) is not configured for their device, they will not receive incoming calls on Cisco Jabber.

          • If users select the Mobile Voice Network calling option on any network and the Single Number Reach (SNR) is configured with the Ring Schedule, they will not receive incoming calls on Cisco Jabber beyond the time set in the Ring Schedule.

          The following table describes the calling methods used for incoming and outgoing calls. The calling method (VoIP, Mobile Connect, DvO-R, or native cellular call) varies depending on the selected Calling Options and the network connection.

          Table 1 Calling Methods used with Calling Options over Different Network Connections

          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:

          1. 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.

          2. Enable DvO on each Cisco Dual Mode for iPhone device. See the Set Up Dial via Office for Each Device topic for more information.

          3. Enable DvO on each Cisco Dual Mode for Android device. See the Set Up Dial via Office for Each Device topic for more information.

          Set Up Dial via Office for Each Device

          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.

          1. Add a Mobility Identity for each user.

          2. Enable Dial via Office on each device.

          3. If you enabled Mobile Connect, verify that Mobile Connect works. Dial the desk phone extension and check that the phone number that is specified in the associated Mobile Identity rings.

          Add Mobility Identity

          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.

          Procedure
            Step 1   Open the Cisco Unified CM Administration interface.
            Step 2   Navigate to the device that you want to configure as follows:
            1. Select Device > Phone.
            2. Search for the device that you want to configure.
            3. Select the device name to open the Phone Configuration window.
            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.

            You must be able to rout this number to an outbound gateway. Generally, the number is the full E.164 number.

            Note   

            If you enable the Dial via Office — Reverse feature for a user, you must enter a destination number for the user's mobility identity.

            If you enable Dial via Office — Reverse and leave the destination number empty in the mobility identity:

            • The phone service cannot connect if the user selects the Autoselect calling option while using a mobile data network and VPN.

            • The phone service cannot connect if the user selects the Mobile Voice Network calling option on any type of network.

            • The logs do not indicate why the phone service cannot connect.

            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.

            The following is an example of mobility Identity timers' information in Cisco Unified Communications Manager 9.x.

            Setting

            Suggested Initial Value

            Answer Too Soon Timer

            3000

            Answer Too Late Timer

            20000

            Delay Before Ringing Timer

            0

            Note   

            This setting does not apply to DvO-R calls.

            The following is an example of mobility Identity timers' information in Cisco Unified Communications Manager 10.x.

            Setting

            Suggested Initial Value

            Wait * before ringing this phone when my business line is dialed.*

            0.0 seconds

            Prevent this call from going straight to this phone's voicemail by using a time delay of * to detect when calls go straight to voicemail.*

            3.0 seconds

            Stop ringing this phone after * to avoid connecting to this phone's voicemail.*

            20.0 seconds

            Step 6   Do one of the following:
            • Cisco Unified Communications Manager release 9 or earlier — Check the Enable Mobile Connect check box.
            • Cisco Unified Communications Manager release 10 — Check the Enable Single Number Reach check box.
            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.

            Option

            Description

            Leave blank

            Choose this option if you want users to use the Enterprise Feature Access Number (EFAN).

            Mobility Profile

            Choose the mobility profile that you just created if you want users to use a mobility profile instead of an EFAN.

            Step 8   Set up the schedule for routing calls to the mobile number.
            Step 9   Select Save.

            Enable Dial via Office on Each Device

            Use this procedure to enable Dial via Office on each device.

            Procedure
              Step 1   Open the Cisco Unified CM Administration interface.
              Step 2   Navigate to the device that you want to configure as follows:
              1. Select Device > Phone.
              2. Search for the device that you want to configure.
              3. Select the device name to open the Phone Configuration window.
              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.
              Note   

              DVO enabled devices may encounter issues registering with Cisco Unified Communications Manager. Resetting the device from the Cisco Unified Communications Manager administrative interface fixes this issue.

              What to Do Next

              Test this feature.

              Mobile Connect

              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.

              Procedure
                 Command or ActionPurpose
                Step 1Enable Mobile Connect
                                  		 
                Step 2Add Mobility Identity
                 

                To configure the mobile device phone number.

                 
                Step 3Add Remote Destination (Optional)
                 

                To configure an alternate phone number.

                 
                Step 4Test your settings. 

                • Exit Cisco Jabber on the mobile device.

                • Call the Cisco Jabber extension from another phone.

                • Verify that the native mobile network phone number rings and that the call connects when you answer it.

                 

                Enable Mobile Connect

                Use the following procedure to enable mobile connect for an end user.

                Procedure
                  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:
                  1. Select Device > Remote Destination.
                  2. Search for the destination number.
                  3. Delete the destination number.
                  Step 3   Configure the end user for mobile connect as follows:
                  1. Select User Management > End User.
                  2. Search for the end user.
                  3. Select the user id to open the End User Configuration window.
                  4. In the Mobility Information section, check the Enable Mobility check box.
                  5. On Cisco Unified Communications Manager Release 9.0 and earlier, specify the Primary User Device.
                  6. Select Save.
                  Step 4   Configure the device settings for mobile connect as follows:
                  1. Navigate to Device > Phone.
                  2. Search for the device that you want to configure.
                  3. Select the device name to open the Phone Configuration window.
                  4. Enter the following information:

                    Setting

                    Information

                    Softkey Template

                    Choose a softkey template that includes the Mobility button.

                    For information about setting up softkey templates, see the related information in the Cisco Unified Communications Manager Administration Guide for your release. This documentation can be found in the maintenance guides list.

                    Mobility User ID

                    Select the user.

                    Owner User ID

                    Select the user. The value must match the mobility user ID.

                    Rerouting Calling Search Space

                    Choose a Rerouting Calling Search Space that includes both of the following:

                    • The partition of the desk phone extension of the user. This requirement is used by the system to provide the Dial via Office feature, not for routing calls.

                    • A route to the mobile phone number. The route to the mobile phone number (that is, the Gateway/Trunk partition) must have a higher preference than the partitions of the enterprise extension that is associated with the device.

                    Note   

                    Cisco Jabber allows users to specify a callback number for Dial via Office-Reverse calls that is different from the mobile phone number of the device, and the Rerouting Calling Search Space controls which callback numbers are reachable.

                    If 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.

                  5. Select Save.

                  Add Remote Destination (Optional)

                  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.

                  Procedure
                    Step 1   Open the Cisco Unified CM Administration interface.
                    Step 2   Navigate to the device that you want to configure as follows:
                    1. Select Device > Phone.
                    2. Search for the device that you want to configure.
                    3. Select the device name to open the Phone Configuration window.
                    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:
                    1. Answer Too Soon Timer—Enter 3000
                    2. Answer Too Late Timer— Enter 20000
                    3. Delay Before Ringing Timer—0

                      This setting does not apply to DvO-R calls.

                    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:
                    • If you have Cisco Unified Communications Manager Version 9 or earlier, check the Enable Mobile Connect check box.
                    • If you have Cisco Unified Communications Manager Version 10, check the Enable Single Number Reach check box.
                    Step 7   Set up the schedule for routing calls to the mobile number.
                    Step 8   Select Save.

                    Move to Mobile

                    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.

                    There are two ways to enable this feature. You can also disable it.

                    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.

                    Enable Handoff from VoIP to 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 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.

                    Set Up Handoff DN

                    Before You Begin

                    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).

                    Procedure
                      Step 1   Open the Cisco Unified CM Administration interface.
                      Step 2   Select Call Routing > Mobility > Handoff Configuration.
                      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.

                      Note   

                      You cannot use translation patterns or other similar manipulations within Cisco Unified Communications Manager to match the inbound DID digits to the configured Handoff DN.

                      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.

                      Match Caller ID with Mobility Identity

                      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).

                      Before You Begin

                      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.

                      Procedure
                        Step 1   Open the Cisco Unified CM Administration interface.
                        Step 2   Select System > Service Parameters.
                        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.

                        Set Up User and Device Settings for Handoff

                        Before You Begin

                        • Set up the user device on the Cisco Unified Communications Manager.

                        • Set up the user with a Mobility Identity.

                        Procedure
                          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 Settings > Phone > Show My Caller ID 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 Menu > Call Settings > Additional settings > Caller ID > Show Number.
                          Step 5   Test this feature.

                          Enable Transfer from VoIP to Mobile Network

                          Procedure
                            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.
                            1. Select Device > Device Settings > Softkey Template.
                            2. Select the same softkey template that you selected when you configured the device for Mobile Connect.
                            3. In the Related Links drop-down list at the upper right, select Configure Softkey Layout and select Go.
                            4. In the call state drop-down list, select the On Hook state and verify that the Mobility key is in the list of selected softkeys.
                            5. In the call state drop-down list, select the Connected state and verify that the Mobility key is in the list of selected softkeys.
                            Step 3   Navigate to the device that you want to configure as follows:
                            1. Select Device > Phone.
                            2. Search for the device that you want to configure.
                            3. Select the device name to open the Phone Configuration window.
                            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.

                            1. Select the Owner User ID on the device page.
                            2. Select the Mobility User ID. The value usually matches that of the Owner User ID.
                            3. In the Product Specific Configuration Layout section, for the Transfer to Mobile Network option, select Use Mobility Softkey or Use HandoffDN Feature.
                            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.
                            What to Do Next

                            Test your settings by transferring an active call from VoIP to the mobile network.