<div class="gmail_quote">On Wed, Mar 4, 2009 at 10:54 PM, Wes Sisk <span dir="ltr"><<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
ICT capacity should be unlimited with a couple exceptions:<br>
1. call rate - CM can only accept ~4call per second for h.323<br>
2. locations bandwidth configuration - allows you to limit total calls
if you desire<br>
<br>
after that you can route essentially unlimited calls over ICT until you
literally crush CM. If you're getting route list exhausted in means CM
is trying to hunt through the routelist. Usually this only happens if
h225 setup fails for ICT. detailed SDL traces and careful eye will
spot the reason. Otherwise a packet capture looking at traffic on
TCP:1720 will provide pretty directly clues.<br>
<br>
every call establishes a new TCP session to the remote cluster on
tcp:1720.<br>
<br>
</div>
</blockquote></div>Thanks Wes,<br><br>What I fear is that I have a routing loop at work that spikes things periodically. Every once in awhile, I get a <30 sec spike on the counter CallsRejectedDueToICTThrottling, and the Route List Failed seems to correlate. I am pretty sure I don't ever maintain >4 cps...maybe in a burst every once in awhile.<br>
<br clear="all"><br>-- <br>Dave Wolgast<br>Livonia, NY<br>