Cisco Issues Warning: Android 14 Update Disrupts Webex and Jabber Clients

The impact extends to various Cisco products, and the company has issued a field notice acknowledging the vulnerabilities in Webex and Jabber, highlighting their use in other related products such as Expressway, Unified Communication Manager (UCM), and Unified Presence Server.

The field notice from Cisco highlights that Google has implemented changes in how applications in background mode receive notifications for incoming calls and messages. This update could impact various Cisco products that utilize Webex and Jabber for messaging, including Expressway, Unified Communication Manager (UCM), and Unified Presence Server.

Google has implemented changes to how applications in background mode receive notifications for incoming calls and messages. Cisco’s field notice emphasizes that this modification may impact various products, including Webex and Jabber, which rely on these notifications for messaging functionality. As of August 31, the “VoIP socket deprecation” is expected to affect background notifications in Webex and Jabber, prompting users and administrators to be aware of and prepare for potential disruptions.

The API change introduced by Google, aimed at optimizing battery usage, involves terminating applications like Webex and Jabber when they enter background mode on Android. This termination prevents the server from delivering notifications to these apps. While the change is designed for better battery efficiency, it poses challenges for real-time communication applications that rely on background notifications for prompt message and call alerts. Users are advised to consider these implications when using Webex and Jabber after the specified date.

The API change in Android that impacts Webex and Jabber is a battery-saving measure, causing termination of these apps when they move to the background. This change has implications for the notification system and communication with unified communications systems, requiring users and organizations to adapt their workflows for effective communication.

The modification in Android’s API has consequences for users of the Webex and Jabber applications. Specifically, if a Webex Android client is registered to the Unified Communication Manager (UCM), it won’t be able to receive calls. Similarly, a Jabber Android client, registered to UCM for calling and UCM’s instant messenger and presence service, will be unable to receive both calls and messages. It’s essential for users to be aware of these limitations and potentially explore alternative communication methods or adjust their workflows accordingly.

The fixed software for affected versions implements a transition to leverage Firebase Cloud Messaging (FCM) push notifications as an alternative to the deprecated VoIP socket. This solution ensures that Webex and Jabber applications can maintain uninterrupted functionality and communication capabilities, particularly regarding background messages and notifications. Users are encouraged to apply these fixes promptly to mitigate any disruptions caused by the Android VoIP socket deprecation.

The updated software is accessible for all impacted products, with the exception of the Webex client for Android. Cisco has communicated that Firebase Cloud Messaging (FCM) support for the Webex Android client is planned for version 44.8, anticipated to be released in August 2024. Users are advised to monitor and install the relevant updates to ensure a seamless transition and continued functionality of Webex and associated services on Android devices.