SBC Provisioning Limits

Number of IP Addresses per Call Leg Size

The number of call legs supported for a given number of IP Addresses on different SBC platforms are as follows:

• Unable to show "metadata-from": No such page "_space_variables"
  , assuming UDP ports 4,000 through 64,444 are configured for media port usage - See table below.
• Unable to show "metadata-from": No such page "_space_variables"
   with 10GE interfaces - Supports a maximum of 75000 sessions, requiring 4 IP addresses per call leg.
• Unable to show "metadata-from": No such page "_space_variables"
  - Supports a maximum of 64000 sessions, requiring 3 IP addresses per call leg.

For 

media resource allocation scenarios, the  requires a minimum of 10 IP addresses configured to support 150,000 call legs (one Primary IP address plus 9 alternate IP addresses in non-VLAN configuration).

For example, to use 100,000 call legs you must configure at least six (6) IP addresses because five IP addresses will only allow up to 96,000 call legs through the

.

The  

supports configuring up to 14 alternate media addresses. For more details, see Alternate Media IP Addresses Support.

Configuration Limits

The 

supports a large number of configurable objects and is capable of supporting from a few very large customers to thousands of small customers. Important details about the provisioning system include:

• Interactive provisioning of configuration objects (such as commands typed at the CLI or entered in the EMA or EMS) does not affect call handling or capacity.
• Provisioning behavior does not depend on the number of existing entities. The addition of the 10,000th instance is roughly comparable to adding the 1st such instance.

Provisioning Limits

provisioning limits are shown in the following table.

The time required to add an object to an existing configuration is immaterial (It takes much longer to actually type the command or complete the EMA/EMS fields). However, bulk loading of a large configuration from the CLI may take a substantial amount of time. 

While the 

supports large limits on multiple types of configuration objects, a few typical usage scenarios exist. The length of time to bulk load a configuration depends on the size of the configuration. Consequently, four profile classes are defined to give customers a rough idea for the bulk loading time relevant to their configuration:

• 1K profile – comprised of 1,000 instances each of Address Contexts, Zones, IP Interface Groups, IP Interfaces, Signaling Ports, and Trunk Groups
• 4K profile – comprised of 4,000 instances each of Address Contexts, Zones, IP Interface Groups, IP Interfaces, Signaling Ports, and Trunk Groups
• 4K/10K profile – comprised of 4,093 instances of IP Interfaces, 2,048 instances each of Zones, Address Contexts, IP Interface Groups, SIP Signaling Ports, 10,000 IP Peer, and 10,000 IP Trunks (see Note below).
• 4K/40K profile [SBC 7000 series only] – comprised of 4,000 instances each of Address Contexts, Zones, IP Interface Groups, IP Interfaces, Signaling Ports; and 40,000 Trunk Groups

SIPREC-based Recording Limitations

Maximum CLI Load Times

The following table lists the maximum CLI load times for the above profile classes.

For a system previously loaded with configuration, the start-up time also depends on the amount of configuration. The start-up time is considered the time from when the

application is started (by PM) to the time that the is ready to accept calls.

Note that this start-up time is typically only relevant to standalone systems after an upgrade. For a HA system, the standby is activated to handle calls while the SBC is being started or restarted. 

Approximate Start-up Times for Standalone SBC

The following table lists the approximate start-up times for a standalone

based on its configuration profile: