Hello. We use 2 kamailio server 4.3 master brancher for load balansing cluster. We have some problems with this deplooiment
fist of all we have REgstering issue: Witth one server all works fine (we have some endpoints with same creditians) all endpoints reinging well. But at 2 servers we hawe problem with this- call ringing only at one endpoint. We use Database for USRLOC module
modparam("usrloc", "db_url", DBURL) modparam("usrloc", "db_mode", 3) modparam("usrloc", "use_domain", MULTIDOMAIN)
As i think it mean al connections to servers ives at database. We have one database for 2 servers and this is means it only one table LOCATION for its.
The second problen id that when loadbalanser sends bye to kamailio from the outside- bye is not recieves to endpoint. It say that no transaction with this CallID. I think it is because transaction goues through another kamailio and kamiaio that recieves BYE does not know about it transaction.
So my first qestion- Does anybody have some information about loafd balansiong between kamailios?
And second question - how to resolve issue with LOCATION table?
Thanks
Hi, Yuriy Gorlichenko!
So my first qestion- Does anybody have some information about loafd balansiong between kamailios?
We use failover such way:
2 K. servers with 1 shared IP (CARP) and all actions replicate via DMQ. This way usable for load balancing too.
And second question - how to resolve issue with LOCATION table?
I think shared database wrong way, right way - DMQ replication.
-- WBR, Victor JID: coyote@bryansktel.ru I use FREE operation system: 3.18.5-calculate GNU/Linux up 3 days, 16 hours, 11 minutes
Victor V. Kustov writes:
We use failover such way:
2 K. servers with 1 shared IP (CARP) and all actions replicate via DMQ. This way usable for load balancing too.
by all actions, to do you mean also transaction state so that reply to a request can come to different server than the one that set the request?
-- juha
We solved this issue with another way because enpoints can registar at only one kam (at location table we see socket field). So we need not register at both servers one endpoint- wee ned call all servers for calling endpoints with same username from both servers. This philosophy right for load balansers.
2015-02-03 22:30 GMT+03:00 Juha Heinanen jh@tutpro.com:
Victor V. Kustov writes:
We use failover such way:
2 K. servers with 1 shared IP (CARP) and all actions replicate via DMQ. This way usable for load balancing too.
by all actions, to do you mean also transaction state so that reply to a request can come to different server than the one that set the request?
-- juha
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Juha Heinanen -
Victor V. Kustov -
Yuriy Gorlichenko