Howto13r1:Firmware Upgrade V12r2 V13r1: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
mNo edit summary
(48 intermediate revisions by 9 users not shown)
Line 4: Line 4:
** Update PBX
** Update PBX
** Installation App Platform (see below for more details)
** Installation App Platform (see below for more details)
*** On local SSD (if Gateway is SSD capable) [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] 
*** On local SSD (if Gateway is SSD capable) ''- is performed automatically by the install process''
*** On external Gateway with SSD [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD]   
*** On external Gateway with SSD [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD]   
*** On virtual machine (Hyper-V or VMWare) [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 Installation of Virtual App Platform] <br><br>
*** On virtual machine (Hyper-V or VMWare) [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 Installation of Virtual App Platform] <br><br>
Line 28: Line 28:
* TURN Server will be changed (Turn User & PW)  
* TURN Server will be changed (Turn User & PW)  
* LDAP Server will be changed to "Force TLS", there for all replications and other LDAP accesses need to be changed to TLS
* LDAP Server will be changed to "Force TLS", there for all replications and other LDAP accesses need to be changed to TLS
** Existing LDAP Server Accounts will be removed
* No of Regs w/o Pwd will be changed to "0"
* No of Regs w/o Pwd will be changed to "0"
* PBX Object number will be changed to **1 <br><br>
<br><br>
All changes can be changed back to another or original value after the migration process manually if necessary.<br>
All changes can be changed back to another or original value after the migration process manually if necessary.<br>
Make sure you store all these values upfront with a backup or manually.
Make sure you store all these values upfront with a backup or manually.
Always make a backup before you start a migration process.<br>
Always make a backup before you start a migration process.<br>
We advice to update all devices to the latest available Minor Release firmware version within your existing release before updating to V13.<br><br>
We advice to update all devices to the latest available Minor Release firmware version within your existing release before updating to V13.<br><br>
'''In this scenario example we show you the Migration steps: PBX with Linux Application Platform on a local SSD and we install an additional Gateway with SSD for the new AP Platform'''.<br><br>
A deeper look in what install does, you can find in the trainings book [[Course13:IT_Connect_-_11.0_The_individual_Device_User_Interface| The individual Device User Interface - What the Install does]].<br><br>
'''In this scenario example we will explain you the Migration steps: PBX with Linux Application Platform on a local SSD and we install an additional Gateway with SSD for the new AP Platform'''.<br><br>
Additional components who are necessary:
Additional components who are necessary:
* IPxx11 Gateway with new SSD
* IPxx11 Gateway with new SSD
Line 46: Line 48:
** DNS Names: you have to make sure before installation that your PC (your browser) and all innovaphone devices receive correct dns resolutions from your internal DNS for the used DNS-Names in the install process
** DNS Names: you have to make sure before installation that your PC (your browser) and all innovaphone devices receive correct dns resolutions from your internal DNS for the used DNS-Names in the install process
* Check your Reverse Lookup Configuration
* Check your Reverse Lookup Configuration
** Until V12r2 the LDAP configuration was deployed on the user object level and thus used by the phone and myPBX. In v13r1 the forward LDAP lookup is still user specific possible, the phone uses the user directories settings (as in v12) and the myApps client uses the ''Contacts App'' entries (which can be user specific by the LDAP object configuration). In v13 the Reverse-Ldap-Lookup is done centrally by the PBX by the [[Reference13r1:PBX/Config/General#Common|PBX configuration]] so called ''Reverse Lookup URL''. (by default Install will configure this to use your ''Contacts App''). The PBX - Reverse Lookup is not user specific, therefore you cannot use the user-specific LDAP-lookup feature of the [[Howto:XPhone_Connect_-_C4B_-_3rd_Party_Product|C4B LDAP server]]
** Until V12r2 the LDAP configuration was deployed on the user object level and thus used by the phone and myPBX. In v13r1 the forward LDAP lookup is still user specific possible, the phone uses the user directories settings (as in v12) and the myApps client uses the ''Contacts App'' entries (which can be user specific by the LDAP object configuration). In v13 the Reverse-Ldap-Lookup is done centrally by the PBX by the [[Reference13r1:PBX/Config/General#Common|PBX configuration]] so called ''Reverse Lookup URL''. (by default Install will configure this to use your ''Contacts App''). Please check the whole [[Reference13r1:Concept_Number_Resolution_and_LDAP|Concept]] before you start.


== App Platform ==
== App Platform ==
Line 94: Line 96:
To proceed we need to install the latest version of the V13r1 firmware on the existing PBX.
To proceed we need to install the latest version of the V13r1 firmware on the existing PBX.


<br>
Before upgrading the licence master (master pbx) make sure you have v13 licences. Delete the old licences and upload the new licences to the licence master. Otherwise you can run into cpu load issues and the install prozess can fail because of the traffic of registration attempts with TLS.
<hr><br>
If the firmware V13r1 is installed, you can access the gateway via its IP-address and you enter into the install process.
If the firmware V13r1 is installed, you can access the gateway via its IP-address and you enter into the install process.


Line 105: Line 108:
We choose for "Update existing PBX with installation of an external App Platform" as the selected scenario.
We choose for "Update existing PBX with installation of an external App Platform" as the selected scenario.


''Tip: Be sure that you don't have any Object with H323 Name: "AP" in your config. If so you will have problems in connecting the AP Platform.''


[[Image:Update existing PBX with installation of an external App Platform.png]]
[[Image:Update existing PBX with installation of an external App Platform.png]]




In case of any inconsistencies between the existing configuration file and new objects, error messages will be displayed.
Those need to be fixed before continuing the installation. Fixing is done by login to the admin-UI and change of the displayed object.
<hr><br>
In the step "innovaphone PBX Installation" you enter the necessary network settings of the gateway.
In the step "innovaphone PBX Installation" you enter the necessary network settings of the gateway.


Line 115: Line 121:


Be aware that if you choose for an update of the firmware, a restart will occur.
Be aware that if you choose for an update of the firmware, a restart will occur.


[[Image:innovaphone PBX installation2.png]]
[[Image:innovaphone PBX installation2.png]]
<hr><br>
''Tip: If the "Login to Devices" message appears, there was already an entry in the advanced user interface in (General/Devices Registration). Clear this entry and restart the Install process again.''<br>


In the step, "Connect to external App Platform" we connect the PBX with the pre-defines gateway with the App Platform.
In the step, "Connect to external App Platform" we connect the PBX with the pre-defines gateway with the App Platform.
Line 125: Line 136:


''Tip: The default password for the App-Platform is "pwd". If you don't enter  a password the default password will be used automatically.  If you changed the password on the App-Platform into a more secure password yourself before starting the Install to update the PBX, Be sure you use this same password to connect. Otherwise the connection will fail and the install can't proceed.''
''Tip: The default password for the App-Platform is "pwd". If you don't enter  a password the default password will be used automatically.  If you changed the password on the App-Platform into a more secure password yourself before starting the Install to update the PBX, Be sure you use this same password to connect. Otherwise the connection will fail and the install can't proceed.''
The installer will overwrite the AP Password, with the current Gateway Adminpassword during the installation.


<br>
<br>
Line 135: Line 148:




Tip: When the next step will follow with  "Connect to Devices" the there was already an entry in the advanced user interface in
''Tip: If no apps are installed and the console displays the following error message maybe there was already an entry in the advanced user interface in (General/Devices Registration). Clear this entry and restart the Install process again.<br>
 
<code>WebSocket connection to 'ws://ip.addr/domain.de/devices' failed: Error during WebSocket handshake: Unexpected response code: 404</code>''<br>
''General/Devices Registration''). Clear this entry and restart the Install process again.<br><br>
<hr><br>
 
In the following step "''innovaphone PBX Options''" you enter the configuration just as you have seen and learned during the iT Connect op iT Update training.
In the following step "innovaphone PBX Options" you enter the configuration just as you have seen and learned during the iT Connect op iT Update training.


Here the PBX name and Domain name (System name) should match with your configuration.
Here the PBX name and Domain name (System name) should match with your configuration.


''Tip: As user please add an additional (not existing) new user as myApps Admin. Name and mail cannot be in use already.''
''Tip: As user please add an additional (not existing) new user as myApps Admin. Name and mail cannot be in use already.''
<br>
<hr><br>
''Tip: At the moment only lower case PBX names can be used. In case the PBX you want to update is using upper case you have to change it to lower case (at the moment) and your phones will loose registration. Later on you have to change the PBX entries of all objects to lower case.''<br>
In the following step "''Emergency Administrator password, please save secure''" the passwords will NOT be created randomly as you have learned during the iT Connect Training. The existing passwords of the PBX system remain as they are.
In the following step "Emergency Administrator password, please save secure" the passwords will NOT be created randomly as you have learned during the iT Connect Training. The existing passwords of the PBX system remain as they are.
<hr><br>
<br>
In the following steps the configurations will be done as learned during your [[Special:Prefixindex/Course13:|iT Connect Training]].
 
<hr><br>
In the following steps the configurations will be done as learned during your iT Connect Training.
<br>
After finishing all the install steps, you can login into the system with the previously define myApps Admin in the myApps client.
After finishing all the install steps, you can login into the system with the previously define myApps Admin in the myApps client.


''Tip: If you cant login with the myApps Admin User, go to the Advanced User Interface ([https://ip.addr/admin.xml?xsl=admin.xsl https://ip.addr/admin.xml?xsl=admin.xsl]) and assign an existing user object the Template "Config Admin". You can then login with this user into myApps.''
''Tip: If you cant login with the myApps Admin User, go to the Advanced User Interface ([https://ip.addr/admin.xml?xsl=admin.xsl https://ip.addr/admin.xml?xsl=admin.xsl]) and assign an existing user object the Template "Config Admin". You can then login with this user into myApps.''
<br>
<hr><br>
As mentioned in the beginning , know you can change your saved and special settings back to its original state if this is necessary for your configuration.
As mentioned in the beginning , one now can change the stored special settings back to its original state if necessary for the configuration
<br>
<hr><br>
To give the existing users the possibility to use the innovaphone myApps, you should inherit the existing templates to the new template "Config User". If the user didn't have any template at all, then assign them  o the template "Config User".
To give the existing users the possibility to use the innovaphone myApps, you should inherit the existing templates to the new template "Config User". If the user didn't have any template at all, then assign them  o the template "Config User".


''Tip: The Users are only seen in Users App if they have the "Visible" flag in Visibility set. This is mostly done by Config Templates. So be aware that if you have another Config Template in use (that has not set the Visibility flag) even if you inheritate it from Config User it will not overwrite the older settings. So choose here the Visibility flag afterwards.''  
''Tip: The Users are only seen in Users App if they have the "Visible" flag in Visibility set. This is mostly done by Config Templates. So be aware that if you have another Config Template in use (that has not set the Visibility flag) even if you inheritate it from Config User it will not overwrite the older settings. So choose here the Visibility flag afterwards.''  


[[Image:Change template.png]]
[[Image:Change template.png]]


''Tip: Assign Administrative users to the new template "Config Admin".''
''Tip: Assign Administrative users to the new template "Config Admin".''
Line 183: Line 195:


== Reverse Proxy ==
== Reverse Proxy ==
Reverse Proxy migration must be done after upgrade the (first) pbx.


Via the advanced user interface install the latest V13r1 firmware.
Via the advanced user interface install the latest V13r1 firmware.
Line 220: Line 234:
The DNS name of the App Platform will be displayed in the next step. Select the DNS name and it will be added to the Reverse Proxy entries.
The DNS name of the App Platform will be displayed in the next step. Select the DNS name and it will be added to the Reverse Proxy entries.


Via the advanced user interface you have to change the hostnames for every PBX (Slaves and Standby).
Via the advanced user interface you have to change the URLs for every hostname pointing to an PBX (Slaves and Standby).
<br>
<br>


Line 232: Line 246:
<br>
<br>


== STUN / TURN / Slave / Standby / DECT ==
== Slave PBX ==


If you  want to have access to the gateway to enter the install process, you have to enter the admin credentials to login.
To proceed we need to install the latest version of the V13r1 firmware on the Slave PBX.
 
If the latest firmware V13r1 is installed, you can access the gateway via its IP-address and you enter into the install process. If there is no standard password you have to enter the admin credentials to login to the gateway.


In the next step select "Manual Configuration" and you will enter the Advanced User Interface.
In the next step select "Manual Configuration" and you will enter the Advanced User Interface.


Install the latest V13r1 firmware.
In the following step we need the Device URL. You can find it on the Master PBX under General/Devices Registration/Devices App URL. Copy the complete URL.
 
<!--
# Via the App Manager, in Settings/General/Devices app URL , we copy the complete URL <br> <br>
 
<br>
 
[[Image:App Manager.png]]
 
# Via the Advanced User Interface of the PBX
-->
 
[[Image:Device Registration2.png]]
 
 
Paste this URL via the Advanced User Interface of the Slave PBX under General/Devices Registration/Devices App URL.
 
Now you can find this Gateway in the Devices App within Devices. It will be displayed with its MAC-address and a wrench symbol.
 
Here you can now assign a meaningful name and the domain to the device.
 
[[Image:Devices.png]]
 
Via Category you should assign the Gateway to the appropriate category.
 
 
[[Image:Devices2.png]]
 
 
''Tip: Now the device configurations are assigned to all devices and the corresponding category(s)''
 
''These include at least:  Alarmserver Global, Media Global, NTP-settings''
 
For provisioning new devices to the Slave PBX you need a new provisioning category and a new phone device configuration.
In the training books you can find how to do this for [http://wiki.innovaphone.com/index.php?title=Course13:IT_Connect_-_06_Managing_Devices#Categories categories] and [http://wiki.innovaphone.com/index.php?title=Course13:IT_Connect_-_06_Managing_Devices#Phone phone configuration]. In the device configuration you need to specify the Slave PBX as Primary Gatekeeper.
 
Next Steps:
 
On a Slave you should change some configuration if it needed.
 
- Slave PBX registration to the Master must be done with authentication. We prefer to do this with H323/TLS as Registration protocol.
 
- Slave Replication must be done with use TLS. Check if the Objects will be synchronized.
 
- For the new Reporting App the Gateway/CDR0 must be adapted accordingly to receive the CDRs of the slave. You can copy the values from the Master.
 
- For reverse lookup you have to configure the Reverse Lookup URL and also the appropriate Prefixes under PBX/General.
<!-- how to get the password of contacts -->
 
At this point no "Edit profile" menu item appears in the myApps client of a Slave PBX user. You can fix this in the [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Service_Users#Users PBX Manager Plugin Users]. Under "Change configuration" select the Slave PBX and activate the displayed app under "Use as profile".''
 
On the Slave PBX go to Services, HTTP, Client, and add the necessary URL's for Events, Voicemail, files, backup-files.
 
You can copy and paste the URL's from the Master. Be aware that you have to set the new Passwords should also be changed on the Master, instances, PBX Objects and HTTP Client!
 
 
''Tip: If the redirect from the slave or standby PBX to the myApps weblauncher does not work, you have to enter the following via Command or the webbrowser:''
!config change HTTP0 /home PBX0/APPCLIENT/appclient.htm
!config write
!config activate
!reboot
 
== IP Phones ==
 
 
Proceed to install the latest version of the V13r1 firmware on the IP Phones.
 
To update the existing IP Phones to V13 there are two possibilities.
 
In a large environment with a lot of IP Phones you probably already have an update server.
 
 
If an update server available,
 
''- Change the Update Server script to update all phones with a Firmware upgrade to V13''
 
''- If the Phones are updates to V13, run the Updates script with a change to delete the Update URL and add the Devices App URL''
 
''- In Devices add the Phones to the appropriate Domain and category and give it a useful name to find a users phone via the search option in devices (unfortunately manual one by one)''
 
If no update server is available,
 
''- Manuel Firmware upgrade to V13''
 
''- Manuel edit the Devices App URL under General, Devices Registration, Devices App URL''
 
''- In Devices add the Phones to the appropriate Domain and category and give it a useful name to find a users phone via the search option in devices  (unfortunately manual one by one)''
 
== STUN / TURN / Standby / DECT ==
 
To proceed we need to install the latest version of the V13r1 firmware on the existing Gateway.
 
If the latest firmware V13r1 is installed, you can access the gateway via its IP-address and you enter into the install process. If there is no standard password you have to enter the admin credentials to login to the gateway.
 
In the next step select "Manual Configuration" and you will enter the Advanced User Interface.


In the following step we need the Device URL which can be found on two different ways.
In the following step we need the Device URL which can be found on two different ways.
Line 276: Line 386:


''Tip: For a Slave, Standby PBX or DECT you should select TLS as Replication protocol.''
''Tip: For a Slave, Standby PBX or DECT you should select TLS as Replication protocol.''
''Tip: If the redirect from the slave or standby PBX to the myApps weblauncher does not work, you have to enter the following via Command or the webbrowser:''
!config change HTTP0 /home PBX0/APPCLIENT/appclient.htm
!config write
!config activate
!reboot


== Configuration Changes ==
== Configuration Changes ==
Line 285: Line 401:
Downgrade from 13r1 to 12r2 (or older firmware) will result in objects with a too large [[Howto:Config_size_Limitations#Global | config line]] being dropped.
Downgrade from 13r1 to 12r2 (or older firmware) will result in objects with a too large [[Howto:Config_size_Limitations#Global | config line]] being dropped.


===PBX name in v13 can't include uppercase letter===


So you should change it in your configuration in V12 before the upgrade of PBX.


== Known issues ==
== Known issues ==
* For the known issues, please have a look into our [http://wiki.innovaphone.com/index.php?title=Support:DVL-Roadmap_Firmware_13r1 Support:DVL-Roadmap Firmware 13r1]
* For the known issues, please have a look into our [http://wiki.innovaphone.com/index.php?title=Support:DVL-Roadmap_Firmware_13r1 Support:DVL-Roadmap Firmware 13r1]
* [[Support:IP10x/IP11x_VLAN_configuration_disturbs_various_functions_in_V13r1_beta/final/sr1]]
** The Headline '''13r1 Release Notes''' will list the known issues.
* install did not finish if you have configured ETH0 as DHCP Server and ETH1 DHCP Client (connected to corporate network, internet access). You have to Swap the ETH interfaces before you start the install.
 
===PBX Replication===
The PBX LDAP Replication won‘t work if Master and Slave have different major Versions (V13/V12).  The reason is that the binding user is different in V13 and V12. The binding user in V12 is called ''_PBX_''. In V13 the binding user is called ''[domain]/_PBX_''. You should either use the same major Version or use the LDAP replicator at Services->LDAP->Replicator.
 
===Fax App===
The Fax App currently supports only dial plan having all objects in the root node. For details see [[Reference13r1:Concept_App_Fax#Known_issues | Concept App Fax: Known issues]].
 
===Install No-DNS mode in V13r1 sr7===
The install process in No-DNS mode stops when installing events.
This can be avoided by entering the DNS name in the hosts file of the PC you are installing with. The hosts file can only be edited with admin rights and is located in the folder:
<code> C:\Windows\System32\drivers\etc\hosts </code>
 
This will be fixed in V13r1 sr8.


== Related Articles ==
== Related Articles ==
Line 305: Line 433:
* [[Howto:Firmware Upgrade V11r2 V12r1]]
* [[Howto:Firmware Upgrade V11r2 V12r1]]
* [[Howto:Firmware Upgrade V12r1 V12r2]]
* [[Howto:Firmware Upgrade V12r1 V12r2]]
* [[Reference13r1:Concept_Number_Resolution_and_LDAP]]
[[Category:Howto|{{PAGENAME}}]]
[[Category:Howto|{{PAGENAME}}]]

Revision as of 08:29, 25 November 2019

Possible Migration scenarios

Changes that will be performed during the install/migration process:

  • CDR0 will be changed
  • DNS0 will be changed
  • LOG0 will be changed
  • IP0 /priority-tos will be changed
  • HTTP Client Authenticated URLs 1-n will be changed, depending on number of installed voicemails
  • HTTP, HTTPS Ports will be changed
  • STUN Server will be changed
  • TURN Server will be changed (Turn User & PW)
  • LDAP Server will be changed to "Force TLS", there for all replications and other LDAP accesses need to be changed to TLS
    • Existing LDAP Server Accounts will be removed
  • No of Regs w/o Pwd will be changed to "0"



All changes can be changed back to another or original value after the migration process manually if necessary.
Make sure you store all these values upfront with a backup or manually. Always make a backup before you start a migration process.
We advice to update all devices to the latest available Minor Release firmware version within your existing release before updating to V13.

A deeper look in what install does, you can find in the trainings book The individual Device User Interface - What the Install does.

In this scenario example we will explain you the Migration steps: PBX with Linux Application Platform on a local SSD and we install an additional Gateway with SSD for the new AP Platform.

Additional components who are necessary:

  • IPxx11 Gateway with new SSD
  • v13 Licenses

Preparation before you start

  • You have to disable Force HTTPS in the configuration before the update, because the installer is HTTP only
    • If you have forgotten it and cannot reach the installer you have to access the advanced UI directly via https://ip/admin.xml?xsl=admin.xsl to deactivate it. After that you can open the installer
  • You have to decide if you want to install with IP addresses or DNS Names.
    • IP Addresses: go ahead
    • DNS Names: you have to make sure before installation that your PC (your browser) and all innovaphone devices receive correct dns resolutions from your internal DNS for the used DNS-Names in the install process
  • Check your Reverse Lookup Configuration
    • Until V12r2 the LDAP configuration was deployed on the user object level and thus used by the phone and myPBX. In v13r1 the forward LDAP lookup is still user specific possible, the phone uses the user directories settings (as in v12) and the myApps client uses the Contacts App entries (which can be user specific by the LDAP object configuration). In v13 the Reverse-Ldap-Lookup is done centrally by the PBX by the PBX configuration so called Reverse Lookup URL. (by default Install will configure this to use your Contacts App). Please check the whole Concept before you start.

App Platform

At first install the gateway with the new Application Platform.

We assume it is in factory default. When a V13 firmware is already installed, you can access the gateway via its IP-address and you will get in the install GUI and can start the install process. If this is not the case, you can perform an update of the firmware to v13r1 via Maintenance, Update.

Tip: If an V13r1 is installed but you don't get the install gui immediately you can open it via http://ipaddress/install.htm

  • Install switch from HTTPS to HTTP, please be careful if you have deactivated HTTP, the redirection will fail !!

If not no secure passwords should be assigned automatically, you can use the default passwords by using the URL with a password switch http://ipaddress/install.htm?stdpwd=on. We recommend the use of secure passwords

If the install doesn't start in your desired language or you want another language during the install process as the OS-language, use an appropriate language switch, for example ?lang=nl for Dutch or ?lang=en for English


As first you will be asked for the username and password of the gateway.

As long as these are on the default values, you don't have to enter a value or just enter this default value.

Tip: On the right pane of the install you find the explanations for the parameters that you can fill out.


In the second step the install method will be asked.
Here we select "Only update and network settings" to prepare the gateway for the installation of the App Platform.

Only update and network settings.png

In the step "innovaphone PBX Installation" you enter the necessary network settings of the gateway and the IP address of the App Platform.

It is also possible to update the gateway to the latest possible firmware version.

Be aware that if you choose for an update of the firmware, a restart will occur.

Innovaphone PBX installation.png

In the next step the App Platform will be downloaded and installed and started.

Innovaphone App Platform.png

PBX

After the App Platform is installed and started, we will follow-up with the update of the PBX (Master, in Distributed Systems).

To proceed we need to install the latest version of the V13r1 firmware on the existing PBX.

Before upgrading the licence master (master pbx) make sure you have v13 licences. Delete the old licences and upload the new licences to the licence master. Otherwise you can run into cpu load issues and the install prozess can fail because of the traffic of registration attempts with TLS.



If the firmware V13r1 is installed, you can access the gateway via its IP-address and you enter into the install process.

As first you will be asked for the username and password of the gateway.

Here you enter the credential of the existing admin user (most of the time it is admin) of the gateway.

The install will recognize that it is an existing PBX configuration and provides you with the appropriate Update scenarios.

We choose for "Update existing PBX with installation of an external App Platform" as the selected scenario.


Update existing PBX with installation of an external App Platform.png


In case of any inconsistencies between the existing configuration file and new objects, error messages will be displayed.

Those need to be fixed before continuing the installation. Fixing is done by login to the admin-UI and change of the displayed object.



In the step "innovaphone PBX Installation" you enter the necessary network settings of the gateway.

It is also possible to update the gateway to the latest possible firmware version.

Be aware that if you choose for an update of the firmware, a restart will occur.


Innovaphone PBX installation2.png




Tip: If the "Login to Devices" message appears, there was already an entry in the advanced user interface in (General/Devices Registration). Clear this entry and restart the Install process again.

In the step, "Connect to external App Platform" we connect the PBX with the pre-defines gateway with the App Platform.

To proceed we enter the IP-address off the App-Platform and its password.

After pressing connect and a successful connection it will show connected.

Tip: The default password for the App-Platform is "pwd". If you don't enter a password the default password will be used automatically. If you changed the password on the App-Platform into a more secure password yourself before starting the Install to update the PBX, Be sure you use this same password to connect. Otherwise the connection will fail and the install can't proceed.

The installer will overwrite the AP Password, with the current Gateway Adminpassword during the installation.


Tip: With the search option you can searh for available App-platform in your network that are installed on a gateway. It is required that this gateway was in default factory setting.

A search is not possible for an App-platforms that runs on a virtual machine. This can only be accessed via its IP-address.


Connect to external App Platform.png


Tip: If no apps are installed and the console displays the following error message maybe there was already an entry in the advanced user interface in (General/Devices Registration). Clear this entry and restart the Install process again.
WebSocket connection to 'ws://ip.addr/domain.de/devices' failed: Error during WebSocket handshake: Unexpected response code: 404



In the following step "innovaphone PBX Options" you enter the configuration just as you have seen and learned during the iT Connect op iT Update training.

Here the PBX name and Domain name (System name) should match with your configuration.

Tip: As user please add an additional (not existing) new user as myApps Admin. Name and mail cannot be in use already.



In the following step "Emergency Administrator password, please save secure" the passwords will NOT be created randomly as you have learned during the iT Connect Training. The existing passwords of the PBX system remain as they are.



In the following steps the configurations will be done as learned during your iT Connect Training.



After finishing all the install steps, you can login into the system with the previously define myApps Admin in the myApps client.

Tip: If you cant login with the myApps Admin User, go to the Advanced User Interface (https://ip.addr/admin.xml?xsl=admin.xsl) and assign an existing user object the Template "Config Admin". You can then login with this user into myApps.



As mentioned in the beginning , one now can change the stored special settings back to its original state if necessary for the configuration



To give the existing users the possibility to use the innovaphone myApps, you should inherit the existing templates to the new template "Config User". If the user didn't have any template at all, then assign them o the template "Config User".

Tip: The Users are only seen in Users App if they have the "Visible" flag in Visibility set. This is mostly done by Config Templates. So be aware that if you have another Config Template in use (that has not set the Visibility flag) even if you inheritate it from Config User it will not overwrite the older settings. So choose here the Visibility flag afterwards.


Change template.png


Tip: Assign Administrative users to the new template "Config Admin".

Tip: In case you are using Apps that need a License the selectable box under License only appear after uploading the necessary license. In test mode everything works. So in case you are using test mode it is better to first upload your licenses, select the license boxes and than deactivate your test mode!

Provisioning

If you want to use Provisioning and you are using Update Server/PHP Update Server 2 you have to consider that your phone needs to reach config.innovaphone.com via Update URL.
That means that if you already provide an Update URL via DHCP that the Provisioning process will not be possible. Therefore delete the Update URL in your DHCP Server.
In case you are using Update Server/PHP Update Server 2 for Certificates etc. your phone needs to reach your old Update Server after provisioning again. (further details will follow)

Please Check: Reference13r1:Services/Update

Assign Hardware of a User to a phone or softwarephone App

This can be done by the administrator in UsersAdmin App.
Alternative the User can do this via his Profile. At the instruction from myApps the user can be shown on which point he can assign the app.

Profile PhoneApp.png

Reverse Proxy

Reverse Proxy migration must be done after upgrade the (first) pbx.

Via the advanced user interface install the latest V13r1 firmware.

In the next step we need the Devices App URL. Via the advanced user interface, in General/Devices Registration/Devices App URL.

Copy this URL.


Device Registration2.png

Paste this URL in the advanced user interface of the Reverse Proxy in the field General/Devices Registration/Devices App URL.

From now on this device can be found in the Devices App in Devices.

The MAC address and a wrench symbol will be displayed.

Here you can now assign a meaningful name and the domain to the device.


Devices.png

Via Categories you should assign this gateway also to the appropriate Category.

Devices2.png

Tip: Now the device configurations are assigned to all devices and the corresponding category(s)

These include at least:  Alarmserver Global, Media Global, NTP-settings

Via the PBX Manager App and the Reverse Proxy plugin you can now configure the Reverse Proxy.

You should add here a new Host entry for the App Platform in the Reverse Proxy via the option "Add Host".

The DNS name of the App Platform will be displayed in the next step. Select the DNS name and it will be added to the Reverse Proxy entries.

Via the advanced user interface you have to change the URLs for every hostname pointing to an PBX (Slaves and Standby).

In the first http forward field you need to enter the following string /PBX0/APPCLIENT/appclient.htm and forward it to the appropriate IP-address with the port numbers 80 and 443 and tag the checkbox Default.

At least the following entries should be available as shown in the picture below.

Reverse Proxy Entries.png

Slave PBX

To proceed we need to install the latest version of the V13r1 firmware on the Slave PBX.

If the latest firmware V13r1 is installed, you can access the gateway via its IP-address and you enter into the install process. If there is no standard password you have to enter the admin credentials to login to the gateway.

In the next step select "Manual Configuration" and you will enter the Advanced User Interface.

In the following step we need the Device URL. You can find it on the Master PBX under General/Devices Registration/Devices App URL. Copy the complete URL.


Device Registration2.png


Paste this URL via the Advanced User Interface of the Slave PBX under General/Devices Registration/Devices App URL.

Now you can find this Gateway in the Devices App within Devices. It will be displayed with its MAC-address and a wrench symbol.

Here you can now assign a meaningful name and the domain to the device.

Devices.png

Via Category you should assign the Gateway to the appropriate category.


Devices2.png


Tip: Now the device configurations are assigned to all devices and the corresponding category(s)

These include at least: Alarmserver Global, Media Global, NTP-settings

For provisioning new devices to the Slave PBX you need a new provisioning category and a new phone device configuration. In the training books you can find how to do this for categories and phone configuration. In the device configuration you need to specify the Slave PBX as Primary Gatekeeper.

Next Steps:

On a Slave you should change some configuration if it needed.

- Slave PBX registration to the Master must be done with authentication. We prefer to do this with H323/TLS as Registration protocol.

- Slave Replication must be done with use TLS. Check if the Objects will be synchronized.

- For the new Reporting App the Gateway/CDR0 must be adapted accordingly to receive the CDRs of the slave. You can copy the values from the Master.

- For reverse lookup you have to configure the Reverse Lookup URL and also the appropriate Prefixes under PBX/General.

At this point no "Edit profile" menu item appears in the myApps client of a Slave PBX user. You can fix this in the PBX Manager Plugin Users. Under "Change configuration" select the Slave PBX and activate the displayed app under "Use as profile".

On the Slave PBX go to Services, HTTP, Client, and add the necessary URL's for Events, Voicemail, files, backup-files.

You can copy and paste the URL's from the Master. Be aware that you have to set the new Passwords should also be changed on the Master, instances, PBX Objects and HTTP Client!


Tip: If the redirect from the slave or standby PBX to the myApps weblauncher does not work, you have to enter the following via Command or the webbrowser:

!config change HTTP0 /home PBX0/APPCLIENT/appclient.htm
!config write
!config activate
!reboot

IP Phones

Proceed to install the latest version of the V13r1 firmware on the IP Phones.

To update the existing IP Phones to V13 there are two possibilities.

In a large environment with a lot of IP Phones you probably already have an update server.


If an update server available,

- Change the Update Server script to update all phones with a Firmware upgrade to V13

- If the Phones are updates to V13, run the Updates script with a change to delete the Update URL and add the Devices App URL

- In Devices add the Phones to the appropriate Domain and category and give it a useful name to find a users phone via the search option in devices (unfortunately manual one by one)

If no update server is available,

- Manuel Firmware upgrade to V13

- Manuel edit the Devices App URL under General, Devices Registration, Devices App URL

- In Devices add the Phones to the appropriate Domain and category and give it a useful name to find a users phone via the search option in devices (unfortunately manual one by one)

STUN / TURN / Standby / DECT

To proceed we need to install the latest version of the V13r1 firmware on the existing Gateway.

If the latest firmware V13r1 is installed, you can access the gateway via its IP-address and you enter into the install process. If there is no standard password you have to enter the admin credentials to login to the gateway.

In the next step select "Manual Configuration" and you will enter the Advanced User Interface.

In the following step we need the Device URL which can be found on two different ways.


  1. Via the Advanced User Interface of the PBX

In General/Devices Registration/Devices App URL copy the complete URL.

Device Registration2.png


Paste this URL via the Advanced User Interface of the Reverse Proxy Gateway in General/Devices Registration/Devices App URL .

Now you can find this Gateway in the Devices App within Devices. It will be displayed with its MAC-address and a wrench symbol.

Here you can now assign a meaningful name and the domain to the device.

Devices.png

Via Category you should assign the Gateway to the appropriate category.


Devices2.png


Tip: Now the device configurations are assigned to all devices and the corresponding category(s)

These include at least: Alarmserver Global, Media Global, NTP-settings

Tip: For a Slave, Standby PBX or DECT you should select TLS as Replication protocol.

Tip: If the redirect from the slave or standby PBX to the myApps weblauncher does not work, you have to enter the following via Command or the webbrowser:

!config change HTTP0 /home PBX0/APPCLIENT/appclient.htm
!config write
!config activate
!reboot

Configuration Changes

SNMP disabled by default

Up and including v12r2, SNMP was by default activated on a innovaphone device. In v13 it is by default deactivated, it can be activated by a new Enable Checkmark. As a result, if you upgrade to v13 firmware SNMP is deactivated and needs to be enabled if SNMP is needed in the customer setup.

Config line size was increased to 32KB

Downgrade from 13r1 to 12r2 (or older firmware) will result in objects with a too large config line being dropped.


Known issues

  • For the known issues, please have a look into our Support:DVL-Roadmap Firmware 13r1
    • The Headline 13r1 Release Notes will list the known issues.
  • install did not finish if you have configured ETH0 as DHCP Server and ETH1 DHCP Client (connected to corporate network, internet access). You have to Swap the ETH interfaces before you start the install.

PBX Replication

The PBX LDAP Replication won‘t work if Master and Slave have different major Versions (V13/V12). The reason is that the binding user is different in V13 and V12. The binding user in V12 is called _PBX_. In V13 the binding user is called [domain]/_PBX_. You should either use the same major Version or use the LDAP replicator at Services->LDAP->Replicator.

Fax App

The Fax App currently supports only dial plan having all objects in the root node. For details see Concept App Fax: Known issues.

Install No-DNS mode in V13r1 sr7

The install process in No-DNS mode stops when installing events. This can be avoided by entering the DNS name in the hosts file of the PC you are installing with. The hosts file can only be edited with admin rights and is located in the folder: C:\Windows\System32\drivers\etc\hosts

This will be fixed in V13r1 sr8.

Related Articles