Avaya CS 1000 Fundamentals page 119

Load Balancing for SIP DECT high capacity
Consider the following factors when you plan the interaction between a Communication Server
1000 and SIP DECT and when the anticipated number of DECT handsets in SIP DECT
systems is large (greater than 200).
• SIP Line server capacity: The SIP Line capacity calculation varies based on the
Communication Server 1000 hardware type and the deployment type.
- SIP Line requires a separate CP PM or COTS server. For more information about
the CP PM platform, see Avaya Co-resident Call Server and Signaling Server
Fundamentals, NN43001-509. For more information about COTS platforms, see
Avaya Linux Platform Base and Applications Installation and Commissioning,
NN43001-315.
- For information about the estimated maximum number of supported SIP Line users
(SIP DECT Handsets) on SIP Line servers, see Avaya Communication Server
1000E Planning and Engineering, NN43041-220.
- The software limit for the number of SIP Line users on one SIP Line server is 1800;
a traffic capacity limit also exists.
• SIP DECT system capacity: A SIP DECT system can support approximately 6000 SIP
DECT Handsets on a single system (256 DAPs with 25 subscriptions for each DAP).
• Determine the number of SIP Line servers.
• SIP DECT load balancing configuration: Communication Server 1000 SIP Lines Node
does not support load balancing of SIP user registration between a Leader and Followers
in the same node. An administrator must add more SIP Line Nodes on the same
Communication Server 1000 system to maintain more SIP users than are allowed by a
single SIP Line server.
SIP DECT system supports load balancing of DECT Handsets between SIP Proxies
based on a DN prefix. An administrator must calculate the overall number of SIP DECT
Handsets in the system and determine DN prefixes for every SIP Line Node so that every
SIP Line Node (DNR Proxy record) does not have more SIP DECT users assigned than
is supported based on the number of SIP Line servers.
SIP DECT configuration is adjusted with the list of SIP Line Node IPs and DN prefixes
assigned. You must select the Multiple Gatekeepers option to perform load balancing.
Figure 37: Load balancing configuration
balancing configuration on a SIP DECT system with three SIP Line nodes. In this example
- The primary proxy for DNs starting with 50 is 192.168.32.135.
SIP DECT Fundamentals
Note:
You must save the system and restart the DAPs to activate the new
configuration.
Multiple-site mobility network configuration
on page 120 shows an example of load
October 2012 119