i think the other thing to note is to keep bandwidth into consideration. Every change/registration from either system needs to be replicated to the other. If either site is of any size this will chew up lots of bandwidth.
95% of the time you're better off with an Audiocodes with SAS at the remote site. Mike On Wed, Jul 6, 2011 at 1:42 PM, Josh Patten <[email protected]> wrote: > Yes, it should work, provided you use BIND views to present different > records to each site (subnet). If connectivity goes down, one site won't > have voicemail and the like, but basic call routing including branch based > routing will work. > > > On Wed, Jul 6, 2011 at 9:36 AM, Tony Graziano < > [email protected]> wrote: > >> I have two site connected via an IPSEC VPN. Right now the system are >> on two different sip domains and have dial plans to each other without >> issue. >> >> Ideally, I would like to have them in a single sip domain in HA mode, >> so no interdomain dial plan would be necessary. >> >> Once I do this, I am trying to predict how dial plans would behave if >> there was a system failure. i.e., both locations have gateways, but >> will each location be able to use each others gateways "seamlessly". I >> think this goes back to branch survivability, which does not >> technically exist yet. >> >> Are there any tricks to allow branch1 use branch2's gateways >> seamlessly or vice versa in the event of a proxy/registrar or system >> outage? >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.326.5325 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Contract Customers: >> http://support.myitdepartment.net >> Blog: >> http://blog.myitdepartment.net >> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > Josh Patten > eZuce > Solutions Architect > O.978-296-1005 X2050 > M.979-574-5699 > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- Michael Picher eZuce Director of Technical Services O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> www.ezuce.com
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
