[cisco-voip] Callmanager version 5.0 Upgrade
Charles J. Boening
charlieb at cot.net
Tue Aug 29 11:19:21 EDT 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alfred,
Your version should be supported by 5.0.4 DMA Tool. I'd suggest opening
a TAC case. Maybe try a reboot if you can then install again. If you
have a publisher/subscriber, then I think you're supposed to run the
tool on the publisher. Also, you have to install the DMA Tool on the
CCM server itself. You can't install to a workstation or another
server.
Good luck,
Charlie
> -----Original Message-----
> From: Thyri Alfred [mailto:alfred.thyri at mii.at]
> Sent: Tuesday, August 29, 2006 3:43 AM
> To: Charles J. Boening; cisco-voip at puck.nether.net
> Subject: RE: [cisco-voip] Callmanager version 5.0 Upgrade
>
> Hi Charlie,
>
> I tried to install the dma tool (5.0(4)) on our CCM 4.1(3)sr2
> installation with bad luck :-(
>
> In the log file I found something interesting:
> 13:54:15: DMAInstall.cpp: fnInitDMAInstallProperty: Error: Init
> SZCMVER from default because of invalid szCCMBuildVersion = 4.1(3)
> 13:54:15: MSIUtils.cpp: fnMsiSetProperty: Function started
> 13:54:15: MSIUtils.cpp: fnMsiSetProperty:
> CCMInstalled = "False"
> 13:54:15: MSIUtils.cpp: fnMsiSetProperty: Function ended
> 13:54:15: MSIUtils.cpp: fnMsiSetProperty: Function started
> 13:54:15: MSIUtils.cpp: fnMsiSetProperty: SZCMVER = "2"
> 13:54:15: MSIUtils.cpp: fnMsiSetProperty: Function ended
> 13:54:15: MSIUtils.cpp: fnMsiGetProperty: Function started
> 13:54:15: MSIUtils.cpp: fnMsiGetProperty: REINSTALL = ""
> 13:54:15: MSIUtils.cpp: fnMsiGetProperty: Function ended
> 13:54:15: MSIUtils.cpp: fnMsiGetProperty: Function started
> 13:54:15: MSIUtils.cpp: fnMsiGetProperty: SZSETUPTYPE = ""
> 13:54:15: MSIUtils.cpp: fnMsiGetProperty: Function ended
>
> It seems that our version is not supported by the dma tool,
> although it should be supported.
>
> I also tried to check with Upgrade Utility (version 4.2(2)),
> with the result that everything is ok but the hardware should
> be upgraded. We already ordered new hardware...
>
>
> Do you have any hints for me?? Somebody else?
>
> cheers,
> Alfred.
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Charles J.
> Boening
> Sent: Dienstag, 29. August 2006 05:40
> To: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Callmanager version 5.0 Upgrade
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Here's my experience with upgrading to CCM5.
>
> I came from a CCM 4.0(2a) system running on an ICS7750 to CCM
> 5.0(3) running on my own supplied IBM server. Cisco
> documentation indicated my IBM server (8491G2U) was supported
> in this release. I actually purchased it based on Cisco
> documentation and specifications just for this application.
> Turns out that the 8841G2U was supported by the installer but
> the 8491G2U wasn't. The only difference between these two is
> the warranty. One has a 1yr warranty and the one I had came
> with a 3yr on-site warranty. Other than that, there are no
> hardware differences. TAC opened a bug case and was supposed
> to fix the documentation. I think TAC said I'd have to wait
> for 5.0(4) which wouldn't be available on DVD for a few more
> months or whatever it was.
> Being the nosey person I am, I snooped around and found where
> in the installer to change it to recognize my machine type.
> I ended up making an ISO image and used a hex editor to
> change the file the installer reads so my machine type would
> be supported. :) Please don't ask what file I changed as
> I'm sure Cisco wouldn't want that information floating
> around. I'm sure some of the more industrious users out
> there will be able to figure it out on their own. For the
> rest, I'm sure someone will post the information on some
> message board or somewhere at some point. :)
>
> During my data export from CCM 4.x, I ended up having some
> data inconsistencies in my 4.x database that caused export
> errors. A call to TAC and a few days later, they had found
> and fixed the problems. I was then able to successfully
> export out my old data using DMA 5.0.4.
>
> Importing of Windows CCM data is done during the installation process.
> In my playing around, I had successfully installed CCM5
> without importing any data. Once installed, I saw no
> provisions for importing the data after the installation.
> So, with exported data in hand (actually on a local FTP
> server), I went through the installer process and came up
> with some errors when importing Windows DMA data. I didn't
> see any documentation indicating it, but it turns out the
> name of my new CCM had to match the name of the machine I was
> coming from. The IP address may have had to match too but
> I'm not sure. Per TAC request, I set both the machine name
> and IP address so they were the same as my current production
> system. This wasn't a problem since I was building the new
> server on it's own VLAN for testing. Once this was done, the
> install went very smooth and all my data was imported. I was
> actually very impressed with the installer and it's ease of
> use. Not that there's much to it, but it was all pretty easy
> and straight forward.
>
> All in all I'd say the installation and upgrade went pretty
> well. I was a little disappointed with a couple of TAC
> people and their slowness to respond. At one point I waited
> over a week for a response. Fortunately I had enough other
> duties to keep me busy in the meantime. I think overall I
> spent about two to three weeks off and on between messing
> with things on my own and waiting on TAC.
>
> Post upgrade everything is running very well. My Unity
> integration, Attendant Console and everything else came over
> just fine. I also have a SIP trunk to an Asterisk box that
> came right up and is running fine as well. I'm using MGCP on
> a 1760V router to two PRIs. I have no FXO or FXS lines.
> We're actually a small rural telephone company so I have
> plenty of CO lines available for fax machines and such. :)
>
> The only issue I've had so far is with shared line
> appearances. In the old system I had 3 extensions shared
> across seven phones. I had call forward busy from one
> extension to the other with the last extension going to
> voicemail on busy. All extensions go to voicemail on no
> answer. After the conversion the forwarding wasn't working
> right. If someone was on the first line, callers would go
> right to voicemail or get a fast busy; I don't remember
> which. In the end I think I had to mess with the number of
> concurrent calls on the line. I increased the max calls for
> each phone on all extensions to the number of shared lines
> + 1. I did this on both 7940 and 7960 phones that shared the
> extensions. I set the busy call trigger to 1 and everything
> seems to be working ok. In CCM5, there seems to be more of a
> distinction between lines and phones. You can edit lines
> directly without even going through the phone config. A
> little confusing at first but not bad once you figure it all out.
>
> One more issue I have is doing the 5.0(4a) update. I'm currently at
> 5.0(4) but it seems that updates are now required to be
> signed and the update posted on CCO isn't. Oh well, another
> call to TAC I guess. :)
>
> We've been live for about two weeks now. Everything has been
> running very smooth and so far I'm pleased with CCM5.
>
> Charlie
>
>
>
>
>
> > -----Original Message-----
> > From: cisco-voip-bounces at puck.nether.net
> > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of
> Manoj Kalpage
> > Sent: Monday, August 28, 2006 7:04 PM
> > To: Matt Slaga (US)
> > Cc: cisco-voip at puck.nether.net
> > Subject: Re: [cisco-voip] Callmanager version 5.0 Upgrade
> >
> > Thank you very much for the reply as always.
> > What is your recommendation to upgrade to Version 5.0? Does
> this work
> > smoothly? Anyone had any bad experience of upgrading to 5.0?
> >
> > Best Regards,
> > Manoj
> >
> >
> > On 8/28/06, Matt Slaga (US) <Matt.Slaga at us.didata.com> wrote:
> >
> > Manoj-
> >
> >
> >
> > CallManager 5.0 only runs on Linux. While you can upgrade from
> 4.0
> > or 4.1 to 5.0, it requires a complete rebuild and restore
> process to
> > migrate the data from SQL to Informix under the new linux platform.
> > There is no 5.0 that runs on win2k.
> >
> >
> >
> >
> >
> >
> > ________________________________
> >
> >
> > From: cisco-voip-bounces at puck.nether.net
> > <mailto:cisco-voip-bounces at puck.nether.net>
> > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of
> Manoj Kalpage
> > Sent: Sunday, August 27, 2006 10:04 PM
> >
> >
> > To: cisco-voip at puck.nether.net
> >
> > Subject: [cisco-voip] Callmanager version 5.0 Upgrade
> >
> >
> >
> >
> >
> > Hi All,
> >
> > Please someone help me if I am wrong here.
> >
> > My Understanding is CallManager 4.0 can be upgraded to
> Callamanger
> > 5.x keeping existing windows 2000 OS but new installation
> only work on
> > Linux.
> >
> >
> >
> > Regards,
> >
> > Manoj
> >
> >
> >
> >
> > ________________________________
> >
> >
> >
> >
> >
> >
> > Disclaimer:
> >
> > This e-mail communication and any attachments may contain
> > confidential and privileged information and is for use by the
> > designated addressee(s) named above only. If you are not the
> > intended addressee, you are hereby notified that you
> have received
> > this communication in error and that any use or reproduction of
> > this email or its contents is strictly prohibited and may be
> > unlawful. If you have received this communication in
> error, please
> > notify us immediately by replying to this message and
> deleting it
> > from your computer. Thank you.
> >
> >
> >
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (MingW32)
>
> iD8DBQFE87cBcGGHuFdGSWARAh5ZAJ4oAgw7f/rYe7uO1ERMvUv9JS48EgCfc/rQ
> TcATbYEo8nOCBavtsYcvzpU=
> =qoKW
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
iD8DBQFE9Fr5cGGHuFdGSWARAtoZAJoCmWT+xXHCBxNic56P0B4HHKj/KQCfUQPx
mMbEx/UzDLZDZXGRSkWbt/E=
=NsnH
-----END PGP SIGNATURE-----
More information about the cisco-voip
mailing list