VoIPModeandApplePushNotificationServiceUpdatesiniOS13
FirstPublished:May7,2020
Description
IniOS13,Applehasmadeupdatestothewayapplicationsinbackgroundmodearenotifiedofingcallsandmessages,inordertopreservebatterylife.ThischangewillimpactusersofCiscoJabberandWebexTeams.TomakesurethatyoursystemsupportstheApplePushNotificationservice(APNs),youmustupgradeyoursystemtoasupportedreleasebytheprescribeddatesandenableAPNs.
Background
HowApplePushNotificationServiceWorks
WhileCiscoJabberiOSclientsareoperatinginforegroundmode,JabbermaintainsapersistentconnectiontoCiscoUnifiedCommunicationsManager.However,whentheJabberclientmovesintobackgroundmode(thisursafteranintervalwhereJabberisnotinteractedwithdirectly),iOSterminatesJabber,preventingCiscoUnifiedCommunicationsManagerfromcontactingJabberdirectly.ThishelpspreservebatterylifeonAppledevices.
TheApplePushNotificationserviceprovidesanalternativechanneltoclientsthatareinbackgroundmode.WhenCiscoUnifiedCommunicationsManagerreceivesaningcallforaclientthatisinbackgroundmode,UnifiedCMcontactsthecloud-basedApplePushNotificationservice,whichmaintainsaconnectiontotheiOSdevice.TheApplePushNotificationservicesendsapushnotificationtothedeviceonwhichJabberisinstalled.Uponreceivingthepushnotification,Jabberre-entersforegroundmode,reconnectstoCiscoUnifiedCommunicationsManager,andreceivestheingcall.
ThefollowingsectionsdescribeupdatestotheApplePushNotificationserviceandhowCiscoproductswillbeaffected.
1.LegacyVoIPModeisnolongersupportedforCiscoJabberafterAugust1,2020 JabberoniOSwillnolongerbeabletoleveragelegacyVoIPsocketsandAPIstoreceivecallsandmessagesfromCiscoUnifiedCommunicationsManager(UCM)andCiscoUnifiedCommunicationsManagerIMandPresenceService. ThedeprecationofthelegacyVoIPsocketsimpactsJabberfunctionalitygoingforward.IfanizationusesCiscoJabberregisteredtoUnifiedCMforcallingandIMandPresenceServiceformessaging,Jabberwillbeunabletoreceivecallsormessageswhilerunninginbackgroundmode,untilAPNsisenabled. 2.iOS13SDKChangesforApplePushNotificationserviceforJabberandWebexTeamsafterApril1,2021 WithiOS13,ApplehaschangedthewaythatPushNotificationsaredeliveredtoVoIPapps.ThisimpactsthewaythatWebexTeamsandJabberreceivecallsandthewaythatJabberreceivesmessages. CiscoSystems,Inc.
1 LegacyVoIPModeandApplePushNotificationServiceUpdatesiniOS13ProblemSymptom ApplenowrequiresthatallVoIPpushnotificationsinvokeCallKitimmediately.IfaVoIPpushnotificationisnotreportedtoCallKitwithinadesignatedperiod,iOSterminatestheapplication.IftheJabberorWebexTeamclientapplicationfailstoinvokeCallKitrepeatedly,thenApplewilldeliveringpushnotificationstotheapplication. JabberandWebexTeamsoniOS13willinvokeCallKitwhenaVoIPnotificationisreceived.CallKitdisplayscallerIDas“Unknowncaller”.WhentheclientreregistersandreceivestheSIPINVITE,CallKitreplaces“Unknowncaller”withtheactualcallerID.ThetimeittakestoreflecttheactualcallerIDdependsonthequalityoftheconnectionbetweentheclientandUnifiedCM. WiththeiOS13SDK,Applealsorequiresthatnon-VoIPpushnotifications,likemessages,can’tusetheVoIPchannelfordelivery.Messagesmustbedeliveredthroughthemessagingchannel.Ifnon-VoIPservicescontinuetouseVoIPchannelsforpushnotifications,butfailtoreportnotificationstoCallKit,theniOSwillterminatetheapplication.Ifanapplicationdoesn’tinvokeCallKitrepeatedly,thenApplesdeliveringpushnotificationstotheapplicationaltogether. ProblemSymptom
1.LegacyVoIPModeisnolongersupportedforCiscoJabberafterAugust1,2020 •CiscoJabberiOSclientapplicationwillbeunabletoreceivecallsormessageswhilerunninginbackgroundmodeuntilAPNsisenabled. 2.iOS13changestheApplePushNotificationserviceforCiscoJabberandWebexTeamsafterApril1,2021 •Ciscoclients,CiscoJabberorWebexTeams,runningoniOS13willgetavoicecallnotificationthatwouldshowtheCallKitwithcalleridas“UnknownCaller”. •TheCiscoclientmaybeterminated,andApplewilldeliveringvoiceandmessagingpushnotifications. Workaround/Solution CiscohasdevelopedasolutionthatmeetsApplePushNotificationrequirements.CiscostronglymendsthatyouupgradeyourUCinfrastructuretoasupportedreleasepriortotheprescribeddatesandenableAPNs. RefertothefollowingtableformendedinfrastructuremigrationscheduletoeasethetransitiontotheAPNsupdates. NOTE:APNsissupportedwithboth11.5and12.5versionsofUnifiedCM.Theupgrademendationsdifferdependingonwhetheryouplantorunan11.5or12.5versionofUnifiedCM. Table1.mendedAPNsMigrationSchedule Ifyouarerunning…ByAugust1,2020,dothis… CiscoUnifiedCommunicationsManagerandIMandPresenceService 11.5
(1)SU8or EnableAPNs higher ByApril1,2021,dothis… Ifyouwant11.5,nothingrequiredIfyouwant12.5,upgradeto12.5
(1)SU3orhigher 11.5
(1)SU4-SU7EnableAPNs Ifyouwant11.5,upgradeto11.5
(1)SU8orhigher Ifyouwant12.5,upgradeto12.5
(1)SU3orhigher
2 LegacyVoIPModeandApplePushNotificationServiceUpdatesiniOS13AdditionalInformation Ifyouarerunning…11.5
(1)SU3orearlier ByAugust1,2020,dothis…Ifyouwant11.5,upgradeto11.5
(1)SU7(minimum)or11.5
(1)SU8(mended)andthenenableAPNS: Ifyouwant12.5,upgradeto12.5
(1)SU2orhigherandthenenableAPNs ByApril1,2021,dothis…Ifyouwant11.5,upgradeto11.5
(1)SU8orhigher Ifyouwant12.5,upgradeto12.5
(1)SU3orhigher CiscoExpressway NOTE:ExpresswayupgradesaremandatoryONLYifthedeploymentincludestheIMandPresenceService. X8.10.1orhigherNothingrequired UpgradetoExpresswayX12.6orhigher X.8.10orearlier WithUnifiedCM11.5,upgradetoExpresswayX8.10.1orhigher UpgradetoExpresswayX12.6orhigher WithUnifiedCM12.5,upgradetoExpresswayX12.5orhigher(X12.6ismended) CiscoJabber11.9 WithUnifiedCM11.5,upgradetoJabber12.8orhighermended(butnotmandatory) UpgradetoJabber12.9orhigher WithUnifiedCM12.5,upgradetoJabber12.8orhigher 11.8orlower UpgradetoJabber12.8orhigher UpgradetoJabber12.9orhigher CiscoWebexclients WebexTeams Nothingrequired UpgradetolatestversionofWebexTeamsapp NOTE:RefertoTable2forinformationonreleasetimelines ForinformationonhowtoupgradeUnifiedCM,refertothelatestUpgradeandMigrationGuideat:/c/en/us/td/docs/voice_m/cucm/upgrade/12_5_1/cucm_b_upgrade-migration-guide125x.html. ForinformationonhowtoenableandconfigureAPNs,refertothePushNotificationsDeploymentGuideat/c/en/us/td/docs/voice_m/cucm/push_notifications/cucm_b_push-notificationsdeployment-guide.html. Additional
Information Table2.ReleaseTimelineforAPNsiOS13SupportedVersions UCApplication mendedVersion CiscoUnifiedCommunicationsManagerandIMandPresenceService CiscoExpressway* CiscoJabber 11.5
(1)SU812.5
(1)SU3X12.612.9 ReleaseTimeline(Datesaresubjecttochange)May31,2020July31,2020 May31,2020June25,2020
3 LegacyVoIPModeandApplePushNotificationServiceUpdatesiniOS13ForMoreInformation UCApplication mendedVersion ReleaseTimeline(Datesaresubjecttochange) CiscoWebexTeamsCiscoWebexCallingApp NotApplicable July31,2020 *CiscoExpresswayupgradeisrequiredONLYifthedeploymentincludestheIMandPresenceService. ForMoreInformation Ifyourequirefurtherassistance,orifyouhaveanyfurtherquestionsregardingthisfieldnotice,pleasecontacttheCiscoSystemsTechnicalAssistanceCenter(TAC)byoneofthefollowingmethods: •Openaservicerequeston •Byemail •Bytelephone ReceiveEmailNotificationforNewFieldNotices: •MyNotifications—Setupaprofiletoreceiveemailupdatesaboutreliability,safety,worksecurity,andend-ofsaleissuesfortheCiscoproductsyouspecify.
4
1.LegacyVoIPModeisnolongersupportedforCiscoJabberafterAugust1,2020 JabberoniOSwillnolongerbeabletoleveragelegacyVoIPsocketsandAPIstoreceivecallsandmessagesfromCiscoUnifiedCommunicationsManager(UCM)andCiscoUnifiedCommunicationsManagerIMandPresenceService. ThedeprecationofthelegacyVoIPsocketsimpactsJabberfunctionalitygoingforward.IfanizationusesCiscoJabberregisteredtoUnifiedCMforcallingandIMandPresenceServiceformessaging,Jabberwillbeunabletoreceivecallsormessageswhilerunninginbackgroundmode,untilAPNsisenabled. 2.iOS13SDKChangesforApplePushNotificationserviceforJabberandWebexTeamsafterApril1,2021 WithiOS13,ApplehaschangedthewaythatPushNotificationsaredeliveredtoVoIPapps.ThisimpactsthewaythatWebexTeamsandJabberreceivecallsandthewaythatJabberreceivesmessages. CiscoSystems,Inc.
1 LegacyVoIPModeandApplePushNotificationServiceUpdatesiniOS13ProblemSymptom ApplenowrequiresthatallVoIPpushnotificationsinvokeCallKitimmediately.IfaVoIPpushnotificationisnotreportedtoCallKitwithinadesignatedperiod,iOSterminatestheapplication.IftheJabberorWebexTeamclientapplicationfailstoinvokeCallKitrepeatedly,thenApplewilldeliveringpushnotificationstotheapplication. JabberandWebexTeamsoniOS13willinvokeCallKitwhenaVoIPnotificationisreceived.CallKitdisplayscallerIDas“Unknowncaller”.WhentheclientreregistersandreceivestheSIPINVITE,CallKitreplaces“Unknowncaller”withtheactualcallerID.ThetimeittakestoreflecttheactualcallerIDdependsonthequalityoftheconnectionbetweentheclientandUnifiedCM. WiththeiOS13SDK,Applealsorequiresthatnon-VoIPpushnotifications,likemessages,can’tusetheVoIPchannelfordelivery.Messagesmustbedeliveredthroughthemessagingchannel.Ifnon-VoIPservicescontinuetouseVoIPchannelsforpushnotifications,butfailtoreportnotificationstoCallKit,theniOSwillterminatetheapplication.Ifanapplicationdoesn’tinvokeCallKitrepeatedly,thenApplesdeliveringpushnotificationstotheapplicationaltogether. ProblemSymptom
1.LegacyVoIPModeisnolongersupportedforCiscoJabberafterAugust1,2020 •CiscoJabberiOSclientapplicationwillbeunabletoreceivecallsormessageswhilerunninginbackgroundmodeuntilAPNsisenabled. 2.iOS13changestheApplePushNotificationserviceforCiscoJabberandWebexTeamsafterApril1,2021 •Ciscoclients,CiscoJabberorWebexTeams,runningoniOS13willgetavoicecallnotificationthatwouldshowtheCallKitwithcalleridas“UnknownCaller”. •TheCiscoclientmaybeterminated,andApplewilldeliveringvoiceandmessagingpushnotifications. Workaround/Solution CiscohasdevelopedasolutionthatmeetsApplePushNotificationrequirements.CiscostronglymendsthatyouupgradeyourUCinfrastructuretoasupportedreleasepriortotheprescribeddatesandenableAPNs. RefertothefollowingtableformendedinfrastructuremigrationscheduletoeasethetransitiontotheAPNsupdates. NOTE:APNsissupportedwithboth11.5and12.5versionsofUnifiedCM.Theupgrademendationsdifferdependingonwhetheryouplantorunan11.5or12.5versionofUnifiedCM. Table1.mendedAPNsMigrationSchedule Ifyouarerunning…ByAugust1,2020,dothis… CiscoUnifiedCommunicationsManagerandIMandPresenceService 11.5
(1)SU8or EnableAPNs higher ByApril1,2021,dothis… Ifyouwant11.5,nothingrequiredIfyouwant12.5,upgradeto12.5
(1)SU3orhigher 11.5
(1)SU4-SU7EnableAPNs Ifyouwant11.5,upgradeto11.5
(1)SU8orhigher Ifyouwant12.5,upgradeto12.5
(1)SU3orhigher
2 LegacyVoIPModeandApplePushNotificationServiceUpdatesiniOS13AdditionalInformation Ifyouarerunning…11.5
(1)SU3orearlier ByAugust1,2020,dothis…Ifyouwant11.5,upgradeto11.5
(1)SU7(minimum)or11.5
(1)SU8(mended)andthenenableAPNS: Ifyouwant12.5,upgradeto12.5
(1)SU2orhigherandthenenableAPNs ByApril1,2021,dothis…Ifyouwant11.5,upgradeto11.5
(1)SU8orhigher Ifyouwant12.5,upgradeto12.5
(1)SU3orhigher CiscoExpressway NOTE:ExpresswayupgradesaremandatoryONLYifthedeploymentincludestheIMandPresenceService. X8.10.1orhigherNothingrequired UpgradetoExpresswayX12.6orhigher X.8.10orearlier WithUnifiedCM11.5,upgradetoExpresswayX8.10.1orhigher UpgradetoExpresswayX12.6orhigher WithUnifiedCM12.5,upgradetoExpresswayX12.5orhigher(X12.6ismended) CiscoJabber11.9 WithUnifiedCM11.5,upgradetoJabber12.8orhighermended(butnotmandatory) UpgradetoJabber12.9orhigher WithUnifiedCM12.5,upgradetoJabber12.8orhigher 11.8orlower UpgradetoJabber12.8orhigher UpgradetoJabber12.9orhigher CiscoWebexclients WebexTeams Nothingrequired UpgradetolatestversionofWebexTeamsapp NOTE:RefertoTable2forinformationonreleasetimelines ForinformationonhowtoupgradeUnifiedCM,refertothelatestUpgradeandMigrationGuideat:/c/en/us/td/docs/voice_m/cucm/upgrade/12_5_1/cucm_b_upgrade-migration-guide125x.html. ForinformationonhowtoenableandconfigureAPNs,refertothePushNotificationsDeploymentGuideat/c/en/us/td/docs/voice_m/cucm/push_notifications/cucm_b_push-notificationsdeployment-guide.html. Additional
Information Table2.ReleaseTimelineforAPNsiOS13SupportedVersions UCApplication mendedVersion CiscoUnifiedCommunicationsManagerandIMandPresenceService CiscoExpressway* CiscoJabber 11.5
(1)SU812.5
(1)SU3X12.612.9 ReleaseTimeline(Datesaresubjecttochange)May31,2020July31,2020 May31,2020June25,2020
3 LegacyVoIPModeandApplePushNotificationServiceUpdatesiniOS13ForMoreInformation UCApplication mendedVersion ReleaseTimeline(Datesaresubjecttochange) CiscoWebexTeamsCiscoWebexCallingApp NotApplicable July31,2020 *CiscoExpresswayupgradeisrequiredONLYifthedeploymentincludestheIMandPresenceService. ForMoreInformation Ifyourequirefurtherassistance,orifyouhaveanyfurtherquestionsregardingthisfieldnotice,pleasecontacttheCiscoSystemsTechnicalAssistanceCenter(TAC)byoneofthefollowingmethods: •Openaservicerequeston •Byemail •Bytelephone ReceiveEmailNotificationforNewFieldNotices: •MyNotifications—Setupaprofiletoreceiveemailupdatesaboutreliability,safety,worksecurity,andend-ofsaleissuesfortheCiscoproductsyouspecify.
4
声明：
该资讯来自于互联网网友发布，如有侵犯您的权益请联系我们。