Voicemaill will still be limited to a single server in sipXecs 4.6, though it can now be moved off of the master server. only openUC 4.6 will have support for more than 1 (redundant) voicemail server.
On Fri, May 25, 2012 at 10:30 AM, Geoff Van Brunt <gvanbr...@dstgroup.com>wrote: > The best option is to have the sipX server be the authoritative server for > its own zone. For example it would be voice.company.com where company.comis > the DNS zone of the company. That way there is no stepping on of toes. > What is needed is guidance for the company admins to configure this in > their current DNS servers. Linux and Windows being the most common. > > One area where this gets complicated, is when there are multiple locations > with multiple gateways. Thinking about it makes my head hurt so I've always > just duplicated records to our company DNS. HA never worked for us anyway > as voicemail wasn't fault tolerant. With this changing, I may have to > rethink our current setup. Advice here by SipX HA DNS experts would be > appreciated. > > > Geoff Van Brunt > IT Manager > > 605 Hewitson St. > Thunder Bay ON, P7B 5V5 > Canada > > > > > > T 807.626.1306 > F 807.623.1792 > M 807.476.7002 > IP 1306 > mailto:gvanbr...@dstgroup.com > www.dstgroup.com > P Please consider the environment before printing this e-mail. > > This e-mail may be privileged and/or confidential, and the sender does not > waive any related rights and obligations. Any distribution, use or copying > of this e-mail or the information it contains by other than an intended > recipient is unauthorized. If you received this e-mail in error, please > advise me (by return e-mail or otherwise) immediately. > > > Ce courriel peut être confidentiel et/ou protégé et l'expéditeur > ne renonce pas aux droits et obligations qui s'y rapportent. Toute > diffusion, utilisation ou copie de ce message ou des renseignements qu'il > contient par une personne autre qu'un(e) destinataire désigné(e) est > interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser > immédiatement, par retour de courriel ou par un autre moyen.) > > -----Original Message----- > From: sipx-users-boun...@list.sipfoundry.org [mailto: > sipx-users-boun...@list.sipfoundry.org] On Behalf Of Douglas Hubler > Sent: Friday, May 25, 2012 8:44 AM > To: Discussion list for users of sipXecs software > Subject: Re: [sipx-users] Unmanaged services plan for 4.6 > > On Fri, May 25, 2012 at 7:23 AM, <pscheep...@epo.org> wrote: > > 2) Use UC DNS for the servers and the company DNS for the clients, > > this means putting the necessary records in the company DNS. All > > records are available on the UC servers as well. > > This is the safest I think because the client records are available > > everywhere. No changes on DHCP. > > 3) Use company DNS for all, meaning entering all records in the company > DNS. > > This requires special skills and time, but would work OK. > > I don't see any advantage of #3 over #2. If you disable/or enable a > single service in HA, it affects DNS now more than ever, but only for > internal connections between UC components so why open a ticket with IT to > make DNS change when the change does not affect any endpoints. > What we need it a clear list of endpoint related records you should copy > into your company DNS server. > > It may help not to think of the DNS server embedded in UC as a "DNS > Server" but instead as an "name resolution system that happens to follow > the DNS specification" > > This is a good discussion so thanks. Fortunately the distinction between > #2 and #3 is really just a best practices thing and nothing sipxecs has to > do or not do. > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- Josh Patten eZuce Solutions Architect O.978-296-1005 X2050 M.979-574-5699 http://www.ezuce.com
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
