Constraints for Proxy Mode

The Oracle® Enterprise Session Border Controller applies session router and session agent constraints when it is in proxy (transaction or stateless) mode if you enable the ACLI constraints parameter for a session agent. However, the Oracle® Enterprise Session Border Controller does not track SIP sessions when in transaction mode, so the following session-specific constraints are not applied:

• max-sessions
• max-inbound-sessions
• max-outbound-sessions
• min-seizures
• min-asr

Constraints the Oracle® Enterprise Session Border Controller applies are:

• max-burst-rate
• max-inbound-burst-rate
• max-outbound-burst-rate
• max-sustain-rate
• max-inbound-sustain-rate
• max-outbound-sustain-rate

In order to set the desired time windows for computing burst rates and sustain rates, you also need to configure these parameters in the session agent configuration: burst-rate-window and sustain-rate-window. You can also set the time-to-resume and in-service-period parameters to control how long to wait before bringing a session agent back into service after its constraints are no longer exceeded.