Apple is scheduled to introduce in its next major iOS release (after iOS 10 anticipated September 2017), a significant change that removes APIs that are required for handling calls and IM’s when the application is running in the background. What this means is that if Jabber is not opened in the foreground, the user will not be notified of incoming calls and IM messages.
So what is getting removed from iOS 11:
The SetKeepAliveTimeout:handler: which is used by VoIP apps to wake up and check VoIP connections as well as (Jabber in particular) to send keep-alive messages to UC servers and WebEx will no longer be supported.
The VoIP Socket will also be removed from iOS 11. This socket is monitored by the system while VoIP apps are running in the background. The reason why Apple is set to remove the VoIP Socket is because it is resource intense and battery consuming. Jabber uses two VoIP sockets (SIP and XMPP).
Cisco’s response to Apple’s changes:
Cisco will be introducing Cisco Jabber support for APNs (Apple Push Notification service) which includes PushKit-based notifications.
Push Notifications for IM (supported versions and configuration requirements):
- Support includes upgrades of the Cisco Unified Communications Manager and Presence (CUCM and IM&P) to version 11.5 SU2.
- Cisco Expressway to version 8.9.
- Cisco Jabber for iOS to version 11.8.
- There will also be a new Jabber client version following the release of 11.8 coming out in the first half of 2017, which will have fast login support to improve Jabber start-up time once the initial configuration is complete.
- Requirements are also for port 443 to be opened on the corporate firewall, as it is used to secure push notifications. Also, it allows corporate users to save Jabber login credentials, which eliminates the need for users to log-in when Jabber is launched.
Push Notifications for Voice/Video (supported versions and configuration requirements):
- Support will be introduced within Cisco Unified Communications Manager and Presence (CUCM and IM&P) version 11.5 SU3. Unfortunately, with regards Cisco Expressway MRA and Cisco Jabber for iOS, we still do not know the exact versions that will have support for this feature.
- For Voice calls to work in the meantime (until push notifications support for Voice/Video is released), enabling SNR for mobile calls on your Cisco Unified Communications Manager server will be the workaround.
Design differences from before and after iOS 10:
Jabber in Foreground, notifications not needed, no changes:
Jabber in the Background – iOS 10 and earlier:
Jabber in the Background – iOS 11 with API change:
The Stack8 team are experts with Cisco Jabber. If you have any questions about Apple push notifications for your Cisco unified communication applications, please don’t hesitate to contact us at Stack8
Other Blogs You Might Enjoy
Ready to take your unified communications from headache to hassle-free?
No throwing darts at proposals or contracts. No battling through the back-end. No nonsense, no run-around.