The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Applies to: All clients
The sign out inactivity timer allows you to automatically sign users out of the client after a specified amount of time of inactivity.
This feature is configured on the mobile clients using the ForceLogoutTimerMobile parameter.
This feature is configured on the desktop clients using the ForceLogoutTimerDesktop parameter.
If the parameter is not set, the client will not automatically sign out.
Applies to: Cisco Jabber for Windows
The client uses an HTTP POST method to submit problem reports. Create a custom script to accept the POST request and specify the URL of the script on your HTTP server as a configuration parameter. Because users can save problem reports locally, you should also create an HTML page with a form to enable users to upload problem reports.
The following is an example form that accepts problem reports:
<form name="uploadPrt" action="http://server_name.com/scripts/UploadPrt.php" method="post" enctype="multipart/form-data"> <input type="file" name="zipFileName" id="zipFileName" /><br /> <input type="submit" name="submitBtn" id="submitBtn" value="Upload File" /> </form>
--help—Show the help message.
--privatekey—Specify the private key file, this is a privacy enhanced mail (.pem) or a personal information exchange PKCS#12 (.pfx) format.
--password—Optional, if the input private key file is password protected.
--encryptionkey—Specify the encryption secret key file, for example file.zip.esk.
--encryptedfile—Specify the encrypted file, for example file.zip.enc.
--outputfile—Specify the output file, for example decryptedfile.zip.
--mobile—Specify for the problem reports from mobile clients.
Applies to: All clients
Silent call monitoring is a Cisco Unified Communications Manager feature that allows a supervisor to hear both call participants, but neither of the call participants can hear the supervisor.
Call recording is a Cisco Unified Communications Manager feature that enables a recording server to archive agent conversations.
Cisco Jabber does not provide any interface to begin silent monitoring or call recording. Use the appropriate software to silently monitor or record calls.
Cisco Jabber does not currently support monitoring notification tone or recording notification tone.
You can use silent monitoring and call recording functionality only. Cisco Jabber does not support other functionality such as barging or whisper coaching.
Server Requirements:
Silent monitoring and call recording are supported for on-premises deployment only.
Cisco Jabber for Windows and Cisco Jabber for Mac require Cisco Unified Communications Manager 9.x or later.
Cisco Jabber for iPhone and iPad and Cisco Jabber for Android require Cisco Unified Communications Manager 11.0 or later.
Before you configure this feature on the server, there are releases of Cisco Unified Communications Manager that require a device package to enable monitoring and recording capabilities. Verify that the Built In Bridge field is available in the Phone Configuration window for the device. If the field is not available, download and apply the most recent device packages.
For detailed information about how to configure silent monitoring or call recording, see the Feature Configuration Guide for Cisco Unified Communications Manager, Release 11.0(1).
Applies to: All clients
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.
You must install the following root certificate to use the telemetry feature: GoDaddy Class 2 Certification Authority Root Certificate. The telemetry server certificate name is "metrics-a.wbx2.com". To resolve any warnings about this certificate name, install the required GoDaddy certificate. For more information about certificates, see the Planning Guide.
Telemetry_Enabled—Specifies whether analytics data is gathered. The default value is true.
TelemetryEnabledOverCellularData—Specifies whether analytics data is sent over cellular data and Wi-Fi (true), or Wi-Fi only (false). The default value is true.
TelemetryCustomerID—This optional parameter specifies the source of analytic information. This ID can be a string that explicitly identifies an individual customer, or a string that identifies a common source without identifying the customer. We recommend using a tool that generates a Global Unique Identifier (GUID) to create a 36 character unique identifier, or to use a reverse domain name.
For more information about these parameters, see the Parameters Reference Guide.
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 https://www.cisco.com/web/siteassets/legal/privacy_02Jun10.html.