Ray Baum's Act inquiry

[Colem92]

Hello!

I'm not sure if this would be the correct spot for this post, but I was wondering if anyone had any information on how 3CX will be handling 911 caller locations to comply with Ray Baum's Act? I haven't had much luck researching, or contacting customer support. Any information would be greatly appreciated!

Thanks,
Cole

 

[Vali_3CX]

https://www.3cx.com/community/threads/911-compliance-911-notifier.66161/

 

[Colem92]

https://www.3cx.com/community/threads/911-compliance-911-notifier.66161/

Does 3CX drop all 911 emergency calls to the cellular provider?

 

[SweetAction]

So you are likely not going to like this answer, but 3CX does technically comply today.

Per the FCC

RAY BAUM’S Act emphasizes the importance of making dispatchable location information from all 911 calls available to PSAPs, regardless of the technological platform used. The FCC states “dispatchable location means a location delivered to the public safety answering point (PSAP) with a 911 call that consists of the validated street address of the calling party, plus additional information such as suite, apartment or similar information.”

You can, today, in 3CX, ensure that when an extension dials a number it's outbound caller ID is set to xxxxxxxxx.

You will need to register that number with your sip trunk provider to have a specific address / location information. And since you can have that outbound caller ID be different for each extension you can have specific location information for each extension.

It's not pretty by any means (hence the idea thread) but it's doable.

And no, 3CX doesn't drop 911 to the cellular provider. This part is still an issue (also if the phone changes locations it's an issue as well). You could just ban calling 911 from the system too if you want.

 

[Colem92]

So you are likely not going to like this answer, but 3CX does technically comply today.

Per the FCC

You can, today, in 3CX, ensure that when an extension dials a number it's outbound caller ID is set to xxxxxxxxx.

You will need to register that number with your sip trunk provider to have a specific address / location information. And since you can have that outbound caller ID be different for each extension you can have specific location information for each extension.

It's not pretty by any means (hence the idea thread) but it's doable.

And no, 3CX doesn't drop 911 to the cellular provider. This part is still an issue (also if the phone changes locations it's an issue as well). You could just ban calling 911 from the system too if you want.

Thank you for this information! Is there any particular method you'd recommend going about, when blocking 911 within 3CX? We believe this might be the best route for us to take.

 

[SweetAction]

 

[cobaltit]

So I'm not sure if you read the thread @Vali_3CX linked but in there, I mentioned an edge case where blocking 911 from the app could be an issue.

 

[Vali_3CX]

We're working on this.

 

[Vali_3CX]

@Colem92
We've just released on TestFlight the Beta version of iOS client handling this issue, please have a look
https://www.3cx.com/blog/releases/ios-beta-ray-baum-act/

Tomorrow we plan to release the Android beta client with the same support.

 

[alextannenbaum]

@Colem92
We've just released on TestFlight the Beta version of iOS client handling this issue, please have a look
https://www.3cx.com/blog/releases/ios-beta-ray-baum-act/

Tomorrow we plan to release the Android beta client with the same support.

What happens if the 3CX Android App is installed on a device without an active SIM card? Will the E911 call go through the PBX, or will it not work at all?

 

[SweetAction]

This thread has a lot of information about different situations and what happens:
https://www.3cx.com/community/threads/new-ios-client-beta-supports-ray-baum-act.87404/