WiFi Calling no longer working after my FTTP upgrade

[#1]

Just going back to the IP address - can you set up a VPN from the mesh system to give you a different IP address to check whether that makes a difference?

The only things I can think of that could be different with FTTP vs FTTC is the IP address and possibly IPv6 support.

[#2]

@Dan_the_Van 

Yes my thoughts too. It's enabled and I'm connected to it.

Tried the ONT reboot a few minutes ago - no joy.

[#3]

The only things I can think of that could be different with FTTP vs FTTC is the IP address and possibly IPv6 support.

The IP address IS likely to be allocated from a different pool on FTTP vs FTTC. As has been suggested earlier, I suspect this is the problem. EE (the MNO in this case) don't support Wifi calling outside of the UK and, by implication wifi calling is only active when there's no mobile signal, they almost certainly use the IP address to geolocate.

However, lets be clear here, ALL PN IP ranges are correctly registered in the UK but some geolocation databases are known to be incorrect.

If one of the PN staff is around, is there any chance of temporarily adding a static IP to the account to prove whether its an IP issue or not ?

[#4]

@Smack, you mentioned earlier that you use AVG mobile security but with the VPN off - can you try with the VPN on, as that may give you a different IP address (hopefully recognised as being in the UK).

[#5]

Following on from @corringham above, can you please post the first three octets of you proper - not VPN created - external IP?

[#6]

Well I’ve been on the phone for an hour and a half to Plusnet technical support using WiFi calling on my neighbours WiFi. Amongst others, I’ve been speaking to a very nice lady who seems determined to sort the problem out  

She gave me a static IP address as suggested but still no joy. I’ve also tried connecting the VPN again also as suggested, that didn’t work either.

I’m leaving it with technical support now for a while longer to see if anyone has a eureka moment. You never know  

Thanks everyone for you help and interest  

[#7]

She gave me a static IP address as suggested but still no joy. I’ve also tried connecting the VPN again also as suggested, that didn’t work either

Well that would seem to rule out an IP address problem🤔

What about a DNS problem ? I'm thinking could it be failing a DNS lookup, using the (I assume) default PN DNS servers, on whatever the Wifi calling server endpoint is ?

@Smack is it possible to temporarily change the DNS servers on your phone to Googles ( 8.8.8.8 & 8.8.4.4 )

[#8]

@MisterW  Thanks for the suggestion it's appreciated, but sadly it hasn't worked. 

Just connected to my neighbour's Wi-Fi again and 'Wi-Fi calling' kicks in instantaneously, it's all very frustrating - it seems to work on everyone else's Wi-Fi but mine!

I'm not going to give up, if Plusnet can't solve it they'll have to release me from the contract and I'll try another supplier. I'm feeling pretty determined with this one.

[#9]

Hmmm... !

Clutching at straws here, but ...

I was pondering whether "WiFi calling" was some variant of SIP (VoIP) ?, 

then noticed Google was coming up with suggestions like this ..

What should I do if Wi-Fi calling cannot work through TP-Link wireless router? 

Which suggests disabling the router's "SIP ALG",  which is a known issue for VoIP on many routers !

That site also outlines port forwarding, that might also work, but I've never needed to open specific network ports for VoIP to work on my network - but I might just have been lucky ?

I couldn't find a user manual for the Tenda Mesh router, so I'll let others here contemplate whether this is worth trying ?

[#10]

@Anonymous 

Well I'm not actually using the Tenda until this is sorted as I figured it would only muddy the waters. I'm connected direct to the Hub Two.

Think I'm going to wait for technical support for a while longer at least.

More importantly right now, it's Friday night and there's a beer in the fridge with my name on it.

[#11]

@Anonymous WiFi calling is by implication VoIP but AFAIK it isn't SIP. The networks are not forthcoming in how it actually works but it is likely some form of VPN connection to the network operators server and a generic volte client on the phone.

Maybe when Ive got time I'll have a look at the traffic using wireshark with my phone in WiFi calling mode....

For info, the SIP ALG is defaulted to OFF on the Hub 2

[#12 · Accepted solution]

@Anonymous  You're wrong there, WiFi calling is nothing to do with VOIP or SIP so SIP ALG will not have any effect.

@MisterW has got it right it works via a VPN connection and I seem to recall I had to allow IPSEC protocol outbound on the router firewall, but I have a strict deny-all policy on my router, I doubt if this applies to the Plusnet Hub. 

@Smack It's hard to understand what has changed to cause the WiFi calling problem, one thing you could check is the Plusnet Firewall which can be accessed on the broadband tab on the member centre, it's unlikely but the upgrade to FTTP may have affected it. Maybe worth checking that it's off or set to low.

[#13]

@RealAleMadrid 

You sir are a miracle worker!

My settings were checked as 'Block Common Ports' in the list of advanced settings. I checked 'Low' as you suggested and Wi-Fi calling started up immediately. To prove the solution I turned my settings to 'High'  and I immediately lost Wi-Fi calling.

I can't imagine why the upgrade altered these settings as I certainly hadn't touched them.

I guess my only niggle now is whether I am adequately protected with the firewall set to low? I do of course still have a firewall on my PC and our iOS devices should have their own security, shouldn't they? There were several other options presented in the advanced tab which I haven't touched namely...

- Block common ports except HTTP and HTTPS

- Block common ports except SMTP

- Block common ports except HTTP, HTTPS and SMTP

It goes on to say that the 'Low' setting is the only one which will allow a VPN to work properly. Interesting.

This is probably a whole new discussion but for now I'm a happy guy. Thank you again.

[#14]

@Smack You are perfectly safe.

[#15]

I guess my only niggle now is whether I am adequately protected with the firewall set to low? I do of course still have a firewall on my PC and our iOS devices should have their own security, shouldn't they? There were several other options presented in the advanced tab which I haven't touched namely...

@Smack the router also provides a firewall. The 'Broadband firewall' was really designed for use when people had USB modems and so the device attached to the modem was exposed to the internet. Now we all have routers with a NAT firewall , none of the connected devices are exposed (unless you explicitly have port forwards configured on the router) so an additional firewall is no longer needed. In fact its no longer available to new customers...

As to why yours changed , I'm confused because I have upgraded my package on many occasions, the last ones being to FTTP and my firewall settings have never changed, strange yours should ?

Glad the problem has been identified though.

edit: @Smack would you mind checking through the closed 'questions' on your account to see if there is any mention of the Firewall settings being changed , log in to the member centre and then go to https://www.plus.net/wizard/?p=search . Look through the closed questions ( there may be a few I'm afraid ) to see if any relate to the firewall setting. Any information may help to understand why it changed and possibly prevent it happening to others