DSG-SCP Configuration

As the available DSG-SCP configuration is extensive, it is broken into several sections. The overall structure of the DSG-SCP configuration within an N2SVCD configuration is as follows:

<?xml version="1.0" encoding="utf-8"?>
<n2svcd>
  ...
  <applications>
    ...
    <application name="<application instance name>" module="DsgScpApp">
      <include>
        <lib>../../n2scp/apps/dsg_scp/lib</lib>
        <lib>../../n2scp/lib</lib>
      </include>
      <parameters>
        <!-- Other common SCP or N2SVCD application top-level parameters -->
        <!-- DSG-SCP specific top-level parameters -->
      </parameters>
      <config>
        <!-- Other common SCP or N2SVCD application configuration sections -->        
        <tags>
          <!-- Tag assignment configuration -->
        </tags>
        <diameter>
          <!-- Diameter-specific configuration for the DSG-SCP -->
        </diameter>
        <notifications>
          <!-- Notification message configuration -->
        </notifications>
        <fcis>
          <!-- FCI message configuration -->
        </fcis>
        <scis>
          <!-- SCI message configuration -->
        </scis>
        <error_handling>
          <!-- Error handling configuration -->
        </error_handling>
        <external_processing>
          <!-- External processing configuration -->
        </external_processing>
        <billing_bypass>
          <!-- Billing bypass configuration -->
        </billing_bypass>
        <post_call>
          <!-- Post-call configuration -->
        </post_call>
        <!-- Other common N2SCP configuration -->  
      </config>
    </application>
    ...
  </application>
  ...
</n2svcd>

Note that the configuration uses the term “SSP” to refer to both INAP SSP and CAMEL MSC endpoints.

The DSG-SCP specific configuration sections are set out in the following pages:

The DSG-SCP also supports all common N2SCP configuration items.