Regarding : IPhone ‘not registered’?

[eska]

Hi,

This is sort of a follow up to this post : IPhone ‘not registered’ | 3CX Forums

Have there been any changes made within the registration timeout for push notification service? Or is this still in debate?

We continue to have problems with iPhone that are unregistered after a week of not being used.

Thanks!

 

[Vali_3CX]

@eska
No changes on this - bottom line, the same condition: at least one connection per week, no matter if by simply launch and exit the client, having an incoming call, quick reply or mark as read chat notification, or via background refresh. Once per week is a must.

 

[SteveITS]

For most normal cases this is likely not a problem, however one such case is an emergency/after-hours extension which will therefore not ring if it is not used for a while and drops offline. Easy to forget to open an app that is rarely used.

 

[Vali_3CX]

My only advice here is to upvote this as a feature request:
https://www.3cx.com/community/threa...veral-days-of-inactivity-on-off-switch.79692/

 

[SteveITS]

I almost posted but didn't try to look up old threads...that thread actually has a comment for what I thought I remembered..."The new Apps which are in BETA have a background task which will renew automatically the push subscription." Is that not yet released?

 

[Vali_3CX]

@SteveITS
Of course it is: have a look in the device Settings/3CX and turn ON the "Background App Refresh". But keep in mind, as its name says, the 3CX client should be in the background - therefore, if you terminate it by swiping up... kaput background app refresh.

Honestly, I didn't want to engage again in this discussion because has been discussed here countless time those conditions which will prevent this background refresh to work, I will recap: app terminated by swipe up, "Background App Refresh" turned off, app crash, device power on/power off, iOS update, no internet connection to MyPhone server (usually port 5001 or 443) for 7 days.

 

[SteveITS]

OK then I misunderstood your post above, sorry.

 

[Vali_3CX]

@SteveITS
No problem
Here's the blog when we implemented this App Background refresh: https://www.3cx.com/blog/releases/latest-ios-app/

 

[paurus]

@SteveITS
https://www.3cx.com/community/threa...n-push-notifications-fail.113957/#post-527672
In this post, @Vali_3CX claims that when the subscription period of Push Notifications expires, PBX sends notifications about it. Neither I nor my users have ever received them. Do your users receive such notifications?

 

[eska]

I think what Vali_3CX is trying to say is that the 3CX has to be ‘active’ in the background of the iPhone. Only then, the app (or PBX) notices the time to live is about to expire and can receive (or send) a keep alive push notification. Resulting in an extra 7 days of ‘standby’ time.

I think this means that the app cannot be closed, either manually (by swiping up) or automatically (for example during a reboot), otherwise the App Background refresh doesn't work.

@Vali_3CX please correct me if I’m wrong.

@SteveITS
https://www.3cx.com/community/threa...n-push-notifications-fail.113957/#post-527672
In this post, @Vali_3CX claims that when the subscription period of Push Notifications expires, PBX sends notifications about it. Neither I nor my users have ever received them. Do your users receive such notifications?

 

[SteveITS]

@SteveITS
https://www.3cx.com/community/threa...n-push-notifications-fail.113957/#post-527672
In this post, @Vali_3CX claims that when the subscription period of Push Notifications expires, PBX sends notifications about it. Neither I nor my users have ever received them. Do your users receive such notifications?

Not a pop up warning to the user…I think he means it’s a background keep alive to the app…hey, check in.

Recent versions have not lost the connection for me unless the phone reboots. Eska is correct.