Howto13r3:Firmware Upgrade V13r2 V13r3
|
FIXME: This article is still work in progress |
Applies To
This information applies to:
- All 13r3 capable innovaphone devices
- For a general overview of the upgrade process and a list of supported devices with 13r3, see Howto:Firmware Upgrade
Migration Policy
Here is how you upgrade a system to 13r3 from 13r2. For hints on upgrading a system to 13r2 see Howto:V13_Firmware_Upgrade_V13r1_V13r2.
Single AP/Single PBX
- Create a new update job in devices and select 13r3 as major version
If not all systems are to be updated at once, the update jobs are split in the preferred order described below:
- Update the PBXs first. Ensure the PBXs are separated in different categories so that you can create separate update jobs and run them according to your schedule. Create dedicated update jobs for the PBXs in those categories. Execute/Schedule PBX update jobs separated in time according to your update plan with the end customer. After successful update of all PBXs proceed with step 2.
ckl 18:02, 23 November 2022 (CET)
- unter welchen Bedingungen würden wir denn empfehlen, nicht alles auf einmal zu aktualisieren?
- Mir wird hier nicht klar, ob mit "all PBXs" nur die PBXen oder auch die Endgeräte gemeint sind?
- was ist mit den myApps clients? Wann soll man die aktualisieren. Da wäre ein Hinweis auf PBX/Config/myApps/Launcher Software Update gut.
- Create & execute a dedicated update job for the shared AP.
ckl 18:02, 23 November 2022 (CET) vielleicht sollte man weiter oben schon erwähnen, dass man nicht nur eigene Kategorien für die "PBX-Batches" machen soll, sondern noch eine für die AP?
- Finally, update the shared AP's version under Apps/App Platform/App Platform Manager/Update (not mandatory)
ckl 18:02, 23 November 2022 (CET) wieso ist das nicht mandatory? Was passiert, wenn man es lässt?
ckl 18:02, 23 November 2022 (CET) Was passiert in der Zwischenzeit, während manche PBXen schon neu sind aber die AP noch alt?
Configuration Changes
In 13r3 we have introduced some new features which are automatically configured if you use the installer to setup your new 13r3 from scratch. If you upgrade an existing installation, you have to configure the following settings manually.
Default SRTP key exchange value in device configuration of Phones/Interfaces
Before v13r3, the default value for SRTP key exchange was SDES-DTLS - with v13r3 it changes to the more secure DTLS-SDES. Therefore innovaphone devices now use DTLS instead - if the called endpoint has this preference. We recommend adjusting the SRTP key exchange setting in the Devices App, Device Configuration for phones and analog endpoints. An exception to this recommendation is if you are using old phone models (IP110A, IP240A) in your setup - as these phones may have CPU performance issues in the connection setup phase. In that case, use SDES-DTLS as value for the SRTP key exchange for all devices, not only for the old phone models.
ckl 18:06, 23 November 2022 (CET) IP150? others? IP2x?
Group Fax
The fax object has to be configured as external resource of a group fax object in 13r3. It is therefore mandatory to assign the fax object as an external resource to all group fax objects after the upgrade.
Also, with 13r3, group faxes can have their own international fax number and company name, so you should fill in these fields, or else the fax header will be empty.
Improved Conference Rooms
- The Web Access allowed checkbox in the conference app has to be set in order to access the Conference Web Access UI.
- To be able create HTTP links for external participants., the conferencing app and hence the conferencing app license is required.
ckl 18:19, 23 November 2022 (CET)
- oder braucht man noch eine weitere nur dafür, wenn man vorher schon eine Lizenz hatte (oder gabs die ihn 13r2 nicht?)?
ckl 18:19, 23 November 2022 (CET) Ich glaube, der Begriff Conference Web Access ist noch strittig
- Update the announcements for your conference rooms, to include also the Web Access announcements.
ckl 18:19, 23 November 2022 (CET) Wo macht man das?
- it is recommended to use a second Turn-Server listening on TCP port 443 as a fallback option for external conference participants, with local firewalls not allowing access to your standard Turn-server. Configure this second Turn-Server in IP4/General/STUN -> Turn Extern
ckl 18:19, 23 November 2022 (CET) Oh je, gibt es dazu einen Concept Artikel auf den man hier verlinken könnte?
- 13r3 adds a search-API for the Conference Rooms, allowing users to search for Conference room names from their Phone, Softphone or RCC App. Each conference object provides its own search API which is named like <Name-of-conference-object>.search and access to it can be granted using the App-Section of a PBX-object. The PBX-Manager Plugin for Conferences offers also an option to add the rights for all conference rooms and their search-APIs to the Config-User and/or Config-Admin template.
NTLM/OAuth
13r3 introduces OAuth2 Windows Authentication for myApps. If your are currently using NTLM/Netlogon for authentication, you might want to consider upgrading it OAuth2, since this authentication mechanisms is more secure. See Reference13r3:Concept OAuth2 Windows Authentication for details.
ckl 18:24, 23 November 2022 (CET) Geht das nur für Windows oder auch für andere OpenID provider (bzw. wollen wir das supporten)?
HTTP-Proxy
13r3 introduces HTTP-Proxy support for myApps. Now, myApps follows by default the OS-settings regarding HTTP-Proxy. This might affect existing setups when updating from 13r2 to 13r3. We recommend to check before a 13r3 update if an HTTP-Proxy is used and if so, test before the update for interop problems between myApps and the used HTTP-Proxy.
Physical Location
The Softphone App supports in 13r3 the determination of the Physical Location. Similar to an IP-Phone, this is determined automatically based on HTTP-Redirects of the myApps PBX-login process. If you use PBX-objects with activated "Local" option (often this is a Trunk Line object), the determined physical location might lead to a different behavior when calling these objects. If this leads to unwanted call flows, you can either adjust the inital myApps registration PBX or configure the Physical location manually at the Softphone.
Application Platform and its applications
App Platform image
It is not mandatory but recommended to update the App Platform image to the latest version to receive a newer kernel and updated Linux packages.
Recordings App
Please follow the procedure described in the Recordings App concept article.
Reports App
The Reports App will improve missed calls queries by adding a new database index. Depending on the size of the reporting database, this database adjustment can take some minutes and results also in high CPU-load and missed CDRs during that time.
App Service Queues, Switchboard App
Configure a group with the name queues in the PBX and assign it as Static to all Waiting Queues used by the Switchboard App and assign it also as Static and Active to all Switchboard Users.
Fax App
Changes visible to end customers
Here are listed changes that should be communicated by resellers to the end customers before a 13r3 upgrade, since the change in the behavior of the application/device will be visible/hearable.
Rework of Phone & Softphone UI
New UI
CallForwarding in Profile App
Added configuration option on call diversions: call forwardings depending on myApps online and Presence state. This can be switched on or off by the user in the Profile App.
Focus App
The "App focus" can be used to define a default app for the user. It is started and shown automatically when myApps is loaded. When closing other apps, the app is shown instead of the home screen. Users can activate (default) or deactivate the Focus function in their myApps Client settings (hamburger menu).
Pin Apps
Apps can be pinned to the main window. Pinned apps are always running and can't be closed. They are also started automatically when the myApps client is loaded. This setting is locally stored per-client. So you can pin different apps on your computer and your smartphone.
Hardware Restrictions
For a list of devices with no/restricted support in 13r3, see the Firmware Upgrade article.
Known Problems
Resources Considerations
RAM, Flash and CPU requirements stay like in 13r2, see 13r2 Resource Considerations.
However, since Conferences now use multiple video streams to display each conference participant (in 13r1 & 13r2 only the video stream of the speaker was shown), the number of video calls in one conference increased dramatically. Please review this bandwidth considerations. Also consider that a device used hosting a multi-video conference on its CONF or SCNF-interface will have in 13r3 an increased CPU-load compared to 13r2.