I'm not sure I understand? The service I built is entirely WiFi based. I find most bars restaurants and coffee shops generally have WiFi capable of VoIP traffic.
It would be cool to get back on a mobile carrier, but only if I had enough network control to handle the kind of hacking attempts in the article
My interpretation is that the MVNO plan and number would only serve the purpose of keeping a constantly on data connection to then use your own infrastructure and number. The number from the MVNO would not really be used.
It seems this would solve the hijacking issues but you’d still likely get bombarded with robo calls to the MVNO number.
Does your setup have any mitigation against robo calls for the anveo number?
What do use for dialing? I’m wondering if it would somehow be possible to disable the device phone app to disable getting nuisances from the MVNO number.
I’m very interested in a write up. Thanks for sharing!
>you’d still likely get bombarded with robo calls to the MVNO number.
presumably all his calls are done through a VOIP app (he said astrix so probably SIP) and he can ignore all "normal" incoming calls, or is forwarded to his phone using a known number and he can ignore every number except that one.
In his setup, yes, this works as he does not have any phone number tied to the device. He’s using WiFi to connect to the PBX.
In the scenario where you use a cheap cell plan to have an always on data connection to the the PBX you will have to have some method of blocking all of the calls to the device number. I suppose you could have them all forward to the PBX and then your filtering could apply.
It would be cool to get back on a mobile carrier, but only if I had enough network control to handle the kind of hacking attempts in the article