Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

HELP! ESA 911

Status
Not open for further replies.

Pir8Radio

Technical User
Jul 31, 2004
291
US
OK BOYS AND GIRLS, here is the question of the year... I need your help.. here is my situation..

I have 2 buildings we will call A and B. My current set up for handeling 911 9-911 calls are as follows, i have 11 and 911 in my SPN table to direct to 2 different RLI's 911 adds a 9 and 11 adds a 99 to dial out my pri. thes are under route 25 of mine for entry 1 (thats for building A) but for entry 0 (building b trunk card) i have a restriction of 3 on it so you have to have tgar on the phone set to 3... this way if building A dials 911 they are not allowed to go out the trunk card in building b and if you are in building b you have access to the trunk card first.. this way 911 goes out of a line in that building and the cops know where to go.. does this make sense? WELL now this is my problem.. all of that works fine and dandy, but now i want to set up ESA to notify the front desk if either building dials 911.. but in ESA i can only choose one route... before you tell me to just change the clid entry for that key.. no can do.. i need this to work some how.. any ideas? Please....... :-(
 
i don't see a solution without enhanced 911 calling turned on, you could look at making building b a serarate tenant, then the tgar could be repalce with tenant to rdb restrictions. even with that you woudl have to tweek it to make it work...

john poole
bellsouth business
columbia,sc
 
How bout this, WHAT IF! I had 911 as the ESN then the output of the ESN go to say 7022 Internal, then i have a SPN of 7022 with a DMI that subtracts 4 digits and adds 9,911.. that way it still goes through the RLI that checks for the TGAR (building a or b) then i can have a spn of 9,911 then direct THAT to 911.. this would cover both 9,911 and 911 also checking for building a or b. would this work? or am i an even bigger moron now...
 
if i dial 9,11 or 911 from bldg a, it sends it to a rli that sends it out on a route marked bldg a, i dial 9,11 or 911 from bldg , it sends it to the same rli that sends it out on a route marked bldg b, the shift can be ncos or tgar. one rli 2 entry;s.. what am i missing?

two entrys in the same rlb

john poole
bellsouth business
columbia,sc
 
Yes this works all fine... but i want it all to go through ESA... so i can have on site notification.. but ESA only allows one entry 911 or 9911 and sends directly out one route. i would loose my building a or b option.. so my question is.. what if (for example) i have the ESA set to 911 then the ESA dials an internal number 7022. then have a SPN 7022 that lets it go through my rli blah blah blah... the ESN output can go to an internal DN but can it be made to go through SPN?

Take it easy on me im fragle... And somewhat new to this area of the switch..

Thanks.
 
I know you said no can do, but why can't you use CLID to seperate bldg. a and b? Is it a knowledge reason or is it an internal thing?
 
if you ncos one building off of one route in your rli (frl=4) and entr 1 same rli, frl=3 it will split the calls over two routes, we used to send pri calls out over watts, first then if your ncos was high enough your call wood take a more expensive route, in network control nctl frl3=ncos3 frl4=ncos4 etc. you can even add entry 2 with a frl off 1 as a last resort if other routes are busy. the station will take the 1st entry that has a frl that is =to or less then their ncos. tgar can be used if route a has a targ of 1 2 4 5 6.. and route b has a targ of 1 2 3 5 6.. then phones with a targ 3 can only use route a and phones with a targ of 4 can only use route b.. the match tgar to targ blocks trunk group access..

john poole
bellsouth business
columbia,sc
 
Actually ESA overrides NCOS, FLR and TGAR settings, so this is not an option.

As long as both locations are being served by the same E911 Tandem the E911 call will arrive at the proper PSAP as long as the CLID is set correctly.

Think of E911 as a cloud. It really doesnt matter where you enter it, as long as you enter the right one.

The perfect example is NJ. They are seviced by 4 E911 tandems, that are grouped into pairs, North and South of the state. All E911 calls in the north of the state end up in the SAME E911 tandem, where the CLIS is matches against the MSAG (Master Street Address Guide) Database. Once a match is established the call is routed to the proper PSAP via it's ESN Identifier (kind of like a 911 zone ID) over PRI or CAMA trunks.

Now again, there MAY be variances in this from State to State, but this is a common state wide 911 network topology.

To take it one step further, in NJ, the new DMS250 911 Tandems are linked via SS7, and even if a call is routed to the 'South' pair, the call will tandem to the 'North' pair where it will be routed to the proper PSAP. This just happened in the past year. Previously they were networked with CAMA type MF signalling trunks and this North/South integration was not possible.

Sorry for such a verbose answer, but E911 is a tricky situation, and unless you understand the E911 topology serving YOUR area, if you assume, you may be making a huge mistake.

Good news is most of this information is vailable on the WEB. Start at the NENA website at
Good luck!

--
Fletch
Visit the Nortel Technical Support Portal at:
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top