[cisco-voip] Multiple subscriber phone load balancing - interesting

[Wes Sisk]

You don't want to do it that way.  Use CM Groups to do load balancing.

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.

/Wes

On Jan 26, 2009, at 3:02 AM, FrogOnDSCP46EF wrote:


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.

A parameter which drew my attention was "Maximum number of register  
device" in call manager service parameter.

I am trying to figure out the best way to load balance IP phone  
registration to all subscribers.

Sales department has 1500 IP phones.

I have 3 subscribers - Sub1, sub2, sub3
Call manager group = sales_cm-group = Sub1, Sub2, Sub3

Device pool for Sales department:   "DP_Sales" = sales_cm-group  
(sub1,sub2,sub3)

If I have set 'max number of register device' = 400 in each  
subscriber's service parameter.
How would it behave?

Just talking to myself:

1. First 500 phones will register to Sub1.
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).

3. Then following Sub3 will register 1001 to 1500 coz sub1 and sub2  
has reached their limits.

If it works, this could be a good way to do load-balancing. Am I right?

-frog


Maximum Number of Registered Devices: 	 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.
  	 This is a required field.
  	 Default:  5000
  	 Minimum:  5000
  	 Maximum:  15000


-- 
Smile, you'll save someone else's day!
Frog
_______________________________________________
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/20090126/2ec25c77/attachment.html>