Diameter Notifier

The Diameter Notifier routes and proxies outgoing MDCs to the EDGW pod. It is part of the EDGW installation.

Note: Diameter Notifier uses the Kubernetes API. You must deploy EDGW with Kubernetes. You cannot deploy EDGW on Docker with Kubernetes. If there is only one pod with an EDGW, the Diameter Notifier is not required. For information about configuring the Diameter Notifier, see the discussion about EDGW sub-chart properties in MATRIXX Installation and Upgrade.

If you have multiple EDGW pods, the Diameter Notifier is required. When an external client connects to an EDGW pod, EDGW registers its peer information with the Diameter Notifier. This enables the Diameter Notifier to route to the correct EDGW when MATRIXX Engine must send a Diameter request, such as a Re-Auth-Request or Spending Status Notification.

Figure 1 shows how the Diameter Notifier routes messages from MATRIXX Engine to EDGW instances. Note the following:
  • All EDGW pods are required to enable the Notifier Server port for gRPC protocol communication with Diameter Notifier(s).
  • All Diameter Notifiers engage with the Kubernetes API Gateway, actively monitoring activities of EDGW pods.
  • The Diameter Notifier establishes connections with EDGW pods autonomously.
  • All peer information is stored directly in the memory of each individual Diameter Notifier pod. When a Diameter Notifier pod is restarted or redeployed, it requests the peer information again from all detected EDGW pods.
  • MATRIXX Engine must be configured to send all outgoing Diameter MDCs to the Diameter Notifier.
  • The Diameter Notifier routes MDC requests from MATRIXX Engine to the correct EDGW with a matching connected peer session.
Figure 1. Diameter Notifier


Figure 2 shows the message flow between the Diameter client and MATRIXX Engine through the EDGW.
Figure 2. Diameter Notifier Message Flow