Configuring USSD Notifications

Configure Unstructured Supplementary Service Data (USSD) notifications to enable Call Control Framework (CCF) to deliver USSD notifications to subscribers.

Configuring the USSD notifications involves configuring Signaling Connection Control Part (SCCP) calling party address properties, setting the maximum length of USSD messages, and configuring Notification Server properties for populating the Mobile Application Part (MAP) callout fields:

Configuring SCCP Address Properties

The USSD notification service delivers USSD notifications using the SCCP calling party address configured for requests. During MATRIXX Engine configuration, system administrators can configure, per processing pod, the following SCCP calling party address properties for delivering USSD notification messages:
  • The point code (pc) and global title (gt) values to use in the SCCP calling party address field.
  • The SCCP sub-system number (SSN) to use. The USSD notifications service uses the SSN configured for MAP call outs.
If required, system administrators can configure a separate SCCP calling party address per called global title. For example, you can set the calling global title to 4512345678 if the called global title starts with 45.

For information about configuring the SCCP calling party address properties used to deliver USSD notifications, see the discussion about how to configure the SCCP address for requests.

Configuring the Maximum Message Length of USSD Notifications

During MATRIXX Engine configuration, system administrators can configure the maximum number of characters to use in USSD notifications (160 by default). Messages are truncated if they are longer than the configured maximum.

The following create_config.info question sets the maximum message length for USSD notifications: 
Camel Gateway:What is the maximum number of USSD octets to allow in a USSD message?

Configuring Notification Server Properties

To enable USSD notifications, you must configure the following information in the mtx_notifier_camel.yaml file located on processing servers:
  • The names of the ActiveMQ queues to which notifications are sent and responses are returned:
    • The ActiveMQ notification/response pair.
    • The ActiveMQ USSD request/response pair.
  • The properties for populating MAP USSD callout fields in the MtxUssdCallOutRequestMsg message. USSD properties include:
    • The USSD data encoding scheme.
    • The USSD alerting pattern for the handset or device.
    • The SCCP called address details.
      Note: When setting the global title digits in the SCCP called address, if set from the MSISDN, then set the numbering plan to 1 for ISDN/telephony numbering plan (ITU-T E.163 and E.164). If set from the IMSI, then set the numbering plan to 6 for land mobile numbering plan (ITU-T E.212).
    • The MAP protocol version.
    • The source MSISDN.
  • For USSD menu services, you must also configure the following:
    • The ActiveMQ menu request/response pair.
    • The USSD menu data encoding scheme.
    • The USSD menu alerting pattern for the handset or device.
    • The MAP protocol version for the USSD menu service.
Note: Over long USSD notifications (messages that are longer than the configured maximum length) are truncated by default. However, the USSD service can send over long USSD notification messages by SMS instead. You can set the following USSD Notification Server properties to define a maximum response length and alternative text:
  • The SMS response length, for example:
    ussd:
  sms_response:
    length: 10000
  • The SMS response alternative text, for example:
    ussd:
  sms_response:
    alternative_text: '"Please Wait for SMS"'
You must also ensure that the SMPP end-point is enabled. To enable, set the disable property to false:
smpp:
  server:
    disable: "false"
If the response message to be sent in the USSD notification is longer than the specified SMS response length, then the USSD notification message is sent by SMS, and the specified alternative text is returned in the USSD response message.

For information about MATRIXX Notification Framework, see MATRIXX Integration.

For information about the USSD notification process, see the discussion about USSD notifications.