extension to use only cetrain trunk members

[vsamudio]

I'm trying out 4 new loop lines . have set them up on the switch as trunk group 3 members 1-4.
the thing is i want only certain extensions to access these 4 line. for example only exts 7100 to 7120 use trk group 3.
ext 7121-7699 use the regular trk group 2 members.

any help is appriciated.
Thanks
V<><

 

[Phoneman2]

One way is to use time-of-day routing.
This would allow you to route to the new trunk group.

You can also put the trunks in a route pattern with a lower FRL then the other trunks in that route. Lower the FRL of said Ext to match that of the new trunks.

Wisdom is Knowledge
that is Shared

Thanks All Phoneman2

 

[Phoneman2]

I think I would go with the first one.
The second one could let other traffic in if the other trunks in the route became full.

Do you have time of day turned on
type &quot;Ch Tim&quot;

If yes you can have 8 different times set up.

Wisdom is Knowledge
that is Shared

Thanks All Phoneman2

 

[Dustinn3]

The only other solutions I can see are setting up a speed dial for the trunk access code or setting up a new partition.

However, if you setup a new partition you would have to setup an ars table, cor, and route pattern for the partition.

 

[avayaman]

Dustinn3,

Actually that is only true if the switch is release 6 or lower. You simply have to use the Partition table, in later releases.

Vasamusio, I can send you a couple of excel sheets with an example if you wish if your switch is later than release 6. My email is below.

Paul Beddows

Avaya Consulting, Implementation, One on One EAS & Definity Training for PBX Administrators.

Vancouver, Canada
E-mail avaya@vancouver.hm

 

[ife]

All the offered solutions seem good, only that they all depend on certain conditions like having Time of Day or Tenant partitioning activated in your switch.
My idea( correct me if I am wrong) will be to give vsamudio a solution that will require only just creating and changing CORs.
I noticed the extensions that you need to access trunk group 3 are 20 or less in number, so I suggest you manupulate your CORs( Afterall you have 96 CORs to play with)such that only the CORs of the users 7100-7120 can access the trunk group 3( see page 2 and 3 of the COR form). For any of the users that have share the same COR with other users outside this range,create a different COR for them.
The only thing that suffers is the CORs which increases in number.
This solution might seem crude, but it eliminates complexities that could arise in the manupulation of the Time of Day and tenant Partitioning features.

 

[Bobg1]

I would tend to agree with ife.
COR is probably the easiest way.
Your trunk groups need to each have their own cor as well as the groups of stations having their own. You then set the cors for the groups of stations to restrict access to the cor of the trunk groups.