multi-location e911 sanity check please.

[dandenson]

Just hoping someone can look this over and see if I'm on track. This is for a single system that handles multiple physical locations. key point here is that there will be a virtual call center that handles all locations and calls will ring at both the location and to call center agents so a single systems fits that the best. The only real issue I'm running into is handling e911, and I think I've got a working solution here. Note, this is running in EC2.

I've got a number of inbound trunks, they are all set as inbound only. This handles the 5 origination servers with voip innovations.

For each location/911 address, I have an additional trunk (actually 2) for that with the main number being the e911 associated number and pointing to a termination server. Outbound calls over these trunks have the main trunk number set to match the location so the provider can match e911 records with numbers.

Extensions at each location get put into an extension group for that location. ie, 4 phones at location 1 are in group 'location1' and so on.

For each location, I have 4 outbound rules each configured for calls from an extension group for that location. a 7 digit (append 1+area code), 10 digit (add a 1), 11 digit, and 3 digit with starting prefix = 9 (will handle 911 and 933 so I can test).


This seems to work perfectly. I realize that there is a lot of moving parts here but through installation procedures and testing on every device and having no default call path, only group matches I'm confident I can avoid issues.

 

[leejor]

You can also create 911 rules that are limited to certain extension numbers (if you don't want to do groups). Place these above the "general" 911 rule that applies to the bulk of the extensions. Rules are read top to bottom.

 

[jmitch11]

Everything you're doing looks great. One thing to note however is that if you have managers or users with outbound CID set at the extension level and you pass the e911 call out of a trunk that doesn't override their DID then you will end up with VI's lovely $250 rogue E911 fee.

Your two options are to:
1: Provision each DID for E911 on VI
2: Create specific trunks specific for outbound E911 calls that will override extension outbound CID settings.

I chose to go with the latter. Look forward to your input.