|
Using TCP Sip would only solve half the problem (and couse some more).
Answers to request could still end up at the wrong server (but one would
only have to write a module for that, and not a kudpvs) and not all
clients support TCP based sip.
Christen R. Pacheco wrote:
SIP Express Router supports TCP SIP.
-----Original Message-----
From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Erik
Versaevel
Sent: Thursday, January 13, 2005 5:21 AM
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Looking for ktcpvs but not quite
Hello,
I'm currently trying to create a loadbalacing SIP (voip protocol)
cluster, however for this to work I need SIP messages from the same call
(identifiable by the sip callid field) to get to the same realserver
over and over again. (so, I need persistence based on the contents of
the SIP Call-ID field). This would call for ktcpvs as we need to process
packets at layer 7, however that poses 2 new problems, the first is that
SIP uses clear text UDP messages, not tcp and the second is that there
are no SIP modules for ktcpvs.
Another option would be to mark SIP packets with iptables/netfilter
based on the callid, however i run into the same problem, there are no
modules to accomplish this.
I know that there are commercial products available who are able to do
SIP session persistence based on callid, the F5 Big-IP for example, the
downside of that is it costs around $ 10.000 for a single loadbalancer
(which is a SPOF so you need 2) and is a bit overkill as i don't need
multi gigabit loadbalancing.
Any thoughts on this?
Kind regards,
E. Versaevel
|
