Known Limitations and Workarounds

The table below lists the Known Limitations and Workarounds for this release.

Known Limitations and Workarounds

Issue

Problem/Limitation

Component

Comments and Workaround

Mutual authentication using TLS 1.3 not supported

OVOC with Rocky Linux installation does not support Mutual authentication using TLS 1.3.

Infra

This functionality will be supported in a future release.

High Availability on OVOC Bare Metal platform

High Availability is not supported for OVOC servers on the Bare Metal platform.

Infra

-

Backup and Restore

When running a backup on the Bare-metal or the Virtual server-based platforms, it’s not possible to restore the backed-up data to Cloud-based server platforms.

Infra

-

Browser cache

Cache memory browser overload causes performance degradation.

In addition, after upgrade to the new OVOC Version its recommended to clear your browser cache.

Infra

See the following link for information on improving browser performance.

https://7labs.io/tips-tricks/clear-site-specific-cookies-cache.html

AWS/Azure Storage extends operations

OVOC background disk extends process sometimes fails during second extend operation.

Infra

This functionality will be supported in a future release.

Cloud Architecture

The Cloud architecture feature for binding SBC communication to a dedicated tunnel is only supported on the AWS, Azure, VMware and HyperV platforms.

■ AWS, Azure platforms with amaximum of 500 connected devices and 120 CAPS.
■ VMware, HyperV platforms with a maximum of 100 connected devices and 30 CAPS.

-

-

IPv6 Networking

The Cloud Architecture feature is not supported for an IPv6 connection.

Infra

-

Public Cloud Networking with AWS and Azure ethernet interfaces are not supported over IPv6.

Infra

-

OVOC Main Management interface only supports IPv4.

Infra

-

Database Password

When upgrading to Version 8.2 with PostgreSQL from Versions 8.0/8.0.1000/8.0.2000/8.0.3000 the default database password “pass_1234” is restored. This is done because the Oracle DB password may contain characters that do not comply with PostgreSQL.

Infra

Following upgrade, change PostgreSQL from default using OVOC Server Manager option Security menu option “PostgreSQL DB Password”.

Elastic search analytics

Elastic search analytics not supported in” vm low” spec due to additional memory requirements

infra

Use OVOC with higher spec

IPv6 MSBR Device Management

License actions (Fixed/Floating/Flex license) are not supported for IPv6 MSBR  devices.

Management

-

External Server Authentication

Multi-tenancy is not supported for the RADIUS server.

Management

-

The option “Use LDAP Credentials for Device Page Opening” is not supported for operators when the LDAP “Level” parameter is set to Admin (1)

Management

This functionality will be supported in a future release.

The option “Use RADIUS Credentials for Device Page Opening” is not supported for operators when the RADIUS “User Level” parameter is set to Administrator (100)

Management

This functionality will be supported in a future release.

Tenant operators with Tenant Monitor Links security level are not supported for RADIUS authentication.

Management

-

Certificates

If you have installed SSL certificates for Microsoft Active Directory, MS-SQL Server or for LDAP User authentication and you then run the Server Certificates Update procedure in the EMS Server Manager, these Microsoft certificates are overwritten.

Management

Before running the Server Certificates Update procedure, ensure that you have backed up the Microsoft Certificates to an external location.

After running the Server Certificates Update procedure, reload the Microsoft Certificates in the OVOC Web.

If you are configuring the connection to the MS‑SQL server with SSL using a certificate file, and then one of the following occurs:

■ Reload of a different certificate file for this SQL server.
■ Adding of an additional SQL server with a different certificate file.

The connection between the OVOC Server and the MS SQL server may fail.

Management

After reloading the new certificate file, restart the OVOC server using the EMS Server Manager.

This issue will be fixed in a future release.

MS Kerberos

MS Kerberos-based authentication on OVOC (including OVOC/Lync/Tenant users AD) is not supported.

MS Kerberos

MS Kerberos-based authentication on OVOC (including OVOC/Lync/Tenant users AD) is not supported.

Single Sign-on

Single Sign-on is not supported for devices with firmware versions prior to Version 7.0 and for CloudBond, SmartTAP and MP2XX (all versions).

Single Sign-on

Single Sign-on is not supported for devices with firmware versions prior to Version 7.0 and for CloudBond, SmartTAP and MP2XX (all versions).

Alarms Forwarding

The Overflow alarm is not cleared if raised during OVOC shutdown.

Management

This issue will be resolved in a future release.

OVOC supports a maximum of 10 alarm forwarding rules for SNMP trap rule destination for the entire system.

Management

Contact AudioCodes support to change this number per customer scenario.

Mass Operations

Mass operations on AudioCodes devices such as Restart or Firmware Upgrade can be done for a maximum of 500 devices (or maximum devices in a single table page).

Management

-

Floating License

The Floating License does not support multitenancy.

Management

-

Device Manager Pro-

When OVOC is operating at its maximum specifications for call storage, limit the Device Manager Pro allocated disk for firmware storage to 1.5GB.

Management

Customers who wish to use more (up to the limit defined) must configure the call storage settings (# of days) so that it will only use 95% of the max storage capacity.

Alarms Suppression

When managing more than 5,000 devices (gateway/SBC/MSBR), alarms suppression must be disabled.

Management

This functionality will be supported in a future release.

User Management Pack (UMP)

Opening the UMP device page from OVOC is not possible for UMP versions prior to Version 8.0.100.

Management

Upgrade to Version 8.0.100.

Voice AI Connect

The following features are not supported for this release: backup/restore and Single Sign-on

Management

These features will be supported in a future release

SBC Privacy Mode (PII Masking)

When SBC PII masking is enabled on SBC devices, PII masking is applied to the following data (according to the number of masked digits configured on the SB):

■ Usernames/hosts displayed in the Calls Table/Call Details/SIP ladder screens are masked.
■ Calls correlation for calls between SBC and Teams is based on URI and will not be operational.
■ User data is not expected tobe operational for all the users for which calls are passed via SBC that report masked data (Operators should ignore all the user statistics when **** appears in the username).
■ Links defined based on phone prefixes will not be operational.
■ Users/URI statistics will not be operational for masked users/hosts.
■ Users/URI statistics Reports will also contain masked users/hosts and therefore operators should also ignore all data when **** appears in the username .

Management

-

Operator Passwords

Operator passwords are validated to comply with UTF8 character sets.

Management

-

Upgrades from version 8.2.1000 and earlier.

Upgrade with migration (customer can choose to upgrade without migrating QoE data) can be very long (8 hours or longer), depending on the number of tenants, volume of QoE data, and data distribution.

QoE Infra

-

Upgrades from version 8.2.1000 and earlier.

Due to Postgres slowness with a large number of partitions, the upgrade is prevented, depending on the number of partitions (which is approximately calculated as the number of tenants):

■ Approximately 5 tenants for VM Low profile (depending on QoE data and distribution)
■ Approximately 20 tenants for VM High profile and Bare-Metal (depending on QoE data and distribution)
■ SP spec – no limitation

QoE Infra

Contact AudioCodes Support

QoE for AudioCodes HA Devices

When there is active call traffic on AudioCodes HA devices during HA switchover, the OVOC QoE application does not recognize this traffic and therefore does not display and calculate the QoE data for this traffic.

Applicable for all AudioCodes HA devices.

QoE

This issue will be resolved in a future release.

Calls Correlations
■ SBC-TEAMS failed calls are not correlated if  the TEAMS notification is received less than five minutes after the call has ended.
■ SBC-TEAMS calls are correlated if the reported time difference between the SBC and TEAMS call is more than two seconds.
■ SBC-TEAMS calls are not correlated if Azure Active Directory is not defined as the Users Sync source.

QoE

-

Active Directory for users sync

Test Connectivity is successful even though the password is incorrect.

QoE

This issue will be fixed in a future release.

Voice Quality Package

Forked calls are NOT supported by OVOC QoE.

QoE

This functionality will be supported in a future release.

Real time information, for example, in the Network/Statistics screens is only supported for the last three hours.

QoE

This functionality will be supported in a future release.

SBC calls more than the pre-configured maximum monitored call duration of three hours (e.g., the session of a participant in a Skype for Business conference call over an SBC) or an SBC call that is incompletely reported to the OVOC server are not displayed in the Calls List.

QoE

This limit can be extended at the request of AudioCodes support.

Adobe has stopped supporting Flash Player beginning December 31, 2020 (“EOL Date”). Version 7.6 and below versions will no longer support QoE reports.

QoE

New HTML5-based reports module is available in OVOC Version 8.0.

Device Manager Pro

 

 

 

Compatibility with Polycom devices: Username is not displayed for registered user and firmware upgrade requires template to be applied manually.

Polycom CCX

 

Irrelevant information is displayed in the Version Info when selecting menu action “More Info”.

IPPUC devices

 

On rare occasions pictures of devices are not always displayed in the Device Status screen.

All devices

 
■ When choosing “Collect logs” option, a confirmation message is displayed even though this feature is only supported for Native Teams devices from version 1.14.x and later.
■ NAT Management:
✔ IP Phones can only be managed behind NAT for Native Teams devices and for IPPUC devices (only from version 3.4.6 and later).
✔ Specific actions are not supported for specific device types.
✔ Alarms details display the public IP address of the devices’ network instead of its private IP address.
■ BT and WiFi statuses are not displayed for all devices.

All devices

-

The path to the latest firmware version points to a Skype folder, instead the relevant SIP folder. This occurs both when trying to update a single device or multiple devices.

For 445HD, 450HD, and C450HD phones in SIP /SIP Gateway mode

 

On the Latest Firmware Versions page, when clicking Get Latest Teams Versions to sync all devices, only the first two files are updated.

All devices

 

When a device is moved from one user to another and subsequently the device is deleted from its current user, it returns upon keep-alive as being assigned with the previous user.

All devices