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.
See the
LCID for Languages topic for a full list of the languages
that you can specify.
This argument is optional.
If
you do not specify a value, Cisco Jabber for Windows uses the regional language
for the current user as the default.
From
Release 11.1(1) onwards, if you do not specify a value, Cisco Jabber for
Windows checks the value for the
UseSystemLanguage parameter. If the
UseSystemLanguage parameter is set to true, the same
language is used as for the operating system. If the
UseSystemLanguage parameter is to set to false or not
defined, then the client uses the regional language for the current user as the
default.
The
regional language is set at
.
|
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.
|
|
AUTOMATIC_SIGN_IN
|
true
false
|
Applies to Release 11.1(1) onwards.
Specifies whether the
Sign me in when Cisco Jabber starts check box is
checked when the user installs the client.
-
true—The
Sign me in when Cisco Jabber starts check box is
checked when the user installs the client.
-
false (default)—The
Sign me in when Cisco Jabber starts check box is not
checked when the user installs the client.
|
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 sign in to
multiple client instances.
By default, users can sign 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 sign 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 sign in to any other Cisco Jabber client
that uses the
wbxconnect
suffix.
-
MUT—Users can sign in to one instance of Cisco Jabber for
Windows at a time, but can sign 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
|
CLICK2X
|
DISABLE
|
Disables
click-to-x functionality with Cisco Jabber.
If you
specify this argument during installation, the client does not register as a
handler for click-to-x functionality with the operating system. This argument
prevents the client from writing to the Microsoft Windows registry during
installation.
You
must re-install the client and omit this argument to enable click-to-x
functionality with the client after installation.
|
ENABLE_PRT
|
true
false
|
If you
set the argument to false, users can still manually use the
directory, or the Program
files directory and launch the Problem Report Tool manually. If a user manually
creates a PRT, and this parameter value is set to false, then the zip file
created from the PRT has no content.
|
ENABLE_PRT_ENCRYPTION
|
true
false
|
Enables problem report encryption. You must configure this
argument with the
PRT_CERTIFICATE_NAME argument.
PRT
encryption requires a public/private key pair to encrypt and decrypt the Cisco
Jabber problem report.
|
PRT_CERTIFICATE_NAME
|
Certificate name
|
Specifies the name of a certificate with a public key in the
Enterprise Trust or Trusted Root Certificate Authorities certificate store. The
certificate public key is used to encrypt Jabber Problem reports. You must
configure this argument with the
ENABLE_PRT_ENCRYPTION argument.
|
INVALID_CERTIFICATE_BEHAVIOR
|
RejectAndNotify
PromptPerSession
|
Specifies the client behavior for invalid certificates.
For
invalid certificates in FIPS mode, this argument is ignored, the client
displays a warning message and doesn't load.
|
Telemetry_Enabled
|
true
false
|
Specifies whether analytics data is gathered. The default value
is true.
To
improve your experience and product performance, Cisco Jabber may collect and
send non-personally identifiable usage and performance data to Cisco. The
aggregated data is used by Cisco to understand trends in how Jabber clients are
being used and how they are performing.
Full
details on what analytics data Cisco Jabber does and does not collect can be
found in the Cisco Jabber Supplement to Cisco’s On-Line Privacy Policy at
http://www.cisco.com/web/siteassets/legal/privacy_02Jun10.html.
|
LOCATION_MODE
|
ENABLED
DISABLED
ENABLEDNOPROMPT
|
Specifies whether the Location feature is enabled and whether
users are notified when new locations are detected.
-
ENABLED(default)—Location feature is turned on. Users are
notified when new locations are detected.
-
DISABLED—Location feature is turned off. Users are not notified
when new locations are detected.
-
ENABLEDNOPROMPT—Location feature is turned on. Users are not
notified when new locations are detected.
|
FIPS_MODE
|
true
false
|
Specifies whether the Cisco Jabber is in FIPS mode.
Cisco Jabber can be in FIPS mode on an operating system that is not FIPS enabled. Only connections with non-Window's APIs are in FIPS mode.
If you don't include this setting, Cisco Jabber will determine the FIPS mode from the operating system.
|