<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
not by total number of calls, only by BHCA and processing ability of
the servers terminating the ICT. H.323, the underlying protocol for
ICT, is one of the 'heavier' protocols that takes considerable memory
and CPU. I believe the quoted sustainable max for h.323 cps is around
4cps. I have seen higher achieved and CM has an valve around 40-43
cps. However, you have to do serious tuning to get to 43cps and it is
not sustainable.<br>
<br>
/wes<br>
<br>
On Monday, November 24, 2008 5:07:37 AM, FrogOnDSCP46EF
<a class="moz-txt-link-rfc2396E" href="mailto:ciscoboy2006@gmail.com"><ciscoboy2006@gmail.com></a> wrote:<br>
<blockquote
cite="mid:92ed69a80811240207r1e2615bck34e4be48822399c2@mail.gmail.com"
type="cite">Hi Gang,<br>
<br>
cluster1-----------ICT trunk-----------------cluster2<br>
<br>
Is there any limitation on how many calls we can send back and fourth
at a certain BHCA between cluster?<br>
In other word is there any benchmarking done by Cisco?<br>
<br clear="all">
<br>
-- <br>
Smile, you'll save someone else's day!<br>
Frog<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</body>
</html>