FRL's

[jimmmaaa]

I read through the following thread( thread690-215035)and was trying to more fully understand the FRL. Are they set in the system and you can't change them or can you configure the FRL?

Thanks,
James

 

[Phoneman2]

You can change them ...but be very careful, read and understand them very well before making any changes. If done incorrectly you could limit or stop all outbound traffic voice, fax and modem. Wisdom is Knowledge
that is Shared

Thanks All Phoneman2

 

[jimmmaaa]

The reason I am askin this I have someone who asked me the following question:
"I have two Class Of Restrictions on my definity system. COR 1 is restricted to certain area codes (local and some others). The other, COR 2 is all of North America. I wish to add a couple of toll free area codes and some other area codes to COR 1. I tried to do change COR 1, but this isn't helpful. Anyone can shed some light on how to change COR1?"

Should I point them to making the change in the ARS Digit Analysis table, maybe they those area codes or toll frees are not in there? That is what I was thinking.

Thanks

 

[Phoneman2]

I would look at the ars table and follow the route pattern and time of day routing. Wisdom is Knowledge
that is Shared

Thanks All Phoneman2

 

[Bobg1]

I think the best way to set up what you want is by using different cor's and then setup you route patterns to the restriction levels set by the cors

 

[avayaman]

There are actually several places to block calls. You can do it by individual strings in the ARS or you can use partiytioning, FRL's, or if you give stations client room COS or set them as all-toll in the COR form, you can also use the Toll Analysis form (that one can get ugly).

Basically we use the philosophy that its best to block the call as early in call processing as possible. I tend to use the Partition tables a lot (They correspond one to one with the TOD prompt in the COR, unless you are using time of day routing). This makes it easy to do what you are trying to accomplish. Assign a "p" number under the route pattern column in the ARS instead of entering a route pattern. Give a different 'p' number to different catagories of area codes. The "p' number in ARS corresponds one to one with the "r" numbers in the Partition form. Assign a different TOD to the 2 different COR's corrsponding to thte blocked and unblocked locals. These TOD's correspond to the vertical column numbers in the Partition form. For the "r" row corresponding to the area codes you want to block, enter 'deny' under the appropriate column. For the others enter the route pattern you wish the call to take.

Its best to use FRL's in cases where you have 2 or more different trunk routes in the same route pattern and want to restrict access to some of them for certain callers.


Here is an Example:

Cor 1 - can call area code 604 & 250 but not 206 or 403
Cor 2 - can call all 4



Cor 1 FRL = 5, TOD = 1
Cor 2 FRL = 7, TOD = 2


ARS Analysis

Dial string Min Max Route Pattern Call Type

1604 11 11 p1 fnpa
1250 11 11 p1 fnpa
1206 11 11 p2 fnpa
1403 11 11 p2 fnpa


Partition Groups

1 2 3 4 5 6 7 8 9

r1 1 1
r2 den 1
r3
..
..



Route Pattern 1

Group number FRL

10 5
11 7


Stations with a COR of 1 will be able to call area codes 604 & 250 but will only be able to use trunks in trunk group 10 since their FRL is less than 7

Stations with a COR of 2 will be able to dial area codes 604,250,403 & 206 and will also be able to access trunks in Trunk Group 11 if all the trunks in 10 are busy, since their FRL is higher or equal to 7.



Paul Beddows
Avaya System Design
Telus
Vancouver

http://www.vancouver.hm

email me via form on above web site