Jabber for Iphone Push Notifications to an unregistered device.

[Marcelo Bergamini]

Hi all!

          I would like to know if some of you faced this behavior:

                    Jabber for Iphone out of the company. VPN not connected. No access to enterprise network.

                    APN notifications enable for CUCM cluster.

                   When there is an incoming call, the user of this Iphone still receives the call notification, which drops when answered.

                   We see it in the DOC:

"Stopping Push Notifications"

"If you want to stop Push Notifications from being delivered to your device, log out of the Cisco Jabber or Webex application".

                  Do you know if this is really normal behavior and if there is a way to avoid notifications for unregistered devices, without deactivating the APN?

                  Best regards!

[Jonas Fraga]

Hello, Marcelo.

If Jabber/Webex are registered to CUCM (no matter if through VPN, Internal or MRA) so the APN will be in action and notifies device about calls.

If device are not registered it should not send APN notification because CUCM will understand a unregistered device and then goes through regular routing process (CFUNREGISTERED, return Disconnect Cause 1, so on).

In your case we're talking about a registered or not registered device?

[Marcelo Bergamini]

Hello Jonas!

Even the device unregistered, the notification is sent.

But checking the documentation again, I believe  this is normal. When the APP is in the background or when it is not registered, the SIP channel between Jabber and Callmanager is interrupted. Hence notification is required for it to try to re-register.

If you are in the background, the call works normally.. If you are unregistered, the call is dropped.

See the images attached.

The solution is to logout...

Regards!

[Roger Kallberg]

If you logout from the Jabber app on the mobile device you should not get any notifications.

[Marcelo Bergamini]

Hello Roger!

The customer would be happy with another solution ... but I believe the logout is the only way.

Regards!

[Adam Pawlowski]

The client has a user setting to tell it to sign out after a period of time, but I feel pretty confident in saying this won't work with the application backgrounded, but I'll try it myself to see if it works. I believe your assessment of how APNs operate is otherwise correct, that channel is independent from the SiP channel.

[Adam Pawlowski]

Setting the client to sign out after a timer only works if the client is awake to sign out, otherwise the push notifications continue. I’m then eventually prompted to sign back in resuming the client. 

I’m not sure if a MRA policy will impact this but based on what I know about Jabber architecture it will not. Sign out before leaving premise or deploy MRA are the two options other than breaking APNs which will be a suboptimal experience.

[Roger Kallberg]

AFAIK this is the solution, there are no other options. Other than not having push notifications not setup at all, but that's not really a feasible option IMO.

[Sergio Quezada]

Hello Guys,

    Have you all had a look at this Bug?

Jabber for iPhone Push Notifications Interactions and Restrictions
CSCvq76467

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvq76467/?rfs=iqvred

Voice Call Apple Push notifications not consistent because of iOS limitation

CSCvm80565

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvm80565/?rfs=iqvred 

Release Notes for Cisco Jabber for iPhone and iPad 12.8

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_8/jabi_b_release-notes-128.html#JABI_RF_L12E92EA_00

[Roger Kallberg]

Absolutely interesting information, but as far as I can tell off topic to the OP question.