Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Unity and Corp Domain

upgrading Unity 2.46 to 3.x <br>(little bit of Callmanager [3.12C] too)<br><br>Callmanagers are in own workgroup (2 - pub and sub)<br>Unity in it's own domain w/ RT ver Exch 5.5 on the Unity box (voicemail only for now)<br>corp Lan in it's own domain <br>(CCM & Unity in 10 network, while corp Lan in 172 network)<br><br>would like to keep the VoIP separated from corp domain,<br>do you see a problem with having the CCM join the Unity domain. <br>(have experimented a little in lab enviro and haven't seen any problems yet !!! )<br><br>Then later when the corporate Exchange 5.5 is upgraded to E2K enterprise (possibly clustered), then can point Unity to corporate Exchange for unified messaging. Still keeping the domains separated. <br><br>there will be a cat6509 doing the switching <br><br>one reason for CCMs joining the unity domain is that HIDS will be installed on the VoIP - each CCM and Unity will run an agent (recommended to be either w/g or domain not both?) <br><br>thanks<br><br>


Re: Unity and Corp Domain

Assuming that your VOIP domain and Corp domain are in different AD forests you are going to run into a snag when you try to connect Unity 3.X to the Exchange 2000 cluster. Windows 2000 does not support forest to forest trusts. Check out:;en-us;Q274438

I would suggest not trying to disjoint your converged network. Our biggest enterprise customers run Unity is the same domain. It's not really different that other member servers.


Keith Chambers
Unity Technical Lead
Unified Voice Team, San Jose
Cisco Systems

CreatePlease to create content