e911

[cfickes]

I am implementing an e911 solution on my core PBX (ACM6.3) but I am only deploying this on a limited basis. The sites I am moving onto the core will connect via the WAN, and they are geographically separated. My query is, how can I setup each site uniquely within the core?
Here is the use case: I have two locations one in FL and one in AZ, and each has 10 phones. If someone in AZ calls 911 (which is coming back to the core) how can I group those extensions in a single ELIN?

 

[kyle555]

CM has, at a subnet level or at a more granular level, station level, the ability to send a certain CLID for emergency numbers. Basically, if the call is of type "alrt", CM will send the Emergency Location Extension that's in the "ip-network-map".
That's how it's done with ISDN trunks.

Depending on what you're doing with e911 and what solution you're using, Session Manager can integrate with something like Redsky and return ELIN to phones upon registration so the phones know what number to send as CLID when they dial emergency calls.
Here's a config note about that:

https://www.devconnectprogram.com/fileMedia/download/c10ec9cd-513d-42a8-8949-bd19bb4fe856

 

[SenorAvayaGuy]

When i handle our E911 system with Intrado i did it by extensions.
if extension 94xx dialed out, their CID would be generate the ELIN and so forth .
for the 5th floor 95xx would have a separate CID and that would show a separate location
I'm not sure how E911 is handled on a PBX but hope i provided SOME help at least.

Best of luck,

An Avaya user.

 

[cfickes]

Kyle, this deployment will be using ISDN trunks.

 

[kyle555]

So, what about your setup for these sites makes any of it e911? Is there anything beyond just sending a different DID to the PSAP to get those calls to AZ 911 instead of the 911 center wherever your core is?

I think you might have a heck of a time setting that up with a provider saying "Hi, I know I'm in NYC, but if I send this CLID when I call 911 on my NYC PRI, I would really like the Scottsdale cops to pickup". I don't think they do that.

Get a gateway with a copper trunk local to the site, or look at using SIP trunks with a SIP provider that can offer you that. I could be wrong, but I don't think your typical PRI service offers that.

 

[cfickes]

Kyle, after doing some more research, I am looking to use network regions/network mapping. I see how to set those to options up but I am not sure how I am going to route the e911 traffic just for each of the sites. Do you have any ideas or suggestion?

 

[kyle555]

Your multi-location dial plan with ARS lets you specify routes/trunks per location.
So, if you "change ars ana 911 location 1" and send 911 to route 1/trunk 1 and "change ars analysis location 2 911" to route 2/trunk 2, that's what separates what trunk that calls go out per location

 

[cfickes]

How do you setup a location if you do not have a gateway at that location?

 

[kyle555]

IP ranges in the network map associate to a network region.
Network regions have a physical location.
Dialed strings within a location have their own location-based tables to analyze those digits.

Unless the sites with no local trunks are close to sites with trunks, you might have a problem sending CLID for your remote branch to the CO on an ISDN trunk and have that CO know what PSAP to route your call to.

For example, I don't know if in NYC you can have a PRI on the west end of town and send CLID for your site w/o a gateway on the east end of town and get the east end's 911 dispatch.

 

[cfickes]

I was able to figured this configuration.

1. Create a new location
2. Create a new "Network Region"
3. Define "Network Map" IP ranges and input new "Network Region"
4. Define new route-pattern for 911 calls
a. delete 3 digits and input the e911(RedSky)number
b. set ISDN trunk group for e911 calls
5.Define ars tables for that location.
This configuration was verified through a trace, and the CLID came across.