Configuring MAP Callout Extensions

Mobile Application Part (MAP) call out extension configuration enables you to include customized private extension data in MAP ATI and MAP SRI requests.

Configuring MAP call out extensions involves the following:

  • Adding the ASN.1 library definition for the MATRIXX private extension data in the asn1_dictionary_base_xml_sed.extra file.
  • Adding a custom MDC to hold the private extension data as defined in the ASN.1 library definition. You must specify the MtxAsn1PrivateExtensionData base container when you add the private MDC.
  • Configuring selective updates on the Charging Server to the Transaction Server interface to add the required elements to the MtxTcapMsg.RatingMsg.CallOutRequestList.MapCallOutRequest.PrivateExtensionList parameter, and to populate the private extension data in MAP call out requests.
  • Configuring selective updates on the Charging Server input interface to extract the private extension data in the MAP callout results from the RatingMsg.CallOutSessionInfo.CalledCallOutResponse.MapCallOutResponse parameter.
  • Configuring pricing in My MATRIXX to configure the PreRating queries for the MAP callout services.

You can normalize the private extension data extracted from the MAP callout result. You can configure selective updates to copy the private extension data extracted from MAP callout results to fields in the custom MDC specified in the answer to this create_config.info file question:

Camel Gateway:Which custom MDC should be used for rating CAMEL Messages? MyDiamRoMsg

You configure CCF number normalization rules for normalizing the copied data in the custom MDC in the mtx_config_base_xml_sed.extra file.

For help configuring CCF number normalization rules, contact MATRIXX Support.