Trunk Access

[SJB01]

We have segregated our TI into 2 trunks
Ports 0-17 Trunk 1
Ports 18-20 Trunk 2
We have different CLI on each trunk and want to restrict one group of people to one trunk and a separte group to the other.

Stations assigned COR 1 reliably dial out and the CLI is that for trunk 1

Stations assigned to COR 5 (Trunk 2) randomly get either Trunk 1 or 2 instead of being restricted to only going out on Trunk 2.

Any suggestions where and how to find the fault.

Regards

SJB01

 

[Bobg1]

I believe what you need to look at is the way your routing tables are set up.

 

[Bobg1]

You also need to look at the cor's assigned to the trunk groups, they should be different and then you can restrict the access by the way the cor's are setup, using the restrict access to cor's function.

 

[SJB01]

Trunk 1 is assigned COR1
Trunk 2 is assigned COR5

Relevant stations are assigned the relevant COR

What is the restrict access to COR function?

 

[RTMCKEE]

The COR's are based on the FRL i assume Cor 1 has a lower FRL than 5. Your FRL gives you access to everything at your FRL and lower, thats why COR 1 only calls TG 1 and cor 5 can call both.

I think there are two different ways to get where you want to go. You are correct asking about the Cor restriction. If you set up the the cor 5 so it cannot call the Cor the first trunk group is in, they will always use the second trunk group. Note: you dont want to make tr 1 be cor 1 and tr 2 cor 5 in this instance because, everyone in cor 5 would not be able to call ppl in cor 1. what you should do is set up two more cor's for the TG's then give cor 1 access to tg 1 and cor 5 access to tg2, and they would still have access to call each other.

The other way is tenant partioning. not sure if you have that turned on, but basically you can separate TG's and users that way aswell.

 

[netcon1]

Tenant partitioning is not required here.

Depending on what version Definity software you have you can us standard station partitioning to achieve what you want.

First. Assign a new cor for the second group of stations that will use trunk group 2 only.

In that cor, set the time of day chart option from 1 to two.
(This puts anyone with the option (2) into a second ARS partition group.

That ARS ANA Partition group can then be set up to point all calls to a new route that again points all calls to the second trunk group (2) only.

This is where it gets tricky depending on the version of Definity you have.

If it is an old version then you must
"change ars ana par 2 0" and enetr the routes for all listed analysis. That route will be the new one above.

If it is a newer system, then you must change the entire ARS ana table (as there is only one) and point all ars ana routes to P<#> routes, where P&quot;P&quot; stands for the partion group form and number.

In the Partion group 0 form you will see the P numbers run down the left hand side of the page and the PGN or partion group number (or TIME OF DAY CHART!!! number run across the top.

How this works is the PGN column will reflect the ars ana table and point to the route that are in the table now.
The second PGN cloumn will be the new route that you set up for the other stations.

I did not say this would be easy, however, if you read the manual on how to arrange these two forms, you can partition stations out different routes to different trunk groups, all within the same &quot;Tenant partition&quot;

OR... Insert money here <=======>

and a business partner can do it for you.

Netcon1

Mark if useful!!!

 

[Bobg1]

You have already established your cor's for the trunks.
What cor's do you have for the users (extensions).
you should have 2 cors set for these also.
On the cor assigments, you should find a page that says restrict access to cor and a list of all cor numbers available, this is where you can set the restriction for a user.