I recently ran Directory Walker on a 3.12b install. I received a message:<br><br>Alias=ESubscriber<br>Display Name=Example Subscriber - LUSD-UNITY<br>(error) Primary Call Handler is not valid!<br>This subscriber may be 'stranded' by an improper uninstall of a previous Unity system or it may be 'sharing' a primary call handler with one or more other subscribers.<br><br>If you select the 'Remove subscriber properties on mail users that have no primary call handlers' option and run again this user can be reimported to Unity.<br> COS Alias=defaultsubscriber<br><br>I ran DBWalker again, but the option to remove subscriber properties, is greyed out. Why can't I select it?<br><br>
That option is only available on 2.x systems. I was able to get away with that since in 2.x all call handlers (primary or otherwise) were stored in the directory along with mail users. I could tell a mail user was "stranded" if it's call handler was not in the directory.
With Unity 3.x all call handler information is stored locally on the Unity server they're created on in SQL. I can't be sure, then, if a user in the directory is stranded or not (i.e. they may just be assoicated with another Unity server elsewhere on the network).
(this is all covered in the fabulous help file for dbWalker, by the way...)
You'll need to use BunnyKiller (also available on AnswerMonkey.net) to clean those mail users of subscriber properties so you can import them again.
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...
[toc:faq]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 discusse...