DiRT doesn't create the subscribers, the SQLSyncSvr does - couple things could be happening here. First, you could already have a contact in AD that matches the alias - in this case the syncher will bind to that account and not create a new user.
If the SubscriberType value in the SQL table for the user is "2" instead of 1 (for Exchange) or 3 (for Domino) then the syncher will create an internet subscriber instead of a full subscriber - this would have had to be in your backed up database of course - DiRT doesn't go through the subscriber tables and change this prior to synching with the directory or the like.
This software populates a hidden field called targetaddress.
We were able to get the DIRT import to work properly, however whenever the targetaddress is being populated, the subscribertype seems to be changed to 2 in unity. We don't know why.
We were able to workaround the problem by changing the type back to 1 manually in SQL but we are not sure if this is a valid operation since we don't know what is changing the subscribertype, when and why.
Not real sure what that migration tool is doing but it sounds like it's setting something for users that makes the synch svr think the user is not a user with a local exchange mailbox but a contact that redirects it's messages to another address (targetaddress sounds an awful lot like something along these lines) - not real sure right off hand.
If after doing the synch the users in AD all have valid mailboxes and the subscriber type in the SQL database for them is still "1" and the SMTP address matches that of the full user in AD (and is not, for instance, the target address) then it should be OK. But of course you're sailing uncharted waters here so I can't say for sure...
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...