Cisco Jabber for Windows 9.2.x Installation and Configuration Guide
Install Cisco Jabber
Downloads: This chapterpdf (PDF - 1.42MB) The complete bookPDF (PDF - 4.24MB) | The complete bookePub (ePub - 1.01MB) | Feedback

Install Cisco Jabber

Install Cisco Jabber

Review the options for installation and learn about different methods for installing Cisco Jabber. Understand the requirements for successful deployments before you start the installation procedure.

Methods of Installation

Cisco Jabber for Windows provides an MSI installation package. You can use this installation package in the following ways:
Use the Command Line

Specify arguments in a command line window to set installation properties.

Choose this option if you plan to install multiple instances.

Run the MSI Manually

Run the MSI manually on the file system of the client workstation and then specify connection properties when you start the client.

Choose this option if you plan to install a single instance for testing or evaluation purposes.

Create a Custom Installer

Open the default installation package, specify the required installation properties, and then save a custom installation package.

Choose this option if you plan to distribute an installation package with the same installation properties.

Deploy with Group Policy

Install the client on multiple computers in the same domain.

Use the Command Line

Specify installation arguments in a command line window.

Procedure
    Step 1   Open a command line window.
    Step 2   Enter the following command:
    msiexec.exe /i CiscoJabberSetup.msi
    Step 3   Specify command line arguments as parameter=value pairs.
    msiexec.exe /i CiscoJabberSetup.msi argument=value
    Step 4   Run the command to install Cisco Jabber for Windows.

    Example Installation Commands

    Review example commands to install Cisco Jabber for Windows.

    On-Premises deployments in default product mode

    msiexec.exe /i CiscoJabberSetup.msi CLEAR=1 TYPE=CUP ADDRESS=1.2.3.4 
    DOMAIN=domain.com LANGUAGE=1033 /quiet
    Where:
    • CLEAR=1 deletes any existing bootstrap file.
    • TYPE=CUP specifies Cisco Unified Presence as the presence server.
    • ADDRESS=1.2.3.4 specifies 1.2.3.4 as the IP address of the presence server.
    • DOMAIN=domain.com specifies domain.com as the domain name of the presence server.
    • LANGUAGE=1033 specifies English as the language.
    • /quiet specifies a silent installation.

    On-Premises deployments in phone mode

    msiexec.exe /i CiscoJabberSetup.msi CLEAR=1 PRODUCT_MODE=Phone_Mode TFTP=1.2.3.4 
    LANGUAGE=1033 /quiet
    Where:
    • CLEAR=1 deletes any existing bootstrap file.
    • PRODUCT_MODE=Phone_Mode specifies phone mode as the product mode.
    • TFTP=1.2.3.4 specifies 1.2.3.4 as the IP address of the TFTP server.
    • LANGUAGE=1033 specifies English as the language.
    • /quiet specifies a silent installation.

    Cloud-Based deployments

    msiexec.exe /i CiscoJabberSetup.msi CLEAR=1 TYPE=WebEx SSO_ORG_DOMAIN=domain.com /quiet
    Where:
    • CLEAR=1 deletes any existing bootstrap file.
    • TYPE=WebEx specifies Cisco WebEx Messenger as the presence server.
    • SSO_ORG_DOMAIN=domain.com specifies domain.com as the domain name for SSO.
    • /quiet specifies a silent installation.

    Run the MSI Manually

    You can run the installation program manually to install a single instance of the client and specify connection settings in the Connection Settings window.

    Procedure
      Step 1   Launch CiscoJabberSetup.msi.

      The installation program opens a window to guide you through the installation process.

      Step 2   Follow the steps to complete the installation process.
      Step 3   Start Cisco Jabber for Windows.
      Step 4   Select File > Change connection settings.

      The Connection Settings window opens.

      Step 5   Specify values for the connection settings properties.
      Step 6   Select Save.

      Related References

      Create a Custom Installer

      You can transform the default installation package to create a custom installer.


      Note


      You use Microsoft Orca to create custom installers. Microsoft Orca is available as part of the Microsoft Windows SDK for Windows 7 and .NET Framework 4.

      Download and install Microsoft Windows SDK for Windows 7 and .NET Framework 4 from the Microsoft website.


      Get the Default Transform File

      You must have the default transform file to modify the installation package with Microsoft Orca.

      Procedure
        Step 1   Download the Cisco Jabber administration package from Cisco.com.
        Step 2   Copy CiscoJabberProperties.mst from the Cisco Jabber administration package to your file system.

        Related Information

        Create Custom Transform Files

        To create a custom installer, you use a transform file. Transform files contain installation properties that you apply to the installer.

        The default transform file lets you specify values for properties when you transform the installer. You should use the default transform file if you are creating one custom installer.

        You can optionally create custom transform files. You specify values for properties in a custom transform file and then apply it to the installer.

        Create custom transform files if you require more than one custom installer with different property values. For example, create one transform file that sets the default language to French and another transform file that sets the default language to Spanish. You can then apply each transform file to the installation package separately. The result is that you create two installers, one for each language.

        Procedure
          Step 1   Start Microsoft Orca.
          Step 2   Open CiscoJabberSetup.msi and then apply CiscoJabberProperties.mst.
          Step 3   Specify values for the appropriate installer properties.
          Step 4   Generate and save the transform file.
          1. Select Transform > Generate Transform.
          2. Select a location on your file system to save the transform file.
          3. Specify a name for the transform file and select Save.

          The transform file you created is saved as file_name.mst. You can apply this transform file to modify the properties of CiscoJabberSetup.msi.

          Transform the Installer

          Apply a transform file to customize the installer.


          Note


          Applying transform files will alter the digital signature of CiscoJabberSetup.msi. Attempts to modify or rename CiscoJabberSetup.msi will remove the signature entirely.


          Procedure
            Step 1   Start Microsoft Orca.
            Step 2   Open CiscoJabberSetup.msi in Microsoft Orca.
            1. Select File > Open.
            2. Browse to the location of CiscoJabberSetup.msi on your file system.
            3. Select CiscoJabberSetup.msi and then select Open.

            The installation package opens in Microsoft Orca. The list of tables for the installer opens in the Tables pane.

            Step 3   Remove all language codes except for 1033 (English).
            Restriction:

            You must remove all language codes from the custom installer except for 1033 (English).

            Microsoft Orca does not retain any language files in custom installers except for the default, which is 1033. If you do not remove all language codes from the custom installer, you cannot run the installer on any operating system where the language is other than English.

            1. Select View > Summary Information.

              The Edit Summary Information window displays.

            2. Locate the Languages field.
            3. Delete all language codes except for 1033.
            4. Select OK.

            English is set as the language for your custom installer.

            Step 4   Apply a transform file.
            1. Select Transform > Apply Transform.
            2. Browse to the location of the transform file on your file system.
            3. Select the transform file and then select Open.
            Step 5   Select Property from the list of tables in the Tables pane.

            The list of properties for CiscoJabberSetup.msi opens in the right panel of the application window.

            Step 6   Specify values for the properties you require.
            Tip   

            Set the value of the CLEAR property to 1 to override any existing bootstrap file from previous installations. If you do not override existing bootstrap files, the values you set in the custom installer do not take effect.

            Step 7   Drop any properties that you do not require. It is essential to drop any properties that are not being set, otherwise the properties being set will not take effect. Drop each property that is not needed one at a time.
            1. Right-click the property you want to drop.
            2. Select Drop Row.
            3. Select OK when Microsoft Orca prompts you to continue.
            Step 8   Enable your custom installer to save embedded streams.
            1. Select Tools > Options.
            2. Select the Database tab.
            3. Select Copy embedded streams during 'Save As'.
            4. Select Apply and then OK.
            Step 9   Save your custom installer.
            1. Select File > Save Transformed As.
            2. Select a location on your file system to save the installer.
            3. Specify a name for the installer and then select Save.

            Related References

            Deploy with Group Policy

            Install Cisco Jabber for Windows with Group Policy using the Microsoft Group Policy Management Console (GPMC) on Microsoft Windows Server.


            Note


            To install Cisco Jabber for Windows with Group Policy, all computers or users to which you plan to deploy Cisco Jabber for Windows must be in the same domain.


            Set a Language Code

            Altering the installation language is not necessary in Group Policy deployment scenarios where the exact MSI file provided by Cisco will be used. The installation language will be determined from the Windows User Locale (Format) in these situations. You must use this procedure and set the Language field to 1033 only if the MSI is to be modified by Orca in any way.

            Procedure
              Step 1   Start Microsoft Orca.

              Microsoft Orca is available as part of the Microsoft Windows SDK for Windows 7 and .NET Framework 4 that you can download from the Microsoft website.

              Step 2   Open CiscoJabberSetup.msi.
              1. Select File > Open.
              2. Browse to the location of CiscoJabberSetup.msi on your file system.
              3. Select CiscoJabberSetup.msi and then select Open.
              Step 3   Select View > Summary Information.
              Step 4   Locate the Languages field.
              Step 5   Set the Languages field to 1033.
              Step 6   Select OK.
              Step 7   Enable your custom installer to save embedded streams.
              1. Select Tools > Options.
              2. Select the Database tab.
              3. Select Copy embedded streams during 'Save As'.
              4. Select Apply and then OK.
              Step 8   Save your custom installer.
              1. Select File > Save Transformed As.
              2. Select a location on your file system to save the installer.
              3. Specify a name for the installer and then select Save.

              Related References

              Deploy the Client with Group Policy

              Complete the steps in this task to deploy Cisco Jabber for Windows with Group Policy.

              Procedure
                Step 1   Copy the installation package to a software distribution point for deployment.

                All computers or users to which you plan to deploy Cisco Jabber for Windows must be able to access the installation package on the distribution point.

                Step 2   Select Start > Run and then enter the following command:
                GPMC.msc

                The Group Policy Management console opens.

                Step 3   Create a new group policy object.
                1. Right-click on the appropriate domain in the left pane.
                2. Select Create a GPO in this Domain, and Link it here.

                  The New GPO window opens.

                3. Enter a name for the group policy object in the Name field.
                4. Leave the default value or select an appropriate option from the Source Starter GPO drop-down list and then select OK.

                  The new group policy displays in the list of group policies for the domain.

                Step 4   Set the scope of your deployment.
                1. Select the group policy object under the domain in the left pane.

                  The group policy object displays in the right pane.

                2. Select Add in the Security Filtering section of the Scope tab.

                  The Select User, Computer, or Group window opens.

                3. Specify the computers and users to which you want to deploy Cisco Jabber for Windows.
                Step 5   Specify the installation package.
                1. Right-click the group policy object in the left pane and then select Edit.

                  The Group Policy Management Editor opens.

                2. Select Computer Configuration and then select Policies > Software Settings.
                3. Right-click Software Installation and then select New > Package.
                4. Enter the location of the installation package next to File Name; for example, \\server\software_distribution.
                  Important:

                  You must enter a Uniform Naming Convention (UNC) path as the location of the installation package. If you do not enter a UNC path, Group Policy cannot deploy Cisco Jabber for Windows.

                5. Select the installation package and then select Open.
                6. In the Deploy Software dialog box, select Assigned and then OK.

                Group Policy installs Cisco Jabber for Windows on each computer the next time each computer starts.

                Cisco Media Services Interface


                Note


                The Cisco Jabber for Windows MSI is supported on Microsoft Windows 8 with the exception of desktop phone video. The MSI does not support Microsoft Windows 8.1.
                Important:
                • Cisco Medianet does not currently support Microsoft Windows 8. As a result, you cannot currently do the following on Microsoft Windows 8:
                  • Use Cisco Media Services Interface to classify and prioritize audio media and video media traffic on the network.
                  • Enable desk phone video capabilities.

                Traffic Marking

                Cisco Media Services Interface provides a Microsoft Windows service that works with Cisco Prime Collaboration Manager and Cisco Medianet-enabled routers to ensure that Cisco Jabber can send audio media and video media on your network with minimum latency or packet loss.

                Before Cisco Jabber sends audio media or video media, it checks for Cisco Media Services Interface.
                • If the service exists on the computer, Cisco Jabber provides flow information to Cisco Media Services Interface. The service then signals the network so that routers classify the flow and provide priority to the Cisco Jabber traffic.
                • If the service does not exist, Cisco Jabber does not use it and sends audio media and video media as normal.

                Note


                Cisco Jabber checks for Cisco Media Services Interface for each audio call or video call.


                Desk Phone Video Capabilities

                You must install Cisco Media Services Interface to enable desk phone video capabilities. Cisco Media Services Interface provides a driver that enables Cisco Jabber for Windows to do the following:
                • Discover the desk phone device.
                • Establish and maintain a connection to the desk phone device using the CAST protocol.

                Prepare Your Network

                To install Cisco Media Services Interface for traffic marking, you must prepare your network.

                Procedure
                  Step 1   Install Cisco Prime Collaboration Manager.
                  Step 2   Install routers or switches enabled for Cisco Medianet where appropriate.
                  Step 3   Configure your network to handle the metadata attributes that Cisco Media Services Interface applies to applications.

                  Not all devices on your network must support Cisco Medianet.

                  The first hop should prioritize traffic based on the metadata attributes from Cisco Media Services Interface. As the traffic traverses the network, all other devices should also prioritize that traffic unless you configure policies on those devices to handle the traffic differently.


                  Install Cisco Media Services Interface

                  Procedure
                    Step 1   Download the Cisco Media Services Interface installation program from the download site on Cisco.com.
                    Step 2   Install Cisco Media Services Interface on each computer on which you install Cisco Jabber.

                    See the appropriate Cisco Medianet documentation for installing Cisco Media Services Interface.


                    Uninstall Cisco Jabber for Windows

                    You can uninstall Cisco Jabber for Windows using either the command line or the Microsoft Windows control panel. This document describes how to uninstall Cisco Jabber for Windows using the command line.

                    Use the Installer

                    If the installer is available on the file system, use it to remove Cisco Jabber for Windows.

                    Procedure
                      Step 1   Open a command line window.
                      Step 2   Enter the following command:
                      msiexec.exe /x path_to_CiscoJabberSetup.msi
                      For example,
                      msiexec.exe /x C:\Windows\Installer\CiscoJabberSetup.msi /quiet
                      Where /quiet specifies a silent uninstall.

                      The command removes Cisco Jabber for Windows from the computer.

                      Use the Product Code

                      If the installer is not available on the file system, use the product code to remove Cisco Jabber for Windows.

                      Procedure
                        Step 1   Find the product code.
                        1. Open the Microsoft Windows registry editor.
                        2. Locate the following registry key: HKEY_CLASSES_ROOT\Installer\Products
                        3. Select Edit > Find.
                        4. Enter Cisco Jabber in the Find what text box in the Find window and select Find Next.
                        5. Find the value of the ProductIcon key.

                          The product code is the value of the ProductIcon key, for example, C:\Windows\Installer\{product_code}\ARPPRODUCTICON.exe.

                          Note   

                          The product code changes with each version of Cisco Jabber for Windows.

                        Step 2   Open a command line window.
                        Step 3   Enter the following command:
                        msiexec.exe /x product_code
                        For example,
                        msiexec.exe /x 45992224-D2DE-49BB-B085-6524845321C7 /quiet
                        Where /quiet specifies a silent uninstall.

                        The command removes Cisco Jabber for Windows from the computer.

                        Command Line Arguments

                        This section describes the command line arguments you can use to install Cisco Jabber for Windows.

                        Override Argument

                        The following table describes the parameter you must specify to override any existing bootstrap files from previous installations:

                        Argument Value Description
                        CLEAR 1

                        Specifies if the client overrides any existing bootstrap file from previous installations.

                        The client saves the arguments and values you set during installation to a bootstrap file. The client then loads settings from the bootstrap file at startup.

                        If you specify CLEAR, the following occurs during installation:
                        1. The client deletes any existing bootstrap file.
                        2. The client creates a new bootstrap file.
                        If you do not specify CLEAR, the client checks for existing bootstrap files during installation.
                        • If no bootstrap file exists, the client creates a bootstrap file during installation.
                        • If a bootstrap file exists, the client does not override that bootstrap file and preserves the existing settings.

                        Note


                        If you are reinstalling Cisco Jabber for Windows, you should consider the following:
                        • The client does not preserve settings from existing bootstrap files. If you specify CLEAR, you must also specify all other installation arguments as appropriate.
                        • The client does not save your installation arguments to an existing bootstrap file. If you want to change the values for installation arguments, or specify additional installation arguments, you must specify CLEAR to override the existing settings.

                        To override existing bootstrap files, specify CLEAR in the command line as follows:
                        msiexec.exe /i CiscoJabberSetup.msi CLEAR=1

                        Mode Type Argument

                        The following table describes the command line argument with which you specify the product mode:

                        Argument Value Description
                        PRODUCT_MODE

                        Default

                        Phone_Mode

                        Specifies the product mode for the client. Set one of the following values:
                        Default

                        Set this value if users authenticate to a presence server as the primary login.

                        Choose this value:
                        • To provision users with instant messaging and presence as base functionality.
                        • For cloud-based deployments.
                        Phone_Mode

                        Set this value if users authenticate to Cisco Unified Communications Manager as the primary login.

                        Choose this value to provision users with audio devices as base functionality.

                        Phone Service Arguments

                        This section describes the command line arguments you specify so that the client can connect to phone services.

                        Set these arguments during installation if you plan to deploy the client in phone mode.

                        Argument Value Description
                        TFTP

                        IP address

                        Hostname

                        FQDN

                        Specifies the address of your TFTP server. Set one of the following as the value:
                        • Hostname (hostname)
                        • IP address (123.45.254.1)
                        • FQDN (hostname.domain.com)

                        If your deployment includes a presence server, specify the address of the Cisco Unified Communications Manager TFTP service that hosts the device configuration.

                        If you deploy in phone mode, specify the address of the TFTP server that hosts the client configuration.

                        See TFTP Server Address for more information.

                        CTI

                        IP address

                        Hostname

                        FQDN

                        Specifies the address of your CTI server.

                        This argument is required if users have desk phone devices and require a CTI server.

                        CCMCIP

                        IP address

                        Hostname

                        FQDN

                        Specifies the address of your CCMCIP server.

                        This argument is required only if the address of your CCMCIP server is not the same as the TFTP server address. If the address of the CCMCIP server is the same as the TFTP server address, the client can use the TFTP server address to connect to the CCMCIP server.

                        TFTP Server Address

                        Cisco Jabber for Windows retrieves two different configuration files from the TFTP server:
                        • Client configuration files that you create.
                        • Device configuration files that reside on the Cisco Unified Communications Manager TFTP service when you provision users with devices.

                        To minimize effort, you should host your client configuration files on the Cisco Unified Communications Manager TFTP service. You then have only one TFTP server address for all configuration files and can specify that address as required.

                        You can, however, host your client configuration on a different TFTP server to the one that contains the device configuration. In this case, you have two different TFTP server addresses, one address for the TFTP server that hosts device configuration and another address for the TFTP server that hosts client configuration files.

                        Default Deployments

                        This section describes how you should handle two different TFTP server addresses in deployments that have a presence server.

                        You should do the following:
                        1. Specify the address of the TFTP server that hosts the client configuration on the presence server.
                        2. During installation, specify the address of the Cisco Unified Communications Manager TFTP service with the TFTP argument.
                        When the client starts for the first time, it:
                        1. Retrieves the address of the Cisco Unified Communications Manager TFTP service from the bootstrap file.
                        2. Gets device configuration from the Cisco Unified Communications Manager TFTP service.
                        3. Connects to the presence server.
                        4. Retrieves the address of the TFTP service that hosts the client configuration from the presence server.
                        5. Gets client configuration from the TFTP server.
                        Phone Mode Deployments

                        This section describes how you should handle two different TFTP server addresses in phone mode deployments.

                        You should do the following:
                        1. During installation, specify the address of the TFTP server that hosts the client configuration with the TFTP argument.
                        2. Specify the address of the TFTP server that hosts the device configuration in your client configuration file with the following parameter: TftpServer1.
                        3. Host the client configuration file on the TFTP server.
                        When the client starts for the first time, it:
                        1. Retrieves the address of the TFTP server from the bootstrap file.
                        2. Gets client configuration from the TFTP server.
                        3. Retrieves the address of the Cisco Unified Communications Manager TFTP service from the client configuration.
                        4. Gets device configuration from the Cisco Unified Communications Manager TFTP service.
                        Related Concepts
                        Related References

                        Presence Server Arguments

                        This section describes the command line arguments you specify so that Cisco Jabber for Windows can connect to your presence server. Specify these arguments if you plan to install:
                        • Full UC deployments with instant messaging and presence as base functionality
                        • Cisco Jabber for Everyone deployments with instant messaging and presence only
                        • Cloud-based deployments
                        Argument Value Description
                        TYPE

                        CUP

                        WebEx

                        Defines the type of presence server. Set one of the following values:
                        CUP
                        Cisco Unified Presence or Cisco Unified Communications IM and Presence
                        WebEx
                        Cisco WebEx Messenger
                        ADDRESS

                        Hostname

                        IP address

                        FQDN

                        Specifies the address of your presence server. Set one of the following as the value:
                        • Hostname (hostname)
                        • IP address (123.45.254.1)
                        • FQDN (hostname.domain.com)

                        You must specify a value for this argument if your presence server does not support domain name system service records (DNS SRV). For example, Cisco Unified Presence 8.5.2 does not support DNS SRV.

                        DOMAIN

                        Domain name

                        Identifies the domain name of the presence server. Specify the domain name as the value of this argument; for example, domain.com.

                        You must specify this argument if the domain of the presence server is not the same as the domain of the workstations on which the client is installed.

                        You can verify the domain of your presence server as follows:
                        1. Do one of the following:
                          • Cisco Unified Presence: Open the Cisco Unified Presence Administration interface.
                          • Cisco Unified Communications IM and Presence: Open the Cisco Unified CM IM and Presence Administration interface.
                        2. Select System > Cluster Topology.
                        3. Select Settings.
                        4. Note the domain name as the value of the Domain Name field.

                        Common Installation Arguments

                        The following table describes command line arguments that are common to all deployments:

                        Argument Value Description
                        LANGUAGE

                        LCID in decimal

                        Defines the Locale ID (LCID), in decimal, of the language that Cisco Jabber for Windows uses. The value must be an LCID in decimal that corresponds to a supported language.

                        For example, you can specify one of the following:
                        • 1033 specifies English.
                        • 1036 specifies French.

                        This argument is optional. If you do not specify a value, Cisco Jabber for Windows uses the system locale language as the default.

                        See the Supported Languages topic for a full list of the languages you can specify.

                        FORGOT_PASSWORD_URL

                        URL

                        Specifies the URL where users can reset lost or forgotten passwords.

                        This argument is optional but recommended.

                        Note    In cloud-based deployments, you can specify a forgot password URL using the Cisco WebEx Administration Tool. However, the client cannot retrieve that forgot password URL until users sign in.
                        TFTP_FILE_NAME

                        Filename

                        Specifies the unique name of a group configuration file.

                        You can specify either an unqualified or fully qualified filename as the value. The filename you specify as the value for this argument takes priority over any other configuration file on your TFTP server.

                        This argument is optional.

                        Remember:

                        You can specify group configuration files in the Cisco Support Field on the CSF device configuration on Cisco Unified Communications Manager.

                        LOGIN_RESOURCE

                        WBX

                        MUT

                        Controls user log in to multiple client instances.

                        By default, users can log in to multiple instances of Cisco Jabber at the same time. Set one of the following values to change the default behavior:
                        WBX

                        Users can log in to one instance of Cisco Jabber for Windows at a time.

                        Cisco Jabber for Windows appends the wbxconnect suffix to the user's JID. Users cannot log in to any other Cisco Jabber client that uses the wbxconnect suffix.

                        MUT

                        Users can log in to one instance of Cisco Jabber for Windows at a time, but can log in to other Cisco Jabber clients at the same time.

                        Each instance of Cisco Jabber for Windows appends the user's JID with a unique suffix.

                        LOG_DIRECTORY Absolute path on the local filesystem

                        Defines the directory where the client writes log files.

                        Use quotation marks to escape space characters in the path, as in the following example:

                        "C:\my_directory\Log Directory"

                        The path you specify must not contain Windows invalid characters.

                        The default value is %USER_PROFILE%\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs

                        SSO Arguments

                        This section describes the command line arguments you can use to deploy Cisco Jabber for Windows with single sign on (SSO) capabilities.

                        Cloud-Based SSO Arguments

                        The arguments in the following table apply to cloud-based deployments only:
                        Argument Value Description
                        SSO_ORG_DOMAIN

                        Domain name

                        Specifies the domain name for the Cisco WebEx Org that contains the URL for the SSO service.

                        Cisco Jabber for Windows uses this argument to retrieve the URL of the SSO service from the Org. When Cisco Jabber for Windows gets the SSO service URL, it can request login tokens to authenticate with Cisco WebEx Messenger.

                        Note   

                        You specify the URL for the SSO service as the value of the Customer SSO Service Login URL in the Cisco WebEx Administration Tool.

                        Installer Properties

                        The following are the properties you can modify in a custom installer:
                        • CLEAR
                        • PRODUCT_MODE
                        • TFTP
                        • CTI
                        • CCMCIP
                        • TYPE
                        • ADDRESS
                        • DOMAIN
                        • LANGUAGE
                        • TFTP_FILE_NAME
                        • FORGOT_PASSWORD_URL
                        • SSO_ORG_DOMAIN
                        • LOGIN_RESOURCE
                        • LOG_DIRECTORY

                        These properties correspond to the installation arguments and have the same values.

                        Supported Languages

                        The following table lists the languages that Cisco Jabber for Windows supports:
                        • Arabic
                        • Bulgarian
                        • Catalan
                        • Croatian
                        • Czech
                        • Danish
                        • German
                        • Greek
                        • English
                        • Spanish
                        • Finnish
                        • French
                        • Hebrew
                        • Hungarian
                        • Italian
                        • Japanese
                        • Korean
                        • Norwegian
                        • Dutch
                        • Polish
                        • Portuguese - Brazil
                        • Portuguese - Portugal
                        • Romanian
                        • Russian
                        • Serbian
                        • Slovak
                        • Slovenian
                        • Swedish
                        • Thai
                        • Turkish
                        • Chinese - China
                        • Chinese - Taiwan

                        Note


                        Cisco Jabber for Windows does not support Locale IDs for all sub-languages. For example, if you specify French - Canada, Cisco Jabber for Windows uses French - France.


                        See the following documentation for more information about Locale IDs:
                        • Microsoft Windows Locale Code Identifier (LCID) Reference
                        • Locale IDs Assigned by Microsoft