Max-Requested-Bandwidth-UL & Max-Requested-Bandwidth-DL AVPs

These AVPs reflect RTP bandwidth requirements for a call. The default behavior (i.e., no options are configured) that dictates how these AVPs are created follows.

The Oracle Communications Session Border Controller reads b=AS parameter from the media line attributes in the SDP and not from the session level attributes. The average rate limit scenario is when no b=AS: parameter in the SDP and the media-profile, average-rate-limit parameter is configured to a value greater than 0. The Oracle Communications Session Border Controller inserts the media-profile, average-rate-limit parameter ×8 into both Max-Requested-Bandwidth-UL & Max-Requested-Bandwidth-DL AVPs.

The SDP bandwidth scenario is when there is a b=AS: parameter in the SDP and the media-profile configuration element has the following configurations:

  • average-rate-limit = 0
  • sdp-rate-limit-headroom > 0
  • sdp-bandwidth = ENABLED

When these conditions are met, the Max-Requested-Bandwidth-UL & Max-Requested-Bandwidth-DL AVPs are populated with the value in the b=AS: parameter + sdp-rate-limit-headroom ACLI parameter.