HELP!!! -- ROUTING 2

[nortelphonediva]

Ok.. I have a routing question that is being posed to me. I can not figure out what to do to make this customer get what they want. Here is the question as it was written. Can someone PLEASE help me answer this. THANK YOU!!! My answer was to use NCOS and FRL.. he said:

"Thanks for the answer. That would work - sort of. The weakness is that it wouldn't positively exclude those users that have an NCOS/FRL giving access to both. We need tomake usre that user Group "A" only hits the DNC trunk group and never hits any other trunk group. User group "B" hits only trunk groups available to them. It must be impossible for BARS to select a trunk from the DNC group for user "B" - and vice versa.

There is way to do this. You'll still need to carefully define the NCOS and FRL in your Route List Data block - but there are additional setting on the route and the set level programming that will allow you to allow/deny access to the route. What are the prompts in the Route data Block (RDB) and the Terminal Number Block (TNB)? "

___________________________________
Carolyn C Kelly, M.S.
Senior Telecommunications Engineer
Transbay Communications
-San Francisco, CA-

 

[bigindian65]

I see his point, you can easily deny A from going out B by making NCOS/FRL of B higher, but then B would be able to go out A.
I think to do what you want, you will have to use TARG/TGAR
In LD 86 ESN, is TGAR set to no? You can't just change it to yes, or nobody is calling anybody. If TGAR is 1 on the route & TARG is 1 on my set, and LD 86 is ESN TGAR is yes, I am blocked. It is a matching game, unlike NCOS/FRL
NCOS on the set is how much $ you have
FRL on the RLI is how much it cost $ to use it, as long as your NCOS is higher than your FRL you have the cash to use it.
TARG/TGAR is a little different, but you will have to make a lot of changes if it isn't currently used. In the ESN data block, it is default no. You can make A match B's route, denying, and B match A's route, denying. Making them entry 0 and Entry 1 of a Route List Index. (I think)

Someone may need to clean up my logic, I'm away from NTP's.

 

[NortelGuy1979]

Bigindian is right; unless you use TGAR already, it could take a bit to set up - however, that being said, it may do what you want.

I believe the default route TARG is 0, and the default TN TGAR is 1; so turning it on may not suddenly cause problems - but you're going to want to make sure before you do. You'll need to plan all your user groups, and all your RLBs, and make a plan of who should be able to use what RLBs. Then, make a chart and design your TGAR/TARG settings, make the changes, and then turn it on in the ESN block.

NCOS and FRL will not let you mutually exclude two groups into using two separate RLIs - you're correct.

Take this scenario: I worked at a site with shared PRI trunking between multiple locations; those locations were T-carrier remotes. So, although all the carrier remotes used the PRI for local dialing, they needed to exclusively use their local loop start trunk for 911. We used TGAR/TARG.

Here were our routes:
RLB 1: PRI, TARG 0 (not blocked); at site A for everyone
RLB 2: 911A, TGAR 2; at site A for 911
RLB 3: 911B, TGAR 1; at site B for 911


All users could use RLB 1 since it was TARG 0
Users at site A had a TGAR of 1 so they could not use RLB 3
Users at site B had a TGAR of 2 so they could not use RLB 2

So, the RLI for local just had RLB 1 in it.
The RLI for 911 had RLB 2 and 3 in it; of course NCOS was set appropriately, but TGAR/TARG made sure the sets used the correct RLB.

Remember that a RLB can have *multiple* TARG values; you use X to remove a specific value. The site I'm referring to actually had about 9 carrier remotes, so our TARG list was quite extensive, but this should be enough to give you an idea. Let me know if you need more help; I could even post the chart we had if you need.

Matthew Heavner
Field Service Engineer

 

[johnpoole]

everone is right BUT i would not do it that way. i would enable tennant service.. that gives you tenant to trunk group access of blocking.. one set of rlb's one set of frl's.. if ten 1 can dial local with ncos 2 then you can allow all tennants to do the same.. you just add a route from each temmant to the rlb..

tennant to tennant is allowed or blocked.. each tennant can have a unique dial 0 target or share.. for me it works great..

john poole
bellsouth business
columbia,sc