[VoiceOps] Ray Baum's act and all-softphone deployments

Carlos Alvarez caalvarez at gmail.com
Mon Sep 27 16:35:34 EDT 2021


Three meters is three floors of resolution, depending on whether the person
is standing or laying on the ground.


On Mon, Sep 27, 2021 at 1:34 PM Mark Lindsey <lindsey at e-c-group.com> wrote:

> In the top 25 cellular market areas, nationwide cell phone providers are
> already required to provide Z-axis (elevation) data within 3 meters for 80%
> of calls [for compatible devices].  The requirements increase each year; by
> 2026, *all* cellular providers are required to provide z-axis precision
> for dispatchable location of +/- 3 meters everywhere in the US.
>
> This is all in addition to providing +/- 50 meter horizontal (x, y axis,
> also known as latitude and longitude) precision for 911 calls.
>
>
> https://www.fcc.gov/public-safety-and-homeland-security/policy-and-licensing-division/911-services/general/location-accuracy-indoor-benchmarks
>
>
> *Mark R Lindsey, SMTS* | +1-229-316-0013 | mark at ecg.co |* https://ecg.co/lindsey/
> <https://ecg.co/lindsey/>*
>
>
>
>
>
>
>
>
> On Sep 27, 2021, at 4:07 PM, Carlos Alvarez <caalvarez at gmail.com> wrote:
>
> They probably don't, and I don't think they are covered by the same
> law/requirements.  Also, they have far more schills(COUGH) I mean lobbyists
> in congress.
>
> FLOOR could be determined by AP lists, probably.  Maybe.  Specific office
> seems impossible currently.
>
>
> On Mon, Sep 27, 2021 at 1:05 PM Alex Balashov via VoiceOps <
> voiceops at voiceops.org> wrote:
>
>> And how do the cell phone operators know what floor you’re on?
>>
>>>> Sent from mobile, with due apologies for brevity and errors.
>>
>> On Sep 27, 2021, at 3:49 PM, Carlos Alvarez <caalvarez at gmail.com> wrote:
>>
>> 
>> It used to be, then the whole Ray Baum thing, and now it's not.  Short
>> story:  911 call failed to identify the specific floor/office, person
>> died.  Now you have to provide enough info for a first responder to reach a
>> person without help, which also means opening main doors if needed.
>> There's simply no way that a laptop will give that specificity.  Will it be
>> sufficient to say that they are near the AP on the third floor southwest
>> corner?  The letter of the law seems to say "no."
>>
>>
>>
>> On Mon, Sep 27, 2021 at 12:40 PM Alex Balashov via VoiceOps <
>> voiceops at voiceops.org> wrote:
>>
>>> I wonder if doing GeoIP via a commercial database like MaxMind—and we
>>> all know how perfect a location mechanism that is—could be construed as a
>>> sufficient “best effort” in this case.
>>>
>>> > On Sep 27, 2021, at 3:28 PM, Carlos Alvarez <caalvarez at gmail.com>
>>> wrote:
>>> >
>>> > Ours doesn't, but that's a good idea to share with the vendor.  But in
>>> most cases, people are using the softphone on a laptop and there's no
>>> native phone app, nor a GPS, nor any other location info other than
>>> proximate wi-fi networks.
>>> >
>>> > I can see no feasible way to meet the letter of the law, and hate to
>>> be depending on the good graces of a bureaucrat to know that it's an
>>> impossible task.
>>>
>>> --
>>> Alex Balashov | Principal | Evariste Systems LLC
>>>
>>> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
>>> Web: http://www.evaristesys.com/, http://www.csrpswitch.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
>>
>> _______________________________________________
>> 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20210927/bde50f54/attachment-0001.htm>


More information about the VoiceOps mailing list