SIP Trunk from Du Etisalat: Your 2026 Guide

You’re probably in the same position as many IT managers and operations leads in Dubai. The business wants Microsoft Teams calling, Zoom Phone, or a proper cloud contact centre. Staff want to use their business numbers from anywhere. Finance wants lower line costs and fewer legacy PBX headaches. Then you hit the UAE reality: none of this matters unless your PSTN connectivity is built on a compliant SIP trunk from Du Etisalat.

That’s the first essential point. In the UAE, voice isn’t just an app decision. It’s a carrier decision, a compliance decision, and a network design decision. If you get that wrong, you don’t have a modern telephony rollout. You have a fragile workaround waiting to fail during business hours.

A SIP trunk is the digital voice connection between your phone system and the public telephone network. If you want external calling on UAE business numbers, that connection has to be designed properly from day one. The rest of the stack, Teams, Zoom, Xcally, 3CX, Yeastar, or a contact centre platform, sits on top of it.

Your First Step to Modern Business Calls in Dubai

Most businesses start with the wrong question. They ask, “Should we move to Teams?” or “Should we replace the PBX?” The right first question is simpler: how will our UAE numbers connect to the public network legally and reliably?

That’s where SIP trunking comes in. If the term still feels abstract, this plain-English guide to what SIP is is a useful primer. In practice, it means your business numbers stop relying on old-style fixed lines and instead route through a managed IP voice connection into your phone platform.

What you need to decide first

Before you compare platforms, lock down these basics:

Your compliance path
In the UAE, business voice services must align with local telecom rules. If you skip this and try to force an overseas setup into a local numbering requirement, you create risk for inbound and outbound calling.
Your number strategy
Most businesses want to keep existing DDI numbers. That’s sensible. Renumbering users, departments, and published support lines creates unnecessary disruption.
Your call flow design
Decide early whether calls will land in Teams, Zoom Phone BYOC, a cloud PBX, or a contact centre stack with CRM integration.

Practical rule: Pick the carrier and compliance model before you buy handsets, SBC services, or user licences.

What usually goes wrong

Businesses often assume SIP trunking is just a technical checkbox. It isn’t. It determines whether calls connect cleanly, whether your UAE numbers remain usable, and whether your future contact centre rollout stays manageable.

If you’re planning a serious rollout in Dubai, treat the SIP trunk from Du Etisalat as the foundation, not the accessory.

Why Du and Etisalat Control UAE SIP Trunking

A SIP trunk is best understood as a private digital voice highway between your business phone platform and the public telephone network. It replaces the old model of physical phone lines, but it still carries the same responsibility. It has to connect your users, departments, and contact centres to real inbound and outbound calling on UAE numbers.

In the UAE, that highway isn’t open to any provider that wants to participate. Etisalat and du are the only two carriers authorised by the Telecommunications and Digital Government Regulatory Authority for SIP trunking services in the UAE, which makes them the required foundation for business telephony that needs TRA-licensed connectivity, as explained in Cloud Call Center’s overview of Etisalat SIP trunking in the UAE.

What that means in real business terms

This isn’t a minor legal detail. It affects every serious deployment:

External calling compliance means your inbound and outbound PSTN traffic must sit on authorised local carrier infrastructure.
UAE DDI retention matters because most companies want to keep existing published numbers and map them into new platforms.
Platform flexibility depends on the carrier layer staying stable while you change the application layer above it.

That’s why a business can keep existing numbers on Etisalat or du SIP trunks and connect them into systems such as Teams Direct Routing, Zoom Phone BYOC, Xcally, or CRM-linked telephony workflows.

The rule most buyers learn too late

A lot of businesses compare cloud phone vendors as if the UAE works like a fully open telephony market. It doesn’t. Your software choice is broad. Your PSTN carrier choice is not.

If your project needs UAE business numbers for public calling, Du or Etisalat isn’t a preference. It’s the starting condition.

That reality simplifies decision-making. You’re not trying to choose from a dozen carriers. You’re making a focused strategic choice between two approved connectivity foundations, then deciding how to integrate them into your wider voice stack.

Key Technical Requirements for Flawless Voice Quality

Poor SIP deployments rarely fail because the idea was wrong. They fail because the setup was casual. Voice traffic is unforgiving. If your network, codec, or signalling choices are sloppy, users hear it immediately.

For DU-based deployments, one point is clear. For optimal voice quality and interoperability, DU SIP trunk configurations prioritise the G711 (PCMA) codec and RFC2833 for DTMF, and mismatches in codec or DTMF handling are a known cause of one-way audio or dropped calls, as discussed in this DU SIP trunk configuration thread.

The three technical checks that matter most

Dedicated voice path

Don’t dump voice onto an overloaded data link and hope QoS will save you. SIP trunks perform best when voice has a predictable path and enough clean bandwidth. If your WAN is unstable, your telephony will be unstable.

Codec discipline

G.711 PCMA remains the practical standard in these deployments because it prioritises compatibility and call clarity. The mistake isn’t using the wrong codec occasionally. The mistake is letting different parts of the stack negotiate inconsistently.

DTMF handling

If IVRs, auto attendants, payment flows, or menu systems matter to your business, DTMF has to work every time. RFC2833 is a common requirement for exactly that reason.

Engineer’s view: When users report “the call connected but the menu didn’t respond” or “audio works one way only”, I check codec and DTMF handling before anything else.

Questions you should ask your provider or implementation partner

Use this checklist in plain language:

Voice separation: How are you isolating voice traffic from general office data?
Codec policy: Are you standardising on G.711 PCMA end to end where required?
DTMF method: Are you explicitly configuring RFC2833 where the trunk and platform expect it?
Interoperability testing: Have you tested with the actual PBX, SBC, Teams, Zoom, 3CX, or Yeastar environment we’ll use?
Failure handling: What happens when the primary route degrades or the PBX loses registration?

What good looks like

Good voice quality isn’t mysterious. Calls connect fast. Audio is clear in both directions. IVR inputs work. Transfers don’t break. Users stop complaining because the system behaves predictably.

That’s the standard you should demand. Not “mostly fine”. Not “usually okay”. Predictable.

Etisalat vs Du A Strategic Comparison for 2026

If you’re choosing between the two authorised carriers, stop looking for a mythical winner. There isn’t one. There’s a better fit for your environment, your budget, and your operating style.

The comparison most buyers need is simple: cost, reliability, and how much implementation friction you’re willing to tolerate.

A useful companion if you’re evaluating the DU route specifically is this overview of a DU SIP trunk for business telephony.

The numbers that matter

The strongest direct comparison available is this: industry quotes suggest Etisalat channels cost AED 150 to 250 per month versus DU’s AED 120 to 200, and 2025 TRA reports indicated SIP trunk downtime averages of 2.1% for Etisalat versus 1.4% for DU in enterprise deployments, according to the discussion referencing those figures in the Asterisk community thread on Etisalat SIP behaviour.

That doesn’t mean DU wins every project. It means price-sensitive buyers and teams benchmarking downtime should take DU seriously instead of assuming Etisalat is automatically the enterprise default.

Side-by-side decision view

Decision factor	Etisalat	Du
Commercial positioning	Often treated as the premium option	Commonly chosen for cost-effectiveness
Typical channel pricing	Higher quoted range	Lower quoted range
Enterprise perception	Favoured by some organisations with stricter security and procurement preferences	Favoured by many teams balancing cost and scale
Operational fit	Works well when the business prioritises established carrier relationships	Works well when the business wants efficient scaling and sharper cost control

Here’s the practical reading of that table. If procurement, internal governance, or legacy carrier relationships strongly favour Etisalat, you may accept a higher cost profile. If you’re building a contact centre or distributed calling environment and finance is watching channel costs closely, DU often makes the harder-to-ignore case.

A short explainer on the wider business telephony environment helps frame the carrier decision before you lock the architecture in:

My recommendation

Use this rule set:

Choose Du when cost control, solid reliability, and scalable SIP capacity matter most.
Choose Etisalat when your organisation already standardises on Etisalat services or your governance model strongly prefers that relationship.
Avoid indecision. Delaying the carrier decision slows every downstream task, from SBC design to user cutover planning.

Buy based on operating reality, not brand comfort. The wrong carrier fit creates friction every month. The right one disappears into the background and just carries calls.

Integrating Your SIP Trunk with Teams and Zoom

Once the carrier layer is decided, the rest becomes straightforward. Your SIP trunk from Du Etisalat connects public calling into the collaboration tools your staff use. That’s the whole point. Users don’t care about trunking terminology. They care that their UAE business number rings inside Teams or Zoom, whether they’re in DIFC, JLT, Abu Dhabi, or working remotely.

How the call path actually works

For Microsoft Teams Direct Routing, the flow is simple in concept:

A customer dials your UAE number.
The call enters through your du or Etisalat SIP trunk.
A Session Border Controller handles routing and policy.
Teams delivers the call to the user, queue, or auto attendant.

The same principle applies to Zoom Phone BYOC. You keep the carrier relationship and number ownership on the SIP side, then extend calling into Zoom through the approved integration model.

For organisations mapping voice into CRM, ticketing, and digital channels, broader system integrations are often part of the same design conversation, especially when voice events need to trigger workflows in platforms like Dynamics 365 or Salesforce.

What a clean integration looks like

A well-built deployment should give you:

Single number identity so staff use one business number across devices
Consistent inbound routing for users, hunt groups, IVRs, and queues
Outbound presentation control so calls show the right CLI
Platform flexibility to move from PBX to Teams or Zoom without rebuilding the carrier base

If you’re planning a Microsoft environment, this guide to Microsoft Teams Voice in the UAE is the practical next read.

The carrier should stay boring. The user experience should feel modern. That’s a good deployment.

Where projects usually become messy

They become messy when teams buy licences first and design call routing second. Or when they treat the SBC as a box-ticking exercise instead of the control point between carrier and collaboration platform.

If you want Teams or Zoom to behave like a serious business phone system, build the call path properly from the trunk upward.

Choosing Your Deployment Model and Best Practices

The carrier is only half the design. The other half is where the voice platform lives and how resilient you want it to be. For most UAE businesses, the primary choice isn’t “PBX or no PBX”. It’s cloud, on-premise, or hybrid.

Which model fits which business

Cloud

Best for organisations that want faster rollout, less onsite infrastructure, and easier support for remote users. It suits many SMBs and distributed teams.

On-premise

Useful when the business has strict internal control requirements, existing data centre investments, or specialised local integrations that are easier to manage onsite.

Hybrid

Often the smartest option for enterprises. It balances local control with cloud flexibility, especially when contact centre functions, recording policies, or business continuity rules differ across departments.

The non-negotiable best practices

Don’t focus only on go-live. Build for failure, growth, and maintenance.

Redundancy first: Trunks, SBCs, and routing paths should fail over cleanly.
Separate critical functions: Don’t let telephony depend on the same weak point as a congested office LAN.
Plan expansion early: Add users, numbers, queues, and locations without redesigning the whole environment.
Test cutover scenarios: Day-one success means little if failover hasn’t been proven.

A real-world reference matters here. In an example of scalable and redundant architecture, Etisalat deployed a Managed SIP Trunk Service for Dubai Media Incorporated with 14 logical SIP trunks configured in Active/Standby mode. That detail comes from the earlier Etisalat reference already noted above.

Resilience isn’t a luxury feature. If voice supports sales, service, or emergency workflows, resilience is part of the design brief.

My position on architecture

For most mid-size and enterprise projects in the UAE, hybrid wins. It gives you cleaner migration paths, better control over integrations, and a more sensible route to continuity planning. Pure cloud can work well. Pure on-premise can work well. But hybrid usually gives the fewest regrets once the business starts changing.

If your phone system has to survive office moves, mergers, policy changes, and contact centre growth, design it to bend without breaking.

Making the Right Choice for Your UAE Enterprise

The core decision isn’t whether SIP trunking matters. It does. The decision is which carrier fit and deployment model will give your business the least friction over the next few years.

Choose Du when cost discipline and efficient scaling are the top priorities. Choose Etisalat when your organisation is already aligned to that carrier relationship or wants that specific operating model. In both cases, don’t treat the trunk as a commodity. It shapes compliance, call quality, platform integration, and business continuity.

The smartest projects in the UAE take a simple approach. Pick the carrier based on commercial and operational fit. Build the voice path properly. Integrate it into Teams, Zoom, PBX, or contact centre platforms only after the foundations are stable.

If you need an implementation partner to handle the carrier side, SBC design, and platform integration, Cloud Move is one local option that works across Etisalat and DU environments for Teams Voice, cloud PBX, and contact centre deployments.

Frequently Asked Questions

Question	Answer
Can I use an international SIP provider for UAE business numbers?	For public calling on UAE business numbers, your compliant carrier foundation must align with the authorised local model. In practice, that means working through Du or Etisalat for the PSTN layer.
Do I need to replace all my phones to use a SIP trunk?	Not always. Many businesses keep parts of their existing setup and connect the SIP trunk into an IP-PBX, SBC, Teams, or Zoom environment. The answer depends on your current telephony stack.
Can I keep my existing DDI numbers?	Yes, businesses can retain existing DDI numbers on Etisalat or du SIP trunks and map them into supported calling platforms, as noted earlier.
How do I know how many channels I need?	Start with actual concurrent call demand, not total headcount. Sales teams, service desks, reception groups, and contact centres need different channel planning logic. If you guess, you’ll either overspend or create busy-hour failures.
Is cloud always better than on-premise?	No. Cloud is often easier to roll out, but hybrid or on-premise can be the better choice when control, local integration, or continuity requirements are stricter.
What causes one-way audio or IVR keypress issues?	Codec and DTMF mismatches are common causes. That’s why consistent voice settings and proper interoperability testing matter.

If you're planning a SIP trunk from Du Etisalat and want a compliant design that works with Teams, Zoom, PBX, or contact centre platforms, speak with Cloud Move for a free demo or consultation. They can help assess carrier fit, deployment model, and integration requirements before you commit to the wrong architecture.