Home
MATRIXX Call Control Framework Integration
Configuring MATRIXX Network Enabler
This section describes how to configure MATRIXX Network Enabler.
Configuring Local Point Codes
You can configure multiple originating (local) point codes for Network Enabler external links that are used only for incoming traffic.

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.
  - MATRIXX Network Enabler Configuration Prerequisites
    During Network Enabler configuration, you must give details about how Network Enabler is to be deployed in a MATRIXX system.
  - MATRIXX Network Enabler Configuration Example
    This example describes Network Enabler signaling links and routing configuration for an example customer.
  - Configuring External Links Based on STP Names
    You can configure external links between Network Enablers and Signaling Transfer Points (STPs) based on the name of each STP instead of the IP address. This feature enables you to use the same configuration files for deployments where the IP address of each STP is different per Network Enabler.
  - Configuring Local Point Codes
    You can configure multiple originating (local) point codes for Network Enabler external links that are used only for incoming traffic.
  - Support for Concerned Point Codes
    Call Control Framework (CCF) provides support for creating Concerned Point Codes (CPCs) derived from Network Enabler routing and link configuration.
  - Configuring SCCP Routing Policy
    You configure Signaling Connection Control Part (SCCP) routing policy to define policy rules for routing outgoing SCCP messages based on address fields such as the point code and global title digits from the called or the calling number.
  - Configuring Network Enabler Fallback Processing
    By default, if Network Enabler receives a message for a valid but unreachable sub-domain, or it is unable to look up the sub-domain, it sends a UDTS message back to the network. You configure Network Enabler fallback processing if you want to specify non-default message handling instead.
- 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

Configuring Local Point Codes

You can configure multiple originating (local) point codes for Network Enabler external links that are used only for incoming traffic.

An external link that is used only for incoming traffic does not require any routes assigned to it, but you can define extra local point codes for it.

To define local point codes for an external link, you must enable advanced link configuration in the create_config.info configuration file by answering y to the following question: Network Enabler defaults: Do you want to prompt for advanced link configuration (y/n)?y

To specify the number of extra local point codes for the link, answer the following create_config.info question: Network Enabler Link 1: How many originating point codes do you want to define?

To define the local point codes to use, answer the following create_confg.info question for each additional point code: Network Enabler Link 1: What is originating point code number 1?

The following shows an example configuration for an external link with three extra local point codes defined.

Network Enabler defaults:Do you want to prompt for advanced link configuration (y/n)?y
...
Network Enabler Link 1: How many originating point codes do you want to define?3
Network Enabler Link 1: What is originating point code number 1?104
Network Enabler Link 1: What is originating point code number 2?105
Network Enabler Link 1: What is originating point code number 3?106