Howto13r3:Firmware Upgrade V13r2 V13r3: Difference between revisions

Latest revision as of 14:18, 10 November 2023

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

Shared AP/Several PBX'es

We generally recommend to upgrade the entire system (endpoints, PBXs, AP) in one shot.

If this is not possible for any reason, the recommended sequence is:

update the master PBX
update the slave PBX and all its endpoints location by location
update the App Platform to the latest build
update all Apps
perform the configuration changes described below

Note that during the update time frame, some App data such as Reporting and Recording may be incomplete.

We recommend to review all the configuration changes described below before you begin the update.

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. To make sure the more secure key exchange is used, we recommend adjusting the SRTP key exchange setting in the Devices App, Device Configuration for [Phone] and [Analog phone/fax]. An exception to this recommendation is if you are using old phone models (IP110A, IP240A) or gateway models (IP24, IP22) in your setup - as these 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.

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 - via PBX Manager .

In the Advanced UI, you have to enter the h323/sip name of the fax object in the field External Resource Destination.

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.

Contacts App | User drop-down menu for sharing address books

With 13r3, personal address books can be created and shared with users/groups. To have a search and drop-down menu in the sharing step, you have to activate the "Admin" option at the "ContactsApi" app object (tab "App") over the Advanced UI. Otherwise, no results will be shown, and you have to enter the correct h323 name of a user.

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 is required.

Update the announcements for your conference rooms, to include also the Web Access announcements.
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 Sga TBD: info zu inno Turn Fallback server
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. In 13r3 only Microsoft AD FS is supported as OpenID Server.

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 initial 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 during the first start after an update. 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

To allow monitoring of all queues by all switchboard users, configure a group (e.g. 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.

Apps new in 13r3

New Apps will not be installed automatically by the 13r2 to 13r3 upgrade. The installation description of new 13r3 apps is usually in the concept article. New apps are:

Changes visible to end customers

Listed here are changes that should be communicated by resellers to end users prior to a 13r3 upgrade, as the change will be visible/audible in the behaviour of the application/device.

Rework of Phone & Softphone UI

Several feature and UI improvements, see 'Features' in Reference13r3:Concept App SoftphoneApp and Reference13r3:Concept Multi-Video-Conference.

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). See 'Features' in Reference13r3:Concept myApps

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. See 'Features' in Reference13r3:Concept myApps

Fax App

The Mail Configuration section of the Fax App offers in 13r3 additional options:

Transmission confirmations
Transmission reports for outgoing fax jobs as PDF
Error notifications for outgoing fax jobs

Hardware Restrictions

For a list of devices with no/restricted support in 13r3, see the Firmware Upgrade article.

Known Problems

Boolean App

Following the update to 13r3, it is not possible to edit Boolean Apps using the myApps client (except when using the myApps client in a web browser). To resolve this issue, you will need to delete the approxy folder for all users who use the boolean app. You can locate this folder in the following directory: %USERPROFILE%\AppData\Local\innovaphone\myApps. Reload or restart myApps afterwards.

This behavior can also occur under Mac OS. Here the problem can be solved by uninstalling the app and then reinstalling it again.

Current major issues that will be fixed with upcoming 13r3SR1 release

More info on other 13r3 SR1 changes can be found in the Release Notes.

Regex Expression

We updated the regular expression syntax which is used for the AD replication. A '\' followed by a non-special character is no longer allowed.

Resources Considerations

New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.

Standard configurations which are according the specs will run on all supported hardware. However, unusual configurations may not. It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade. Please find details in Reference:Device Health Check.

RAM

As a rough rule of thumb, a 13r3 release will consume the same amount of RAM compared to a v13r2 firmware.

Flash Memory

As a rough rule of thumb, a v13r3 release will consume ~ 0.5 MB flash more compared to a v13r2 firmware.

New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v13r3. Here is the recommended procedure for upgrade on such devices:

save entire configuration
reset to factory defaults
load saved configuration (this will reorganize the flash memory usage)
upgrade to new firmware

When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a Firmwareupdate failed:no space / Update client end in a Error 0x00130001 Major FLASHMAN0 no space event) please open a support case with your current configuration file.

Conferences

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 concurrent video streams used in a single conference increased. Please review this bandwidth considerations. As a result, a device hosting a multivideo conference on its CONF or SCNF interface has a higher CPU load in 13r3 than in 13r2.

The graph shows the bandwidth needed for a device running the CONF interface to participate in a conference. The values shown are for when all participants are in gallery mode (which is the worst case scenario) and in fullscreen presentation mode (which is the best case scenario). In general, the actual bandwidth needed will fall somewhere between these two extremes.

To calculate the CPU requirements for the device, you can use the following formula: CPU% = Bandwidth (in Mbps) / x, where x is

0.42 for a xx10 device
0.18 for IP311 and IP411 devices
0.56 for a xx11 device
3.6 for a xx13 device

For example, if you are hosting a conference with 10 participants on a xx11 device in gallery mode, the upstream and downstream bandwidth would be 25 Mbps. Using the formula, you can calculate the CPU requirements as follows: CPU% = 25 Mbps / 0.56 = 44.64%. This means that the device should have at least 45% free CPU capacity to handle the conference.

From the client's perspective, the worst case values for upstream bandwidth (when presenting) would be 1 Mbps, and for downstream bandwidth (when in a gallery mode conference with 20 participants) would be 5 Mbps.

@@ Line 1: / Line 1: @@
-{{FIXME|reason=This article is still work in progress}}
 == Applies To ==
 This information applies to:
-* All V13r1 capable innovaphone devices
+* 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 ==
-== Migration Policies ==
+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]].
-=== Pre-v13 to v13++ ===
+=== Single AP/Single PBX===
-* [[Howto:V13_Firmware_Upgrade_V12r2_V13r1#Possible_Migration_scenarios|Follow this description]]
+* Create a new update job in devices and select 13r3 as major version
-=== v13r1 to v13r2 ===
-==== Single AP/Single PBX====
-* Use update service in devices and select 13r2 as major version
-====Common AP/Several PBX'es====
+===Shared AP/Several PBX'es===
-In case updating all systems at once is not desired, update jobs are splitted in the preferred order described below:
+We generally recommend to upgrade the entire system (endpoints, PBXs, AP) in ''one shot''.
-# Update the PBX'es first. Ensure the PBX'es are separated in different categories. Create dedicated update jobs for the PBX'es in those categories. Execute/Schedule PBX update jobs separated in time according to your update plan with endcustomer. After successful update of all PBX'es proceed with step 2.
+If this is not possible for any reason, the recommended sequence is:
-# Create & execute a dedicated update job for the common AP.
+# update the master PBX
-# Finally update the common AP's version under AP Manager/Update (not mandatory)
+# update the slave PBX and all its endpoints location by location
+# update the App Platform to the latest build
+# update all Apps
+# perform the configuration changes described below
+Note that during the update time frame, some App data such as Reporting and Recording may be incomplete.
+We recommend to review all the configuration changes described below before you begin the update.
-Note: If Recordings is used on the common AP, update jobs can't be split over a long time. Postpone the update until further notice, see also section [[#Recordings_App|Recordings App]] or choose to update all systems at once!
--->
 == 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.
-=== Fax App ===
+=== Default SRTP key exchange value in device configuration of Phones/Interfaces ===
-When upgrading from 13r2 to 13r3, the stored user email-settings (i.e. receive email notification, with or without attachment) need to be configured again.
+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. To make sure the more secure key exchange is used, we recommend adjusting the ''SRTP key exchange setting'' in the Devices App, ''Device Configuration'' for ''[Phone]'' and ''[Analog phone/fax]''. An exception to this recommendation is if you are using old phone models (IP110A, IP240A) or gateway models (IP24, IP22) in your setup - as these 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.
-=== Default SRTP key exchange value in device configuration of Phones/Interfaces ===
+===Group Fax===
-Previous to v13r3, the default SRTP key exchange value was SDES-DTLS - with v13r3 it changes to DTLS-SDES. As a result, innovaphone devices will now use DTLS instead - if both endpoints have this preference. We recommend adjusting the SRTP key exchange setting in your Devices App, ''device configuration'' for phones and analog endpoints.
+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 - via PBX Manager .
-<!--
+In the Advanced UI, you have to enter the h323/sip name of the fax object in the field '''External Resource Destination'''.
-In 13r2 we have introduced some new features which are automatically configured if you use the installer to setup your new 13r2 from scratch. If you upgrade an existing installation you have to setup the configuration manual.
+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.
-=== Tutorials App ===
+===Contacts App | User drop-down menu for sharing address books===
-A Tutorial App to provide additional help to the end user. The configuration must be done according to the [[Reference13r2:Concept_myApps#Tutorials_app | myApps concept article]].
+With 13r3, personal address books can be created and shared with users/groups. To have a search and drop-down menu in the sharing step, you have to activate the "Admin" option at the "ContactsApi" app object (tab "App") over the Advanced UI. Otherwise, no results will be shown, and you have to enter the correct h323 name of a user.
-=== Push ===
+===Improved Conference Rooms===
-To use the new [[Reference13r2:Apps/PbxManager/Push|Push Concept]], simply use the Push PBX-Manager-Plugin and edit the existing Push-Object (set URL to <code>https://push.innovaphone.com/push/ws</code>) and confirm the settings. If your PBX runs on a IPVA that has no innovaphone device certificate, [[Reference13r2:Concept_Push_Notifications_for_iOS_and_Android#Initial_configuration | you need to install an innovaphone signed device certificate]].
+* 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 is required.
+* Update the [[Reference13r3:PBX/Objects/Conference/Announcement_types#Sample_Announcement_Files | announcements]] for your conference rooms, to include also the ''Web Access announcements''.
+* 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 [[Reference13r3:IP4/General/STUN#TURN_Extern | IP4/General/STUN -> Turn Extern]] [[User:Sga|Sga]] TBD: info zu inno Turn Fallback server
+* 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.
-=== Switchboard App ===
+=== NTLM/OAuth===
-To use the new Switchboard App see [[Reference13r2:Concept_App_Service_Queues]] and add the Queues App accordingly.
+r3 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.
+In 13r3 only Microsoft AD FS is supported as OpenID Server.
-For exchanging the Operator Application to the Switchboard App, also check [[Reference13r2:Concept_App_Service_Queues#Additional_information]] regarding the licenses.
+===HTTP-Proxy===
+r3 introduces [[Reference13r3:Concept_myApps_platform_services#HTTP_proxy_support | 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.
-=== Events App===
+===Physical Location===
-In the Configuration panel of Events App ''(Burger Menu top right corner)'' a new option ''"Save logs on database"'' is available. This is by default in v13r2 not activated, logs are only displayed in the Logging App as LiveView.'''
+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 initial myApps registration PBX or configure the Physical location manually at the Softphone.
-You will need to activate the option after the update''', if you want to have the logs saved in the DB. <br />
+== Application Platform and its applications ==
-With the v13r1 logs were always by default stored in the Event App service DB, start from the v13r2 logs are by default available as LiveView mode via the Logging App. Its storage need to be activated by the administrator in the Event App settings.
+===App Platform image===
-=== Fax App ===
+It is not mandatory but recommended to [[Reference13r3:Concept_App_Platform#Update_of_the_App_Platform_itself | update the App Platform image]] to the latest version to receive a newer kernel and updated Linux packages.
-To use the new e-mail notification feature, you must configure your SMTP server in the Fax PBX Manager plugin.  Neither the SMTP data configured in the App manager nor in the PBX/Config/Authentication tab of the advanced UI are used for this.
-=== Favorite Users on Home Screen ===
+===Recordings App===
-Favorite users added to the Home screen in V13r2 will update their display Name automatically. In V13r1 this was not the case as the display name was only stored when added.
+Please follow the procedure described in the [[Reference13r3:Concept_App_Service_Recordings#Upgrade_from_V13r2_to_V13r3_Recordings_App | Recordings App concept article]].
-As a result of this, pre-V13r2 added favorite users cannot be removed from the homescreen by unticking the Home-icon in the Users-App, but must be deleted via a longpress on the favorite in the Home screen.
-== Application Platform and its applications ==
+===Reports App===
-===App Platform image===
+The Reports App will improve missed calls queries by adding a new database index during the first start after an update. 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.
-It is not mandatory but recommended to [http://wiki.innovaphone.com/index.php?title=Reference13r2:Concept_App_Platform#Update_of_the_App_Platform_itself update the App Platform image] to the latest version to receive a newer kernel and updated linux packages.
+=== App Service Queues, Switchboard App ===
+To allow monitoring of all queues by all switchboard users, configure a group (e.g. 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.
-===AP Manager===
-A new [[Reference13r2:Concept_App_Platform#App_Platform_disk_space_warning | used disk space threshold]] and an email address of the responsible person that shold be notified can be configured in the [[Reference13r2:Concept_App_Platform#Alarms_and_events | Alarms and events section of the AP manager]].
-The Email notification is sent by the AP Manager, therefore the [[Reference13r2:Concept_App_Platform#SMTP | SMTP section of the AP manager]] should be configured.
-===Recordings App===
+===Apps new in 13r3===
-The Recordings App is not yet included in the 13r2 release. If a 13r1 installation using the Recordings App must be upgraded to 13r2, please follow the upgrade procedure described in the [[Reference13r2:Concept App Service Recordings#Upgrade_from_V13r1_to_V13r2_Recordings_App | 13r2 Recordings App concept article]].
+New Apps will not be installed automatically by the 13r2 to 13r3 upgrade. The installation description of new 13r3 apps is usually in the concept article. New apps are:
+* [[Reference13r3:Concept_App_Service_Connector_for_kuando®#Configuration | Connector for kuando®]]
+* [[Reference13r3:Concept_App_Service_Connector_for_Microsoft_365 | innovaphone myApps Connector for Microsoft 365]]
 == Changes visible to end customers ==
-Here are listed changes that should be communicated by resellers to the users before a 13r2 upgrade, since the change in the behavior of the application/device will be visible/hearable.
+Listed here are changes that should be communicated by resellers to end users prior to a 13r3 upgrade, as the change will be visible/audible in the behaviour of the application/device.
-===App Sharing via Video===
+===Rework of Phone & Softphone UI===
+Several feature and UI improvements, see 'Features' in [[Reference13r3:Concept_App_SoftphoneApp#Features | Reference13r3:Concept App SoftphoneApp ]] and [[Reference13r3:Concept Multi-Video-Conference]].
-To significantly improve the quality of Application Sharing in myApps, we are now using a high-performance video codec to transmit shared content.
+===CallForwarding in Profile App===
-This will provide the user with a smooth experience in excellent quality, even for scrolling movements and animations.
+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.
-The Application Sharing protocol in 13r2 uses the VP8 video codec for encoding the shared application and the RTP protocol for transmitting the encoded data.
+===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). See 'Features' in [[Reference13r3:Concept_myApps#Features | Reference13r3:Concept myApps]]
-This new implementation has still some limitations, which will be addressed in future releases:
+===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.  See 'Features' in [[Reference13r3:Concept_myApps#Features | Reference13r3:Concept myApps]]
-* If application sharing is activated, it replaces the normal video stream. The speaker recognition is deactivated to keep the shared content visible. This means that during Application Sharing, no webcam video image is transmitted (neither of the speaker nor of any other participant) since both streams use the same RTP connection. If application sharing is stopped, webcam video is transmitted again.
+=== Fax App ===
-* No possibility to provide mouse or keyboard control to remote peer.
+The [[Reference13r3:Concept_App_Service_Fax#Mail_Configuration | Mail Configuration]] section of the Fax App offers in 13r3 additional options:
+* Transmission confirmations
-===Improved echo cancellation for telephones IP111, IP112, IP101, IP102 and myApps for Windows===
+* Transmission reports for outgoing fax jobs as PDF
-Echo cancellation technique has been improved for the speakerphone mode of the VoIP telephones IP111, IP112, IP101 IP102 and for the myApps for Windows native client.
+* Error notifications for outgoing fax jobs
 ==Hardware Restrictions==
-For a list of devices with no/restricted support in 13r2, see the [[Howto:Firmware_Upgrade#Version_13r2 | Firmware Upgrade article]].
+For a list of devices with no/restricted support in 13r3, see the [[Howto:Firmware_Upgrade#Version_13r3 | Firmware Upgrade article]].
 ==Known Problems==
-=== Resources Considerations ===
+===Boolean App===
+Following the update to 13r3, it is not possible to edit Boolean Apps using the myApps client (except when using the myApps client in a web browser). To resolve this issue, you will need to delete the approxy folder for all users who use the boolean app. You can locate this folder in the following directory: %USERPROFILE%\AppData\Local\innovaphone\myApps.
+Reload or restart myApps afterwards.
+This behavior can also occur under Mac OS. Here the problem can be solved by uninstalling the app and then reinstalling it again.
+===Current major issues that will be fixed with upcoming 13r3SR1 release===
+* [[Support:PBX_13r3_final_trap_with_Unknown_Registrations | PBX 13r3 Final trap with Unknown Registrations]]
+* [[Support:13r3final_App_Platform_-_SMTP_delivery_may_fail_due_to_IPv6_DNS_results | 13r3final App Platform - SMTP delivery may fail due to IPv6 DNS results]]
+* [[Support:13r3final PBX randomly does not execute CFU | 13r3final PBX randomly does not execute CFU]]
+More info on other 13r3 SR1 changes can be found in the [[Reference13r3:Release_Notes_Firmware#13r3_Service_Release_1 | Release Notes]].
+===Regex Expression===
+We updated the regular expression syntax which is used for the AD replication. A '\' followed by a non-special character is no longer allowed.
+== Resources Considerations ==
 New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.
 Standard configurations which are according [[Howto:How_to_implement_large_PBXs#Technical_data_and_recommended_number_of_users_supported | the specs ]] will run on all supported hardware.  However, unusual configurations may not.  It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade.  Please find details in [[Reference:Device Health Check]].
-==== RAM ====
+=== RAM ===
-As a rough rule of thumb, a v13r2 release will consume ~ 1 MB RAM more compared to a v13r1 firmware.
+As a rough rule of thumb, a 13r3 release will consume the same amount of RAM compared to a v13r2 firmware.
-==== Flash Memory ====
+=== Flash Memory ===
-As a rough rule of thumb, a v13r2 release will consume ~ 0.4 MB flash more compared to a v13r1 firmware.
+As a rough rule of thumb, a v13r3 release will consume ~ 0.5 MB flash more compared to a v13r2 firmware.
-New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v13r2.  Here is the recommended procedure for upgrade on such devices:
+New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v13r3.  Here is the recommended procedure for upgrade on such devices:
 * save entire configuration
@@ Line 110: / Line 137: @@
 * upgrade to new firmware
-When there is still not enough flash memory available to store the new firmware (Web GUI end in a ''Firmwareupdate failed:no space'' / Update client end in a ''Error 0x00130001 Major FLASHMAN0 no space'' event) please open a presales case with your current configuration file.
+When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a ''Firmwareupdate failed:no space'' / Update client end in a ''Error 0x00130001 Major FLASHMAN0 no space'' event) please open a support case with your current configuration file.
+=== Conferences ===
+Since Conferences now use [[Reference13r3:Concept_Multi-Video-Conference | multiple video streams]] to display each conference participant (in 13r1 & 13r2 only the video stream of the speaker was shown), the number of concurrent video streams used in a single conference increased. Please review this [[Reference13r3:Concept_Multi-Video-Conference#Bandwidth_Consideration | bandwidth considerations]]. As a result, a device hosting a multivideo conference on its CONF or SCNF interface has a higher CPU load in 13r3 than in 13r2.
+[[Image:13r3_conference_bandwidth.png|700px|Estimated Conference bandwidth requirements]]
+The graph shows the bandwidth needed for a device running the CONF interface to participate in a conference. The values shown are for when all participants are in gallery mode (which is the worst case scenario) and in fullscreen presentation mode (which is the best case scenario). In general, the actual bandwidth needed will fall somewhere between these two extremes.
-=== Mobility Licenses ===
+To calculate the CPU requirements for the device, you can use the following formula: <code>CPU% = Bandwidth (in Mbps) / x</code>, where x is
+* 0.42 for a xx10 device
+* 0.18 for IP311 and IP411 devices
+* 0.56 for a xx11 device
+* 3.6 for a xx13 device
-In 13r1 and previous firmware, PBX users having a mobility device configured could fork calls (and use Mobility features) without a mobility license. This bug has been corrected in 13r2.
+For example, if you are hosting a conference with 10 participants on a xx11 device in gallery mode, the upstream and downstream bandwidth would be 25 Mbps. Using the formula, you can calculate the CPU requirements as follows: CPU% = 25 Mbps / 0.56 = 44.64%. This means that the device should have at least 45% free CPU capacity to handle the conference.
+From the client's perspective, the worst case values for upstream bandwidth (when presenting) would be 1 Mbps, and for downstream bandwidth (when in a gallery mode conference with 20 participants) would be 5 Mbps.
 == Related Articles ==
 *[[Howto:Firmware_Upgrade]]
+* [[Howto:Firmware Upgrade V11r2 V12r1]]
+* [[Howto:Firmware Upgrade V12r1 V12r2]]
+* [[Howto:Firmware Upgrade V12r2 V13r1]]
+*[[Support:PBX_V13r3_Final_trap_with_Unkown_Registrations]]
 [[Category:Howto|{{PAGENAME}}]]
--->
-<!-- Keywords:  -->

Howto13r3:Firmware Upgrade V13r2 V13r3: Difference between revisions

Latest revision as of 14:18, 10 November 2023

Contents

Applies To

Migration Policy

Single AP/Single PBX

Shared AP/Several PBX'es

Configuration Changes

Default SRTP key exchange value in device configuration of Phones/Interfaces

Group Fax

Contacts App | User drop-down menu for sharing address books

Improved Conference Rooms

NTLM/OAuth

HTTP-Proxy

Physical Location

Application Platform and its applications

App Platform image

Recordings App

Reports App

App Service Queues, Switchboard App

Apps new in 13r3

Changes visible to end customers

Rework of Phone & Softphone UI

CallForwarding in Profile App

Focus App

Pin Apps

Fax App

Hardware Restrictions

Known Problems

Boolean App

Current major issues that will be fixed with upcoming 13r3SR1 release

Regex Expression

Resources Considerations

RAM

Flash Memory

Conferences

Related Articles

Navigation menu

Howto13r3:Firmware Upgrade V13r2 V13r3: Difference between revisions

Latest revision as of 14:18, 10 November 2023

Applies To

Migration Policy

Single AP/Single PBX

Shared AP/Several PBX'es

Configuration Changes

Default SRTP key exchange value in device configuration of Phones/Interfaces

Group Fax

Contacts App | User drop-down menu for sharing address books

Improved Conference Rooms

NTLM/OAuth

HTTP-Proxy

Physical Location

Application Platform and its applications

App Platform image

Recordings App

Reports App

App Service Queues, Switchboard App

Apps new in 13r3

Changes visible to end customers

Rework of Phone & Softphone UI

CallForwarding in Profile App

Focus App

Pin Apps

Fax App

Hardware Restrictions

Known Problems

Boolean App

Current major issues that will be fixed with upcoming 13r3SR1 release

Regex Expression

Resources Considerations

RAM

Flash Memory

Conferences

Related Articles

Navigation menu

Search