[VoiceOps] 911 address policy for company phones at home

[Mary Lou Carey]

If you currently provide the roaming 911 service and the customer is balking
about paying for it, I think I would just tell them that you are legally
required to provide 911 service to your customers and you're not willing to
accept waivers for 911 when end users move their phones because it is a
liability issue for you. If they want to take on the liability of choosing
to not provide 911 service to their employees when they bring their phone
home, then they can go look for a provider who will allow them to do that.
While they may be able to find a provider to do that, they have to realize
that the decision to change providers so they don't have to pay an
additional 911 fee when their employees bring their phones home opens them
up for a lawsuit should anything happen when an employee tries to use their
VOIP phone to dial 911 from home.

 

The waiver may be appealing in the short run because it can save you money,
but chances are its really not going to be worth it in the long run. If you
think about it, when something bad happens and your end user needs to dial
911 they are not going to remember that phone doesn't display their address
accurately. They are going to pick up the first phone they see because they
are in a heightened state of alert and common sense usually goes out the
window in those moments! The reason doctor's offices always put have a
recording on their voicemails stating to that if you have a life threatening
emergency to call 911 is because people don't think straight when disaster
strikes and they frequently call the doctor's office when they should be
heading for the ER!  

 

Mary Lou Carey

BackUP Telecom Consulting

marylou at backuptelecom.com 

Office: 615-791-9969 x 2001

 

 

From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Carlos Alvarez
Sent: Friday, January 18, 2013 5:41 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] 911 address policy for company phones at home

 

On Fri, Jan 18, 2013 at 4:38 PM, Nathan Anderson <nathana at fsr.com> wrote:

 

Yes, but again, that doesn't help with the question of what to do if a
single TN for CLID purposes is shared amongst many devices, which is what I
took your original question to be.  The E911 provider will look at the CLID
and transmit the address provisioned for it, so in this scenario, there can
only be 1 address for all of these devices because there is only 1 TN for
all of these devices.  There's no mechanism to identify a device *other*
than by TN, so if you share a TN between devices, there is no way to achieve
the 911 granularity that you want for your customers that choose to operate
like this.

 

Well the question was what to tell a customer who refuses to pay for the
costs we incur in implementing the solution for them.  On a technological
level we have no problem; we assign a DID to that device, and put the
appropriate address on it.  We bill the customer for it to cover costs.  The
customer just says they don't want to pay.

 

-- 

Carlos Alvarez

TelEvolve

602-889-3003

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20130118/ca4f1710/attachment-0001.html>