From what (little) I understand, VoLTE and VoWiFi are quite similar under the hood—VoLTE is more or less SIP, and VoWiFi is that same SIP over IPsec. You see how this would be an interoperability nightmare (not that I’m excusing the telecom people for getting us into this mess). Furthermore, some carriers get testy about you avoiding roaming charges by using VoWiFi (while others actually encourage it).
"That's on you" is not something that works at cellular scale. You're going to end up fighting some mafia scheme microcosm forming around that little thing.
From what (little) I understand, VoLTE and VoWiFi are quite similar under the hood—VoLTE is more or less SIP, and VoWiFi is that same SIP over IPsec. You see how this would be an interoperability nightmare (not that I’m excusing the telecom people for getting us into this mess). Furthermore, some carriers get testy about you avoiding roaming charges by using VoWiFi (while others actually encourage it).
That still uses their infrastructure at some point, as you are still using your carrier's phone number when you make a VoWiFi call.
Yeah, but what’s the problem they’re trying to avoid? Bad SIP implementation not working with their servers?
Just text the user: “Hey, you’re using an unsupported VoWiFi stack, if it breaks – that’s on you.”
I don't know, and I haven't seen any explanation either, malicious or otherwise.
"That's on you" is not something that works at cellular scale. You're going to end up fighting some mafia scheme microcosm forming around that little thing.