3CX SIP Trunk Configuration in Dubai — Etisalat & du, Connected and Carrying Calls
The Etisalat engineer left this morning. The trunk is live. 3CX still cannot find it. If that is your week, the causes are a short known list and every one has a fix. If the engineer is booked for Thursday, what follows is how to make sure that morning goes cleanly — what to order from the carrier, what to have ready, why a live trunk can still refuse to register, and how your existing numbers move with you.
Vector Digital Systems has connected business phone systems to Etisalat and du lines from Dubai since 2009 and holds 3CX Titanium — the highest solution-provider tier 3CX awards. Trunk configuration, number porting and live testing are part of every 3CX installation we hand over.
Three ways a trunk project stalls — all three preventable
A 3CX system is judged on one morning: the day it goes live. When that morning slips, it is almost never the PBX. It is one of three things that went wrong weeks earlier — at the carrier order, in the network, or in the porting plan. Name them early and none of them happens.
The wrong product from the carrier
- Etisalat eLife and du Home are residential lines — they carry no SIP
- A 3CX system needs Etisalat Business or du Business — and SIP must be specifically requested as a service on that account, it is not enabled by default
- Discovered after the visit, this costs weeks — a new carrier order from zero
- Etisalat and du do not provision residential lines at business addresses — so this error surfaces in villa offices or premises registered as residential
The trunk registers — then calls misbehave
- One-way audio. Transfers that drop. An IVR that answers in silence
- UAE SIP trunks arrive on the carrier’s own private network — a dedicated connection with private IP addresses, separate from the business internet
- The 3CX machine must be routable from that private carrier interface — if the router does not bridge the carrier’s segment to the LAN correctly, audio breaks even when registration succeeds
- SIP ALG then fires on top of that — rewriting voice packets in transit and breaking calls that were just starting to work
The numbers arrive after the phones
- The number your customers have dialled for years must move on cutover day
- Porting is a carrier process with its own clock — it cannot be compressed at the end
- Planned at the start, the port lands on schedule and the cutover is invisible to callers — the old system answers until the moment the new one does
- Left to the end, the new system waits for its own number
All three are prevented in the same place: a scoping conversation before anyone visits. That is the first thing we do — and it is why the have-ready list at the top of this page exists.
Who does what — stated before anyone visits
A trunk project has three parties. Confusion between them is where days disappear. Here is the split, in writing, before a single visit is booked.
Etisalat / du deliver
- The business SIP trunk, provisioned to your premises on the carrier's own network
- The line rental and call charges — billed on your carrier account, directly
- The porting execution, on the carrier's confirmed window
Vector Digital configures
- The trunk on 3CX — carrier-correct settings, inbound and outbound routes
- Number porting preparation and the cutover plan
- Live testing on the real line — inbound, outbound, transfers, IVR, recording
- Firewall coexistence — including FortiGate — so voice and security stop fighting
You provide
- The carrier account type and the SIP details letter
- A static IP and the firewall or router model
- The list of numbers moving with you
- A LAN contact for the visit window
The line rental is never on our quotation
It is a carrier service on your own Etisalat or du account, billed by them directly — before us, during us, after us. What we quote is the work: configuration, porting and testing on the live line. Trunk work is one part of a full phone system installation — extensions, IVR, training and handover complete it.
Running a Dubai head office and a Sharjah or Abu Dhabi branch on one dial plan is the same discipline applied twice — we run exactly that topology ourselves between our Dubai and Kochi offices, every working day.
The trunk is active. 3CX cannot see it. Here is why that happens
This is the call we get most: the carrier confirms the trunk is live, a softphone even registers — and 3CX will not. Three days in, everyone is blaming everyone. The causes are a short, known list.
The generic template. 3CX ships with generic SIP templates, and UAE carrier trunks have their own expectations — the credential format, which field takes the domain and which the proxy, how authentication is presented. A template that is close-but-wrong registers nothing and reports little. The fix is carrier-correct configuration, not more retries.
SIP ALG, rewriting packets in silence. Many routers ship with SIP ALG enabled — a feature that rewrites voice traffic to be helpful and quietly breaks registration or audio instead. Everything pings. Nothing calls. It is one of the first things we check, because it is invisible from inside 3CX.
The topology question. UAE business trunks are delivered to your premises over the carrier's own network — not the open internet. Where the 3CX machine sits relative to that handoff decides whether registration is even possible. A system placed on the wrong side of the network cannot reach a trunk that is, on paper, in the same building.
The firewall doing its job too well. A security policy that passes ping and web traffic can still drop voice. We deploy FortiGate firewalls ourselves, so voice-and-security coexistence is configuration we do weekly — not a standoff between two systems.
Each of these has a definite fix. None of them is guesswork the fourth time you have seen it — and by now we have seen each of them far more than four times.
Describe the Symptom on WhatsAppThe number your customers dial moves with you
A business number is not a technical detail. It is on your signboard, your invoices, your trade licence file and in a thousand saved contacts. Moving to 3CX does not mean changing it — porting moves your existing Etisalat or du numbers onto the SIP trunk, so the outside world notices nothing.
The part that matters is when porting is planned. It is a carrier process with a confirmed window — we place the port with the carrier at the start of the project and align the cutover to it, after working hours, so the old system answers calls until the moment the new one does.
On cutover day the sequence is simple: the numbers land on the trunk, 3CX answers them, and every extension, IVR branch and recording rule you approved is already live — tested before your customers ever dial in. What the full system costs — licence, appliance and installation — is mapped in AED on our 3CX price guide for Dubai.
Compliant by design — licensed trunks, on your premises
Under TDRA regulation, business voice in the UAE runs on licensed Etisalat and du SIP trunks — and those trunks are delivered on-premise, to equipment in your building. A foreign cloud PBX carrying office calls over the public internet, bypassing the licensed carrier, is not the compliant path.
That is why the UAE-standard 3CX deployment is the shape this page describes: the system on your premises, the licensed trunk connected to it, your call recordings and data staying inside your office. Compliance is not a constraint we work around — it is the design. The full picture — editions, licensing and what 3CX replaces — is on our 3CX telephone system Dubai hub.
Etisalat, du and 3CX — the working answers
The Etisalat engineer said the trunk is active. Why won't 3CX register it?
We signed up for Etisalat eLife. Will it work with 3CX?
Can we keep our existing phone numbers when we move to 3CX?
How long does SIP trunk configuration take?
Does our monthly Etisalat or du bill change when we switch to SIP?
Can I run 3CX on a cloud server with a UAE SIP trunk?
Etisalat or du — which SIP trunk works better with 3CX?
What should we have ready before the configuration visit?
Which areas of Dubai and the UAE do you cover for SIP trunk work?
Can 3CX run alongside our old Panasonic or NEC during the switch?
Trunk installed and not registering? Tell us the symptom.
Send the Etisalat or du account type and the carrier's SIP details letter on WhatsApp. We tell you what is wrong — and what it looks like fixed — before anyone books a visit. Still at the planning stage? Send the five have-ready items instead, and the whole project is scoped the same day.