Long distance call user rights bound to account codes.

[ZebrAYA]

Is it possible to bind user rights to account codes?

We’re making and installation for a customer that formerly owned a non Avaya PBX which allowed the users to share their phones, entering an account code before dialing the desired number.
According to the dialed account code the user was granted long distance call user rights. That prevented that some malicious user could make LD calls from and extension belonging to a boss, for example.

1) Anyone has this method (or similar) implemented on IP Office?

2) If that’s not possible, could the user enter the account code before dialing the desired number (I’m trying to make the new system the most seamless for the user)


I have two pre designs

a- Giving account codes to every one, (but i only allows to track back the user moves with a CDR software) and configure all the users as agents so they can log in and log out before making any call.

B - Making short codes for every one, the shortcode would lead the user to an ARS line configured according to the user rights to call, otherwise the LD call will be blocked

 

[mattKnight]

Not to an account code i think...


However, the IPO has a feature built for this - look up Authorisation codes on the web KB

here

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[tlpeter]

This is the way to go
With the autorisation code you can select a user or a user right


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[ZebrAYA]

that’s great, i feel like unveiling avaya’s secrets

i’m creating auth codes for every user
auth codes seem perfectly right for us, I checked the force auth code on an ARS line.

except that when the user takes line, the auth code is not asked immediately but after 3 digits (I’m making the route based on that first 3 digits)

just wonder if I can force the asking for auth code from the very first digit.

Thanks ‘gain

[Always Close your threads for avoiding other people to entangle]

 

[puregold]

It asks for the auth code when the dial delay count is reached.

Im not sure if you can force an auth code at the start but you can force it at the end.

Set the dial delay count to 0, and then it will ask for the auth code when the dial delay timer expires. Hopefully this will only occur when you have finished dialling.

Slow diallers may see problems here. Set your dial delay timer accordingley.

ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor

 

[ZebrAYA]

After Reading the advice shown in this thread and reading the existing documentation I still have some questions.


Trying to implement authorization and/or account codes
I presume the only main difference between the two types of code is that auth code is bound to user (or user right) while account code belongs to a pool not bound to a specific user.
That allows me to go to another users phone and dial with my auth code, increasing rights for example if the user has no right to LD.

The other advantage is that auth code can be sent BEFORE ending LD dialing.
In fact the auth code should be dialed BEFORE, since if I have a user with call baring, anytime the user tries to make a LD call will receive a busy tone. With no chance to dial the auth code AFTER.

My current configuration is like this:
I made several (three) ARS lines with gradually LD privileges, you always got dial tone (system tone) when you press the outgoing digit, and according to the rights of the ARS line that is taken, the user will be going LD or not.
I made three ARS lines for three levels of LD user rights

Using auth code BEFORE shortcode could sound weird but quoting the document, it shows as possible.
Global_IP_Office_Technical_Tip_156.pdf Page 8
IP Office 3.2 – CaLA Authorization Codes

“In general, an Authorization Code can be either forced by dialing a short code (as seen as above) or forced on a specific user. For the latter, a User would also be specified in the User field in the Authorization Code entry (see Figure 9).
Lastly, authorization codes can be entered before dialing a short code that requires an authorization code or when prompted to enter one, after dialing a short code that requires an authorization code. Prompts to enter an authorization code consist of two short, audible tones on your handset and/or visual prompts on the phone’s display.”


[Always Close your threads for avoiding other people to entangle]

 

[ZebrAYA]

quoting puregold...

"It asks for the auth code when the dial delay count is reached."

I got it partially working adding the ";" at the end of the code.

when not ";" it always asked me the code in the middle! i mean after dialing 3 first digits.

[Always Close your threads for avoiding other people to entangle]

 

[veraguas]

hi, friends.
I need your help.

i have problem whith auth code and account code on E1 Pri Line, however on analogue trunk Line i don´t have problem.

I tested Version 4.0(14) and V4.1(9), and happened the same problem.

With Analogue Trunk Line and Auth code: asks for the auth code when the dial delay count is reached, but with E1 Pri Line: when the dial delay count is reached i get a "busy number" and a "busy tone".

Please I need your help.

Thanks..

 

[ZebrAYA]

Finally I did not use authorization codes, since they are not visible on the CDR logging software, the account codes are shown are recorded, but authorization codes appear as ***** (hidden)
So, if user B called from user A phone, we would knew that call was done from user A phone, but never that the author was user B


[Always Close your threads for avoiding other people to entangle]