[VoiceOps] 911 address policy for company phones at home

[Joshua Goldbard]

I can't look up the document now, but all registered exchange carriers are required by law to route 911. If you don't populate the e911 info, the call will still go through, only it'll route to the national 911 line and the response will be delayed.

I, personally, would avoid exposing my organization to such a liability if at all possible.

That being said, the accuracy of e911 information is questionable at best. What if I'm talking on my soft phone? What if I'm talking on my soft phone on the other side of the country?

The FCC does not strictly regulate VoIP communications technology unless you're a LEC. Even then it's all quite unclear (see pending rulings on MagicJack et al).

My point is this: e911, from a regulatory standpoint, is a strange beast. I am not a lawyer, but you might ask your counsel what the implications of a delayed 911 call are and who is culpable from a financial perspective.

Hope that helps!!

Cheers,
Joshua

Sent from my iPhone

On Jan 18, 2013, at 7:53 AM, "Carlos Alvarez" <carlos at televolve.com> wrote:

> We have a customer who wants us to block 911 on the phones that they give to key employees to take home.  They don't want to pay fees for 911 service at each home (which is stupid, since it's so cheap, but that's a digression).  I told them this is "illegal" but they asked to see the law, and I can't actually find something that says so.  Yet that's the common knowledge around the industry.  I do have the FCC documents that require an ITSP to provide the service, but the customer contends it doesn't apply to this specific case.
> 
> So two questions...
> 
> Does anyone here allow their customers to do this?
> 
> What is the best document to give the customer to support our position?
> 
> -- 
> Carlos Alvarez
> TelEvolve
> 602-889-3003
> 
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops