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 2020
- 22 participants
- 40 messages
STIR/SHAKEN implementation - CLI tool, HTTP API server and C library
by miconda@gmail.com
Thanks Alex! Feedback if works fine or not would be appreciated, if
someone already has access to a service where the Identity header is
sent (I can assist if one needs help to get secsipid project set up). In
Europe I expect to take much longer than in North America to see these
extensions enabled between SIP carriers.
Cheers,
Daniel
On 27.01.20 17:53, Alex Balashov wrote:
> Indeed, this is great news for the many successful operators of open-source platforms on this list.
>
> Thank you very much for your generous contribution of time to make a foray into this challenging area, Daniel. I know the large installed base of Kamailio in North America will deeply appreciate it!
>
> ? Alex
>
> ?
> Sent from my iPad
>
>> On Jan 27, 2020, at 11:11 AM, Peter Beckman <beckman at angryox.com> wrote:
>>
>> ?Thank you!!! This is great. We haven't yet had to implement, and I'm now
>> less worried about it as a result of your code. I really appreciate you
>> writing the code and putting it out there for those of us who will soon and
>> likely on a short timeline.
>>
>> Kudos Daniel!
>>
>> Beckman
>>
>>> On Mon, 27 Jan 2020, Daniel-Constantin Mierla wrote:
>>>
>>> Hello,
>>>
>>> I noticed the discussion about STIR/SHAKEN that happened on this forum a
>>> few weeks ago and for quite some time I had in my todo list the task to
>>> add support for those extensions to Kamailio SIP server, but with no
>>> real pressure to deploy them here in Europe, I kept postponing for a
>>> while (also, some people did it already for Kamailio using embedded
>>> scripting languages Lua or Python).
>>>
>>> Anyhow, as I saw the discussion here, it became fresh again and I
>>> searched the web, but I could not find any free/open tools to
>>> test/validate implementations, so it looked a bit like chicken-egg
>>> problem, therefore I created recently such a project, written in Go
>>> language, with option to build a C static or shared library.
>>>
>>> It is still very fresh code, not much tested, now with ES256 signing
>>> algorithm based on golang native support, no interoperability done with
>>> other applications. The project is available at:
>>>
>>> * https://github.com/asipto/secsipidx
>>>
>>> To be able to enable older versions of PBX/SIP servers to support
>>> STIR/SHAKEN extensions, besides the C library exports, there is an
>>> application that can run as CLI tool or HTTP API server to check or
>>> generate Identity headers. I haven't tested at all on Windows, but I
>>> expect that golang ensures good portability, not using anything OS
>>> specific in the code.
>>>
>>> I thought it worth announcing it here, in case someone wants to play
>>> with, suggest improvements or even contribute to make it easier to use
>>> on their specific deployments.
>>>
>>> Cheers,
>>> Daniel
>>>
>>> --
>>> Daniel-Constantin Mierla -- www.asipto.com
>>> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>>> Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
>>> Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
>>>
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>> ---------------------------------------------------------------------------
>> Peter Beckman Internet Guy
>> beckman at angryox.com http://www.angryox.com/
>> ---------------------------------------------------------------------------_______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
Jan. 30, 2020
STIR/SHAKEN implementation - CLI tool, HTTP API server and C library
by miconda@gmail.com
Glad to hear it looks useful for you!
The implementation so far was purely based on my understanding for the
specs, no interop testing being done as I don't have access to a service
using it already.
Anyhow, golang has native support for json and many embedded encryption
algorithms, so if some parameters need to be tuned there, should be
straightforward. Just report any issue on github project and it will be
taken care.
Cheers,
Daniel
On 27.01.20 17:11, Peter Beckman wrote:
> Thank you!!! This is great. We haven't yet had to implement, and I'm now
> less worried about it as a result of your code. I really appreciate you
> writing the code and putting it out there for those of us who will
> soon and
> likely on a short timeline.
>
> Kudos Daniel!
>
> Beckman
>
> On Mon, 27 Jan 2020, Daniel-Constantin Mierla wrote:
>
>> Hello,
>>
>> I noticed the discussion about STIR/SHAKEN that happened on this forum a
>> few weeks ago and for quite some time I had in my todo list the task to
>> add support for those extensions to Kamailio SIP server, but with no
>> real pressure to deploy them here in Europe, I kept postponing for a
>> while (also, some people did it already for Kamailio using embedded
>> scripting languages Lua or Python).
>>
>> Anyhow, as I saw the discussion here, it became fresh again and I
>> searched the web, but I could not find any free/open tools to
>> test/validate implementations, so it looked a bit like chicken-egg
>> problem, therefore I created recently such a project, written in Go
>> language, with option to build a C static or shared library.
>>
>> It is still very fresh code, not much tested, now with ES256 signing
>> algorithm based on golang native support, no interoperability done with
>> other applications. The project is available at:
>>
>> ? * https://github.com/asipto/secsipidx
>>
>> To be able to enable older versions of PBX/SIP servers to support
>> STIR/SHAKEN extensions, besides the C library exports, there is an
>> application that can run as CLI tool or HTTP API server to check or
>> generate Identity headers. I haven't tested at all on Windows, but I
>> expect that golang ensures good portability, not using anything OS
>> specific in the code.
>>
>> I thought it worth announcing it here, in case someone wants to play
>> with, suggest improvements or even contribute to make it easier to use
>> on their specific deployments.
>>
>> Cheers,
>> Daniel
>>
>> --?
>> Daniel-Constantin Mierla -- www.asipto.com
>> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>> Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
>> Kamailio World Conference - April 27-29, 2020, in Berlin --
>> www.kamailioworld.com
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>
> ---------------------------------------------------------------------------
>
> Peter Beckman?????????????????????????????????????????????????
> Internet Guy
> beckman at angryox.com????????????????????????????????
> http://www.angryox.com/
> ---------------------------------------------------------------------------
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
Jan. 30, 2020
STIR/SHAKEN implementation - CLI tool, HTTP API server and C library
by abalashov@evaristesys.com
Indeed, this is great news for the many successful operators of open-source platforms on this list.
Thank you very much for your generous contribution of time to make a foray into this challenging area, Daniel. I know the large installed base of Kamailio in North America will deeply appreciate it!
? Alex
?
Sent from my iPad
> On Jan 27, 2020, at 11:11 AM, Peter Beckman <beckman at angryox.com> wrote:
>
> ?Thank you!!! This is great. We haven't yet had to implement, and I'm now
> less worried about it as a result of your code. I really appreciate you
> writing the code and putting it out there for those of us who will soon and
> likely on a short timeline.
>
> Kudos Daniel!
>
> Beckman
>
>> On Mon, 27 Jan 2020, Daniel-Constantin Mierla wrote:
>>
>> Hello,
>>
>> I noticed the discussion about STIR/SHAKEN that happened on this forum a
>> few weeks ago and for quite some time I had in my todo list the task to
>> add support for those extensions to Kamailio SIP server, but with no
>> real pressure to deploy them here in Europe, I kept postponing for a
>> while (also, some people did it already for Kamailio using embedded
>> scripting languages Lua or Python).
>>
>> Anyhow, as I saw the discussion here, it became fresh again and I
>> searched the web, but I could not find any free/open tools to
>> test/validate implementations, so it looked a bit like chicken-egg
>> problem, therefore I created recently such a project, written in Go
>> language, with option to build a C static or shared library.
>>
>> It is still very fresh code, not much tested, now with ES256 signing
>> algorithm based on golang native support, no interoperability done with
>> other applications. The project is available at:
>>
>> * https://github.com/asipto/secsipidx
>>
>> To be able to enable older versions of PBX/SIP servers to support
>> STIR/SHAKEN extensions, besides the C library exports, there is an
>> application that can run as CLI tool or HTTP API server to check or
>> generate Identity headers. I haven't tested at all on Windows, but I
>> expect that golang ensures good portability, not using anything OS
>> specific in the code.
>>
>> I thought it worth announcing it here, in case someone wants to play
>> with, suggest improvements or even contribute to make it easier to use
>> on their specific deployments.
>>
>> Cheers,
>> Daniel
>>
>> --
>> Daniel-Constantin Mierla -- www.asipto.com
>> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>> Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
>> Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com http://www.angryox.com/
> ---------------------------------------------------------------------------_______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Jan. 27, 2020
STIR/SHAKEN implementation - CLI tool, HTTP API server and C library
by beckman@angryox.com
Thank you!!! This is great. We haven't yet had to implement, and I'm now
less worried about it as a result of your code. I really appreciate you
writing the code and putting it out there for those of us who will soon and
likely on a short timeline.
Kudos Daniel!
Beckman
On Mon, 27 Jan 2020, Daniel-Constantin Mierla wrote:
> Hello,
>
> I noticed the discussion about STIR/SHAKEN that happened on this forum a
> few weeks ago and for quite some time I had in my todo list the task to
> add support for those extensions to Kamailio SIP server, but with no
> real pressure to deploy them here in Europe, I kept postponing for a
> while (also, some people did it already for Kamailio using embedded
> scripting languages Lua or Python).
>
> Anyhow, as I saw the discussion here, it became fresh again and I
> searched the web, but I could not find any free/open tools to
> test/validate implementations, so it looked a bit like chicken-egg
> problem, therefore I created recently such a project, written in Go
> language, with option to build a C static or shared library.
>
> It is still very fresh code, not much tested, now with ES256 signing
> algorithm based on golang native support, no interoperability done with
> other applications. The project is available at:
>
> ? * https://github.com/asipto/secsipidx
>
> To be able to enable older versions of PBX/SIP servers to support
> STIR/SHAKEN extensions, besides the C library exports, there is an
> application that can run as CLI tool or HTTP API server to check or
> generate Identity headers. I haven't tested at all on Windows, but I
> expect that golang ensures good portability, not using anything OS
> specific in the code.
>
> I thought it worth announcing it here, in case someone wants to play
> with, suggest improvements or even contribute to make it easier to use
> on their specific deployments.
>
> Cheers,
> Daniel
>
> --
> Daniel-Constantin Mierla -- www.asipto.com
> www.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
> Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
Jan. 27, 2020
STIR/SHAKEN implementation - CLI tool, HTTP API server and C library
by miconda@gmail.com
Hello,
I noticed the discussion about STIR/SHAKEN that happened on this forum a
few weeks ago and for quite some time I had in my todo list the task to
add support for those extensions to Kamailio SIP server, but with no
real pressure to deploy them here in Europe, I kept postponing for a
while (also, some people did it already for Kamailio using embedded
scripting languages Lua or Python).
Anyhow, as I saw the discussion here, it became fresh again and I
searched the web, but I could not find any free/open tools to
test/validate implementations, so it looked a bit like chicken-egg
problem, therefore I created recently such a project, written in Go
language, with option to build a C static or shared library.
It is still very fresh code, not much tested, now with ES256 signing
algorithm based on golang native support, no interoperability done with
other applications. The project is available at:
? * https://github.com/asipto/secsipidx
To be able to enable older versions of PBX/SIP servers to support
STIR/SHAKEN extensions, besides the C library exports, there is an
application that can run as CLI tool or HTTP API server to check or
generate Identity headers. I haven't tested at all on Windows, but I
expect that golang ensures good portability, not using anything OS
specific in the code.
I thought it worth announcing it here, in case someone wants to play
with, suggest improvements or even contribute to make it easier to use
on their specific deployments.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
Jan. 27, 2020
RAY BAUMS Act - How are people planning on complying?
by kmcginnis@bandwidth.com
I work for Bandwidth and we are a 911 provider. The new law does require
the phone companies to make sure they have the right features to be
compliant but the law imposes the compliance ON THE ENTERPRISE manager of
their phone system. We vendors and carriers have manufacture the car with
a seat belt. It is the driver of the car (the enterprise) that gets a
ticket if they do not buckle up (comply - as in update the address data).
-----Original Message-----
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Mary Lou Carey
Sent: Friday, January 24, 2020 11:19 AM
To: Carlos Alvarez <caalvarez at gmail.com>
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] RAY BAUMS Act - How are people planning on
complying?
I don't think that you would be held responsible if the customer refused
to install phones, BUT.......it would be to your benefit to know the laws
regarding how many phones are required in a big building because it would
help cover your butt at the same time it would increases your sales.
So if that company were my customer, I'd say something like .'Did you know
that the law requires you to have a working phone every "_____" sq feet?
If you don't want to pay the full amount for an outside line, an
alternative option that's not as costly for you is to have us set you up
with a phone that only connects to the operator and emergency services.
That way you're covered if there's an emergency and you don't have to
worry about being sued should one of your employees not be able to reach
911 in time!"
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2020-01-23 03:54 PM, Carlos Alvarez wrote:
> The number one user of 911 service for us is a chain of urgent care
> clinics that use our hosted service. Several times a week, someone
> will casually walk in saying they think they're having a heart attack
> or stroke. Some drive by the ER to get there. So yeah, what Mary
> said. And if you read the cases that lead to these laws, you will see
> a string of poor decisions leading to injury and death.
>
> I haven't figured out how they will break out responsible parties on
> all of this. As a hosted provider, are we bound to FORCE people to
> put phones in the right places? To buy more phones/DIDs and pay for
> more 911 locations? Or do we need to just tell them that they are
> responsible for it? I can't quite get a solid answer on this also.
>
> For example, we have a customer whose manufacturing facility is well
> over the size that would allow a phone or two as legal coverage. They
> have balked at putting phones out ever 6-7k square feet on poles and
> such. Is that our problem? I don't think so.
>
> On Thu, Jan 23, 2020 at 1:21 PM Mary Lou Carey
> <marylou at backuptelecom.com> wrote:
>
>> Logically it makes sense that if your phone says it can't make 911
>> calls, you would look for another phone. The problem is that when
>> people are in survival mode or trauma mode, they don't do things that
>> make sense! When I was much younger I worked for a medical clinic and
>> I remember them telling us that if there's a natural disaster people
>> may show up at the clinic thinking it's a hospital because when
>> people are in trauma mode, they don't think rationally. They'll do
>> crazy things.....like call their doctor when they're having a heart
>> attack and ask if they should go to the hospital or show up at a
>> clinic thinking it's a hospital and demand immediate care.
>>
>> I think the same mentality applies here. People see a phone and if it
>> has a dial tone they will attempt to make a 911 call regardless of
>> whether there's a sticker stating that it can't make 911 calls. So
>> its always best to provide 911 service if your customers can
>> originate calls.
>>
>> To get 911 service for your customers you can either order 911 trunks
>> for each county through the ILEC (the expensive route) or you can
>> connect with a VOIP 911 provider that will establish two diverse
>> connections between them and your switch. You just send the VOIP 911
>>
>> provider the traffic and they'll take care of routing your calls to
>> the appropriate PSAP. You're just responsible for keeping your
>> customer's address location up to date in the ALI database.
>>
>> I know at one time that there was a ruling that you had to provide
>> your customer a way to update their location if you allowed them to
>> move their phone to another location. I don't know if that was
>> changed or the work around still remains that you can put a sticker
>> on the phone stating that if you move your phone to another location
>> it may not connect to the right 911 center. At any rate.....I
>> wouldn't mess around with providing 911 services because the FCC
>> doesn't consider it optional. The only waiver I"m aware of is the one
>> that states your customers are only terminating traffic onto your
>> network....not making any originating calls!
>>
>> MARY LOU CAREY
>> BackUP Telecom Consulting
>> Office: 615-791-9969
>> Cell: 615-796-1111
>>
>> On 2020-01-23 01:47 PM, Pete Mundy wrote:
>>> I guess different people have different interpretation of that
>> wording
>>> :)
>>>
>>> To me it seems UNreasonable to assume that a phone or device with
>> a
>>> sticker on it that says "This phone does not work for emergency
>> calls"
>>> can call emergency services.
>>>
>>>
>>>> On 24/01/2020, at 6:46 AM, Carlos Alvarez <caalvarez at gmail.com>
>> wrote:
>>>>
>>>> I believe that the stickers on home phones may not really cover
>> the
>>>> liability. The wording is something like: A phone or device
>> that a
>>>> person would reasonably assume can call emergency services." So
>> the
>>>> softphone is obviously different, but a physical phone at home
>> seems
>>>> like it must still work properly.
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 24, 2020
RAY BAUMS Act - How are people planning on complying?
by marylou@backuptelecom.com
I don't think that you would be held responsible if the customer refused
to install phones, BUT.......it would be to your benefit to know the
laws regarding how many phones are required in a big building because it
would help cover your butt at the same time it would increases your
sales.
So if that company were my customer, I'd say something like .'Did you
know that the law requires you to have a working phone every "_____" sq
feet? If you don't want to pay the full amount for an outside line, an
alternative option that's not as costly for you is to have us set you up
with a phone that only connects to the operator and emergency services.
That way you're covered if there's an emergency and you don't have to
worry about being sued should one of your employees not be able to reach
911 in time!"
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2020-01-23 03:54 PM, Carlos Alvarez wrote:
> The number one user of 911 service for us is a chain of urgent care
> clinics that use our hosted service. Several times a week, someone
> will casually walk in saying they think they're having a heart attack
> or stroke. Some drive by the ER to get there. So yeah, what Mary
> said. And if you read the cases that lead to these laws, you will see
> a string of poor decisions leading to injury and death.
>
> I haven't figured out how they will break out responsible parties on
> all of this. As a hosted provider, are we bound to FORCE people to
> put phones in the right places? To buy more phones/DIDs and pay for
> more 911 locations? Or do we need to just tell them that they are
> responsible for it? I can't quite get a solid answer on this also.
>
> For example, we have a customer whose manufacturing facility is well
> over the size that would allow a phone or two as legal coverage. They
> have balked at putting phones out ever 6-7k square feet on poles and
> such. Is that our problem? I don't think so.
>
> On Thu, Jan 23, 2020 at 1:21 PM Mary Lou Carey
> <marylou at backuptelecom.com> wrote:
>
>> Logically it makes sense that if your phone says it can't make 911
>> calls, you would look for another phone. The problem is that when
>> people
>> are in survival mode or trauma mode, they don't do things that make
>> sense! When I was much younger I worked for a medical clinic and I
>> remember them telling us that if there's a natural disaster people
>> may
>> show up at the clinic thinking it's a hospital because when people
>> are
>> in trauma mode, they don't think rationally. They'll do crazy
>> things.....like call their doctor when they're having a heart attack
>> and
>> ask if they should go to the hospital or show up at a clinic
>> thinking
>> it's a hospital and demand immediate care.
>>
>> I think the same mentality applies here. People see a phone and if
>> it
>> has a dial tone they will attempt to make a 911 call regardless of
>> whether there's a sticker stating that it can't make 911 calls. So
>> its
>> always best to provide 911 service if your customers can originate
>> calls.
>>
>> To get 911 service for your customers you can either order 911
>> trunks
>> for each county through the ILEC (the expensive route) or you can
>> connect with a VOIP 911 provider that will establish two diverse
>> connections between them and your switch. You just send the VOIP 911
>>
>> provider the traffic and they'll take care of routing your calls to
>> the
>> appropriate PSAP. You're just responsible for keeping your
>> customer's
>> address location up to date in the ALI database.
>>
>> I know at one time that there was a ruling that you had to provide
>> your
>> customer a way to update their location if you allowed them to move
>> their phone to another location. I don't know if that was changed or
>> the
>> work around still remains that you can put a sticker on the phone
>> stating that if you move your phone to another location it may not
>> connect to the right 911 center. At any rate.....I wouldn't mess
>> around
>> with providing 911 services because the FCC doesn't consider it
>> optional. The only waiver I"m aware of is the one that states your
>> customers are only terminating traffic onto your network....not
>> making
>> any originating calls!
>>
>> MARY LOU CAREY
>> BackUP Telecom Consulting
>> Office: 615-791-9969
>> Cell: 615-796-1111
>>
>> On 2020-01-23 01:47 PM, Pete Mundy wrote:
>>> I guess different people have different interpretation of that
>> wording
>>> :)
>>>
>>> To me it seems UNreasonable to assume that a phone or device with
>> a
>>> sticker on it that says "This phone does not work for emergency
>> calls"
>>> can call emergency services.
>>>
>>>
>>>> On 24/01/2020, at 6:46 AM, Carlos Alvarez <caalvarez at gmail.com>
>> wrote:
>>>>
>>>> I believe that the stickers on home phones may not really cover
>> the
>>>> liability. The wording is something like: A phone or device
>> that a
>>>> person would reasonably assume can call emergency services." So
>> the
>>>> softphone is obviously different, but a physical phone at home
>> seems
>>>> like it must still work properly.
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Jan. 24, 2020
RAY BAUMS Act - How are people planning on complying?
by David.Zilk@cdk.com
?For example, we have a customer whose manufacturing facility is well over the size that would allow a phone or two as legal coverage. They have balked at putting phones out ever 6-7k square feet on poles and such. Is that our problem? I don't think so.?
I don?t believe that there is any requirement to have a phone covering every place in the building. The only requirement is that wherever there IS a phone, you have to provide good enough location information to get the first responder to it. If someone needs to hike a mile to get to the phone, that is just the way it is.
David
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Carlos Alvarez
Sent: Thursday, January 23, 2020 1:54 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] RAY BAUMS Act - How are people planning on complying?
The number one user of 911 service for us is a chain of urgent care clinics that use our hosted service. Several times a week, someone will casually walk in saying they think they're having a heart attack or stroke. Some drive by the ER to get there. So yeah, what Mary said. And if you read the cases that lead to these laws, you will see a string of poor decisions leading to injury and death.
I haven't figured out how they will break out responsible parties on all of this. As a hosted provider, are we bound to FORCE people to put phones in the right places? To buy more phones/DIDs and pay for more 911 locations? Or do we need to just tell them that they are responsible for it? I can't quite get a solid answer on this also.
For example, we have a customer whose manufacturing facility is well over the size that would allow a phone or two as legal coverage. They have balked at putting phones out ever 6-7k square feet on poles and such. Is that our problem? I don't think so.
On Thu, Jan 23, 2020 at 1:21 PM Mary Lou Carey <marylou at backuptelecom.com<mailto:marylou at backuptelecom.com>> wrote:
Logically it makes sense that if your phone says it can't make 911
calls, you would look for another phone. The problem is that when people
are in survival mode or trauma mode, they don't do things that make
sense! When I was much younger I worked for a medical clinic and I
remember them telling us that if there's a natural disaster people may
show up at the clinic thinking it's a hospital because when people are
in trauma mode, they don't think rationally. They'll do crazy
things.....like call their doctor when they're having a heart attack and
ask if they should go to the hospital or show up at a clinic thinking
it's a hospital and demand immediate care.
I think the same mentality applies here. People see a phone and if it
has a dial tone they will attempt to make a 911 call regardless of
whether there's a sticker stating that it can't make 911 calls. So its
always best to provide 911 service if your customers can originate
calls.
To get 911 service for your customers you can either order 911 trunks
for each county through the ILEC (the expensive route) or you can
connect with a VOIP 911 provider that will establish two diverse
connections between them and your switch. You just send the VOIP 911
provider the traffic and they'll take care of routing your calls to the
appropriate PSAP. You're just responsible for keeping your customer's
address location up to date in the ALI database.
I know at one time that there was a ruling that you had to provide your
customer a way to update their location if you allowed them to move
their phone to another location. I don't know if that was changed or the
work around still remains that you can put a sticker on the phone
stating that if you move your phone to another location it may not
connect to the right 911 center. At any rate.....I wouldn't mess around
with providing 911 services because the FCC doesn't consider it
optional. The only waiver I"m aware of is the one that states your
customers are only terminating traffic onto your network....not making
any originating calls!
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2020-01-23 01:47 PM, Pete Mundy wrote:
> I guess different people have different interpretation of that wording
> :)
>
> To me it seems UNreasonable to assume that a phone or device with a
> sticker on it that says "This phone does not work for emergency calls"
> can call emergency services.
>
>
>> On 24/01/2020, at 6:46 AM, Carlos Alvarez <caalvarez at gmail.com<mailto:caalvarez at gmail.com>> wrote:
>>
>> I believe that the stickers on home phones may not really cover the
>> liability. The wording is something like: A phone or device that a
>> person would reasonably assume can call emergency services." So the
>> softphone is obviously different, but a physical phone at home seems
>> like it must still work properly.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
> https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
----------------------------------------------------------------------
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
Jan. 23, 2020
RAY BAUMS Act - How are people planning on complying?
by caalvarez@gmail.com
The number one user of 911 service for us is a chain of urgent care clinics
that use our hosted service. Several times a week, someone will casually
walk in saying they think they're having a heart attack or stroke. Some
drive by the ER to get there. So yeah, what Mary said. And if you read
the cases that lead to these laws, you will see a string of poor decisions
leading to injury and death.
I haven't figured out how they will break out responsible parties on all of
this. As a hosted provider, are we bound to FORCE people to put phones in
the right places? To buy more phones/DIDs and pay for more 911 locations?
Or do we need to just tell them that they are responsible for it? I can't
quite get a solid answer on this also.
For example, we have a customer whose manufacturing facility is well over
the size that would allow a phone or two as legal coverage. They have
balked at putting phones out ever 6-7k square feet on poles and such. Is
that our problem? I don't think so.
On Thu, Jan 23, 2020 at 1:21 PM Mary Lou Carey <marylou at backuptelecom.com>
wrote:
> Logically it makes sense that if your phone says it can't make 911
> calls, you would look for another phone. The problem is that when people
> are in survival mode or trauma mode, they don't do things that make
> sense! When I was much younger I worked for a medical clinic and I
> remember them telling us that if there's a natural disaster people may
> show up at the clinic thinking it's a hospital because when people are
> in trauma mode, they don't think rationally. They'll do crazy
> things.....like call their doctor when they're having a heart attack and
> ask if they should go to the hospital or show up at a clinic thinking
> it's a hospital and demand immediate care.
>
> I think the same mentality applies here. People see a phone and if it
> has a dial tone they will attempt to make a 911 call regardless of
> whether there's a sticker stating that it can't make 911 calls. So its
> always best to provide 911 service if your customers can originate
> calls.
>
> To get 911 service for your customers you can either order 911 trunks
> for each county through the ILEC (the expensive route) or you can
> connect with a VOIP 911 provider that will establish two diverse
> connections between them and your switch. You just send the VOIP 911
> provider the traffic and they'll take care of routing your calls to the
> appropriate PSAP. You're just responsible for keeping your customer's
> address location up to date in the ALI database.
>
> I know at one time that there was a ruling that you had to provide your
> customer a way to update their location if you allowed them to move
> their phone to another location. I don't know if that was changed or the
> work around still remains that you can put a sticker on the phone
> stating that if you move your phone to another location it may not
> connect to the right 911 center. At any rate.....I wouldn't mess around
> with providing 911 services because the FCC doesn't consider it
> optional. The only waiver I"m aware of is the one that states your
> customers are only terminating traffic onto your network....not making
> any originating calls!
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2020-01-23 01:47 PM, Pete Mundy wrote:
> > I guess different people have different interpretation of that wording
> > :)
> >
> > To me it seems UNreasonable to assume that a phone or device with a
> > sticker on it that says "This phone does not work for emergency calls"
> > can call emergency services.
> >
> >
> >> On 24/01/2020, at 6:46 AM, Carlos Alvarez <caalvarez at gmail.com> wrote:
> >>
> >> I believe that the stickers on home phones may not really cover the
> >> liability. The wording is something like: A phone or device that a
> >> person would reasonably assume can call emergency services." So the
> >> softphone is obviously different, but a physical phone at home seems
> >> like it must still work properly.
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Jan. 23, 2020
RAY BAUMS Act - How are people planning on complying?
by marylou@backuptelecom.com
Logically it makes sense that if your phone says it can't make 911
calls, you would look for another phone. The problem is that when people
are in survival mode or trauma mode, they don't do things that make
sense! When I was much younger I worked for a medical clinic and I
remember them telling us that if there's a natural disaster people may
show up at the clinic thinking it's a hospital because when people are
in trauma mode, they don't think rationally. They'll do crazy
things.....like call their doctor when they're having a heart attack and
ask if they should go to the hospital or show up at a clinic thinking
it's a hospital and demand immediate care.
I think the same mentality applies here. People see a phone and if it
has a dial tone they will attempt to make a 911 call regardless of
whether there's a sticker stating that it can't make 911 calls. So its
always best to provide 911 service if your customers can originate
calls.
To get 911 service for your customers you can either order 911 trunks
for each county through the ILEC (the expensive route) or you can
connect with a VOIP 911 provider that will establish two diverse
connections between them and your switch. You just send the VOIP 911
provider the traffic and they'll take care of routing your calls to the
appropriate PSAP. You're just responsible for keeping your customer's
address location up to date in the ALI database.
I know at one time that there was a ruling that you had to provide your
customer a way to update their location if you allowed them to move
their phone to another location. I don't know if that was changed or the
work around still remains that you can put a sticker on the phone
stating that if you move your phone to another location it may not
connect to the right 911 center. At any rate.....I wouldn't mess around
with providing 911 services because the FCC doesn't consider it
optional. The only waiver I"m aware of is the one that states your
customers are only terminating traffic onto your network....not making
any originating calls!
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2020-01-23 01:47 PM, Pete Mundy wrote:
> I guess different people have different interpretation of that wording
> :)
>
> To me it seems UNreasonable to assume that a phone or device with a
> sticker on it that says "This phone does not work for emergency calls"
> can call emergency services.
>
>
>> On 24/01/2020, at 6:46 AM, Carlos Alvarez <caalvarez at gmail.com> wrote:
>>
>> I believe that the stickers on home phones may not really cover the
>> liability. The wording is something like: A phone or device that a
>> person would reasonably assume can call emergency services." So the
>> softphone is obviously different, but a physical phone at home seems
>> like it must still work properly.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Jan. 23, 2020