Configuring Network Enabler Fallback Processing
By default, if Network Enabler receives a message for a valid but unreachable sub-domain, or it is unable to look up the sub-domain, it sends a UDTS message back to the network. You configure Network Enabler fallback processing if you want to specify non-default message handling instead.
Note: If all sub-domains are down or unreachable, then MATRIXX
Traffic Routing Agent
closes down all SCTP/IP links with SIGTRAN network clients.
You can configure the following non-default fallback processing options for all types of platforms (both those that use, and those that do not use sub-domain routing):
- For new calls and events (IDP and IDPSMS messages), send TCAP END(ReleaseCall), configure the release cause, and raise an appropriate statistic.
- For new calls and events (IDP and IDPSMS messages), send TCAP END(Continue).
- For existing calls, after receiving an ApplyChargingReport or an eventReport operation, send TCAP END(ReleaseCall), configure the release cause, and raise an appropriate statistic.
- For any other message, including TCAP responses that contain a MAP payload for existing calls and outstanding sessions, such as USSD Notify, and MAP ATI or MAP SRI responses, suppress UDTS responses and raise a statistic.
- Use selective updates to specify the fallback processing action to take at a finer level.Note: Any modifications made through selective updates to the MtxTcapMsg MDC are not passed to processing pods. The message passed to processing pods is the same as the one received from the network.