<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">You don't want to do it that way. Use CM Groups to do load balancing.<div><br></div><div>once that parameter is exceeded CM simply rejects registration requests. That parameter has some interesting history as well where route lists, hunt lists, built in bridge devices from ip phones, and other random software / virtual devices are counted.</div><div><br></div><div>/Wes</div><div> </div><div><div><div>On Jan 26, 2009, at 3:02 AM, FrogOnDSCP46EF wrote:</div><br class="Apple-interchange-newline"><br>Holiday today, just sitting at home on the couch with a glass of red wine. I was doing nothing so I started flocking through CCM 6x parameters.<br><br>A parameter which drew my attention was "Maximum number of register device" in call manager service parameter.<br> <br>I am trying to figure out the best way to load balance IP phone registration to all subscribers.<br><br>Sales department has 1500 IP phones.<br><br>I have 3 subscribers - Sub1, sub2, sub3<br>Call manager group = sales_cm-group = Sub1, Sub2, Sub3<br> <br>Device pool for Sales department: "DP_Sales" = sales_cm-group (sub1,sub2,sub3)<br><br>If I have set 'max number of register device' = 400 in each subscriber's service parameter.<br>How would it behave?<br> <br>Just talking to myself:<br><br>1. First 500 phones will register to Sub1.<br>2. Then next lot, 501 to 1000 phones will register to Sub2. This is bcoz Sub1 has reached its limit of 500. So Phone#501 will try to register to second subscriber #sub2 (hunting through list).<br> <br>3. Then following Sub3 will register 1001 to 1500 coz sub1 and sub2 has reached their limits.<br><br>If it works, this could be a good way to do load-balancing. Am I right?<br><br>-frog<br><br><br><table class="content-form"> <tbody><tr><td valign="top"><a name="MaxTotalNumberOfRegisteredCallingEntities"> <label for="NAME"><b>Maximum Number of Registered Devices:</b> <img alt="Required Field" src="https://172.16.16.11:8443/ccmadmin/themes/VtgBlaf/required.gif"> </label> </a></td> <td> 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 and built in bridges. </td> </tr> <tr> <td> </td> <td> This is a required field. </td> </tr> <tr> <td> </td> <td> Default: 5000 </td> </tr> <tr> <td> </td> <td> Minimum: 5000 </td> </tr> <tr> <td> </td> <td> Maximum: 15000 </td></tr></tbody></table><br><br>-- <br>Smile, you'll save someone else's day!<br>Frog<br> _______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div><br></div></body></html>