2.1.5.5 NPRELAY Service Action Handler

The NPRELAY Service Action Handler performs an Number Portability lookup on the conditioned CdPN digit string and indicates Relay behavior.

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

Configuration Options Used

The TIFOPTS NPTYPERLYNPTYPE configuration option indicates the conditions that are used for a successful Number Portability match.

The destination-based NPRST configuration option and the TIFOPTS NPFLAG configuration option indicate when and how the NM bits should be processed.

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

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

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

Action Performed

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

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

If the TIFOPTS NPFLAG 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 a lookup has not already been performed, the NPRELAY Service Action Handler performs an Number Portability lookup on the CdPN digit string. RN and SP can be found as a successful match. RN and SP entities are processed as described in RN, SP, and DFLTRN Handling.

Interpretation of lookup results is described in Number Portability Lookup.

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 SPORTRELAY option value is IS41 or ALL
  • Network Entity type is SP and the SPORTRELAY option value is GSM or ALL

If the NPTYPERLY configuration option is RNSPDN, ANY, or ALL and a match is found on a non-RN/SP condition, then the RN or SP entities are not used. The end result is that NPP performs formatting of the outgoing CdPN.

The NPP Formatting Action processing will be skipped on an unsuccessful lookup. One way to force formatting of the outgoing CdPN, even after an unsuccessful lookup, is to configure the CDIAL Service Action.

On a successful lookup, where DN and entity data was found, the CdPN message parameter is changed to the ported number and the message is relayed to the recipient network.

On a successful lookup, where DN was found but entity data was not found (NPTYPERLY=ALL), the CdPN is unchanged and the message is relayed to the original destination.

The decoded NM result is used to determine if the NM bits need to be set in the outgoing IAM message.

Terminating Action?

This is not a terminating action.