How to Update Network Settings on a Mitel PBX

If you administer a Mitel phone system, the most common reason to open the admin tools is a network change: the PBX is moving to a new subnet, the DNS server changed, or a gateway was replaced. This guide covers how to update network settings on a Mitel PBX, and as a bonus it walks through how to log in to the system and answers the questions admins ask most often.

Every step below was checked against Mitel's own MiVoice Business installation and administration documentation. The guide is written for MiVoice Business, the platform that grew out of the 3300 ICP and the most widely deployed Mitel PBX, running on 3300 ICP controllers, the MXe Server, the EX Controller, the SMB Controller, and as a virtual machine. If you run MiVoice Connect, the former ShoreTel line, or MiVoice Office 250, the menu names differ, but the network-change discipline is the same.

Quick answer: On a MiVoice Business PBX, the core network settings (IP address, subnet mask, gateway, and DNS) are changed in Server Manager or the Server Console, not in the System Administration Tool. Log in to Server Manager at the controller IP address, open the networking configuration, update the values, save, and reboot. The voice-side network forms live separately in the System Administration Tool.

TL;DR

• Core IP settings (address, mask, gateway, DNS, DHCP, domain) are changed in Server Manager or the Server Console, which trips up admins coming from other platforms.
• The default Server Manager login is admin / default1, and the system forces an eight-character-minimum password change on first login.
• Voice-side networking (phone DHCP, IP routing, network elements) is separate and lives in the System Administration Tool.
• Changing the system IP is disruptive: phones lose registration until they re-resolve, and reusing an old IP can require clearing the router ARP cache.
• A reboot is almost always required, and a controller can take up to roughly 15 minutes to come back.

The rest of this guide expands each of those points with exact interfaces and steps, then closes with the operational reality of running the box by hand.

Why Mitel Admins Are Reassessing On-Prem

A little context frames why this knowledge matters more than it used to. Mitel filed for Chapter 11 bankruptcy protection on March 10, 2025, in the U.S. Bankruptcy Court for the Southern District of Texas, using a prepackaged plan that ended Searchlight Capital's ownership and handed control to the company's lenders. Through the financial restructuring that Mitel completed on June 20, 2025, the company reduced its debt by roughly 1.15 billion dollars and cut annual cash interest by about 135 million dollars, emerging repositioned around a hybrid-communications thesis.

That corporate pivot mirrors where the buying market has gone. According to Metrigy's UCaaS market forecast, the global UCaaS market reached 21.7 billion dollars in 2024, up 6.5 percent year over year, and is projected to grow to 26.5 billion dollars by 2029. Metrigy also reports cloud telephony seats worldwide grew to 114.0 million in the first half of 2025. The adjacent contact center as a service market is climbing faster still, projected to rise from 5.82 billion dollars in 2024 to 17.12 billion dollars by 2030.

The most relevant figure for anyone still running an on-premises controller is that, by Metrigy's count, a little under half of all telephony seats worldwide still sit on customer-owned platforms, which the firm frames as the remaining migration runway. Your MiVoice Business keeps running regardless. The point is that the manual work below is increasingly work that cloud platforms have eliminated. With that established, here are the steps.

Log In to a Mitel MiVoice Business PBX

Logging in to a Mitel MiVoice Business PBX means choosing the right interface for the job, because the platform exposes three of them and they do different things. Most admins use the System Administration Tool day to day, but network changes happen in Server Manager or the Server Console.

Log in to the System Administration Tool

1. From a PC on the same network, open a supported browser and go to https://<system-IP>.
2. Accept the self-signed certificate warning. MiVoice Business ships with its own certificate, so a browser prompt on first connection is expected.
3. Log in with your administrator account. The Root Administrator profile has unrestricted read and write access to all forms. A MiVoice Business system supports up to five System Administration Tool users at once.

Log in to Server Manager

1. Browse to the server IP and open Server Manager.
2. On a new system, log in with the default admin / default1 credentials.
3. You are prompted to change the password, which must be at least eight characters. Changing it here also updates the Web GUI password and the System Administration Tool admin (mimx) account, so set it deliberately and record it.

For the Server Console, connect a local console or open an SSH session to the system IP. You can log in as root, or log in and then run su admin to switch to the admin user. Leaving any of these on factory credentials is the most common security finding on Mitel estates, so close that gap first.

Updating Network Settings: The Two-Layer Model

Updating network settings on MiVoice Business happens at two distinct layers, and knowing which layer owns which setting is the difference between a clean cutover and an afternoon of broken phones. This is the single most common point of confusion for admins arriving from other platforms.

• Layer 1, server networking. The controller's own IP address, subnet mask, default gateway, DNS servers, DHCP, and domain name live in Server Manager (web) or the Server Console (direct or SSH). This is what most people mean by network settings.
• Layer 2, voice networking. DHCP options for IP phones, IP routing for voice, and network elements live in the System Administration Tool. These shape how phones and trunks find the system, not the system's own IP identity.

If you go looking for the controller's IP address inside the System Administration Tool, you will not find it there. It is a Server Manager and Server Console setting. Hold that distinction and the rest of this guide falls into place.

Method 1: Update Network Settings in Server Manager

Server Manager is the recommended way to update the network settings on a running MiVoice Business system, because it provides a guided web interface over the underlying Mitel Standard Linux configuration.

Steps in Server Manager

1. Browse to the server IP and log in to Server Manager with your administrator credentials.
2. Open the networking configuration section, where the server Ethernet and IP settings are listed.
3. Update the values you need: IPv4 address, subnet mask, default gateway, and DNS servers. Update the domain name and DHCP settings here too if they apply.
4. Save the change. Server Manager validates the entries before applying them.
5. Reboot if prompted. Many IP-level changes require a restart to take effect, and the controller can take up to roughly 15 minutes to fully start.

DNS is a server-level setting, so it is configured in Server Manager or the Server Console alongside the IP address and gateway, not in the System Administration Tool. Update the DNS server entries in the same networking section, save, and reboot if prompted.

Method 2: Update Network Settings in the Server Console

The Server Console is the right tool when you are doing initial setup, recovering a system, or you have lost web access to Server Manager. It provides direct, menu-driven access to the same underlying configuration.

Steps in the Server Console

1. Connect to the system using a local console, or open an SSH session to the system IP.
2. Log in as root, or log in and run su admin to switch to the admin user, then enter the administrator password.
3. Choose the option to configure the server. The console lets you view and modify the configuration entered during installation: Ethernet cards, IPv4 address information, DHCP, DNS, and domain names.
4. Enter the new values, apply the configuration, and reboot when prompted.

Voice-Side Networking in the System Administration Tool

The System Administration Tool is where voice-side networking is configured, separate from the server's own IP identity. Admins reach for these forms when phones are not getting addresses or when call routing crosses subnets.

• DHCP for IP phones. MiVoice Business can act as the DHCP server for phones, or you can use an external DHCP server with the correct vendor-specific options pointing phones at the call server. The DHCP forms are in the System Administration Tool.
• IP routing and network elements. Routing for voice traffic and the definition of network elements, meaning other controllers, gateways, and resilient pairs, are managed in the System Administration Tool, not Server Manager.

A practical rule: if the setting is about how phones and trunks reach the system, it is in the System Administration Tool. If it is about the system's own address on the network, it is in Server Manager or the Server Console.

What Breaks When You Change the IP

Changing the system IP address on MiVoice Business is disruptive by nature, and planning for the fallout is part of doing it correctly. The change does not just update a field. It moves the address every phone and trunk was registered against.

• Phones lose registration until they re-resolve the call server, which may require a phone reboot or a DHCP lease renewal.
• Reusing an old IP on a replacement controller can leave you reachable only from the local subnet at first. Until the router ARP cache updates or you clear it manually, other subnets will not reach the new hardware.
• Mitel's own troubleshooting guidance is to change a single setting, hardware or software, per step, and to document the starting state before you touch anything.
• Because a restart is usually required and startup can take up to roughly 15 minutes, treat any IP change as a maintenance window, not a live edit.

Troubleshooting a Mitel Network Change

Most network-change problems on MiVoice Business fall into a short list of causes. This matrix maps the symptom to the likely cause and the fix.

On-Premises Mitel vs a Cloud Platform

Set the manual work of MiVoice Business administration next to how the same tasks run on a cloud platform and the operational gap is easy to see. The table below contrasts on-premises Mitel with a cloud-delivered model for the work this guide covers.

The On-Premises Admin Tax

Here is the framing worth sitting with. Changing a phone system's network settings should be a field update, not a maintenance window with broken-phone fallout and a fifteen-minute reboot. Call it the on-premises admin tax, the recurring cost in admin hours, scheduled downtime, and platform-specific tribal knowledge that comes with owning the box rather than consuming the service.

Knowing that DNS lives in Server Manager but DHCP for phones lives in the System Administration Tool is exactly the kind of platform trivia that does not transfer anywhere and does not create value. It is overhead. That overhead compounds across every move, network change, and upgrade, and it is the friction that pushed the market toward cloud and hybrid delivery in the first place, the same shift the platform vendor itself is now chasing. For teams weighing that move, our guide to replacing legacy phone hardware covers the migration decision in detail.

This is where a modern platform changes the equation. Viirtue runs a carrier-grade voice network delivered as a service, so the underlying network configuration is Viirtue's responsibility, not a console an admin has to learn. For providers who resell communications rather than just run their own phones, the white-label reseller program packages that platform as a white label VoIP platform partners can brand as their own, with quoting and billing automation handled by ViiBE. Moving a customer or standing up a new site is a console action, not a subnet-cutover project, and our white label PBX reseller guide walks through how that model is packaged and priced.

The contrast goes beyond avoiding reboots. SIP-only providers hand you connectivity and leave provisioning, billing, and any intelligence layer for you to assemble. Standalone AI calling tools require stitching multiple systems together. Mainstream UCaaS platforms treat resellers as a channel afterthought. Viirtue's AI Voice Agents are native to the platform rather than bolted on, so the same console that manages a customer can stand up an AI agent. If you are weighing where a Mitel estate goes next, the best white-label VoIP providers for 2026 is a useful starting comparison.

For context on scale, Viirtue supports 500 or more reseller partners on this model today, which is the practical evidence that channel-first, full-stack delivery is a working alternative to owning on-premises hardware.

Key Takeaways

• MiVoice Business core network settings (IP, mask, gateway, DNS, DHCP, domain) live in Server Manager or the Server Console, never in the System Administration Tool.
• The platform has three admin surfaces: System Administration Tool for voice, Server Manager for server and network, Server Console for direct and recovery access.
• The default Server Manager login is admin / default1, with a forced eight-character-minimum password change that syncs the Web GUI and admin account.
• Voice-side networking, meaning phone DHCP, IP routing, and network elements, is separate and lives in the System Administration Tool.
• Any IP change is a maintenance event: expect phone re-registration, possible ARP-cache clearing, and a reboot that can take up to roughly 15 minutes.
• The platform knowledge required to do all this by hand is the on-premises admin tax that cloud and hybrid delivery are designed to remove.

Hold the layer model, plan the IP change as a maintenance window, back up first, and the cutover is routine.

Updating Network Settings on a Mitel PBX and the Partner Opportunity

Updating network settings on a Mitel MiVoice Business PBX is straightforward once you know the layer model: server and IP settings in Server Manager or the Server Console, voice-side networking in the System Administration Tool. Plan the IP change as a maintenance window, back up first, account for phone re-registration, and the cutover is routine. The harder question is how much of this work should exist at all.

If the platform overhead is wearing on your team, or if you resell communications and want a network someone else keeps running, a cloud-delivered hosted VoIP model changes the math. There are no subnet cutovers, no fifteen-minute controller reboots, and no three-surface tribal knowledge, and the same console that provisions a customer can stand up an AI agent or generate a branded invoice. To see how the reseller economics work, become a Viirtue partner and walk through provisioning without the maintenance windows. The Viirtue partner program is built for MSPs, IT providers, and telecom resellers who want margin ownership instead of referral fees.