James, You should do split dns, yes.
SRV records can point to multiple machines. sipx1 sipx2 These records should be listed in each location. In each location at the local DNS make the "local" one the highest priority (10) and the remote one a lower priority (20). >From the external facing records you might consider load balancing by putting the priority of each records to "1". You might also consider using a HA setup for this for registration. On Tue, Nov 10, 2009 at 5:41 AM, Picher, Michael <[email protected]>wrote: > The problem with this is that you have actually specified two different > SIP domains. One would be newyork.example.com and the other SIP domain > would be orlando.example.com. > > > > This would indicated two separate sipXecs systems and not one. > > > > Mike > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *James Johnson > *Sent:* Saturday, November 07, 2009 12:57 PM > > *To:* [email protected] > *Subject:* [sipx-users] SRV Records > > > > We would like to have SipX servers at two of our locations. Given that _sip > srv records can only point to one machine, what is the preferred way of > handling this. Do we need to do Split Horizon DNS (so that the local systems > receive an SRV record that points to their local machine)? Do we need to use > sub domains (sipx.newyork.example.com and sipx.orlando.example.com) or is > there some other approach we can use? > > _______________________________________________ > sipx-users mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
