Required Information

The config_engine.py script enables you to add simple AVPs, grouped AVPs, and Diameter applications to your base MATRIXX configuration. It also allows you to map MATRIXX result codes to Diameter results codes.

Diameter Setup Information

To add AVPs to a Diameter packet, you must provide the following information about the Diameter configuration:
  • The Diameter realm, for example company.com.
  • The Diameter source host name, for example source.company.com.
  • An IP address that the Diameter Capabilities Exchange can return.
  • The IP address of the Diameter host system.
  • The Vendor ID and name (Optional).

Simple AVP Information

To add simple AVPs to a Diameter packet, provide the following information:
AVP Name
The name of the Diameter AVP.
AVP Code
An integer that distinguishes the AVP in Diameter. The code must be unique among all AVP types of the same vendor name.
AVP Type
The AVP data type. AVP data types are defined in the Diameter Dictionary.
AVP Vendor Name
(Optional) The vendor to which the AVP is specific. MATRIXX Engine supports the 3GPP vendor so you do not need to add it.
MDC Field Name
The name of the MDC field to which the AVP is mapped. MATRIXX Engine will not recognize a new AVP value if it is not mapped to an MDC field.

Grouped AVP Information

To add grouped AVPs to a Diameter packet, provide the following information:
Grouped AVP Name
A descriptive name for the grouped AVP.
Grouped AVP Code
An integer that distinguishes the grouped AVP in Diameter. The code must be unique among all AVP types of the same vendor name.
Fixed AVP Name
The name of each fixed AVP in the grouped AVP. You can configure the maximum number of times the AVP may occur.
Required AVP Name
The name of each required AVP in the grouped AVP. You can configure the maximum number of times the AVP may occur.
Optional AVP Names
The name of each optional AVP in the grouped AVP. You can configure the maximum number of times the AVP may occur.
AVP Vendor ID Name
(Optional) The vendor to which the grouped AVP is specific.
MDC Field Name
The names of the MDC fields to which the required and optional AVPs are mapped. MATRIXX Engine will not recognize a new AVP value if it is not mapped to an MDC field.

Result Code Mapping

A result code mapping identifies a result code that MATRIXX Engine assigns to an accounting request and maps the code to a Diameter result code. The code is returned in the Diameter Result-Code AVP.

To add a new result code mapping, provide the following information:
Code
A descriptive name for the results code mapping.
Error Code Range
From and To values that define a range of values that can contain the error code. For result codes that can only be a single value, the From and To values are the same.
Diameter Mapping Code
The Diameter code to return when the error result is generated by a MATRIXX blade.

Diameter Application Information

To add a Diameter application to be used by the MATRIXX Charging Application or the MATRIXX Policy Application during processing, provide the following information:
Application Name
The Diameter application name.
Application Code
The code identifying the Diameter application.
Diameter Command
The name of the command used by the Diameter application.
Command Code
The code to assign to the request and response messages.
Proxiable
Sets whether the message can be routed through proxies toward the destination realm. Valid values are true and false. Non-proxiable messages are routed to the next hop and are never forwarded. If you set the proxiable value to true, the application request message must contain the Destination-Realm AVP.
Request Message MDC Name
The name of the MDC message to which the Diameter request packet is mapped.
Response Message MDC Name
The name of the MDC message to which the Diameter response packet is mapped.
AVP Names
The names of all simple and grouped AVPs contained in the request and response messages.