Chris, Hrm; difficult to deduce what is going on without more details. The best is really to enable debug logs and look into what they contain at the precise time you miss a call.
Cheers Germán > On 26 Oct 2021, at 23:20, Chris Jackson <ch...@cd-jackson.com> wrote: > > For this test I was actually not using Wifi - the iPhone was on the mobile > network and it was working fine (I was able to make normal calls). Sorry - I > don’t seem to have mentioned that point below, but I think I did say this in > the report when I sent in the logs. So, I can try this using Wifi, but your > suggestion to disable Wifi is actually what I’ve already done. > > Is it really true that time doesn’t matter? I was recently reading up on how > the push notification registration works and while I didn’t really go into > all the detail I thought that I read that there was a need to re-registration > after some period? Also, it may not be time related - it’s just my first > impression but I’ve not really characterised this particularly well as it > takes a lot of time. What I can say is it seems mostly reliable if I call > shortly after I’ve used the app, and mostly unreliable if I call when the > iPhone has been sitting idle for a reasonable period. > > Thanks. > > Chris > >> On 27/10/2021, at 10:10 AM, German Cancio <german.can...@gmail.com> wrote: >> >> Chris, >> >> Would that rather look like an issue with your Wifi connection? The app on >> iOS will be sent to rest only seconds after a call is completed and the app >> is sent to background (e.g. locking the phone); it doesn’t make any >> difference to the app whether a call is received one minute or one hour >> after the previous one - it gets waken up by a push notification received by >> iOS and passed to the app. But your Wifi connection might be put into >> dormant mode by your router, so that push notification might not make it >> through in time for picking up the call. That’s a quite common problem that >> ends up affecting many VoIP apps. >> >> Try disabling Wifi and see whether you still have the same issue using >> mobile data. If that doesn’t fix the issue, you could try to enable logs and >> look what the app does at the time of the call. >> >> Germán >> >> >>> On 26 Oct 2021, at 21:17, Chris Jackson <ch...@cd-jackson.com> wrote: >>> >>> I’ve been testing out LinPhone, and while it mostly seems to work well, >>> notifications of iPhone calls seems to be unreliable. I sent some logs >>> recently but thought I should follow up with a message here to see if >>> others were experiencing issues, or if it is just a problem with my system. >>> >>> I’ve not characterised this well, but from a few tests it seems that longer >>> periods of no use will result in calls not being established. It seems that >>> possibly leaving the iPhone “off” for an hour (ie not opening any apps and >>> certainly not opening LinPhone) will result in calls not being connected. I >>> might be wrong as I’ve only tested this a couple of times and obviously >>> this takes a lot of time between tests. Calls made after 30 or 40 minutes >>> of no use have so far always worked ok though. >>> >>> I wonder if this is a known issue or something that could be a settings >>> issue in my system? I’m using the LinPhone cloud FlexiSip and have not >>> changed any settings from default in the iPhone app. >>> >>> Thanks >>> Chris >>> _______________________________________________ >>> Linphone-users mailing list >>> Linphone-users@nongnu.org >>> https://lists.nongnu.org/mailman/listinfo/linphone-users >> >> >> _______________________________________________ >> Linphone-users mailing list >> Linphone-users@nongnu.org >> https://lists.nongnu.org/mailman/listinfo/linphone-users > > > _______________________________________________ > Linphone-users mailing list > Linphone-users@nongnu.org > https://lists.nongnu.org/mailman/listinfo/linphone-users _______________________________________________ Linphone-users mailing list Linphone-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/linphone-users
