Did DBWalker report a stranded (orphaned) call handler that had an alias of "ch_"? I'm betting it did... 2.x didn't handle objects being deleted out from under it in Exchnage terribly well and it wont clean up the primary call handler associated with the subscriber.
dbWalker should definitely pick this up and offer the option of removing the orphaned handler (I'd be very suprised if no errors were in that output at all). If not you can check manually in the Unity folder in the Exchange administrator... drill down into the call handler branch and look for an object that has that alias and remove it... this should clear your problem.
hmmm... yeah, if you could email me the log that would be good (and include the alias of the subscriber you ended up removing and their extension number as well). This is so much more straight forward in 3.x where it's all in SQL and it's a matter of kicking a few queries out....
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...