Licensing Models in MX-ONE

The licensing structure in MX-ONE is constantly evolving as the demand is changing. While the system has transformed into a SIP-based software system, complemented by a wide range of hardware options, alternative licensing and business models are also supported.

Subscription and SWA with Time based Licenses

The CAPEX business model includes a SoftWare Assurance (SWA) license in the license file. The SWA license will generate a warning when 30 days remain for its expiry. Upon expiry, another alarm is generated.

Software updates or upgrades are rejected, and even data changes that require a license will be rejected after expiry of the license.

The OPEX Business model includes a Subscription/MLA system license in the license file. The System license for Subscription/MLA systems will generate a warning alarm when 30 days remain for its expiry. Upon expiry, another alarm is generated. Software updates or upgrades are rejected after the expiry of this license. 60 days after expiration, external calls except those which go to an emergency destination will be barred.

For more information about these licenses, see the ordering information document for MX-ONE and Mitel CPQ tool.

Capital Expenditure (CAPEX) Based Business Model

Á-la-carte configuration and licensing is the classic model. Through this model, the system can be tailor-made in order to fulfill the various needs for complex or specific system deployments. Á-la-carte is the model to be used for systems migrating from earlier versions towards MX-ONE 7.x.

To address the demand for a simplified structure, and to align with expectations pure IP-based systems MX-ONE also offers the Feature Bundle based licensing model. Through this model competitive user-bundles are offered, including both the MX-ONE user functionality and a range of matching UCC features in MiCollab. The different "feature-level” profiles or pre-set user profiles are:

  • Basic user
  • Entry UC user
  • Standard UC user

For more information about the MX-ONE licensing see New sales & Add-on or Feature-based ordering information document for MX-ONE and Mitel CPQ tool.

Operating Expenditure (OPEX) Based Business Model

Furthermore, MX-ONE supports customers and partners who are looking forward towards new business models. In addition to the classic á-la-carte configuration model and the Feature-Based configuration model which are both offered as a Capital Expenditure (CAPEX) based business model, the MiVoice MX-ONE also offers native support for cloud-based deployments and an Operating Expenditure (OPEX) based business model. This subscription-based business model is based on the Feature-Based configuration model and is offered by partners who qualify for delivering and charging for the Subscription//OPEX model where customers are charged for actual license usage on monthly basis.

Each Subscription/MLA licensed MX-ONE system will automatically send monthly license usage reports as the basis for all invoicing. The license usage information for each MX-ONE Subscription/MLA system is sent in the form of an e-mail with a CSV attachment to pre-determined recipients at the Partner and Mitel. This CSV file is then the basis for the true usage-based charging.

For more information about the MX-ONE Subscription/MLA licensing see the ordering information document for MX-ONE and Mitel CPQ tool.

SLS Heartbeat Function

If the “SLS-HEARTBEAT” function is turned on, the MX-ONE system will send a heartbeat request to SLS, with its own HW Identity and version. This is for statistical purposes.

At system startup, the first heartbeat request is sent, and then a request is sent every 30 days. If a request fails to get a response, another attempt is made after 1 hour. After three consecutive failed attempts, an alarm is raised.

When the alarm state is entered, a new attempt is made every 24 hours until a response is obtained. The function is turned on/off using the license_sls command.

SLS License Download

When this function is turned on, MX-ONE attempts to download a new license every 30 days in conjunction with the SLS heartbeat function. The function is turned on/off by using the license_sls command.