Home
MATRIXX Diameter Integration
Diameter Gateway
The following information describes the Diameter Gateway.
Supported AVPs
The MATRIXX Diameter Dictionary is defined in the diameter_dictionary.xml file and contains definitions for the Diameter AVPs, functions, and Diameter-to-MDC mappings implemented in MATRIXX Engine.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
- About MATRIXX Diameter Integration
  MATRIXX Diameter Integration provides information about MATRIXX Engine Diameter support and configuration.
- Diameter Gateway
  The following information describes the Diameter Gateway.
  - Diameter Gateway Overview
    Diameter Gateway is a Diameter server that allows communication between MATRIXX Engine and a network entity requesting service through the Diameter protocol.
  - Diameter Gateway Support for 5G Non-Standalone Architecture
    MATRIXX supports 5G Non-Standalone Architecture deployments by including extended fields for 5G RAN in Gx messages to enable the high-bandwidth data flows available in 5G networks.
  - Supported AVPs
    The MATRIXX Diameter Dictionary is defined in the diameter_dictionary.xml file and contains definitions for the Diameter AVPs, functions, and Diameter-to-MDC mappings implemented in MATRIXX Engine.
    - Common
      This section lists the Common application AVPs by command name. For more information, see the 3GPP Specification.
    - NASREQ
      This section lists the Network Access Server Requirements (NASREQ) application AVPs by command name. For more information, see the 3GPP Specification.
    - Accounting
      This section lists the Accounting application AVPs by command name. For more information, see the 3GPP Specification.
    - Credit-Control
      This section lists the Credit-Control application AVPs by command name. For more information, see the 3GPP Specification.
    - DiameterWrappedMDC
      This section lists the DiameterWrappedMDC application AVPs by command name.
    - Diameter AVPs for MATRIXX Policy Application
      MATRIXX Engine supports the Sy and Gx interfaces for policy control.
  - Configuring the Diameter Protocol
    You can configure and customize the Diameter Dictionary and the Diameter protocol.
  - Working with the Diameter Protocol
    The Diameter protocol is comprised of two basic parts: the Diameter Base Protocol and Diameter applications.
  - Handling VoLTE Announcements
    MATRIXX Engine can return Voice over Long-Term Evolution (VoLTE) Announcement-Information AVPs for Diameter LTE (Long-Term Evolution) sessions. The AVPs define the list of pre-quota announcements to play to the subscriber using VoLTE technology.
  - Handling Diameter Errors
    Errors with the Diameter protocol fall into two categories: protocol errors and application errors.
- External Diameter Gateway
  The following information describes External Diameter Gateway (EDGW).
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Supported AVPs

The MATRIXX Diameter Dictionary is defined in the diameter_dictionary.xml file and contains 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 will not be 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 will not get 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 the 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.