IDP A-Party Routing and Service Key Routing Interaction

The two features link together when both features are turned on and the A-Party Routing CGPNRTG NPP Service Action is provisioned.

The processing always attempts A-Party Routing first. If A-Party Routing is not attempted, Service Key Routing will be attempted depending on the CGPNSKRTG configuration option value in the IDPROPTS table. Service Key Routing is considered only if both features are enabled and turned on.

• If the CGPNSKRTG option is ON, Service Key Routing will be considered if A-Party Routing is not attempted. A-Party Routing will not be attempted if sufficient data required for A-Party Routing is not provisioned.
• If the CGPNSKRTG option value is OFF, Service Key Routing will be skipped and the message falls through to GTT routing if A-Party Routing is not attempted.

Whether A-Party Routing or Service Key (SK) Routing is attempted, after a message attempts to route, no other routing method (including the regular SCCP GTA/GTT routing) is attempted. If routing fails, this is treated as an IDP Relay routing failure; a UDTS is sent and the message is discarded.

Table 5-10 IDP A-Party Routing and IDP Service Key Routing Feature Interaction

A-Party Routing Turned On	CGPNRTG Service Action Provisioned		SK Routing Turned On	IDPROPTS CGPNSKRTG	Routing Decision
No	N/A		No	N/A	Fall through to GTT
			Yes	N/A	SK Routing (Fail = UDTS, discard) (Insufficient Data=Fall through to GTT)
Yes	No		No	N/A	Fall through to GTT
			Yes	N/A	SK Routing (Fail = UDTS, discard) (Insufficient Data = Fall through to GTT)
Yes	Yes	Insufficient Data	No	N/A	Fall through to GTT
			Yes	Off	Fall through to GTT
				On	Fall through to SK Routing (Fail = UDTS, discard) (Insufficient Data = Fall through to GTT)
		Sufficient Data	N/A	N/A	A-Party Routing (Fail = UDTS, discard)