Do you have any 4G signal? The suresignal is 3G only and will only kick in when you have absolutely no coverage on 4G. It�s meant for total black spots... I suspect the device is working fine but your device is getting some 4G or seeing enough 4G even if barely usable to mean it doesn�t fall onto the suresignal.

Generally WiFi calling should activate when you have 1 bar of signal. Otherwise it tends to use the local mast as WiFi calling can be a battery drain.

This means with EE when I have eg 3 bars of service I don�t use WiFi calling even with the option enabled as the standard network is adequate to support the calls etc. If you are not seeing WiFi calling with 1 bar of 4G it could be your WiFi network is not stable enough, if the data isn�t consistently flowing through solid it will disable.

The luxury of a 1 bar 3G signal doe not exist at home a very poor 2G 1 bar signal is all I get from vodafone and in fact looking at O2 and EE coverage maps i would not get better with them.
To get any signal that is workable I need to move much closer to the mast.
All masts are beyound line of sight from here.
Perhaps i should encourage vodafone et al to put a mast up in one of my fields!

In reply to a post by crule:

a very poor 2G 1 bar signal is all I get from vodafone

In which case Vodafone wifi calling should easily be kicking in on your iPhone 7 and is a far better solution than the Sure Signal box.

First of all thanks for your interest
Wifi calling is enabled on my Iphone7 and Vodafone confirm that it is OK on my account. it just never cuts in. and that seems to be the problem The Router is a Billion 7800DXL it works fine with other VOIP services like Skype and also works with VPNs which I use for remote access.
I am baffled

Doesn't the Billion firewall log have entries for what it's blocking? If you know what IP the suresignal is using, it should be easy to find out in the logs what's going on.

Thanks
Relevant entries in the log file are:-
Jul 10 09:24:18 daemon info syslog: sending OFFER to IP:***.***.1.100, MAC:50:**:f0:6d:f8:16
Jul 10 09:24:18 daemon info syslog: sending ACK to IP:***.***.1.100, MAC:50:**:f0:6d:f8:16
Any thoughts?

Hi

Wi-Fi calling shouldn't be a battery drain at all, if anything it's the opposite, simply because less power is required to connect to a Wi-Fi point a few tens of metres away than a phone mast hundreds and hundreds of metres away. I can go 5 or 6 days connected to Wi-Fi calling without needing to charge my Pixel phone, I simply disable the mobile connection as get an appalling signal at home, so it remains on Wi-Fi Calling (unless I'm out of the house) and it hardly drains the battery, much less than the cell signal.

You need a Wi-Fi access point set up for power saving using U-APSD, all modern access points will support this. All good smart phones will offload the Wi-Fi calling VPN tasks to the Wi-Fi stack, so the phone remains asleep, with the Wi-Fi chip handling the house keeping tasks to keep the VPN alive and respond to incoming calls, all without needing the phones main CPU doing a thing.

To the OP, you may need to test with your mobile signal turned off, simply put your phone into flight mode, then just enable Wi-Fi.

Regards

Phil

Hi

That router is quite old now, and is known to have issues with Wi-Fi calling due to how it handles the VPN.

See this thread http://www.billion.uk.com/forum/viewtopic.php?f=18&t...

Regards

Phil

Thanks
That could well be the problem however I can use a VPN to remotely connect to another system.