In theory, you could use a FWM (firewall mark) setup and persistent connections. If you map the virtual server group to use the same FWM for the TCP ( SIP uses TCP port 5060) and UDP (RTP usually is configured for UDP ports 16384-32767) datastreams. It should work in theory.
However, the application-based Load-balancing in Asterisk does function fairly well and you might end up with a better solution. Typically, with load-balancing I find that the more complexity you add just makes it that much harder to debug when things go awry. -- Morgan Fainberg Systems Architect (mt) Media Temple, Inc http://www.mediatemple.net/ On May 16, 2008, at 12:52 PM, Gerry Reno wrote: > Graeme Fowler wrote: >> You could definitely sort out the main ports - TCP & UDP port 5060 - >> trivially; but the follow-on complication is how you then track the >> session traffic which can wander around all over the place (cf. the >> LVS >> FTP helper). >> >> I'd strongly recommend you have a good read of the Asterisk mailing >> list >> - it seems that there are several app-based load balancing schemes >> for >> Asterisk, and if they do what you need, I'd use them. >> >> > I had seen several references where people had said they had done this > with lvs so that is what gave me the idea. But maybe this is a case > where an app-based LB scheme might be best. > > Regards, > Gerry > > > _______________________________________________ > LinuxVirtualServer.org mailing list - [email protected] > Send requests to [EMAIL PROTECTED] > or go to http://lists.graemef.net/mailman/listinfo/lvs-users _______________________________________________ LinuxVirtualServer.org mailing list - [email protected] Send requests to [EMAIL PROTECTED] or go to http://lists.graemef.net/mailman/listinfo/lvs-users
