10 Jan 08 13:21
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]