2.1.5.6 NPRLS Service Action Handler

The NPRLS Service Action Handler performs a lookup on the conditioned CdPN digit string and indicates Release behavior on a successful lookup.

This Service Action should be used after the CRP Service Action.

The NPRELAY and NPRLS Service Actions are mutually exclusive in an Action Set.

Configuration Options Used

The TIFOPTS NPTYPERLSNPTYPE configuration option indicates the conditions used for a successful match.

The TIFOPTS RNRQD configuration option indicates if a Redirection Number should be included in the Release message.

The TIFOPTS RLCOPC option indicates whether the destination-based RCAUSE configuration option value or the TIFOPTS RCAUSENP configuration option value is used as the Release Cause to be included in the Release message.

The RCAUSENP configuration option indicates the Release Cause to be included in the Release message.

The value of the TIFOPTS DFLTRN option, if provisioned, is used to populate the RN on a successful match on SP.

The destination-based NPRST configuration option and the TIFOPTS NPFLAG configuration option indicates if the NM bits should be processed, and if a Release message should be generated if a DN is-not-found.

The TIFOPTS SPORTRLS option indicates the Service Portability processing for the NPRLS Service Action (none, GSM, IS41, all).

The TIFOPTS SPFILL option indicates whether SP should be populated when the DFLTRN value or the GRN data is used for the RN value.

Action Performed

If the NPRELAY Service Action has already been executed with a successful match, no NPRLS processing is performed.

This Service Action Handler uses the incoming NM bits to determine whether a lookup has already been performed. See Use of NM Bits.

If the NPFLAG configuration option is set to NM and the NM bits indicate that a lookup has already been performed, then the Service Action Handler returns immediately.

If the NM bits indicate that a lookup has not already been performed, the Service Action Handler performs an Number Portability lookup on the conditioned CdPN digit string. RN or SP can be found as successful match. The RN and SP values are processed as described in RN, SP, and DFLTRN Handling.

Interpretation of lookup results is described in Number Portability Lookup.

On a match, the RNRQD option indicates whether or not a Redirection Number is included in the Release message, and the RCAUSE option or the RCAUSENP option indicates the Release Cause to be included in the Release message.

• On a successful lookup, where DN and entity data was found, a Release message is sent. If the Redirection Number configuration option (RNRQD) is set to YES, then the ported number is included in the ISUP Release message.
• On a successful lookup, where DN was found but entity data was not found (NPTYPERLS=ALL), a Release message is sent. If the Redirection Number configuration option (RNRQD) is set to YES, then the original CdPN is included in the ISUP Release message.

Depending on the Formatting Action configuration for the selected rule, the updated RN or SP can be used during CdPN formatting by NPP.

Wen the Service Portability feature is ON, and:

• Network Entity type is RN/PT=0 and the SPORTRLS option value is IS41 or ALL
• Network Entity type is SP and the SPORTRLS option value is GSM or ALL

The Formatting Action processing will be skipped on an unsuccessful lookup. The original message is relayed using the original CdPN, unless NPFLAG=NM and a Release message is to be generated. If TIFOPTS NPFLAG=NM, the incoming NM Bits value is 01, and no match is found in the Number Portability lookup on the CdPN, then the NPRLS Service Action Handler sends a Release message with no Redirection Number and the Release Cause set to the value of the TIFOPTS RCAUSENP option.

Terminating Action?

This is a terminating action in either of the following two conditions:

• The NPFLAG is set to NM, lookup is not successful, and the NM bits indicate “query not performed” (binary value 01).
• The lookup is successful.