Aggregate Session Constraints for SIP
You can set a full suite of session constraints and then apply them to a SIP interface. The session constraints configuration contains many of the same parameters as the session agent, so you can configure a group of constraints and then apply them to a SIP interface/
The SIP interface configuration’s constraint-name parameter invokes the session constraint configuration you want to apply. Using the constraints you have set up, the Oracle® Enterprise Session Border Controller checks and limits traffic according to those settings for the SIP interface. Of course, if you do not set up the session constraints or you do not apply them in the SIP interface, then that SIP interface will be unconstrained. If you apply a single session-constraint element to multiple SIP interfaces, each SIP interface will maintain its own copy of the session-constraint.
SIP interfaces now have two states: “In Service” and “Constraints Exceeded.” When any one of the constraints is exceeded, the status of the SIP interface changes to Constraints Exceeded and remains in that state until the time-to-resume period ends. The session constraint timers that apply to the SIP interface are the time-to-resume, burst window, and sustain window.
Aggregate Session Constraints Configuration
This section shows you how to configure aggregate session constraints and then apply them to a SIP interface.
The session constraints configuration contains many of the same parameters as the session agent does; it also incorporates the changes to the session agent parameters that are described in this section.
To configure the session constraints:
Applying Session Constraints in a SIP Interfaces
In the SIP interface, there is a new parameter that allows you to use a set of session constraints for that interface; the parameter is called constraint-name.
To apply session constraints to a SIP interface:
Configuring CAC Policing and Marking for non-Audio non-Video Media
In the media profile and the media policy configurations, the following values have been added for the media-type parameter:
- application | data | image | text
For the media policy, these new values apply to ToS marking.
Support for the AS Bandwidth Modifier
Two new parameters have been added to the media profile configuration:
- sdp-bandwidth—Enable or disable the use of the AS modifier in the SDP if the
req-bandwidth and
sdp-rate-limit-headroom parameters are not set to valid values in a corresponding media profile. The default value is
disabled. The valid values are:
- enabled | disabled
- sdp-rate-limit-headroom—Specify the percentage of headroom to be added while using the AS bandwidth parameter while calculating the
average-rate-limit (rate limit for the RTP flow). The default value is zero (0). The valid range is:
- Minimum—0
- Maximum—100
The following conditions apply to the use and application of these two new parameters:
- If the amount of required bandwidth is not specified in the media profile (req-bandwidth) for the media type in the m= line of the SDP, then the value specified in the AS modifier is used. The Oracle® Enterprise Session Border Controller only uses the AS value if you set the new sdp-bandwidth to enabled.
- If the average rate limit value for RTP flows is not specified in the media profile (average-rate-limit) for the media type in the m= line of the SDP, then the value specified in the AS modifier is used. The system only uses the AS value if you set the new sdp-bandwidth to enabled. When calculating the average rate rate limit that it will use based on the AS modifier, the Oracle® Enterprise Session Border Controller applies the percentage set in the sdp-rate-limit-headroom parameter.
- The Oracle® Enterprise Session Border Controller uses the value specified in the AS modifier (if sdp-bandwidth is enabled, and req-bandwidth is set to 0) along with the user-cac-bandwidth value set in the realm configuration; this works the same way that the req-bandwidth parameter does.
- The system uses the value specified in the AS modifier (if sdp-bandwidth is enabled, and req-bandwidth is set to 0) along with the max-bandwidth value set in the realm configuration; this works the same way that the req-bandwidth parameter does.