Thanks. CDR data looks good on all my test machine, so it looks like
that data should be fine.
On 7/17/2010 10:34 AM, Tony Graziano wrote:
WAIT...
You might want to make a manual backup of your CDR data. When I did an
upgrade from 3.10.3 to 4.0.4 all CRD data went bye bye. I haven't been
curious enough yet to see if 4.0.4 to 4.2.1 does the same thing, but I
suspect it does.
On Sat, Jul 17, 2010 at 11:03 AM, Matthew Kitchin (Public)
<[email protected] <mailto:[email protected]>> wrote:
Thanks. I will do that. Maybe stopping it will allow that ftp
scriptlet to succeed. I think I will go through with the upgrade
today or tomorrow.
------------------------------------------------------------------------
*From: * Michael Picher <[email protected]
<mailto:[email protected]>>
*Date: *Sat, 17 Jul 2010 09:07:00 -0400
*To: *Matthew Kitchin (public/usenet)<[email protected]
<mailto:[email protected]>>
*Cc: *<[email protected]
<mailto:[email protected]>>
*Subject: *Re: [sipx-users] Upgrading from 4.0.4 to 4.2.1 - any
last minute words of wisdom?
Matthew,
The only thing additional that I do is 'service sipxecs stop'
before I do the 'yum update sipxecs'.
And then when the PBX comes back up, send server profile, and then
send all phone profiles.
Mike
On Fri, Jul 16, 2010 at 1:37 PM, Matthew Kitchin (public/usenet)
<[email protected] <mailto:[email protected]>> wrote:
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]
<mailto:[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/
--
There are 10 kinds of people in this world, those who understand
binary and those who don't.
[email protected] <mailto:[email protected]>
blog: http://www.sipxecs.info
call: sip:[email protected] <mailto:sip%[email protected]>
_______________________________________________
sipx-users mailing list [email protected]
<mailto:[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/
--
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
<mailto:[email protected]>
Fax: 434.984.8431
Email: [email protected] <mailto:[email protected]>
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]
<mailto:[email protected]>
Fax: 434.984.8427
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
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/
