[cisco-voip] IVR DST Updates

[Matthew Saskin]

The 3.5(3) to 3.5(4) upgrade went smoothly for me in the lab.  The only 
snag is one that I've run into with every major version of CRS server 
installation, that is the install process complains that I've got a 
blank SA account password on my SQL server even though I don't.

-matt

Poper, Cathy wrote:
> Hi Bill
> I did the upgrade from IPCCx 3.0(3a) to 3.5(4), applied the SR2 for DST
> (1.5hrs). I noticed that the real-time reporting monitor was broken
> however Cisco's just released ES1 to address that issue and I ran it in
> test and works fine.
>
> It was a real pain to upgrade all of our desktop agents (connected to
> 200 pc's remotely) and ran the upgrade - no need to uninstall.
> Other than that, it was pretty painless.
>
>
>
> Cathy Poper
> City of Hamilton/IT Services
> Network Support Analyst
> 55 York Blvd., 6th floor
> Hamilton, Ontario
> Canada
> L8L 3K7
> Tel: 905-546-2424 x5481
> Fax: 905-546-2333
> cpoper at hamilton.ca
>
>
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of bill kemmer
> Sent: Tuesday, March 06, 2007 9:25 AM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] IVR DST Updates
>
>
> We're running IP-IVR 3.5(3) as part of our IPCC
> Enterprise system.  IP-IVR is used for prompting and
> digit collection.  There is no resource selection or
> reporting going on through IP-IVR, and ICM routes all
> the calls.
> As part of my research for updating all of our voice
> servers for the DST events of this coming weekend, I
> know that I need to upgrade IP-IVR 3.5(3) to 3.5.(4)
> plus a service release and engineering special.  The
> Cisco field notice says that I'd see problems with
> "incorrect reporting data" and "incorrect trace file
> time stamps" if I don't upgrade the servers.  My
> question is---since I don't do any reporting through
> the IP-IVR platform, and since I could live with my
> trace file timestamps being off by an hour for a few
> weeks, is this upgrade necessary in my case?  I ask
> because it is quite an effort to get the software to
> several remote sites, plus trying to schedule
> resources to be there to perform the upgrade.
> Also, has anyone else done the 3.5(3) to 3.5(4)
> upgrade? Are there any gotchas?  I assume that this is
> a relatively painless upgrade, but Cisco's
> documentation is not very specific for this upgrade.
>  
> I appreciate any advice.
>
>
>
>  
> ________________________________________________________________________
> ____________
> The fish are biting. 
> Get more visitors on your site using Yahoo! Search Marketing.
> http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>