Mitel in Syria — PBX and UC supply, migration and support

Mitel call platforms cover hotels, banks and public institutions, and they come up both where a system is already installed and where a building has to choose one. EIE supplies, configures and supports Mitel systems for customers in Syria from its engineering base in Jeddah.

Why Mitel matters in Syria now

Two kinds of work bring Mitel into a conversation. The first is an existing system: where an organisation in Damascus, Aleppo or Homs has kept a telephone system working without vendor support, the question is what can still be supported and what has to be replaced. The second is renewal: where a hotel, a bank, a ministry or a university is re-equipping a building, the project reaches a point at which the telephone system has to be decided. EIE supports both for customers in Syria.

Transport changes the answer. Where a site has usable IP connectivity, SIP trunking is practical whether the building stands in Latakia, Tartus or the capital, so the choice can be an IP PBX rather than a like-for-like replacement of whatever failed. Mitel earns its place there for a platform range covering a branch office and a national campus without changing vendor, native hospitality integration, and a documented route off legacy PBX equipment.

What EIE supplies and supports for Mitel in Syria

We handle both halves of the work: new systems supplied and commissioned, and existing systems kept running.

• MiVoice Business — call control for mid-size and large organisations, with resilience across sites, and contact-centre and recording options.
• MX-ONE — campus and multi-site estates run as one numbering plan, with call handling placed close to the users it serves.
• MiVoice Office — compact call control for branches, clinics, smaller hotels and single-building offices.
• Hospitality integration — the link to the property management system: check-in and check-out, guest name display, voicemail provisioning, wake-up calls, room status and charge posting.
• Handsets, consoles and gateways — desk phones, guest-room instruments, cordless handsets, attendant consoles in Arabic and English, SIP trunk termination, and gateways keeping existing circuits and paging alive.
• Design, installation support and migration — dial plan and routing design, licence sizing, staged installation, commissioning, and structured migration from a legacy PBX.

How delivery works for Syrian customers

EIE is headquartered in Jeddah, Saudi Arabia, and delivers into Syria without a local base. The model is built around that fact.

Remote engineering from Saudi Arabia. Design, dial plan build, configuration, integration setup and fault diagnosis are carried out by our Saudi engineering team over a remote connection to the customer’s system.

Supply and shipment. We quote and source equipment, which can normally be shipped to Syria with logistics coordinated with the customer’s freight forwarder and import broker so the consignment follows the customer’s own import route. Where it shortens the on-site window, systems are staged in Jeddah before they ship. 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 Syria for the stages that cannot be done down a wire: physical installation, cutover, integration testing, and handover to the operating team. A Damascus presence is planned; until it exists, on-site work is delivered by travelling engineers.

Support after handover. Fault handling, moves and changes, software currency and spare parts continue after commissioning, with coverage, escalation and on-site attendance governed by each customer’s service agreement.

Example Mitel projects in Syria

Consider a hotel returning to service: it needs guest-room handsets, front-desk consoles, hospitality integration to the property system, and cordless coverage for housekeeping. The exceptions matter more than the demonstration path: room moves, split folios, suites with several extensions, and check-out while the room is still being cleaned.

A bank would bring a different shape — branch survivability when a link drops, a numbering plan spanning head office and branches, and recording with a clear position on where recordings live and who may replay them. A government department would be a numbering and resilience problem: one dial plan across buildings, plus paging and emergency notification interfaces. A campus is the same at larger scale, delivered in phases.

Migrating to Mitel from a legacy PBX

Migration from a legacy PBX is one route into a Mitel project. 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 approach applies to an Avaya estate that has become difficult to keep supplied.

The work is a structured migration rather than a swap. It begins with an assessment of what is actually installed — platform versions, the numbering plan, the features people genuinely use, trunk arrangements, cabling and power — because the surprises in a migration are the things nobody wrote down. Numbering is preserved, attendant and queue behaviour is rebuilt and tested before cutover, and gateways let old and new run alongside each other while departments move.

Vendor detail sits on our Nortel in Syria and Avaya in Syria pages; where the network underneath also needs attention, see Ruijie in Syria. For the wider picture, see unified communications and Mitel systems in Saudi Arabia.

How to start

The starting point is an assessment of what you have. Tell us the building type, what is installed today and what is failing, and we will tell you 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 Syria.

Frequently asked questions

Can EIE supply a new Mitel system to Syria?
Yes. We supply and support new Mitel IP-PBX and unified communications systems for Syrian customers, including MiVoice Business, MX-ONE and MiVoice Office, which can normally be shipped to Syria with logistics coordinated with the customer’s freight forwarder and import broker, subject to the supply conditions set out above.

Does EIE have an office in Damascus?
Not today. EIE is headquartered in Jeddah, Saudi Arabia, and serves Syrian customers through remote engineering, equipment supply, and engineers who travel to Syria for on-site phases. A Damascus presence is planned.

Can you support a Mitel system that someone else installed?
Yes. Taking on an estate someone else installed begins with documentation, because the configuration is rarely written down accurately: platform versions and support status, licensing, numbering and routing as actually built, and integration points. From there we agree a support arrangement.

How long does a migration from an old PBX take?
It follows estate size, building count and how many integrations must survive, and the assessment establishes that before any date is discussed. Large estates are staged building by building rather than cut over in one night.