![]() ![]() |
|
![]() |
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
![]()
I am working with IPO R6.0.8 and I am using call restrictions based on account codes. There are currently 150+ account codes assigned.
The customer would like to have the ability for the users to go to any phone on the system to place thier outbound calls and the client wants to be able to restrict calls based on account code and not by user/extension. I have done some research and found that this is possible to do this using Authorization codes. I have created a test authorization code of "4390" (which does not match any account codes). When a user dials "9", the ARS table is referenced. In this ARS table, if the user dial "1" followed by any numbers I have set the short code to "force authorization code". The user enters "4390" which is setup up to refer to a user right called "4390A". In the user right, short codes are set to apply to user right and there is a short code added as follows 19055656565/dial/19055656565/0. The goal here is that 19055656565 is going to be the only long distance number that this user can call, however, I am finding that the user can dial anything as long as they enter "4390" Have I missed anything? Thanks |
#2
|
|||
|
|||
![]()
The user rights are a combination of what is allowed and what is disallowed. You have only set what is allowed. You also need to create another short code 91N/Barred// to indicate that any other long distance number other than the one specified is not allowed. You may wish to add forced authorization code to the user or user rights short code for the short code 19055656565/dial/19055656565/0 as well. I am using 6.0.14 and it is functional. I setup the Authorization Code to a specific user instead of User rights but it should still work the same for the User rights.
|
#3
|
|||
|
|||
![]()
Thanks pdgavin,
I have done the shortcode 91N/Barred// and the call still goes through. I have upgraded to 6.0.14 and same thing. Even when it is the only shortcode in the user right the call still goes through. Should I be looking for anything in particular in monitor? Thanks again Mike |
#4
|
||||
|
||||
![]()
Are you sure its matching the code and going to the correct ARS table? Use sysmon to see what codes are being matched, and IF the call is reaching your intended ARS table.
|
#5
|
|||
|
|||
![]()
The call is going to the correct ARS because that is where I am forcing the Authorization Code. It doesn't seem to be referencing the user right after the code is entered.
|
#6
|
|||
|
|||
![]()
Try setting up the short code in the User form for that particular user, not in user rights. You may have to turn on Short Code Messages in the call section of Trace Options in SysMonitor in order to see which short code is being matched. It may be helpful to see how the IP Office call flow works and what order it does it's match on:
http://marketingtools.avaya.com/know...er_dialing.htm |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|