Using ARS and UserRights
by DougR on Jun.13, 2008, under Avaya, Best Practices, IP Office
In 3.2 and older versions of IP Office, call restrictions could be made in System ShortCodes, User ShortCodes, Least Cost Route (LCR) tables, or in UserRights. In the post 4.0 world ARS handles the process of matching all outbound call routes. Here is a look at how to transition the restrictions based on ARS in 4.0+.
First build all the ARS tables to handle each group of calls. Typically one route, 50:Main in this example, will handle the basic calling for most users. This ARS table would have codes like these for normal calls:
- N; | N | Dial3k1 | 5
- 1N; | 1N | Dial3k1 | 5
In a second ARS table, 51:Alternate, restrict Long Distance (LD) calls using codes like:
- N; | N | Dial3k1 | 5
- 1N; | | Busy | 0
Then in a third ARS table, 52:BillingTN, set the outbound CallerID to be the main telephone number:
- N; | Nsi18007902029 | Dial3k1 | 5
- 1N; | 1Nsi18007902029 | Dial3k1 | 5
Next configure the ShortCodes in System ShortCodes, User ShortCodes, or UserRights to point to the appropriate ARS table (50:Main, 51:Alternate, or 52:BillingTN) for how the users outbound calls should be processed. Each is a simple 9N | N | Dial | shortcode with the Line Group ID pointing at one of the ARS tables.
Leave a Reply
You must be logged in to post a comment.
