Re:Show HN: Bring phone calls into the browser (sip-to-WebRTC)
by codetrotter on Thursday January 04, 2024 @02:50PM
(#38871401)
My impression is that SIP providers are usually not regular telephony companies. So by looking at who the provider is, it is often possible to determine that it is a SIP number and not a regular number. Which in turn might lead to the phone number you are paying for not being usable for account activation. Because websites will think that you are a spammer.
[ Parent
| on HN ]
Re:Show HN: Bring phone calls into the browser (sip-to-WebRTC)
by bobsmith432 on Thursday January 04, 2024 @03:15PM
(#38871683)
Could you mask the provider, and a VoIP provider appear to be like "SimpleTalk Wireless" or something and fake being a mobile phone carrier?
Re:Show HN: Bring phone calls into the browser (sip-to-WebRTC)
by taf2 on Thursday January 04, 2024 @06:32PM
(#38873727)
Any pointers to make that happen using kamailio?
Re:Show HN: Bring phone calls into the browser (sip-to-WebRTC)
by kelnos on Thursday January 04, 2024 @10:35PM
(#38875418)
No, at least not without spinning up your own MVNO, registering it, and getting the phone numbers you care about ported over to it.
The provider information isn't encoded in the calls themselves, there's essentially a (number of) centralized databases that can be queried to get provider information, out of band.
Re:Show HN: Bring phone calls into the browser (sip-to-WebRTC)
by mc_ on Thursday January 04, 2024 @07:09PM
(#38874002)
It used to be the wild west but FCC is tightening up (maybe even going too far, we'll see). STIR/SHAKEN and KYC (know your customer) rules are making it more expensive for providers to allow any traffic over their networks. Shady providers would look the other way at spammers pumping traffic (providers getting paid); shady providers mix legitimate traffic in so upstream carriers can't just block them, etc.
Now, there's more regulatory teeth to go after the shady providers allowing this traffic.