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

Before you start, open Settings → Phone numbers → Add a number → Add SIP integration in Famulor, choose the SIP region and copy the hostname from the SIP URI.
  1. Ask Easybell support to activate Trusted FQDN if it is unavailable for your number.
  2. In my.easybell, open Phone functions → Manage numbers. Open the settings for the trunk number and choose Trusted IP → Domain (FQDN). Enter the Famulor hostname without the sip: prefix and choose TCP, or TLS for encrypted signaling. Set Incoming Number Signaling to E.164 with +.
  3. In Famulor, enter the exact DID and configure Provider source IPs with the Easybell networks below for your transport. If you also place calls through Easybell, follow the outbound SIP identity settings below.
Easybell Trusted IP settings with the FQDN option and hostname field

Select Domain (FQDN) in the Trusted IP settings for your Easybell trunk.

What to enter in Famulor

The screenshots use the English app labels.
Incoming calls in Famulor

Incoming calls in Famulor

  • Your phone number (DID) · Enter the exact number delivered by Easybell, with its country code and leading + for an E.164 DID.
  • Inbound authentication / Allowed source IPs · Choose Provider source IPs and enter the complete SIP signaling list for Easybell and the selected route.
Example in the English app

Example in the English app

Use your own number, provider settings and SIP login. The password field is blank in the example.
  • Termination address · Use the provider hostname from the setup above (voip.easybell.de). Enter only the hostname, without a SIP prefix or port.
  • Outbound authentication / SIP username / SIP password · Select Username / password when using Digest. Enter the SIP login and password from SIP.
  • Only configure this direction when your provider has confirmed and provisioned it.

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.

Transferring calls

Cold transfer uses SIP REFER through the provider of the current call. Confirm that your exact Easybell product supports the intended destination. A 405 response means the method was rejected; changing the phone-number format does not enable REFER. For a new outgoing connection, use Warm Transfer and select the Outbound phone number to use. This can be a platform number even when the incoming call uses Easybell. If you select Easybell for the outgoing leg, its outbound authentication must work first.

Validate the setup

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 History. Sources: Easybell FQDN authentication, Easybell Cloud PBX FQDN resource, Easybell Trusted IP. Accessed 22 August 2026.

Outbound SIP identity

Easybell requires the SIP authentication username in the outbound From user. If it differs from your public phone number, choose SIP username under Outbound SIP identity. Keep Phone number (DID) and your public number. Match Caller ID source to the field selected in the Easybell caller ID settings. Do not replace the DID with the username or add a custom From header. Easybell SIP authentication · Easybell caller ID settings