SIP trunks and e911

[Matt Waechter]

I'm just interested in seeing what you all are doing for SIP trunks and e911 regulations. Are you selling enhanced DID's instead of regular DID's or handling e911 info via the trunk. Customer wants to send their outbound caller ID not corporate number. Which has me leaning towards enhanced DID's. Most of these customers are at multiple sites so it's either multiple trunks or eDID's.

 

[craigreilly]

In a single office setup...
We have 1 trunk with 2 registrations: one via username/password and one via IP.
Individual extensions use their own Caller ID and the username trunk - but calls to 911 use the IP authorized trunk.
There is an enhancement request that is several years old - and many replies and votes... https://www.3cx.com/community/threads/ability-to-set-a-caller-id-for-outbound-calls.42840/unread

 

[Matt Waechter]

In a single office setup...
We have 1 trunk with 2 registrations: one via username/password and one via IP.
Individual extensions use their own Caller ID and the username trunk - but calls to 911 use the IP authorized trunk.
There is an enhancement request that is several years old - and many replies and votes... https://www.3cx.com/community/threads/ability-to-set-a-caller-id-for-outbound-calls.42840/unread

Thank you Craig, I have seen that one and voted on it but it seems like we haven't gotten traction with 3CX on it yet. Just hoping to see what everyone else is doing until we can have proper e911 enhancements built in. Enjoy the day

 

[cobaltit]

Everyone else is doing the only thing that can be done. Enhanced DID is a provider term typically indicating whether e911 service (among other feature) is included, but has no bearing on 3CX. From a 3CX persepective, you basically have three options:

• If every extension needs to show their own DID when they call out, then you have to have e911 enabled for each DID (enhanced DID as your provider calls it)
• If you don't care about the DID that is displayed for outbound calls then you reduce the e911 requirements to unique DIDs per physical location. So all devices at location A displays 1 DID for outbound, location B another, etc.
• If all extensions need to display the corporate number then your only option is multiple trunks per e911 location with corresponding outbound rules. This is an administrative nightmare and pretty much not worth doing as noone wants to be responsible for injury/death/lawsuit because of a single fat-fingered mistake.

Why 3CX can't do what FreePBX has been doing for years I have no idea. I can only imagine it's something due to the SIP stack they are built-in on but even a simple announcement that it's not feasible due to XXX would be an improvement over the current state. As it stands it seems like they refuse to add a simple extension field (or better yet on the phone provisioning tab now that multiple devices per extension on supported) and a couple lines of code to the effect of if emergency number is dialed and if e911 number field on the phone tab exists then use that for outbound CID.