Global IP Office Technical Tip
156: IP Office 3.2 – CaLA Authorization Codes
*Release Date: October 23, 2006
IP Office 3.2 – CaLA Authorization Codes
Authorization codes allow a user to go to another phone and make calls using their personal toll restrictions. This may grant the user greater or fewer privileges than the phone in use. Authorization codes are independent of the currently supported Account Codes. Each authorization code can be linked with a User Template and enable logging via the Delta Server. Authorization Codes will only be visible in Manager if the registry key has been
entered. Please refer to this document to enable Authorization Codes on your IP Office system.
1 Authorization Code Specifications
Authorization codes must be unique
Authorization codes cannot be the same as a user’s extension
Authorization code length must be greater than or equal to 4 and less than or equal to 13
Authorization codes must only contain digits
2 Registry Settings
Specific registry settings are required to see the Authorization Code fields in IP Office 3.2 Manager and Delta Server.
To see Authorization Code settings in Manager, you need to set the following registry setting to one:
HKEY_CURRENT_USER\Software\Avaya\IP400\Manager\EnableAuthorizationCodes
Figure 1: Enable Authorization Code Registry Setting For call logging purposes, the authorization code field will not be displayed under the recent
SMDR view, but they will be added to the following SMDR outputs:
SMDR via COM port
SMDR.csv file
To enable authorization code logging in SMDR, two registry entries must be added:
allowauthorization
ShowAllowAuthorization
These two values must exist in the registry table and set to one.
HKEY_LOCAL_MACHINE\SOFTWARE\Avaya\CCCServer\Setup
Figure 2: New Registry Entry – allowauthorization
3 Authorization Code Logging in SMDR via DeltaServer
Start DeltaServer service and DeltaServer web client. Check “Add Authorization Code Fields to SMDR” under “Comms”. Verify that “Comms Status” is “Comms Restored.”
Two new fields will be added to the current SMDR output.
• Auth. Valid – Indicating whether the authorization code entered by user is valid or not. “0” means “invalid” while “1” means “valid.” There are two cases for invalid authorization code. The first is that the system does not have such an entry in the authorization code list. The second one is that the authorization code does exist but its call privilege is not high enough to make the call.
• Auth. Code – The authorization code provided by the user. If no authorization code is required, “n/a” will be filled in.
Figure 3: New Checkbox to Add Authorization Code to SMDR
Figure 4: Authorization Codes in SMDR
86061mS
CALL:2005/05/2013:35,00:00:08,000,206,O,011441707299977,90114417072999777747#,Extn206,,,0 ,,"",7747,1
105424mS == Fri May 20 13:36 [192.168.42.1]
108430mS CALL:2005/05/2013:36,00:00:00,000,206,O,0,90,Extn206,,,1,,"",n/a,0 130016mS
CALL:2005/05/2013:36,00:00:00,000,207,O,011441707299900,90114417072999007738#,W.GUO,,,1,, "",7738,0 155506mS
CALL:2005/05/2013:36,00:00:00,000,207,O,011441707392200,90114417073922001234#,W.GUO,,,1,, "",1234,0 163952mS == Fri May 20 13:37 [192.168.42.1]
184965mS
CALL:2005/05/2013:36,00:00:12,000,207,O,17328521933,917328521933,W.GUO,,,0,,"",n/a,0 222465mS == Fri May 20 13:38 [192.168.42.1]
226618mS CALL:2005/05/2013:37,00:00:20,006,210,O,207,207,Extn210,,,1,,"",n/a,0
Figure 5: Sample SMDR log with Authorization Code fields
4 Configuring Authorization Codes in Manager 3.2
4.1 Forcing an Authorization Code when using a Short Code
After setting the authorization code registries to one on the Manager PC, the Force
Authorization Code checkbox will now be viewable and editable when editing an existing short code or when creating a new short code. Checking the Force Authorization Code box will require any user that dials the short code to enter a valid authorization code (see Figure 6). The authorization code must be associated to a User Rights entry to allow or disallow the dialled digits to be dialled.
Figure 6: Short Code with Force Authorization Code checkbox
4.2 Creating a User Rights Entry
A User Rights entry must exist before creating an authorization code. A name needs to be entered for the user rights entry within the User tab (see Figure 7). All short codes that will be used to restrict users under this User Rights profile must be entered in the ShortCodes tab (see Figure 8).
Figure 7: User Rights Entry
Figure 8: User Rights Short Code Entries
4.3 Creating an Authorization Code
To create an Authorization Code, simply click on Authorization Code option on your left- hand side menu in Manager 3.2. Then, click the Create a New Record icon . Enter a unique authorization code and associate it to an existing User Rights entry by selecting one of the available options in the User Rights pull down menu just below the authorization code that was previously entered. Click OK, and save your configuration file.
Figure 9: Authorization Code Entry
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.
1-800-429-0077
  
|
