Skip to main content
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:
For TLS, Easybell publishes:
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:
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, Easybell Cloud PBX FQDN resource, Easybell Trusted IP. Accessed 22 August 2026.