help setting Trunk-group 1

[namr007]

Hi all,
I need to setup a trunk-group of 6 phone numbers, and have it rings on 4 stations. I'm not sure if I am doing this the right way. but I set up the trunk-group to a destination that points to one of these station. and bridged it to the remaining three stations. so now whenever I get any incoming call on the trunk, it rings on four stations at the same time. I would like to be able to hardcode those stations to go out through this trunk, instead of using our main trunk to go out. is there any way to do this? Thanks.

 

[Bobg1]

For starters a terminating extension group would probably work better than having to do all the bridgeing. You would set your trunk group to ring to the terminating ext grp and you would put the ext of the station you want to ring in the group.
As for outgoing, you need to setup a cor for these stations and match the routing of the cor to the trunk group.

 

[namr007]

I mathced the Trunk-group COR with the COR of the stations, but whenever I dial out, I still see the trunk status in idle stats, which tells me that dialing out uses different trunk, how can match the routing of COR to the correct trunk group as you mentioned.

 

[Barrier]

If the "ars analysis" table is using the "partion routing table" (column route pattern has p1, p2 and so on), the way to solve it is as follows:

Add a route that points to the trunk group on which the 4 stations have to call out. On second row you can make a backup to the main trunk.

In the "partion routing table" choose an empty column (PGN x) and put the route number in it. If the "ARS ANA" table has p1 to p6 fill rows 1 to 6 with number

Choose an empty "time-of-day" (d) routing plan and fill the first PGN column with (x).

The last change is the time-of-day number in the cor of the station. It must be set to the matching number of the "time-of-day" (d).

 

[namr007]

I checked my system params amd it doesn't use tenant partitioning. any other idea on how to hardcode these 6 stations to go out on specific trunk.

 

[rjblanch]

We use the digit of 2 as an ARS routing parameter. We set up an autodial button as "Outside Line" and set it to dial "02 (0 for outside access and 2 as route signifier)". In the ARS table, you then make the digits "2xxx" and all have them use the same route pattern.

On the route pattern, you then have only 1 trunk group. This will not allow any other way out.

 

[Bobg1]

The cor should not be the same as that of the trunk group.
It should be a unique cor for those stations. Within the cor you can set restrictions as to which other cors that cor can call. you also must have a routing pattern that will allow calls to use that trunk group.

 

[1a22ip]

How about matching the FRL of the stations to the FRL of the new trunk group?

Just a thought
ED

1a2 to ip I seen it all

 

[namr007]

Bobg1, I am a cisco guy, I can write a new routing pattern to use the trunk group, but still, how can I hardcode these 6 station to use The new route-pattern instead of the one we use
to go out for everyone else in the company?

 

[marcell55]

OK, give those people a different COR than everyone else. The only difference in their cor will be the time-of-day chart. Make it 2. This will make those people belong to partition index group 2.

Now, in ARS analysis you have the dialed string pointing to a route pattern. In the route pattern field you'll either see a number, or the letter p and a number. If it's p and a number, this will be easy.
For example: say the route patter the dialed string is pointing to is p4. You can then type "change part 4". In the table, you would put your new route pattern in the field for partition index group 2. Everyone else will continue to use the route pattern for partition index group 1.

Ok, if the route pattern in ars is pointing to just a number, you'll have to create the partition index tables yourself. Once you create them (change part x) then you can assign them to the ars analysis table by putting the route pattern in as p and then the line from the table, such as p4 or p5.

This may sound very confusing, and it's hard to write a good explanation of this without writing for hours, but hopefully this will point you in the right direction.

 

[namr007]

I was able to change the chart of the day number to 2, and when I list ARS analysis, I found the routing pattern points to a number. when I do list part-group I see all my COR points to group 1 except for the new COR I created for these stations
and that COR points to group 2. but when I try to issue add part x, the switch don't take that. Is there anything I need to enable is the system params to make this command available on my switch?

 

[marcell55]

It is not an add command, it's "change part x". The tables are already there, you just have to fill them in.

 

[namr007]

The switch did not take this as well, I I need to enable something in the system params to make this command available.

 

[Bobg1]

What version of software is your switch running on?

 

[namr007]

G3V6I

 

[namr007]

hey guys, any other thoughts on my routing problem. Thanks.

 

[avayaman]

Parttion tables worked in a different way prior to release 7. For TOD 2, the command is "change ars analysis partition 2" followed by the string you are looking at. By default partrtion 2 will be identical to part 1. You just change the string in question & re-save.

Paul Beddows
Avaya Implementation
Telus
Vancouver, Canada
E-mail via

http://www.vancouver.hm/email.html

 

[namr007]

I finally got this to work on my definity version. Thanks for all the help from you guys specially beddows who points the ch ars analysis command. I created a new routing pattern that points to the new trunk and change the cor of the station time of the day to 2. then ch ars analysis part 2 and point it to the new routing pattern and that did it for me. Thanks again.