Session Agent Minimum Reserved Bandwidth

You can assign session agents minimum bandwidth, applicable in accessOracle® Enterprise Session Border Controller deployments. Assigning a session agent minimum bandwidth can prevent overloading other network devices—such as another Oracle® Enterprise Session Border Controller configured as a session agent. Doing so assures signaling bandwidth and availability to the endpoints behind this Oracle® Enterprise Session Border Controller. This feature is only available on the Acme Packet 4500.

In the following diagram, the internal Oracle® Enterprise Session Border Controller is configured as a session agent on the platform Oracle® Enterprise Session Border Controller (which conveys traffic to the core realm). Setting up bandwidth reservation allows for the creation of only one allocated flow, and secures bandwidth for all the SIP clients behind the internal Oracle® Enterprise Session Border Controller. Contrast this scenario with the one where the platform Oracle® Enterprise Session Border Controller must allocate multiple flows for many SIP clients.

When you configure minimum reserved bandwidth for session agent to a non-zero value, the Oracle® Enterprise Session Border Controller allocates a separate pipe for per session agent. This is achieved by setting up an access control configuration in a specific way, instructing the Oracle® Enterprise Session Border Controller to use a minimum number of transmission timeslots the individual pipe is guaranteed to receive.

This feature works across both signaling services: SIP and H.323. No more than 4000 session pipes are supported.