VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
January 2013
- 57 participants
- 176 messages
911 address policy for company phones at home
by nathana@fsr.com
I'm confused, and I apologize to those who have already been involved in this discussion thread for a while since I am just now jumping in. CLID is inherently outbound, so I am not sure what you mean by "inbound vs. outbound caller IDs". Perhaps by "inbound CLID" you mean DID, or DNIS?
I'm also not sure how you propose to bind E911 details to a device instead of a telephone number. The few E911 services I've looked at all only give you the option to provision E911 information via TN. So if you propose a set-up such as what is being discussed here, where each company phone only has an internal extension # and no DID, and CLID is uniformly set to a single number for all outbound calls from any phone whether it is located in the office building or at an employee's residence, then there can only be a single E911 address for all of those phones. That seems inescapable. Are you saying that there are E911 companies that can provision differently, and not use the CLID as the "key" to looking up an address? What do they use/how do they work, and can you name some names?
The only other kludgey workaround I can think of that might pass muster would be to assign unique "throwaway" TNs to each individual extension that you would use as the CLID for outbound from that extension *only* when 911 is dialed, and continue to use the global office TN as CLID across all extensions for all other outbound calls. It's not a perfect solution, since if the individuals using those phones have no clue about those numbers, they might get confused when asked to verify their own telephone number by the PSAP and the dispatcher reads some number back to them that isn't their main office number. At that point, you might as well let the customer know that these numbers exist and give them the option of using them as DIDs for the extensions/devices they've been assigned to.
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Carlos Alvarez
Sent: Friday, January 18, 2013 11:49 AM
To: Joshua Goldbard
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] 911 address policy for company phones at home
On Fri, Jan 18, 2013 at 12:46 PM, Joshua Goldbard <j at 2600hz.com> wrote:
Yeah, but you're talking about inbound.
In many corporate environments, the outbound caller ID is uniform for a location (and even if it's not, most systems support uniform caller ID for emergencies). E911 is an outbound service and the inbound and outbound caller IDs can certainly be different.
Does that help clarify my viewpoint?
Ah, yes. We very rarely get anyone who wants to do that, so it didn't cross my mind.
We do have special 911 CLID/DID settings and special processing for those calls. However we bind them to a device, since the device is what has location, in most of our installations.
--
Carlos Alvarez
TelEvolve
602-889-3003
Jan. 18, 2013
911 address policy for company phones at home
by marylou@backuptelecom.com
I just wanted to point out one thing. The waiver I mentioned is NOT to avoid
providing 911 service for the customer as it sounds to be the case in
Vantage's situation. You MUST provide 911 service for the customer. The
waiver simply states that the 911 service is for the single location that
the phone was installed and while the phone might work if you move it
somewhere else, the 911 service will not!
I would fully agree that relying on waivers is risky business - especially
when it comes to 911. When McDonald's can be held liable for someone
spilling hot coffee on themselves when they stuck it between her legs, you
can most certainly be sued for not providing 911 service when the customer
moved their phone. My suggestion would be to sign up for the roaming ALI
database service so the customers can update their location information
whenever they move the phone and then program the phones so that every time
the phone is powered up, the customer has to update their location in the
ALI database. That's really the safest way to operate!
I remember going on an interview years ago to a retail company (who is no
longer in business) and one of the questions they brought up was a problem
they were dealing with at the moment. They had two locations across the
freeway from each other and when someone called the 911 from one location,
the ambulance ended up showing up at the wrong building. Through a little
investigation we found out that regardless of which location someone dialed
911 from, the calls were all routed to one number in their PBX. That one
number happened to be associated with the main building so when 911 was
called, that's where the ambulance showed up.
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 Jon Radel
Sent: Friday, January 18, 2013 12:44 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] 911 address policy for company phones at home
Unless I'm missing something here, you're not proposing to sell service to a
stationary location and warning the customer that 911 will break if they
fail to notify you that they've moved the phone, but you're selling service
to stationary location A when the customer has already notified you that
they'll really be using the phone in stationary location B. That really
doesn't sound like the same thing at all. They've already told you that the
phone is going to be in location B and you're proposing to not handle 911
appropriately. (My apologies if I've misunderstood the situation.)
Be warned that the FCC has clearly signaled that they don't find waivers
involving 911 the slightest bit amusing. See
http://www.fcc.gov/document/vantage-communications for their side of our
story. You might find the references to actual regulatory language useful.
I also find myself impelled to ask: Are you actually pricing this in such a
way that there's a line item for 911 service with a dollar figure next to
it? That's just inviting the customers to try haggle, and could be
construed that you consider 911 optional rather than a fundamental part of
your service. Or is this all just a side-effect of charging for the DIDs in
the additional rate center(s) where the customer's employees live?
Bottom line, however, my advice is that you're treading into waters where
you *really* *really* want to talk to a competent lawyer with a specialty in
this arena and not take random advice on a mailing list. Not even mine.
:-) Getting this wrong could conceivably destroy your company.
At the very least, compare what the FCC is currently saying against what
Mary Lou is saying, some of which appears to be dangerously out of date.
--Jon Radel
jradel at vantage.com
267-756-1014
On 1/18/13 1:01 PM, Carlos Alvarez wrote:
Great answer, thanks. This really covers what the customer is asking for,
which is basically the stationary option (all phones show one
CLID/ANI/location). I will advise them that it's legal, just not advised,
and get a written signature for liability.
We do use a 911 service provider, we're not a CLEC. We currently provide
the ability for a customer to have an address for each individual phone if
they choose.
On Fri, Jan 18, 2013 at 10:48 AM, Mary Lou Carey <marylou at backuptelecom.com>
wrote:
Legally VOIP providers have the option to offer roaming VOIP services or
stationary VOIP services. If you offer roaming VOIP you are required to
provide your customers with a way to update their address information
whenever they move their phone. It can either be a website they log into to
change their address or a 24 hour phone number they call, but either way you
MUST provide it if you allow them to roam. If you do allow them to roam you
have to get your 911 service from a VOIP 911 provider (who has connections
to every PSAP in the country) or be connected to every PSAP in the country
yourself because a connection to the LEC network will only cover you for the
counties or parishes that you establish trunks for.
Most VOIP providers I know sign up with a VOIP 911 provider because they
cover a large area so it's cheaper to do that then have a multitude of
connections through the LEC. If you decide to go with a stationary VOIP
product, you must have the customer sign a waiver stating that they are
aware that if they move their phone they will not receive 911 service. I
believe the FCC ruled in the last year or so that if you also have to place
some type of sticker on the phone so that the end user who uses the phone
knows 911 is not available when you move it rather than just the person who
ordered the phones.
So the decision is not your customer's, but yours. If you choose to allow
the customer to move their phone then you either have to place a sticker on
the phone stating that 911 service will not be available to the customer OR
you have to provide the customer with a way to change their address
information when they do move the phone. While you could offer either option
to customers based on how much they wanted to pay, I would think liability
wise it would be better if you either offered it to everyone or no one at
all because it would be too easy for one of your employees to make a mistake
in setting someone up and not put them on the right plan.
Mary Lou Carey
BackUP Telecom Consulting
marylou at backuptelecom.com
Office: 615-791-9969 x 2001 <tel:615-791-9969%20x%202001>
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Carlos Alvarez
Sent: Friday, January 18, 2013 9:51 AM
To: voiceops at voiceops.org
Subject: [VoiceOps] 911 address policy for company phones at home
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
--
Carlos Alvarez
TelEvolve
602-889-3003
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 18, 2013
911 address policy for company phones at home
by mike@astrocompanies.com
FYI, at least in Florida, providers are *required* to separately list the
911 surcharge as a separate line item, and are prohibited from marking it up
or down from the actual surcharge amount, usually 0.50 per line. While one
would have the ability to change or waive a provider-imposed records
management charge, it would not (at least in Florida) have the ability to
remove the surcharge or bundle it with the service price.
Mike Ray, MBA, CNE, CTE
Astro Companies, LLC
11523 Palm Brush Trail #401
Lakewood Ranch, FL 34202
DIRECT: 941 600-0207
http://www.astrocompanies.com
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Jon Radel
Sent: Friday, January 18, 2013 1:44 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] 911 address policy for company phones at home
Unless I'm missing something here, you're not proposing to sell service to a
stationary location and warning the customer that 911 will break if they
fail to notify you that they've moved the phone, but you're selling service
to stationary location A when the customer has already notified you that
they'll really be using the phone in stationary location B. That really
doesn't sound like the same thing at all. They've already told you that the
phone is going to be in location B and you're proposing to not handle 911
appropriately. (My apologies if I've misunderstood the situation.)
Be warned that the FCC has clearly signaled that they don't find waivers
involving 911 the slightest bit amusing. See
http://www.fcc.gov/document/vantage-communications for their side of our
story. You might find the references to actual regulatory language useful.
I also find myself impelled to ask: Are you actually pricing this in such a
way that there's a line item for 911 service with a dollar figure next to
it? That's just inviting the customers to try haggle, and could be
construed that you consider 911 optional rather than a fundamental part of
your service. Or is this all just a side-effect of charging for the DIDs in
the additional rate center(s) where the customer's employees live?
Bottom line, however, my advice is that you're treading into waters where
you *really* *really* want to talk to a competent lawyer with a specialty in
this arena and not take random advice on a mailing list. Not even mine.
:-) Getting this wrong could conceivably destroy your company.
At the very least, compare what the FCC is currently saying against what
Mary Lou is saying, some of which appears to be dangerously out of date.
--Jon Radel
jradel at vantage.com
267-756-1014
On 1/18/13 1:01 PM, Carlos Alvarez wrote:
Great answer, thanks. This really covers what the customer is asking for,
which is basically the stationary option (all phones show one
CLID/ANI/location). I will advise them that it's legal, just not advised,
and get a written signature for liability.
We do use a 911 service provider, we're not a CLEC. We currently provide
the ability for a customer to have an address for each individual phone if
they choose.
On Fri, Jan 18, 2013 at 10:48 AM, Mary Lou Carey <marylou at backuptelecom.com>
wrote:
Legally VOIP providers have the option to offer roaming VOIP services or
stationary VOIP services. If you offer roaming VOIP you are required to
provide your customers with a way to update their address information
whenever they move their phone. It can either be a website they log into to
change their address or a 24 hour phone number they call, but either way you
MUST provide it if you allow them to roam. If you do allow them to roam you
have to get your 911 service from a VOIP 911 provider (who has connections
to every PSAP in the country) or be connected to every PSAP in the country
yourself because a connection to the LEC network will only cover you for the
counties or parishes that you establish trunks for.
Most VOIP providers I know sign up with a VOIP 911 provider because they
cover a large area so it's cheaper to do that then have a multitude of
connections through the LEC. If you decide to go with a stationary VOIP
product, you must have the customer sign a waiver stating that they are
aware that if they move their phone they will not receive 911 service. I
believe the FCC ruled in the last year or so that if you also have to place
some type of sticker on the phone so that the end user who uses the phone
knows 911 is not available when you move it rather than just the person who
ordered the phones.
So the decision is not your customer's, but yours. If you choose to allow
the customer to move their phone then you either have to place a sticker on
the phone stating that 911 service will not be available to the customer OR
you have to provide the customer with a way to change their address
information when they do move the phone. While you could offer either option
to customers based on how much they wanted to pay, I would think liability
wise it would be better if you either offered it to everyone or no one at
all because it would be too easy for one of your employees to make a mistake
in setting someone up and not put them on the right plan.
Mary Lou Carey
BackUP Telecom Consulting
marylou at backuptelecom.com
Office: 615-791-9969 x 2001 <tel:615-791-9969%20x%202001>
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Carlos Alvarez
Sent: Friday, January 18, 2013 9:51 AM
To: voiceops at voiceops.org
Subject: [VoiceOps] 911 address policy for company phones at home
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
--
Carlos Alvarez
TelEvolve
602-889-3003
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 18, 2013
911 address policy for company phones at home
by abalashov@evaristesys.com
On 01/18/2013 02:27 PM, Carlos Alvarez wrote:
> This is a good point, and a fine line. I'd say at least 50% of our
> customers move phones. Almost none of them tell us. I suppose knowing
> that they do puts us in a tougher legal situation than having plausible
> deniability.
Which is why this paragraph should have been written as:
"It occurs to me that conceivably, at least 50% of our customers could,
hypothetically, in principle, be moving their phones, and possibly
without telling us, perhaps maybe."
:-)
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Jan. 18, 2013
911 address policy for company phones at home
by carlos@televolve.com
On Fri, Jan 18, 2013 at 12:46 PM, Joshua Goldbard <j at 2600hz.com> wrote:
> Yeah, but you're talking about inbound.
>
> In many corporate environments, the outbound caller ID is uniform for a
> location (and even if it's not, most systems support uniform caller ID for
> emergencies). E911 is an outbound service and the inbound and outbound
> caller IDs can certainly be different.
>
> Does that help clarify my viewpoint?
>
Ah, yes. We very rarely get anyone who wants to do that, so it didn't
cross my mind.
We do have special 911 CLID/DID settings and special processing for those
calls. However we bind them to a device, since the device is what has
location, in most of our installations.
--
Carlos Alvarez
TelEvolve
602-889-3003
Jan. 18, 2013
911 address policy for company phones at home
by j@2600hz.com
Yeah, but you're talking about inbound.
In many corporate environments, the outbound caller ID is uniform for a location (and even if it's not, most systems support uniform caller ID for emergencies). E911 is an outbound service and the inbound and outbound caller IDs can certainly be different.
Does that help clarify my viewpoint?
Cheers,
Joshua
Sent from my iPhone
On Jan 18, 2013, at 11:29 AM, "Carlos Alvarez" <carlos at televolve.com<mailto:carlos at televolve.com>> wrote:
On Fri, Jan 18, 2013 at 12:16 PM, Joshua Goldbard <j at 2600hz.com<mailto:j at 2600hz.com>> wrote:
We run our e911 through a service as well but price per location as opposed to per phone. We've also found that, if possible, binding the e911 to a did is preferable to device binding.
We price per location also. The extension binding versus device binding is confusing to me; don't you give a customer the same DID to ring all of their devices? That's what we do, so the home phone and office ring concurrently.
--
Carlos Alvarez
TelEvolve
602-889-3003
Jan. 18, 2013
911 address policy for company phones at home
by carlos@televolve.com
On Fri, Jan 18, 2013 at 12:16 PM, Joshua Goldbard <j at 2600hz.com> wrote:
> We run our e911 through a service as well but price per location as
> opposed to per phone. We've also found that, if possible, binding the e911
> to a did is preferable to device binding.
>
We price per location also. The extension binding versus device binding is
confusing to me; don't you give a customer the same DID to ring all of
their devices? That's what we do, so the home phone and office ring
concurrently.
--
Carlos Alvarez
TelEvolve
602-889-3003
Jan. 18, 2013
911 address policy for company phones at home
by carlos@televolve.com
On Fri, Jan 18, 2013 at 11:44 AM, Jon Radel <jradel at vantage.com> wrote:
> Unless I'm missing something here, you're not proposing to sell service
> to a stationary location and warning the customer that 911 will break if
> they fail to notify you that they've moved the phone, but you're selling
> service to stationary location A when the customer has already notified you
> that they'll really be using the phone in stationary location B. That
> really doesn't sound like the same thing at all. They've already told you
> that the phone is going to be in location B and you're proposing to not
> handle 911 appropriately. (My apologies if I've misunderstood the
> situation.)
>
This is a good point, and a fine line. I'd say at least 50% of our
customers move phones. Almost none of them tell us. I suppose knowing
that they do puts us in a tougher legal situation than having plausible
deniability.
> I also find myself impelled to ask: Are you actually pricing this in such
> a way that there's a line item for 911 service with a dollar figure next to
> it? That's just inviting the customers to try haggle, and could be
> construed that you consider 911 optional rather than a fundamental part of
> your service. Or is this all just a side-effect of charging for the DIDs
> in the additional rate center(s) where the customer's employees live?
>
It's a line item to cover our costs, just like regular phone company charge
a line item for 911 service. We do it on a per-location basis because
that's how we are charged.
--
Carlos Alvarez
TelEvolve
602-889-3003
Jan. 18, 2013
911 address policy for company phones at home
by j@2600hz.com
We run our e911 through a service as well but price per location as opposed to per phone. We've also found that, if possible, binding the e911 to a did is preferable to device binding.
Just one service providers perspective; e911 is a lot of fun so I'm sure there's a lot of opinion on this topic.
Cheers,
Joshua
Sent from my iPhone
On Jan 18, 2013, at 10:04 AM, "Carlos Alvarez" <carlos at televolve.com<mailto:carlos at televolve.com>> wrote:
Great answer, thanks. This really covers what the customer is asking for, which is basically the stationary option (all phones show one CLID/ANI/location). I will advise them that it's legal, just not advised, and get a written signature for liability.
We do use a 911 service provider, we're not a CLEC. We currently provide the ability for a customer to have an address for each individual phone if they choose.
On Fri, Jan 18, 2013 at 10:48 AM, Mary Lou Carey <marylou at backuptelecom.com<mailto:marylou at backuptelecom.com>> wrote:
Legally VOIP providers have the option to offer roaming VOIP services or stationary VOIP services. If you offer roaming VOIP you are required to provide your customers with a way to update their address information whenever they move their phone. It can either be a website they log into to change their address or a 24 hour phone number they call, but either way you MUST provide it if you allow them to roam. If you do allow them to roam you have to get your 911 service from a VOIP 911 provider (who has connections to every PSAP in the country) or be connected to every PSAP in the country yourself because a connection to the LEC network will only cover you for the counties or parishes that you establish trunks for.
Most VOIP providers I know sign up with a VOIP 911 provider because they cover a large area so it's cheaper to do that then have a multitude of connections through the LEC. If you decide to go with a stationary VOIP product, you must have the customer sign a waiver stating that they are aware that if they move their phone they will not receive 911 service. I believe the FCC ruled in the last year or so that if you also have to place some type of sticker on the phone so that the end user who uses the phone knows 911 is not available when you move it rather than just the person who ordered the phones.
So the decision is not your customer's, but yours. If you choose to allow the customer to move their phone then you either have to place a sticker on the phone stating that 911 service will not be available to the customer OR you have to provide the customer with a way to change their address information when they do move the phone. While you could offer either option to customers based on how much they wanted to pay, I would think liability wise it would be better if you either offered it to everyone or no one at all because it would be too easy for one of your employees to make a mistake in setting someone up and not put them on the right plan.
Mary Lou Carey
BackUP Telecom Consulting
marylou at backuptelecom.com<mailto:marylou at backuptelecom.com>
Office: 615-791-9969 x 2001<tel:615-791-9969%20x%202001>
From: voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org> [mailto:voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>] On Behalf Of Carlos Alvarez
Sent: Friday, January 18, 2013 9:51 AM
To: voiceops at voiceops.org<mailto:voiceops at voiceops.org>
Subject: [VoiceOps] 911 address policy for company phones at home
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<tel:602-889-3003>
--
Carlos Alvarez
TelEvolve
602-889-3003
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 18, 2013
911 address policy for company phones at home
by jradel@vantage.com
Unless I'm missing something here, you're not proposing to sell service
to a stationary location and warning the customer that 911 will break if
they fail to notify you that they've moved the phone, but you're selling
service to stationary location A when the customer has already notified
you that they'll really be using the phone in stationary location B.
That really doesn't sound like the same thing at all. They've already
told you that the phone is going to be in location B and you're
proposing to not handle 911 appropriately. (My apologies if I've
misunderstood the situation.)
Be warned that the FCC has clearly signaled that they don't find waivers
involving 911 the slightest bit amusing. See
http://www.fcc.gov/document/vantage-communications for their side of our
story. You might find the references to actual regulatory language useful.
I also find myself impelled to ask: Are you actually pricing this in
such a way that there's a line item for 911 service with a dollar figure
next to it? That's just inviting the customers to try haggle, and could
be construed that you consider 911 optional rather than a fundamental
part of your service. Or is this all just a side-effect of charging for
the DIDs in the additional rate center(s) where the customer's employees
live?
Bottom line, however, my advice is that you're treading into waters
where you *really* *really* want to talk to a competent lawyer with a
specialty in this arena and not take random advice on a mailing list.
Not even mine. :-) Getting this wrong could conceivably destroy your
company.
At the very least, compare what the FCC is currently saying against what
Mary Lou is saying, some of which appears to be dangerously out of date.
--Jon Radel
jradel at vantage.com
267-756-1014
On 1/18/13 1:01 PM, Carlos Alvarez wrote:
> Great answer, thanks. This really covers what the customer is asking
> for, which is basically the stationary option (all phones show one
> CLID/ANI/location). I will advise them that it's legal, just not
> advised, and get a written signature for liability.
>
> We do use a 911 service provider, we're not a CLEC. We currently
> provide the ability for a customer to have an address for each
> individual phone if they choose.
>
>
> On Fri, Jan 18, 2013 at 10:48 AM, Mary Lou Carey
> <marylou at backuptelecom.com <mailto:marylou at backuptelecom.com>> wrote:
>
> Legally VOIP providers have the option to offer roaming VOIP
> services or stationary VOIP services. If you offer roaming VOIP
> you are required to provide your customers with a way to update
> their address information whenever they move their phone. It can
> either be a website they log into to change their address or a 24
> hour phone number they call, but either way you MUST provide it if
> you allow them to roam. If you do allow them to roam you have to
> get your 911 service from a VOIP 911 provider (who has connections
> to every PSAP in the country) or be connected to every PSAP in the
> country yourself because a connection to the LEC network will only
> cover you for the counties or parishes that you establish trunks for.
>
> Most VOIP providers I know sign up with a VOIP 911 provider
> because they cover a large area so it's cheaper to do that then
> have a multitude of connections through the LEC. If you decide to
> go with a stationary VOIP product, you must have the customer sign
> a waiver stating that they are aware that if they move their phone
> they will not receive 911 service. I believe the FCC ruled in the
> last year or so that if you also have to place some type of
> sticker on the phone so that the end user who uses the phone knows
> 911 is not available when you move it rather than just the person
> who ordered the phones.
>
> So the decision is not your customer's, but yours. If you choose
> to allow the customer to move their phone then you either have to
> place a sticker on the phone stating that 911 service will not be
> available to the customer OR you have to provide the customer with
> a way to change their address information when they do move the
> phone. While you could offer either option to customers based on
> how much they wanted to pay, I would think liability wise it would
> be better if you either offered it to everyone or no one at all
> because it would be too easy for one of your employees to make a
> mistake in setting someone up and not put them on the right plan.
>
> Mary Lou Carey
>
> BackUP Telecom Consulting
>
> marylou at backuptelecom.com <mailto:marylou at backuptelecom.com>
>
> Office: 615-791-9969 x 2001 <tel:615-791-9969%20x%202001>
>
> *From:*voiceops-bounces at voiceops.org
> <mailto:voiceops-bounces at voiceops.org>
> [mailto:voiceops-bounces at voiceops.org
> <mailto:voiceops-bounces at voiceops.org>] *On Behalf Of *Carlos Alvarez
> *Sent:* Friday, January 18, 2013 9:51 AM
> *To:* voiceops at voiceops.org <mailto:voiceops at voiceops.org>
> *Subject:* [VoiceOps] 911 address policy for company phones at home
>
> 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 <tel:602-889-3003>
>
>
>
>
> --
> Carlos Alvarez
> TelEvolve
> 602-889-3003
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Jan. 18, 2013