911 with 3CX Update 5 Alpha (Feedback)

[SyncWave]

I'm glad you're working to improve this, however, I feel the wrong approach is being taken to handling emergency calling. Creating an array of trunks (often to the same provider) to chunk out Outbound DID's on various extensions if 911 is dialed simply manipulate caller ID output seems overly convoluted and complex. Typically we don't need to select different trunks per DID if 911 is dialed, we need to set different Outbound CID if 911 is dialed. We can configure Outbound CID per extension already, all we need is the option to configure an Emergency CID per extension.

In many multi-site deployments, its desired for all extensions to have the same outbound CID, but with multi-site, work from home, and mobile we need to be able to quickly and easily set outbound CID per extension if 911 is dialed. So really each extensions just needs a "Outbound Caller ID" and "Emergency Caller ID" boxes (FreePBX has this). It would also be great if we could give a permission to allow each extension to change this emergency value from mobile or webclient (Voyant/Broadsoft has this). If there was an option in mobile we could enable to toggle cell based 911 data (GPS) when off Wi-Fi, that would be great too (Voyant/Broadsoft has this)!

 

[SyncWave]

These concerns primarily apply to cloud hosted multi-site deployments and recent pandemic developments. With everyone working remote and needing a their own DID with different E911 associations. In some temporary cases, the Emergency DID may need to be a DID not associated with any Trunk. Also, with all the location accuracy wireless mandates coming out, E911 for mobile extensions really needs the ability to pass through GPS data which also has nothing to do with a trunk.

A great start really would be a "Emergency Call ID" box right under "Outbound Caller ID" on each extension.

 

[Evolute IT]

These concerns primarily apply to cloud hosted multi-site deployments and recent pandemic developments. With everyone working remote and needing a their own DID with different E911 associations. In some temporary cases, the Emergency DID may need to be a DID not associated with any Trunk. Also, with all the location accuracy wireless mandates coming out, E911 for mobile extensions really needs the ability to pass through GPS data which also has nothing to do with a trunk.

A great start really would be a "Emergency Call ID" box right under "Outbound Caller ID" on each extension.

There's already a way via Extension Groups, DIDs and Settings -> General -> Emergency.

 

[myrich22]

Is there a database / website that has all the local PSAP 911 equivalent phone numbers? For my work-at-home users, I was thinking of an outbound 911 rule to route 911 to the local emergency number where 911 goes for their specific location. For example, Las Vegas NV is 702 828 9111 . My current sip provider (call centric) doesn't support the outbound emergency did / address from 3CX. So, I'm planning multiple accounts (trunks) for remote offices, but not for the work-at home users. Or am I'm heading in the wrong direction?

 

[SyncWave]

There's already a way via Extension Groups, DIDs and Settings -> General -> Emergency.

Not really the same. I addressed what they are doing in the section you referenced. It's feedback for a better more flexible way.

 

[myrich22]

!!! Hello. At least for me, using outbound rules for 911 is going to work better than the new emergency settings (except there is no email notifications in the outbound rules). With the emergency settings, there is no way to override the number dialed. For example, if I dial 911 from my phone (as a remote user), I want to route it to my local emergency dispatch ( 972 771 7724 ) , NOT pass through 911 to a trunk. So, as it stands, I'll have to move ALL 911 (for ALL USERS) out of emergency settings back to outbound rules or 911 for me (and my other remote users) won't work correctly. !!!

 

[cobaltit]

It sounds like you are just trying to avoid paying Call Centric for e911? That's exactly what that is for. Looking at the CID and routing to the local PSAP without having to do what you are asking for. But yes if you are trying to bypass that process you'll need to use outbound rules.

 

[myrich22]

It isn't really trying to "avoid". It is only about $5/month per remote user. But, Call Centric makes it a pain. They don't have "master" accounts. So, I would need to setup a totally separate account for EACH remote user. All separate invoices. Make my expense report a total nightmare. I'm sure for some customers, they will have to switch trucks. I suggest that the approach that 3CX and Call Centric are using is going to be a legal compliance issue. It just isn't realistic to setup an account for EACH and EVERY remote user. That said, maybe what has been done will work fine for many 3CX installs. But, seems like most have remote users and this will be an issue.

 

[cobaltit]

Eww.. I'd double-check with Call Centric to make sure it's not because of the account type you are under. We don't have any such requirements, just simply updating the address tied to the number.