Avaya IPOSE (Server Edition) Setup

This document provides a setup guide on initialising and configuring an IPOSE (IP Office Server Edition)

It covers the below

12. IPOSE Ignition Process
13. Configure System Settings
14. System Name, Locale, Messaging Server, SIP & H.323 (IP Phone), SMTP, SIP Domain/FQDN, Telephony and VOIP Security
15. Licensing
16. Security and Access
17. Certificates Setup
18. Voicemail Setup
19. User and Extension Setup
20. Connecting J Series Handset
21. IX Workplace Softphone – Windows Install and Configuration
22. IX Workplace Softphone – Android Install and Configuration
23. Testing

URL Access Links of reference

Web Manager

https://x.x.x.x:7070/WebManagement/WebManagement.html

Server Control

https://x.x.x.x:7071

46xxsettings File

https://x.x.x.x/46xxsettings.txt

Network Assumptions

The below documents system is configured to use a valid Domain and FQDN

If using J Series and IX Workplace softphone remotely the below ports will need to be allowed through the firewall and directed to the internal IP address of the IPOSE

411 TCP (secure access)

5061 TCP (secure registration)

40750 through to 50750 UDP (voice traffic)

Additionally, if the customer would like to use the IX Workplace softphone and J Series internally on the local network where the IPOSE system is located. Then they need to create an internal DNS record to resolve the FQDN to the internal IP address of the IPOSE.

This is to prevent the IX Workplace softphone and J Series handset resolving the FQDN to the public IP address and so routing traffic out to the internet which then routes back to the internal network and causes issues with no voice (this is known as hair pinning)

IPOSE Ignition Process

Browse to the public IP address of the instance: https://x.x.x.x:7070

Login: Username: root / Password: Administrator

Agree to EULA

Select the Server Type

Configure any new hardware (if using an additional drive for call recording it will show here)

Networking details will remain (as this is in AWS it does not need to be changed)

Enter a Hostname of the instance, example company name

Select the Time Zone and set the Companding as A-law

Enter the passwords for root/security, Administrator and System

Write these down and save somewhere (they can be updated in the future)

Generate a new CA certificate

Select OK to the warning

Confirm the setup and Apply

The system will reboot and apply the changes, allow 20 minutes for this before trying to access the below URL’s again

Web Manager

https://x.x.x.x:7070/WebManagement/WebManagement.html

Server Control

https://x.x.x.x:7071

Confirm the landing pages for both URL above work

Provide the dealer with the above URL’s (they will login as Business Partner)

Do not give out the Administrator, System or Security passwords

Access Web Manager

Example URL: https://x.x.x.x:7070/WebManagement/WebManagement.html

Username: Administrator / Password: (as configured in setup)

Agree to the EULA

Select Yes to the warning about synchronization

When logging into Web Manager you will be advised of the Login History, click OK

Configure System Settings

System Name, Locale, Messaging Server, SIP & H.323 (IP Phone), SMTP, SIP Domain/FQDN, Telephony and VOIP Security

Select Solution, drop down on the system to view the current setup and services

Select the icon at the top right and select Offline Mode

Select OK to the Information

Select System Settings, System

Select the three horizontal lines to open the System settings

Enter a Name for the system

Set the Locale to Australia

Set Messaging Server to Avaya Spaces

Enable Softphone HTTP Provisioning

Select SMTP tab

Enter the SMTP details (this will be used if alarms are setup to be emailed in System Events tab)

Select LAN1 tab

Enable H.323 Gatekeeper and H.323 Remote Extension

Enable SIP Register and SIP Remote Extension

Enter the SIP Domain and SIP Registrar FQDN

Enable TLS

Set Keepalives Scope to RTP-RTCP and set the Periodic Timeout to 5 seconds and enable Initial Keepalives

Select the Network Topology sub-tab in LAN1 tab

Enter the Public IP Address of the Avaya Phone System

Select VoIP tab

Set Media Security to Preferred

Select Telephony tab

Set Dial Delay Count to 16

Set Hold Timeout to 60 seconds

Enable DSS Status

Disable Inhibit Off-Switch Forward/Transfer

Disable Drop External Only Impromptu Conference

Select Telephony tab

Select Avaya Push Notification Service and Enable Avaya Push Notification Services

Select Update

Select Save to IP Office

Login and confirm the Name and Locale have updated

Licensing

Select System Settings, Licenses

Select the three horizontal lines to open the System settings

Select PLDS License and Send to IP Office

Locate and select the license file and select OK

Return to licenses and confirm the licenses are showing and valid

Security and Access

Select Security, Security Settings, Select the system

Select System on the left and Unsecured Interfaces tab

If required update the System password, Voicemail password (minimum 31 characters) and Monitor password

Example Voicemail Password: 1357924680135792468013579246809

Set all Application Controls to No

Select Security, Security Settings, Select the system

Select Service Users on the left

Edit Administrator and if required update the password

Select BusinessPartner and update the password (this will be provided to the dealer for access)

Delete CustomerAdmin, DirectoryService and MCMAdmin 

The Service Users remaining will be the below

Select Security, Security Settings, Select the system

Select Rights Groups on the left

Edit Business Partner

Set Default Configuration to No and Save

In Rights Groups delete Customer Admin, Directory Group, MCM Admin, Management API Groups

The remaining Rights Group will be the below

Access the system on port :7071

Example: https://x.x.x.x:7071

Select Settings, General

Update the Subject Alternative Name(s) to include the system name, FQDN, Domain, Internal IP and Public IP

Example: DNS:harrylab, IP:192.168.152.48, DNS:harrylab.cpdcloud.com.au, IP:52.63.29.182

Select Regenerate and Apply

Select Yes

The Avaya system will restart, this can take 10 minutes

Once restarted, access the Avaya system on port: 7071

Example: https://x.x.x.x:7071

Select Settings, General, Certificates

Download the DER-encoded CA Certificate (root-ca.crt)

This will be used later when installing IX Workplace

Voicemail Setup

Select Application, Voicemail Pro – System Preferences

Select the three horizontal lines to open the System settings

Set the Default Telephony Interface to IP Office

Set the Voicemail Password to match the Voicemail password set in security

Select Email on the left

Edit the default SMTP Sender

Update the SMTP settings (example below)

Test Connection to confirm successful and save

Confirm the new settings are now showing

The Voicemail service needs to be restarted for the changes to take affect

Open a new browser and login to https://x.x.x.x:7071

Username: Administrator / Password: (as configured in setup)

Stop and Start the Voicemail Pro service

Check voicemail is running

Browse to system status (use IE if you have issues with Java) or use System Status installed locally

https://x.x.x.x/ssa/index.html

Username: Administrator / Password: (as configured in setup)

Select Yes to the warning about unsecure connection

Check Voicemail and confirm it is showing Voicemail Type as Voicemail Pro

User and Extension Setup

Access Web Manager

Example: https://x.x.x.x:7070/WebManagement/WebManagement.html

Username: Administrator / Password: (as configured in setup)

Select Call Management, Users

Select Add User (top right) and select the system and OK

Configure a Name, Full Name, Password and Extension Number in the User tab

Set the Profile (license) as Power User)

Configure a voicemail code and email address and set voicemail email mode to copy in the Voicemail tab

Enable Reserve Last CA in Telephony tab

Enable Web Self-Administration in Web Self-Administration tab

Select Create

If the user will be using a physical handset, then select a SIP Extension (J series) or H.323 Extension (96 series)

Enter a login (suggest this to be the same login code as setup for the user)

Select OK

Select Call Management, Extensions

Confirm the extension created for the new user is showing

Edit the extension and disable Allow Direct Media Path and Save

Connecting a J Series handset

Connect the J series handset to the network (with internet access if Avaya is not onsite) and wait for the handset to power on

When prompted select No to “Do you want to allow Auto Provisioning”

Wait for the phone to obtain IP address details from the local DHCP server

Wait till you are asked to enter the File Server Address (select Config)

Or you will be asked to enter Provisioning Details

Enter the IP address of the Avaya system

This could be a local LAN IP address if the handset is on the same network as the Avaya system

Or a public IP address if the handset is on a remote site and not the same network as the Avaya system (recommended to use secure port)

Example: http://x.x.x.x

Example: http://x.x.x.x:8411 (unsecure port)

Example: http://x.x.x.x:411 (secure port)

If no DHCP server is available on the network, select Admin and enter the passcode CRAFT and OK to enter the programming and in IP Address and Ethernet IPv4 enter

Disable Use DHCP

Statically Assign the below

Phone IP

Gateway IP

Mask IP

Save and Exit

Then wait till prompted and enter File Server Address (as per the above)

The J series handset will contact the Avaya system and upgrade any firmware required

Once firmware has been upgraded you can login with the extension number and login code

Check System Status to confirm you can see the handset registered

Certificate Installation

Locate the certificate downloaded earlier

Right click and select Install Certificate

Select Local Machine, select Next

Select Trusted Root Certification Authorities, select Next, select Finish

Browse to the 46xxsettings file location

Example: https://harrylab.cpdcloud.com.au/46xxsettings.txt

There should be no warning of the site been unsecure and you will see a padlock next to the URL to indicate it is secure

You should also see the 46xxsetings file

Test access to the Web Manager URL using the FQDN to confirm that is also secure 

Test access to the server control URL using the FQDN to confirm that is also secure

IX Workplace Softphone – Windows Install and Configuration

Select the settings icon and select Use Web Address

Enter the 46xxsettings URL string

Example: https://harrylab.cpdcloud.com.au/46xxsettings.txt

Select Next

Enter Extension and Password, select Next

Skip the tutorial pop up

IX Workplace softphone will be logged in (with green tick at top left)

Select Top of Mind to edit hide sections on the home screen, example below hidden Next Meetings and Workplace Meetings

Instant Messaging is not showing as the system is configured to use Avaya Spaces and we have not setup Avaya Spaces account in this document (that would be addressed in a different document)

IX Workplace Softphone – Android Install and Configuration

Email the certificate to the android device

Download the certificate on the android device

Select Settings, search certificates

Select Install Certificates

Select CA Certificate

Select the certificate downloaded (root-ca.crt)

Enter a name for the certificate, select OK

Select Settings, search certificates

Select Security, VPN & App User Certificates

Select VPN & App User Certificates

Confirm the certificate is showing in the list

Install IX Workplace and open IX Workplace

Accept EULA, select OK

Select Configure my Account

Repeat the steps in screen shots above (see IX Workplace – PC)

Select the settings icon and select Use Web Address

Enter the 46xxsettings URL string

Example: https://harrylab.cpdcloud.com.au/46xxsettings.txt

Select Next

Enter Extension and Password, select Next

Skip the tutorial pop up

IX Workplace softphone will be logged in (with green tick at top left)

Select Top of Mind to edit hide sections on the home screen, example below hidden Next Meetings and Workplace Meetings

Instant Messaging is not showing as the system is configured to use Avaya Spaces and we have not setup Avaya Spaces account in this document (that would be addressed in a different document)

Check System Status and confirm that the extension is showing on the 3 devices

J series handset

IX Workplace Windows App

IX Workplace Android App

Testing

Add additional users and extensions as required and make test calls between extensions to confirm calls working

Testing Checklist

1. Call From J Series Handset to J Series Handset Connected and Voice OK

2. Call from J Series Handset to IX Workplace Windows App Connected and Voice OK

3. Call from J Series Handset to IX Workplace Android App Connected and Voice OK

4. Call from IX Workplace Windows App to J Series Handset Connected and Voice OK

5. Call from IX Workplace Android App to J Series Handset Connected and Voice OK

6. Call from IX Workplace Windows App to IX Workplace Android App Connected and Voice OK

7. Call from IX Workplace Android App to IX Workplace Windows App Connected and Voice OK

8. Voicemail left on extension and retrieved from J Series handset

9. Voicemail left on extension and retrieved from IX Workplace Windows App

10. Voicemail left on extension and retrieved from IX Workplace Android App

11. Voicemail left on extension and received on email