The cunning plan I came up with works because a lot of our VoIP customers are also our Internet customers, and that is likely to be common with lots of ISP+VoIP providers. Also, a lot of our Internet customers are on DSL lines.
Basically, if we have no location data but the call comes from one of our IPs that is on a broadband line - we can find the phone number of the broadband line (a BT phone number on BT exchange).
So why not send that as the calling number on the 999 call. That way they get the location spot on.
This has huge advantages over the alternative proposals for handling nomadic callers.
- 999 service need no new protocols or systems to get the location from IP
- End user has a typically familiar number quoted on the call to avoid any confusion
- The area code of the number is what the 999 operator is expecting for the location (often not the case with VoIP services)
- The VoIP+ISP provider is not having to maintain the location data
- It can be implemented by many ISP+VoIP providers and is self contained
- It has none of the privacy issues or feature creep of NICC ND1638
I suggested to OFCOM. They shoot it down in flames because it means we would be relying on BT to have accurate location data and we have no way to guarantee that!
What?!?!??! This would be providing location data that is very very likely to be very accurate instead of no location data. Clearly a huge step in the right direction. And OFCOM think we should not do it.
I wonder why I bother.
P.S. More ideas: we could even have contracts with other ISPs such that we would pass the 999 call to them to pass to 999 if it is one of their IP addresses so they can insert the CLI on the way (not tell us the CLI) - as long as we have a short timeout fallback if they don't reply or reject the call so we can send on without location data anyway. Of course the call media can go direct from their IP to their 999 gateway then reducing the interdependencies.