3 ms·
> map them down like we do it with IPs and domain names We have been able to map phone numbers to SIP URIs for a long time with E.164 ENUM. Numbers are a hassl
by jallmann 11y ago
> map them down like we do it with IPs and domain names
We have been able to map phone numbers to SIP URIs for a long time with E.164 ENUM. Numbers are a hassle, but there's nothing preventing numbers from living alongside proper URIs today.
> let conventional telephony die and VoIP take over its place.
Many places are still circuit-switched at the last mile, whether over landline or cellular. We can't turn off the PSTN in favor of VoIP until everybody has switched over -- similar to the IPv6 changeover dilemma, although more tractable due to the ubiquity of Internet access and proper interworking -- no tunneling required.
What I'm waiting for though, is the ability to "bring your own" SIP URI so the carriers can handle our calls in the same way GMail can handle our email for personal/business domains. (Not to mention the capability to dial out to SIP addresses...)
Ideally, this would extend all the way down to "bring your own SIP proxy and registrar" where the carriers would just act as dumb pipes to carry your calls at the same QoS as theirs, but that's a far ways off.
- caruizdiaz 11y ago> We have been able to map phone numbers to SIP URIs for a long time with E.164 ENUM yes, because dialing 3.0.3.3.8.4.0.3.5.5.1.2.5.e164.arpa is super easy to do. I was talking about a proper solution, not patching an existing one. > We can't turn off the PSTN in favor of VoIP until everybody has switched over Exactly, but we have to start at some point. We have been doing phone calls for more than 100 years, and it remained practically unchanged since then.
- jallmann 11y ago> yes, because dialing 3.0.3.3.8.4.0.3.5.5.1.2.5.e164.arpa is super easy to do. Nonsense, the user would never dial that. The number gets mechanically translated as necessary, which is extremely straightforward... > We have been doing phone calls for more than 100 years, and it remained practically unchanged since then. Really? Most of your comments in this thread are uninformed, bordering on the absurd. If you are doing a telecom startup (as your profile implies), I would encourage a better understanding of the industry: you can't compete with what you don't know.
- redbeard0x0a 11y agoCould you image what things would look like with rogue "DNS" servers that mapped bankofamerica.phone to a phisher controlled endpoint? You could no longer trust that calling the "number" on the back of your credit card would actually get you in touch with the actual bank.
- jallmann 11y agoThe same problems would happen if someone mapped "google.com" to a phisher controlled endpoint. TLS solves that, and by extension, so does SIPS. Then add in SRTP, etc.