Force outbound calls out a specific Route. 1

[jebloome]

I have a Nortel OPT81 Succession 1000m Version 5.5 that I need some help with. We have a new client that has brought in there own 2 T1's. They want all of their inbound and outbound to go out these T1's only. I have programmed the T1's and installed everything just fine and they are ready to go. My problem that i am stuck on is how to set up my Authcodes in such a way that all of their outbound calls go out those two T1's only. We have our general use T1's that all of the calls go out right now utilizing Authcodes. We have our CLAS set up so that CLAS 000 goes out our ATT T1's for Local and Toll Free and CLAS 001 to go out our Verizon T1s for LD calls. That is working just fine. The problem is that i want to set up the new Authcodes to utilize CLAS 003 so all calls utilizing their Authcode will go out their T1's only. How do i do that?

 

[NortelGuy1979]

I assume since you're using AUTH codes you're using BARS/NARS for your outbound routing.

Check to see if TGAR = YES in you ESN configuration, then your CLAS can control the TGAR of the call, and you can use TARG on the routes to control which CLAS uses which route. On the RLI, you simply have ENTR 0 = client 0 route, ENTR 1 = client 1 route, etc.

You'll have to build a TGAR/TARG map of what TGAR blocks what route (TARG) and keep track of that, but it's possible to do.

-Matthew

Matthew - Technical Support Engineer

 

[jebloome]

I will give that a try. Sounds easy enough. i will let you know if that works or not.

 

[tnphoneman]

Be careful turning it on the first time. Default on all ends is 1 to all calls will be blocked when turned on.

Signature===========================================

Aastra Authorized Reseller

 

[NortelGuy1979]

Excellent point, set up your TGAR/TARG maps IN ADVANCE and make sure all phones / routes / AUTH classes are programmed how you want, THEN turn on TGAR in ESN.

If you're already using TGAR in ESN, then you'll be OK.

-Matthew

Matthew - Technical Support Engineer

 

[jebloome]

oh boy. i just noticed that TGAR in the ESN is set to NO. i am somewhat positive all of the phones, routes, and AUTH classes are built correctly. i just use one standard across the board for all entities. Would i need to change the TGAR on these specific phones for this client? All of my phones are set up with a TGAR of 1 with a NCOS of 0. We just let the Authcodes dictate permissions or not. will this be an issue before i make the change?

Will i need to change the TGAR on the RDB to a higher number then have the AUB TGAR match it?

Where does the TARG come into play?

 

[GHTROUT]

I'd read up on Tenant service - you can have one route list, but certain tenants will hope over entries to get their own trunks.

Here is TGAR and TARG:

http://www.ghtrout.com/ghtrout/files/TGAR_and_TARG_Help.html

But I would hesitate to use it in BARS/ESN

--
GHTROUT.com - Help for Nortel Meridian/CS1000 System Administrators
--

 

[NortelGuy1979]

TGAR = on a phone, TIE trunk, or AUTH class. Only one value is allowed.
TARG = on the route data block. Multiple values are allowed.

If TGAR = TARG when the call is placed, then it's BLOCKED.

So, if you have 3 client groups, then you need to choose three TGAR values, one for each of those client groups. Assign all their phones and AUTH classes to that TGAR. I'd suggest NOT using "1" as it's default.

Example:
Client A = TGAR 2 for phones and AUTH classes
Client B = TGAR 3 for phones and AUTH classes
Client C = TGAR 4 for phones and AUTH classes

Client A = TARG 3, 4 for Route Data Blocks
Client B = TARG 2, 4 for Route Data Blocks
Client C = TARG 2, 3 for Route Data Blocks

In your RLI's (LD 86) for each type of call:
ENTR 0 = route for client A
ENTR 1 = route for client B
ENTR 2 = route for client C

In ESN (LD 86), TGAR = YES - ONLY after you've mapped out every phone / AUTH class / route data block.

Then, when someone tries to make a call, their NCOS is too low so MFRL prompts for an authcode (or they enter it in advance, whichever), which sets the NCOS / TGAR / CLS for the call, then it goes to the RLI, and based on the TGAR of the call and TARG of the route, it chooses the entry they can use.

That make more sense?

-Matthew



Matthew - Technical Support Engineer

 

[jebloome]

Since i have TGAR of 1 on all of my phones, that would mean that as soon as i turn TGAR on in the ESN, all calls would be blocked at that point. is that a true statement?

 

[NortelGuy1979]

@Jebloome - only if 1) the TARG on your outbound route data blocks = 1, and 2) you're not using an AUTH class that changes the TGAR when the call is made.

If TGAR = TARG, call is blocked. If ESN TGAR = NO, then BARS/NARS calls ignore TGAR/TARG restrictions. If ESN TGAR = YES, then TGAR/TARG restrictions are enforced on BARS/NARS calls.

-Matthew

Matthew - Technical Support Engineer