Push Notifications Support in Release 11.5(1)SU2
Note |
If your deployment includes Cisco Jabber on iPhone and iPad clients, Cisco highly recommends that you upgrade to a minimum release of Cisco Unified Communications Manager 11.5(1)SU3 to receive full support for the Push Notifications solution with voice and video calling as well as high availability for instant messaging. |
If you are currently running Release 11.5(1)SU2 with Push Notifications and don't want to upgrade, Release 11.5(1)SU2 provides limited Push Notifications support for IM and Presence. Refer to the contents of this appendix for Push Notifications information that is relevant to your release.
Release 11.5(1)SU2 provides Push Notification support for IM and Presence (without High Availability
The following restrictions apply to the Push Notifications feature with Release 11.5(1)SU2:
-
High Availability for IM and Presence is not supported for Jabber on Cisco iPhone and iPad.
-
Voice call support—Cisco Jabber on iPhone and iPad clients cannot receive incoming voice calls when the Jabber client is in suspended mode. If you want to use Jabber on iPhone or iPad for calling, configure Single Number Reach.
Minimum Releases
IM and Presence support is provided for Push Notifications in Cisco Unified Communications Manager and IM and Presence Service Release 11.5(1)SU2 with the following minimum compatible releases:
-
Cisco Prime License Manager 11.5(1)SU2 in a co-resident deployment or 11.5.1SU1 (Build11.5.1.10000-4) in a standalone deployment.
-
Cisco Jabber 11.8.1
-
Cisco Expressway x8.9 (if MRA is deployed)
Terminated Push Notifications for Service Shutdowns
Note |
Terminated Push Notifications are included with Release 11.5(1)SU2 only. The Push Notifications High Availability feature introduced with 11.5(1)SU3 replaces Terminated Push Notifications. |
When a Cisco Jabber for iPhone and iPad client begins running in the background, the IM and Presence Service queues all instant messages, Presence updates, and other XMPP stanzas (for example, chat room invites) on the local server. Only when the Jabber user clicks on an IM notification, or moves the client back to the foreground, does the IM and Presence Service send all queued messages to the Jabber client.
If the Cisco XCP router stops or is restarted (for example, an administrator restarts the service for a configuration change or upgrade), the IM and Presence Service flushes out the message queue resulting in all queued messages being lost.
However, before the service shuts down, the IM and Presence Service sends a terminated push notification to Cisco Jabber for iPhone and iPad clients notifying them that the service is shutting down and that all queued messages are lost. The Jabber user must move the client back to the foreground to create a new session so that Push Notifications are enabled in this new session.
Failover Situations
If a node fails suddenly, no terminated push notification gets sent and all instant messages, Presence updates, and XMPP stanzas that were queued on the failed node are lost. If High Availability is configured for IM and Presence, the backup node in the Presence Redundancy Group takes over, but the queue on the failed node is still lost. When the backup node takes over, it sends an iOS system notification to the user and the user must click the notification to bring Jabber back to the foreground and create a new session. Push Notifications is not enabled until the new session is created.
Note |
Cisco recommends that you configure High Availability for the IM and Presence Service so that your deployment has redundancy. For configuration details, see the Configuration and Administration Guide for IM and Presence Service. |