> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voice.wixzel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mobily SIP trunk: setup for Wixzel Voice

> Connect a Mobily SIP Trunk in Saudi Arabia to Wixzel Voice for AI phone calls: your SBC on the Mobily link, the platform IP, G.711 A-law and the inbound route.

Agents you build on Wixzel Voice place and answer phone calls over a SIP trunk
you bring, and Mobily SIP Trunk, in Saudi Arabia, is one that works with it.
Mobily bills you for the trunk and the minutes at your own rates; the voice
engine is billed per second of actual usage from your Wixzel Voice balance. This
page covers what is different about Mobily. The steps that are the same for
every carrier, and the troubleshooting list, are on [SIP trunks](https://docs.voice.wixzel.com/sip-trunks.md).

> [!NOTE]
>
> Allowlist **`187.126.120.231`** for outbound calls, and send inbound calls to
> **`sip:187.126.120.231:5090`**. Every trunk returns both as `platform_ip` and
> `origination_uri`, so read them from `GET /v1/sip-trunks` rather than trusting
> this page to stay current.

> [!WARNING]
>
> No Mobily trunk has been tested end to end with Wixzel Voice yet. These settings
> come from Cisco's 2020 interop note for Mobily SIP Trunk, so ask Mobily to
> confirm them for your link.

## How do I connect a Mobily SIP trunk to Wixzel Voice?

Mobily has no API for trunks or numbers, so there is no one-step connect in the
console. Mobily also delivers the trunk over a private link to your site, so
the platform cannot reach Mobily directly: an SBC or PBX of yours on that link
relays the calls.

**1. Order SIP Trunk from Mobily Business**

Mobily sells SIP Trunk to businesses in Saudi Arabia through its sales
team: call 901 from a Mobily Business line or email
[DigitalSalesB2B@mobily.com.sa](mailto:DigitalSalesB2B@mobily.com.sa). Your numbers come with the trunk or are
ported to it.

**2. Put an SBC with a public IP on the Mobily link**

Mobily trusts your side of the link by IP, without SIP REGISTER. The SBC
sits on that link and also has a public IP the platform can reach.

**3. Trust the platform and route both ways**

On the SBC, trust **`187.126.120.231`** and route inbound Mobily calls to
the `origination_uri` your trunk returns. Calls from the platform go out to
Mobily with numbers in the `966…` form. Use G.711 A-law and RFC 2833 DTMF on
the Mobily side.

**4. Add the trunk in Wixzel Voice**

Create the trunk with your SBC's public IP as `host`, `transport: "udp"` and
`send_plus: false`. Put "Mobily" in its name so the console shows the Mobily
mark.

## What goes wrong on Mobily?

* Mobily cuts calls, inbound and outbound, at one hour. A long call that drops
  at exactly 60 minutes is the carrier, not the agent.
* Calls arriving from Mobily offer G.711 A-law and never G.729. An SBC that only
  allows G.729 toward Mobily fails every inbound call.
* A re-INVITE that puts the call on hold (`sendonly` or `inactive`) can drop the
  call on Mobily. Have the SBC rewrite it to `sendrecv`.

## What if a Mobily call does not connect?

Work through [When a call does not connect](https://docs.voice.wixzel.com/sip-trunks.md#when-a-call-does-not-connect),
and start with your SBC's logs: they show whether the call reached the SBC from
each side and which side cleared it.

## Related

* [SIP trunks](https://docs.voice.wixzel.com/sip-trunks.md): the allowlist, the inbound address and the
  troubleshooting list that apply to every carrier.
* [Quickstart](https://docs.voice.wixzel.com/quickstart.md): connect the trunk, register a number, create an
  agent and place a first call.
* [Mobily SIP trunk setup](https://voice.wixzel.com/carriers/mobily): the short
  version on the Wixzel Voice site, with what a minute costs on each voice
  engine.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.