2.1.5.4 Using NPRELAY and NPRLS in One Service Action Set

In a Service Action set containing both the NPRELAY and NPRLS Service Actions, TIF will perform Service Action processing in the order in which the Service Actions are provisioned (the lower-numbered sax configuration parameter specifies the first Service Action to be executed). If the first Service Action (NPRELAY or NPRLS) has a successful database match, then the second Service Action (NPRLS or NPRELAY) will not be executed. If the first Service Action (NPRELAY or NPRLS) does not have a successful database match, then the second Service Action (NPRLS or NPRELAY) is executed.

The TIFOPTS NPTYPERLY option will determine the Network Entity type behavior for the NPRELAY Service Action, and the The TIFOPTS NPTYPERLS option will determine the Network Entity type behavior for the NPRLS Service Action. This s allows the NPRELAY and NPRLS Service Actions to be configured for non-ported subscribers and ported subscribers independently. The following table has a list of possible combined Service Actions scenarios for NPRELAY and NPRLS. Scenarios 1 and 4 have the same behavior, and scenarios 2 and 3 have the same behavior. If the NP type is the same for both Service Actions, the second Service Action will never get executed.

Table 2-4 Scenarios for Combining the NPRELAY and NPRLS Service Actions

Scenario	First Service Action	Second Service Action	Result
1	NPRELAY, NPTYPERLY=SP	NPRLS, NPTYPERLS=RN	NP Relay an own-network subscriber; NP Release a foreign subscriber
2	NPRELAY, NPTYPERLY=RN	NPRLS, NPTYPERLS=SP	NP Relay foreign subscriber; NP Release an own-network subscriber
3	NPRLS, NPTYPERLS=SP	NPRELAY, NPTYPERLY=RN	NP Release an own-network subscriber; NP Relay a ported subscriber
4	NPRLS, NPTYPERLS=RN	NPRELAY, NPTYPERLY=SP	NP Release a foreign subscriber; NP Relay an own-network subscriber