Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 17
MME Enhancements for 17.3 ▀
Release Change Reference, StarOS Release 17 ▄
267
When the default is overridden with the new
peer-msc
command, the output of the
show configuration
command will indicate:
peer-msc interface-type sv weight
CSCuu18023 - MME standards violation - IDA without Supported-Features AVP
Feature Changes
Supported-Features AVP Always for ISDA
Previous Behavior: The MME sent the Diameter AVP Supported-Features in the Insert Subscriber Data Answer
(ISDA), only if the Supported-Features AVP was present and matched with the MME’s Supported-Features AVP
including the Vendor-ID and Feature-List-ID.
(ISDA), only if the Supported-Features AVP was present and matched with the MME’s Supported-Features AVP
including the Vendor-ID and Feature-List-ID.
New Behavior: In compliance with 3GPP TS 29.272, now the MME always sends the Supported-Features AVP in
ISDA messages, even if the Supported-Feature AVP is not present in the ISDR. And, if the Feature-List value in the
ISDR differs from the MME's Feature-List, then the Feature-List value in the ISDA will be the negotiated value.
ISDA messages, even if the Supported-Feature AVP is not present in the ISDR. And, if the Feature-List value in the
ISDR differs from the MME's Feature-List, then the Feature-List value in the ISDA will be the negotiated value.
Support for the Supported-Features AVP is documented in the AAA Interface Administration and Reference for Release
18 with M-bit information included in the Diameter Attribute Quick Reference table of that manual.
18 with M-bit information included in the Diameter Attribute Quick Reference table of that manual.