Home
MATRIXX Call Control Framework Integration
Supported Message Sequences
MATRIXX Call Control Framework (CCF) provides support for message sequences using the Camel Application Part (CAP) protocol.
Furnish Charging Information (FCI) Message Sequences
MATRIXX Call Control Framework (CCF) provides support for FCI message sequences. CCF sends FCI operations to instruct the Mobile Switching Center (MSC) to add charging information to the call data record (CDR) for a call.

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.
  - Released Calls and Denial Codes
    For calls that are rejected by pricing before the call is connected, the pricing denial code is mapped onto the cause value in the ReleaseCall operation sent to the MSC.
  - TCAP Session Timer
    Call Control Framework (CCF) maintains an end of transaction timer for TCAP sessions.
  - How CCF Decodes or Encodes CallingStationId and CalledStationId Fields
    The way Call Control Framework (CCF) decodes or encodes the CallingStationId and CalledStationId fields in the MtxDiamRoMsg MDC depends on whether the field holds a GSM 04.08 number or a Q.763 number.
  - Basic Voice Charging Message Sequences
    MATRIXX Call Control Framework (CCF) provides support for basic voice charging message sequences.
  - CAP1 Message Sequences
    MATRIXX Call Control Framework (CCF) provides support for voice call message sequences using the CAP1 protocol.
  - CS1 INAP Message Sequences
    MATRIXX Call Control Framework (CCF) provides support for message sequences using the CS1 INAP protocol.
  - Reauthorization on Answer Message Sequences
    MATRIXX Call Control Framework (CCF) provides support for reauthorization on answer and for no reauthorization on answer message sequences. When a call is answered, MATRIXX Engine determines whether to send an ApplyCharging operation with, or without reauthorization, based on configuration.
  - SMS Charging Message Sequences
    MATRIXX Call Control Framework (CCF) provides support for SMS charging message sequences.
  - Pre-Call Announcement Message Sequences
    MATRIXX Call Control Framework (CCF) pre-call announcement functionality enables you to play announcements to the caller before connecting them to the dialed number, either by returning the IDs of one or more announcements to play, or the ID of a VoiceXML (VXML) script to run in response to an initial quota request.
  - CallInformationRequest Message Sequences
    MATRIXX Call Control Framework (CCF) provides support for CAP4 message sequences that include CallInformationRequest operations.
  - ActivityTest Message Sequences
    MATRIXX Call Control Framework (CCF) provides support for ActivityTest message sequences. MATRIXX Engine periodically sends ActivityTest operations for non-chargeable voice calls that are being monitored (through CallInformationRequest operations) to find out whether calls are still active.
  - Disconnect Leg 2 Message Sequences
    MATRIXX Call Control Framework provides support for called party disconnects message sequences. In the following example scenarios, Call Control Framework (CCF) is configured to arm the oDisconnect (leg 2) or tDisconnect (leg 2) event detection point (EDP) as interrupted.
  - Alternative Message Sequences
    You can configure MATRIXX Call Control Framework (CCF) to use alternative message sequences.
  - Furnish Charging Information (FCI) Message Sequences
    MATRIXX Call Control Framework (CCF) provides support for FCI message sequences. CCF sends FCI operations to instruct the Mobile Switching Center (MSC) to add charging information to the call data record (CDR) for a call.
    - Successful Call, Send FCI with Connect or Continue
      Two example message sequence diagrams for a successful call when the caller disconnects and Call Control Framework (CCF) is configured to send a FurnishChargingInformation (FCI) operation with Connect or Continue operations.
    - Uncharged Call, Send FCI with Connect
      This example message sequence diagram is for an uncharged call when Call Control Framework (CCF) is configured to send FurnishChargingInformation (FCI) operations with Connect or Continue operations.
    - Uncharged Call with FCI, Following a Pre-call Announcement
      The following three scenarios show example FurnishChargingInformation (FCI) message sequences for uncharged calls with pre-call announcements when CCF is configured to send an FCI operation with Connect or Continue operations.
    - Charged Call With FCI, Following a Pre-call Announcement
      The following two scenarios show example FurnishChargingInformation (FCI) message sequences for charged calls with pre-call announcements when Call Control Framework (CCF) is configured to send an FCI operation with Connect or Continue operations.
    - Send FCI With ReleaseCall
      Two example FurnishChargingInformation (FCI) message sequence diagrams when a call is released and Call Control Framework (CCF) is configured to send an FCI operation with ReleaseCall operations.
    - Announcement Successful, Send FCI With ReleaseCall
      Two example FurnishChargingInformation (FCI) message sequence diagrams when a call is released following a successful pre-call announcement and Call Control Framework (CCF) is configured to send FCI operations with ReleaseCall operations.
    - Announcement Failure, Send FCI With ReleaseCall
      Example FurnishChargingInformation (FCI) message sequence diagram for a failed pre-call announcement when Call Control Framework (CCF) is configured to send an FCI operation with a ReleaseCall operation.
    - Reauthorization After VXML Script, FCI Sent with Continue
      Example FurnishChargingInformation (FCI) message sequence diagram when a call is reauthorized after a VoiceXML (VXML) script is played to the caller and Call Control Framework (CCF) is configured to send FCI operations with Connect or Continue operations.
    - VXML Script, FCI Sent with ReleaseCall
      Example FurnishChargingInformation (FCI) message sequence diagram when a call is released after a VoiceXML (VXML) script is run, and Call Control Framework (CCF) is configured to send an FCI operation with ReleaseCall operations.
    - Send FCI After ApplyChargingReport
      The following FurnishChargingInformation (FCI) examples show the message sequences for a successful call when the called party disconnects, and Call Control Framework (CCF) is configured to send FCI operations after ApplyChargingReport (ACR) operations.
    - CallInformationReport, Send FCI After ApplyChargingReport
      Example CAP4 FurnishChargingInformation (FCI) message sequence diagram when the switch disconnects the call after the timer expires, CCF requests a call information report (CIR), and CCF is configured to send FCI operations after ApplyChargingReport operations.
    - Timeout Waiting for CIR, Send FCI After ACR
      The following FurnishChargingInformation (FCI) example shows the message sequence used when the called party disconnects, a timeout occurs while waiting for the Mobile Switching Center (MSC) to return a CallInformationReport (CIR) operation, and Call Control Framework (CCF) is configured to send FCI operations after ApplyChargingReport operations.
    - oDisconnect Armed as Interrupted, Send FCI After ACR
      The following CAP4 FurnishChargingInformation (FCI) example shows the message sequence used when Call Control Framework (CCF) is configured to arm oDisconnect as interrupted, and to send FCI operations after ApplyChargingReport (ACR) operations.
    - CallInformationReport, oDisconnect Armed as Interrupted
      The following CAP2 or CAP3 FurnishChargingInformation (FCI) example shows the message sequence used when a call information report (CIR) is requested, Call Control Framework (CCF) is configured to arm oDisconnect as interrupted and to send FCI operations after ApplyChargingReport operations.
    - EventReportBCSM, Send FCI After ApplyChargingReport
      The following FurnishChargingInformation (FCI) example shows the message sequence used when Call Control Framework (CCF) receives a separate EventReportBCSM operation after an ApplyChargingReport (ACR) operation and CCF is configured to send FCI operations after ACR operations.
    - (CAP2, CAP4) Funds Exhausted, Send FCI After ApplyChargingReport
      The following CAP2 and CAP4 FurnishChargingInformation (FCI) examples show the message sequences used when a caller runs out of funds and Call Control Framework (CCF) is configured to send FCI operations after ApplyChargingReport (ACR) operations.
    - (CAP3) Funds Exhausted, Send FCI After ApplyChargingReport
      The following CAP3 FurnishChargingInformation (FCI) examples show the message sequences used when a caller runs out of funds and Call Control Framework (CCF) is configured to send FCI operations after ApplyChargingReport (ACR) operations.
  - Non-Standard ConnectToResource Message Sequence
    Call Control Framework (CCF) supports using a non-standard message sequence for playing announcements on an external interactive voice response (IVR) system in which MATRIXX sends an extra ConnectToResource (CTR) operation in a separate TCAP CONTINUE message before playing the first announcement.
  - Error Condition Message Sequences
    MATRIXX Call Control Framework (CCF) includes message sequences to support the following error conditions.
- 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

Furnish Charging Information (FCI) Message Sequences

MATRIXX Call Control Framework (CCF) provides support for FCI message sequences. CCF sends FCI operations to instruct the Mobile Switching Center (MSC) to add charging information to the call data record (CDR) for a call.

You can configure CCF to send FCI operations in one or more of the following situations:

In response to every ApplyChargingReport operation.
With every Connect or Continue operation.
With every ReleaseCall operation.

You can also configure CCF to send FCI operations in separate TCAP messages, if required.

Note: The message sequences in this section are valid for Camel Application Part (CAP) versions 2, 3, and 4, unless otherwise stated.

For information about configuring CCF to send FCI operations, see the discussion about sending FurnishChargingInformation.

Common Parameter Settings

FCI Example CAP Parameter Settings lists the settings for CAP operation parameters that are common to all the example FCI message sequences.

Table 1. FCI Example CAP Parameter Settings
CAP Operation Parameter	Set to
ApplyCharging.partToCharge	Leg 1
ApplyCharging.aCHCHargingAddress (CAP4)	Not set, leg 1 by default
FurnishChargingInformation.fCIBCCCAMELsequence1.partyToCharge (CAP3 and CAP4)	Not set, leg 1 by default
CallInformationrequest.legID	Leg 2