Unity 2.4.6 on Exchange 5.5 SP3. All User IS are kept on another larger Exchange 5.5 SP3 machine. No other users report this problem:<br><br>User records name. Within 5 minutes name is gone (replaced with "Extension 3220"). Within another 5 minutes or so the person cannot be located by spelling their name in the corporate voicemail directory (it works at first, playing hte recorded name, then later the "Extension 3220", and then just can't find it).<br><br>We've tried deleting the Unity account, deleting the Exchange account, then recreating the Exchange account, recreating the Unity account, importing mail back in (via .PST). Same problem.<br><br>I'd think it was an end-user problem, except that I changed the password, recorded the name myself, and have witnessed it disappear. Both Exchange servers appear to have plenty of space free.<br><br>Jason Roysdon, CCDP/CCNP:Security, MCSE, CNA<br>Network Engineer<br>NetsWork, Inc.<br>
This is a classic example of an Exchange user that's hidden in the address book being imported as a subscriber but Unity is not configured to pick up hidden users in the directory. The subscriber information is dumped in the memory cache (which is what the SA reads from) and everything is fine for about 10 minutes and then a resync kicks in. The DOH doesn't see the user in the directory so they are removed from the cache and disappear from the SA and the conversations wont find them.
If this user is hidden in Exchange I'm betting this is your issue (if not let me know). Here's a post on the registry changes you need to make sure are set in 2.4.6 so Unity will pick up hidden users and/or hidden distribution lists:
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...