I'm suddenly fielding complaints that when new users self enroll for voice mail, everything works fine... until the next time they log in to VM and then gets asked to enroll again. I can manually uncheck the Self Enrollment box and that works fine, but I'm at a loss to explain the reason for this. This is a cluster set of Unity Connection servers.
Any ideas of where to start looking?
Sounded like a weird enough problem to be a bug but I don't
see any that match this exactly. Can you duplicate this problem?
If, so do you get ALL the way through the enrollment on the first
try or maybe only part way through?
It almost sounds like it might be some sort of replication issue. The next time
it happens go to the web admin on both the Pub and Sub and see if the First
Time Enrollment status is the same on both boxes.
I can replicate the issue with a newly created mailbox with no change to the status on either site... but the enrollment does not ask for a PIN change.
I thought at first that my feeble attempts to do some intrasite networking had screwed the db replication, but I've removed all links and restarted the server and still have the same issues.
Thanks for taking the time to reply... much appreciated!
Do you think you might be seeing this behavior??
Require Users to
Record Names at
By default, Cisco Unity Connection prompts users to record a name during first-time enrollment, but
it does not prevent them from completing the enrollment process if they do not. When listing a user in the corporate directory, Connection will play the display name of the user by using Text to Speech when the user does not have a recorded name. If you prefer to have all names played in the user voices, you may want to change how Connection handles first-time enrollment.
Check this check box if you want to force users to record a name. When this check box is checked, users who do not record a name during first-time enrollment are not enrolled as Connection users and cannot access their messages. They hear the first-time enrollment conversation each time that they sign in to Connection until they successfully enroll.
Note This setting affects all users who are associated with the Connection server, regardless of their conversation style.
Just made sure that this is unchecked on both pub and sub. I might go ahead and chek it, apply it, then uncheck it again and see if that helps.
I would recommend opening a TAC case here, which you can do right from
It seems like there may be some deeper underlying issue going on here.
TAC has resolved this issue.... by getting me to restart both servers in the cluster (Pub first.... wait for it to reboot, the sub).
Turns out there was a replication glitch between the servers.
Thanks for so kindly posting back with your results (+5). This will likely
help someone else down the road