<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Not much difference in multiple UCM clusters except the added complexity of how you route calls. As long as both UCM clusters are 9.0 then ILS will take care of sorting out which cluster owns which URIs. <div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>-Ryan</div></span>
</div>
<br><div><div>On Jun 22, 2012, at 10:34 AM, Florian Kroessbacher wrote:</div><br class="Apple-interchange-newline"><div bgcolor="#FFFFFF"><div>Hy out there</div><div><br></div><div>what about 2 ucm clusters and one vcs, vcse.</div><div><br><div>--</div>Florian Kroessbacher<div><span class="Apple-style-span" style="">gmail: <a href="mailto:florian.kroessbacher@gmail.com">florian.kroessbacher@gmail.com</a></span></div>
</div><div><br>Am 22.06.2012 um 16:18 schrieb Ryan Ratliff <<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>>:<br><br></div><div><span></span></div><blockquote type="cite"><div>I'll defer to the 9.0 SRND when it's out but I believe you will be ok with the same domain on both. Expressway can send incoming calls to both VCS and UCM. On UCM 9.0 the service that takes care of sharing URI information among clusters is ILS. VCS can't talk directly to ILS yet but ILS does support importing data from VCS so that UCM will know exactly which URIs should route to VCS. What this doesn't help with is shared URIs on both VCS and UCM. Is there a reason you'd have <a href="mailto:dan@test.com">dan@test.com</a> in both systems? <div>
<br><div> <br><div>
<span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; "><div>
-Ryan</div></span>
</div>
<br><div><div>On Jun 22, 2012, at 7:54 AM, Daniel wrote:</div><br class="Apple-interchange-newline"><p>Hi All,</p><p>There’s a lot of acronyms in that subject!!</p><p>We’re currently looking at integrating VCS into our CUCM and H323 Tandberg environment to migrate our VC/Tandberg/Telepresence gear to SIP and enable external IP video conferences.</p><p>We're on CUCM 8.5 with the new VCS being VCS-C 7.1 we will have VCS-E also.</p><p>My question is on the strategy for our domain name and what to use for DNS SRV and URI Dialling.<br>When we upgrade to CUCM 9.0 and have URI dialling within CUCM do the domain names need to be different on CUCM and VCS?</p><p>How will it work, how will the call route if I'm <a href="mailto:dan@test.com">dan@test.com</a> on CUCM and VCS.?<br>Does it need to be <a href="mailto:dan@test.com">dan@test.com</a> on CUCM and <a href="mailto:dan@video.test.com">dan@video.test.com</a> on VCS?<br>
This would be eaiser with a SIP route pattern of "@<a href="http://video.test.com/">video.test.com</a>" to VCS etc... <br>External DNS (VC calls form the internet) would then be transformed from "@<a href="http://test.com/">test.com</a>" to "@<a href="http://video.test.com/">video.test.com</a>" on the VCS<br>
Calls from VCS to CUCM would use DNS SRV, zones, and search rules pattern matching @<a href="http://test.com/">test.com</a> to be sent to CUCM. CUCM would be configured with a cluster wide FQDN as "<a href="http://test.com/">test.com</a>"</p><p>Right now its <a href="mailto:1234@%3CCUCM">1234@<CUCM</a> IP> on CUCM and <a href="mailto:dan@test.com">dan@test.com</a> (@<a href="http://test.com/">test.com</a> external also) on VCS which is very simple.</p><p>
I think I understand how it works for registration but not for call routing.</p><p>I just want to make sure we configure the correct domain name now so we don't have to change it in the future when upgrading to CUCM 9+.</p><p>Does anyone have any experience with this?</p><p>thanks</p><p>Dan</p><div> <br class="webkit-block-placeholder"></div>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div><br></div></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br></div></blockquote></div>
</div><br></div></body></html>