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

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.
  - Configure Relay SCCP Address for a Service
    Perform this task to configure the Signaling Connection Control Part (SCCP) address for relaying incoming TCAP messages for voice, SMS, or USSD services.
  - Relay SCCP Address Configuration Parameters
    Use configuration parameters in create_config.py to define the SCCP address for relaying incoming TCAP messages from subscribers who cannot be found in the MATRIXX database to another platform.
- 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.
- 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

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.

CCF can perform TCAP handover in a single domain or multi-domain environment. If you enable relay SCCP for the service, CCF hands the message over to another platform based on the configured relay SCCP address. In a multi-domain environment, depending on domain resolution configuration, if MATRIXX cannot find a subscriber in the MATRIXX database, the incoming TCAP message is consumed or forwarded to an available MATRIXX sub-domain. CCF can then send the message to the configured relay SCCP address.

In a multi-domain environment, domain resolution behavior is based on the following cache_fail_perform_domain_resolution and cache_fail_behavior configuration options set in the mtx_config.xml configuration file:

If cache_fail_perform_domain_resolution = 0, domain resolution is not performed. Then, if cache_fail_behavior is set to:
- -1 — CCF sends the TCAP message to the default sub-domain. If you enabled relay SCCP for the service, CCF sends the message to the relay SCCP address configured for the service.
- -2 — The TCAP message is consumed.
If cache_fail_perform_domain_resolution = 1, domain resolution is attempted. If unsuccessful, and cache_fail_behavior is set to:
- -1 — CCF sends the TCAP message to the default sub-domain. If you enabled relay SCCP for the service, CCF sends the message to the relay SCCP address configured for the service.
- -2 — The TCAP message is consumed.
- -3 — The TCAP message is assigned to the next sub-domain ID in the list of all sub-domain IDs. If you enabled relay SCCP for the service, CCF sends the message to the relay SCCP address configured for the service.

During engine configuration, you can enable SCCP relay, and define the relay SCCP address for the following services:

Voice services
SMS services
USSD services