SCP-Specific Configuration

Introduction

In addition to the core CUG configuration, the CUG SCP SVC library allows for additional INAP-specific configuration to be specified.

Default CUG Configuration

The below CUG configuration values will be used at runtime as a default. Any user-defined values for these fields will:

• be prepended to the rule list for rules keys such as match_found.
• replace the value for simple parameters such as apply_lists.

Default CUG Actions Configuration

          <configuration allow_sc_user="0"
                         allow_match_sc="1">
              <match_found>
                  <rule action="continue"/>
              </match_found>
              <no_match_found>
                  <rule action="continue"/>
              </no_match_found>
              <no_user_found>
                  <rule action="continue"/>
              </no_user_found>
              <not_allowed_list>
                  <rule action="release" cause="31"/>
              </not_allowed_list>
              <not_allowed_user>
                  <rule action="release" cause="31"/>
              </not_allowed_user>
          </configuration>

Default CUG Lookup Configuration

          <configuration allow_sc_user="0"
                         allow_match_sc="1">
              <user_number>
                <rule source="input.normalised_calling_party"/>
              </user_number>
              <match_number>
                  <rule source="input.normalised_called_party"/>
              </match_number>
          </configuration>

Action Handling

CUG SVC rules, in addition to the parameters for rule selection, require the specification of a single action to take when a rule is matched during processing. Only one action will be applied per call.

The following specific actions are available for CUG SCP SVC processing:

For actions using continue handling, a Connect will be sent instead of a Continue if any of the following apply:

• Number translation of the B-party has occurred (e.g. a short code has been translated into a long number).
• A different calling party is to be presented to the called party (i.e. the caller’s short code).
• The global FORCE_CONNECT is set to a truthy value.

Additional selector rule parameters are also available when specifying CUG SVC SCP rules.

Announcements

Overview

As part of handling defined action rules for CUG SVC SCP call control, a pre-configured announcement may be played to the calling party. Such interactions are configured with a name so that they may be invoked by the applicable action rules.

Announcements may be played prior to any action other than abort.

Announcements are configured in the LogicApp global ANNOUNCEMENTS. A sample announcement configuration might be:

<application name="N2CUG-Logic" module="LogicApp">
    ...
    <config>
        <services>
            <service module="LhoScpApp::LhoScpLuaService">
                ...
                <globals>
                    <global name="ANNOUNCEMENTS" type="array">
                        <announcement name="ann1" srf_name="OnSwitch" announcement_id="25"/>
                        <announcement name="ann2" srf_name="OnSwitch" announcement_id="26"/>
                    </global>

Announcement Configuration Details

Each announcement can support the following attributes:

FCI/SCI Messages

Overview

As part of handling defined action rules for CUG SVC SCP call control, a pre-configured FurnishChargingInformation or SendChargingInformation message may be sent. Such messages are configured with a name so that they may be invoked by the applicable action rules.

Both FCI and SCI messages may only be sent along with a Connect, Continue, or PlayAnnouncement operation, and therefore may only be specified against action rules that allow the call to continue in this fashion.

FCIs and SCIs are configured in the LogicApp globals FCIS and SCIS, respectively. A sample FCI/SCI configuration might be:

<application name="N2CUG-Logic" module="LogicApp">
    ...    
    <config>
        <services>
            <service module="LhoScpApp::LhoScpLuaService">
                ...
                <globals>
                    <global name="SCIS" type="array">
                        <!--
                          01 64 00  # value
                        -->
                        <sci name="sci-100">016400</sci>
                        <sci name="sci-101">016500</sci>
                    </global>

                    <global name="FCIS" type="array">
                        <!--
                          a0 0f                       # constructed, tag 0 (fCIBCCCAMELsequence1), length 15
                            80 08                     # primitive, tag 0 (freeFormatData), length 8
                              12 34 56 78 90 ab cd ef # value
                            a1 03                     # constructed, tag 1 (partyToCharge), length 3
                                80 01                 # primitive, tag 0 (sendingSideID), length 1
                                  01                  # value
                        -->
                        <fci name="fci-x">a00f80081234567890abcdefa103800101</fci>        <!-- 1234567890abcdef -->
                    </global>

In the above, four FCI/SCI messages are defined and would have the following configuration:

FCI/SCI Configuration Details

Each fci or sci can support the following attributes:

FCI Data

As indicated in the FCI/SCI configuration details, the FCI data value is used as the entire FCI payload within the FCIBillingChargingCharacteristics field.

Other INAP variants, such as CAMEL, have this parameter subdivided into other fields. As an example, if CAMEL2 were used with the FCI definition data of a00f80081234567890abcdefa103800101, this would decode to:

a0 0f                       # constructed, tag 0 (fCIBCCCAMELsequence1), length 15
  80 08                     # primitive, tag 0 (freeFormatData), length 8
    12 34 56 78 90 ab cd ef # value
  a1 03                     # constructed, tag 1 (partyToCharge), length 3
      80 01                 # primitive, tag 0 (sendingSideID), length 1
        01                  # value

Available Fields

Input Context

The input context that is supplied for use with the CUG SVC SCP is as per the N2SCP HANDLE-ALEG-IDP message, with the initialdp_arg field populated as per the relevant INAP ASN.1.

Fields within this context should be referred to with the prefix input., e.g. input.normalised_calling_party or input.initialdp_arg.serviceKey.

Service Context

The service context for the CUG SVC SCP is populated with the following fields: