Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
COR & Route-Pattern for Controlling IDD
- Thread starter Kely
- Start date
- Thread starter
- #3
Kely,
i'm not sure whether this is just a convenient marketing term or some country-specific technology, but anyway you can control toll calls by the means of toll restriction and/or ars. first way is more complicated but right, second is quick'n'convenient. on the cor form, there is a setting for frl, and this frl value is used on the route pattern form. so you can define, say, three cors for ordinary users, those who have national access and for those who have international access. then, you can create three route patterns requiring different frl levels for accessing the same trunk group. next you just modify your ars analysis to route national and international calls through different route patterns. see the picture? if the user dials an international number, system will analyze it and route it through the international route pattern. in this pattern, there is frl setting. so if the user has cor that has frl equal to or greater than required in route pattern, the call will go out. if not, user will hear busy tone. but really it's not a nice way, especially if you have more than one trunk group and more than one telephony provider.
i'm not sure whether this is just a convenient marketing term or some country-specific technology, but anyway you can control toll calls by the means of toll restriction and/or ars. first way is more complicated but right, second is quick'n'convenient. on the cor form, there is a setting for frl, and this frl value is used on the route pattern form. so you can define, say, three cors for ordinary users, those who have national access and for those who have international access. then, you can create three route patterns requiring different frl levels for accessing the same trunk group. next you just modify your ars analysis to route national and international calls through different route patterns. see the picture? if the user dials an international number, system will analyze it and route it through the international route pattern. in this pattern, there is frl setting. so if the user has cor that has frl equal to or greater than required in route pattern, the call will go out. if not, user will hear busy tone. but really it's not a nice way, especially if you have more than one trunk group and more than one telephony provider.
- Thread starter
- #5
Hi dawlin,
Many thanks for you explaination. You have get what exactly I'm asking for.... ^^"
However, I still can't get the picture of your words, "next you just modify your ars analysis to route national and international calls through 'different route patterns'". I can only see that there is ONE field for each string for us to fill in the route patterns in ars ana screen. So, how could I tell it to use different route patterns for different group of users to use the same trunk with toll control?
Thx again.
Many thanks for you explaination. You have get what exactly I'm asking for.... ^^"
However, I still can't get the picture of your words, "next you just modify your ars analysis to route national and international calls through 'different route patterns'". I can only see that there is ONE field for each string for us to fill in the route patterns in ars ana screen. So, how could I tell it to use different route patterns for different group of users to use the same trunk with toll control?
Thx again.
Kely,
that's easy. on the ars analysis form, you can define what digits to match and where to route the matched call. we here in russia use digit '8' to access national and international telephony network, so i'll explain using our conditions. i don't know what prefixes you should use. so, to ensure fast ars processing without delays, i do the following: create 8 strings in ars analysis, for digits 1-7, 9, string length of 7 digits, type pubu, route pattern 1 (local calls, toll-free). next one for national calls: digit 8, string length 10, type pubu, route pattern 2. and another one for international calls: digits 810 (that's our prefix for international), length 12 to 24 digits, route pattern 3. so you see, the number entered by user will be analyzed and routed accordingly. more of this, analysis will take place _in the process_ of entering digits, so if the user don't have access to national calls and press 9 (ars access fac) and next 8, he will hear busy immediately. very convenient for small setups.
here is a screen shot, to make it more clear:
[pre]
display ars analysis 2 Page 1 of 2
ARS DIGIT ANALYSIS TABLE
Location: all Percent Full: 1
Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
1 7 7 1 pubu n
2 7 7 1 pubu n
3 7 7 1 pubu n
4 7 7 1 pubu n
5 7 7 1 pubu n
6 7 7 1 pubu n
7 7 7 1 pubu n
8 11 11 2 pubu n
810 12 24 3 pubu n
8499 11 11 1 pubu n
8800 11 11 1 pubu n
890x 11 11 1 pubu n
891x 11 11 1 pubu n
892x 11 11 1 pubu n
9 7 7 1 pubu n
[/pre]
note that we have 8-800 service, analogous to 1-800 in us, and some toll-free national indexes, and this scheme routes them through toll-free route pattern accessible to ordinary users.
hope this helps.
that's easy. on the ars analysis form, you can define what digits to match and where to route the matched call. we here in russia use digit '8' to access national and international telephony network, so i'll explain using our conditions.
i don't know what prefixes you should use. so, to ensure fast ars processing without delays, i do the following: create 8 strings in ars analysis, for digits 1-7, 9, string length of 7 digits, type pubu, route pattern 1 (local calls, toll-free). next one for national calls: digit 8, string length 10, type pubu, route pattern 2. and another one for international calls: digits 810 (that's our prefix for international), length 12 to 24 digits, route pattern 3. so you see, the number entered by user will be analyzed and routed accordingly. more of this, analysis will take place _in the process_ of entering digits, so if the user don't have access to national calls and press 9 (ars access fac) and next 8, he will hear busy immediately. very convenient for small setups.here is a screen shot, to make it more clear:
[pre]
display ars analysis 2 Page 1 of 2
ARS DIGIT ANALYSIS TABLE
Location: all Percent Full: 1
Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
1 7 7 1 pubu n
2 7 7 1 pubu n
3 7 7 1 pubu n
4 7 7 1 pubu n
5 7 7 1 pubu n
6 7 7 1 pubu n
7 7 7 1 pubu n
8 11 11 2 pubu n
810 12 24 3 pubu n
8499 11 11 1 pubu n
8800 11 11 1 pubu n
890x 11 11 1 pubu n
891x 11 11 1 pubu n
892x 11 11 1 pubu n
9 7 7 1 pubu n
[/pre]
note that we have 8-800 service, analogous to 1-800 in us, and some toll-free national indexes, and this scheme routes them through toll-free route pattern accessible to ordinary users.
hope this helps.
- Thread starter
- #7
dwalin,
I still have the problem. In my situation, it depends on different provider, we can use either "1" or "0" for international call. However, "1" could also be the first digit of some others local services inquires numbers provided by venders. So, I can't list each service nubmers in ars ana form. Is there any other way to accomplish my requirment? ^^
I still have the problem. In my situation, it depends on different provider, we can use either "1" or "0" for international call. However, "1" could also be the first digit of some others local services inquires numbers provided by venders. So, I can't list each service nubmers in ars ana form. Is there any other way to accomplish my requirment? ^^
- Status
Similar threads
- Locked
- Question
