Thanks for all the replies guys, looks like i'll stick with H323.<br><br>
<div class="gmail_quote">2009/5/19 Justin Steinberg <span dir="ltr"><<a href="mailto:jsteinberg@gmail.com">jsteinberg@gmail.com</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">SIP is required if you want intercluster presence. Although if you really wanted to you could create a special CSS for Subscribe that used the SIP trunks and actual calls/media could use h323.
<div>
<div></div>
<div class="h5"><br><br>
<div class="gmail_quote">On Mon, May 18, 2009 at 10:01 PM, Tanner Ezell <span dir="ltr"><<a href="mailto:tanner.ezell@gmail.com" target="_blank">tanner.ezell@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">I've had the same experience, and feelings towards sip. H323 > SIP (imo)
<div>
<div></div>
<div><br><br>
<div class="gmail_quote">On Mon, May 18, 2009 at 6:57 PM, Jason Burns <span dir="ltr"><<a href="mailto:burns.jason@gmail.com" target="_blank">burns.jason@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">I'd stick with H.323 between CCM clusters over SIP. I find it easier to troubleshoot and understand (but that's just personal preference I suppose), and everything usually "just works" with the H.323 setup.<br>
<font color="#888888"><br>- Jason</font>
<div>
<div></div>
<div><br><br>
<div class="gmail_quote">On Fri, May 15, 2009 at 10:32 AM, Matthew Linsemier <span dir="ltr"><<a href="mailto:mlinsemier@apassurance.com" target="_blank">mlinsemier@apassurance.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div><font face="Calibri, Verdana, Helvetica, Arial"><span style="FONT-SIZE: 11pt">If you use Unity you may want to verify that features such as MWI and voice profiles work across the a SIP link. There was a reason we went with H.323 during our CCM 4 to UCM 7 migration, and I think this was one of them.<br>
<br>Matt
<div>
<div></div>
<div><br><br><br>On 5/15/09 3:13 AM, "Nick" <<a href="http://csvoip@googlemail.com" target="_blank">csvoip@googlemail.com</a>> wrote:<br><br></div></div></span></font>
<blockquote><font face="Calibri, Verdana, Helvetica, Arial"><span style="FONT-SIZE: 11pt">
<div>
<div></div>
<div>Hi All<br> <br>I'm looking setting up an ICT to another CUCM cluster, just wondering if using SIP instead of H323 is now a better option?<br> <br>Any thoughts on this?<br> <br> <br><br></div></div>
<hr align="center" size="3" width="95%">
</span></font>
<div><font size="2"><font face="Consolas, Courier New, Courier"><span style="FONT-SIZE: 10pt">_______________________________________________<br>cisco-voip mailing list<br><a href="http://cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></span></font></font></div></blockquote>
<p><font color="#808080" size="1" face="Arial">
<hr>
</font>
<p></p>
<p><font color="#808080"><font size="1" face="Arial">CONFIDENTIALITY STATEMENT<br>This communication and any attachments are CONFIDENTIAL and may be protected by one or more legal privileges. It is intended solely for the use of the addressee identified above. If you are not the intended recipient, any use, disclosure, copying or distribution of this communication is UNAUTHORIZED. Neither this information block, the typed name of the sender, nor anything else in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message. If you have received this communication in error, please immediately contact me and delete this communication from your computer. Thank you.</font> </font></p>
<p><font color="#808080">
<hr>
</font>
<p></p></p></p></div><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a 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></div></div><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a 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></div></div><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a 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></div></div><br>_______________________________________________<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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>