Nutanix AHV support for Audiocodes SBC Mediant VE/CE

Introduction

Until now, deploying a virtualized Audiocodes SBC meant a restricted choice of hypervisors : VMware, KVM / OpenStack or Hyper-V. Organizations whose infrastructure relies on Nutanix therefore had to maintain a separate platform for their telephony, or give up virtualizing it on their main foundation. Version 7.40A.605.092, released on 18 June 2026 in the Long-Term Support branch, adds Nutanix AHV support for Mediant VE and Mediant CE.

Check the new LTS branch 7.40A.600 article HERE.

What Nutanix support brings

Audiocodes now supports deploying its Mediant VE and CE SBCs as a virtual appliance on a Nutanix infrastructure, based on the AHV (Acropolis Hypervisor) hypervisor.

The announced items are the following :

• Certified deployment : The SBC is validated by Audiocodes on Nutanix AHV, not merely tolerated.
• Image-based installation : Deployment is done through a virtual machine image in OVA or ISO format.
• High availability : High availability and redundancy mechanisms are supported.
• Licensing unchanged : The existing licensing model and management tools remain compatible, with no specific reference to Nutanix.

The important point is the absence of any functional compromise. Security, interoperability and media services are identical to those of the other supported platforms. In the capacity tables of the release notes, Nutanix appears under the KVM / Nutanix entry, alongside VMware, KVM / OpenStack and Hyper-V, which confirms that it is a first-class platform and not a degraded mode.

The other new features in version 7.40A.605.092

Nutanix support is not the only new feature in this release :

• High-performance 8-port fiber connectivity for the Mediant 9080C
• New hardware component for the Mediant 800C with 4 PRI
• High-performance SR-IOV networking with the Mellanox driver
• New SDR field for ring duration
• Configurable maximum duration for FXS line testing
• Cloud storage of Debug Recording files and debug log files
• Improved handling of Reason Phrase in SIP replies
• Configurable HTTP response buffer size for remote web services

Prerequisites before upgrading

Upgrading requires checking three compatibilities on the tooling side.

One Voice Operations Center (OVOC)

This SBC version is compatible with and recommended for OVOC 8.4 (8.4.591, or 8.4.3068 and later). It can also be managed by OVOC 8.2 (8.2.3122 or later), with partial functional alignment. In all cases, OVOC must be upgraded before the devices.

Centralized license pool

Organizations running a centralized license pool through OVOC, whether Fixed, Floating or Flex, must update OVOC first. For WebRTC and SIPREC sessions in a Floating or Flex pool, OVOC version 8.0.3000 or later is required.

Stack Manager

Deploying Mediant CE requires Stack Manager version 4.1.0 or later.

Impacts for Teams Direct Routing

For a Microsoft Teams Direct Routing environment backed by Audiocodes SBCs, this version opens up a consolidation opportunity. A Nutanix infrastructure already in place can now host the SBCs, which removes the dedicated virtualization platform that many were maintaining solely for telephony.

Two reflexes remain necessary :

1. First, validate the expected capacities in the documentation tables, since vCPU and memory sizing differs from one hypervisor to another.
2. Then, treat this switch as a platform migration and not as a simple update, with a test SBC before production.

Conclusion

Nutanix AHV support fills a real gap for organizations whose virtualization foundation is neither VMware nor Hyper-V. The fact that this new feature arrives in the LTS branch, and not in a Latest Release version, is a good signal : it is intended for production environments. The main constraint is not technical but sequential, with the OVOC then devices upgrade order, at the risk of taking the SBCs out of the centralized license pool.

Sources

Audiocodes - Release notes

Did you enjoy this post ? If you have any questions, comments or suggestions, please feel free to send me a message from the contact form.

Don’t forget to follow us and share this post.