911 CID Masking

[TechCheck]

I know this has been asked/begged for in the past, but can someone provide an update on when 911 CID masking will be available? We are losing deals because other systems can send a different CID when someone dials 911.

Thanks
Brian

 

[cobaltit]

3CX can as well with some administrative tweaking. But not easy as what FreePBX has done with a e911 CID.

 

[TechCheck]

3CX can as well with some administrative tweaking. But not easy as what FreePBX has done with a e911 CID.

Hold the phone!! Please share more information or point me to a post. I am very interested.

Thanks,
Brian

 

[cobaltit]

Basically you need a provider than either do IP authenticated trunks (we can) or will let you do multiple registrations. Then it's a matter of setting the required 911 CID per trunk and using outbound rules to match extensions or extension groups and then routing it out that dedicated trunk. It's hack, and it gets ugly real quick with more than a handful of separate 911 CIDs needed but it's doable.

 

[SweetAction]

I wonder if we can build something to solve this pain point easier. This method does have downsides though...

1: Define the number 911 as an IVR in 3CX
2: Set destination no input to a CFD
3: CFD looks at a SQL table which defines extension to outbound CID

1. Store existing CID
2. Update outbound CID for extension based on table (Can you do this via the API?)
3. Pass call to 911
4. When call completes, change CID back to previous CID

Downside (besides being a whole lot more complex) is you wouldn't be able to define 911 as emergency number, which mean license limits will apply to calls, no notifications, etc. Could probaly solve the notifications inside the CFD.

 

[leejor]

Have you read through this...

https://www.3cx.com/community/threads/ability-to-set-a-caller-id-for-outbound-calls.42840/page-8

unfortunatly, it's been "In Progress" for a few years now.

 

[TechCheck]

Basically you need a provider than either do IP authenticated trunks (we can) or will let you do multiple registrations. Then it's a matter of setting the required 911 CID per trunk and using outbound rules to match extensions or extension groups and then routing it out that dedicated trunk. It's hack, and it gets ugly real quick with more than a handful of separate 911 CIDs needed but it's doable.

Ahh, in a school setting with 400 extensions and therefore 400 different 911 CIDs that would get pretty messy.

Brian

 

[cobaltit]

Yes, but it is doable but in theory you'd only have to do it once.