...
Caption | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Footnotes 1 - The aggregate number of IP trunk groups (SIP + GW + H.323) cannot exceed 40,000. As a best practice, do not provision more than 20,000 trunk groups in a single zone. 2 - The aggregate number of IP trunk groups (SIP + GW + H.323) cannot exceed 10,000. 3 - Includes approximately 40,000 IP ACLs for peers, 10,000 IP ACLs for signaling ports (2 x 4,000 SIP, 2,000 H323) and 100 IP ACLs for OAM. 4 - Includes approximately 10,000 IP ACLs for peers, 4,000 IP ACLs for signaling ports and 100 IP ACLs for OAM. 5 - In earlier SBC SWe releases, the provisioning limits in this table were not enforced. As a result, when upgrading to 5.x from a pre-5 .x release and the system includes more than 128 trunk groups and/or address contexts, the system will operate normally. Plus, trunk groups/address contexts may be deleted with no ill effect. However, no new trunk groups or address contexts may be added in excess of the 128 limit.6 - SBC SWe supports a maximum of 64 alternate media IP addresses per vNIC. |
...