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

Where an Avaya platform still carries a building’s call traffic in Jordan, its age eventually forces a decision. EIE supports installed Avaya platforms for customers in Jordan and supplies the parts, licences and migration work they need.

Why Avaya matters in Jordan now

Avaya’s enterprise range is wide, and an estate in Jordan can sit anywhere in it. Where Communication Manager or Aura sits under a bank, an insurer, a telecom operator or a public body in Amman, the assessment has to cover more than dial tone; where Avaya IP Office runs a mid-size business, a private clinic or a city hotel, licensing and feature depth are the constraint; and a Definity cabinet can still be doing quiet work in a building nobody has had reason to touch. Where contact-centre routing is part of the estate, it is the hardest part to replace casually.

In EIE’s assessments, what dates an estate is rarely the equipment itself but what surrounds it: software releases move past what an older system runs, licensing models shift, and the engineers who knew a release well move on. A building programme does the same. Consider a hospital wing added in Amman, a hotel refurbished in Aqaba or on the Dead Sea, faculties consolidated in Irbid, or an industrial unit in Zarqa rebuilding its network: in each of those examples the system is judged against the building it will serve rather than the one it was specified for. The question is then not whether the system works, but how long it can sensibly be kept working.

What EIE supplies and supports for Avaya in Jordan

• Support for installed platforms — Definity, Communication Manager, Aura and IP Office estates, including systems EIE did not install, with fault handling and moves and changes.
• Remote troubleshooting — trunk and signalling faults, one-way audio, routing and dial plan errors, messaging problems, and contact-centre routing that has drifted.
• Spare parts sourcing — media gateways and modules, IP Office control units, circuit packs for Definity and Communication Manager including station, trunk and processor cards, and replacement telephones.
• Licence and software work — licence replacement after a hardware change, establishing what an estate is entitled to run, and a controlled move to a supported Avaya release.
• Migration — a structured route to Mitel where the estate has reached the end of its life, with numbering, queues and integrations carried across rather than rebuilt.
• Assessment and documentation — what is installed, what release it runs and what depends on it: the first deliverable EIE produces on an inherited estate.

How delivery works for customers in Jordan

EIE is headquartered in Jeddah, Saudi Arabia, with service coverage in Jordan and no local base. That matters less than it sounds: diagnosis, licence work and change control are carried out over a connection, and the phases that need hands are scheduled as visits.

Remote engineering from Jeddah. Diagnostics, configuration, dial plan and routing changes and licence work are done by the Saudi engineering team over a connection arranged to fit the customer’s security rules.

Parts and equipment supply. Cards, gateways, control units and handsets can be shipped from Saudi Arabia: road freight through the Saudi–Jordanian land border, air into Amman when a failed card is holding up a live system, or sea into Aqaba. Import formalities are handled by the customer’s freight forwarder and customs 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 when the phase requires it. Card replacement in a live cabinet, cutovers, integration testing and handover are done by engineers travelling to Jordan, alongside the customer’s own technicians.

Support scope. Coverage, escalation and on-site attendance are set out in each customer’s service agreement, so both sides know what is included before anything fails.

Example Avaya projects in Jordan

One engagement EIE provides is parts and diagnosis. A typical scenario: a system stable day to day but starting to drop cards, with no record of the release it runs. The work is to establish the true configuration, identify spares by part code, and put a change process around it.

A second is an IP Office estate that has outgrown itself — consider a hotel in Aqaba or a company in Amman that added extensions for years and now finds licensing and features fighting each other. A third would be a contact centre in Amman, where the constraint is the routing logic and the reporting built around it, so the project is documentation-heavy and phased. A fourth would be a building programme — a hospital wing, a Dead Sea refurbishment, a campus block in Irbid — where the system is not in the future design.

Staying on Avaya, or migrating to Mitel

Both are legitimate answers, and the assessment decides which. Staying makes sense where the release is supportable, the hardware obtainable and the licence position clean. Moving makes sense where cards are scarce, the release is well behind, or the building is being rebuilt around the system anyway.

Where migration is the answer, Mitel is the platform EIE supplies and migrates to, and the mechanics are those of any structured PBX move: numbering survives, attendant and queue behaviour is rebuilt and proved before anyone cuts over, gateways hold the analogue lines and lift telephones through the change, and departments cross in phases.

See Mitel in Jordan for platform detail, Nortel in Jordan where the building carries Nortel equipment, and Ruijie in Jordan for the network underneath. See also unified communications and EIE in Jordan.

How to start

Send us what you know: platform, approximate release, how many sites it serves, and what has failed. Establishing the release is part of the assessment. Start with the Contact form, email info@eliteideas.net or call +966 12 652 2996.

Frequently asked questions

Can you support an Avaya system in Jordan without being based there?
Yes. Diagnosis, configuration and licence work are done remotely from Jeddah, parts can be shipped from Saudi Arabia, and engineers travel to Jordan for the physical work. There is no EIE base in Jordan.

Can you find parts for a Definity or an older Communication Manager?
Availability follows the specific card or module, so the answer depends on the part code rather than the platform name. Send the code from the label and we will say what can be sourced.

We are undecided between upgrading Avaya and moving to Mitel. How do we choose?
By assessing the estate first: release and support status, licence entitlement, hardware availability, the integrations that must survive, and how the building is changing.

How are shipping and customs handled for parts going into Jordan?
Equipment can be shipped from Saudi Arabia by road through the Saudi–Jordanian land border, by air into Amman, or by sea into Aqaba, subject to the conditions above, with import formalities handled by the customer’s freight forwarder and customs broker.