05-21-2004 08:18 AM - edited 03-18-2019 03:03 PM
Wanted to check and see what the implications might be for a customer who wants to deploy Exchange routing groups between distant locations. A Unity server would be at each routing-group location, servicing local Exchange servers, and all machines would be networked via a common AD forest. I know there used to be functional considerations (i.e. ISM didn't work) when routing groups were implemented, but not sure what other caveats might be out there.
Solved! Go to Solution.
05-21-2004 09:07 AM
We changed ISM in 3.1(6) and 4.0(3) so that it spoofs the sender rather than actually logging in to their mailbox to send the message. That limitation didn't really have anything to do with routing groups but the concept was the same in that we didn't want to login to a mailbox in Timbuktu. ISM used to only work if the users were on the same Unity server where now it works as long as they are in the same dialing domain.
The design you are proposing looks solid and it the right way to go.
Hope this helps...
Keith
05-21-2004 09:07 AM
We changed ISM in 3.1(6) and 4.0(3) so that it spoofs the sender rather than actually logging in to their mailbox to send the message. That limitation didn't really have anything to do with routing groups but the concept was the same in that we didn't want to login to a mailbox in Timbuktu. ISM used to only work if the users were on the same Unity server where now it works as long as they are in the same dialing domain.
The design you are proposing looks solid and it the right way to go.
Hope this helps...
Keith
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide