[cisco-voip] IPCC and Call Manager Upgrades

[Scott Voll]

Agreed.  we did the same going from CM 4.1 to 6.1 and UCCx 4.0 to 5.0.
one other thing to keep in mind is upgrading your CAD.  just remember to
save time to at least get the first few agents upgraded so first thing they
can answer calls.  the rest of our agents did there own upgrades.

make sure you check all your 3rd party apps will work and are upgraded to
support CM 7.  we have CM, Unity, UCCx, Phone proxy, Xmedius, Berbee IC, Arc
Console, etc.  You will need to know what has to be adjusted to make sure
everything works.  eg. Linux based CM started using Application users which
need to be setup.  and Java versions change so you will need to keep that in
mind.  Most of the applications we ran the JTAPI client and they worked, and
Unity needed the new TSP plugin.

Just things to keep in mind.

Scott

On Mon, Jun 8, 2009 at 8:06 AM, Michael Back <Michael.Back at nisd.net> wrote:

> We did the same thing recently.  We were on CM 4.1.3 and CRS 3.5.  We
> purchased new hardware for the upgrade to Ver. 7.  I chose to use new IP
> addresses for the new hardware.  If you do the same, run DMA on your old
> CM and import the database on a during test build.  Make sure EVERY
> PHONE that you own is configured before running DMA the first time.
> Once you get this initial import, get your license from Cisco for your
> final build.  During the initial build, we intended on building our UCCX
> 7 box, but had trouble due to licensing.  It took a long time for us to
> get our UCCX media and PAK compared to the UCM media and PAK.  Once you
> have the software and PAK, perform your install, and make sure the
> licensing matches what you are supposed to have on your system.  You can
> then build your new UCCX using your old scripts and prompts.  Test all
> your scripts thoroughly before going live.  Once you have your UCM
> license and have UCCX ready, you can plan for the final upgrade for UCM.
>  We did a final DMA a week before our upgrade and kept changes to a
> minimum.  If a change was necessary, we made it to both the old and new
> system.  All I had to do from this point was run a script that changed
> option 150 on my DHCP scopes to the new TFTP.  If you have ATAs, make
> sure they are using the most recent firmware.  I was able to complete
> almost all of the staging during business hours, and had to work a
> couple of hours extra on a Friday night for the DHCP change and actual
> migration.  Make sure to do a device baseline so that you know how many
> phones, gateways, etc. should be registered when you are done.  We have
> more than 10,000 phones and had very few problems aside from our UCCX
> licensing delay.
>
> MB
>
> >>> "Mike J. Erickson" <mjerickson at orbits.net> 6/8/2009 9:34 AM >>>
> Hi All,
>
> Somewhat general question.
>
> We are running CM 4.2SR3 and IPCCX 4.0(5).  We want to get both
> upgraded to 7, but it sounds like a tremendous task.  Anyone have any
> experiences with this type of upgrade or suggestions on which path to
> take?  We are going to go with new hardware.  I am wondering if there is
> some way to stage this kind of upgrade.
>
> Thanks.
>
> Mike Erickson
> Systems Engineer
> ORBIT Systems, Inc.
> www.orbits.net<http://www.orbits.net/>
> 651-767-3300 helpdesk
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090609/7f5c6686/attachment.html>