[cisco-voip] Upgrading from CallManager 4.1 to 7x the ACDeviceAuthenticationUser

Wes Sisk wsisk at cisco.com
Thu Jul 1 11:21:03 EDT 2010


No more DMA cycles at this point :-\

/Wes

On Saturday, June 26, 2010 1:33:52 PM, Jason Aarons (US) 
<jason.aarons at us.didata.com> wrote:
>
> Yes it did, any time I upgrade where AC was working in 4x the upgrade 
> to 7x  requires additional back end Callmanager steps to get AC 
> working again.
>
>  
>
> *From:* Mike Lydick [mailto:mike.lydick at gmail.com]
> *Sent:* Saturday, June 26, 2010 12:59 PM
> *To:* Jason Aarons (US)
> *Subject:* Re: [cisco-voip] Upgrading from CallManager 4.1 to 7x the 
> ACDeviceAuthenticationUser
>
>  
>
> So the 4.1 cluster did not have AC setup originally?
>
>     On Jun 26, 2010 12:45 PM, "Jason Aarons (US)"
>     <jason.aarons at us.didata.com <mailto:jason.aarons at us.didata.com>>
>     wrote:
>
>     It seems like a common problem that customers upgrading from 4.1
>     with Attendant Console have to go in a manually and create the
>     Application User ACDeviceAuthenticationUser and associate devices
>     to it just to get TCD to work.
>
>      
>
>     Is there a reason DMA or CallManager installation doesn't create
>     this user and setup Cisco CallManager Attendant Console Server
>     Service to just work for a upgrade? If this a PERS/BUG in DMA? 
>
>      
>
>     Also did I miss creating the user ACDeviceAuthenticationUser  in
>     the CallManager 4x to 7x Upgrade Documentation for post install, I
>     didn't find any warning about this, but had it bite me on 3
>     upgrades (somehow I keep forgetting about it<grin>)!
>
>     ------------------------------------------------------------------------
>
>     *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 <mailto: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. *
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/20100701/81f71669/attachment.html>


More information about the cisco-voip mailing list