The Cluster nodes should be within the 40ms but some time this may not be the case down to Traffic or other issues. I was asking about the protocols because I know that MGCP is a Client server based protocol and most of the configuration is done on the Call manager if the nodes are not within the 40ms will that be a problem using MGCP.<br>
<br>As using H323 or SIP I can get the Gateway to do more of the signalling. I hope you understand what I am trying to get at. <br><br><br><br><div class="gmail_quote">On Feb 18, 2008 7:39 PM, Matthew Saskin <<a href="mailto:matt@saskin.net">matt@saskin.net</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The protocols you have listed are primarily used for gateway<br>communication - the signaling within the cluster happens automatically<br>
using a proprietary protocol. As long as the cluster nodes are within<br>40ms of each other, you're fine on that front.<br><br>As far as gateway protocols, there are plenty of pros and cons to using<br>H323, SIP, or MGCP. It depends significantly on what your requirements are.<br>
<br>-matt<br><div><div></div><div class="Wj3C7c"><br>Akaal singh wrote:<br>> Hello,<br>><br>> Just wanted to know which Codec would work best if I have a call<br>> manager Cluster where the pub and Sub are connected over a WAN. I was<br>
> thinking H323 or SIP, I don't think MGCP will be as good over the WAN.<br>> Looking for some advices.<br>><br>> Thank you<br>> Akaal<br></div></div>> ------------------------------------------------------------------------<br>
><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><br></blockquote></div><br>