Kas One LogoKas One
Back to Guides2 min read

Azure AudioCodes SBC deployment parameters and requirements.

October 27, 2025
AudiocodesAzureTelephony

Azure SBC

- To be deployed in Azure.

- Provide BOM - (VM Type for Azure cost, HA Cluster, 20 SIP channels,  10 T-Coding, support)

-Stack manager - Standard_B1ms ( for HA deployment)

-SBCs in HA Pair ->

Option1: 2 x Standard_DS3_v2 (will be deployed through Stack Manager)

Option2: 2x Standard_DS1_v2 could also work and is cheaper. It has only 2 NW IF. Need to assign them multiple roles to each – 1 IF is Admin + HA ; 2 IF is Control + Media for calls.

-Standard SKU Public Network addresses for the VMs(2 – one for each IF)

-Load Balancer with NAT rules – will be deployed automatically. Adds resource utilization and NAT rules

-Can be deployed in multiple availability zones if the Azure region allows.

 

-Azure requirements for SBC deployment in Azure (HA Cluster)

Stack manager – Standard_B1ms, Standard SKU Public network address, Ports needed:22,80,443

Reference Stack Manager Guide - https://www.audiocodes.com/media/15907/stack-manager-for-mediant-ve-ce-sbc-users-manual-ver-74.pdf

The stack manager will be used to enter many parameters of the SBCs Pair.

It can determine the SBC VM size. However Standard_DS3_v2 is the one we are aiming. (DS1_v2 if 2 NW interfaces are enough)

The SBC pair will have:

-HA subnet for HA (internal communication)

-Main subnet for management. With Standard_DS1_v2: HA Subnet and Main subnet merge.

-additional subnets for Signaling/Media (Sip Trunk to Teams and Telephony Provider)

Reference SBC 7.4 Guide - https://www.audiocodes.com/media/15567/mediant-software-sbc-users-manual-ver-74.pdf

Reference SBC 7.4 Deployment Guide https://www.audiocodes.com/media/15886/mediant-virtual-edition-sbc-for-microsoft-azure-installation-manual-ver-74.pdf

Public IP addresses for Main Subnet and Additional Subnet/s.

 

NSG Rules:

-Allow SSH/HTTP/HTTPS rules for management subnet

-Allow SIP-UDP, SIP-TCP, Media for the additional subnets for Signaling/Media.

-The rest of the rules should be there already to allow the communication inside the VNetwork and the outbound communication.

We can tweak the allowed source/destination addresses to match the provider addresses later.

Management Ports 22/tcp,80/tcp,443/tcp

Signaling Ports 5060-5090/udp, 5060-5090/tcp

Media ports 6000-65535/udp

All of ports are suggestions. They can be changed on your discretion.

VM Sizes can be changed according to vendor recommendations or organizational needs.