12 Mar
2013
12 Mar
'13
9:29 a.m.
Hi, What would be the community's architecture advice for deploying Kamailio in a high
availability environment? I am looking for something simple, still efficient. Thanks,
12 Mar
12 Mar
9:34 a.m.
Use multiple kamailio's, access them over sip-srv (that will give you high
availability) , and checkout cassandra if you need db-connectivity ;)
That should be imho the simplest and oh boy efficient :)
On 12 Mar 2013, at 10:29, Moacir Ferreira wrote:
Hi,
What would be the community's architecture advice for deploying Kamailio in a high
availability environment? I am looking for something simple, still efficient.
Thanks,
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
6:36 p.m.
The limitation is when the client phone is not srv aware. But anyway, for sure this would
be the best solution. So, if I understood, we install 2 servers (let's say server A
and server B) and both use the same SQL server/database and we create 2 sip-srv's in
our DNS, done. Is this?
Now, devices that run over batteries will usually use SIP over TCP to save power, making
it possible to send few keep alive. What happens if a client was registered on server A
and this server fails? Will every client, when trying to make a call, switch from server A
to server B based on the sip-srv record? Just by having access to the same SQL database
will server B be able to call (locate) a client that was registered initially on server A?
Thanks, MoacirFrom: davy.van.de.moere(a)gmail.com
Date: Tue, 12 Mar 2013 10:34:58 +0100
To: sr-users(a)lists.sip-router.org
Subject: Re: [SR-Users] High availability
Use multiple kamailio's, access them over sip-srv (that will give you high
availability) , and checkout cassandra if you need db-connectivity ;)
That should be imho the simplest and oh boy efficient :)
On 12 Mar 2013, at 10:29, Moacir Ferreira wrote:Hi,
What would be the community's architecture advice for deploying Kamailio in a high
availability environment? I am looking for something simple, still efficient.
Thanks,
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
7:52 p.m.
Yes, srv record for both. You can control where the requests go using priority/weights.
The location(registration) records are stored in the database, so the registrations are
not bound to a specific server.
For high availability I have had good luck with corosync / pacemaker combination for
kamailio high availability. While this is certainly more complex than using srv records,
it is another possibility. I use a combination of both. I have also had good luck using
corosync / pacemaker /drbd combination for database availability.
-Dan
From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org]
On Behalf Of Moacir Ferreira
Sent: Tuesday, March 12, 2013 2:36 PM
To: Kamailio Mail List
Subject: Re: [SR-Users] High availability
The limitation is when the client phone is not srv aware. But anyway, for sure this would
be the best solution. So, if I understood, we install 2 servers (let's say server A
and server B) and both use the same SQL server/database and we create 2 sip-srv's in
our DNS, done. Is this?
Now, devices that run over batteries will usually use SIP over TCP to save power, making
it possible to send few keep alive. What happens if a client was registered on server A
and this server fails? Will every client, when trying to make a call, switch from server A
to server B based on the sip-srv record? Just by having access to the same SQL database
will server B be able to call (locate) a client that was registered initially on server
A?
Thanks,
Moacir
________________________________
From: davy.van.de.moere@gmail.com<mailto:davy.van.de.moere@gmail.com>
Date: Tue, 12 Mar 2013 10:34:58 +0100
To: sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
Subject: Re: [SR-Users] High availability
Use multiple kamailio's, access them over sip-srv (that will give you high
availability) , and checkout cassandra if you need db-connectivity ;)
That should be imho the simplest and oh boy efficient :)
On 12 Mar 2013, at 10:29, Moacir Ferreira wrote:
Hi,
What would be the community's architecture advice for deploying Kamailio in a high
availability environment? I am looking for something simple, still efficient.
Thanks,
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________ SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
4110
days inactive
4110
days old
3 comments
3 participants
participants (3)
-
Daniel W. Graham -
davy van de moere -
Moacir Ferreira