Next year's e911 requirements- needed sooner!

[DDJohn]

We have 12 locations and need to be able to define e911 addressing per location ahead of the new e911 requirements for next year for a new office(municipality requirements).

That would be easy enough to do if everyone had just one assigned office, but we use hotdesking A LOT. So for example to define an outbound CID for a user in the Manhattan office today, would make it inaccurate tomorrow when she is in the Bronx office, and there's no way we're going to be able to change folks' CIDs every day if they moved. That would be awful!

At 12 locations, even if we could do 1911, 2911, 3911.... (which I read the new e911 will require that this is not admissible) I'd run out of prefixes 9 offices in.

We are exclusively Yealink at our facilities, so I tried going through the settings, but did not see anything that would let me set it per hardware (which DOES stay in one place...)

We have the each offices' DID mapped to its e911 required location, I just need a way to apply these DIDs to my floating hotdesk users... so I tried looking in the Hotdesking settings

There was an aha moment- if you have to define the MAC address to create a hotdesk config for a phone, then the system knows the MAC of the hardware that is processing a call.

PROPOSED SOLUTION: Let us map a CID to MAC addresses in the Hotdesking module, and we solve the whole floating user issue.


Is there anything at all like this in the offing? I tried to post in suggestions, but I cannot post there for some reason.

 

[AWS2P]

reason you can't post in IDEAS is you need to be gold or more level to be granted to post or Premier customer

 

[cobaltit]

3CX just put a blog post regarding the roadmap, and it's not happening this year:

https://www.3cx.com/blog/releases/v16-roadmap/

 

[DDJohn]

3CX just put a blog post regarding the roadmap, and it's not happening this year:

https://www.3cx.com/blog/releases/v16-roadmap/

So what is 3cx's suggestion to workaround MANDATORY, FEDERAL requirements?

 

[craigreilly]

Separate 911 trunks for each location won't work because of the hotdesking scenario...
This does seem problematic.

 

[cobaltit]

Can you link to the mandatory, federal requirements 3CX is not meeting today?

My understanding is that Kari's law (which 3CX already supports) goes into effect on 2/16/2020 and that Section 506 of RAY BAUM'S Act dealing with e911 and dispatchable location requirements has no set date. A one year time frame for implementation was proposed which means the earliest implementation requirement would be 8/1/2020 based off the adoption on 81/2019 and this will likely get pushed back. So it seems 3CX's road map has this being a feature before the it's an actual requirement.

 

[craigreilly]

(municipality requirements)

perhaps user has some local requirements to meet?

 

[DDJohn]

Can you link to the mandatory, federal requirements 3CX is not meeting today?

If I change a hotdesked user's CID to reflect the office she is at every single day, then sure, 3cx is in compliance.

What I'm asking is for the system to recognize MAC addresses or IP scopes of 911 call originating phones and to make the distinction as to what outbound CID it uses accordingly, so that the e911 information is correct, EVERY day, without having to check which office Suzie is floating at today.

Because you KNOW 50 people aren't going to check in every day to tell me which site they are at, nor am I going to have time to manually change their outbound CID everyday.

It's not that it isn't technically compliant, it's that it isn't sustainable as is.

 

[cobaltit]

I understand your administrative headache, as does everyone else who has ever had to admin a setup. Heck I even started a e911 thread and lamented why 3CX hasn't implemented something FreePBX was doing almost 20 years ago. But your response to my post about their roadmap was regarding mandatory, federal requirements of which there are none to date (other than the original e911 regs). It appears 3CX will have a solution before this is required by law, but I wouldn't expect anything sooner than that. What would be nice would be for 3CX to make an official statement that they will be compliant by whatever required date so people can provide that for opportunities that want to purchase now and know that it will be a compliant solution.

 

[YiannisH_3CX]

Please note that we are looking into this and we are in contact with some supported providers on what is the best way to implement this. We will be ready before the deadline arrives.

 

[simply7]

A good solution may be to create Device Groups. You could assign things like e911 numbers, Shared Parking numbers, pickup groups, office hours, MOH, etc.