Network Enabler Fallback Processing Configuration Properties

Network Enabler fallback processing configuration properties determine how incoming TCAP messages are handled if a sub-domain is down or unreachable, or if Network Enablers are unable to look up the sub-domain.

By default, Network Enabler sends a UDTS message back to the network if:
  • It receives a message for a valid but unreachable sub-domain, for example, because the sub-domain is down.
  • It recieves a message for which it is unable to look up the sub-domain, for example, because the message is for a subscriber who is not in the MATRIXX database.
You can configure NEs to use the following non-default message handling options instead:
  • 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.

If required, you can ensure that traffic is still sent to Network Enablers when all processing pods are down by specifying a list of subsystem numbers (SSNs) that Network Enablers always activate. Enter a comma-separated list of the SSNs to use when you answer the following create_config.info question: Network Enabler:What are the SSNs Network Enabler should always activate?

Unreachable Domains

Message Handling Configuration for Unreachable Domains describes the create_config.py properties for configuring Network Enabler fallback processing using non-default message handling when a sub-domain is unreachable.
Note: These configuration options are applicable both to platforms which use sub-domain routing and those which do not.
Table 1. Message Handling Configuration for Unreachable Domains
Property Description Default Value
Unreachable Domain Message Handling Configuration Enable this option only if, instead of the default fallback processing, you want to specify non-default message handling when a sub-domain is unreachable.

To enable this configuration answer y to the following question, and answer the additional questions that become available:

create_config.info question: Do you want to enable special handling of messages when a domain is unreachable?

 n
Unreachable Domain: Release New Calls Answer y to the following question to send a TCAP END(ReleaseCall) message on receipt of TCAP BEGIN (IDP) messages if the sub-domain becomes unreachable.

create_config.info question: Do you want to send END(ReleaseCall) on receipt of BEGIN(InitialDP) for an unreachable domain (y/n)?

If you answered y, answer the following question to configure the release cause. Defaults to 41 (system failure).

create_config.info question: What is the release cause to put in END(ReleaseCall) on receipt of BEGIN(InitialDP) for an unreachable domain?

 n
Unreachable Domain: Continue New Calls If you set Unreachable Domain: Release New Calls to n, answer the following question:

create_config.info question: Do you want to send END(Continue) on receipt of BEGIN(InitialDP) for an unreachable domain (y/n)?

Answer y to send a TCAP END(Continue) message on receipt of TCAP BEGIN (IDP) messages if the sub-domain becomes unreachable.

 n
Unreachable Domain: Release Existing Calls Answer y to the following question to send a TCAP END(ReleaseCall) message on receipt of TCAP CONTINUE(ApplyChargingReport or EventReportBCSM) messages if the sub-domain becomes unreachable.

create_config.info question: Do you want to send END(ReleaseCall) on receipt of CONTINUE(ACR or ERBCSM) for an unreachable domain (y/n)?

If you answered y, answer the following question to configure the release cause. Defaults to 41 (system failure).

create_config.info question: What is the release cause to put in END(ReleaseCall) on receipt of CONTINUE(ACR or ERBCSM) for an unreachable domain?

n
Unreachable Domain: Release SMS Answer y to the following question to send a TCAP END(ReleaseSMS) message on receipt of TCAP BEGIN (IDPSMS) messages if the sub-domain becomes unreachable.

create_config.info question: Do you want to send END(ReleaseSMS) on receipt of BEGIN(InitialDPSMS) for an unreachable domain (y/n)?

If you answered y, answer the following question to configure the release cause. Defaults to 41 (system failure).

create_config.info question: What is the release cause to put in END(ReleaseSMS) on receipt of BEGIN(InitialDPSMS) for an unreachable domain?

n
Unreachable Domain: Continue SMS If you set Unreachable Domain: Release SMS to n (no), answer the following create_config.info question:

Do you want to send END(ContinueSMS) on receipt of BEGIN(InitialDPSMS) for an unreachable domain (y/n)?

Answer y to send a TCAP END(ContinueSMS) message on receipt of TCAP BEGIN (IDPSMS) messages if the sub-domain becomes unreachable.

n
Unreachable Domain: Suppress UDTS Responses Answer y to the following question to ignore the message and suppress sending UDTS on receipt of any other TCAP message if the sub-domain becomes unreachable.

create_config.info question: Do you want to suppress UDTS responses for other messages received for an unreachable domain (y/n)?

n
Unreachable Domain: Use Selective Updates This question is asked if you answered n to either of the following:

Do you want to send END(Continue) on receipt of BEGIN(InitialDP) for an unreachable domain (y/n)?

Do you want to send END(ContinueSMS) on receipt of BEGIN(InitialDPSMS) for an unreachable domain (y/n)?

Answer y to process the message using selective updates.
create_config.info question: Do you want to use selective updates to determine the action to be taken on receipt of a message for an unreachable domain (y/n)?
Note: If sub-domain routing is enabled on the platform, configure the selective updates you require on the Network Enabler sender interface. If sub-domain routing is not enabled on the platform, configure the selective updates you require on the Network Enabler incoming interface. Use the selective updates to update only the MtxTcapMsg MDC.
 n

Domains that Network Enablers Cannot Look Up

Message Handling Configuration for Domains that Network Enablers Cannot Look Up describes the create_config.py properties for configuring Network Enabler fallback processing to use non-default message handling when it cannot look up a subscriber's sub-domain, for example, if the message is for a subscriber who is not in the MATRIXX database.
Note: These configuration options are applicable only to platforms for which sub-domain routing is enabled.
Table 2. Message Handling Configuration for Domains that Network Enablers Cannot Look Up
Property Description Default Value
Enable Domain Not Looked Up Message Handling Configuration Enable this option only if, instead of the default fallback processing, you want to specify non-default message handling when Network Enabler is unable to find a sub-domain.

To enable this configuration answer y to the following question, and answer the additional questions that become available:

create_config.info question: Do you want to enable special handling of messages when a domain cannot be looked up?

 n
Domain Not Looked Up: Release New Calls Answer y to the following question to send a TCAP END(ReleaseCall) message on receipt of TCAP BEGIN(IDP) messages if the Network Enabler cannot look up the sub-domain.

create_config.info question: Do you want to send END(ReleaseCall) on receipt of BEGIN(InitialDP) for which the domain cannot be looked up(y/n)?

If you answered y, answer the following question to configure the release cause. Defaults to 41 (system failure).

create_config.info question: What is the release cause to put in END(ReleaseCall) on receipt of BEGIN(InitialDP) for which the domain cannot be looked up?

n
Domain Not Looked Up: Continue New Calls If you set Domain Not Looked Up: Release New Calls to n, answer the following question:

create_config.info question: Do you want to send END(Continue) on receipt of BEGIN(InitialDP) for which the domain cannot be looked up(y/n)?

Answer y to send a TCAP END(Continue) message on receipt of TCAP BEGIN(IDP) messages if the Network Enabler cannot look up the sub-domain.

 n
Domain Not Looked Up: Release Existing Calls Answer y to the following question to send a TCAP END(ReleaseCall) message on receipt of TCAP CONTINUE(ApplyChargingReport or EventReportBCSM) messages if the Network Enabler cannot look up the sub-domain.

create_config.info question: Do you want to send END(ReleaseCall) on receipt of CONTINUE(ACR or ERBCSM) for which the domain cannot be looked up (y/n)?

If you answered y, answer the following question to configure the release cause. Defaults to 41 (system failure).

create_config.info question: What is the release cause to put in END(ReleaseCall) on receipt of CONTINUE(ACR or ERBCSM) for which the domain cannot be looked up?

n
Domain Not Looked Up: Release SMS Answer y to the following question to send a TCAP END(ReleaseSMS) message on receipt of TCAP BEGIN(IDPSMS) messages if the Network Enabler cannot look up the sub-domain.

create_config.info question: Do you want to send END(ReleaseSMS) on receipt of BEGIN(InitialDPSMS) for which the domain cannot be looked up y/n)?

If you answered y, answer the following question to configure the release cause. Defaults to 41 (system failure).

create_config.info question: What is the release cause to put in END(ReleaseSMS) on receipt of BEGIN(InitialDPSMS) for which the domain cannot be looked up?

n
Domain Not Looked Up: Continue SMS If you set Domain Not Looked Up: Release SMS to n, answer the following create_config.info question:

Do you want to send END(ContinueSMS) on receipt of BEGIN(InitialDPSMS) for which the domain cannot be looked up(y/n)?

Answer y to send a TCAP END(ContinueSMS) message on receipt of TCAP BEGIN (IDPSMS) messages if the Network Enabler cannot look up the sub-domain.

n
Domain Not Looked Up: Suppress UDTS Responses Answer y to the following question to ignore the message and suppress sending UDTS on receipt of any other TCAP message if the Network Enabler cannot look up the sub-domain.

create_config.info question: Do you want to suppress UDTS responses for other messages received for which the domain cannot be looked up(y/n)?

n
Domain Not Looked Up: Use Selective Updates This question is asked if you answered n (no) to either of the following:

Do you want to send END(Continue) on receipt of BEGIN(InitialDP) for which the domain cannot be looked up(y/n)?

Do you want to send END(ContinueSMS) on receipt of BEGIN(InitialDPSMS) for which the domain cannot be looked up(y/n)?

Answer y to process the message using selective updates.
create_config.info question: Do you want to use selective updates to determine the action to be taken on receipt of a message for which the domain cannot be looked up(y/n)?
Note: Configure the selective updates you require on the Network Enabler domain lookup interface. Use the selective updates to update only the MtxTcapMsg MDC.
 n