Avaya IPO Instance Move from one IPOSE Instance to Another

4. Migrating an existing Avaya IPOSE instance from one platform 
5. Avaya JSeries and Workplace registered using Avaya Self-Signed Certificate
6. SIP Trunks Registered (using credentials)
7. Callflows in Voicemail Pro

Note: Media Manager (call recording) is not part of this document. If the instances been moved has Media Manager and call recording, you need to have the internal LAN1 IP address on the new IPOSE instance the same as the LAN1 IP address on the existing IPOSE instance. You can then follow the separate guide on migrating Media Manager from one instance to another.

Configuration Backup

Access the existing IPOSE Instance with Manager and receive a new config.

Select File, Save Configuration As and save the config.cfg file.

Open the configuration file with Manager offline.

Select File, Import/Export and select Export.

Change the File Type to Binary.

Tick the boxes below.

Select OK to save the file (make a note of the directory it is saved to).

Note: You cannot save a config (File, Save Configuration As) from the existing and then restore to the new instance, as this will cause issues with the licensing not to register. You need to use the import/export binary method.

Voicemail Backup

Use Voicemail Pro Client to access and download the latest voicemail call flow database.

Select Administration, Preferences, General

Take screen shots of the General tab and the Email, SMTP Sender Configuration

Select File, Import/Export and select Export.

Select Export Data.

Select a location and enter a name for the entire database to backup.

Complete the backup.

Access the existing IPOSE Instance via Web Manager (port 7070)

Select Applications, File Manager

Browse to Disk, vmpro, Greetings

Download the greeting files

Repeat the process for Disk, vmpro, Names

Repeat the process for Disk, VMProCustomPrompts

Voicemail Pro SFTP Backup

It is also recommended to use a SFTP client (example WinSCP or Bitvise) to access and download the folders in the following directories.

/opt/vmpro/Accounts – this contains folders for each user and group on the system and contain any voicemails they have

/opt/vmpro/Names – this contains files for each user and group on the system who have recorded their name

/opt/vmpro/Wavs/CustomPrompts – this contains files used in Voicemail Pro call flows

/opt/vmpro/Wavs/CustomPrompts – this contains files used in Voicemail Pro call flows (download any individual .wav or .opus files

Music on Hold Backup

Access the existing IPOSE Instance via Web Manager (port 7070)

Select Applications, File Manager

Browse to System, Primary

Search and download any wav files (music on hold files)

PLDS License Backup (if using PLDS not Subscription Licensing)

Access the existing IPOSE Instance via Web Manager (port 7070)

Select Applications, File Manager

Browse to System, Primary

Search and download the PLDS license files (this is for reference only)

New Instance Setup

Spin up the new IPOSE instance

Confirm an Elastic IP has been assigned.

Access the new IPOSE instance via Platform View (port 7071)

Complete the Ignition process.

Access the new IPOSE instance via Web Manager (port 7070)

Complete the System Initial Configuration (screen shots below)

Note: if the new IPOSE instance will be in subscription mode and will be using the existing IPOSE instance subscription details, it is recommended to set the new instance to PLDS licensing and not subscription. Then generate a 30 day trial license to have the new IPOSE instance licensed and running. 

Then when the existing IPOSE instance is switched off, the new IPOSE instance can be changed to Subscription licensing using the Initial Configuration in Manager or Web Manager and the subscription for the customer in the COM Server can be updated to license the new IPOSE instance.

Guides for creating a trial license and configuration subscription licensing can be found on the CommsPlus PRC knowledgebase.

System Configuration

Set the System Mode as required.

2. Server Edition or Server Edition Select if using PLDS licensing (check the licensing on the existing system to confirm which mode is required
3. Server Edition Subscription if using a new Subscription licensing (not been used by the existing IPOSE instance) enter the subscription details to license the system.

Set the System Name as required.

Set the Locale

Note: in our setup we do not have a Server Edition Secondary

Select Apply.

VoIP Configuration

Enable the required settings.

Set the SIP Domain Name and SIP Registrar FQDN as required.

Select Apply

Note: The Domain Name/FQDN might be staying the same, as per our setup. We will program this new IPOSE instance with the same details, then update the public IP of the Domain/FQDN to the public IP address of the new IPOSE instance when testing/cutting over.

Voicemail Configuration

Select the HoldMusic.wav file and upload.

If additional holdmusic files are required, repeat the process to upload these.

Select Apply

Saving the Initial Configuration Details

As we will use the Binary Import to upload the rest of the configuration details

Select Save to IP Office

Select the system and select Immediate and select OK

System Configuration

Access the new IPOSE Instance with Manager and receive a new config.

Select System and configure the settings as required (compare to the existing IPOSE instance config) 

Examples below of basic settings to review.

Set Messaging Server to Avaya Spaces

Enable TLS (confirm port)

Enable Keepalive settings.

Set the Firewall/NAT Type

Configure the Public IP Address

Set the CLI for the Voicemail SIP Settings

Review and amend as required the Telephony Settings and Telephony/Tones & Music

Review and amend as required the VoIP Settings (specifically the Media Security)

Review and amend as required the Avaya Cloud Services Avaya Push Notifications Services

NOTE: it is recommended to setup but leave Enable Settings File URL sync as Disabled (otherwise the system will sync with Avaya Spaces and update the JSON file). Additionally leave Enable User Synchronization un-ticked. Both these can be enabled after cut-over.

Uploading Binary Configuration Data

Access the new IPOSE Instance with Manager and receive a new config.

Select File, Import/Export and select Import.

Change the File Type to Binary.

Tick the boxes below.

Select OK to restore the data to the configuration.

SIP Line Configuration

NOTE:  The imported Binary Data for line will import the SIP lines, you will need to disable / un-tick the In Service on the SIP Line. So that the new IPOSE instance does not register the SIP. When testing this can be enabled once the SIP has been put out of service on the existing IPOSE.

License Configuration

If using Subscription confirm the Subscription licenses are valid (Guides for configuration of subscription licensing can be found on the CommsPlus PRC knowledgebase)

If using PLDS (or PLDS trial license, until subscription from existing to new IPOSE is configured)

Set the Remote Server Configuration as Local

Set the SIP Trunk Sessions

Rehost the existing PLDS licenses to the new PLDS Host ID and upload

Or create and upload the PLDS trial license, until subscription from existing to new IPOSE is configured)

Save the configuration back to the new IPOSE instance and reboot.

Close and open a new configuration once the reboot has completed.

Check the configuration is correct.

Security Settings Configuration

Access the Security Settings using Manager.

Review and amend as required the Rights Groups and Service Users

Review and amend the System/Unsecured Interfaces

If using Workplace and Avaya Spaces.

Create a new API key in Avaya Spaces against the company.

Update the Security Settings with the Avaya Spaces API Key and Key Secret.

NOTE: Do not use the existing API key in Avaya Spaces which is synced with the existing IPOSE, create a new one for the new IPOSE instance.

Save the Security Settings when finished.

File Manager Configuration

Access the new IPOSE Instance via Web Manager (port 7070)

Select Applications, File Manager

Browse to Disk, vmpro, Greetings

Upload the greeting files

Repeat the process for Disk, vmpro, Names

Repeat the process for Disk, VMProCustomPrompts

Once files have been uploaded to the VMProCustomPrompts folder, you will need to select them all and then select the Apply Prompts icon, to make them available in Voicemail Pro call flows.

Voicemail Pro Configuration

Use Voicemail Pro Client to access and download the latest voicemail callflow database.

Select Administration, Preferences, General

Update the configuration as per the screen shots taken of the existing IPOSE Instance

Select File, Import/Export and select Export.

Select Import Data.

Select the location of the backup file taken from the existing IPOSE instance.

Complete the restore.

Check the Modules to confirm the correct audio files are showing (with a length)

Select File, Save & Make Live to save the callflow and settings to the new IPOSE instance.

Certificate Backup

The below are steps required, if the existing IPOSE instance is using Avaya Self Signed Certificates

Backing Up the CA Certificate (Root Certificate)

Access the existing IPOSE Instance via Platform View (port 7071)

Select Settings and in Certificate, CA Certificate.

Select Export

Enter a Password (and Confirm Password)

Select Encrypt and Download

In the window that appears, select the root-ca-p12 to download and save the file.

Then click OK to close the window.

Creating a new Identity Certificate for the new IPOSE Instance (Identity Certificate)

Access the existing IPOSE Instance via Platform View (port 7071)

In Create Certificate for a Different Machine.

IP Address – Enter the public IP address of the new IPOSE instance.

Password (and Confirm Password – Enter a Password.

Subject Name: Enter the FQDN that will be assigned to the new IPOSE instance.

Subject Alternative Name: Enter the required details (in our example we have only needed the DNS:FQDN)

Select Generate

In the window that appears, select the server identity certificate-p12 to download and save the file.

Then click OK to close the window.

Certificate Configuration

Uploading the CA Certificate (Root Certificate)

Access the new IPOSE Instance Platform View (port 7071)

Select Settings, General

In Certificates / CA Certificate

Select Import

Browse and select the CA Certificate (root certificate) exported from the existing IPOSE instance.

Enter the password used when exporting that CA Certificate.

Select Upload.

Select Yes

Select OK

Uploading the Identity Certificate

Access the new IPOSE Instance Web Manager (port 7070)

Select Security and select the edit icon.

Select Certificates

In Identity Certificate select Set.

Browse to the Identity Certificate (created and downloaded from the existing IPOSE instance)

Enter the Password

Select Upload

Select OK.

A message will show.

Wait a few minutes then login again to Web Manager.

Select Security and select the edit icon.

Select Certificates.

In Identity Certificate confirm the Issued To is now the correct one.

Additionally in the Trusted Certificate Store you will see the CA root Certificate.

You can select View to check and confirm the Issued By and Issue To are correct

Creating and Importing the WebRootCA.pem

Access the new IPOSE Instance Platform View (port 7071)

Select Settings, General

In Certificates / CA Certificate

Select Download (DER-encoded)

Save and rename the file to WebRootCA.pem

Access the new IPOSE Instance Web Manager (port 7070)

Select Applications, Web Manager.

Select the Add symbol, browse and select the WebRootCA.pem file and select OK.

Search for WebRoot and confirm the file is showing in the Primary folder

Installing a Public Certificate

You should have 3 files.

Access the Security Settings of the IPO using Manager.

Select System, Certificates.

In Identity Certificate, select Set.

Select Paste from clipboard, select OK.

Select OK to the warning.

In the folder with the 3 files.

Open the certificate.crt with Notepad.

Copy and paste the certificate text into the Certificate .

Open the private.key with Notepad.

Copy and Paste the certificate text into the Private Key.

Select OK.

The Issued To will update to the new certificate name.

Select View to check and confirm the Issue By is correct (in our example ZeroSSL)

Select OK to close.

Select OK (at the bottom of the Certificates tab)

Select File, Save Security Settings

Browse to the settings file of the IPO (note, we are using Chrome in the example below, different browser will be slightly different in navigating to the certificate details)

Select the padlock symbol next to the URL.

Select Connection is secure.

Select Certificate is valid.

Select Details

You will see the certificate hierarchy.

In our example we have USERTrust and ZeroSSL.

These are not in the Trusted Store of the IPO, so we need to select each one of these and save the certificate, then import into the IPO trusted certificate store.

Select ZeroSSL certificate and select Export.

Save the file to a location on your PC.

Select USERTrust certificate and select Export.

Save the file to a location on your PC.

In IPO Security, System, Certificates, Trusted Certificate Store.

Select Add.

Select Import certificate from file, select OK.

Select OK to the warning box.

Select the ZeroSSL certificate and import.

Repeat the process to add the USERTrust certificate to the Trusted Certificate Store.

All certificates in the certificate hierarchy chain should now be showing in the Trusted Certificate Store Installed Certificates.

Select OK (at the bottom of the Certificates tab).

Select File, Save Security Settings.

Restart New IPOSE Instance

Access the new IPOSE Instance Platform View (port 7071)

Select System, Reboot.

Once the restart has completed, the new root and identity certificate will be active.

Testing

It is recommended to register a test JSeries phone and Workplace softphone to the existing IPOSE.

Once done you can (out of hours) re-map the FQDN from the existing IPOSE instance public IP address to the new IPOSE instance public IP address.

Power off the JSeries phone for 5 minutes then power on, if the JSeries phones was programmed with the FQDN, then it will now connect to the new IPOSE instance and register. Alternatively access the Administration of the Jseries and select Get Updates and Update (the phone will reboot and connect to the new IPOSE instance.

Logout and close the Workplace app to disconnect from the existing IPOSE. 

Open the Workplace app again. If it is programmed with the FQDN, then it will now connect to the new IPOSE instance and register.

Disable the SIP trunk on the existing IPOSE instance and enable on the new IPOSE instance.

Confirm the SIP trunks are registered.

Carry out testing.

4. Internal Calls
5. External Calls (inbound and outbound via SIP trunk)
6. Voicemail Access (including testing voicemail call flows
7. Hold Music (default short code to listen to music on hold is *341#)

If everything is testing ok, then cut over can be completed on the remaining JSeries phones and Workplace softphones.

NOTE: Be aware of any 3rd party devices or other devices on the existing system that might need to be tested before carrying out the cut-over. These could include.

3. ATA
4. Conference Phones
5. Cordless Phones