Avaya in Syria — support, parts and migration for installed estates

Where an Avaya system has run for years without vendor attention, parts and a current software release can be hard to obtain. EIE supports, supplies parts for and migrates Avaya estates for customers in Syria from its engineering base in Jeddah.

Why Avaya matters in Syria now

EIE supports Avaya estates for customers in Syria across banks, ministries, hospitals and larger enterprises, and the work takes a few recognisable shapes. Where a Definity or Communication Manager system still carries head-office traffic in Damascus or Aleppo, the questions are about parts and release support. Where an IP Office unit sits in a branch, clinic or mid-size office in Homs, Latakia or Hama, they are about configuration and licensing. Where Aura components are in service, they are about session routing and supported releases.

Where such a system has been in service for years, the harder problems can sit around it rather than in it. Spare cards can be difficult to source, a software release can sit outside vendor support, the engineers who knew the dial plan can have moved on, and the licence position can stop matching what is actually installed. An Avaya IP Office system can run for a long time without attention and then fail in a way that nobody on site can resolve, because the knowledge and the parts both went. EIE’s Avaya support for Syria is scoped to close that gap.

What EIE supplies and supports for Avaya in Syria

Our Avaya work in Syria is support-led, with supply where the estate is worth extending.

• Communication Manager and Definity — remote fault diagnosis, dial plan and routing work, translations changes, and advice on which releases still have a sensible upgrade route.
• IP Office — IP Office 500 V2 control units and Server Edition estates: configuration, voicemail, hunt groups and auto-attendant work, and licence reconciliation.
• Aura components — Communication Manager, Session Manager and System Manager estates, including SIP trunk and session routing troubleshooting.
• Parts and hardware — control units, media gateways such as the G430 and G450, trunk and station cards, power supplies, and handsets from the 1400, 1600, 9600 and J100 families.
• Licensing — establishing what the estate is entitled to, what it actually uses, and what a supported position would cost.
• Migration — a staged route to Mitel, or a controlled move to a supported Avaya release where the estate justifies staying.

How delivery works for Syrian customers

EIE is headquartered in Jeddah, Saudi Arabia, and delivers into Syria without a local base.

Remote engineering from Saudi Arabia. EIE does the diagnosis and configuration work over a remote connection. Our Saudi engineering team connects to the system, reads the configuration as built, reproduces the fault and makes the change, which avoids waiting for travel on problems that do not need hands.

Parts sourcing and shipment. We identify the correct part against what is physically installed rather than against the drawing and source it, and it can normally be shipped to Syria with logistics coordinated with the customer’s freight forwarder and import broker. 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 for the physical phases. Card replacement, gateway swaps, cutovers and structured migration have stages that need an engineer in the room. EIE engineers travel to Syria for those phases. A Damascus presence is planned; until it exists, on-site work is delivered by travelling engineers.

Ongoing support. Fault handling, moves and changes and parts continue under an agreed arrangement, with coverage, escalation and on-site attendance governed by each customer’s service agreement.

Example Avaya projects in Syria

Consider a bank that asks us to stabilise a Communication Manager estate: document what is installed, restore the parts position, and set out whether the sensible next step is a supported release or a migration. A government department might need a failed card replaced and the dial plan documented, because the person who built it is no longer there.

A hotel running IP Office would want working guest telephony and a property-system link that survives check-out, which can become a migration conversation. A campus would ask whether a multi-building estate can be consolidated onto one platform without renumbering everybody.

Migration, or a supported Avaya release

There are two realistic routes off an installed Avaya estate, and which one fits depends on the equipment rather than on a preference.

Where the hardware still has life and the organisation is comfortable with the platform, a controlled move to a supported release keeps the investment and restores the ability to get help. Where the estate is Definity-era, the parts position is poor, or the organisation is consolidating several sites, migration to Mitel is the better answer — see Mitel in Syria. Either way the method is the same: assess what is genuinely installed, preserve numbering, rebuild attendant and queue behaviour before cutover, and run old and new alongside each other while departments move.

Where an estate also includes Nortel equipment, that is covered on our Nortel in Syria page; where the network underneath needs attention, see Ruijie in Syria. For the wider picture, see unified communications.

How to start

Tell us what is installed, what is failing and what you can see from the system’s own screens, and we will tell you what we would check 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 support an Avaya system in Syria without an office there?
Yes. Diagnosis and configuration work are done remotely from Saudi Arabia, parts can be shipped to Syria, and EIE engineers travel for the phases that need hands on the equipment. Coverage is governed by each customer’s service agreement.

Can you find parts for an old Definity or IP Office system?
In most cases. We identify the part against what is physically installed and source it, and it can normally be shipped to Syria, subject to the supply conditions set out above. Where a part has become impractical to obtain, we say so and set out the alternatives rather than leaving the estate waiting.

Should we repair the Avaya estate or migrate to Mitel?
It depends on the hardware generation, the parts position and whether you are consolidating sites. We give a straight assessment of both routes with the reasoning, because the decision belongs to you.

Do you work on Avaya IP Office in branches outside Damascus?
Yes. Remote work reaches any site with a usable connection, and travel is arranged for the physical phases wherever the site is.