[cisco-voip] CallManager DMA doesn't keep ICD Extension

[Jason Aarons (US)]

I see 6.1.3a is current, any guesses on when 6.1.4 might release, this
is a large call center with UCCE/IPIVR.  I'd hate to manually have to
set the ICD Extension.

 
-----Original Message-----
From: Chris Ward (chrward) [mailto:chrward at cisco.com] 
Sent: Thursday, October 01, 2009 9:40 AM
To: Jonathan Charles; Jason Aarons (US)
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] CallManager DMA doesn't keep ICD Extension

CSCsy07560

Resolved in DMA 7.1.2 and 6.1.4. Which means you would also need to
upgrade to 7.1.2 or 6.1.4.

-Chris

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jonathan
Charles
Sent: Thursday, October 01, 2009 9:35 AM
To: Jason Aarons (US)
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CallManager DMA doesn't keep ICD Extension

I noticed this a long time ago.. figured it was just a normal part of
having to rebuild IPCC from scratch....

J

On Thu, Oct 1, 2009 at 8:24 AM, Jason Aarons (US)
<jason.aarons at us.didata.com> wrote:
> Anyone found a workaround for this, can the ICD Extension settings be
BATed
> back in after upgrade to 6.1(3) ?
>
> I also recall the DMA upgrade won't set IAQInstalledFlag to True on
> CallManager, so in the long run re-installing IP IPV/UCCX was the only
good
> fix.
>
>
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method
=fetchBugDetails&bugId=CSCsy07560
>
> DMA does not migrate ICD Extension Symptom:
>
> ICD Extension not exported in DMA Process.
>
> Conditions:
>
> This occurs for all DMA Exports including DMA 6.1(3) and 7.0.
>
> Workaround:
>
> Manually recreate the ICD Extension after install.
>
> Fixed-In
> 7.1(1.17)
> 7.1(1.18)
> 7.1(1.19)
> 7.1(2.1)
> 7.1(2.2)
> 7.1(2.3)
> 7.1(2.4)
> 7.1(2.5)
> 7.1(2.6)
> 7.1(2.7)
> 7.1(2.31)
> 7.1(2.32)
> 7.1(1.39000.137)
> 7.1(1.39000.138)
> 6.1(3.9901.121)
> 7.1(1.21)
> 6.1(3.7)
> 7.1(1.22)
> 6.1(3.8)
> 7.1(1.23)
> 6.1(3.9)
> 6.1(3.10)
> 6.1(3.11)
> 6.1(3.12)
> 6.1(3.13)
> 6.1(3.9999.1)
> 6.1(3.14)
> 6.1(3.15)
> 6.1(3.16)
> 7.1(2.10000.16)
> 6.1(4.1000.10)
> 7.1(2.39000.158)
> 6.1(4.39000.90)
> 6.1(4.14)
> 6.1(4.15)
> 6.1(4.16)
> 6.1(3.601)
> 6.1(4.17)
> 6.1(4.2000.2)
> 6.1(4.18)
> 6.1(3.602)
> 6.1(4.19)
>
> ONLY
>
>> Anyone noticed that the DMA for 7.0(1) isn't keeping UCCX information
>> about users. Customer is using DCD.
>
> CSCsy07560
>
>
http://www.gossamer-threads.com/lists/cisco/voip/104284?search_string=dm
a%20uccx;#104284
>
> Status Report to PM about why it took so long;
>
> 7. Created all call center agents (resources) in rmcm subsystem. (This
> took longer than expected because it appears that the DMA did not
> maintain certain user directory settings from the old UCM4.x....such
as
> which phone exten. is primary and whcih UCCX extension. I had to
> manually set all of these in UCM7 for all 280 or so agents.
> Investigated using the BAT tool, but I saw that was going to waste too
> much time and may not have been doable in the end)
>
> ________________________________
>
> 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.
>
> _______________________________________________
> 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

-----------------------------------------
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.