Common SCP Configuration

Common SCP Configuration

Many common N2SCP configurations are available to all N2SCP applications. The overall structure of the common configuration within an N2SVCD configuration is as follows:

<?xml version="1.0" encoding="utf-8"?>
<n2svcd>
  ...
  <applications>
    ...
    <application name="..." module="LhoScpApp">
      <include>
        ...
      </include>
      <parameters>
        <!-- Top-level parameters for N2SCP application -->
      </parameters>
      <config>
        <special_numbers>
          <!-- Special number handling rules for the N2SCP application -->
        </special_numbers>
        <normalisation>
          <!-- Normalisation rules for the N2SCP application -->
        </normalisation>
        <denormalisation>
          <!-- Denormalisation rules for the N2SCP application -->
        </denormalisation>
        <ssps>
          <!-- SSP selection rules for the N2SCP application -->
        </ssps>
        <srfs>
          <!-- Available SRFs for the N2SCP application -->
        </srfs>
        <trace_traps>
          <!-- Pre-defined trace traps configuration -->
        </trace_traps>
      </config>
    </application>
    ...
  </application>
  ...
</n2svcd>

The common N2SCP configuration sections are set out in the following pages:

• Special Number Configuration
• Normalisation and Denormalisation Configuration
• SSP Selection Configuration
• SRF Configuration
• Trace Trap Configuration

TCAP Application Context Alias Values

The following TCAP Application Context alias values may be used where required during SSP Selection Configuration and SRF Configuration selection.

Note that for historical reasons, etsi is generally treated as an alias for cs1.
However, the use of etsi is deprecated. Please specify cs1 for new configuration.

These Application Context aliases are for use when communicating with an SSP/SSF (Service Switching Platform/Function), i.e. they are applicable for configuring as application context in an <ssp> configuration entry.

These Application Context aliases are for use when communicating with an SRF/IP (Specialized Resource Function, or Intelligent Peripheral), i.e. they are applicable for configuring as application context in an <srf> configuration entry.