rhwimmers

Is their a way to check all the route patterns to see where a certain trunk group is used? Id like to do a list usage trunk 313 but it doesnt work that way! Any other ideas?

Also - Changelog - is their anyway to keep track of what has changed in our system in the last X days? Id like to put something in place (if not already) so I can know exactly what was changed on a certain date...

One more - Starting that the station level...How is it deteremined which ARS table it will hit - is that the TN number?

Thanks
Ross

martinyoung

Do a "list route" and this will list all the route patterns that have trunk groups assigned to them.

Do a "list history" this will show any programming changes that have been done. This log goes back a long way. It does not, however show exactly what was changed.

If you changed the name on station 1234, the history would show that you changed station 1234, the date you did it and the time you did it, but not what you did.

Yes, the number you are calling will determine the route you use. Long distance numbers will have their own ARS entry with 11 numbers to dial and local calls will have their own entry with 7 digits to dial.

__________________
Marty
Retired Avaya DSIC tech

PBXtech.info

 

rhwimmers

Thanks... basically I am doing a trace on a station. It does not do what the ars analysis table says.. So im thinking that the station itself is not "assigned" to the correct location.
Im doing list ars analysis loc 9 and see that 1765 min11 max11 should use route pattern p93... Route pattern 93 says use either 7 or 109 and its using 313. So its either not associated to the right location - or the p is telling it to route differently...

martinyoung

P93 is referring you to Partition Route Table 93, not route pattern 93. Partition Route Table 93 will send the calls to the route patterns (not necessarily route pattern 93) listed in that table.

__________________
Marty
Retired Avaya DSIC tech

rhwimmers

ok so when I do a list partition-route-table and go down to 91 (which is p91 on the ARS screen) I see that under PGN7 it just says 91 (route pattern 91) but under PGN 8 has 991(route pattern 991). What assigns a station to the PGN number - what im thinking is if they are PGN 7 it will use 97 and if they are PGN 8 it will use 997 - which looks correct, but I believe the problem is they are set for the wrong PGN.

rodrifra

PGN 7 is one value and PGN 8 is another, both independent. The value you use depends on the COR assigned to the station (if you have agents then it would be the agents COR). So, display COR, see what time of day it uses. Display that time of day, there you will see what partition it uses. Now you know what partition you have to look at to see the route.

PBXtech.info

 

stubborne

It's the "time of day chart" field in the COR. Also, it sounds like you are doing location based routing (list ars a location 9). If so, there are two separate ars tables. Any route not assigned in ars a location 9 would be found in "list ars a" (without the location parameter).

The time of day chart field in the COR is used to determine which PGN to use in the partition route table.

__________________
Stu

rhwimmers

When I do a list time-of-day # (1-8) they all look the same with no information in them at all...

martinyoung

The default for time-of-day routing is 00:00 seven days a week and PGN 1. If they all look this way then you have the added complexity of partitioned routing for no reason. Do you have an entry in the PGN 1 position of the partition routing table?

With 00:00 as your time of day choice that means the COR that references this time-of-day chart is going to use PGN 1 all the time from the partition routing table.

__________________
Marty
Retired Avaya DSIC tech

rhwimmers

I have PGN 1 in the partition-route-table but not for the series of route patterns im concerned about (91-96). I also verified that their is nothing in the time-of-day tables 1-8 everything just says 0:00.

SO Back to square 1 - how can I determine why calls from certain extensions are going out the wrong trunk group? Seems the partition route table is not being used for anything. Is their a command other than list trace ext that will give me more details on what COR it is calling from and why it chose a certain route pattern etc?

rhwimmers

Ok - I changed one of the extensions COR to one that routes differently and got the same result - so now im really confused - the COR had no effect on how the call was routing...

martinyoung

You are stuck half way between two worlds. You have time-of-day routing active in your CORs but you are not using time-of-day routing because you have no parameters defined. changing to another COR won't help. Your outbound call is using the ARS entry because you are not overriding it in any way.

Your ARS tables are referring you to a partition route table that has no entry for PGN 1, if I understand you correctly. That is the one definition in your time-of-day tables that will apply. Essentially the PBX is making its' own determination of how to get out. It is probably using the route pattern of the last successful call.

The easiest way to test this is do "ch ars an 1xxx" remove pxx and replace it with the specific route pattern you want to use.

If for some reason you must keep partition route tables (right now I do not see why you need them), go back to the partition table and put "deny" in all the PGN entries before the one you want to use or move that one to PGN 1.

__________________
Marty
Retired Avaya DSIC tech

dragrace8

What version switch do you have? The commands I'm giving are for a s8700 CM 2.0 or greater.

Question 1. Try the command LIST ROUTE TRUNK 313 This will tell you all the route patterns that 313 is associated with.

Question 3. Try using the command LIST ARS ROUTE-CHOSEN 1765XXXXXXX LOCATION X This gives you the default routing from that location. You can also try LIST ARS ROUTE-CHOSEN 1765XXXXXXX PARTITION X This gives you the route being used through each partition (1-8).

Hopefully this helps.

rhwimmers

were on 2.2...
Ok - list route tru 313 looks correct - it does not show any reference to the location that is using trunk 313.
list ars route-chosen 1765 loc 9 gives me unique entry error - so i do 17657 and I get no records match the specified query options...
If I do list ars route-chosen 423 loc 9 I also get the "no records match"
HOWEVER - doing list ars analysis loc 9 I get a bunch of stuff including
"1765 11 11 p93 locl"
and
"4 7 7 p92 hnpa"
Everything in this analysis table for location 9 has a p## route pattern but yet if I do route-chosen for that location it says no records match!!!

martinyoung

"1765 11 11 p93 locl" is wrong. 1 plus area code is not a local call, change to fnpa.

"4 7 7 p92 hnpa" is ok. That is just telling you that a seven digit call starting with 4 is a local call and it can be hnpa or locl.

You will get the "no records match" error if there is not an entry in the ARS tables to match your request. Unless you have 17657 or 423 in the ARS tables, this is the correct response.

I suspect you are getting the route-chosen error message because your partition route table does not have a route in the PGN 1 location.

I still recommend replacing the pxx with the specific route pattern you want the call to use.

__________________
Marty
Retired Avaya DSIC tech