Selective Updates for Fallback Processing

For platforms that use sub-domain routing, define selective updates for Network Enabler fallback processing on the Network Enabler domain lookup interface or Network Enabler sender interface. For platforms that do not use sub-domain routing, define selective updates for fallback processing on the Network Enabler incoming interface.

Platforms With Sub-Domain Routing Enabled

You define selective updates for the Network Enabler domain_lookup_task or sender_task to specify the action to take when Network Enabler is unable to reach, or look up, a sub-domain. The domain_lookup_task selective updates are used only when there is a failure to look up a sub-domain for a TCAP BEGIN message. The sender_task selective updates are used only when there is a failure to send a message to a sub-domain. The selective updates can only operate on the MtxTcapMsg MDC type. (Any selective updates for other types of MDC are ignored.)

Platforms Not Using Sub-Domain Routing

For platforms that do not use sub-domain routing, define selective updates for the Network Enabler fallback processing on the Network Enabler external_network_task (incoming interface). The external_network_task selective updates are used only when there is a failure to send a message to the processing server. The selective updates can only operate on the MtxTcapMsg MDC type. (Any selective updates for other types of MDC are ignored.)

Decoding the Incoming TCAP Message

The information from the incoming TCAP message is decoded into the MtxTcapMsg:InTcapInfo field using the subscriberDetermination dictionary as defined in the asn1_dictionary.xml file. For efficiency, this dictionary decodes only those fields usually necessary to determine the subscriber. If the selective updates use other fields that are not usually decoded, then you must use the asn1_dictionary_base_xml_sed.extra file to decode those fields and update the subscriberDetermination dictionary.
Note: The asn1_dictionary_base.xml file, located in the opt/mtx/data directory, and the asn1_dictionary_base_xml_sed.extra file, located in the opt/mtx/custom directory, define mapping between CAP parameters and MDC fields.
For example, to force the encoding and decoding of the following fields so that they can be used in selective updates:
  • InitialDPSMSArg.locationInformationMSC
  • InitialDPArg.locationInfo
  • InitialDPArg.redirectionInformation
Add the following lines in the asn1_dictionary_base_xml_sed.extra file:
s/<mdc_field field_name="LocationInfoMobileSwitchCenter" encode="false" decode="false">/<mdc_field
 field_name="LocationInfoMobileSwitchCenter" asn1_parameter_name="locationInformationMSC" asn1_type="SEQUENCE" optional="true">\n                <tag class="context" p_or_c="constructed" number="5"\/>/g

s/<mdc_field field_name="LocationInfo" encode="false" decode="false">/<mdc_field
 field_name="LocationInfo" asn1_parameter_name="locationInformation" asn1_type="SEQUENCE" optional="true" encode="true" decode="true">\n                <tag class="context" p_or_c="constructed" number="52"\/>/g

s/<mdc_field field_name="RedirectInfo" encode="false" decode="false">/<mdc_field
 field_name="RedirectInfo" asn1_parameter_name="redirectionInformation" asn1_type="REDIRECTION_INFORMATION" optional="true">\n                <tag class="context" p_or_c="primitive" number="30"\/>/g

TCAP Message Fields

The MtxTcapMsg:InTcapInfo field contains parameters from the incoming TCAP message. It includes the following fields that you use for making selective update decisions:
  • DomainFailureType — Defines which type of sub-domain failure has occurred:
    • 0 or not present — The sub-domain could not be looked up. (Applicable only if sub-domain routing is enabled.)
    • 1 — The sub-domain could not be determined. (Applicable only if sub-domain routing is enabled.)
    • 2 — The sub-domain is unreachable.
  • NotAvailableDomain — If applicable, identifies which sub-domain is unreachable.
Use selective updates to set the following fields in MtxTcapMsg:InTcapInfo to specify the action to take in the event of a failure:
  • DomainFailureAction — The action to take if Network Enabler cannot look up or reach the sub-domain:
    • 1 = Send UDTS.
    • 2 = Send ReleaseCall or ReleaseSMS.
    • 3 = Send Continue or ContinueSMS.
    • 4 = Route to the given sub-domain. (Applicable only if sub-domain routing is enabled.)
  • DomainFailureReleaseCause — Sets the cause value to send in ReleaseCall or ReleaseSMS operations.
  • RouteToDomain — Sets the ID of an alternative sub-domain to route the message to. (Applicable only if sub-domain routing is enabled.)
  • RouteToDomainNotAvailableAction — Sets the action to take if Network Enabler cannot reach the sub-domain specified by RouteToDomain:
    • 1 — Send UDTS.
    • 2 — Send ReleaseCall or ReleaseSMS.
    • 3 — Send Continue or ContinueSMS.
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.

Routing to a Specified Sub-Domain

When sub-domain routing is enabled, if selective updates set DomainFailureAction to 4 (route to the specified sub-domain), the Network Enabler sender_task attempts to send the message to the domain specified by RouteToDomain. However, it is unlikely that the subscriber is in the database on that sub-domain, therefore you must configure rules in pricing, or configure engine selective updates, to define how this case is treated by pricing. For example, you could specify configuration to play the caller an announcement before releasing the call.

Pricing can use the value of the MtxTcapMsg:RatingMsg.ServiceInfo.DomainFailureType field when deciding what actions to perform. The DomainFailureType field defines the type of sub-domain failure that has occurred. It can have the following values:
  • 0 or not present — The sub-domain could not be looked up.
  • 1 — The sub-domain could not be determined.
  • 2 — The sub-domain is unreachable.