Home
Call Control Framework Integration
Mobile Application Part (MAP) Call Outs
MATRIXX Call Control Framework (CCF) provides support within the MATRIXX Charging Server for making MAP call out requests to an external platform in response to TCAP or Diameter messages that require them.

Welcome
Release Notes
Architecture Overview
MATRIXX Cloud Native Installation and Configuration
MATRIXX Cloud Native Integration
Implementing MATRIXX in a Cloud
Installation and Configuration
MATRIXX Digital Commerce Upgrade
MATRIXX Security
MATRIXX Engine Administration
MATRIXX Web App Administration
MATRIXX Engine Integration
Call Control Framework Integration
- About Call Control Framework Integration
  Call Control Framework Integration provides information about MATRIXX Call Control Framework support and configuration.
- MATRIXX Call Control Framework (CCF)
  MATRIXX Digital Commerce includes an integrated GSM Service Control Function to support call control capabilities for telephony services.
- Network Request Processing
  Call Control Framework (CCF) can allocate incoming requests to any processing blade within a customer sub-domain.
- 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 chapter 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 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) provides support for processing 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 FurnishChargingInformation (FCI)
  You can configure Call Control Framework (CCF) to send 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, 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 messages to another platform if a subscriber can't be found in the MATRIXX database.
- 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
  MATRIXX 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 provide subscribers with 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 MATRIXX 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. The MAP protocol is used by MATRIXX to query external platforms such as the Mobile Number Portability (MNP) database or the Home Location Register (HLR), for example, to perform number portability or to retrieve additional routing information for the dialed number.
  - MAP Call Out Process
    Call Control Framework (CCF) can process Mobile Application Part (MAP) call out requests for CAP and Diameter sessions.
  - MAP Call Out Service Configuration
    Map Application Part (MAP) call out service configuration involves configuring the default MAP call out service and any additional MAP call out services, configuring the Signaling Connection Control Part (SCCP) calling party address properties for MAP call out requests, and configuring pricing to define pre-rating queries for MAP services.
  - 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.
  - Using Profiles With Next Logical State
    You can configure pre-rating queries to use the Next Logical State configured for pre-rating profiles. By using the Next Logical State, you can specify call out processing that uses more complex logic, and that requires multiple passes through the pre-rating generator for a single message.
  - Queries Using Balance Range Normalizers
    You can use Balance Range Normalizers in pre-rating generator decision tables.
  - Example Pricing Configuration to Handle Call Out Errors
    This example shows how you can configure pricing to detect and handle an error in the Mobile Application Part (MAP) call out pricing logic.
  - Mobile Application Part Statistics
    The statistics tracked for MAP (Mobile Application Part) Any Time Interrogation (ATI) messages and Send Routing Information (SRI) messages are defined in the MATRIXX MIB files and are saved to the Statistics database.
- Extending MAP Call Outs
  You can extend the data used in Mobile Application Part (MAP) call out requests and results to include customized private extension data in the extensionContainer parameter in MAP ATI (AnyTimeInterrogation) and MAP SRI (SendRoutingInfo) operations. This feature enables you to perform additional manipulation on the data that is sent and returned in MAP call outs, for example, to correct the digits dialed by a user when roaming.
- LDAP Call Out Service
  MATRIXX 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.
- Call Out Response Data MDCs
  Call Control Framework (CCF) uses MATRIXX Data Containers (MDCs) to hold response data for Mobile Application Part (MAP) call outs and Lightweight Directory Access Protocol (LDAP) call outs for a call or a session.
- Appendixes
MATRIXX Diameter Integration
MATRIXX 5G Integration
MATRIXX Monitoring and Logging
Pricing and Rating
MATRIXX Pay Now
MATRIXX Policy
MATRIXX Event Streaming
Subscriber Management
Subscriber Management (SubMan) API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
Third-Party Licenses
Glossary

Mobile Application Part (MAP) Call Outs

MATRIXX Call Control Framework (CCF) provides support within the MATRIXX Charging Server for making MAP call out requests to an external platform in response to TCAP or Diameter messages that require them.

A MAP call-out request queries the external platform to retrieve information about a subscriber, for example, to:

Establish the location of a party on the call, such as the called party for a mobile originating (MO) call for a location dependent charging type service.
Determine the recipient operator for MNP.
Determine call forwarding or routing information.
Determine which services the subscriber subscribes to.

The types of subscriber data retrieved include number portability data, subscriber location, subscriber state, and the subscriber's International Mobile Equipment Id (IMEI).