Solved: Unity Networking Trouble

srichardson · ‎03-28-2003

Scenario: 2 Unity Servers, each serving a separate exchange2000 server with only one message store in the same Win2000 domain. We call them SUNNY and DAYTON. SUNNY's primary location had dial ID 408 and is configured to search the entire dialing domain. DAYTON is 937 and also searches the entire dialing domain. They both belong to the same dialing domain. A user who's mailbox is on DAYTON (x1049) can forward a message to x1050 homed on SUNNY with no trouble. The use on SUNNY (x1050) cannot locate the subscriber in the directory by x1049, so instead attempts to locate him by using the dial id and extension (9371049). Unity accepts this entry and allows he forward, but the message never arrives at its destination.

What could be the trouble? I can tell you that there are several instances of "default location" in the primary location for the DAYTON Unity due to two reinstallation attempts, could this be causing the trouble? I should note that these default location entries were not removed by the Unity Uninstall process.

Thank you.

Stephanie

joconnors · ‎03-30-2003

Yes Stephanie, those extra default locations objects could be causing you trouble. You'll want to get those out of there. But you want to be real careful to not remove the wrong ones. You might want to have TAC assist you with that.

Another thing to look at regarding your addressing troubles on SUNNY...Use the Cisco Unity Data Link Explorer (CUDLE) downloadable from www.ciscounitytools.com. Check out the dtmfAccessId table and see if 1049 is showing up in there - it should be. If not, that's why the extension is not recognized. Look and see if 1049 is in the globalsubscriber table - it should also be in there. If it's in there but not in dtmfAccessId that's a problem.

Since it does let you address using 9371049, use Exchange 2000 Message Tracking to try and determine where the message went instead of the intended recipient. You'll first want to make sure message tracking is enabled on all your Exchange servers. This is done via Exchange Admin by right-clicking on each server and selecting Properties, then on the General tab check the "Enable Message Tracking" box. Then run your test again.

The Message Tracking tool is available via the Exchange 2000 Admin in the Tools subtree.

View solution in original post

joconnors · ‎03-30-2003

Yes Stephanie, those extra default locations objects could be causing you trouble. You'll want to get those out of there. But you want to be real careful to not remove the wrong ones. You might want to have TAC assist you with that.

Another thing to look at regarding your addressing troubles on SUNNY...Use the Cisco Unity Data Link Explorer (CUDLE) downloadable from www.ciscounitytools.com. Check out the dtmfAccessId table and see if 1049 is showing up in there - it should be. If not, that's why the extension is not recognized. Look and see if 1049 is in the globalsubscriber table - it should also be in there. If it's in there but not in dtmfAccessId that's a problem.

Since it does let you address using 9371049, use Exchange 2000 Message Tracking to try and determine where the message went instead of the intended recipient. You'll first want to make sure message tracking is enabled on all your Exchange servers. This is done via Exchange Admin by right-clicking on each server and selecting Properties, then on the General tab check the "Enable Message Tracking" box. Then run your test again.

The Message Tracking tool is available via the Exchange 2000 Admin in the Tools subtree.