I need to upgrade from 4.0.4 to 4.2.1 in the next week or so. I have tested everything I know to test, and don't see any issues I can't deal with.
I'm currently running -4.0.4 -CentOS 5.4 64 Bit. -Polycom Soundpoint 450s and 550s -Polycom Soundstation 6000s -All Polycoms running Bootrom 4.2.1 and firmware 3.1.3 Rev C Split -Sipxbridge with Verizon VoIP -Auidocodes MP 118 FXO with 5.4 firmware for emergency -Microsoft Domain certificate authority internally generated SSL cert -Using ACD and Autoattendants -Permissions change to allow Polycoms to upload their user settings -Variety of headsets -No remote phones That is about all I can think of for what I am running. I do not plan to change the polycom firmwares. I plan to point my repo files to the staple 4.2.1 build repo below [sipXecs] name=sipXecs build service for CentOS $releasever - $basearch baseurl=http://download.ezuce.com/sipfoundry/4.2.1/CentOS_5 enabled=1 gpgcheck=0 -run yum update sipxecs -using yum, remove 4.0.4 FTP package that fails to uninstall -restart all phones (not sure if this is necessary or not). On my test machines, the server tried unsuccessfully to restart phones. I can power cycle them at the switch level if needed. -Check all the basic functionality (ACD, Voicemail, PIN change, Autoattendant, MOH, transfer, forward, Web GUI for end users) That is about it. As far as failback, I assume the only option is to reinstall 4.0.4 and restore from backup. If voicemails were left on the 4.2.1 before failing back, I would have to manuallly locate them in a backup of the 4.2.1 system I took before failing back to 4.0.4. Does anyone see any major issues with this? It has all worked in testing, but obviously my test setup doesn't have the amount uf users, devices, etc that production has. Thanks, Matthew _______________________________________________ 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/
