Configure Push Notifications

• Push Notifications Overview, on page 1

• Push Notifications Configuration, on page 5

Push Notifications Overview

When your cluster is enabled for Push Notifications, and the IM and Presence Service use Google and Apple’s

cloud-based Push Notification service to push notifications for voice and video calls, instant message notification

to Cisco Jabber or Cisco Webex on Android and iOS clients that are running in suspended mode (also known

as background mode). Push Notifications allows your system to maintain a persistent communication with

Cisco Jabber or Cisco Webex. Push Notifications is required both for Cisco Jabber and Cisco Webex on

Android and iOS clients that connect from within the enterprise network, and for clients that register to an

on-premise deployment through Expressway's Mobile and Remote Access (MRA) feature.

How Push Notifications Work

At startup, clients that are installed on Android and iOS platform devices register to , the IM and Presence

Service and to the Google and Apple cloud. With MRA deployments, the clients registers to the on-premises

servers through Expressway. So as long as the Cisco Jabber and Cisco Webex client remains in foreground

mode, and the IM and Presence Service can send calls and instant messages to the clients directly.

However, once the Cisco Jabber or Cisco Webex clients moves to suspended mode (for example, to maintain

battery life), the standard communication channel is unavailable, preventing and IM and Presence Service

from communicating directly with the clients. Push Notifications provides another channel to reach the clients

through the partner clouds.

Cisco Jabber and Cisco Webex is considered to be running in suspended mode if any of the following conditions

are true:

• the Cisco Jabber or Cisco Webex application is running off-screen (in the background)

• the Android or iOS device is locked

• the Android or iOS device screen is turned off

Note

Configure Push Notifications

Figure 1: Push Notifications Architecture

The above diagram displays what happens when Cisco Jabber or Cisco Webex for Android and iOS clients

run in the background or are stopped. The figure illustrates: (1) an MRA deployment where the clients that

connects with an on-premises Cisco Unified Communications Manager and IM and Presence Service

deployment through Expressway, and (2) a Cisco Jabber or Cisco Webex for Android and iOS clients that

connects directly to the on-premises deployment from within the enterprise network.

As of iOS13 for Apple clients and supported Android clients, voice calls and messages use separate Push

Notifications channels ('VoIP' and 'Message') to reach a client that is running in background mode. However,

the general flow is the same for both channels. With iOS 12, voice calls and messages are delivered using the

same channel.

Note

Push Notifications Behavior for Cisco Jabber and Cisco Webex

The following table describes the behavior under iOS 12 and iOS 13 for Cisco Jabber or Cisco Webex iOS

clients that are registered to and the IM and Presence Service.

Configure Push Notifications

Push Notifications Overview

Cisco Jabber is running on an iOS13 Device

or Android Device

Cisco Jabber is running on an iOS12 DeviceCisco Jabber or Cisco

Webex client is running

in...

The behaviour is the same as with iOS12.Voice and Video Calls

sends voice and video calls to Cisco Jabber

or Cisco Webex clients directly using the

standard SIP communications channel.

For calls, also sends Push Notifications to

Cisco Jabber or Cisco Webex clients that are

in foreground mode. However, the standard

SIP channel gets used to establish the call,

rather than the Push Notifications channel.

Messages

The IM and Presence Service sends messages

to the client directly using the standard SIP

communication channel. For messages, Push

Notifications are not sent to clients that are

in foreground mode.

Foreground Mode

Configure Push Notifications

Push Notifications Overview

Cisco Jabber is running on an iOS13 Device

or Android Device

Cisco Jabber is running on an iOS12 DeviceCisco Jabber or Cisco

Webex client is running

in...

With iOS13, call traffic and message traffic

is split into separate Push Notifications

channels: a 'VoIP' channel for calls, and a

"Message" channel for messaging.

Voice or Video Calls

Standard communication channel is

unavailable. Unified CM uses Push

Notifications 'VoIP' channel.

Upon receiving the VoIP notification, Jabber

launches CallKit with Caller ID.

This behavior holds for Cisco Jabber or Cisco

Webex iOS clients.

Messaging

Standard communication channel is

unavailable. IM and Presence Service uses

Push Notifications 'Message' channel.

1. IM and Presence Service sends the IM

notification to the Push REST service in

the Cisco cloud, which forwards the

notification to the Apple cloud.

2. The Apple cloud pushes the IM

notification to the Cisco Jabber or Cisco

Webex client.

3. When the user clicks the notification,

Cisco Jabber or Cisco Webex client

moves to foreground mode. Cisco Jabber

or Cisco Webex client resumes the

session with the IM and Presence Service

and downloads the message.

While Cisco Jabber or Cisco

Webex client is in suspended

mode, the user Presence displays

as Away.

Note

Voice or Video Calls

Standard communication channel is

unavailable. Unified CM uses the Push

Notifications channel.

Upon receiving the notification, the Cisco

Jabber or Cisco Webex client re-enters

foreground mode automatically, and the client

rings.

Messaging

Standard communication channel is

unavailable. IM and Presence Service uses

the Push Notifications channel to send IM

notifications as follows:

1. IM and Presence Service sends the IM

notification to the Push REST service in

the Cisco cloud, which forwards the

notification to the Apple cloud.

2. The Apple cloud pushes the IM

notification to the Cisco Jabber or Cisco

Webex client and a notification appears

on the Cisco Jabber or Cisco Webex

client.

3. When the user clicks the notification, the

Cisco Jabber or Cisco Webex client

moves back the foreground. The Cisco

Jabber or Cisco Webex client resumes

the session with the IM and Presence

Service and downloads the instant

message.

While the Cisco Jabber or Cisco

Webex client is in suspended

mode, the user's Presence status

displays as Away.

Note

Suspended Mode

(Background mode)

Supported Clients for Push Notifications

Cloud ServicePlatform CloudOSClient

Apple Push Notification

Service (APNS)

AppleiOSCisco Jabber on iPhone

and iPad

Android PNS ServiceGoogleAndroidCisco Jabber on Android

Apple Push Notification

Service (APNS)

AppleiOSWebex on iOS

Configure Push Notifications

Push Notifications Overview

Cloud ServicePlatform CloudOSClient

Android PNS ServiceGoogleAndroidWebex on Android

Push Notifications Configuration

For details on how to configure and deploy Push Notifications, refer to Deploying Push Notifications for Cisco

Jabber on iPhone and iPad at https://www.cisco.com/c/en/us/support/unified-communications/

unified-communications-manager-callmanager/products-installation-and-configuration-guides-list.html.

Configure Push Notifications

Push Notifications Configuration

Configure Push Notifications

Push Notifications Configuration