[Spce-user] Easybell Peering on MR13.5 CE: Split-Horizon (DNS vs Inbound) & Upgrade-safe Header Manipulation

[Atilla Ceylan]

Hi everyone,

I am setting up a Sipwise CE MR13.5.1 system with Easybell (Germany) and facing specific configuration challenges regarding their "Split Horizon" infrastructure.

We are looking for advice on the best practice / upgrade-safe way to solve these in the CE version, as we want to avoid modifying the raw Kamailio templates (kamailio.cfg.tt2).

1. Connectivity: DNS & Inbound Matching As discussed in various VoIP user groups (e.g., IP-Phone-Forum), Easybell uses a redundant setup where the main proxy sip.easybell.com resolves via SRV/A records to specific gateways (e.g., a.sip.easybell.com at 195.185.214.173 and b.sip.easybell.com at 195.52.221.142).

Outbound: We handle this by setting the Peer Host to sip.easybell.com. LCR resolves this correctly.

Inbound Question: When calls come in from Easybell, they originate from one of these specific IPs (195.x.x.x).

Does Sipwise CE automatically resolve the configured Peer Hostname (sip.easybell.com) and add the resulting A-record IPs to the trusted permissions table for inbound matching?

Or is it required to manually add the specific IPs (195...) as additional Peer Servers to ensure inbound calls are correctly matched to this Peering Group?


2. Identity: From-Header Mismatch & Upgrade Safety Regardless of the connection domain (.com), Easybell strictly requires the From-Header and Auth Realm to be sip.easybell.de.

If we connect to sip.easybell.com, Sipwise defaults to sending the local domain user at sip.local.domain or the connection domain user at sip.easybell.com in the From-Header.

Easybell rejects this (403/407 loop) because it expects <user at sip.easybell.de>.

The Missing Feature in MR13.5 CE: This "Split Horizon" requirement is well-known in the Kamailio community and typically solved using uac_replace_from(). In previous Sipwise versions (or PRO), this was handled via the outbound_from_domain preference or Header Rule Sets.

However, these options appear to be hidden/removed in the CE MR13.5 GUI.

My Question: What is the recommended, upgrade-safe method in Sipwise CE to force the From-Domain to sip.easybell.de?

Is there a specific "custom hook" or configuration file intended for this type of header manipulation in the modern CE architecture that survives system upgrades?


Thanks for your support!

Best regards, Atilla
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20260113/8d01ffe0/attachment.htm>