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

# Easybell SIP trunk

> Route an Easybell DID to the platform with FQDN and source-IP authentication

## Recommended profile

| Setting                         | Value                                                                  |
| ------------------------------- | ---------------------------------------------------------------------- |
| Easybell destination            | The platform SIP FQDN                                                  |
| Platform inbound authentication | **Provider source IPs**; do not enable digest for this forwarding path |
| Number                          | Exact DID in `+E.164`                                                  |
| Transport                       | TCP where possible; TLS only with the TLS-specific source list         |

Easybell treats username/password registration, Trusted IP, and Trusted FQDN as different connection modes. For inbound FQDN delivery, point Easybell to the platform SIP FQDN, then authenticate the incoming traffic on the platform by source address.

## Choose the Easybell path

### Direct Easybell SIP trunk

Make sure the FQDN connection is enabled for the Easybell product. Configure the platform SIP FQDN as the trusted destination without a `sip:` prefix, send the DID in `+E.164`, and use the source list that matches the selected transport.

### Easybell Cloud PBX

In the Easybell Cloud PBX, create a **Resource** of type **FQDN**, assign the public number, and enter the platform SIP URI under **Call handling → Forwarding → FQDN** without the `sip:` prefix. Do not assume that the direct-trunk source list below also covers Cloud PBX delivery; confirm the current Cloud PBX signaling sources with Easybell or from a verified SIP trace before saving the platform allowlist.

Cloud PBX Pro can allow the connected service to transfer a call back to an internal extension. Enable forwarding on the FQDN resource and use a SIP target such as `200@easybell`. Easybell documents this as internal-only; it does not permit forwarding through that resource to an external PSTN number.

## Official Easybell networks

For UDP/TCP, Easybell publishes:

```text theme={null}
195.185.187.0/27
195.52.221.128/27
```

For TLS, Easybell publishes:

```text theme={null}
195.185.187.0/27
212.172.204.95/32
212.172.58.207/32
```

Choose the list that matches the transport configured at Easybell. These are signaling sources for the receiving system, not outbound platform addresses.

## Famulor-observed addresses

The following exact sources were observed in a successful Easybell delivery on 22 August 2026:

```text theme={null}
195.52.221.151/32
195.185.214.173/32
195.52.221.142/32
212.172.204.95/32
212.172.58.207/32
```

This is operational evidence, **not an official global Easybell list**. Two addresses fall inside Easybell's published `195.52.221.128/27`, two are published TLS hosts, and `195.185.214.173` is not in the published networks above. Do not copy the additional host blindly: confirm it in the current Easybell account/support response or a verified SIP trace first.

## Validate

Save the exact DID and source addresses, assign the number to an assistant, and call it externally. Confirm a new inbound call, the correct assistant, and two-way audio in **Calls**.

Sources: [Easybell FQDN authentication](https://www.easybell.de/hilfe/fragen/fragen-zum-telefonanschluss/antwort/sip-trunk-authentifizierung-per-fqdn-domain-einrichten/), [Easybell Cloud PBX FQDN resource](https://www.easybell.de/hilfe/cloud-telefonanlage/antwort/fqdn-anbindung-ki-dienste-in-die-cloud-telefonanlage-integrieren-1/), [Easybell Trusted IP](https://www.easybell.de/hilfe/fragen/fragen-zum-telefonanschluss/antwort/trusted-ip-bei-sip-trunks-einrichten/). Accessed 22 August 2026.