2 Degrees VoWiFi problem

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › 2 Degrees VoWiFi problem

1 | 2

ajbw

131 posts

Master Geek
+1 received by user: 11

Lifetime subscriber

#3471664 19-Mar-2026 12:28

SaltyNZ:
ajbw:

As a test, yesterday I went to the local library and tried from there - same result, so it doesn't look like it's our router

Sounds like your handset then.

It probably is, but I tried the following test (again) with the Alcatel 5033T and a different SIM:

I went into aeroplane mode and re-enabled the wifi, and tested that wifi was working.

On trying to make a call, I get "Turn off aeroplane mode or connect to a wireless network to make a call"

But it is connected to a wireless network.

Am I doing a meaningful test here?

SaltyNZ

8862 posts

Uber Geek
+1 received by user: 9539

Trusted

2degrees

Lifetime subscriber

#3471669 19-Mar-2026 12:40

Well, that does seem to confirm that the Alcatel, at least, is not compatible.

iPad Pro 11" + iPhone 15 Pro Max + 2degrees 4tw!

These comments are my own and do not represent the opinions of 2degrees.

ajbw

131 posts

Master Geek
+1 received by user: 11

Lifetime subscriber

#3471673 19-Mar-2026 12:56

SaltyNZ:
Well, that does seem to confirm that the Alcatel, at least, is not compatible.

It looks that way. If I enable wifi calling in the settings, it (eventually) times out with a 'Server Unreachable' message.

If I disable wifi calling, it makes the call.

On the Nokia, enabling or disabling wifi calling makes no difference - it always makes the call over VoLTE.

yitz

2238 posts

Uber Geek
+1 received by user: 594

#3471675 19-Mar-2026 13:10

ajbw: If I enable wifi calling in the settings, it (eventually) times out with a 'Server Unreachable' message.

I wonder what it's trying to connect to?

Since you are running Pihole, it could be worth trying this users suggestion of rebinding the 3gppnetwork.org search domain for MCC530/MNC024 (2degrees).
https://www.geekzone.co.nz/forums.asp?forumid=97&topicid=298485&page_no=21#3173222

boosacnoodle

1271 posts

Uber Geek
+1 received by user: 855

#3471693 19-Mar-2026 14:05

2degrees, for whatever reason, appear to have elected not to follow 3GPP TS 23.003, 19.4.2.9.2 Operator Identifier based ePDG FQDN, which states:

The ePDG Fully Qualified Domain Name (ePDG FQDN) contains an Operator Identifier that shall uniquely identify the PLMN where the ePDG is located. The ePDG FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The third and fourth labels together shall uniquely identify the PLMN. The first two labels shall be "epdg.epc". The result of the ePDG FQDN will be: "epdg.epc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org"

One NZ has the default setup epdg.epc.mnc001.mcc530.pub.3gppnetwork.org

Spark has a strange hybrid of epdg.epc.mnc005.mcc530.pub.3gppnetwork.spark.co.nz; however, epdg.epc.mnc005.mcc530.pub.3gppnetwork.org (i.e. the default) also works so you need not strictly use Spark's custom config.

2degrees, for whatever reason, has elected to go off the rails entirely and only uses epdg.ims.2degrees.net.nz - epdg.epc.mnc024.mcc530.pub.3gppnetwork.org does not resolve anywhere, which is why your phone is likely not working. Surely this would be a trivial fix given that it's the standard but who really knows?

ajbw

131 posts

Master Geek
+1 received by user: 11

Lifetime subscriber

#3471696 19-Mar-2026 14:10

yitz:
ajbw: If I enable wifi calling in the settings, it (eventually) times out with a 'Server Unreachable' message.

I wonder what it's trying to connect to?

Since you are running Pihole, it could be worth trying this users suggestion of rebinding the 3gppnetwork.org search domain for MCC530/MNC024 (2degrees).
https://www.geekzone.co.nz/forums.asp?forumid=97&topicid=298485&page_no=21#3173222

I tried adb logcat.
It didn't come up with any DNS resolution failures.
It did come up with lots of these:
1038 1141 E WifiVendorHal: getWifiLinkLayerStats_1_3_Internal(l.973) failed {.code = ERROR_NOT_SUPPORTED, .description = }
Which may be relevant?

Lego

Shop now for Lego sets and other gifts (affiliate link).

Linux

12178 posts

Uber Geek
+1 received by user: 8472

Trusted

Lifetime subscriber

#3471729 19-Mar-2026 15:24

boosacnoodle:

2degrees, for whatever reason, appear to have elected not to follow 3GPP TS 23.003, 19.4.2.9.2 Operator Identifier based ePDG FQDN, which states:

The ePDG Fully Qualified Domain Name (ePDG FQDN) contains an Operator Identifier that shall uniquely identify the PLMN where the ePDG is located. The ePDG FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The third and fourth labels together shall uniquely identify the PLMN. The first two labels shall be "epdg.epc". The result of the ePDG FQDN will be: "epdg.epc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org"

One NZ has the default setup epdg.epc.mnc001.mcc530.pub.3gppnetwork.org

Spark has a strange hybrid of epdg.epc.mnc005.mcc530.pub.3gppnetwork.spark.co.nz; however, epdg.epc.mnc005.mcc530.pub.3gppnetwork.org (i.e. the default) also works so you need not strictly use Spark's custom config.

2degrees, for whatever reason, has elected to go off the rails entirely and only uses epdg.ims.2degrees.net.nz - epdg.epc.mnc024.mcc530.pub.3gppnetwork.org does not resolve anywhere, which is why your phone is likely not working. Surely this would be a trivial fix given that it's the standard but who really knows?

@SaltyNZ might be able to add 2cents here or maybe not

yitz

2238 posts

Uber Geek
+1 received by user: 594

#3471731 19-Mar-2026 15:41

ajbw: I tried adb logcat.
It didn't come up with any DNS resolution failures.
It did come up with lots of these:
1038 1141 E WifiVendorHal: getWifiLinkLayerStats_1_3_Internal(l.973) failed {.code = ERROR_NOT_SUPPORTED, .description = }
Which may be relevant?

Is your log level set to include "D" debug as matt1553's name resolution error was at that level.

ajbw

131 posts

Master Geek
+1 received by user: 11

Lifetime subscriber

#3471749 19-Mar-2026 16:36

yitz:
ajbw: I tried adb logcat.
It didn't come up with any DNS resolution failures.
It did come up with lots of these:
1038 1141 E WifiVendorHal: getWifiLinkLayerStats_1_3_Internal(l.973) failed {.code = ERROR_NOT_SUPPORTED, .description = }
Which may be relevant?

Is your log level set to include "D" debug as matt1553's name resolution error was at that level.

I did have 'D' entries in the log.

However, I tried another test:
I set up one phone (nokia 7.2) as a hotspot and then tried wifi calling through that with the Nokia G20. So our local wlan was not involved.

It worked! On the second try.
It didn't work the other way round, interestingly

So I have to assume that it is our wlan, and not the handsets....

How to diagnose?

ajbw

131 posts

Master Geek
+1 received by user: 11

Lifetime subscriber

#3472001 20-Mar-2026 14:59

More research

There are two problems (there usually are):
The first is that two of the four handset (Nokia 7.2 and Smart E10 5033T)
do not seem to do WoWifi at all on 2DM

But two (Nokia G20 and Nokia C10) will do VoWifi.
But not on our network.

I've tried using the wlan from the router, from a Mikrotik access point and from a Raspberry Pi, and none work.

If I set up a phone as a hotspot and connect to that, two phones (as above) will do VoWifi.
They also do it on other people's networks.

So I conclude that the router is the problem to solve first - unless it's a problem with Voyager...

It's a NetComm N300 NF10WV , software Version NF10WV.NC.AU-R5B030.EN

Does anyone have any experience using VoWifi on one of these?

1 | 2