In reply to a post by gap300:

Another legend spotted

https://postimg.cc/MMK4YX08

The bottom slider is worrying....

You definitely, 100% do NOT want an 'old fashioned' VoIP app that has to be kept open in the background of a modern smartphone, constantly polling the VoIP provider: purely because it will gobble up your battery life and needlessly use data.

The solution I'm advocating does NOT entail actively running the app in the background - it can remain fairly and squarely closed.

The inbound call notifications are done using a combination of Android / iOS built-in/system push notifications AND the Acrobits servers which keep the SIP connection back to the actual VoIP provider (i.e Sipgate) "alive". When a call comes in, the operating stem on the phone then handles it in the background and wakes up the app. as needed.

In reply to a post by think26872:

In reply to a post by gap300:

Another legend spotted

Thanks but most of what I know I have learned from this forum so credit goes to everyone who has help me in the past also. I just hope that one day I can put it into practice - if there are any full fibre gods please answer my prayers and do me next!

Have just setup sipgate basic now have to wait 2- 4 days for code in the post

Mobile connected straight away

https://postimg.cc/S2KXpFbp

In reply to a post by Pheasant:

In reply to a post by gap300:

Another legend spotted

https://postimg.cc/MMK4YX08

The bottom slider is worrying....

You definitely, 100% do NOT want an 'old fashioned' VoIP app that has to be kept open in the background of a modern smartphone, constantly polling the VoIP provider: purely because it will gobble up your battery life and needlessly use data.

The solution I'm advocating does NOT entail actively running the app in the background - it can remain fairly and squarely closed.

The inbound call notifications are done using a combination of Android / iOS built-in/system push notifications AND the Acrobits servers which keep the SIP connection back to the actual VoIP provider (i.e Sipgate) "alive". When a call comes in, the operating stem on the phone then handles it in the background and wakes up the app. as needed.

That is a very good point, going to check what FOSS options there are regards VOIP and if thats a fail will go with Acrobits (which has 39 permissions btw lol)

Again thank you so much for the very informative information

Checked over at r/fossdroid and people seem to like this one

https://postimg.cc/yJJStCm3

>Have just setup sipgate basic now have to wait 2- 4
>days for code in the post
>Mobile connected straight away

Out of interest what is the code for?
What did you decide to use on your mobile?

Thanks

Code will be for verification of address for 999 emergency calls placed.

In reply to a post by think26872:

>Have just setup sipgate basic now have to wait 2- 4
>days for code in the post
>Mobile connected straight away

Out of interest what is the code for?
What did you decide to use on your mobile?

Thanks

Hi mate went with linphone (fdroid version)

OK little update I am getting BT 900mbps installed on the 9th February

Waiting for code off sipgate so I can test the phone then if all good will port Plusnet landline number over

Off topic:

When my new FTTP Line is installed will my netgear r7800 connect directly to the ONT? (running openwrt)

Or do I need to purchase a modem ie Draytek Vigor 130

In reply to a post by Pheasant:

In reply to a post by gap300:

Another legend spotted

https://postimg.cc/MMK4YX08

The bottom slider is worrying....

You definitely, 100% do NOT want an 'old fashioned' VoIP app that has to be kept open in the background of a modern smartphone, constantly polling the VoIP provider: purely because it will gobble up your battery life and needlessly use data.

The solution I'm advocating does NOT entail actively running the app in the background - it can remain fairly and squarely closed.

The inbound call notifications are done using a combination of Android / iOS built-in/system push notifications AND the Acrobits servers which keep the SIP connection back to the actual VoIP provider (i.e Sipgate) "alive". When a call comes in, the operating stem on the phone then handles it in the background and wakes up the app. as needed.

In many cases receiving incoming calls should not result in additional battery being used because the VoIP functions are usually handed off to the modem/context CPU, which is always on anyway. Of course this may not be supported by some devices so worth testing, which is why the warning exists about battery life.

Also worth nothing that the built in VoIP of the Phone dialler is depreciated and is no longer available in new versions of Android. https://www.xda-developers.com/android-12-killing-na...

In reply to a post by E300:

In reply to a post by Pheasant:

In reply to a post by gap300:

Another legend spotted

https://postimg.cc/MMK4YX08

The bottom slider is worrying....

You definitely, 100% do NOT want an 'old fashioned' VoIP app that has to be kept open in the background of a modern smartphone, constantly polling the VoIP provider: purely because it will gobble up your battery life and needlessly use data.

The solution I'm advocating does NOT entail actively running the app in the background - it can remain fairly and squarely closed.

The inbound call notifications are done using a combination of Android / iOS built-in/system push notifications AND the Acrobits servers which keep the SIP connection back to the actual VoIP provider (i.e Sipgate) "alive". When a call comes in, the operating stem on the phone then handles it in the background and wakes up the app. as needed.

In many cases receiving incoming calls should not result in additional battery being used because the VoIP functions are usually handed off to the modem/context CPU, which is always on anyway. Of course this may not be supported by some devices so worth testing, which is why the warning exists about battery life.

Also worth nothing that the built in VoIP of the Phone dialler is depreciated and is no longer available in new versions of Android. https://www.xda-developers.com/android-12-killing-na...

Well I would prefer to use the baked in system than install another app on my phone so I will test both

Thank you for the link