Avaya switches and servers: the foundation of the voice platform
When you make a phone call, the decisions behind it are made by the call-control server and by the media gateway that brings the calls into the corporate network. This page sets out the hardware and software forms Avaya commonly takes.
Separate the three layers first, then discuss models
Call-control layer: Aura Communication Manager handles extensions, trunks, routing and feature codes; IP Office is the integrated platform for smaller organisations. This layer takes the form of a server, whether physical hardware, a virtual machine or a cloud instance.
Access and media layer: media gateways such as the G450 and G430 connect legacy analogue phones, fax machines and outside trunks to the IP network. Branch sites commonly use them for local break-out and power-fail bypass.
Border layer: SBCE (Session Border Controller for Enterprise) handles SIP trunk access, NAT traversal, topology hiding and security policy. Any scenario that exposes SIP to the outside world generally needs one.
Once these three layers are clear, selection stops being led astray by the words switch and server: in Avaya terminology a voice switch usually means a call-control platform or a media gateway, not an Ethernet switch in the data centre.
Common models and their uses
Aura Communication Manager: the call-control core for mid-size and large enterprises, supporting multi-site distribution and redundant configurations.
Avaya IP Office: an integrated platform for smaller organisations. Server Edition can be virtualised, and it works out of the box with J-series phones.
G450 and G430 media gateways: branch and legacy phone access, analogue outside-line break-out, and local survivability so internal branch calls still work when the WAN is down.
SBCE: the security boundary for SIP trunks and remote-working access, where certificate and release maintenance are the operational focus.
Aura System Manager and Session Manager: unified management and routing across multiple CM systems and sites.
In-production models follow Avaya's official Devices and Phones catalogue; discontinued models are maintained as legacy equipment with repair and spare-part support, and are not recommended for new projects.
Four numbers drive selection
Extension count and concurrent calls: these determine the specification and licensing of the call-control platform. Do not look only at extensions; concurrency is where the bottleneck appears.
Trunk type and count: whether trunks are SIP, digital or analogue decides whether a gateway and an SBC are needed.
Site and redundancy requirements: whether branches need local survivability and whether headquarters needs dual-server failover.
Legacy endpoints: how many analogue phones, conferencing endpoints and fax machines must be retained directly determines the gateway port count.
Once these four numbers are established, the design largely settles itself.
Hardware selection frequently asked questions
Q: Is an Avaya switch a network switch? A: No. It usually refers to the voice platform or media gateway; whether network switching is included depends on the specific solution.
Q: Can the server be virtualised? A: Yes. Both Aura and IP Office support virtual deployment, provided the official resource and network requirements are met.
Q: Can an old G450 still be used? A: Yes, for legacy maintenance scenarios, though new projects should plan around in-production models.
Q: Do we have to buy SBCE? A: It is advisable when SIP is exposed to the internet or remote working access is required, as it addresses both security and interoperability.
Planning a platform upgrade?
Send us extension count, concurrency, sites and current models and we will produce a comparison list with a budget range.

