Mitel in Yemen — IP PBX and UC supply, migration and support

Mitel is one of the platforms EIE puts on the shortlist for a hotel, a bank or a campus, and it is built to be specified once and kept in service for a long working life. EIE supplies, configures and supports Mitel systems for customers in Yemen from Jeddah.

Why Mitel is on EIE’s shortlist for Yemen

A telephone system is rarely replaced while it can still be kept in service, so by the time a replacement is specified the organisation has lived with the previous choice for a long time. Where EIE is asked to specify a platform for a site in Sana’a, Aden or Taiz, the questions that matter first are less about feature lists than about whether the platform restarts cleanly after a transfer to generator, whether a building keeps dialling when its link drops, and whether existing analogue instruments can stay.

Mitel answers those questions well. One vendor covers a single administrative building and a multi-site university, and an IP PBX built this way keeps a site dialling when the wider network is unreachable. Hospitality integration is native, which matters where the building is a hotel in Aden or Mukalla. Where the system being replaced is a Nortel one, the history matters: Nortel’s enterprise voice business became part of Avaya, and Avaya has since ended sales and manufacturer support for the CS1000 line. A move to Mitel is a platform change to a different vendor; EIE plans it from an assessment of the installed release, licensing, handset and trunk compatibility, and lifecycle — not from any vendor lineage.

What EIE supplies and supports for Mitel in Yemen

• MiVoice Business — call control for larger organisations, with resilience across locations, and contact handling and recording where a bank or ministry switchboard calls for them.
• MX-ONE — campus and multi-site estates under one numbering plan, with call handling placed close to the users it serves.
• MiVoice Office — compact call control for a clinic, a governorate administration building, an exchange house head site or a smaller hotel.
• Hospitality integration — the property management system link: check-in and check-out, guest name display, wake-up calls, room status and charge posting.
• Gateways and trunking — SIP termination where the operator delivers it, E1 and analogue interfaces where it does not, and gateways that keep existing risers and paging circuits in service.
• Handsets and consoles — desk and guest-room instruments, cordless handsets for housekeeping rounds, and attendant consoles in Arabic and English.
• Design and migration — dial plan and routing design, licence sizing, UPS planning for the call control and the switching that feeds IP handsets, and structured migration from a legacy PBX.

How delivery works for customers in Yemen

EIE is headquartered in Jeddah, Saudi Arabia, and has service coverage in Yemen without a local base.

Remote engineering from Jeddah. Design, dial plan build, configuration, integration and fault diagnosis are carried out by our Saudi engineering team over a remote connection, in sessions shaped for a narrow or intermittent link where that is what the site has.

Supply, staging and shipment. We quote and source the equipment, which can normally be shipped by sea through Aden and Mukalla or by road through the Saudi-Yemeni land crossings, with import handled by the customer’s freight forwarder and customs broker. Where it shortens the on-site window, the system is racked, licensed and tested in Jeddah before packing. Equipment supply is confirmed at quotation and is subject to the vendor’s export and re-export rules for the destination, restricted-party and end-use screening, customs documentation, and carrier and route availability at the time of shipment.

Engineers on site when the phase needs it. EIE engineers travel to Yemen for installation, cutover, integration testing and handover, when a project needs it and conditions allow.

Support after handover. Fault handling, moves and changes, software currency and spare parts continue, governed by each customer’s service agreement.

Example Mitel projects in Yemen

Consider a hotel in Aden or Mukalla: it needs guest-room instruments, a front-desk console, hospitality integration and cordless coverage for housekeeping. The exceptions decide whether the installation is any good: room moves, split folios, and check-out while the room is still being cleaned. Power planning belongs in the same conversation, because a guest telephone that dies with the mains is not a telephone.

A bank or exchange house would have a different shape: numbering spanning the head site and outlying locations, each working when its link drops, and a clear position on where call recordings are held. A ministry or governorate administration would be a continuity problem, with one dial plan across buildings and published numbers that must not change, and a hospital or university the same at larger scale.

Migrating to Mitel from a legacy PBX

Where an organisation is coming off a legacy PBX, the route matters as much as the destination. Nortel’s enterprise voice business became part of Avaya, and Avaya has since ended sales and manufacturer support for the CS1000 line. A move to Mitel is a platform change to a different vendor; EIE plans it from an assessment of the installed release, licensing, handset and trunk compatibility, and lifecycle — not from any vendor lineage. The same assessment governs a move from an Avaya estate that can no longer be licensed.

The work is a structured migration, not a swap. It starts with an assessment of what is installed: platform versions, the numbering plan, the features people genuinely use, trunks, cabling and the power feeding all of it. Published numbers are preserved, attendant and queue behaviour is rebuilt and tested before cutover, and gateways let old and new run alongside each other. EIE plans that staging so an on-site visit covers as much of the work as it can.

Vendor detail sits on our Nortel in Yemen and Avaya in Yemen pages, and the network underneath on Ruijie in Yemen. For the wider picture see unified communications and Mitel systems in Saudi Arabia.

How to start

Tell us the building type, what is installed, how the site is powered and what is failing, and we will say what we would look at first. Start with the Contact form, email info@eliteideas.net or call +966 12 652 2996. See also EIE in Yemen.

Frequently asked questions

Can EIE supply a new Mitel system to Yemen without a local base?
Yes. Systems can normally be shipped by sea to Aden or Mukalla or by road through the Saudi-Yemeni land crossings, subject to the conditions above; the customer’s freight forwarder and customs broker handle import, and EIE engineers travel for installation and commissioning.

Will a Mitel system cope with our power arrangement?
That is a design question rather than a footnote. We size UPS autonomy for the call control and the switching that feeds IP handsets, check restart behaviour after a transfer to generator, and keep a survivable dialling path.

How is a quotation handled if lead times or rates change before we order?
The quotation states the currency and a validity period agreed in writing, and equipment is sourced once the order is confirmed. Route and timing follow with the customer’s freight forwarder.

Can the system be configured and tested before it ships?
Yes, and for Yemen we prefer it. The platform is built, licensed and loaded with your numbering plan in Jeddah, so what arrives has already answered a call.