<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">The sip stack needs to be modified to spin that data up into the state machine so that it can take over calls once the fail over takes place... its not an easy task.<div><br></div><div>/b</div><div><br><div><div>On Aug 29, 2009, at 2:56 PM, Mitul Limbani wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div>Is itnpossible to have a db cluster know the state of each and every call and then use Heartbeat on this db +</div><div>fs cluster so that clients see only one ip where as internally all fs boxes refer db for call states, db again is under replication.</div><div><br></div><div>This in the thioery can be written, but I am sure if we think bit more on this direction the problem seem to be getting addressed.</div><div><br></div><div>Other guys also chip in their 2 cents, we just need 50 of em to make a full dollar.<br><br>Thanks & Regards,<div>Mitul Limbani,</div><div>Founder & CEO,</div><div>Enterux Solutions Pvt. Ltd.,</div><div>The Enterprise Linux Company (r),</div><div><a href="http://www.enterux.com">http://www.enterux.com</a></div><div><a href="http://www.entVoice.com">http://www.entVoice.com</a></div></div></span></blockquote></div><br></div></body></html>