NARS help needed 1

[MagnaRGP]

Good Day all.

I'm having a little difficulty connecting the dots on my NARS. CS1k 5.0 SA with a survivable media gateway and alternate call server.

Loops 0 0 and 0 1 are in NPA 416/647 (Primary CS) and loops 4 0 and 4 1 (alternate CS) are in NPA 905/289. Both sites have PRI's.

The issue is, some 905 numbers are local to the 416/647 NPA site but LD to the 905/289 NPA site. What I need to achieve is for the system to recognize 1-905-NNX-XXXX as being local to the 416 site and select that OGT route and place the call as local first choice, or if it's all trunks busy, leave in the 1 and use the 905 PSTN.

Rt 9 is my 905 PSTN OGT and Rt 10 is my 416 PSTN OGT.

I have created an FCAS table with all of the 905 NNXs that are local to the 416 NPA, and a second FCAS for the 289 NNXs that are local to the 416 NPA but am not sure how to apply it to the RLI for 1905 and 1289 NPAs. There are already RLIs created for NPAs 416, 647, 289 and 905 selecting their appropriate routes.

There will be users in 416 NPA dialing 9,905 etc and users in the 905 NPA that dial 9,1-905 etc for the same number.

I also have to deal with the 911 calls from each site using the correct PSTNs, but I'm going to try to implement the subnet method of differentiating the callers as this is a 100% IP solution and both sites have different subnets.

I hope that's enough detail.

Thanks in advance.

 

[bigindian65]

You may have to break those out with spns that are including both npa & nxx in the string. I have had that situation with nearly matching nxxs in Fla & all calls originating out of my pbx in Ky. I had to spn for the Fla calls to go out local in Fla & Ky calls go out local in Ky. All calls originate in Ky. spn 101npanxx



Mato' Was'aka

 

[911guru]

Magna-

For the E911 implementation make sure you got PKG 337 to enable the I-LIS for subnet discovery. Make sure you turn on the LIS before you provision the ERL on the sets.

If the LIS is OFF then a <CR> at the ERL prompt puts in a hard coded '0' value. If the LIS is ON, then a <CR> puts in a NULL value which means auto discovery.

This will save you from having to go back and touch the TNs and NULL the ERL prompt!

911Guru

http://pbx-e911.com

 

[MagnaRGP]

Thanks.

911guru -

I think the package required is 336 Subnet LIS. Pkg 337 is ESA_EXTERNAL_DM which I think means an external server.

Anyway, the system does not have pkg 336, so I'm going to be stuck with static entries. Assuming I'm right, here's what I THINK I need to do. Can you provide some insight please?

I will assign an ERL of 4161 (1 representing the first site within that NPA) to all of the 416 NPA located sets and 9051 for all of the sets in the 905 NPA. Then, I need to create the appropriate RLI for each ERL.

That correct?

 

[MagnaRGP]

I think I got it. Using EM, I created the ERLs as described above, and used a static route at for eact using local PSTN. Now, I believe all I have to do is apply the ERL to the appropriate sets and enable the list and then arrange with the local EMS to test.

Have I missed anything?

 

[johnpoole]

sounds like your there.. other then possible overflow, i didn't see that step in your solution... this forum is getting smarter...

john poole
bellsouth business
columbia,sc

 

[911guru]

Sorry about the PKG numbers, you are absolutely right! Too many in my head these days.

REQ  prt
TYPE pkg 336
ESA_SUBNET_LIS        336

REQ  prt
TYPE pkg 337
ESA_EXTERNAL_DM       337

Looks liek you are on the right track. A few things though:

1.) Are you using ELINs or DID numbers?
2.) If you are using ELINs, will they be dynamic? (mapped to caller upon use)

Also in your RLI, you may want to consider (in addition to overflow) the last entery being an LTERM to local security in the event you get an All Trunks Busy condition. That way you can at least get the call to someplace no matter what.

911Guru

http://pbx-e911.com

 

[MagnaRGP]

Thanks guys.

Both sites only have 1 PSTN route (for now) as the customer hasn't yet sprung for a couple of POTS lines at the sites. When I convince them that it's necessary, I will change the single route entry in the ERL db to an RLI for each site and include a step to a local POTS from the local PRI.

The reception sets at each site are going to be OSDN's for the site and have the OSN key as well. There isn't any "security" desk other than reception, so I'm kinda hooped there.

I quite like the static list capability....since I don't yet have any truly mobile sets at this customer, static is the way to go. Next phase is WLAN sets, so we'll see how that goes.

Thanks for the insight.

 

[MagnaRGP]

Update:

I've tested my 911 implementation above and it works like a champ. The only issues I had was that 911 was in the system as a SPN, so if a user dialed 9,911, it "over-rode" the ESA programming. The other issue was the system was inserting the AC as it was in the ERL provisioning. Once I took that out, voila.

Once I took out the SPN, direct dialing 911 works based on the ERL.

What a cool functionality.