Cisco Jabber Voice for Android Release 9.1(4) Administration Guide
Downloads: This chapterpdf (PDF - 1.34 MB) The complete bookPDF (PDF - 2.87 MB) | The complete bookePub (ePub - 292.0 KB) | Feedback



Set Up the Client

Perform this series of procedures to set up all your Cisco Jabber Voice features on your Unified CM, and then provide users with instructions for setting up the client on their devices.

Perform the following procedures in order:

  1. Add a test device with basic telephony features. See Add user device.
  2. Set up any additional features on your test device. These features are optional. See Feature setup.
  3. After you verify that all features work on your test device, set up individual users and devices in bulk. See Bulk configuration.
  4. Provide users with instructions for setting up their clients. See User instructions.

Add User Device

Before You Begin
  • Set up and test voicemail for the extension that you plan to assign to this device, following standard procedures for any device. Make sure you set up the voicemail number as a regular phone number so users can call in to the voicemail system using an Enterprise VoIP or mobile call.
  • Verify that the Device Pool that you plan to assign to the client device is associated with a region that includes support for one of the following codecs: G.711u, G.729a, or G.729b.
  • Determine whether you want to enable or disable usage and error tracking for each user. For information, see Usage and Error Tracking.
    Step 1   Sign in to the Unified CM Administration portal.
    Step 2   Add a new Cisco Dual Mode for Android phone device as follows:
    1. Select Device > Phone.
    2. Click Add New.
    3. In the Phone Type drop-down list, select Cisco Dual Mode for Android.
    Step 3   Enter settings for Device Information.

    Restrictions and requirements that are not specific to the client may apply to these values. If you need more information about any option on the device configuration page, see the online help in Unified CM.

    1. Enter the Device Name. The Device Name:
      • Must start with BOT
      • Must be uppercase
      • Can contain up to 15 characters
      • Can include only the following characters: A to Z, 0 to 9, dash (-), or underscore (_)
      Cisco recommends that the device name include the username of the user so it is easy to remember.

      Example:The recommended device name of user jsmith is BOTJSMITH.
    2. For the Phone Button Template, choose Standard Dual Mode for Android.
    3. 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.
      • Media Resource Group List

        You must select an option in the Media Resource Group List to ensure that users can merge the audio for calls.

      • User Hold MOH Audio Source
      • Network Hold MOH Audio Source

      Cisco Jabber Voice for Android does not support Multicast Music on Hold. Ensure that the Media Resource Group List that you apply to the client device does not contain multicast-enabled Media Resource Groups.

      These settings are not specific to this device. For information, see the Unified CM documentation.

    Step 4   Enter settings for Protocol Specific Information.
    1. In the Device Security Profile drop-down list, select Cisco Dual Mode for Android - Standard SIP Non-Secure Profile.

      This profile has SIP Digest Authentication disabled.

    2. In the SIP Profile drop-down list, select the appropriate SIP profile. See Create dedicated SIP profile.

    This document describes only the values of the Protocol Specific Information section that are specific to Cisco Jabber Voice for Android. You may need to enter other protocol-specific values that are not specific to the client for the device to work properly.

    Step 5   Enter settings for the Product Specific Configuration Layout section.
    1. Select the appropriate level of usage tracking in the Cisco Usage and Error Tracking drop-down list. See Usage and Error Tracking.
    2. In the Application Dial Rules URL field:
      • For Unified CM Release 8.6 and later, leave this field blank. For Unified CM 8.6 and later, you set the Application Dial Rules by choosing Call Routing > Dial Rules > Application Dial Rules. For information about Application Dial Rule setup, see the related chapter in the Cisco Unified Communications Manager Administration Guide for your release, available from the Unified CM maintenance guides list.
      • If you are using Unified CM Release 8.5 or earlier and you want the client to apply Application Dial Rules, you must specify the path to these dial rules files, including the filenames. Use the following format: tftp://ip address of TFTP server/pathname to the XML file/XML filename
    3. If your directory server requires authentication, enter the LDAP username and password; otherwise leave these fields blank.

      You can set up the LDAP credentials for a single read-only account for all users. These credentials are sent to the client in clear text in the TFTP file. Therefore, we strongly recommend that LDAP directory administrators generate a directory query account that has no other rights. Create this account with a value that is low enough to ensure that its credentials are semipublic (available to anyone on the local network).

    4. Enter designated emergency numbers in the Emergency Numbers field.

      You can enter a comma-separated list of additional emergency numbers that are always dialed direct for this user. These numbers must contain only numerical digits. No spaces, dashes, or other characters are permitted.

      Emergency numbers as defined on the device are always dialed direct using the mobile network (never dialed using Enterprise VoIP) to allow the location of the caller to be sent automatically to emergency services personnel where this service is available. Direct-dial numbers are useful in the following situations:

      • If users frequently travel to countries other than the country of their mobile network provider
      • If the emergency number differs depending on the users' location
      • If your company has a dedicated security number
    5. Enter your domain in the Domain Name field if the Unified CM Administration setting in System > Server is a hostname that does not include the domain name.
    6. In the Preset Wi-Fi Networks field, enter a list of up to three SSIDs separated by forward slashes (/).

      The client attempts to connect to Unified CM only after the mobile device is connected to an SSID that you list here, or one that the user selects in the client. The client must be able to reach Unified CM when it is connected to these SSIDs. Typically, these are your corporate Wi-Fi SSIDs. SSIDs can be up to 32 characters long and are case sensitive.

    Step 6   (Optional) In the Device Ringtone Volume drop-down list, select an option if you want to prevent users from silencing incoming Cisco Jabber Voice for Android calls.
    Option Description

    (Default) Select this option if you want to allow the user to set any ringtone volume on the Android device, including silent mode or vibrate.

    Low, Medium or High

    Select one of these options to specify the minimum ringtone volume on the user's device. Users can specify a louder ringtone volume than the minimum on their device.

    Step 7   (Optional) In the Device Ringtone drop-down list, select the desired ringtone option.
    Option Description
    Native Ringtone

    (Default) The client uses the ringtone that the user sets for the native phone application on the Android device.

    Cisco Ringtone

    The client uses only the Cisco ringtone (even if the user sets a different ringtone for the native phone application on the Android device).

    Step 8   Select Save.
    Step 9   Select Apply Config.
    Step 10   Select [Line number] - Add a new DN.
    Step 11   Enter the Directory Number (DN) of this device.

    This DN can be new; a desk phone with the same DN is not required.

    Step 12   (Optional) Enter Caller ID settings for the device.
    1. In the Directory Number Information section, in the Route Partition drop-down list, select a route partition to which the directory number belongs.
    2. (Optional) In the Description field, enter a description of the directory number and route partition.
    3. In the Alerting Name field, enter the name or directory number you want to appear for the Caller ID.
    4. In the ASCII Alerting Name field, enter the same information as the Alerting Name field, but limit the input to ASCII characters.
    5. In the Line number on Device device name section, in the Display (Caller ID) field, enter the name or directory number you want to appear for the Caller ID.
    6. In the ASCII Display (Caller ID) field, enter the same information as the Display (Caller ID) field, but limit the input to ASCII characters.
    7. If required, in the External Phone Number Mask field, enter the phone number (or mask) that is used to send Caller ID information when a call is placed from this line.
    8. In the Forwarded Call Information Display on Device device name section, check the Caller Name check box to display the caller name when a call is forwarded.
    9. Check the Dialed Number check box to display the original dialed number when a call is forwarded.
    Step 13   Set the No Answer Ring Duration to 24 seconds to allow time for the client to ring before calls go to voicemail.

    See general restrictions in the online help in Unified CM.

    Step 14   In the Multiple Call/Call Waiting Settings on Device device name section, in the Busy Trigger field, ensure that the value is set to 2 or greater.
    Step 15   Select Save.
    Step 16   Navigate to the End User page for the user.
    Step 17   Associate the Cisco Dual Mode for Android device that you just created for this user.

    After you associate the device, it appears in the Controlled Devices box in either the Device Information or Device Associations section (depending on your release of Unified CM).

    Step 18   If this user has a desk phone, select the desk phone as the Primary User Device.
    Step 19   If the device is a standalone device that runs without an associated desk phone, you may need to enter other information that is standard for all devices in your system.
    Step 20   Select Save.

    What to Do Next

    Verify that your configuration works:

    • Make sure the mobile device is connected to the corporate network. Verify that you can access a web page on your corporate intranet using the browser on your device.
    • Launch the client and complete the setup wizard. Enter the IP address of your TFTP server (generally the IP address of your Unified CM server) and the Device Name (BOTXXXX) of the device you just added. For information on completing the setup wizard, see the FAQs for end users.
    • Wait for a notice that the device is registered. The Cisco Jabber Voice icon in the status bar turns black when the device is connected to Unified CM.
    • Test basic telephony features in the client, such as the ability to make, hold, and transfer calls.

    Changes to User Device

    If you change settings on the Unified CM Administration pages (for example, LDAP, call control, dial plan), the client reregisters after you click Save and then click Apply Config. The application reregisters again 30 seconds later. If the user is on a call when the application reregisters, the call drops and the application restarts automatically. If the device is out of coverage at the time you apply the changes, the application updates later when it reregisters to Unified CM.

    If you delete the device from Unified CM, the client drops any active calls and after several reregister attempts the user receives an error message that it cannot connect. Client information is not erased from the device. To remove all client information (for example, if the employee leaves the company), use the appropriate device management solution, such as Microsoft ActiveSync.

    To delete a device, see “Deleting a Phone” topic in Cisco Unified Communications Manager Administration Guide for your release, available from the maintenance guides list.

    Bulk Configuration

    Use the information in this document to set up an individual test user and device as the basis for completing a Bulk Administration template to set up all users and devices.

    When you are ready for bulk processes, follow the instructions in the Bulk Administration Guide for your release of Unified CM, available from the maintenance guides list.


    The settings in the Product Specific Configuration Layout section of the device configuration page are not handled as individual columns in the exported spreadsheet. Instead, all of those settings, and the information they contain, appear as XML code in a single cell for each device. If you edit user-specific information in this cell, do so cautiously.

    User Instructions

    After you set up devices in Unified CM, give your users the following information:
    • Instructions for connecting the mobile device to the corporate Wi-Fi network. This process is independent of Cisco Jabber Voice for Android.
    • User documentation with instructions for setting up the client, available from the FAQs.

      If users are outside the corporate network when they set up the client for the first time, they must use a VPN connection to the corporate network. Users must set up this VPN connection before they use the client.

    • Instructions to download and install Cisco Jabber Voice for Android from Google Play (formerly known as Google Android Market).
    • The device name of their Cisco Dual Mode for Android device, for example BOTJSMITH.
    • The IP address or FQDN of the TFTP server.
    • (If applicable) Credentials that users need for SIP Digest Authentication. You must provide these credentials if you enabled SIP Digest Authentication and you set up users to manually authenticate to the Unified CM.


      Cisco Jabber Voice does not support SIP Digest Authentication with the Dial via Office - Reverse feature.

    • (If applicable) Credentials that users need to access visual voicemail.
    • (If applicable) Credentials that users need to access the corporate directory. The recommended username format is either or the full DN format, cn=userid,ou=organization,dc=company,dc=com.
    • (If applicable) Information that users need to access the corporate network remotely using VPN. Provide instructions to help users download, install, and set up a VPN client such as Cisco AnyConnect Secure Mobility Client. If you set up your system to use Cisco AnyConnect Secure Mobility Client, users can obtain information about how to install and use the client application on an Android device from the latest Android User Guide for Cisco AnyConnect Secure Mobility Client in the user guide list. Users can obtain the Cisco AnyConnect Secure Mobility Client application in one of the following ways:
      • Manual method: Ask users to manually download the Cisco AnyConnect Secure Mobility Client and Cisco Jabber Voice for Android applications for free from Google Play.


        Host the links to these two applications on an internal web portal to help users find them.

      • Automated method: Use Mobile Device Manager (MDM) software to push the applications to the devices so that the device automatically receives the two applications after registration. For information about how to use MDM, see the relevant third-party documentation.
    • The email address to which users can send problem reports (troubleshooting logs).
    • Instructions for users about how to send logs.

    Port and Protocol List

    The following table lists ports and protocols that are in Cisco Jabber Voice. The duration for each entry is “Ephemeral.”

    Table 1 Cisco Jabber Voice Ports and Protocols
    Feature Protocol Network Protocol Port Remarks
    Unified CM Registration TCP TCP 5060 SIP port for Unified CM Registration

    Phone Services


    69, then Ephemeral


    Desk Phone Integration

    QBE TCP 2748 N/A
    Media RTP UDP


    This range is specified by the Unified CM in the device configuration file. These are the default values and can be any valid port.

    Directory LDAP TCP 389 LDAP with optional TLS
    Unity Connection Voicemail VMREST TCP



    VMRest through HTTPS

    7080 for Jetty