AVAYA: OUTGOING CALL RESTRICTION PROCESS April 3, 2007Posted by Jovi De Guzman in AVAYA.
OUTGOING CALL RESTRICTION PROCESS
Toll restriction and/or the routes that calls can/will take are dictated by the COR of the set and what strings are defined in the ARS and/or the AAR digit analysis tables. The key fields in the COR are FRL, Time of Day & Calling Party Restrictions. There are 7 FRL levels (0-7). 7 is the highest level and 0 the lowest. An extension is assigned an FRL by virtue of its COR. When an outgoing call eventually ends up in a Route Pattern, the FRL is compared to that of the Route Pattern. If it is the same or higher than the FRL of the Route Pattern the call is allowed to proceed. If not, it is blocked. It is best to block a call at the earliest possible stage in call processing.
This can be done in the COR in many cases. Placing “outward” in the “calling party restrictions” will prevent a call from getting out at all. You can also prevent a call from accessing specific trunk groups on Page 3 by placing an “n” next to the COR of the appropriate trunk group. Placing “all-toll” in the “Calling party Restriction” field will force the call to reference the “Toll Analysis” form. This is similar to the ARS form except the call isanalyzed before the trunk access code is processed rather than afterwards. This form can get quite complex, so we tend to avoid using it, unless necessary. It is integral to the use of Authorization & Account Codes, however, It can also be useful if you want one specific telephone number blocked, since it allows all strings “not defined” as opposed to the ARS form which only allows calls to defined strings. It is, however, quite important in a hotel environment.
Toll Denied guest rooms are forced to this form. Since 1-800 type numbers are blocked by default in this form, Toll Denied rooms will be prevented from accessing 1-800 access codes for calling cards. In this case you need to go to this form and remove the 180 restriction and add restrictions back in for 1801, 1802, etc. You need to do the same for 185,186,187 & 188.
The “time-of-day prompt” references the “Time-of-Day tables”. There are 8 possible of these. They all exist by default. The default for each one is 24 hours a day, seven days a week. You can define specific time ranges when calls will be allowed or denied, but this is unusual. The Time-of-Day chart corresponds directly to the PGN number in the “Partition Group” form. In other words, time-of-day 1 is Partition Group 1. This can be changed in the Time of Day forms.
The Partition Group entries correspond to restrictions found in the ARS and or AAR digit analysis tables. Specific strings in those tables will have either “deny” or p1, p2, p3, p4 etc. against them. These show up as r1, r2, r3, r4, etc in the Partition table. Each Partition Group has either “deny” against these entries or a Route Pattern number.
The tables below are simplified versions of the COR, ARS Analysis, Route Pattern & Parttion Group forms.
Look at the tables below. Suppose a set with COR 1, dials 1-250-XXX-XXXX. First of all, COR 1 references Time-of-day chart 1. This corresponds to PGN1 in the Partition Group. Under column PGN1, “r1″ is denied. This directly corresponds to “p1″ in the ARS table. In that table “p1 is next to 12 (followed by 11 digits). This covers the number we are trying to dial. It is therefore denied. Suppose the set is in COR 2. This time it references time-of-day 2 which corresponds to PGN2 in the Partition Group. This time there is no deny next to “r1″ (“p1″ in the ARS), therefore the call can proceed to the next step. The Partition table specifies it should go out on Route pattern 2. Route Pattern 2 has a FRL of 3 which is equal or less than the FRL in COR 2. Therefore the call is allowed. It will go out on Group 2, which is Trunk Group 2.
Suppose the set is COR 4. Cor 4 has a “Calling Party Restriction” of “outward”. Therefore this call, or any other call out of the switch, is denied. Suppose the set is COR 5. This time, time-of-day chart 3 is referenced. This corresponds to PGN 3 in the Partition Table. This time the call is allowed to proceed and is sent to Route Pattern 1. However the FRL of this COR is less than that in Route Pattern 1, choice number 1 (trunk Group 1) so the call is denied anyway, at least on Trunk Group 1. However, Route Pattern 1 has a second choice (Trunk Group 3). The FRL next to this Trunk Group is 1, so the call can proceed out on Trunk Group 3, even though it is blocked from Trunk Group 1. Suppose, though, the station had dialed 325-XXXX. This time the entry in the ARS is “p3″, corresponding to “r3″ in the Partition Table.
The entry in this row under PGN is 3. Route pattern 3 has a FRL of 1, equal or less than the FRL in COR 5. Therefore this call is allowed. Notice that all 0+ calls are denied in the ARS Table below. In a case like this, these may be accessed by a dial 8 and exist in the AAR Table instead. This table looks the same as the ARS table and is referenced to the same Partition Groups. For example all the entries in the AAR may have “p2″ next to them. This means that calls in each Partition group will only access the Route Pattern in the “r2″ row for strings that have been defined in the AAR. This Route Pattern would likely have a Group Number relating to the Trunk Group of Toll Access Trunks or something like that.
The use of different FRL levels in the same Route Pattern (Route Pattern 1 below), can be used to control traffic. Suppose you have a bunch of Executives that always want to be able to get an outside line, and a bunch of proletariat that you want to be able to call out, but not at the expense of the Executives. You could separate the outgoing trunks into 2 separate trunk groups, put them in the same Route Pattern, giving one a high FRL and the second choice a lower FRL. The executives with the higher FRL would be able to access both Trunk Groups, the minions only the second choice.
|COR 1||COR 2||COR 3||COR 4||COR 5|
|Time of Day||1||2||1||1||3|
|Calling Party Restriction||None||None||None||Outward||none|
ARS Digit Analysis
|Min||Max||Route Pattern||Call type|
Route Pattern 1
Route Pattern 2
Route Pattern 3