CUC old Recorded Name plays when leaving voice mails

[d.anthony.hadley_2]

Unity Connection  Version 8.6.2.20000-76  is integrated with LDAP (Active directory on a domain controller- don't know what version).  No Unified Messaging.  User A replaced user B in the company.  The Unity account for user B was given to user A who recorded their own Greetings and Recorded Name.  All is working fine but when user A leaves a message with user C, and others within the company, the greeting says it's from user B, not user A.  The account was deleted and recreated but the same thing is still happening.  The Recorded Name was recorded again by user A, but still the same thing.

How do I get user A's name to play when they leave a voice mail with someone?  Is there something still "stuck" in AD?

[Jonathan Schulenberg]

The good news is that AD should have nothing to do with this.

Is this the auto-generated TTS of the previous user's name or the actual user's recording?

Is this a CXN cluster or single-server install?

If a cluster, what does the cluster management page look like under CXN Serviceability?

Is the database replication intact?

https://supportforums.cisco.com/docs/DOC-5963

Please remember to rate helpful responses and identify helpful or correct answers.

[d.anthony.hadley_2]

Good to hear that AD is not involved.  It's the actual user's recording that people hear.  This is a cluster, pub and sub.  The cluster is in tact according to the cluster management page and the CLI, both are active/connected.

[Brad Magnani]

It could be

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCuh43453

I'd suggest upgrading to the latest ES from TAC for 8.6(2).

Hope that helps,

Brad

[Rob Huffman]

Hey Brad,

Nice find buddy! +5

I looked for bugs and couldn't pinpoint one so thanks for jumping

in with your expertise here You ROCK!

Cheers!

Rob

"Your life is worth much more than gold." 

- Bob Marley

[d.anthony.hadley_2]

Thanks for the reply.  The messages are announcing the correct name now.  Would the bug cause something like that?  Or, is it possible that the database didn't update right away?

[Brad Magnani]

It's possible although not too common.  I'd highly recommend still patching as it can cause some very undesirable behavior.