N2SCP Applications

Overview

Two N2SCP applications are available for use in N2SVCD:

The LHO-SCP application is a re-usable mechanism which allows an SCP to hand off to a LUA LogicApp instance for the purpose of controlling sophisticated “Value Added Service” such as Automated Call Distribution (ACD, “Toll-Free”).

Traffic Type Determination

Calls handled by N2SCP applications may be for Originating, Forwarding, or Terminating call legs. Some factors of processing (e.g. Diameter Result-Code or Special Number rules) may take the traffic type into account for rule selection.

All N2SCP applications apply the following rules, in order, to determine the traffic type of a received InitialDP:

  1. If the InitialDPEventTypeBCSM field value is 12 (termAttemptAuthorized), set the traffic type to Terminating.

  2. If:

    1. The SSP model inap value is camel1, camel2, camel3, or camel4.
    2. The InitialDPEventTypeBCSM field value is 2 (CollectedInfo) or 3 (AnalyzedInformation).
    3. The InitialDPlocationInformation field is not present.

    …set the traffic type to Forwarding.

  3. If:

    1. The SSP model inap value is cs1.
    2. The InitialDPEventTypeBCSM field value is 2 (CollectedInfo) or 3 (AnalyzedInformation).
    3. The InitialDPredirectingPartyID field is present.

    …set the traffic type to Forwarding.

  4. If the InitialDPEventTypeBCSM field value is 2 (CollectedInfo) or 3 (AnalyzedInformation), set the traffic type to Originating.

For all N2SCP applications, this call type may be used by Special Number rules as required. For the DSG-SCP application, the call type may be used within any selector rules.