Normalisation and Denormalisation

Overview

Normalisation and denormalisation rules may be defined for any N2SCP application using N2SVCD number normalisation in any of the calling_party, called_party, or called_party_bcd blocks within the config definition, e.g.:

<?xml version="1.0" encoding="utf-8"?>
<n2svcd>
  ...
  <applications>
    ...
    <application name="<application name>" module="LhoScpApp" ...>
      ...
      <config>
        ...
        <normalisation>
          <common>
            <rule .../>
          </common>
          <calling_party>
              <rule .../>
          </calling_party>
          <called_party_bcd>
            <rule .../>
          </called_party_bcd>
        </normalisation>
          
        <denormalisation>
          <called_party>
            <rule .../>
          </called_party>
        </denormalisation>
        ...  
      </config>
    </application>
    ...
  </application>
  ...
</n2svcd>

Rules in the calling_party block are treated as ISUP numbers and apply to:

• Normalisation:
  • the callingPartyNumber in the InitialDP message.
  • the redirectingPartyID in the InitialDP message.
• Denormalisation:
  • The redirectingPartyID in the Connect message.
  • The callingPartyNumber in the Connect message.

Rules in the called_party block are treated as ISUP numbers and apply to:

• Normalisation:
  • the calledPartyNumber in the InitialDP message.
  • the originalCalledPartyID in the InitialDP message.
• Denormalisation:
  • The destinationRoutingAddress in the Connect message.
  • The originalCalledPartyID in the Connect message.
  • The assistingSSPIPRoutingAddress in the EstablishTemporaryConnection message.

Rules in the called_party_bcd block are treated as GSM called party BCD numbers and apply to:

• Normalisation:
  • the calledPartyBCDNumber in the InitialDP message.
• Denormalisation:
  • Not used.

All configuration blocks may use the following sentinel replacements:

Note that the VLR number and MSC address fields are not normalised and are expected to be in E.164 international format when received.