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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ARS Restriction Table

Status
Not open for further replies.

mroberts

Vendor
Mar 22, 2002
1,362
US
Hi all,

I have done this before and it has worked. I am now on another system and it is not working. I shall explain.

I am working on an IPO v2 7.0.27 and I am creating a new routing table (51) that will restrict all toll calls. In that table I am adding short codes like:
Code: 1N
Telephone number: (nothing)
Feature: Barred
Line Group ID: 0

Then in the User (201) programming I am going to the short codes tab and I entered:
Code: 9N
Feature: Dial
Telephone number: N
Line Group ID: 51 (the restricted ARS table)

So user 201 should not be able to dial 9 + any phone number beginning with 1.

BUT user 201 can dial 9 and a long distance phone number beginning with 1 just fine. It goes through. I do not know what I am doing wrong here.

I built a restricted table (51) and barred 1N and then did a user short code that pushed any 9N through the 51 table. Why is it not restricting the 1+ numbers?


Thank you in advance

MRoberts
 
Did you enable "Check User Call Barring", by default it's Off

If it ain't dutch it ain't much
 
Ow, has nothing to do with it.
I have the same issue with user shortcodes.

If it ain't dutch it ain't much
 
I would put all call baring in system short codes & then add exceptions as necessary to user rights/Ars tables.

this gives a fail-safe configuration where new users will not be able to dial restricted numbers unless explicitly allowed.


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top