Home
MATRIXX Call Control Framework Integration
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.
MDC Field Mapping for MAP Messages
Call Control Framework (CCF) uses MATRIXX Data Container (MDC) fields for setting the invoke request fields used in MAP messages and for storing the 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.
  - Mobile Application Part Protocol
    The Mobile Application Part (MAP) protocol is an SS7 protocol that provides an application layer to allow communication between the various nodes in GSM, UMTS and GPRS core networks. MATRIXX uses the MAP protocol to query external platforms such as the Mobile Number Portability (MNP) database or the Home Location Register (HLR). For example, these are used to perform number portability or to retrieve more routing information for the dialed number.
  - MAP Callout Process
    Call Control Framework (CCF) can process Mobile Application Part (MAP) callout requests for CAP and Diameter sessions.
  - MAP Callout Service Configuration
    Map Application Part (MAP) callout service configuration involves configuring:
  - MDC Field Mapping for MAP Messages
    Call Control Framework (CCF) uses MATRIXX Data Container (MDC) fields for setting the invoke request fields used in MAP messages and for storing the results.
    - Any Time Interrogation Field Mapping to MDC
      Call Control Framework (CCF) sets MAP-ATI invoke request fields based on pre-rating queries configuration in My MATRIXX and stores the MAP-ATI results in MtxCallOutResponseData MDCs.
    - Send Routing Information Field Mapping to MDC
      Call Control Framework (CCF) sets MAP-SRI invoke request fields based on pre-rating queries configuration in My MATRIXX and stores the MAP-SRI results in MtxCallOutResponseData MDCs.
  - Using Profiles With Next Logical State
    You can configure prerating queries to use the next logical state configured for prerating profiles. By using the next logical state, you can specify callout processing that uses more complex logic and requires multiple passes through the prerating generator for a single message.
  - Example Callouts Using Logical State
    This example shows how to use the Next Logical State value defined in the pr-rating profile. You can use this value to perform a sequence of callouts that use the previous callout results to select a another profile, and to perform more queries. Callouts on the start message are used to establish the location of the A-party (caller) and the B-party (called party) so that the call is charged appropriately.
  - Queries Using Balance Distribution Normalizers
    You can use balance distribution normalizers in prerating generator decision tables.
  - Example Pricing Configuration to Handle Callout Errors
    This example shows how you can configure pricing to detect and handle an error in the Mobile Application Part (MAP) callout pricing logic.
  - Mobile Application Part Statistics
    The statistics for MAP (Mobile Application Part) Any Time Interrogation (ATI) messages and Send Routing Information (SRI) messages are defined in the MATRIXX MIB files. This information is saved to the Statistics database.
- 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.
- 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

MDC Field Mapping for MAP Messages

Call Control Framework (CCF) uses MATRIXX Data Container (MDC) fields for setting the invoke request fields used in MAP messages and for storing the results.

CCF sets only supported fields for MAP-ATI and MAP-SRI invoke requests, and stores the results for only supported MAP-ATI and MAP-SRI results fields. If CCF receives results for an unsupported field, these results are ignored.

For information about supported and unsupported fields, see the discussion of MAP Protocol Implementation Conformance Statement in the appendixes for MATRIXX Call Control Framework Integration.