Avaya IP Office Phone Systems

Avaya IP Office

The Avaya IP Office platform is the ultimate in converged voice and data technology. IP Office brings a combination of voice and data applications formerly reserved for only the largest corporations. Cutting edge customer service with easy to use tools is now available to the smallest of businesses.

Overview of Authorization Codes

•  WARNING: Changing PC Registry Settings
  Avaya no liability for any issues arising from the editing of a PC's registry settings. If you are in any doubt about how to perform this process you should not proceed. It is your responsibility to ensure that the registry is correctly backed up before any changes are made.

Enabling Authorization Codes in Manager
To enable support for authorization codes within Manager requires a change to the Manager PC registry settings. Once this change is made, various authorization code related features are visible when Manager is restarted and a configuration from a 3.2 or higher system is loaded.

1. Close Manager.  

2. Locate the registry key HKEY_CURRENT_USER\Software\Avaya\IP400\Manager\EnableAuthorisationCodes and change its value from 0 to 1.

3. Restart Manager and load a configuration from an IP Office 3.2 or higher system.   

Enabling Authorization Codes in Delta Server
The use of authorization codes can be included in the SMDR output logged by the IP Office Delta Server application. Again this requires changes to the registry of the PC running the Delta Server application.

1. Open the registry and locate the HKEY_LOCAL_MACHINE\Software\Avaya\CCCServer\Setup registry keys.

2. Add two new DWORD registry keys and set their values to 1. They are:

3. • AllowAuthorization.

   • ShowAllowAuthorization.

3. Open the browser to the Delta Server configuration screens.

4. Select SMDR. An Add Authorization Fields to SMDR option should now be available. Select this to enable logging of authorization codes to the SMDR log file.

The use of authorization codes is not shown in the Recent SMDR screen. They are only logged to the SMDR log file. Two new fields are added to the end of each call log record in the SMDR log file. The first new field is the authorization code used or n/a if no authorization code was used. The second field is 1 for valid authorization or 0 for invalid authorization.

Forcing Authorization Codes
There are two methods to force a user to enter an authorization code in order to complete dialing an external call. When this occurs, the user must enter an authorization code that is associated with them or the user rights to which they as associated. In an incorrect authorization code is entered 3 times, the user is blocked from further attempts for the next minute.

• To Force Authorization Codes on All External Calls
  A user can be required to enter an authorization code for all external calls. This is done by selecting Force Authorization Code on the User | Telephony tab.

• To Force Authorization Codes on Specific Calls
  To require entry of an authorization code on a particular call or call type, the Force Authorization Code option should be selected in the short code settings. This can be used in user, user rights or system short codes in order to apply its effect to a user, group of users or all users respectively.  You need to ensure that the user cannot dial the same number by any other method that would by pass the shortcode, for example with a different prefix.

Entering an Authorization Code
Where possible, when an authorization code is required, the user can enter it through their phones display. However this is not possible for all type of phone, for example it is not possible with analog phones and Avaya XX01 or XX02 phones. The users of these device must either enter the authorization code using Phone Manager or by using a shortcode set to the Set Authorization Code feature immediately before making the call.

When entry of an authorization code is triggered, the user can enter any authorization code with which they are either directly associated or associated through their current user rights.*1

Note

1. It is possible to create an authorization code which has no associated user or user rights. Such an authorization code is useable by any user. However this is deprecated as not being the intended purpose of authorization codes.

2. If account code entry is setup for a particular number, calls forwarded or transferred to that number will also trigger account code entry.

3. On systems using line appearances to BRI trunk channels to make outgoing calls, account code entry may not be triggered. This can be resolved by adding a short code such as [9]XN;/Dial/XN/0 (adjust the prefix and line group as necessary).

Authorization Code Settings

• Authorization Code: Range = Up to 12 digits.
  The digits used for the authorization code. Each code must be unique. Wildcards are not useable with authorization codes.

• • User Rights
    This field is used to select the user right with which the authorization code is associated. The authorization code can then be used to authorize calls made by users currently associated with that set of user rights.

  • User
    This field is used to select a user with which the authorization code is associated. The authorization code can then be used to authorize calls made by that user.