Products · Mitel
Mitel MiVoice MX-ONE: support, maintenance and upgrades
Mitel MiVoice MX-ONE, formerly Ericsson MX-ONE, is Mitel’s PBX for large organisations, with roots in the MD110. We provide MX-ONE support and maintenance, upgrades and step-by-step modernisation with Teams, Mitel CX and Workflow Studio.
We usually start with a simple inventory of your PBX, licences and integrations.
About Mitel MiVoice MX-ONE
From the MD110 to today’s MX-ONE
MiVoice MX-ONE is a SIP-based PBX for large organisations with many sites. It consists of a call server running on Linux, a software media server and, where needed, gateways for analogue and digital connections. According to Mitel, it scales from 500 to 500,000 users in a single system.
Ericsson developed MX-ONE as the step to IP for MD110 customers. The platform passed via Aastra to Mitel in 2014. The latest version is 8.2 SP1, and it can run on your own servers, virtualised or in AWS and Azure.
We are a Mitel Silver Partner and have completed training on MX-ONE.
Last updated 25 October 2026.
At a glance
- For large organisations with many sites
- Latest version 8.2 SP1
- On your own servers, virtualised or in AWS and Azure
- Redundancy and branch survivability
- Open interfaces: SIP, CSTA and REST
- Works with Teams, Mitel CX and Workflow Studio
Support
Support and maintenance for MX-ONE
We support MiVoice MX-ONE in all versions, including systems sold as Ericsson MX-ONE or Aastra MX-ONE. If you have an older version, we can upgrade it so that it receives Mitel’s fixes again.
What’s included
- Fault reporting and troubleshooting, with remote access that you control
- Contact with Mitel when a case needs escalating
- Changes to the PBX, such as extensions, groups and permissions
- Software Assurance and your licences with Mitel
- Regular reviews of the PBX and a plan for the next step
We describe what a support contract should include in the guide PBX support contracts.
Fault reporting
Report faults as set out in your support contract, which also states the hours that apply. No contract with us yet? Call +46 8 730 66 00 or email info@icomserv.com.
How we help you
What we do with Mitel MiVoice MX-ONE
Upgrades
From older 7.x to 8.x, with checks of licences, Software Assurance and integrations.
Security
We follow Mitel’s security advisories and make sure fixes are applied in good time.
Virtualisation
From your own hardware to virtual servers in your data centre or in the cloud.
Teams
Via Direct Routing and an SBC, which protects the traffic between your network, your operator and Teams, or with Mitel Assistant in Teams.
Contact centre and automation
Mitel CX and Workflow Studio on top of the PBX, without replacing it. Workflow Studio also works without Mitel CX.
Support takeover
If another provider has looked after your PBX, we take over support with a plan and a parallel period, as part of our third-party PBX maintenance.
Use cases
How Mitel MiVoice MX-ONE is used
Moving on from the MD110 and older 7.x
A controlled path to a version that receives fixes and works with new integrations.
Teams for the office, MX-ONE for the rest
Users make calls in Teams, while alarms, analogue devices and the contact centre stay on the PBX.
Contact centre with Mitel CX
Voice, chat, email and SMS in the same queues, on top of MX-ONE.
Voicemail to text
With Workflow Studio, voice messages become cases. According to Mitel, a hospital group in Belgium does this with its MX-ONE.
Virtualisation
Old hardware is replaced with virtual servers, with the same PBX and the same numbers.
Branches that keep working during outages
Branches have local survivability and their own route out to the phone network if the link to the main system goes down.
Works with
- Microsoft Teams via Direct Routing and SBC, or Mitel Assistant
- Mitel CX (requires MX-ONE 7.8 SP1 or later)
- Mitel Workflow Studio, also without Mitel CX
- Mitel InAttend attendant console
- SIP trunks from operators
- Analogue phones, DECT and alarms via gateways
What we review first
- Current version and hardware
- Software Assurance status
- Number of users and sites
- Integrations: contact centre, attendant console, alarms and Teams
- Requirements for redundancy and backup routes
- How the PBX is exposed to the internet
How we work
From the first conversation to day-to-day operations
01
Discovery
We review how you work today, which systems you have and what you want to achieve.
02
Proposal
You receive a concrete proposal covering technology, timeline and cost, and we explain our choices.
03
Implementation
We install, integrate and test, and we train your users and administrators.
04
Operations and support
After go-live, we stay with you for support, updates and further development.
Common questions
Frequently asked questions about Mitel MiVoice MX-ONE
Is MX-ONE the same PBX as Ericsson’s?
Yes, it is the same product line. Ericsson developed MX-ONE as the step to IP for MD110 customers. It passed via Aastra to Mitel in 2014 and is now called Mitel MiVoice MX-ONE.
Can MX-ONE run in the cloud?
Yes. According to Mitel, it can run on your own servers, virtualised in your own data centre, for example on VMware, Hyper-V or Nutanix, or in AWS and Azure. We can also run it for you as a private cloud hosted in Sweden.
Does MX-ONE work with Teams?
Yes, via Direct Routing and a certified SBC. Mitel also offers Mitel Assistant in Teams, with presence in both directions. Users who make calls via Direct Routing need Teams Phone.
We run an older 7.x. Do we have to upgrade?
No, not to get support. We work with all versions of MX-ONE. But Mitel’s fixes come in the latest version, and new integrations such as Mitel CX 3.0 require version 7.8 SP1 or later. New versions require active Software Assurance. We go through what applies to you. We explain what it means when a version no longer receives fixes in the guide on the PBX lifecycle.
Can we keep analogue phones, wireless DECT phones and alarms?
Yes. Gateways handle analogue and digital connections, and the DECT system can stay. Mitel also describes a step-by-step path to a fully IP-based PBX.
What happens if a server goes down?
It depends on how the PBX is set up. The options include standby servers, phones that register with another server, survivability per site and geographic disaster recovery.
Further reading
Guide
Upgrade or replace your PBX?
Decision support for organisations that run MX-ONE or OpenScape today.
Solution
PBX migration
From an old PBX to a new platform or Teams, step by step, with a rollback plan for every stage.
Guide
Teams and your existing PBX: coexistence and gradual migration
How to let Teams and your PBX work together while you move at your own pace.
Product
Mitel CX
Contact centre for voice and digital channels, with AI, on top of Mitel PBXs such as MX-ONE and OpenScape.
Solution
Third-party PBX maintenance
Keep the PBX that works. We take over support for MX-ONE, OpenScape and OmniPCX Enterprise and keep your PBX up to date with the manufacturer’s security fixes.
Guide
PBX lifecycle and end of life: extending its life safely
What manufacturers’ lifecycles mean, and how to keep your PBX secure for many years to come.
Third-party PBX maintenance
Start with an inventory
Do you have an MX-ONE, OpenScape or OmniPCX Enterprise? We usually start with a simple inventory of your PBX, licences and integrations, free of charge. You then know where you stand, and we can give you a quote for support, operations or replacement.