Avaya IPO Creating a Default Config and Using Binary Data and Templates to Program a System

It is recommended to use templates and/or binary data

You can create a default config containing default programming and upload that config into a new system, then adjust any programming

However, be aware, as new versions of firmware are released, new settings become available. If you had created a default config in V10 then attempted to import into a V11 system, it could have issues with not writing correct data into new settings available in V11

When a new major version becomes available, it is recommended to create a new default config with the Manager of the new version and use that default config on system in that version only

For example, when V12 is released, download and install Manager V12 then create a new Offline Config as a default using Manager V12 and use that config on V12 systems only

To create a config offline

In Manager, select File, Offline, Create New Config

In the Configuration Creation you can create a config with specific cards/modules

Leave this all as default and select OK to create the config

As each system will have specific settings

We cannot export System data as a template or binary

It would be best practice to program the generic System data in the default config

For example, in the System, Telephony tab, Telephony sub-tab you might want to setup all systems with a Hold Timeout of 120 seconds

Once you have configured the System data in the default config

Save the config as a offline file

Select File, Save Configuration As

Select a location and enter a name for the file and select Save

Anytime you now select the Save icon (retro floppy disk icon on top bar) or select File, Save Configuration. it will save the changes to this IPODefaultConfigV11.cfg file

SIP Lines can be programmed in a default config. These lines can then be exported as a template or binary data

In our example we have created our SIP line

Right click on the SIP line and select Export as Template

Select a location and enter a name for the SIP line template and select Save

You can import this template into any config, to import into a config

In lines, right click and select New from Template – Open from File

Browse to the folder where the SIP line template was saved

Change the Template File type to .xml

Select the template and select Open to import

SIP Credentials are not saved in templates

You will need to add the SIP Credentials into the newly imported SIP line

Extensions can be programmed in a default config. These Extensions can then be exported as a template or binary data

To create a new SIP Extension, right click and select New – SIP Extension

The Extension ID does not need to be changed

Configure the Base Extension as the first extensions on the system

Configure the Phone Password (this will be the login code used)

Untick the Allow Direct Media Path box

Select OK to create the Extension

To export the Extension as a template, right click on the Extension and select Export as Template

Select a location and enter a name for the SIP Extension template and select Save

You can import this template into any config, to import into a config

In Extensions, right click and select New from Template – Open from File

Browse to the folder where the Extension template was saved

Select the template and select Open to import

Set the number of records to import and the start extension number

As we already created Extension 201, we have started at Extension 202 and will add 9 records

Select OK

The SIP Extensions will be created, all with the same login code used

3rd Party SIP Extensions will use a SIP Extension

Digital and Analogue Extensions cannot be created via templates

If you are installing a system with Digital and/or Analogue Extension cards, then these Extensions will be created automatically by the cards in the system and display when you receive a new config from the system. You can then configure these Extensions with different numbers/settings

H.323 Extensions can be created; these are required if using an old IP phone model 

(96XX Series or 16XX Series)

Users can be programmed in a default config. These Users can then be exported as a template or binary data

If you are installing a system with Digital and/or Analogue Extension cards, then a User for each Extension will be created automatically by the cards in the system and display when you receive a new config from the system. It would be recommended to delete these auto created Users and create Users for these using the method below

To create a new User, right click and select New

Configure the User settings (remember these will be generic)

Select OK to create the User

Recommended generic User settings to configure would be

User tab

Name

Password

Full Name

Extension

Voicemail tab

Voicemail Code

Telephony tab – Supervisor Settings subtab

Login Code

Telephony Tab – Multi-Line Options subtab

Enable Reserve Last CA

Web Self Admin / User Portal

Enable access as required

To export the User as a template, right click on the User and select Export as Template

RemoteManager user can be deleted, this was used to provide an ability to dialin to a system over an ISDN or Analogue PSTN line

NoUser should remain on the system, if a phone is connected and registered as an Extension but doesn’t have a User matching the Extension. Or if a User is logged out of a phone.

Then the phone will become NoUser and there will be an option on the buttons to select Login and login as a User (using the users extension number and login code)

Select a location and enter a name for the User template and select Save

You can import this template into any config, to import into a config

In Users, right click and select New from Template – Open from File

Browse to the folder where the User template was saved

Select the template and select Open to import

Set the number of records to import and the start extension number

As we already created User Extension 201, we have started at User Extension 202 and will add 9 records

Select OK

The Users will be created, all with the same generic settings are configured in each User

Groups can be programmed in a default config. These Groups can then be exported as a template or binary data

It is recommended to create Groups in the config for each possible requirement

Enter a Name, Extension Number and Voicemail Code for each group

Depending on the customers’ requirements will depend on how you configure the Groups

Groups created can be exported individually and saved as a template, these templates can then be imported into any config

To export the Group as a template, right click on the Group and select Export as Template

Select a location and enter a name for the Group template and select Save

You can import these templates into any config, to import into a config

In Groups, right click and select New from Template – Open from File

Browse to the folder where the Group template was saved

Select the template and select Open to import

Short Codes cannot be exported as a template

In the default config you will need to create a Short Code to access the voicemail of Groups using Voicemail, you might also need to create a Short Code to be used in Night/Out of service/Group No Answer Destinations to send calls to a Group voicemail

Example below is to access the Day Group, to record greetings for a Group you need to access the Group voicemail via a Short Code and select 3 and follow the prompts

Example below is to send a call to the Night Group voicemail

For further explanations on Group and Group Voicemail configuration. Refer to the articles “Avaya IPO Manual Night Mode” and “Avaya IPO Time Profile Night Mode” available on the CommsPlus PRC site

A Dial Emergency Short Code should also be configured in the system Short Codes to route 000 calls out via the line (example below is using the SIP line 17)

RAS It is recommended to delete the DialIn from the RAS, this was used to provide an ability to dialIn to a system over an ISDN or Analogue PSTN line

Incoming Call Routes cannot be exported as templates

It is recommended to delete the entry with Destination DialIn, this was used to provide an ability to dialIn to a system over an ISDN or Analogue PSTN line

It is also recommended to configure the default entry with the Line Group ID (usually 17 as majority of systems are using SIP) and the Destination as the Day Group

Time Profiles can be programmed in a default config. These Time Profiles can then be exported as a template or binary data

Time Profiles created can be exported individually and saved as a template, these templates can then be imported into any config

To export the Time Profile as a template, right click on the Time Profile and select Export as Template

Select a location and enter a name for the Time Profile template and select Save

You can import these templates into any config, to import into a config

In Time Profile, right click and select New from Template – Open from File

Browse to the folder where the Time Profile template was saved

Select the template and select Open to import

IP Route cannot be exported as a template

It is recommended to create a default route entry in IP Routes

In the example below we have programmed all traffic to route to 192.168.42.254 via LAN1

User Rights cannot be exported as a template

It is recommended to delete the default User Rights in the config (leaving Application)

Right click and select New

Configure the User Right with generic settings and apply to the Users

Remember to set Apply User Rights value to any settings configured that need to be applied to the Users assigned to the User Right

Example below shows button programming configured and set to applied

Once the default config has been configured

Select the Save icon (retro floppy disk icon on top bar) or select File, Save Configuration. it will save the changes to this IPODefaultConfigV11.cfg file

Uploading the default Config to a new system

Install the cards in the new system, power on and connect the laptop to the system

Open Manager and login to the system and follow the steps to configuring the initial setup and security

Once the config appears, select File, Save Configuration, and reboot immediately

While the system is rebooting, select File, Close Configuration

Select File, Offline, Open File

Browse to the folder location of the default config, select the config, and select Open

Once the config has opened

Select File, Save Configuration As

Browse and select a location for the config

Rename the file as the company name and select Save (example CompanyA)

Make any customer specific programming changes required to the config

When finished select File, Save Configuration (this will mean the CompanyA.cfg has the customer specific config programming saved offline)

Select File, Offline, Send Config

Select the system

Enter the Username and Password and select OK

The config for CompanyA will be sent to the system and the system will reboot

You can program CompanyA config details without the system

Open the default config with Manager

Save the conifg as a new file (example CompanyA)

Make the customer specific programming changes required

When finished select File, Save Configuration (this will mean the CompanyA.cfg has the customer specific config programming saved offline, ready to upload when you have the system available

Binary Export/Import

It is an option to export one or multiple parts of the programming from one config and import into a new config

To Export

When a config is open

Select File, Import/Export and Select Export

Change the location the file will be saved to

Change the File Type to Binary

Select the items to export and select OK

To Import

When a config is open

Select File, Import/Export and select Import

Change the location the file will be saved to

Change the File Type to Binary

Select the items to import and select OK