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.The FQDN feature on a plain SIP trunk isn’t self-service — request it by emailing support@easybell.de. It costs roughly €10/month and can take several days to activate, so ask for it before you plan a go-live date. 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. Cloud PBX delivery does not necessarily come from the direct-trunk networks below. A separate candidate list has been reported for Cloud PBX Pro signaling — 62.144.211.104, 195.52.221.134, 195.52.221.137 — but it is unverified: treat it as a starting point, and confirm the current Cloud PBX signaling sources with Easybell or from a verified SIP trace before saving them as a production 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.
