Archibald J. Cox

I had a multi-site survivable option 11 at one point that was located in three different counties. In order to make it all work correctly, we set up different TGAR/TARG entries to limit which routes calls could go out. Each site had a route that was specifically for use by phones in that location.

For example:

911 is set to use RLI 9
RLI 9 ENTR 0 points to ROUT 1
RLI 9 ENTR 1 points to ROUT 2
RLI 9 ENTR 2 poitns to ROUT 3

In the RDB for ROUT 1 TARG is 02 03 04 05 06 07 08
In the RDB for ROUT 2 TARG is 01 03 04 05 06 07 08
In the RDB for ROUT 3 TARG is 01 02 04 05 06 07 08

All Phones at location 1 have TGAR of 01 so they are allowed to use ROUT 1

All Phones at location 2 have TGAR of 02 so they are allowed to use ROUT 2

All Phones at location 3 have TGAR of 03 so they are allowed to use ROUT 3

(In actuality there were 2 different TGAR/TARG numbers for each site so that we could restrict other calls, but you get the idea.)

For you, set up the SPN of 11 (or 911) to use an RLI that nothing else points to. (For the sake of argument, I'll use 9)

Set entry 1 to go over the Houghton main ROUT
Set entry 2 to go over the backup Houghton ROUT
Set entry 3 to go over the West Seneca ROUT

in the RDB for both Houghton ROUTs, set TARG to 02 03 04 05 06 07 08
in the RDB for West Seneca ROUT, set TARG to 01 03 04 05 06 07 08

Change the TGAR of all phones at Houghton to 01
Change the TGAR of all phones at West Seneca to 02

Remember, if the TGAR of your phone matches the TARG of the ROUT, you don't get to use that ROUT.


It's a lot of global changes, but I'm sure someone on this site has a Procomm script that could take care of that for you. If not, my company will do it for a fee (I know you don't want to hear that, but they won't let me do it for free)

Let me know if you need further assistance. (Or if I mis-stated something)

Arch

HCJes

Thanks. I thought TARG/TGAR was the way to go.
I think it is about time to audit my Targ/Tgar on the stations and trunks for each site. That is the only part of my ESN I have not fully documented yet.

HCJes

I found a catch to the recommended solution.
We still want people from Houghton to go out the West Seneca trunks as this allows us to get free local buffal.
We still want people from West Seneca to go out Houghton's trunks as they will be able to get free local Houghton.
Targ/Tgar restrictions would prevent that from making any calls on that Route.

Any other ideas?

Archibald J. Cox

How about by FRL in the RLI entries for the SPN?

By using this, it's specific to the SPN, and other calls (NXX/NPA) can be controlled separately.


Say something like ENTR 0 uses an FRL of 2 and local ROUT and ENTR 1 uses FRL of 1 and remote ROUT. Local phones only need to have an NCOS of 2 (assuming 1-1 matching) and they will default to the local trunk group. Remote phones would all need an NCOS of 1 and would be blocked from using the LOCAL rout and would use ENTR 1 and go out the remote ROUT.

However, this leaves the option of LOCAL phones using the REMOTE ROUT if the LOCAL ROUT is entirely in use. On the other hand, it's better than not attempting to separate the two at all.

You'd have to play with your actual NCOS/FRL levels to see how you could make it work.

Arch

Archibald J. Cox

That also means that you're going to need to rethink the entire BARS setup as it is right now.

Another idea:

Remove one trunk from the ROUTs at each site and set up a new rout specifically for 911. You can still allow outbound calls to overflow to these two 911 routes and assuming your original ROUT has more trunks than you normally use, this can work. (Because you don't want to pay $45 a month for a CO line that doesn't get used except for 911)

Then you TGAR/TARG those two routes. Set up the RLI for the "11" SPN to attempt those routes first. With TGAR/TARG it will go out the correct ROUT. IF you allow calls to be made on those trunks, you would probably want to allow outbound 911 to roll up to the main trunk groups in case the 911 routes are busy.

I actually had many customers (Public Schools) who my previous company made them purchase a COT for 911 purposes only at each and every site. If the customer refused, then they had to sign a 10-page CYA liability waiver recognizing that there was a slim possibility that a user wouldn't be able to dial 911.

I would love to hear any other possible solutions. Does anyone know of a feature where a high priority phone can drop anyone else's call and dial out if a trunk group is entirely used? That would be a handy 911-related option.

Arch

HCJes

Our offices use NCOS 4, there for there 911 calls would still end up going out the route that has FRL2. This would continue to be a problem.

Jes

HCJes

I am going to suggest setting up a seperate route with a trunk. I will then use TGAR/TARG to prevent HOUGHTON from using the member.

Archibald J. Cox

Probably your best bet

Arch

papa-bear

Agreed with seperate routes for 911. We have the big switch the city hall with 7 sites outside serviced from the one set of PRI. We install a 1B in each location to use for 911 identification. When we move or set up a phone in any site, we make sure that when they dial 911 the switch sees it and re-routes it back down a trunk line to the 1B and out. E-comm gets the right address and everyone is happy.