Hi Andreas,

you can distribute load amongst several instances of WeSIPs using OpenSER scripts but nowadays replication of sessions(sip dialogs with their state) is not implemented. We are developing a memory replication mechanism that will spread session data amongst several servers. We are a couple of months away from it. From the OpenSER script you could use some sort of database query to find a suitable app server to invoke from a list than have a monitoring mechanism (like nagios script or similar) that removes failed WeSIPs from that list. That would add some kind of redundancy but not complete. When a dialog is setup in a WeSIP it has to be routed back to the same WeSIP for completition so in case of failure of an application server new dialogs could be setup properly using the distribution mechanism explained above but ongoing dialogs couldn't be finished properly.

Regards

Gines

El 29/04/2007, a las 20:53, Andreas Granig escribió:

Hi,

I was wondering if there's any mechanism in WeSIP for redundancy and failover. Assuming that I've one application server holding SIP dialog states, how could I add high availability to it?

There's some sort of session replication in Tomcat [1], so is this somehow used by WeSIP? Are there any other best practices to redundantly set up WeSIP?

Andreas

[1] http://www.onjava.com/pub/a/onjava/2004/11/24/replication1.html This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person: to do so could be a breach of confidence. Thank you for your cooperation. Information pursuant to paragraph 14 Austrian Companies Code: UPC Austria GmbH; Registered Office: Wolfganggasse 58-60, 1120 Vienna Company Register Number: FN 189858d at the Commercial Court of Vienna