Sounds like these subscibers were failed import attempts or something similiar, does that sound right? If the primary call handler didn't get created because the import failed before it was complete, you'd see something like this.
The only way to fix it is to pop open SQL, go to the Subscriber table in UnityDB and delte the row that contains that subscriber. Be sure you get the right ones, there's no undo here. The you'll need to clean the Unity extensions off the mail users for those folks in Exchange 5.5... open it in raw mode and remove the Voice Mail User ID and the custom attributes #12 and #14. Then things should be clean.
It'd be interesting to know why the import for these folks failed, assuming that's the case...
1. Go to Start - Programs - Microsoft SQL Server - Enterprise Manager
2. In the MMC, left panel, expand the + signs to get to your server name, which is under Micrsoft SQL Servers - SQL Server Group
3. Expand folder Databases
4. Expand database UnityDb
5. Click on Tables
6. Right-click on table Subscriber, select Open Table, then select Return all rows
7. The second row is Alias. You can browse this column for the subscriber you want to delete or create a SQL query to locate within the table. Highlight the subscriber, then right-click and select Delete. This is a permanent and immediate change as mentioned in Jeff's note.
Ok for starters I'm still running version 220.127.116.11, and I had my Exchange admin look for this database and we don't have it or SQL. So is this db just a 3.X thing and if so where should I look in 2.4.6 to fix this same issue? BTW we are looking on the Unity server.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...