Issues Resolved in Version 8.0.518 (Direct Routing and Operator Connect services)

Phone numbers cannot be assigned in Live Platform; however Teams-side assignment works. Operation fails with PowerShell error “The user is not found”. Background Sync operations are not running and token-based user account authentication succeeds.

Token-based Onboarding and Replication for tenant fails even after admin consent. Live Platform reports “Last replication failed” with PowerShell validation error: “Cannot validate argument on parameter 'AccessTokens'.”

The SNMP connection with Live Platform is frequently disconnected and as a result the EMS Main and EMS Alarm Agent must be restarted for recovery purposes.

Token authentication email invitations are not sent. As a result, customers cannot secure the token connection with their M365 platform and therefore cannot complete the Onboarding process.

The default SNMPv2 community string is exposed on UDP port 161. The community string value should be changed to a strong value to mitigate risk.

Following an upgrade, users are not displayed in the Service portal despite existing in the database. This issue is due to customer tenant admin credentials errors causing the Sync process failure.

A Channel admin user views numbers for other customers that do not belong to their channel in the OC Number Management page.

Customer-created M365 user accounts do not replicate into the database and therefore are not displayed in the Service portal Users page.

Adding a  specific SIP Connection to customer tenant service fails.

After the Live Platform portal is disconnected, Live Platform displays the SBC without any status and site count with zero value even after performing “Reload from OVOC” in the Known SBCs page.

After onboarding an Operator Connect customer, the customer was manually migrated on the SBC from Operator Connect to Direct Routing. As a result, Live Platform does not display the numbers for the migrated Direct Routing service.

When onboarding a Direct Routing service, the App registration is successfully created, however, the "Pending Invitations" link in the Onboarding wizard did not display this state as a new secured connection.

The importing of a PBX users CSV file fails for tenant when using a custom SBC Onboarding script.

Request for a change in dial plan naming convention change from dynamic template variables (e.g., {{this.DialPlanName}} / {{DialPlanName}}) to static dial plan names.

When releasing Operator Connect numbers, the MS job report confirms the task, the number is not displayed in the Multitenant portal; however, subsequent uploads fail with duplicate errors.

A large quantity of Operator Connect numbers are unexpectedly being removed from the SBC dial plan.

Operator Connect number upload task fails with duplicate detection errors.

The SBC Show Prefixes refresh fails when a SIP Connection with a configured PSTN Gateway mapped to this SBC does not have any prefixes configured.

Synchronization between Live Platform and Microsoft Teams failed for a Voice App number when the number was explicitly deleted on the customer M365 Microsoft Teams platform.

The data displayed for User number assignment in the Queued Changes page is inaccurate due to synchronization issues with the Microsoft platform.

When LifeCycle Management configuration elements such as Voice Routing Policy are configured in LifeCycle Management templates, and then removed on the customer M365 platform, Live Platform keeps trying to apply the configuration. As a result, an excessive quantity of error messages are generated.

A number that was previously unassigned as a Direct Routing number cannot be uploaded to an Operator Connect service with a duplication error.

Following a UMP-365 upgrade, significant delays are experienced for updates to User’s voice settings due to network latency issues.

The Operator Connect number validation upon upload fails with duplication error despite the fact that the number is not found in the database.

This issue arose due to the following number synchronization operational and functional scenario:

For a customer with separate "Wireline" and "Wireless" services: When the "Wireline" service was removed, the "Wireless" service was also erroneously removed.

When onboarding with IP-PBX configuration, the registration failed to register with the PBX. In affected versions, the PBX user import could fail silently, resulting in no registration attempts appearing in PBX logs.

A PowerShell script has been provided to automatically deploy and configure a REST API Microsoft Entra ID App for integrating an AudioCodes SBC via REST API in an Operator Connect managed service context.

Multiple authentication tokens created for different admin users for the same tenant disrupted the replication process.

Following upgrade, authentication errors were experienced due to an incorrect parameter "TrustServerCertificate" in the install_tenant.ps1 script.

Importing a phone number into Number Inventory fails even though the number is not visible in the Service portal with duplication error.

When onboarding Microsoft Teams Direct Routing and creating DNS entry using the Configure M365 Default Routing option, Live Platform fails to automatically create the required TXT DNS record. As a result, the custom domain is added to the M365 tenant; however, remains unverified, which prevents the onboarding of new Direct Routing services for the tenant.

When onboarding a Live Express Direct Routing Hosted Essentials+ service, automatic DNS provisioning incorrectly reports that there are no eligible license available for DNS automation even though the tenant has valid Microsoft licenses (e.g., Microsoft 365 Business Basic and Microsoft Teams Phone Resource Account).