Configure Private Extensions for MAP Callouts

Perform this task to configure private extensions for Mobile Application Part (MAP) callouts. The private extension data can be sent in MAP callout request operations and returned in the MAP callout results.

About this task

This task configures Call Control Framework (CCF) to send private extension data in MAP callout request operations and to extract private extension data from the MAP callout results.

For an example configuration, see the example MAP ATI call out extension configuration.

Perform this task on any processing pod.

Procedure

Go to the ${MTX_CUSTOM_DIR} directory:
cd_custom_dir
Open the create_config.info file with a text editor and change the answer to the following question:
```
How many custom MDCs do you want to add?
```
Increment the number of custom MDCs by the number of extra custom MDCs required to hold the MATRIXX private extension data.

Delete the following questions:

Do you want to define any selective-updates (y/n)?
Do you want to define any selective-updates on the Charging Server's input interface (y/n)?
Do you want to define any selective-updates on the Charging Server to Transaction Server interface (y/n)?

Save and close the file.
Define the MATRIXX private extension data for MAP callouts in the ASN.1 library by adding the PrivateExtension definitions in the asn1_dictionary_base_xml_sed.extra file.
For an example definition, see the example ASN.1 MAP private extension definition. For help adding a private extension definition in the ASN.1 library, contact MATRIXX Support.
Run the configure_engine.py script as user mtx.

When prompted, add the custom MDCs to use to hold the MATRIXX private extension data.

You must base the private extension data MDC on the MtxAsn1MapPrivateExtensionData MDC, for example:

Added MDC:00005:What is the container's name?MyPrivateExtensionData
Added MDC:00005:What is the container's key?-5
Added MDC:00005:What is the name of the base container (if any)?MtxAsn1MapPrivateExtensionData
Added MDC:00005:What is the created schema version?2
Added MDC:00005:What is the deleted schema version?0

For information about adding custom MDCs, see the discussion about adding a custom MDC in MATRIXX Integration.

When prompted, add the fields for each custom MDC.

For information about adding fields to custom MDCs, see the discussion about adding a field to a custom MDC in MATRIXX Integration.
Configure selective updates to add the required elements to the MtxTcapMsg.RatingMsg.CallOutRequestList.MapCallOutRequest.PrivateExtensionList parameter and to populate the custom MDC fields:
1. When prompted, answer y to the following question:
```
Do you want to define any selective-updates (y/n)?y
```
2. To extract private extension data from the MAP callout results you must configure selective updates on the Charging Server's input interface. When prompted, answer y to the following question:
```
Do you want to define any selective-updates on the Charging Server's input interface (y/n)?y
```
3. To send private extension data in MAP call out requests, you must configure selective updates on theCharging Server to Transaction Server interface. When prompted, answer y to the following question:
```
Do you want to define any selective-updates on the Charging Server to Transaction Server interface (y/n)? y
```
4. Configure the selective updates.
  For information about selective updates configuration, see the discussion about configuring selective updates in MATRIXX Configuration.
When the script finishes, run the configure_engine.py script as user mtx to propagate the configuration changes to the other processing servers in the engine:
configure_engine.py
Restart the MATRIXX Engine:
restart_engine.py

What to do next

Configure how the MAP callouts are triggered. For information, see the discussion about configuring pre-rating in My MATRIXX Help.