Jabber Unified Communications Solution
Product Specifications
- Compatibility: iOS 12 and above, supported Android devices
- Channels: ‘VoIP’ channel for voice calls, ‘Message’ channel for
messages - Integration: Unified Communications Manager and IM and Presence
Service
Product Usage Instructions
Overview of Push Notifications
The product utilizes Push Notifications to deliver voice calls
and messages to users on iOS 12 and above, as well as supported
Android devices. The system distinguishes between voice calls
(‘VoIP’ channel) and messages (‘Message’ channel) for efficient
delivery.
Configuration Steps
- Ensure the Cisco Jabber or Cisco Webex client is registered to
Unified Communications Manager and the IM and Presence
Service. - Configure Push Notifications settings based on the device’s
operating system (iOS 12 or iOS 13/Android). - Understand the behavior differences between iOS 12 and iOS 13
for handling voice calls and messages.
Push Notifications Behavior
iOS 12 Behavior:
- Voice and video calls are sent directly using the standard SIP
channel. - Messages are delivered through the standard SIP communication
channel without Push Notifications.
iOS 13/Android Behavior:
- Voice or video calls use separate Push Notifications channels
(‘VoIP’ channel). - Messages are sent through the ‘Message’ channel.
- Clients automatically re-enter foreground mode upon receiving
notifications for calls or messages.
Frequently Asked Questions (FAQ)
Q: What happens if a client is in suspended mode (background
mode) during a call?
A: With iOS 13, call traffic is split into
separate Push Notifications channels, ensuring the call continues
smoothly even when the standard communication channel is
unavailable. The client receives notifications and re-enters
foreground mode automatically.
Q: How are messages handled when the client is running in
foreground mode?
A: Messages in foreground mode are directly
sent using the standard SIP communication channel without
additional Push Notifications.
Q: Does the system differentiate between voice calls and
messages for notification delivery?
A: Yes, the system uses distinct ‘VoIP’ and
‘Message’ channels to efficiently deliver voice calls and messages
to clients based on their operating system version.
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, Unified Communications Manager 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 feature.
How Push Notifications Work At startup, clients that are installed on Android and iOS platform devices register to Unified Communications Manager, the IM and Presence Service and to the Google and Apple cloud. With Mobile and Remote Access 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,Unified Communications Manager 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 Unified Communications Manager and IM and Presence Service from communicating directly with the clients. Push Notifications provides another channel to reach the clients through the partner clouds.
Note 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
Configure Push Notifications 1
Push Notifications Overview Figure 1: Push Notifications Architecture
Configure Push Notifications
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 Mobile and Remote Access 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.
Note 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.
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 Unified Communications Manager and the IM and Presence Service.
Configure Push Notifications 2
Configure Push Notifications
Push Notifications Overview
Cisco Jabber or Cisco Webex client is running in…
Cisco Jabber is running on an iOS12 Device Cisco Jabber is running on an iOS13 Device or Android Device
Foreground Mode
Voice and Video Calls
The behaviour is the same as with iOS12.
Unified Communications Manager sends voice and video calls to Cisco Jabber or Cisco Webex clients directly using the standard SIP communications channel.
For calls, Unified Communications Manager 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.
Configure Push Notifications 3
Push Notifications Overview
Configure Push Notifications
Cisco Jabber or Cisco Webex client is running in…
Cisco Jabber is running on an iOS12 Device Cisco Jabber is running on an iOS13 Device or Android Device
Suspended Mode (Background mode)
Voice or Video Calls
With iOS13, call traffic and message traffic
Standard communication channel is unavailable. Unified CM uses the Push Notifications channel.
is split into separate Push Notifications channels: a ‘VoIP’ channel for calls, and a “Message” channel for messaging.
Upon receiving the notification, the Cisco Voice or Video Calls
Jabber or Cisco Webex client re-enters
Standard communication channel is
foreground mode automatically, and the client unavailable. Unified CM uses Push
rings.
Notifications ‘VoIP’ channel.
Messaging
Upon receiving the VoIP notification, Jabber
Standard communication channel is
launches CallKit with Caller ID.
unavailable. IM and Presence Service uses This behavior holds for Cisco Jabber or Cisco
the Push Notifications channel to send IM Webex iOS clients.
notifications as follows:
Messaging
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.
Standard communication channel is unavailable. IM and Presence Service uses Push Notifications ‘Message’ channel.
2.
The Apple cloud pushes the IM
1.
notification to the Cisco Jabber or Cisco
Webex client and a notification appears
on the Cisco Jabber or Cisco Webex
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.
client.
2. The Apple cloud pushes the IM
3. When the user clicks the notification, the Cisco Jabber or Cisco Webex client
notification to the Cisco Jabber or Cisco Webex client.
moves back the foreground. The Cisco 3. When the user clicks the notification,
Jabber or Cisco Webex client resumes
Cisco Jabber or Cisco Webex client
the session with the IM and Presence
moves to foreground mode. Cisco Jabber
Service and downloads the instant
or Cisco Webex client resumes the
message.
session with the IM and Presence Service
and downloads the message.
Note
While the Cisco Jabber or Cisco Webex client is in suspended mode, the user’s Presence status displays as Away.
Note While Cisco Jabber or Cisco Webex client is in suspended mode, the user Presence
displays as Away.
Supported Clients for Push Notifications
Client
OS
Cisco Jabber on iPhone iOS and iPad
Cisco Jabber on Android Android
Webex on iOS
iOS
Platform Cloud Apple
Google Apple
Cloud Service
Apple Push Notification Service (APNS)
Android PNS Service
Apple Push Notification Service (APNS)
Configure Push Notifications 4
Configure Push Notifications
Push Notifications Configuration
Client Webex on Android
OS Android
Platform Cloud Google
Cloud Service Android PNS Service
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 5
Push Notifications Configuration
Configure Push Notifications
Configure Push Notifications 6
Documents / Resources
 |
CISCO Jabber Unified Communications Solution [pdf] User Guide Jabber Unified Communications Solution, Jabber, Unified Communications Solution, Communications Solution |