3 ms·

See this is a temporary solution and shows off all the problems with a global routing database. If I could dial sarah and it knew that I was referring to my Sa

See this is a temporary solution and shows off all the problems with a global routing database. If I could dial sarah and it knew that I was referring to my Sarah, that would be great, but another individual identifier of global significance isn't helpful. What sprint needs are truly separate routing databases for each client. If I dial 101 on my cellphone, I want it to ring my dad; why isn't this possible today? The answer is that it is, but it's too much of a headache for existing equipment within core carrier networks. In short, bring on the real unified communications, woe to the impostors.

corin_ 14y ago
"If I dial 101 on my cellphone, I want it to ring my dad; why isn't this possible today?" Is this more useful than ringing "Dad" from your cellphone, which is already possible?
- josh2600 14y ago
  In some capacities, yes. I meant generically, being able to remove identity from phone numbers. I want to call someone, however I want to call them, and reach them because the network I'm a part of already has enough information to divine who I'm trying to talk to. This isn't fantasy, you could realistically do this right now with all of the signals we have online about who people are. It's just that no one sees value in aggregated routing databases, only in adding additional routing databases, like star star me. Calling 'dad' and calling '101' are just placeholders for the real intention, reaching the person who is your father. However I want to get ahold of them should be reasonable and possible to do with today's technology. Not trying to be combative, only trying to clarify my point :).