Dear All,
I have seen in the new kamailio release 5.3.0, kamailio support for haproxy protocol – both the v1 (human-readable) and v2 (binary) versions of the protocol are supported ( https://www.kamailio.org/w/kamailio-v5-3-0-release-notes/%C2%A0) but it seems to be for Database, webserver failover not for kamailio itself. Haproxy is ONLY supporting TCP but not UDP.
My question is :
I am looking for failover service of kamailio servers looks like haproxy but udp & tcp.
- one domain name : sip.secure.com pointing my public ip address. - two kamailio server pointing same database content (user, whitelist, ...) no asterisk or pbx. Kamailio is used Only for signaling (users, whitelist & rtp)
Monitoring service : identify who is the kamailio server online, offline and the ability to force all the SIP/RTP/MANAGEMENT connection from Kamailio Srv1 to Kamailio Srv2 and vice-versa ?
Thanks for your suggestions.
-- Youssef
Hello,
it is for SIP over TCP/TLS.
Check the next link to see if the ha solution described there suits your needs:
- https://www.kamailio.org/w/2015/11/kamailio-ha-with-ansible-corosync-and-pac...
Cheers, Daniel
On 28.10.19 06:03, Youssef Boujraf wrote:
Dear All,
I have seen in the new kamailio release 5.3.0, kamailio support for haproxy protocol – both the v1 (human-readable) and v2 (binary) versions of the protocol are supported ( https://www.kamailio.org/w/kamailio-v5-3-0-release-notes/%C2%A0) but it seems to be for Database, webserver failover not for kamailio itself. Haproxy is ONLY supporting TCP but not UDP.
My question is :
I am looking for failover service of kamailio servers looks like haproxy but udp & tcp.
- one domain name : sip.secure.com pointing my public ip address.
- two kamailio server pointing same database content (user, whitelist,
...) no asterisk or pbx. Kamailio is used Only for signaling (users, whitelist & rtp)
Monitoring service : identify who is the kamailio server online, offline and the ability to force all the SIP/RTP/MANAGEMENT connection from Kamailio Srv1 to Kamailio Srv2 and vice-versa ?
Thanks for your suggestions.
-- *Youssef *
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
On Mon, Oct 28, 2019 at 06:03:09AM +0100, Youssef Boujraf wrote:
I am looking for failover service of kamailio servers looks like haproxy but udp & tcp.
-??one domain name : sip.secure.com pointing my public ip address.
- two kamailio server pointing same database content (user, whitelist,
...) no asterisk or pbx. Kamailio is used Only for signaling (users, whitelist & rtp)
Monitoring service : identify who is the kamailio server online, offline and the ability to force??all the SIP/RTP/MANAGEMENT connection from Kamailio Srv1 to Kamailio Srv2 and vice-versa ?
Why do these kind of failover setups at all? When I create these failover setups they work perfectly during tests but fail during real failures. With round robin A records, NAPTR and SRV you can have multiple live servers. Only the endpoints what actually use a hardcoded ipaddress will have problems in the case of a failure.
The added benefit is scalability and easy maintenance.
The bad is there isn't a wiki entry on how to do it AFAIK.
BTW the shared database seems to be a bit deprecated (and a common point of failure), look at DMQ if you have to start from scratch.
Hi Daniel,
In an ideal world, DNS is, as you said, the easiest of approaches one can think of. However, not all endpoints support [properly] SRV failover. Take for example Asterisk's chan_sip. Is does resolve the hostname by SRV, however the failover is proven/accepted as broken.
https://stackoverflow.com/questions/41487243/dns-srv-failover-not-working-in...
Cheers, --Sergiu
On Mon, Oct 28, 2019 at 8:38 AM Daniel Tryba d.tryba@pocos.nl wrote:
On Mon, Oct 28, 2019 at 06:03:09AM +0100, Youssef Boujraf wrote:
I am looking for failover service of kamailio servers looks like haproxy but udp & tcp.
-??one domain name : sip.secure.com pointing my public ip address.
- two kamailio server pointing same database content (user, whitelist,
...) no asterisk or pbx. Kamailio is used Only for signaling (users, whitelist & rtp)
Monitoring service : identify who is the kamailio server online, offline and the ability to force??all the SIP/RTP/MANAGEMENT connection from Kamailio Srv1 to Kamailio Srv2 and vice-versa ?
Why do these kind of failover setups at all? When I create these failover setups they work perfectly during tests but fail during real failures. With round robin A records, NAPTR and SRV you can have multiple live servers. Only the endpoints what actually use a hardcoded ipaddress will have problems in the case of a failure.
The added benefit is scalability and easy maintenance.
The bad is there isn't a wiki entry on how to do it AFAIK.
BTW the shared database seems to be a bit deprecated (and a common point of failure), look at DMQ if you have to start from scratch.
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
On Tue, Oct 29, 2019 at 11:24:34AM -0400, Sergiu Pojoga wrote:
Hi Daniel,
In an ideal world, DNS is, as you said, the easiest of approaches one can think of. However, not all endpoints support [properly] SRV failover.
And that is why you do both. Both a hot standby and multiple active frontends.
BTW I hate the hot standby keepalive/heartbeat/whatever solutions. They work perfectly during testing, they fail in production. But luckily a static kamailio.cfg itself (just playing a proxy) is very stable.
-
Daniel Tryba -
Daniel-Constantin Mierla -
Sergiu Pojoga -
Youssef Boujraf