Diameter AVPs for MATRIXX Policy Application
MATRIXX Engine supports the Sy and Gx interfaces for policy control.
The MATRIXX Diameter Dictionary is defined in the diameter_dictionary.xml file and has definitions for the Diameter AVPs, functions,
and Diameter-to-MDC mappings implemented in MATRIXX Engine.
Note: Most
AVPs are mapped to an MATRIXX Data Container (MDC) field, but this is not required. If the AVP is not mapped, it is not used during processing. One reason not to map an
AVP to an MDC field is when the AVP is sent to MATRIXX Engine but it is not used during rating. The presence
of the AVP makes it known to MATRIXX Engine, so an error message about an unknown AVP is not logged. Another
reason not to map an AVP is when it is in a grouped AVP and is not used.
AVPs that are received by Diameter Gateway but not specified in the appropriate <request> or <answer> section in the diameter_dictionary.xml file are logged as an error in the mtx_debug.log file.
Grouped AVPs are indented under their parent AVPs in the following tables.
Note: For more information about MATRIXX Engine Diameter support, see MATRIXX Diameter Integration.