Enterprise-grade SIP trunks designed for Kamailio SBC and proxy deployments. LCR routing support, dispatcher integration, and engineers who understand Kamailio scripting.
Integrate with lcr module for cost-based routing
Ready-to-use kamailio.cfg snippets
Load balancing across our gateways
Full encryption support
Configure Kamailio to route calls through IPComms
Add to your kamailio.cfg or modparam section:
#!define IPCOMMS_GW "sip.ipcomms.net"
#!define IPCOMMS_USER "YOUR_USERNAME"
#!define IPCOMMS_PASS "YOUR_PASSWORD"
loadmodule "uac.so"
modparam("uac", "credential", "IPCOMMS_USER:sip.ipcomms.net:IPCOMMS_PASS")Add route for PSTN calls:
route[TO_PSTN] {
$du = "sip:" + IPCOMMS_GW + ":5060";
# Add authentication header
uac_auth();
# Forward to IPComms
t_relay();
exit;
}For high-availability with multiple gateways:
loadmodule "dispatcher.so"
modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list")
# dispatcher.list content:
# 1 sip:sip.ipcomms.net:5060 0 0 weight=100Accept calls from IPComms:
route[FROM_PSTN] {
# Verify source is IPComms
if ($si != "sip.ipcomms.net") {
sl_send_reply("403", "Forbidden");
exit;
}
# Route to internal destination
route(RELAY);
}Run kamctl restart and verify with kamcmd dispatcher.list
Built for high-volume deployments.
Predictable costs for steady volume
No monthly fees, just usage
We support Kamailio 5.x and newer. Our SIP implementation follows RFC 3261 standards.
Yes! We can whitelist your Kamailio server IPs for authentication without credentials.
Absolutely. Our platform works well with topoh and other SBC modules.
Fully supported. Our media servers work seamlessly with rtpengine-based setups.
Get your SIP credentials in minutes. Enterprise-grade support for Kamailio deployments.