Home
MATRIXX Configuration
Configuring Sub-Domain Routing (Multiple Sub-domains)
In a MATRIXX environment where multiple customer sub-domains are implemented in separate engine chains, you configure sub-domain routing so that traffic is directed to the correct customer sub-domain where the subscriber is homed. You must configure different components across MATRIXX for sub-domain routing to work.
Reference Architecture for Sub-Domain Routing
The reference architecture below demonstrates sub-domain routing configurations across a MATRIXX environment where multiple customer sub-domains exist. See the related links for reference configurations that apply to the Route Cache Controller (RCC), Route Cache, TRA-RT-(SI/DR), Route Cache Proxy (RCP), TRA-PROC with RCP, and engine processing blades.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
- About MATRIXX Configuration
  MATRIXX Configuration describes the tasks required to configure MATRIXX components.
- Configuring MATRIXX Using Helm
  Configure MATRIXX by adding values for properties from the MATRIXX Helm chart in your Helm values file. The MATRIXX Helm chart includes component sub-charts in a hierarchy of reusable components.
- Configuring MATRIXX Engine
  MATRIXX Engine configuration can be applied from a configuration source.
- Configuring Traffic Routing Agent
  Traffic Routing Agent (TRA) configuration can be added to the deployment with a configuration source.
- Configuring Sub-Domain Routing (Multiple Sub-domains)
  In a MATRIXX environment where multiple customer sub-domains are implemented in separate engine chains, you configure sub-domain routing so that traffic is directed to the correct customer sub-domain where the subscriber is homed. You must configure different components across MATRIXX for sub-domain routing to work.
  - Information Requirements for Sub-Domain Routing
    You must configure addresses and ports for sub-domain routing in environments with multiple customer sub-domains. Address and port information must be provided for interfaces that enable route-cache-processing communication across MATRIXX components including the Traffic Routing Agent as a sub-domain router (TRA-RT-(SI/DR)), the Route Cache Controller (RCC) service, the Route Cache Proxy (RCP) service (if in peer-to-peer or dual network mode), and MATRIXX Engine. If Network Enabler is also installed, it uses the same route-cache processing configurations for performing sub-domain routing as the TRA-RT-(SI/DR).
  - RCC Redundancy Configurations (Local and Inter-Site)
    Route Cache Controller (RCC) configurations are required for high availability (HA) to work. This is required for RCC services running at one site (local redundancy) and running at different sites (inter-site redundancy).
  - RCC-L1 Configurations
    Route Cache Controller level 1 (RCC-L1) functionality removes limitations to the number of records held in the routing tables, and ensures that even if the routing table is near to full capacity, new subscriber IDs or session IDs are still added to the tables.
  - Route Cache Sizing and Checkpoint Configurations
    The Route Cache holds subscriber identity data and session identity data that maps either subscribers or sessions to particular customer sub-domains. The Traffic Routing Agent (TRA-RT-(SI/DR)) and the Network Enabler use the Route Cache to look up routing information when processing network requests. You can use the configuration settings below for sizing the Route Cache and creating Route Cache checkpoints.
  - Route Cache Miss Handling
    When a request to look up information in the Route Cache yields a not found error (a cache miss), the requesting application (such as the Traffic Routing Agent, TRA-RT-(SI/DR), or the Network Enabler) issues a resolution request on its local Route Cache domain resolver.
  - Configure the Route Cache Controller
    Perform this task to configure the Route Cache Controller (RCC) service after an initial installation of the MATRIXX software. Perform this procedure for each RCC service that is to run in your environment.
  - Route Cache Controller Configuration Properties
    The Route Cache Controller (RCC) service must be configured to connect to the Route Cache Proxy service and to size the route-cache tables contained in the Route Cache. Set the values for the parameters described in this reference in a Route Cache Controller properties file (for example, rcc_base.cfg). The properties file is used as input to the create_rc_config.py configuration script.
  - Configure an RCC-L1 Instance
    Perform this task to configure the Route Cache Controller level 1 (RCC-L1) service. Perform this procedure for each RCC-L1 service that is to run in your environment.
  - Configure the Route Cache Proxy
    Perform this task to configure the Route Cache Proxy (RCP) service after an initial installation of the MATRIXX software. Perform this procedure for each RCP service that is to run in your environment.
  - Route Cache Proxy Configuration Properties
    The Route Cache Proxy must be configured to connect to the Route Cache Controller, a TRA-RT-(SI/DR), and the engine processing blades. Set the values for the parameters described in this reference in a Route Cache Proxy properties file (for example, rcp_base.cfg). The properties file is used as input to the create_rc_config.py configuration script.
  - Reference Architecture for Sub-Domain Routing
    The reference architecture below demonstrates sub-domain routing configurations across a MATRIXX environment where multiple customer sub-domains exist. See the related links for reference configurations that apply to the Route Cache Controller (RCC), Route Cache, TRA-RT-(SI/DR), Route Cache Proxy (RCP), TRA-PROC with RCP, and engine processing blades.
    - Reference Architecture Quick-Start Setup
      You can use the information in this quick-start to set up the sub-domain routing reference architecture. Before proceeding with the setup, collect the IP/VIP/port information described in each section. For details about configuring the RCC VIPs on the TRA-RT, see the related link about virtual-server/IP (VIP) setup RCC configuration. The RCC setup consists of 3 layers: The RCC configuration in TRA-RT, TRA-PROC with RCP configuration, and the engine configuration.
    - Reference Architecture Description
      The reference architecture below demonstrates sub-domain-routing configurations required in a MATRIXX environment that has multiple customer sub-domains. See related links for reference configurations of the network, hardware, and software components that are configured for sub-domain routing.
    - Reference Architecture Cheat Sheet
      The sub-domain routing configurations in the three layers of the reference architecture include: Route Cache Controller environment, Route Cache Proxy environment, and Engine environment.
    - (Site 1) TRA-RT-(SI/DR) HA Pair Configuration
      You can use the sample Traffic Routing Agent configuration files below for configuring the TRA-RT-(SI/DR) running on the TRA-RT-(SI/DR)-1 host at site 1 in the reference architecture. Similar configuration files would be used for the TRA-RT-(SI/DR) HA peer that runs on the TRA-RT-(SI/DR)-1-S host.
    - (Site 1) RCC Main Configuration
      You can use the configuration reference below for the Route Cache Controller (RCC) configuration properties file for the main RCC service running on site 1 in the reference architecture. This file is used as the properties input file for the RCC service when you run the create_rc_config.py script on the TRA-RT-(SI/DR)-1 host.
    - (Site 1) RCC Standby Configuration
      You can use this reference configuration for the Route Cache Controller (RCC) service properties file for the standby RCC service running at site 1 in the reference architecture. This file would be used as the input properties file for the create_rc_config.py script when you run the script on the TRA-RT-(SI/DR)-1-S host at site 1.
    - (Site 1 E1) RCP Configuration
      You can use the configuration reference below for the Route Cache Proxy (RCP) configuration properties file for the RCP service that runs at site 1 on Engine 1 in the reference architecture. This file would be used as the input properties file for the create_rc_config.py script when you run the script on the TRA-PROC/RCP/E1-1 host.
    - (Site 1 E1) TRA-PROC HA Pair Configuration
      You can use the sample TRA-PROC-(SI/DR) configuration files below, which apply to the TRA-PROC with RCP service running on Engine 1 of site 1 in the reference architecture on the TRA-PROC/RCP/E1-1 host. A similar configuration file would be used for the TRA-PROC with RCP HA peer that runs on the TRA-PROC/RCP/E1-2 host. See the tra_config.xml file for descriptions of the generic and cluster parameters; most of them do not need to be changed.
    - (Site 1 E1) Engine Configuration
      You can use the provided configuration reference for the MATRIXX Engine configuration for the processing blade server at site 1 on Engine 1 in the reference architecture. These answers would be used by the create_config.py script when you run the script on the TRA-PROC/RCP/E1-1 host to set configurations (RCC/RCP configuration) on the engine processing blade running on that host.
    - (Site 2) TRA-RT-(SI/DR) HA Pair Configuration
      Use this configuration reference to help configure the Traffic Routing Agent (TRA-RT) configuration files that configure the TRA-RT service running at site 2 on the TRA-RT-(SI/DR)-2 host. The TRA-RT-(SI/DR) HA peer running on the TRA-RT-(SI/DR)-2-S server would use a similar configuration.
    - (Site 2) RCC Main Configuration
      You can use the sample Route Cache Controller (RCC) service properties file for the RCC running on site 2 in the reference architecture. This file would be used as the input properties file for the create_rc_config.py script when you run the script on the TRA-RT-(SI/DR)-2 server.
    - Virtual-Server/IP Setup RCC Configuration
      In the reference architecture, Route Cache Controller (RCC) services are running at site 1 and site 2 (intersite redundancy). At each site, an active and standby RCC service runs on its own TRA-RT-(SI/DR) host. The TRA-RT-(SI/DR) host where each RCC HA peer runs is provisioned with a virtual-server/IP (VIP) address to be used as the RCC-service VIP. The same RCC-service VIP is used for each RCC HA peer (at the same site). You can configure the VIP address/port connection information in the RCC setup and in the TRA-PROC with RCP setup for site 1 in the reference architecture. The TRA-PROC with RCP service on each TRA-PROC with RCP server at site 1 is configured to use the VIP to communicate with the RCC, as shown below.
- Example Single Domain Deployments
  Example configurations are provided for single-engine, dual-engine, and dual-engine with Traffic Routing Agent in disaster recovery mode (TRA-DR) cloud native MATRIXX examples.
- Configuring MATRIXX Gateways and Web Apps
  In a non-containerized installation of MATRIXX, configure MATRIXX gateways and web apps using files in the /opt/mtx/conf directory in the pod(s) hosting those components. In a cloud native deployment, configuration files can be provided in the /opt/mtx/conf directory of the component container(s) using the following methods:
- Configuring CDR Processing
  The MATRIXX Engine can import and rate Solution42® call detail records (CDRs) and generate MATRIXX Event Detail Records (EDRs) from them. Generally, this is used only when integrating with an Oracle BRM system. Other projects should use external mediation to convert external CDRs into Diameter messages for MATRIXX processing.
- Configuration Input Settings
  In a cloud native MATRIXX installation, MATRIXX Engine configuration specified in the create_config.info file is applied with a configuration source. This file contains a list of the questions asked by the configuration script during the configuration process and the answers provided by the administrator. Each question sets a configuration parameter. The engine(s) are configured with these parameters with a helm upgrade command.
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
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

Reference Architecture for Sub-Domain Routing

The reference architecture below demonstrates sub-domain routing configurations across a MATRIXX environment where multiple customer sub-domains exist. See the related links for reference configurations that apply to the Route Cache Controller (RCC), Route Cache, TRA-RT-(SI/DR), Route Cache Proxy (RCP), TRA-PROC with RCP, and engine processing blades.