[cisco-voip] Jabber Push Notifications for iPhone and iPad

[Brian Meade]

Yea, they are describing anything in the cloud as that way now even if they
aren't currently converged like Spark and WebEx.  It's specifically
fos-a.wbx2.com according to the document.

Word is they are adding an HTTP Proxy function to a future Expressway
release so you don't have to allow CUCM to have direct internet access.
Otherwise, you'll need your own web proxy.

On Thu, Apr 6, 2017 at 10:52 AM, Ryan Huff <ryanhuff at outlook.com> wrote:

> Anthony, I think it is. When you log into the Spark admin portal it calls
> itself "Cloud Collaboration Management Interface".
>
> I also think it is being used as a fluid moniker to describe all the
> things that are being added and changed (like how the WebEx and Spark
> backends are converging).
>
> Thanks,
>
> Ryan
>
> On Apr 6, 2017, at 10:45 AM, Anthony Holloway <
> avholloway+cisco-voip at gmail.com> wrote:
>
> Can someone confirm if "Collaboration Cloud" is in fact the Spark platform
> as a service?
>
> From the docs:
>
> *Cisco Communications Manager will need to register and stay connected to
> Cisco Collaboration Cloud.*
>
> On Thu, Apr 6, 2017 at 1:48 AM bertacco.alessandro at alice.it <
> bertacco.alessandro at alice.it> wrote:
>
>> Hi guys,
>>    I would discuss with you about the Apple iOS Phase1 and Phase2 and how
>> Apple are changing the notification behaviour that impact on Jabber for
>> iPhone and iPad.
>>
>> Here the Link: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/
>> cucm/im_presence/pushNotifications/11_5_1_su2/cucm_b_push-notification-
>> deployment-iPhone-iPad/cucm_b_push-notification-deployment-
>> for-apple_chapter_010.html
>>
>>
>> Here and Extract on what's is going on.
>>
>>
>> And a question for you, using Push notification at the end of Phase 2,
>> make jabber fully functional when in Background, or for voice call we need
>> to configure Single Number Reach? I don't understand that.
>>
>>
>> Regards
>>
>> Alessandro
>>
>>
>>
>> Important Notice
>>
>> In alignment with Apple's changes to the iOS notification architecture,
>> Cisco Jabber is in the process of implementing Apple Push Notification
>> support for notifications. We highly recommend that customers upgrade Cisco
>> Unified Communications Manager, IM and Presence Service, Cisco Expressway,
>> and Cisco Jabber before September 2017. Failure to upgrade in a timely
>> manner will result in loss of voice, video, and IM notifications for Jabber
>> iOS users.
>>
>> IOS Push Notification support for Cisco Jabber will be delivered in
>> phases. Phase 1 is for IM only, phase 2 adds push notification support for
>> voice and video calls.
>> Phase 1 Version Requirements
>>
>>    -
>>
>>    Cisco Unified Communications Manager and IM and Presence Service
>>    11.5(1)SU2, available Jan 23, 2017
>>
>>    -
>>
>>    Cisco Jabber 11.8.1, available Feb. 06, 2017
>>
>>    -
>>
>>    Cisco Expressway X8.9.1, available Jan. 30, 2017
>>
>>    -
>>
>>    Cisco Communications Manager to register and stay connected to Cisco
>>    Collaboration Cloud
>>
>>
>> What to Expect Next
>>
>> Phase 2 will complete the updates for Push Notifications for voice and
>> video calls in Jabber for iOS mid CY 2017. Upgrades to Cisco Unified
>> Communications Manager, IM and Presence Service, Cisco Jabber, and Cisco
>> Expressway will be required. Details around Phase 2 software versions will
>> be published as part of the Phase 2 availability announcement.
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170406/ce5565fe/attachment.html>