I am running two systems. I run a production 4.0 system. The upgrade never worked, but I had a backup from 3.10.3. I wiped and reinstalled from the 4.0 ISO then manually copied some directories over once I recreated all the users and devices to get all the voicemail, greetings and such back in place. It wasn't bad, because it was not a large system.
I also run a lab 4.1 system. The update I did today seems to have pretty much broken my remote workers. I continue to have one way audio issues to for outbound calls. I don't believe it to be firewall issues, but I'll tackle it after a few more patches have been submitted. It's a work in progress. >>> Cuneyt M <[email protected]> 05/30/09 3:41 PM >>> Hi Tony, Thanks for the prompt reply. I do recall reading your message to list about the error in one of the xml file - which i came across too in the test system. Did you manage to solve it? Do you also experience web interface not responding until iptables are stopped? I take it that you are running 4.01 on production with polycoms? (which rom and firmware are you using as i had to rollback to SIP2.2.2 on 3.10.2/3 due to repetitive updates and phone xml in-compatibility since 3.8 Centos ISO) I am eager to move to 4.01 (either through yum or with fresh install) for two reasons 1) NAT traversal and dialing other branches without a secondary SBC hardware/installation 2) Move to latest firmware and ROM for Polycom 330s as yum updated 3.10.3 (from 3.8) has phone xml version issues which i had to fallback to sip 2.2.2 but I can't locate a single success story that outlines how to deal with the issues arise. I second your question. Does anyone upgraded successfully at all? If yes is there a guideline/tutorial that once can refer to? All the best! Tony Graziano wrote: > If it were me, I would wait until 4.01 is out and stable. Perhaps mid-July > judging from a statement by Scoot a few weeks ago? I would ask if anyone has > upgraded succesfully first. The 4.1 unstable is pretty good, but there are > still some problems to be fixed slated for the 4.01 release. > > >>>> Cuneyt M <[email protected]> 05/30/09 3:13 PM >>> >>>> > Hi there, > > I have one sipX server running on 3.10 which is upgraded from 3.8 via > YUM (3.8 was installed off the Centos ISO at the time). > > Having briefly read the troubles reported in the list and the 4.01 > announcement on sipx homepage, I am not sure how i should go about > upgrading to a stable 4.0 (or 4.01) with Yum. > > I had another test installation of 3.8, upgraded to 3.10 with yum. My > initial attempts of yum update to 4.0 is failed. I had to install > sipxsupervisor and fix the bits reported on sipxecs service start. Even > then i couldnt get access to the web interface without stopping iptables > (i had selinux disabled at all times). > > Even stopping iptables and getting access to web interface, few services > reported failure from web UI. > > Taking into consideration of a smooth upgrade of a live 3.10.2/3 system > to 4.0 (or 4.1), I would like to know Your suggestions. > > Is there an automated, tested and proven, smooth way to upgrade a Live > system? Or should i install from a 4.0 ISO from scratch (even then i > presume i need to update to 4.01 unstable builds?). > > Clearly I'm rather confused on the current state and would like to hear > your advise. > > All the best. > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
