Jabber for Windows

Jabber for Mac

DownloadURL

The DownloadURL file element in the XML file for automatic updates is:

The DownloadURL file element refers to the Cisco Jabber for Mac installation file. The installation file on the update server must be renamed to match this DownloadURL file element name.

You can also download the manual installation file, if your users install the client manually.

Note	To ensure the DSA signature succeeds, configure Web servers to escape special characters. For example, on Microsoft IIS the option is: Allow double spacing.

Support for Webex meetings on the Webex Suite meeting platform

Released in 14.2.

Support Webex meetings on the Webex Suite meeting platform.

Note

For customers who use Cisco Jabber clients to join Webex meetings: Webex meetings are hosted on our Webex Suite meeting platform. Find out if your meetings use the Webex Suite meeting platform. To avoid issues joining Webex meetings on the Webex Suite meeting platform, please upgrade your Jabber client to version 14.2 or later for Windows, Mac, Android, iPhone, or iPad. Failure to do so may result in a failed connection to the meeting.

Support for iOS 17

Released in 14.2.1.

Added support for iOS 17.

Support iPhone 15 series

Released in 14.2.1.

Added support for iPhone 15 series.

Jabber Dual VPN support

Released in 14.2.

Jabber is connecting using a dual VPN, tunneling inside another to services.

The admin should config key in Jabber config file.

Applies to Jabber for Android only.

EnableDualVPNSupport

• False (Default)—Jabber will disable dual VPN support

• True—Jabber will enable dual VPN support

Example: <EnableDualVPNSupport>True</EnableDualVPNSupport>

Support for new devices

Released in 14.2.

Jabber now supports these Android devices:

• Samsung Xcover6 Pro (Android 13)

• Samsung Galaxy A53 (Android 13 and later)

• Sharp AQUOS SH-M20 (Android 11)

Supported Android devices in 14.2

Support 'mailto:' link in custom tab

Released in Cisco Jabber 14.2.1.

Cisco Jabber can support 'mailto:' link in customer tab.

Support configuration keys 'SSO_Enabled' and 'OAuth_Enabled' in MDM configuration and URL provision

Released in Cisco Jabber 14.2.1.

Cisco Jabber can support'SSO_Enabled' and 'OAuth_Enabled' in MDM configuration and URL provision.

Support set the availability status changes to 'Away'

Released in Cisco Jabber 14.2.1.

The admin should config key in Jabber config file. It can support Cisco Jabber Android's availability status not changing to Away when users are inactive.

Set_Status_Away_On_Inactive

This configuration key previously applied to Cisco Jabber for Windows only.

From Jabber 14.2.1, it also applies to Cisco Jabber for Android.

Specifies if the availability status changes to Away when users are inactive.

• true (default)—Availability status changes to Away when users are inactive.

• false—Availability status does not change to Away when users are inactive.

Example:

<Set_Status_Away_On_Inactive>false</Set_Status_Away_On_Inactive>

iOS

• XCode 14.1 and iOS 16.1 SDK update

• Local Push Notification support

  • For end users:

    • A reliable and secure way to notify a Jabber user on iOS devices of incoming VoIP calls when iOS devices operate in a WiFi-constrained network; or when they have no Internet connection, and consequently don't have access to Apple Push Notification Service (APNs).

    • With Local Push Notifications framework (LPNs) on iOS, Jabber users receive calls directly from UCM by connecting to local WiFi network on the same Intranet.

  • For admins:

    • Admins must specify the supported WiFi list in jabber-config.xml file:

      Parameter	Description and values	Supported platforms
      LocalPushSSIDList	Specifies a whitelist of up to 10 Service Set IDs (SSIDs) separated by a semicolon. You must configure this parameter when the Local Push Notification Connectivity feature is enabled on CUCM. Example:<LocalPushSSIDList>SSID1;SSID2</LocalPushSSIDList>	iOS and iPadOS

      Note

      To get LPNs call notifications, users must grant the Local Network permission to the Jabber app. If both LPNs and APNs are configured on UCM, UCM will deliver the call via the LPNs channel first. If it fails due to any reason, APNs will be the fallback option with the best effort. To get LPNs call notifications working properly, when users have multiple iPhones or iPads, they must ensure the Jabber app runs only on one iPhone and one iPad. Supported UCM & DI version: 14 SU3 onwards. Supported iOS version: iOS 16.5 and iPadOS 16.5 onwards.

These clients follow a delayed release cycle. The clients release later than the corresponding releases of Jabber for Android and Jabber for iPhone and iPad.