My Oracle Support Banner

Max-Requested-Bandwidth value in AVP (UL/DL) of Diameter AAR message is set to 0 by SBC (Doc ID 2815368.1)

Last updated on OCTOBER 22, 2021

Applies to:

Acme Packet Legacy Platform Software - Version S-Cz7.4.0 and later
Information in this document applies to any platform.

Symptoms

Max-Requested-Bandwidth value is set to 0 by SBC in uplink/downlink (UL/DL) in the Diameter message AAR (Authorization Authentication Request)
This is causing mismtach with the far end PCRF, as they expect SBC to be sending 64000, instead of 0 in the uplink/downlink of AAR.

AAR Sample:

Diameter Protocol
     Version: 0x01
     .
     .
     AVP: Media-Component-Description(517) l=1644 f=VM- vnd=Test789
            AVP Code: 517 Media-Component-Description
            AVP Flags: 0xc0, Vendor-Specific: Set, Mandatory: Set
            AVP Length: 1644
            AVP Vendor Id: 3GPP
            Media-Component-Description: 000001234
            .
            .
            .
            AVP: Max-Requested-Bandwidth-UL(516) l=16 f=VM- vnd=TGPP val=0 <<---------------
            AVP: Max-Requested-Bandwidth-DL(515) l=16 f=VM- vnd=TGPP val=0 <<---------------

Changes

Per design, the SBC populates the AVP in Diameter message AAR with UL/DL values, with the bandwidth header b=AS value, when the 183 Session Progress is received with this header from PCRF. If the bandwidth (b) header is not present in the 183 session progress, then SBC should refer the ‘average-rate-limit’ value from the media-profile for the corresponding codec x 8 times. Example: if average-rate-limit is set as 8000, the AVP UL/DL link value sent by SBC will be: average-rate-limit x 8 times i.e. 8000 x 8 = 64000 or 64k

There was media-profile set for codec (in this case for AMR codec) but even then the value was set as 0 by SBC

media-profile
               name                               AMR
               subname                         Test
               media-type                      audio
               payload-type
               transport                         RTP/AVP
               clock-rate                        0
               req-bandwidth                 0
               frames-per-packet          0
               parameters                     max-red=0
                                                      mode-change-neighbor=1
                                                      mode-change-period=2
                                                      mode-set="0,1,2"
               average-rate-limit        8000       <<----------------------
               peak-rate-limit                 0

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.