<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
As long as your network meets the requirements set in the SRND (<a href="http://www.cisco.com/go/srnd">www.cisco.com/go/srnd</a>) for clustering over the wan you should be ok. Check the appropriate doc for your version to find the specifics.<div><br><div> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">-Ryan</font></p> </div><br><div><div>On Dec 10, 2008, at 10:54 AM, Duane Priebe wrote:</div><br class="Apple-interchange-newline"> <div class="Section1"><p class="MsoNormal">I’m co-locating all of our phone system components to a new production data this weekend and was thinking about keeping the publisher in the failover datacenter and just moving the subscriber to the new location. I know that the database can be sensitive to latency and some have said yes go ahead and split the two over the WAN and others said don’t do it. The average latency between the two sites is 30 – 38ms for a 64 byte packet. Any thoughts and/or suggestions? Thanks in advance!<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Duane<o:p></o:p></p> </div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">cisco-voip mailing list</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></div> </div><br></div></body></html>