Definitely B. Try doing an export of the users / phones to ease the migration.
I don't think a backup will do you that much good. Mike > -----Original Message----- > From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users- > boun...@list.sipfoundry.org] On Behalf Of Nathaniel Watkins > Sent: Friday, April 30, 2010 8:47 AM > To: Scott Lawrence; Tony Graziano > Cc: sipx-users@list.sipfoundry.org > Subject: Re: [sipx-users] xmpp federation question > > In order to get the xmpp federation stuff working - I'm planning on re- > installing 4.2 - and making my xmpp/sip domain publicly resolvable. > Here is the question: > > If I were to > > 1) Make a backup of my current system configuration > 2) Re-install 4.2 from the .iso > 3) Make a backup of the fresh install > > Is there a way to 'update' my original backup with the domain specific > changes from the fresh install backup. Then restore this modified > backup file. The goal obviously being to have my original > configuration intact. > > Or > > Should I stop being a baby and just do it... > > -----Original Message----- > From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users- > boun...@list.sipfoundry.org] On Behalf Of Scott Lawrence > Sent: Thursday, April 29, 2010 4:08 PM > To: Tony Graziano > Cc: sipx-users@list.sipfoundry.org > Subject: Re: [sipx-users] xmpp federation question > > On Thu, 2010-04-29 at 13:06 -0400, Tony Graziano wrote: > > That's a very good question. MY logic tells me NO (wont work) if the > > DNS ZONE is a different name than the internal one. I may be wrong, > > but look at my question to user/developers on EXACTLY what my logic > is > > and asking for some confirmation (or rejection) of my logic. > > > > > > If the ZONE name (SIPDOMAIN) is the same, I don't think it will > matter > > if the client can resolve it properly no matter where they are > > located. > > You are correct. When XMPP servers federate using TLS, the certificate > at each end must match the domain name they thought they were > connecting to. > > Some servers can play tricks with reverse DNS lookups and such, but > that's pretty fragile and equally hard with private addressing. > > > > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org 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/ > > This message and any files transmitted with it are intended only for > the individual(s) or entity named. If you are not the intended > individual(s) or entity named you are hereby notified that any > disclosure, copying, distribution or reliance upon its contents is > strictly prohibited. If you have received this in error, please notify > the sender, delete the original, and destroy all copies. Email > transmissions cannot be guaranteed to be secure or error-free as > information could be intercepted, corrupted, lost, destroyed, arrive > late or incomplete, or contain viruses. Garrett County Government > therefore does not accept any liability for any errors or omissions in > the contents of this message, which arise as a result of email > transmission. > > > Garrett County Government, > 203 South Fourth Street, Courthouse, Oakland, Maryland 21550 > www.garrettcounty.org > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org > 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 sipx-users@list.sipfoundry.org 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/
