[cisco-voip] IPCCX 3.5(3) to 4.0(4) Upgrade

[Martin Lohnert]

Hi Matt,
I've gone through something very similar, and because of downtime,
decided to do a new install.
We were adding a 2nd IPCC server for HA, so I used that one to install
a new IPCC 4.0.4, integrate with directory, and CCM with a new range
of CTI ports. I then set up CTI route points for testing the migrated
apps.
All of this just because my biggest concern was script conversion, as
ours are quite long and complex. I did the automatic conversion in a
lab, and even though the scripts did work afterwards, they became
cluttered with extra (and unnecessary) steps, so I decided to clean
them up manually.
Kept running this IPCC4 for some time and had the apps thouroughly
tested, and once there were no issues, changed the production CTI
route points to associate with the new server. At this point you have
to reinstall desktops, and can start rebuilding the original server
for IPCC4.
Hope this makes sense ;)
Cheers,
Loni

On 10/24/06, Matthew Melbourne <matt at melbourne.org.uk> wrote:
> Does anyone have any good/bad experiences of upgrading IPCC Express from
> 3.5(3) to 4.0(4) and introducing high availability (we currently have a
> cold standby server). The jury seems to be out over the best migration
> strategy, i.e. an upgrade versus a new installation. With a new
> installation we would lose the historical reports, but this isn't a
> show-stopper. We have a small time window to upgrade IPCCX and visit all
> the desktops split over several sites to upgrade CAD/CSD/HR.
>
> An upgrade would, hopefully, retain all CRS configuration and reporting
> data, but I'm unsure whether it's possible to rollback to IPCCX 3.5 when
> the changes to the cluster have been made in DC Directory.
>
> Cheers,
>
> Matt
>
> --
> Matthew Melbourne
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>