Home
MATRIXX Call Control Framework Integration
MATRIXX Call Control Framework
MATRIXX includes an integrated GSM Service Control Function to support call control capabilities for telephony services.
Transaction Overload Handling
If the volume of voice and SMS traffic overloads the platform, Call Control Framework (CCF) throttles incoming voice and SMS transactions while continuing to process existing ones.

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 CAP Operations
    Call Control Framework (CCF) provides support for CAMEL Application Part (CAP) operations using the CAP1, CAP2, CAP3, and CAP4 protocols.
  - Supported Operations for VoiceXML
    Call Control Framework (CCF) provides support for CAP operations and the Capability Set 2 (CS2) for VoiceXML (VXML).
  - Voice Calls Using CAP4 Protocol
    Message sequences for voice calls using the CAMEL Application Part 2 (CAP2), CAP3, and CAP4 protocols are usually the same. However, CCF handles the following exceptions to message sequences for voice calls using the CAP4 protocol:
  - Time Zone Handling
    Call Control Framework (CCF) can handle dates and times in different time zones.
  - Transaction Overload Handling
    If the volume of voice and SMS traffic overloads the platform, Call Control Framework (CCF) throttles incoming voice and SMS transactions while continuing to process existing ones.
  - Network Request Processing
    Call Control Framework (CCF) can assign incoming requests to any processing server within a customer sub-domain.
  - MATRIXX Network Enabler
    The Network Enabler is a MATRIXX service that load balances TCAP messages across the processing servers, which offer charging and balance control operations. Each Network Enabler acts as a signaling gateway process (SGP) and the MATRIXX services on the processing servers act as application server processes (ASPs).
  - Network Enabler Fallback Processing
    Network Enabler performs fallback processing if it receives messages destined for a valid sub-domain but that sub-domain is down or unreachable, or if it fails to look up the sub-domain. If all sub-domains are down or unreachable, then MATRIXX Traffic Routing Agent (TRA) closes down all SCTP/IP links with SIGTRAN network clients.
- 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.
- 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

Transaction Overload Handling

If the volume of voice and SMS traffic overloads the platform, Call Control Framework (CCF) throttles incoming voice and SMS transactions while continuing to process existing ones.

The platform becomes overloaded when the offered load is more than the maximum defined for all types of voice and SMS traffic. For example, an overloaded platform might be one that can handle 50,000 transactions per second (TPS), but receives 200,000 TPS. In this case, CCF would reject the excess 150,000 TPS while still attempting to successfully handle 50,000 TPS. CCF prioritizes existing sessions over new sessions.

To handle platform overload, CCF calculates a queue size for the CAMEL Gateway to Charging Server queue, and an overload threshold percentage, based on sizing configuration defined in the create_config.info file. If the number of entries in this queue exceeds the overload threshold, or the number of transactions per second exceeds the configured maximum for the type of transaction, it means that the system has become overloaded. In this case, CCF rejects all incoming TCAP BEGIN messages, effectively throttling new transactions as early as possible while still continuing to finish existing transactions.

CCF bases platform overload calculations on answers to the following configuration questions in the create_config.info file. For more information, see the discussion about CAMEL Gateway general configuration.

The following create_config.info file excerpt shows an example overload configuration for CCF traffic.

How many CAP Transactions per second is this system sized for?5500
How many CAP Transactions per second is this system sized for?0 
How many CAP SMS per second, using immediate charging, is this system sized for?0
What is the average number of CAP transactions per call?2
What is the average call hold time in seconds?60
What is the rate of reorigination calls per second for the TSAN service?0 
 What is the maximum number of correlation ID objects per sub-domain?10000
How many MAP call outs per second will there be?2750
What is the average response time for MAP call outs in milliseconds?1000
How many incoming USSD queries per second will there be?0
How many outgoing USSD notifications per second will there be?0