[cisco-voip] Phone limits per server
Wes Sisk
wsisk at cisco.com
Wed Mar 10 16:25:56 EST 2010
inline, ws.
On Wednesday, March 10, 2010 3:49:54 PM, Matthew Saskin
<msaskin at gmail.com> wrote:
> 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)
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:
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.
This is a required field.
Default: 5000
Minimum: 5000
Maximum: 15000
>
> 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 :)
>
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.
> Matthew Saskin
> msaskin at gmail.com <mailto:msaskin at gmail.com>
> 203-253-9571
>
> July 18, 2010 - 1500m swim (in the hudson), 40k bike, 10k run
> Please support the Leukemia & Lyphoma Society
> http://pages.teamintraining.org/nyc/nyctri10/msaskin
>
>
> On Wed, Mar 10, 2010 at 3:40 PM, Jason Aarons (US)
> <jason.aarons at us.didata.com <mailto:jason.aarons at us.didata.com>> wrote:
>
> 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.
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net
> <mailto:cisco-voip-bounces at puck.nether.net>
> [mailto:cisco-voip-bounces at puck.nether.net
> <mailto:cisco-voip-bounces at puck.nether.net>] *On Behalf Of *Lelio
> Fulgenzi
> *Sent:* Wednesday, March 10, 2010 9:45 AM
> *To:* Jeremy Rogers
> *Cc:* cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> *Subject:* Re: [cisco-voip] Phone limits per server
>
>
>
> 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.
>
> 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).
>
> With each revision of hardware, I suspect they would handle 7500
> devices without blinking.
>
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Cooking with unix is easy. You just sed it and forget it.
> - LFJ (with apologies to Mr. Popeil)
>
>
> ----- Original Message -----
> From: "Jeremy Rogers" <Jeremy.Rogers at ip-soft.net
> <mailto:Jeremy.Rogers at ip-soft.net>>
> To: cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> Sent: Wednesday, March 10, 2010 9:02:05 AM GMT -05:00 US/Canada
> Eastern
> Subject: [cisco-voip] Phone limits per server
>
>
> 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?
>
> Also, since each gateway endpoint is a “device” is there a major
> weighting difference between FXO/FXS endpoints and PRI endpoints
> for capacity planning?
>
>
>
> Jeremy Rogers
>
> Network Management
>
>
>
>
>
>
> _______________________________________________ cisco-voip mailing
> list cisco-voip at puck.nether.net
> <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ------------------------------------------------------------------------
>
> *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. *
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100310/516175b7/attachment.html>
More information about the cisco-voip
mailing list