Just to give the end result on this thread, we went ahead and merged the latest code, built RPMs and used it to update our servers. We had one small error that was the result of machine times being off (one was like off by two hours, not sure why) and then they synced fine and logs showed both machines were handshaking.
Thanks for all your hard work! Seeing the two machines finally connect was awesome. Daniel Chang PATLive -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Douglas Hubler Sent: Thursday, June 14, 2012 4:01 PM To: sipXecs developer discussions Subject: Re: [sipx-dev] Error adding second SipXecs 4.5.2 machine to cluster On Thu, Jun 14, 2012 at 1:41 PM, Dan Chang <[email protected]> wrote: > Awesome, thanks! I am testing out working it into our servers now. I was > looking at the commits and to test it is it as easy as just making changes to > config files on our primary (a la just edit files according to c3ea02f1ab and > c9ce7f14b0), or do I need to take other source code changes and actually > recompile? Not sure what you're saying, but any commits to git, no matter how small or to what type of file requires rebuilding rpms, that's just the way it goes, anything else is insanity. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
