Home
MATRIXX Diameter Integration
Diameter Gateway
The following information describes the Diameter Gateway.
Working with the Diameter Protocol
The Diameter protocol is comprised of two basic parts: the Diameter Base Protocol and Diameter applications.
Diameter Peer Reporting
The print_diameter_peers.py script reports current peer connections in detail. It includes information about the mapping of destinations to connections.
print_diameter_peers.py
Prints a report of the connected diameter peers.

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.
  - 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.
    - Diameter Applications, Commands, and Messages
      A Diameter application is a networking protocol based on the Diameter base protocol (RFC 3588). Each application is identified by a code and a command. Each command has an assigned command code and has a set of Request and Answer messages, each of which uses the same command code. These messages are converted to MDC format by Diameter Gateway and are the base units used to send the command or deliver a notification between a Diameter client and MATRIXX Engine.
    - Diameter Multiple-Service Credit Control (MSCC)
      A single network message using the Diameter Credit Control Application (DCCA) can include usage for multiple service contexts in one session. In such cases, the MATRIXX Charging Application rates usage for each service context individually and creates a separate Event Detail Record (EDR) for each one.
    - Gy Re-Auth-Request (RAR) Message
      MATRIXX Engine sends a Re-Auth Request (RAR) to the network for a subscriber-management (SubMan) request, when an open session is perceived as inactive, or on content quota expiration.
    - Session Management RAR and Spending Limit SNR Messages
      Gx RARs are sent to the Policy and Charging Enforcement Function (PCEF) or Sy SNRs are sent to the Policy and Charging Rules Function (PCRF) when MATRIXX Policy Application determines that there has been a policy change.
    - Diameter Quantity Unit
      The Diameter Requested-Service-Unit and Used-Service-Unit AVPs can contain AVPs which are used to determine the quantity unit for the incoming event.
    - Diameter Quota Configuration
      Pricing administrators set up quota configurations when they define service types for a pricing plan. Each service type definition is a pricing XML configuration file that has all attributes of the service type. A quota can be specified for an entire service type or for each service context of a service type. When a quota is defined for the entire service type, the quota applies to all service contexts that do not have quotas specified for them.
    - Diameter Quota Authorization
      When a network message using the Diameter Credit-Control (CC) Application requests an authorized quantity before allowing usage, the authorized quantity (the quota) is returned in a response to the network by the MATRIXX Charging Application. The actual authorized quota may be less than the requested quantity.
    - Adaptive Quota Management
      Adaptive Quota Management (AQM) dynamically and automatically adjusts the quota size, reservation size, and validity times by actively monitoring balance and quota consumption velocity and thresholds, eliminating erroneous reporting and service denial. AQM optimizes network communication and the accuracy of balance queries and threshold notifications and is self-adjusting for different services, minimizing the need for service-specific configuration.
    - Balance Accuracy Feedback
      When authorizing a request for a usage of service quota, Balance Accuracy Feedback (BAF) limits the maximum amount and validity times of reservations against each instance of a balance or meter according to parameters configured on the corresponding pricing template.
    - Diameter Total Octet Calculation
      The Diameter CC-Total-Octets AVP contains the total data quantity for a session. When there are multiple service contexts in one session, the value is calculated for each service context. In some Diameter applications (such as Gy/Ro), usage is requested and reported in the grouped AVPs Requested-Service-Unit and Used-Service-Unit respectively. In some situations, a Diameter client does not send the CC-Total-Octets AVP because the AVPs in the Requested-Service-Unit and the Used-Service-Unit grouped AVPs are optional. If the CC-Total-Octets is not sent, you can configure the Diameter Gateway to set CC-Total-Octets to be the sum of the CC-Input-Octets and the CC-Output-Octets AVPs.
    - Diameter Final Unit Indication
      The Diameter Final-Unit-Indication AVP indicates that the Granted-Service-Unit AVP in the Credit-Control (CC) Answer or AA answer message contains the final units for a service or service contexts. After these units have expired, the Diameter credit-control client is responsible for executing the action indicated in the Final-Unit-Action AVP.
    - Diameter Usage Start Time
      To determine which offers and balances are valid at the time of rating and to perform time normalizations, the MATRIXX Charging Application uses its own internal view of time, which is derived from the MtxDiamRoMsg MDC EventTime field. For rating based on data volume (rather than duration), this time is always the EventTime. For rating based on duration, the MATRIXX Charging Application can segment the event based on time.
    - Simulating Diameter Messages
      The diameter_simulator.py script sends diameter packages to a MATRIXX Engine for testing purposes.
    - Diameter Peer Reporting
      The print_diameter_peers.py script reports current peer connections in detail. It includes information about the mapping of destinations to connections.
      - print_diameter_peers.py
        Prints a report of the connected diameter peers.
  - 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

print_diameter_peers.py

Prints a report of the connected diameter peers.

Syntax

print_diameter_peers.py [-h] [-d] [-a ADDRESS] [-v]

print_diameter_peers.py accepts the following options.

-h, --help: Help about the script options.
-a ADDRESS, --address ADDRESS: Specify the management server address:port or hostname:port. If you do not specify an address, the address is determined from the configuration files.
-v , --verbose: Prints all details for each peer entry.
-d, --debug: Debug flag. The default is off (0). If enabled (1), extra messages are printed.