mferro

Is it possible to have long distance calls to the same number go out 1 trunk group from one extension (i.e 8500s) and go out another trunk group if calling from a different extension (i.e. 7400s)?

looking in our ars table, if we dial 1 212 (NY) the calls all seem to go out a particular route pattern which eventually point to a particular trunk group.
Calling from extensions 8500s and doing a list trace show this is happening ok.

However if we call the same number from a 7400 extension, the list trace shows it's going through a different route pattern and trunk group and we don't know where/how that is set up.

we are not sure if this means the PBX is partitioned, but how else could this be happening?

thanks

fataldata

Yes, with different COR's on the stations they will use the same partition but different time of day columns (when you display partition xx, notice the 6 columns corresponding to different Time of Day Charts and entries on the COR page 1) therefore different route patterns.

__________________
Systems In Use:
S8700 CM3.0 and S8710 CM3.1.1

PBXtech.info

 

ahays

Referring to fataldata's post, it's called ARS Partitioning ... and while it has it's place, Avaya is FAMOUS for using (or rather ABusing) ARS Partitioning even when it's completely unnecessary.

Here's the way it works: The ARS table (change ars ana xxxx) has an entry that begins with a "p" ... such as p3. The "p" refers to the partition table and the "3" refers to the row on the table (change partition 3). The COLUMN of the table is determined by the "time of day" entry of the COR. At the intersection of the row and column you will find the appropriate route pattern.

If you have no need for ARS partitioning then you can eliminate all of this nonsense by placing the route pattern directly in the ARS Analysis Table and eliminating the "p" entry.

regs,

.al.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

mferro

thanks! got it!