[cisco-voip] Unity has picked the wrong DC - how to fix?

Robert Kulagowski bob at smalltime.com
Wed Apr 4 13:35:20 EDT 2007


In the ADDomain table, Unity is using one of the worst (pipe / latency) 
DCs that we have for a particular domain.  There's a better DC for that 
domain local to the Unity box; I'm guessing that the 
easy/dangerous/non-supported way to fix that would be to edit the 
ADDomain table.

Ideas on the right way?


More information about the cisco-voip mailing list