The easiest thing to do is make the gateways H.323, that way any device can send calls to and from it.<br><br>Just make sure your voip dial-peers pointing back to CCM are limited to only the extensions that exist on that cluster, otherwise you may get unallocated number on inbound calling.
<br><br><br><br>Jonathan<br><br><div><span class="gmail_quote">On 2/13/07, <b class="gmail_sendername"><a href="mailto:Jean-Victor.Brun@ins.com">Jean-Victor.Brun@ins.com</a></b> <<a href="mailto:Jean-Victor.Brun@ins.com">
Jean-Victor.Brun@ins.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div vlink="purple" link="blue" lang="EN-US">
<div dir="ltr">
<div dir="ltr"><font color="#000000" face="Arial" size="2">I'm looking for support for adding a 2nd CCM cluster on an existing GW<br>router. The scenario is the existing CCM provides support for the local<br>campus and the new CCM going up will support remote sites.
<br><br>Does anyone have experience with multiple clusters at one location?</font></div></div></div><br>_______________________________________________<br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net">
cisco-voip@puck.nether.net</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
<br><br></blockquote></div><br>