Dial plan configuration

Dial plan is configured in below tables and more

1. Dialplan analysis – this is the first table always that CM looks at. The table is not
FullMatch
2. Uniform Dial Plan -
3. AAR – Automatic Alternate Routing.
4. ARS – Automatic Route Selection Analysis
5. Public Unknown numbering and private numbering
6. Inc-call-handling trunk-group x
7. Dialplan parameters
8. Feature Access Code List

Utility Server - build into AADS starting RLS 7.1.3

General
During install select to enable utility server – you will not be able to enable it later.
The utility server will provide:
1. Phone firmware upgrade
2. Phone settings files

The utility server administration page can be accessed by following link

https://<AADS IP>:8543/admin.html
The utility server will need its own IP and FQDN.
The user name and password will be as configured during AADS install.
Enable HTTP access
If you need HTTP access run below CLI command on AADS
Type cdto misc
Type sudo ./us-http-port.sh --enable
To Disable HTTP Access
Type sudo ./us-http-port.sh --disable
AADS configuration for the phones 46xxsettings.txt file
AADS dynamic configuration is now used for the 466xxsettings file.
Create the device groups.

AADS will store a different 46xx for each phone type

Create a 46xx settings file

You may create a new configuration or import an existing 46xxsettings file.

Save the file and then publish it to the phone module you want.
The 46xx is store under /var/www/html/<Device group number>
Publish the settings

Off course you may publish same file for all phone types.
Do not forget to load the certificate used using the custom file upload. (Certificate file name
is case sensitive)
Use the utility URL https://<AADS IP>:8543/admin.html

Hebrew support on J1xx phones

Currently you need to manually add the language file names into the J100Supgrade.txt file
for each J1xx phone module.
This manual change must be performed after each J1xx software loaded into AADS Utility
server.

Do not set the languages or system language in the AADS 46xx file or it will over write the
J100S upgrade file.
A sample J100Supgrade.txt file is at C:\Data\Avaya\Software Keycodes Databases
Patches\Phones\J100

Phone firmware
For each phone you want to provision you must upload and activate a firmware.
Log into Utility admin page.
Use "upload Files" to load the firmware.
Note that for files larger than 750M upload the file manually using filezilla into /tmp.

Use "Manage Phone Firmware" to unpack and activate

After loading the firmware, you MUST manually modify the upgrade file for the specific
phone type loaded and Hebrew support if needed
 /var/www/html/J100Supgrade.txt
 /var/www/html/96x1Supgrade.txt
 /var/www/html/K1xxSupgrade.txt

Use vi and add the group ID of the phone firmware as configured in the AADS.
Phone module group example as configured in AADS:

Modify the J100Supgrade.txt as below so phone will find the correct path to 46xxsettings file

Note the GET 1/46xxsettings.txt

DHCP Configuration to support phone provisioning from AADS.

Note that Avaya phones have a build in logic to get the configuration from HTTPS server
even without a
matching certificate. (Fresh phones without any previously installed certificate)
HTTP Based Access
Use option 242 as usual
HTTPSRVR=149.49.103.33
HTTPS Based Access
Use option 242 as below
TLSSRVR=149.49.103.33,TLSPORT=1543,TLSSRVRID=0
AADS Utility access log files
The logs file are under /var/log/httpd:
 access_log – will show all phone connection
 error_log