<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
inline, ws.<br>
<br>
On Wednesday, March 10, 2010 3:49:54 PM, Matthew Saskin
<a class="moz-txt-link-rfc2396E" href="mailto:msaskin@gmail.com"><msaskin@gmail.com></a> wrote:<br>
<blockquote
cite="mid:bbbb0f691003101249t71b458a8i5ba380b19025adc3@mail.gmail.com"
type="cite">
<div>There is a service parameter that will keep you from allowing
more than 5000 phones to register to a single server. It can be
changed, but should only be done so if you're running a server capable
of supporting more than 5K phones (and have run the scenarios through
the capacity tool, etc, caveat emptor)</div>
</blockquote>
ws: Yes, "Maximum Number of Registered Devices", and default is still
5000 in CM 8.0. I believe media resources still count as registered
devices. Built in bridges on phones and huntlists/routelists used to be
included but have since been removed ( CSCef30459, CSCeg36292).
Parameter help:<br>
This parameter specifies the maximum number of devices that can
register with Cisco CallManager and is used to limit the overall
resource demand. Devices that count toward this limit include:
Annunciator devices, H.323 gatekeepers, H.323 phones, H.323 gateways,
ICT trunks (gatekeeper or non-gatekeeper-controlled), MGCP CAS trunks,
MGCP gateways, MGCP FXS ports (analog ports), MGCP FXO ports, MGCP
T1/E1 PRI, media termination points (hardware or software),
transcoders, Music on Hold servers (not MOH audio sources), SIP trunks,
IP phones, conference bridge devices (hardware or software), legacy
Skinny Gateway Control Protocol devices like Cisco Analog Access, and
video conference bridges (IP/VC 3540 configured with Skinny Client
Control Protocol [SCCP] port). The following devices are NOT counted
toward this limit: line appearances (directory numbers), route lists,
Remote Destinations and built in bridges.<br>
This is a required field.<br>
Default: 5000<br>
Minimum: 5000<br>
Maximum: 15000 <br>
<blockquote
cite="mid:bbbb0f691003101249t71b458a8i5ba380b19025adc3@mail.gmail.com"
type="cite">
<div> </div>
<div>Code Red/Code Yellow are different scenarios under which
CallManager will either start throttling call attempts (code yellow) or
outright rejecting call attempts (code red) in an attempt to recover
from some particular problem. I've seen it occur primarily over high
CPU usage, but I'm sure Ryan and/or Wes can/will chime in with more
specifics :)</div>
<div><br clear="all">
</div>
</blockquote>
ws: Code yellow rejects new call attempts. Code Red forces ccm process
to divide by zero on windows or (can't remember the forced exception on
linux) and thereby restart. Code Red used to be enabled by default.
Then it was disabled by default. Now again it is enabled by default.
Code Red is enabled by the CM service parameter "Code Yellow Duration".
This is typically triggered by being CPU bound or disk i/o bound.<br>
<br>
<blockquote
cite="mid:bbbb0f691003101249t71b458a8i5ba380b19025adc3@mail.gmail.com"
type="cite">
<div>Matthew Saskin<br>
<a moz-do-not-send="true" href="mailto:msaskin@gmail.com">msaskin@gmail.com</a><br>
203-253-9571<br>
<br>
July 18, 2010 - 1500m swim (in the hudson), 40k bike, 10k run<br>
Please support the Leukemia & Lyphoma Society<br>
<a moz-do-not-send="true"
href="http://pages.teamintraining.org/nyc/nyctri10/msaskin">http://pages.teamintraining.org/nyc/nyctri10/msaskin</a><br>
<br>
<br>
</div>
<div class="gmail_quote">On Wed, Mar 10, 2010 at 3:40 PM, Jason
Aarons (US) <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">
<div vlink="purple" link="blue" lang="EN-US">
<div>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">In 7x
isn’t there a service parameter around 5000 lines, right (going from
memory) ? So you couldn’t have 5000 7962s with 6 lines on each before
hitting that trigger. As I recall it called something like code red,
etc. </span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p>
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span
style="font-size: 10pt;"> <a moz-do-not-send="true"
href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>
[mailto:<a moz-do-not-send="true"
href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Lelio Fulgenzi<br>
<b>Sent:</b> Wednesday, March 10, 2010 9:45 AM<br>
<b>To:</b> Jeremy Rogers<br>
<b>Cc:</b> <a moz-do-not-send="true"
href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Phone limits per server</span></p>
</div>
</div>
<div>
<div class="h5">
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><span style="font-size: 10pt; color: black;">The
only thing I've heard is that you have to change a service parameter to
up the 7845 from 5000 to 7500 devices and that it's an extra licensing
cost. When you purchase CUCM for 7845 it comes with only 5000
"licenses". To be legit, you need to purchase the RTU license to go up
to 7500.<br>
<br>
I've heard nothing about not using a 7845 for 4000 devices. We
currently run over 3500 devices on each of our 4 7845s (5 year old
hardware too) and have not had any issues (so far, touch wood).<br>
<br>
With each revision of hardware, I suspect they would handle 7500
devices without blinking.<br>
<br>
<br>
---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr. Popeil)<br>
<br>
<br>
----- Original Message -----<br>
From: "Jeremy Rogers" <<a moz-do-not-send="true"
href="mailto:Jeremy.Rogers@ip-soft.net" target="_blank">Jeremy.Rogers@ip-soft.net</a>><br>
To: <a moz-do-not-send="true" href="mailto:cisco-voip@puck.nether.net"
target="_blank">cisco-voip@puck.nether.net</a><br>
Sent: Wednesday, March 10, 2010 9:02:05 AM GMT -05:00 US/Canada Eastern<br>
Subject: [cisco-voip] Phone limits per server<br>
<br>
<br>
</span></p>
<p class="MsoNormal"><span style="color: black;">According to the
SRND for 6.1 you can have a max of 7500 phones on a 7845, however in
side discussions Ive heard mention that this should be limited to no
more than 4000 phones on a server in large deployments. Is that the
case and is there documentation to back it up?</span></p>
<p class="MsoNormal"><span style="color: black;">Also, since each
gateway endpoint is a “device” is there a major weighting difference
between FXO/FXS endpoints and PRI endpoints for capacity planning?</span></p>
<p class="MsoNormal"><span style="color: black;"> </span></p>
<p class="MsoNormal"><span
style="font-size: 10.5pt; color: black; font-family: Consolas;">Jeremy
Rogers</span><span style="color: black;"></span></p>
<p class="MsoNormal"><span
style="font-size: 10.5pt; color: black; font-family: Consolas;">Network
Management</span><span style="color: black;"></span></p>
<p class="MsoNormal"><span
style="font-size: 10.5pt; color: black; font-family: Consolas;"> </span><span
style="color: black;"></span></p>
<p class="MsoNormal"><span style="color: black;"> </span></p>
<p class="MsoNormal"><span style="font-size: 10pt; color: black;"><br>
_______________________________________________ cisco-voip mailing list
<a moz-do-not-send="true" href="mailto:cisco-voip@puck.nether.net"
target="_blank">cisco-voip@puck.nether.net</a> <a
moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</span></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p></p>
<hr size="1">
<p><strong>Disclaimer: This e-mail communication and any
attachments may contain confidential and privileged information and is
for use by the designated addressee(s) named above only. If you are not
the intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of this
email or its contents is strictly prohibited and may be unlawful. If
you have received this communication in error, please notify us
immediately by replying to this message and deleting it from your
computer. Thank you. </strong></p>
</div>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a moz-do-not-send="true" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a moz-do-not-send="true"
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>
<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>