Home
MATRIXX Call Control Framework Integration
Callout Response Data MDCs
Call Control Framework (CCF) holds response data for Mobile Application Part (MAP) callouts and Lightweight Directory Access Protocol (LDAP) callouts for a call or a session in MATRIXX Data Container (MDC) format.
MAP Response Data MDCs
Mobile Application Part (MAP) response data MATRIXX Data Containers (MDCs) hold the results of prerating queries that use the MAP protocol.
MtxAsn1MapMnpInfoResultData
The MtxAsn1MapMnpInfoResultData MDC contains mobile number portability (MNP) information from the Mobile Application Part (MAP) query results.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
- About Call Control Framework Integration
  MATRIXX Call Control Framework Integration provides information about MATRIXX Call Control Framework support and configuration.
- MATRIXX Call Control Framework
  MATRIXX includes an integrated GSM Service Control Function to support call control capabilities for telephony services.
- Supported Message Sequences
  MATRIXX Call Control Framework (CCF) provides support for message sequences using the Camel Application Part (CAP) protocol.
- Configuring MATRIXX Network Enabler
  This section describes how to configure MATRIXX Network Enabler.
- Configuring CAMEL Gateway
  CAMEL Gateway is a CAMEL Application Part (CAP) server. Configure CAMEL Gateway to allow communication between MATRIXX Engine and Network Enablers through the CAP protocols.
- Configuring Routing Preferences
  Configuring routing preferences allows you to define how routes are prioritized between CAMEL Gateway on each engine and Network Enablers.
- Configuring Correlation ID Length
  Call Control Framework (CCF) supports configurable correlation ID lengths. CCF handles 10 digit correlation ID lengths by default.
- Support for CAP1
  Call Control Framework (CCF) supports the processing of roaming voice calls that use the CAP1 protocol.
- Charging for CS1 INAP Calls
  Call Control Framework (CCF) provides support for processing and applying charging for voice calls that use the CS1 INAP protocol.
- Sending Furnish Charging Information
  You can configure Call Control Framework (CCF) to send Furnish Charging Information (FCI) operations at specific points during call handling. CCF sends FCI operations to instruct the Mobile Switching Center (MSC), or service switching point (SSF), to add charging information to the call data record (CDR) for a call.
- Support for MT Call Forwarding
  When handling a mobile terminating (MT) call, Call Control Framework (CCF) can forward the call to another number if the call is not answered, or the called number is busy.
- TCAP Handover and Relay Configuration
  Call Control Framework (CCF) can handover (relay) incoming TCAP requests for subscribers that MATRIXX cannot find in its subscriber database to another platform for processing. For example, when migrating to the MATRIXX platform, CCF can relay incoming TCAP requests to the incumbent platform for subscribers that have not yet been migrated across. After handover, the incumbent platform processes the TCAP request without any further involvement with MATRIXX.
- Support for Announcements
  MATRIXX Call Control Framework (CCF) provides support for playing pre-call announcements. The following topics describe CCF pre-call announcement functionality and explain how to configure CCF to play announcements.
- Support for USSD Services
  Call Control Framework (CCF) supports making Mobile Application Part (MAP) Unstructured Supplementary Service Data (USSD) call out requests to deliver USSD notifications to a subscriber. CCF also supports USSD services for queries, call back, and interactive menus using MAP-Process-UnstructuredSS-Request messages, and MAP-UnstructuredSS-Request messages.
- Announcements (IVR) and USSD Menus
  Call Control Framework (CCF) provides support for menu driven announcements using IVRs and interactive USSD service menus that give subscribers options for retrieving and updating their balances and account details.
- Apache FreeMarker Template Configuration
  You can configure Apache FreeMarker templates for handling Call Control Framework (CCF) services such as Unstructured Supplementary Service Data (USSD) query and call back services, and menu services using announcements or interactive USSD menus.
- Mobile Application Part (MAP) Call Outs
  MATRIXX Call Control Framework (CCF) provides support within the Charging Server for making MAP call out requests to an external platform in response to TCAP or Diameter messages that require them.
- Extending MAP Callouts
  You can extend the data used in Mobile Application Part (MAP) callout requests and results. You can include customized private extension data in the extensionContainer parameter in MAP ATI (AnyTimeInterrogation) and MAP SRI (SendRoutingInfo) operations. This feature enables you to manipulate the data sent and returned in MAP callouts, for example, to correct the digits dialed by a user when roaming.
- LDAP Callout Service
  Call Control Framework (CCF) provides support for making Lightweight Directory Access Protocol (LDAP) call out requests to an LDAP server in response to TCAP or Diameter messages that require them.
- Callout Response Data MDCs
  Call Control Framework (CCF) holds response data for Mobile Application Part (MAP) callouts and Lightweight Directory Access Protocol (LDAP) callouts for a call or a session in MATRIXX Data Container (MDC) format.
  - MtxCallOutResponseData
    The MtxCallOutResponseData MDC holds the query results of Mobile Application Part (MAP) and Lightweight Directory Access Protocol (LDAP) callouts for a call or a session.
  - MtxCallOutQueryLogData
    The MtxCallOutQueryLogData MDC holds named MATRIXX Data Container (MDC) fields used to log the results for a call or a session. This MDC logs the results of the following:
  - MtxSingleCallOutQueryLogData
    The MtxSingleCallOutQueryLogData MATRIXX Data Container (MDC) records the result of the most recent Mobile Application Part (MAP) callout request for a call or session, for a specific subscriber information type, such as:
  - LDAP Response Data MDCs
    MATRIXX Engine stores the results of Lightweight Directory Access Protocol (LDAP) callout requests to the MtxLdapResponseDataExtension MATRIXX Data Container (MDC).
  - MAP Response Data MDCs
    Mobile Application Part (MAP) response data MATRIXX Data Containers (MDCs) hold the results of prerating queries that use the MAP protocol.
    - MapCallOutResponse Parameters
      The MapCallOutResponse in the MtxCallOutResponseData MDC contains Mobile Application Part (MAP) query specific response parameters within an MtxCallOutResponseData MDC.
    - MtxMobileLocationData
      The MtxMobileLocationData MDC contains mobile phone location fields from the Mobile Application Part (MAP) query results.
    - MtxAsn1MapRedirectOptionData
      The MtxAsn1MapRedirectOptionData MDC contains forwarding information from the Mobile Application Part (MAP) query results.
    - MtxAsn1MapCugCheckInfoData
      The MtxAsn1MapCugCheckInfoData MDC contains Closed User Group (CUG) information from the Mobile Application Part (MAP) query results.
    - MtxAsn1MapMnpInfoResultData
      The MtxAsn1MapMnpInfoResultData MDC contains mobile number portability (MNP) information from the Mobile Application Part (MAP) query results.
    - MtxAsn1Gsm408NumberData
      The MtxAsn1gsm408NumberData MDC contains encoded number data from the Mobile Application Part (MAP) query results.
    - MtxAsn1IsdnSubAddressData
      The MtxAsn1IsdnSubAddressData MDC contains ISDN sub-address data from the Mobile Application Part (MAP) query results.
    - MtxAsn1Map2ExtendedBasicServiceIdData
      The MtxAsn1Map2ExtendedBasicServiceIdData MDC contains the extended basic service id (the ext-BearerService code or the ext-Teleservice code) from the Mobile Application Part (MAP) query results.
    - MtxAsn1MapPreferredCarrierIdData
      The MtxAsn1MapPreferredCarrierIdData MDC contains the preferred carrier ID information from the Mobile Application Part (MAP) query results.
    - MtxAsn1MapCallCompleteIfBusyServiceFlagsData
      The MtxAsn1MapCallCompleteIfBusyServiceFlagsData MDC contains the call completed if busy (CCBS) indicators from the Mobile Application Part (MAP) query results.
    - MtxAsn1Map2BasicServiceCodeData
      The MtxAsn1Map2BasicServiceCodeData MDC contains the basic service code (the BearerService code or the Teleservice code) from the Mobile Application Part (MAP) Interrogate SS query results.
    - MtxAsn1Map2RedirectFeatureData
      The MtxAsn1Map2RedirectFeatureData MDC holds one element of the call forwarding feature list from the Mobile Application Part (MAP) Interrogate SS query results.
    - MtxAsn1Map2GeneralServiceInfoData
      The MtxAsn1Map2GeneralServiceData MDC contains the call general service information data from the Mobile Application Part (MAP) Interrogate SS query results.
- Appendixes
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

MtxAsn1MapMnpInfoResultData

The MtxAsn1MapMnpInfoResultData MDC contains mobile number portability (MNP) information from the Mobile Application Part (MAP) query results.

MDC Format

MtxAsn1MapMnpInfoResultData Fields describes the MtxAsn1MapMnpInfoResultData fields.

Table 1. MtxAsn1MapMnpInfoResultData Fields
Field	Type	Description
RoutingPhoneNumber	String	The routing number.
Imsi	String	The IMSI.
Msisdn	MtxAsn1Gsm408NumberData	The MSISDN.
NumberPortability	String	The status for number portability: 0 — Not known to be ported. 1 — Own number ported out. 2 — Foreign number ported to foreign network. 3 — Not used. 4 — Own number not ported out. 5 — Foreign number ported in.