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

Where Avaya equipment is still answering calls at a Yemeni site, the licence path, the software plan and the administration passwords are the first things EIE asks about. EIE supports Avaya estates for customers in Yemen from Jeddah, sources the parts an estate needs, and sets out the route forward.

Why an Avaya estate in Yemen may need attention now

Avaya platforms are specified for the building types Yemen has — banks and exchange houses, ministries and governorate administrations, hospitals, universities and oil-and-gas operators. Where an estate of that kind is still in a comms room in Sana’a or Hodeidah, EIE’s first questions are about what surrounds the cabinet rather than the cabinet itself: whether a support arrangement is still in place, where the installed release sits against maintenance, whether the licence file was ever backed up, and who holds the administration password.

EIE’s Avaya work for customers in Yemen covers both recovery and expansion, and two site conditions shape how it is done. Where power at a site is interrupted, systems that keep their identity on removable media or a spinning disk suffer for it. And an Avaya estate is administered through sessions that assume a stable link, so where the connection is intermittent the work is broken into short prepared steps rather than one long session.

What EIE supplies and supports for Avaya in Yemen

• IP Office — IP Office 500 V2 control units, combination and extension cards, digital and analogue station ports, Voicemail Pro, and SD card and licence rebuilds after a failure.
• Communication Manager and Aura — call control, Session Manager and System Manager, G430 and G450 gateways, media modules, and the licensing housekeeping these estates quietly depend on.
• Definity and older cabinets — TN circuit packs, power supplies, E1 and analogue interfaces, and the cross-connect work that goes with them.
• Endpoints — digital and IP instruments from the 1400 and 9600 families, DECT for wards, and the analogue instruments an estate still carries.
• Remote troubleshooting — fault diagnosis, trace capture sized for a narrow link, trunk correction after an operator change, and changes applied in short windows.
• Parts sourcing — cards, modules, control units and instruments sourced against the specific requirement, tested before dispatch and consolidated into one consignment.
• Documentation recovery and migration — reading the estate out as it was actually built, then moving to Mitel or a supported Avaya release.

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. Diagnosis, configuration, licensing recovery and change work are done by our Saudi engineering team remotely, scoped to the bandwidth the site has.

Parts and shipment. Replacement cards, modules and control units are sourced against the requirement and can normally be shipped by sea to Aden or Mukalla, or by road through the Saudi-Yemeni land crossings, with import formalities handled by the customer’s freight forwarder and customs broker. Where a system is being rebuilt, the replacement is prepared in Jeddah so it can be fitted quickly. 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 card replacement, cabinet work, cutover and commissioning when a project needs it and conditions allow.

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

Example Avaya work in Yemen

Consider a bank or exchange house running IP Office at its outlying locations, where one has failed and nobody on site can rebuild it. The work is licensing recovery, a configuration restored from whatever backup exists, then a standing arrangement so the next failure is routine.

A hospital would be a continuity problem before it is a telephony problem: ward extensions, a switchboard that cannot go quiet, and analogue instruments that survive whatever the power does. An oil-and-gas or port operator adds distance and environment, with paging interfaces that must keep working alongside it, and a ministry or university would turn on published numbers and a dial plan across buildings.

Staying on Avaya, or migrating to Mitel

Both are legitimate answers and the estate decides which. If the platform can still be licensed, supplied and patched, a controlled move to a supported Avaya release is the shorter road and we will say so. If it depends on hardware that can no longer be sourced sensibly, or the licensing position cannot be re-established, migration is the recommendation we will give.

Where migration is the answer, Mitel is one of the platforms EIE assesses against the estate: the range covers the same building types, and the choice is settled by the installed release, licensing, handset and trunk compatibility and lifecycle rather than by any relationship between vendors. Numbering is preserved, queue and attendant behaviour is rebuilt and tested before cutover, and gateways let both platforms run side by side while departments move. See Mitel in Yemen, Nortel in Yemen where the site also carries older equipment, Ruijie in Yemen where the network needs work too, and unified communications.

How to start

Tell us what is installed, what has failed, and what you still have of backups, licence records and documentation. Start with the Contact form, email info@eliteideas.net or call +966 12 652 2996. See also EIE in Yemen.

Frequently asked questions

Our IP Office lost its licensing after a power failure. Can that be dealt with remotely from Jeddah?
Often yes. The usual route is to rebuild the SD card image, re-host the entitlement against the system identity and restore the configuration from the most recent backup. If the control unit itself has failed, a replacement is prepared in Jeddah and shipped.

Can EIE support an Avaya system it did not install, with no documentation?
Yes. Where no documentation survives, the first task is a survey recording platform and release, licensing position, numbering and routing as actually built, and how the equipment is powered.

How are Avaya spare parts obtained for a site in Yemen?
They are sourced against the confirmed requirement, tested before dispatch, and consolidated with the rest of the order, so you are not put through a second import cycle for a single card.

Should we stay on Avaya or move to Mitel?
That is decided by what the estate can still be licensed and supplied for, not by preference. The assessment sets out both routes and what each costs you in disruption.