Home
MATRIXX Administration
Appendixes
MATRIXX Engine Scripts
You can use the following scripts to support servers, clusters, engines, pricing domains, system logging, notification messaging, and event-repository storage. Use them to gather information, perform maintenance operations, such as starting and stopping servers, configure system behavior, and manage engine failover operations.
Configuration, Demo, and Test Scripts
Use these scripts to configure MATRIXX Engine, create demos, and test system functionality.
create_diameter_packets_from_wireshark_trace_file.py
This script reads Diameter Gateway packet log entries from a Wireshark trace file and creates a Python script that re-sends the Diameter packets to the MATRIXX Engine. It also creates a script that verifies that the Diameter Gateway responses are the same as those in the input log file. This script is useful for verifying that diameter packets are processed correctly or for recreating an issue with processing.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
- About MATRIXX Administration
  MATRIXX Administration describes how to monitor MATRIXX Engine components and to perform daily operations for maintaining a geographically redundant system. This includes administration for the engine, Traffic Routing Agent, MATRIXX gateways and web apps, and Notification Framework. It also provides information about recovering from a total system failure.
- Administering MATRIXX Engine
  The topics in this section have information about maintaining, managing, and resolving issues with a MATRIXX Engine installation.
- Administering MATRIXX Traffic Routing Agent
  The topics in this section describe administering Traffic Routing Agent (TRA) servers, including starting and stopping Traffic Routing Agent nodes and clusters. The information in this section applies to all Traffic Routing Agent functions unless otherwise noted.
- Administering the Route Cache
  The topics in this section describe administering the Route Cache.
- Administering US Tax Data
  US tax data is imported from CCH tax data, compiled in My MATRIXX, and output as compact MATRIXX Data Container (MDC) files, including an MDC file containing tax database metadata and status information. MDC files are packaged into a .zip file and loaded into the MATRIXX tax database.
- Troubleshooting Issues
  This section has information to help identify and resolve system issues.
- Appendixes
  - Admin Service Commands
    The Admin Service includes commands for administering MATRIXX components.
  - Engine Validation Error Codes
    The following return codes can be written to the system log when a network message is processed.
  - Python Value Type to AVP Type Mapping
    The following table describes how Python value types are mapped to AVP types.
  - MATRIXX Engine Scripts
    You can use the following scripts to support servers, clusters, engines, pricing domains, system logging, notification messaging, and event-repository storage. Use them to gather information, perform maintenance operations, such as starting and stopping servers, configure system behavior, and manage engine failover operations.
    - Analytical and Informational Scripts
      Use the scripts in this section to gather information about system performance, system topology, performance statistics, system configuration, and MATRIXX Engine versioning. All scripts run locally on a server as user mtx.
    - Configuration, Demo, and Test Scripts
      Use these scripts to configure MATRIXX Engine, create demos, and test system functionality.
      - configure_engine.py
        Use the configure_engine.py to propagate configuration changes to all servers in a MATRIXX Engine cluster. This script is run as user mtx.
      - create_config.py
        The create_config.py script updates the configuration settings on either a MATRIXX Engine server or on a TRA-RT-(SI/DR) server using the configuration question answers specified in their create_config.info files and any modifications in sed.extra files.
      - create_demo.py
        The create_demo.py script is an interactive script that generates several scripts and data files you can use to create subscriber and pricing data, load it into the MATRIXX Engine databases, and pass event messages through the system. Use it to set field values in subscriber-related MDCs and to test and demonstrate MATRIXX functionality.
      - create_diameter_packets_from_log_file.py
        This script reads Diameter Gateway packet log entries from a log file and creates a Python script that resends the Diameter packets to MATRIXX Engine. It also creates a script that verifies that the Diameter Gateway responses are the same as those in the input log file. This script is useful for verifying that diameter packets are processed correctly or for recreating an issue with processing.
      - create_diameter_packets_from_wireshark_trace_file.py
        This script reads Diameter Gateway packet log entries from a Wireshark trace file and creates a Python script that re-sends the Diameter packets to the MATRIXX Engine. It also creates a script that verifies that the Diameter Gateway responses are the same as those in the input log file. This script is useful for verifying that diameter packets are processed correctly or for recreating an issue with processing.
      - delete_old_transaction_logs.py
        The delete_old_transaction_logs.py script deletes transaction log files that are obsolete because they are included in a checkpoint file. The log files are deleted until the specified target is reached or all obsolete transaction logs are removed.
      - run_test.py
        The run_test.py script calls a number of scripts that are generated by the create_demo.py script to perform all operations necessary to test and run a demonstration of the MATRIXX Engine functionality. The run_test.py script requires that the MATRIXX Engine is started.
    - Server Administration Scripts
      Use the following server administration scripts to administer MATRIXX Engine servers.
    - Cluster Administration Scripts
      Use the cluster administration scripts to start, stop, restart, and check the status of all logical servers in a cluster and to sync all MATRIXX directories on all servers in the cluster.
    - Engine Administration Scripts
      Use the following engine administration scripts to administer the MATRIXX Engine.
    - Control Scripts for Containerized Installations
    - Failover Scripts
      Use these scripts to publish MATRIXX and clean up orphaned transaction log files after an engine failover.
    - Provisioning Scripts
      Use these scripts to provision data in the MATRIXX database.
  - Scripts and Utilities for MATRIXX Gateways and Web Apps
    Use the following scripts to administer MDC Gateway, Gateway Proxy, RS Gateway, and other MATRIXX gateways and web apps.
  - Traffic Routing Agent Administration Scripts
    Use the following scripts to administer Traffic Routing Agents (TRAs), to check the status of a TRA server, or to validate the TRA configuration.
  - MATRIXX Data Container Field Data Types
    MATRIXX Engine supports several data types for its network message MATRIXX Data Containers (MDCs) and database object MDCs. When you define custom MDCs and MDC fields, you must specify one of these data types for the fields.
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

create_diameter_packets_from_wireshark_trace_file.py

This script reads Diameter Gateway packet log entries from a Wireshark trace file and creates a Python script that re-sends the Diameter packets to the MATRIXX Engine. It also creates a script that verifies that the Diameter Gateway responses are the same as those in the input log file. This script is useful for verifying that diameter packets are processed correctly or for recreating an issue with processing.

Syntax

create_diameter_packets_from_wireshark_trace_file.py -h | -a | -d | -i input_log_file | -o outfile | -s skip_list | -u

Options

-h: Displays help information for this script.
-a, --answers_only: If specified, only Diameter Answer packets are processed. The default is to process all packets.
-d: Runs the script in debug mode. If this option is specified, more messages are returned to assist in debugging.
-i input_log_file: Identifies the log file that has the Diameter Gateway packet log entries.
-o outfile, --outfile=outfile: Specifies the output Python filename. For example, create_test_packets.py. The default is create_and_send_packets.py.
-r, --requests_only: If specified, only Diameter Request packets are processed. The default is that all packets are processed.
-s skip_list, --skip_list=skip_list: Specifies a list of comma-separated numeric values (Diameter command values) to skip. For example, to skip the Device-Watchdog packets, then enter 280. To skip the Capabilities-Exchange packets, then enter 257. To skip both, enter "280, 257".
-u, --unit_test: If specified, the output is formatted to be able to be copied into a unit test script which can verify the results from a Diameter Request matches the Diameter Answer in the log.