Home
Call Control Framework Integration
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.

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.
- 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.
  - Configuring MAP Call Out Extensions
    Mobile Application Part (MAP) call out extension configuration enables you to include customized private extension data in MAP ATI and MAP SRI requests.
  - Configure Private Extensions for MAP Call Outs
    Perform this task to configure private extensions for Mobile Application Part (MAP) call outs. The private extension data can be sent in MAP call out request operations and returned in the MAP call out results.
  - Example ASN.1 MAP Private Extension Definition
    You define private extension parameters for Mobile Application Part (MAP) ATI and MAP SRI operations in the asn1_dictionary_base_xml_sed.extra file. This section describes an example private extension definition for the MAP ATI operation.
  - Example MAP ATI Call Out Extension Configuration
    This example is for a MAP ATI private extension configuration. The example uses an initial ATI request to retrieve the corrected number for a subscriber. The corrected number is sent as the subscriber identity in a second ATI request and used to retrieve MNP information. The MNP routing number is then prefixed to the corrected number for use as the destinationRoutingAddress in the Connect operation.
- 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

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.

You send private extensions in the top level extensionContainer parameter of the MAP ATI operation or the MAP SRI operation. You can also extract private extensions from the top level extensionContainer parameter contained in the MAP ATI or MAP SRI call out results. You can use the private extension data for a variety of purposes, for example, it can be used during rating, for determining the number to connect to, and so on.

The MAP specification defines extensionContainer parameters at many levels in the hierarchy of MAP ATI and MAP SRI operations and results. CCF supports only top level extensionContainer parameters. CCF does not support extensionContainer parameters that are sub-parameters of other parameters. For information about the MAP parameters that CCF supports, see the discussion about MAP protocol implementation conformance statement.