Info Analyzed Relay Features

2.1 Operation Overview

The following Info Analyzed Relay (IAR) features are used to process AnalyzedInformation messages that are sent from an MSC to an SCP or SN.

IAR Base (Part Number 893034201)

IAR Base intercepts and identifies the AnalyzedInformation messages that require IAR feature processing, and performs all message processing.

The IAR Base feature must be on before any other IAR features can be used in the system.
IAR Number Portability (IAR NP) (Part Number 893026101)

IAR NP performs an RTDB lookup on the conditioned number from the message, distinguishes own network subscribers from foreign network subscribers, populates Formatting Action values used for outgoing message formatting, and performs Service Portability processing when the Service Portability feature is on.

The IAR NP feature supports MNP and Service Portability processing, but it does not dictate how the customer will use it. For example, the IAR NP feature can be used to identify subscribers that belong to the customer’s network, but it does not dictate whether or not AnalyzedInformation messages associated with them should be modified before they are relayed. Each customer can decide how to represent subscribers of own and foreign networks in the RTDB. The IAR features allow each customer to decide how to react to that data appropriately.

Service Portability (S-Port) (Part Number 893034301) processing can be applied by the IAR NP feature, allowing the RTDB GRN value to be used as the RN in the outgoing message.

S-Port Subscriber Differentiation (Part Number 893037901) can be used with Service Portability to allow use of provisioned ASD digits in place of GRN digits as an alternative Routing Number for own-network subscribers.
IAR Additional Subscriber Data (IAR ASD) (Part Number 893035001)

IAR ASD provides the ability to obtain Additional Subscriber Data from the RTDB and populate the ASD Formatting Action value with the ASD.
IAR Generic Routing Number (IAR GRN) (Part Number 893035101)

IAR GRN provides the ability to obtain the Generic Routing Number from the RTDB and populate the GRN Formatting Action value with the GRN.

Note:

There are several features that can use GRN data: IDP A-party Blocklist, INP/G-Port /ATINP Support for ROP, and Service Portability. The IDP A-party Blocklist feature is mutually exclusive with Service Portability; the two features cannot be enabled in the same system. There is no other restriction placed in the code to make other combinations of features using GRN mutually exclusive with each other. It is anticipated that the other combinations will not occur in the same system, based on market requirements. The combinations of features that use GRN should be considered in configuring each system.

Subscriber data population and feature configuration provide information to identify subscribers as own-network or foreign network, and to determine which AnalyzedInformation messages will be processed by IAR features.

Message processing is also guided by configuration of the Numbering Plan Processor (NPP). After a message is determined to require IAR feature processing, the NPP configuration determines whether or not the CdPN parameter or CgPN parameter, or both, will be modified.

IAR General Relay Call Flow

Call Flow Example for a Foreign Network Subscriber

Call Flow Example for an Own Network Subscriber

The following general call flow relays AnalyzedInformation messages:

An incoming MSC event trips an Intelligent Network trigger.
The MSC sends an AnalyzedInformation message to the EAGLE.
The IAR Base feature intercepts an AnalyzedInformation query based on customer configured criteria.
The following actions are performed, based on configuration options:
- The B-Party number and A-Party number are extracted from the CdPN parameter and CgPN parameter.
- An RTDB lookup is performed on the CdPN or CgPN or both to check subscriber status.
- The CdPN parameter or CgPN parameter, or both, could be modified based on configuration options and RTDB lookup results.
- The message is relayed to its original destination.
  The SCP uses the information in the AnalyzedInformation message to apply a billing tariff to the associated call, and check the balance of a prepaid subscriber, among other things. An AnalyzedInformation response message will be returned to the originator of the AnalyzedInformation message.
  
  The MSC handles the call based on the information in the AnalyzedInformation response. The MSC could have been instructed to terminate the call. The SCP can also have the MSC reroute the call by providing a DGTSDIAL parameter in the response message

For a configuration that would modify AnalyzedInformation messages when the CdPN parameter describes a subscriber that is served by a foreign network, the RTDB could be provisioned to associate an RN that identifies the network supporting all foreign subscribers:

Subscriber range records could be used for blocks of numbers that are used by foreign networks.
Individual records could be used to describe subscribers that have had their numbers ported out of the customer's network to some foreign network.

The IAR NP feature can key off of the existence of an RTDB record for some CdPN to determine which messages should be modified before relay, and also use the RN in the modification. The RN would probably be prepended to the original CdPN, but NPP allows the the data to be used in whatever way best suits the needs.

The Home SCP can easily strip an RN from the front of a CdPN parameter if all of the RN values used to provision of the RTDB are the same length.

This example represents the following processing:

A prepaid subscriber attempts to make a call that trips an IN trigger at the MSC. The MSC sends an AnalyzedInformation message to the network served by the EAGLE.
The IAR Base feature intercepts the AnalyzedInformation message,and determines that it requires IAR processing.
The IAR NP feature performs an RTDB lookup using the digit string in the CdPN parameter, and finds that the number is associated with an RN; the B-party subscriber was ported to a foreign network.
The IAR Base feature formats a new CdPN parameter using the RN and DN (as directed by NPP).
The modified AnalyzedInformation message is sent to the Home SCP.
The Home SCP detects and strips the RN from the CdPN parameter, and uses it to determine an appropriate tariff rate for the call.

The following processing illustrates a call to an own-network subscriber:

A prepaid subscriber attempts to make a call that trips an IN trigger at the MSC. The MSC sends an AnalyzedInformation message to the network served by the EAGLE.
The IAR Base feature intercepts the AnalyzedInformation message,and determines that it requires IAR processing.
The IAR NP feature performs an RTDB lookup using the digit string in the CdPN parameter, and finds that the number is not associated with an RN; the B-party subscriber was ported into the customer's network.
The IAR Base feature does not modify the CdPN parameter.
The unmodified AnalyzedInformation message is sent to the Home SCP.
The Home SCP detects the lack of an RN in the CdPN parameter, and associates an appropriate tariff rate with the call.

NPP

Message processing is also guided by configuration of the Numbering Plan Processor (NPP). After a message is determined to require IAR feature processing, the NPP configuration determines whether or not the CdPN parameter will be modified.

NPP processing relies on Nature of Address Indicator (NAI) values. These values are available in SCCP parameters and GSM MAP parameters, but they are not available in the CdPN and CgPN parameters of AnalyzedInformation query operations. The National Indicator bit (least significant bit) of the Nature of Number field in the CdPN and CgPN will be used wherever the NAI is called for in this document.

Interaction with Other EAGLE Functions

MTP-Routed Messages

All incoming GT-routed traffic is sent to a Service Module card by the LIM card that receives it, but MTP-routed traffic may not be. See MTP-Routed AnalyzedInformation Message Processing.

The Gateway Screening (GWS) feature on a LIM card inspects message traffic before it is directed to a Service Module card. GWS can be used to select incoming MTP-routed traffic for Service Module card processing on a linkset basis.
The MTP Routed Messages for SCCP Applications feature can be used to direct all MTP routed SCCP messages to Service Module cards for service selection processing.

IS41 GSM Migration

When the IGM feature is ON; an IS41 own-network subscriber will be associated with an RN entity and a Portability Type of 0, instead of an SP entity.

2.1.1 MTP-Routed AnalyzedInformation Message Processing

An MTP-routed message is a “through-switched” message that is not generated by or destined to the EAGLE (neither the MTP OPC nor DPC is the EAGLE true point code or capability point code). An MTP-routed message is routed to the destination designated by the DPC of the MTP3 routing label.

Typically, MSUs that receive service on a Service Module card require the message to be GT-routed to the EAGLE, so that GTT service selector-based discrimination can be applied to the message to select a specific service (such as TTR or IDPR). Some MTP-routed messages might not contain Global Title digits (GTI=0); they are referred to as "GTI=0" messages. The GTT Service Selector cannot be applied.

The IAR Base feature can process MTP-routed SCCP messages with SCCP CdPA GTI=0 and an ANSI TCAP Query With Permission package that has a Invoke Last component that contains an ANLYZD operation. One of the following methods can be used:

The MTP Routed Messages for SCCP Applications (MTP Msgs for SCCP Apps) feature

The feature is available system-wide and sends all MTP-routed SCCP messages from LIM cards to Service Module cards for processing.

The feature can be enabled and turned on when the GTT feature is turned on.

The feature can be turned on when the IAR Base feature is turned on.
The MTP Routed GWS Stop Action feature with Gateway Screening

The MTP Routed GWS Stop Action feature (Part Number 893-0356-01; also called MTPRTD GWS Stop Action) can be turned on and off after it has been enabled.

The Gateway Screening SCCP Stop Action can be provisioned only if the MTP Routed GWS Stop Action feature is enabled, and must be the last stop action in the GWS action set.

The SCCP Stop Action is mutually exclusive with the TIF, TIF2, TIF3, TLNP, CNCF and RDCT Stop Actions. Screening with the SCCP Stop Action occurs only when the MTP Routed GWS Stop Action feature is turned on.

When the MTP Routed GWS Stop Action feature is on, and Gateway Screening (GWS) is provisioned to screen MSUs using the GWS SCCP Stop Action, only UDT, UDTS, XUDT, and XUDTS SCCP messages are sent from a LIM card to a Service Module card for processing.

Gateway Screening is applied to messages on a linkset basis, and it is applied to all traffic on that linkset. The GWS SCCP Stop Action must be configured to process MTP-routed traffic on appropriate linksets.

In case of failure, the screened MSU continues with MTP routing. (Failure is the LIM card could not deliver MSU to SCCP Service Module due to some reason, such as all Service Module cards are out of service or Service Module cards deny service grant.)

Both the MTP Routed GWS Stop Action and MTP Msgs for SCCP Apps features can be turned on at the same time.

When both features are turned on, the MTP Msgs for SCCP Apps feature takes precedence over the MTP Routed GWS Stop Action feature. The MTP Msgs for SCCP Apps feature forwards the SCCP message to a Service Module card whether or not the message is screened by the GWS SCCP Stop Action.

When a Service Module card receives an MTP-routed AnalyzedInformation message that has GTI=0 in the Address Indicator, the IAR Base feature is selected to process the message.

The IAR Base feature processes only those GTI Zero messages that are bound for a Home SCP.

The IAR Base feature performs DPC Screening on the message.

The message DPC is compared with DPCs with the HOMESCP option provisioned in the Destination table.
If a matching DPC that is a full point code for a Home SCP is found, then the IAR Base feature will continue processing the message.
Otherwise, the message is dismissed.

The IAR Base feature processing for GTI=0 messages that pass the DPC screening is the same as the processing other AnalyzedInformation messages, as described in IAR Pre-NPP Processing, NPP Processing for IAR Features, and IAR Base Post-NPP Processing.

After the MTP-routed SCCP message is processed by a Service Module card, the MSU is MTP routed if the processing indicates to do so. If the message was dismissed due to errors in processing, the message is relayed without modification.

While routing the MTP-routed SCCP message to its destination, if the DPC is not defined in the Route table, then UIM 1004 is generated along with a TFP to the adjacent node. The message is discarded.

2.1.2 Hardware Requirements

EPAP-related features that perform an RTDB lookup require Service Module cards (E5-SM4G, E5-SM8G-B, or SLIC cards) running the SCCPHC application. The EAGLE can be equipped with up to 32 (31+1) Service Module cards.

Features that do not perform an RTDB lookup require Service Module cards only for GTT processing that might be performed for the feature. These features can coexist in systems with EPAP, but do not require an EPAP connection.

2.1.3 MPS/EPAP Platform

Oracle provides the Multi-Purpose Server (MPS) platform as a subsystem of the Oracle Communications EAGLE. The MPS provides support for EPAP-related features that perform Real Time Database (RTDB) lookups.

The MPS is composed of hardware and software components that interact to create a secure and reliable platform. For details about the MPS hardware, refer to Application B Card Hardware and Installation Guide. The MPS provides the means of connecting the customer provisioning application with the EAGLE and accepts the customer number portability data, while accommodating numbers of varying lengths.

The Oracle Communications EAGLE Application Processor (EPAP) is software that runs on the MPS hardware platform. EPAP collects and organizes customer provisioning data, and forwards the data to the EAGLE Service Module cards. For detailed information about EPAP, refer to Administration Guide for EPAP.

In this manual, Service Module card refers to an E5-SM4G, E5-SM8G-B, or SLIC card unless a specific card is required. For more information about the supported cards, refer to Hardware Reference.

2.2 IAR Base Feature Message Processing

The IAR Base feature provides the message processing functions upon which the other IAR-related features are built. The other IAR-related features modify how AnalyzedInformation messages are handled as they pass through the IAR Base feature. The IAR Base feature performs all AnalyzedInformation message processing.

The IAR Base feature processes AnalyzedInformation messages that are sent from an MSC to an SCP or SN.

Called Party Number (CdPN) parameters are used to carry B-Party numbers in MAP messages. WIN AnalyzedInformation operations have one or two CdPNs: the DSTDGTS parameter, the DGTSDIAL parameter, or both. ANSI AnalyzedInformation messages use only the DGTSDIAL parameter.
Calling Party Number (CgPN) parameters are used to carry A-Party numbers in MAP messages. Both WIN and ANSI AnalyzedInformation messages use the CPNDGTS1 parameter to carry the CgPN.
The IAR Base feature only uses A-Party and B-Party numbers that are encoded using the Binary Coded Decimal (BCD) format.

A message that reaches the Service Module card when the IAR Base feature is enabled and turned on is subjected to further analysis to determine if it needs processing by the IAR Base feature.

IAR Base feature message processing has four main components:

Service Selector processing
IAR pre-NPP processing
NPP processing for IAR
IAR post-NPP processing

IAR Base message processing has the following considerations:

All messages that are received by the TTR Service Selector on the Service Module card are eventually routed, whether or not they are modified first.
A message that is routed to the IAR Base feature from the TTR Service Selector may not pass IAR pre-NPP processing.
A message that passes through NPP processing still may not have any IAR-specific modification made to it.

2.2.1 Service Selection for AnalyzedInformation Messages

On a Service Module card, the service selection process selects messages for IAR processing in the following sequence of steps:

Check for SCCP CdPA GTI=0.

If GTI is not 0, service selection continues as described in Step 2.

If GTI=0, verify that the IAR Base feature is on.

If the IAR Base feature is not on, the message is dismissed.

If the IAR Base feature is on, the message is sent to the IAR Base feature for Pre-NPP processing See IAR Pre-NPP Processing.

Additional service selection is bypassed, because GTI=0 messages do not contain the GT information in the CdPA parameter that is required for the additional service selection.
Decode the SCCP layer to identify the CdPA and CgPA parameters.

Decoding errors cause the message to be dismissed.
Compare provisioned Service Selector data to the CdPA SCCP data (Global Title Indicator, - GTI Subsystem Number, SSN Translation Type - TT, Nature of Address Indicator - NAI, and Numbering Plan - NP) to determine whether the TTR service applies to the message.

The message will be handled by another service or dismissed if the TTR service is not selected.

If the TTR service is selected, processing continues with Step 4.
The TTR service verifies that the TCAP layer of the message starts with a PRIVATE tag (the ANSI TCAP Package Type is defined using PRIVATE tag values).

If the PRIVATE tag is present, the TTR service verifies that the IAR Base feature is on.

If the IAR Base feature is on, the IAR Base feature begins IAR Pre-NPP processing on the message. See IAR Pre-NPP Processing.

If the IAR Base feature is not on, the message is dismissed.

2.2.2 IAR Pre-NPP Processing

The IAR Base feature applies IAR pre-NPP processing to SCCP UDT message and unsegmented XUDT messages; all other SCCP messages are dismissed.

The IAR Base feature applies pre-NPP screening to a message in the following sequence:

Note:

NPP processing relies on Nature of Address Indicator (NAI) values. These values are available in SCCP parameters and GSM MAP parameters, but they are not available in the CdPN and CgPN parameters of AnalyzedInformation query operations. The National Indicator bit (least significant bit) of the Nature of Number field in the CdPN and CgPN will be used wherever the NAI is called for in this document.

DPC Screening or SCCP CdPA GT Digit Screening

DPC Screening
The IAR Base feature applies DPC Screening to MTP-routed messages with SCCP CdPA GTI=0.
- DPC screening compares the message DPC with DPCs provisioned with the HOMESCP option in the Destination table.
- If a matching DPC that is a full point code for a Home SCP is found, the IAR Base feature processing continues for the message.
- If no Home SCP DPC match is found, the message is dismissed.
SCCP CdPA GT Digit Screening
The IAR Base feature applies CdPA GT Digit Screening to GT-routed and MTP-routed messages with SCCP CdPA GTI not 0.
CdPA GT Digit Screening can be used to make sure that the IAR Base feature processes only messages that are bound for a customer Home SCP.
- The IAR Base feature compares the CdPA parameter GT digits to a list of digits string values provisioned in the GT list of the Common Screening List (CSL) table.
- The IAR Base feature continues processing the message only if a match is found.
- If a match is not found, the message is dismissed.

TCAP and MAP Decoding

The IAR Base feature decodes the TCAP portion of the message to continue processing. The IAR Base feature checks the structure of the message, checks to make sure that the message carries an AnalyzedInformation operation, and identifies the MAP CdPN and CgPN parameters.

The message must contain an ANSI TCAP Query with Permission package; if not, the message is dismissed.
The IAR Base feature uses and modifies only data within the first Invoke Last TCAP component portion of the message.
The IAR Base feature handles WIN Standard Phase 2 ANLYZD operations.
The MAP layer can contain a DSTDGTS parameter, a DGTSDIAL parameter, or both.
- If only a DSTDGTS parameter is present, or both parameters are present, the DSTDGTS parameter is used as the CdPN.
- If only a DGTSDIAL parameter is present, the DGTSDIAL parameter is used as the CdPN.
- If neither parameter is present, UM 1427 is generated and the message is dismissed.
The MAP layer CPNDGTS1 parameter is used as the CgPN.
- If the CPNDGTS1 parameter is not present, UIM 1428 is generated and the message is dismissed.
- Messages that contain TCAP decoding errors relating to the CgPN parameter will be dismissed and the associated UIM will be issued, only if and when CgPN processing is to be used - if the IARCDPN service invokes the IARCGPN service.
If the CdPN or CgPN parameter is not encoded in BCD format, UIM 1427 or UIM 1428 is generated and the message is dismissed.
If the MAP layer does not contain a TRIGTYPE parameter, UIM 1429 is generated and the message is dismissed.

Trigger Type Screening

The message TRIGTYPE parameter indicates the kind of trigger that caused the AnalyzedInformation message to be sent:

The Calling_Routing_Address_Available trigger that trips when an MSC has all of the information it needs to route a call
The Initial_Termination and Called_Routing_Address_Available triggers that trip when an MSC is handling a call to a prepaid subscriber

The IAR Base feature compares the message TRIGTYPE parameter value to numeric values provisioned in the TRIGTYPE list of the CSL table.

The IAR Base feature continues processing only if an exact match is found.

If an exact match is not found, the message is dismissed.

SCCP CgPA Default Country Code (DEFCC) Check

This check can be used when a roaming subscriber dials a number that is local to the area in which he is roaming, and uses the national number format instead of international format. MNP control does not need to be applied across international boundaries. The IAR Base feature will not process messages sent on behalf of a roaming subscriber calling a number in national format.

CgPA DEFCC screening is enabled and disabled by the CGPACCCK configuration option, independent of provisioning of the STPOPTS DEFCC option.

The check is not performed if the CGPACCCK option value is NONINTL and the CdPN National Indicator bit of the Nature of Number field is INTL.
The check is not performed if the SCCP CgPA does not contain GT digits (GTI=0), or if the SCCP CgPA contains and NAI (GTI=4) and the SCCP CgPA NAI is not International.

If the CGPACCCK option is on, the IAR Base feature compares the SCCP CgPA parameter value to a provisioned Default Country Code (STPOPTS DEFCC parameter value).

The IAR Base feature will continue processing only if the SCCP CgPA matches the Default Country Code.
If no match is found, the message is dismissed.

2.2.3 NPP Processing for IAR Features

If a message passes all IAR pre-processing, then NPP processing is applied to it.

Refer to Numbering Plan Processor (NPP) User's Guide for descriptions of NPP components and procedures for NPP provisioning.

Note:

NPP processing relies on Nature of Address Indicator (NAI) values. These values are available in SCCP parameters and GSM MAP parameters, but they are not available in the CdPN and CgPN parameters of AnalyzedInformation query operations. The National Indicator bit (least significant bit) of the Nature of Number field in the CdPN and CgPN will be used wherever the NAI is called for in this document.

The IAR Base feature defines two NPP services:

IARCDPN - The service that processes Called Party (CdPN; B-Party) Numbers

The IAR Base feature invokes IARCDPN for every message that passes IAR pre-NPP processing.

The value of the National Indicator bit of the Nature of Number field of the CdPN is passed as the NAI to NPP when the IARCDPN service is applied to the message.

The IARCDPN service always executes before the IARCGPN service. The IARCDPN service Rule must be provisioned with the CgPNSVCRqd, CgPNASDRqd, or CgPNGRNRqd Service Action to invoke the IARCGPN service.
IARCGPN - The service that processes Calling Party Number (CgPN), A-Party) Numbers.

The IARCGPN service is invoked only by the IARCDPN service when the CgPNSVCRqd, CgPNASDRqd, or CgPNGRNRqd Service Action is provisioned in the NPP Rule.

The value of the National Indicator bit of the Nature of Number field of the CgPN is passed as the NAI to NPP when the IARCGPN service is applied to the message.

IAR Base NPP processing consists of the following functions:

Verify that the IARCDPN service status is ON.
Execute IARCPDN processing.
- Apply NPP filters to select the appropriate NPP Rule for the message processing.
- Execute provisioned Conditioning Actions and Service Actions.
  - The Conditioning Actions can condition the CdPN digit string RTDB lookup, and can extract data to populate the values for the provisioned Formatting Actions.
  - The CDPNNP Service Action can be executed to apply number portability processing if the IAR NP feature is on, apply Service Portability processing if the Service Portability feature is on, and populate provisioned Formatting Action values.
- If the CgPNSVCRqd, CgPNASDRqd, or CgPNGRNRqd Service Action is provisioned in the NPP Rule, call the IARCGPN service.
  - Execute IARCGDN processing.
    - Apply NPP filters to select the appropriate NPP Rule for the message processing.
    - Execute provisioned Conditioning Actions and Service Actions.
      
      The Conditioning Actions can condition the CgPN digit string for RTDB lookup, and can extract data to populate the values for the provisioned Formatting Actions.
      
      The CGPNNP Service Action can be executed to apply number portability processing if the IAR NP feature is on, and populate provisioned Formatting Action values.
    - Execute Formatting Actions for modifying the CgPN in the outgoing digit string if required by provisioning and processing results.
Execute Formatting Actions for modifying the CdPN in the outgoing digit string, if required by provisioning and processing results.

Conditioning Actions

The IARCDPN and IARCGPN services can use all general NPP Conditioning Actions.

Service Actions

For each service, the NPP service status must be ON for service processing to occur.

The IAR Base feature NPP services use the Service Actions shown in Table 2-1.

Table 2-1 IAR Base Feature NPP Service Actions

Service Action	Feature	Precedence	IARCDPN	IARCGPN
ASDLKUP	IAR ASD	50	Yes	Yes
CCNCCHK	IAR Base	100	Yes	No
CDIAL	IAR Base	10	Yes	Yes
CDPNNP	IAR NP	80	Yes	No
CgPNASDRqd	IAR ASD	50	Yes	No
CgPNGRNRqd	IAR GRN	50	Yes	No
CGPNNP	IAR NP	80	No	Yes
CgPNSVCRqd	IAR Base	60	Yes	No
GRNLKUP	IAR GRN	50	Yes	Yes

Provisioning restrictions require specific features to be enabled when defining NPP Rules. The status of each of the ON/OFF features is also checked at run-time. The ASDLKUP and CGPNASDRQD cannot be provisioned in the same Rule. The GRNLKUP and CGPNGRNRQD Service Actions cannot be provisioned in the same Rule.

In the following Service Action summaries, the term DN is used to describe a value that is the result of applying Conditioning Action execution to the digit string passed into an NPP service. The DN within the IARCDPN service is the CdPN in international format. The DN within the IARCGPN service is the CgPN in international format.

ASDLKUP - Populates the ASD Formatting Action value using the ASD found in the RTDB lookup.
CCNCCHK - Highest precedence Service Action for IAR. Compares the first digits of the DN to the entries in the CCNC list of the CSL table. If a match is found, NPP processing continues. If a match is not found, all other Service Actions in the NPP Rule are ignored,, the message is not modified, and the message is dismissed.
CDiAL - Requests Formatting Action execution to be performed even when the prior Service Action requested that it be skipped.
CDPNNP - Applies CdPN number portability functions for IARCDPN when the IAR NP feature is on; applies Service Portability functions when the feature iand option are onapplies Service Portability and S-Port Differentiation functions when the features and options are on; evaluates the result of an RTDB lookup based on the TATROPTS CDNPTYPE option value, or on the SPORTTYPE option value for Service Portability. Populates the RN or SP Formatting Action value with the data from the RTDB lookup or the provisioned DFLTRN option value, depending on provisioning and lookup results. Populates the SRFIMSI Formatting Action value with the SRFIMSI associated with the RN or SP entity from the RTDB, if any.
CGPNASDRQD - Used by the IARCDPN service to invoke the IARCGPN service, and to populate the ASD Formatting Action value prior to IARCDPN Formatting Action execution.
CGPNGRNRQD - Used by the IARCDPN service to invoke the IARCGPN service, and to populate the GRN Formatting Action value prior to IARCDPN Formatting Action execution.
CGPNNP - Applies CgPN number portability functions when the IAR NP feature is on and the IARCGPN service is invoked; evaluates the result of an RTDB lookup based on the TATROPTS CGNPTYPE option value. Populates the SRFIMSI Formatting Action value with the SRFIMSI associated with the RN or SP entity from the RTDB, if any.
CDPNSVCRQD - Used by the IARCDPN service to invoke the IARCGPN service for CgPN processing.
GRNLKUP - Populates the GRN Formatting Action value using the GRN found in the RTDB lookup.

Formatting Actions

Both services can use all general NPP Formatting Actions.

Formatting Action execution can modify the CdPN or CgPN, or both, in the outgoing digit string before IAR NPP post-processing begins.

2.2.3.1 NPP RTDB Lookup and NPTYPE Evaluation

RTDB lookup is performed at the request of the CDPNNP and CGPNNP Service Action Handlers that are used by the IARCDPN and IARCGPN services.

RTDB lookup is performed once per service execution.

A conditioned number of maximum 15 digits is used to query RTDB records for individual subscribers. If a matching record is found then processing continues based on that record. Otherwise, the number is used to query RTDB records for subscriber groups. If a match is found, processing continues based on that record.

The NPTYPE Evaluation process uses the result of the RTDB Lookup process, and is guided by either the TATROPTS:CDNPTYPE or TATROPTS:CGNPTYPE option value. The option value is used to determine whether the lookup result was a success or a failure. For example, if the option is set to SP then the lookup result is a success only if a matching record was found and that record contains an SP entity.

For the IARCDPN service, the CdPN from the message is conditioned, and the lookup success is determined by the TATROPTS CDNPTYPE option value.
For the IARCGPN service, the CgPN from the message is conditioned, and the lookup success is determined by the TATROPTS CGNPTYPE option value.

Table 2-2 NPTYPE Evaluation Success

Configuration Option Value	Success Criteria
RN	An RTDB match is found with an RN entity and PT is not 0. An RTDB match is found with an RN entity and PT = 0, if the Service Portability feature is not enabled or the IGM feature is OFF.
SP	An RTDB match is found with an SP entity. An RTDB match is found with an RN entity and PT = 0 if the Service Portability feature is enabled or the IGM feature is ON.
RNSP	An RTDB match is found with an RN or SP entity.
RNSPDN	An RTDB match is found with an RN or SP entity.
ALWAYS	Always matches
ANYMATCH	An RTDB matching record exists.

IS41 GSM Migration (IGM) Feature

IGM functions are applied by the CDPNNP and CGPNNP Service Actions. When the IGM feature is ON, the IAR NP feature interprets RTDB subscriber data slightly differently: A customer’s own IS41 subscribers are associated with RN entities that have a Portability Type of 0. This affects the NPTYPE Evaluation procedure.

Table 2-3 NPTYPE Success Criteria for IGM Feature and Service Portability Feature

NPTYPE Option	Success
RN	When an RTDB match is found with an RN entity that has a Portability Type other than 0
SP	When an RTDB match is found with an SP entity, or an RN entity that has a Portability Type of 0
RNSP	When an RTDB match is found with an RN or SP entity
RNSPDN	When an RTDB match is found with an RN or SP entity
ALWAYS	Always
ANYMATCH	When an RTDB match is found

This data interpretation also applies for the purposes of RN and SP Formatting Action population; when the IGM feature is ON, and the IAR NP feature is handling an IS41 subscriber associated with an RN entity with Portability Type of 0, the RN entity is treated as if it were an SP entity in Table 2-4.

2.2.3.2 IAR NPP Number Portability

The IAR Number Portability feature (IAR NP) can be called by the IAR Base feature to apply Number Portability functions using both the CDPNNP and CGPNNP NPP Service Actions. See IAR Number Portability Feature.

When the Service Portability feature is on with the IAR NP feature, the the CDPNNP and CGPNNP NPP Service Actions can also apply service portability functions. See Service Portability for IAR NP.

The S-Port Subscriber Differentiation feature can work with the Service Portability feature to allow use of ASD digits to provide an additional routing number per in-network subscriber (in addition to the GRN routing number per in-network subscriber). Subscribers without ASD provisioned will follow standard S-Port processing and will always use GRN. See S-Port Subscriber Differentiation.

NPP Formatting Action value population occurs when the RTDB lookup success criteria are met (see NPP RTDB Lookup and NPTYPE Evaluation). If the success criteria are not met, then the CDPNNP and CGPNNP Service Action Handlers will request that Formatting Action execution be skipped for the respective service only.

Note:

The TATROPTS:DFLTRN option value overrides an SP entity when one is provisioned in the RTDB.

When the RTDB does not contain an RN or SP entity, but the NPTYPE Evaluation success criteria are still met (ALWAYS or ANYMATCH), then neither the RN Formatting Action value nor the SP Formatting Action value is changed.

Table 2-4 Number Portability NPTYPE RN and SP Formatting Action Population

NPTYPE Option	RTDB has RN Entity	SP Entity and DFLTRN	SP Entity No DFLTRN
RN	Set RN Formatting Action value to RTDB RN. SP Formatting Action value not changed.	(failure)	(failure)
SP	(failure)	Set RN Formatting Action value to DFLTRN. SP Formatting Action value not changed.	RN Formatting Action value not changed, SP Formatting Action value set to RTDB SP.
RNSP	Set RN Formatting Action value to RTDB RN. SP Formatting Action value not changed.
RNSPDN
ALWAYS
ANYMATCH

2.2.4 IAR Base Post-NPP Processing

The IAR Base feature pulls together the results of the IARCDPN and IARCGPN service processing to determine whether or not the message should be modified.

If required, the message is encoded with any modified parameters.

The IARPASSD and IARFAILD measurement pegs are updated.

The message is routed.

2.3 IAR Number Portability Feature

The Number Portability (IAR NP) feature, the Numbering Plan Processor (NPP), the Service Portability feature, and the S-Port Subscriber Differentiation feature support Mobile Number Portability (MNP), Service Portability (S-Port), and S-Port Subscriber Differentiation functions.

The Number Portability (IAR NP) feature, the Numbering Plan Processor (NPP), and the Service Portability feature support Mobile Number Portability (MNP) and Service Portability (S-Port).

IAR NP uses provisioning of subscriber data to treat messages that relate to ported subscribers differently than it does non-ported subscribers. In this way, other entities in the customer network can treat these subscribers differently by simply reacting to the message data screened and manipulated by the EAGLE, rather than having to distinguish one kind of subscriber from another themselves.

Feature and NPP configuration options can be used to identify which AnalyzedInformation messages need processing by IAR-related features.

After the IAR Base feature determines that an AnalyzedInformation message requires IAR processing, IAR NP can perform an RTDB lookup using the digit string in the CdPN parameter or the CgPN parameter, or both. RTDB subscriber data from the the lookup results can be used to identify which subscribers belong to a customer's own network and which belong to a foreign network.

Depending on the RTDB lookup results, IAR NP can modify RN and DN of the CdPN parameter or the CgPN parameter, or both, in the message. If the Service Portability feature is used with IAR NP and GRN data is found in the RTDB lookup, the IAR NP feature can use the GRN data to modify the CdPN RN.

When IAR NP and NPP processing is complete for the message, the IAR Base feature relays the message to the originator.

2.3.1 Service Portability for IAR NP

With the Service Portability feature (Part Number 893034301), the subscriber can port to a different network technology with the same service provider. Service Portability is applied only to the subscribers served by the customer's own network.

The subscriber is considered as an own-network IS41 subscriber if the Entity type is RN and the Portability Type is 0 (RN/PT=0). In the case of RN/PT=0, the RN for this subscriber is considered to be the SP (the IS-41 HLR address).
The subscriber is considered as an own-network GSM subscriber if the Entity type is SP with any Portability Type.

Service Portability is handled by the NPP CDPNNP Service Action Handler in the IAR NP feature. The SPORTTYPE option in the TATROPTS table controls the mode of Service Portability that is applied for IAR NP. The SPORTTYPE option has the following values:

NONE - Apply standard NP processing for own-network GSM and IS41 subscribers.
GSM - Use the GSM Service Portability prefix (GRN) for GSM own-network subscribers, and apply standard NP processing for own-network IS41 and OLO subscribers.
IS41 - Use the IS41 Service Portability prefix (GRN) for Is41 own-network subscribers, and apply standard NP processing for own-network GSM and OLO subscribers.
ALL - Use the GSM Service Portability prefix (GRN) for GSM own-network subscribers, use the IS41 Service Portability prefix (GRN) for IS41 own-network subscribers, and apply standard NP processing for OLO subscribers.

The NPTYPE Evaluation criteria for the Service Portability feature are the same as those for the IGM feature. See Table 2-3.

After the Service Portability feature is considered to be applicable, the CDPNNP Service Action uses the subscriber GRN data in the RTDB to populate the the Service Portability prefix in the RN Formatting Action value.

If the GRN is not present in the RTDB, then UIM 1426, “S-Port: Missing GRN for srvc prtd subs” is generated indicating that Service Portability could not be applied due to missing Service Portability data.

2.3.1.1 S-Port Subscriber Differentiation

S-Port Subscriber Differentiation can be used with Service Portability to allow use of provisioned ASD digits in place of GRN digits as an alternative Routing Number for own-network subscribers. For example, the ASD can be used as the subscriber’s private routing number (for message relay features) and the GRN as the subscriber’s public routing number (for query/response features).

The S-Port Subscriber Differentiation controlled feature (Part Number P/N 893-0379-01) and the SCCPOPTS SUBDFRN configuration option control S-Port Subscriber Differentiation operation. The SUBDFRN option cannot be provisioned unless the S-Port Subscriber Differentiation feature is enabled and turned on.

When the Service Portability feature and option are on, the S-Port Subscriber Differentiation feature and option are on, and Service Portability is applicable, then provisioned ASD digits are used in place of GRN digits.Subscribers without ASD provisioned will follow standard Service Portability processing and will always use GRN.

2.3.1.2 S-Port and NPP Configuration Recommendations

For features that use Service Portability and the Numbering Plan Processor (NPP), feature-specific configuration options, EPAP, and EAGLE data and NPP Formatting Actions work together to produce the “routing tag” that is used to modify digits in applicable messages. A “routing tag” is the Number Portability or Service Portability digits chosen to prefix the DN. Own-network GSM and IS41 subscribers can be tagged with the GRN (from EPAP entity data), the DFLTRN configuration option value, SP (EPAP entity digits), or no tag. OLO subscribers can be tagged with the RN (EPAP entity digits) or no tag.

Table 2-5 indicates the recommended provisioning for features that use NPP, based on how the subscriber numbers will be tagged. Service Portability provides the capability to use the GRN to tag own-network GSM and IS41 subscribers. A few potential combinations are not supported, because standard Number Portability processing does not differentiate between GSM and IS41 subscribers.

The following acronyms are used in the table header for feature-specific configuration options. The option names are not the same across all features that use NPP, but all NPP features do provide a similar option:

NPTYPE - determines lookup success criterion
SPORTTYPE - determines which own-network subscribers to tag with the GRN prefix (IS41, GSM, all, or none)
DFLTRN – specifies feature-specific value for a default Routing Number
SPFILL – specifies whether NPP should populate both SP and RN Formatting Action values even when DFLTRN or GRN is being used for local subscribers. In some scenarios, setting SPFILL to YES can cause double digits to be present. IS41 digits (RN/PT=0) are considered SP, because they should contain an E.164 HLR ID.

Because S-Port Subscriber Differentiation operates within the Service Portability call flow, when both are on and Service Portability is applicable, then ASD digits are used, if provisioned, in place of GRN digits. If ASD digits are not provisioned, then standard Service Portability processing is used. Wherever GRN appears in Table 2-5, provisioned ASD digits will be used if S-Port Subscriber Differentiation and Service Portability are ON.

Table 2-5 Recommended NPP Provisioning for "Routing Tags"

Requested Tagging			Recommended Feature Configuration for NPP and S-Port Processing
GSM (SP/any PT)	IS41 (RN/PT=0)	OLO	NPTYPE	SPORTTYPE	DFLTRN	SPFILL	Formatting Action
GRN	GRN	RN	RNSP	ALL	N/A	N/A	RN+DN
DFLTRN	GRN	RN	RNSP	IS41	DFLTRN	N/A	RN+DN
SP	GRN	RN	RNSP	IS41	None	No	RN+SP+DN
None	GRN	RN	RNSP	IS41	None	N/A	RN+DN
GRN	DFLTRN	RN	RNSP	GSM	DFLTRN	N/A	RN+DN
DFLTRN	DFLTRN	RN	RNSP	None	DFLTRN	N/A	RN+DN
SP	DFLTRN	RN	Not supported: Use SP/GRN instead
None	DFLTRN	RN	Not supported: Use None/GRN instead
GRN	SP	RN	RNSP	GSM	None	No	RN+SP+DN
DFLTRN	SP	RN	Not supported: Use GRN/SP instead
SP	SP	RN	RNSP	None	None	N/A	RN+SP+DN
None	SP	RN	Not supported: NP does not differentiate tags for own-network subscribers
GRN	None	RN	RNSP	GSM	None	N/A	RN+DN
DFLTRN	None	RN	Not supported: Use GRN/None
SP	None	RN	Not supported: NP does not differentiate tags for own-network subscribers
None	None	RN	RN	N/A	N/A	N/A	RN+DN
GRN	GRN	None	SP	ALL	N/A	N/A	RN+DN
DFLTRN	GRN	None	SP	IS41	DFLTRN	N/A	RN+DN
SP	GRN	None	SP	IS41	None	No	RN+SP+DN
None	GRN	None	SP	IS41	None	N/A	RN+DN
GRN	DFLTRN	None	SP	GSM	DFLTRN	N/A	RN+DN
DFLTRN	DFLTRN	None	SP	None	DFLTRN	N/A	RN+DN
SP	DFLTRN	None	Not supported: Use SP/GRN instead
None	DFLTRN	None	Not supported: Use None/GRN instead
GRN	SP	None	SP	GSM	None	No	RN+SP+DN
DFLTRN	SP	None	Not supported: Use GRN/SP instead
SP	SP	None	SP	None	None	N/A	SP+DN
None	SP	None	Not supported: NP does not differentiate tags for own-network subscribers
GRN	None	None	SP	GSM	None	N/A	RN+DN
DFLTRN	None	None	Not supported: Use SP/GRN instead
SP	None	None	Not supported: NP does not differentiate tags for own-network subscribers
None	None	None	N/A	N/A	N/A	N/A	DN

2.4 IAR Additional Subscriber Data Feature

The IAR Additional Subscriber Data (IAR ASD) feature allows for the insertion of Additional Subscriber Data (ASD) from the incoming CgPN and CdPN digit strings into the CdPN of an outgoing message.

IAR ASD uses the ASDLKUP and CgPNASDRqd Service Actions for the IARCDPN service in NPP processing. The CgPNASDRqd Service Action Handler performs an RTDB lookup for the DN in the CgPN indicated by the ASDLKUP Service Action, and populates the value for the ASD Formatting Action with the found ASD.

IAR ASD uses the ASDLKUP and CgPNASDRqd Service Actions for the IARCDPN service in NPP processing.

The ASDLKUP Service Action Handler uses the ASDLKUP Service Action to perform an individual or range RTDB lookup on the conditioned CdPN, to find an entry containing an ASD digit string.
The CgPNASDRqd Service Action Handler causes the IARCGPN service to be called. The IARCGPN service performs an RTDB lookup for the DN in the CgPN indicated by the ASDLKUP Service Action, and populates the value for the ASD Formatting Action with the found ASD.

The ASDLKUP Service Action or CgPNASDRqd Service Action can coexist in the same Service Action group with any other Service Actions used by IAR features. The ASDLKUP Service Action and the CgPNASDRqd Service Action are mutually exclusive in the same Action Set.

Depending on the Formatting Action configuration for the selected NPP rule, the NPP Formatting Action execution can use the ASD in formatting the CdPN digit string in the outgoing message.

2.5 IAR Generic Routing Number Feature

The IAR Generic Routing Number (IAR GRN) feature allows for the insertion of Generic Routing Number data (GRN) from the incoming CgPN and CdPN digit strings into the CdPN of an outgoing message.

IAR GRN uses the GRNLKUP and CgPNGRNRqd Service Actions for the IARCDPN service in NPP processing.

The GRNLKUP Service Action Handler uses the GRNLKUP Service Action to perform an individual or range RTDB lookup on the conditioned CdPN, to find an entry containing a GRN digit string.
The CgPNGRNRqd Service Action Handler causes the IARCGPN service to be called. The IARCGPN service performs an RTDB lookup for the DN in the CgPN indicated by the GRNLKUP Service Action, and populates the value for the GRN Formatting Action with the found GRN.

The GRNLKUP Service Action or CgPNGRNRqd Service Action can coexist in the same Service Action group with any other Service Actions used by IAR features. The GRNLKUP Service Action and the CgPNGRNRqd Service Action are mutually exclusive in the same Action Set.

Depending on the Formatting Action configuration for the selected NPP rule, the NPP Formatting Action execution can use the GRN in formatting the CdPN digit string in the outgoing message.

2.6 IAR-Related Feature Processing

Every IAR Service Action depends upon one or more features. Some feature status checking is performed at provisioning time. Many of the IAR-related features may be turned ON and OFF at any time. All SA that are associated with features other than the IAR Base check the ON/OFF status of those features at run-time.

With all IAR-related features ON, Service Actions can perform NP, extract ASD data from the RTDB, invoke the IARCGPN service, and reformat the CdPN. However, if the IAR NP feature is OFF then Number Portability processing is not performed. Likewise, if the IAR ASD feature is OFF then the ASDLKUP SA has no effect. Turning OFF a feature can also have the side-effect of disabling use of the IARCGPN service.

The Service Portability (S-Port) feature affects only the CDPNNP Service Action and that Service Action depends upon the IAR NP feature. S-Port processing applies only when both S-Port feature and the IAR NP feature are ON. Although the S-Port feature may be ON, S-Port processing is ignored when the IAR NP feature status is OFF.

S-Port Subscriber Differentiation feature processing occurs only when the IAR NP feature is on, the Service Portability feature and option are on, the S-Port Subscriber Differentiation feature and option are on, and Service Portability is applicable.

2.7 IAR-Related Features Configuration Options

The TATROPTS table contains configuration option values for the IAR-related features, and the Service Portability feature when it is used with IAR NP. The TATROPTS option data is loaded to the LIM cards and to Service Module cards that contain the RTDB database. The configuration option values influence number conditioning, response message formatting and generation, and Service Portability processing.

TATROPTS options can be provisioned after the IAR Base feature is enabled and before the feature is turned on.

Table 2-6 describes the TATROPTS options.

Table 2-6 TATROPTS Configuration Options

Parameter	Value	Description	Notes
CDNPTYPE - Entity type for CdPN RTDB lookup performed by IAR NP. Specifies the CdPN entity type for which the lookup is considered a success.	SP	Service Provider
	RN	Routing Number
	RNSP	Routing Number or Service Provider
	ANYMATCH	RN, SP, or match with any entity
	ALWAYS	The lookup is always considered successful.
	RNSPDN	RN, SP, or DN
CGNPTYPE - CgPN entity type for RTDB lookup performed by IAR NP. Specified the CgPN entity type for which the lookup is considered a success.	SP	Service Provider
	RN	Routing Number
	RNSP	Routing Number or Service Provider
	ANYMATCH	RN, SP, or match with any entity
	ALWAYS	The lookup is always considered successful.
CGPACCCK - CgPA Country Code Check Specifies whether IAR Base checks the incoming CgPA for presence of the country code defined in the STPOPTS DEFCC option.	ALWAYS	Always check for the DEFCC value
	NONINTL	Check for the DEFCC value if the CDPN NAI is not International.	The value refers to the National Indicator bit in the Nature of Number file of the CdPN parameter. The check is performed only when the National Indicator bit in the Nature of Number field of the CdPN is not INTL.
	OFF	The DEFCC check is not performed.
DFLTRN - Default Routing Number Specifies the default RN that is used when a value of SP or RNSP is specified for the CDNPTYPE or CGNPTPE parameter, and the CdPN or CgPN RTDB lookup finds entity type SP.	1-15 hex digits
	NONE	A default RN is not used.
SPORTTYPE - Service Portability Type Specifies whether Service Portability is performed for the feature.	NONE	Service Portability is not performed for IAR NP.	Can be provisioned only when the IAR Base, IAR NP, and Service Portability features are enabled.
	GSM	Apply Service Portability prefix (RTDB GRN entity ID) for own-network GSM subscribers
	IS41	Apply Service Portability prefix (RTDB GRN entity ID) for own-network IS41 subscribers
	ALL	Apply Service Portability prefix (GRN from RTDB entity) for all own-network subscribers

2.8 Destination-based Configuration Options for IAR Pre-NPP Processing

The Destination table can contain an IAR-related option value for destination point codes. The HOMESCP option contains a flag that is used by IAR pre-NPP processing for messages with GTI=0 to determine if the associated full point code is for a Home SCP.

See EAGLE Commands and Commands User's Guide for a description of the destination-based option for IAR and the EAGLE commands that are used to configure the option.

2.9 SCCP Options Configuration Option for S-Port Subscriber Differentiation

The SCCPOPTS SUBDFRN option turns the S-Port Subscriber Differentiation function on and off in the system. The S-Port Subscriber Differentiation feature must be enabled and turned on before the option can be provisioned..

See EAGLE Commands and Commands User's Guide for a description of the SCCPOPTS SUBDFRN option and the EAGLE chg/rtrv-sccpopts commands that are used to configure the option.

2.10 EAGLE Commands

This section describes commands that can be used for the configuration of the Info Analyzed Relay-related features.

Refer to Commands User's Guide for complete descriptions of the following commands, including parameter names, valid values, and output examples for the commands.

Table 2-7 Commands used for IAR-Related Features

Type	Commands
System Serial Number	ent/rtrv-serial-num
Card	ent/dlt/rtrv/alw/inh/init/rept-stat-card
Numbering Plan Processor (NPP)	ent/chg/dlt/rtrv-npp-as, ent/chg/dlt/rtrv-npp-srs, chg/rtrv-npp-serv
STP Options	chg/rtrv-stpopts
Feature Control	chg/rtrv-feat, enable/chg/rtrv-ctrl-feat
Service Selector	chg/dlt/ent/rtrv-srvsel
Common Screening List	chg/rtrv-csl
TATR Options	chg/rtrv-tatropts
SCCP Options	chg/rtrv-sccpopts
Destination Option	ent/chg/dlt/rtrv-dstn
Test Tool	chg/rtrv-tatr-msg, tst-msg

ent/chg/dlt/rtrv-npp-as, ent/chg/dlt/rtrv-npp-srs, chg/rtrv-npp-serv

The NPP commands are used to provision and display the values for components that are used in NPP processing.

chg/rtrv-stpopts

The STP Options commands are used to provision system options for the EAGLE. The options are used to control system-level processing. Features can check the option values to determine what processing to apply. The IAR-related features and the ANSIGFLEX option cannot be used together in the same system. The DEFCC option defines the Default Country Code, which is used in the CgPA DEFCC Check to identify message from the home network that should not be modified.

enable/chg/rtrv-ctrl-feat

These commands are used to enable, turn on, and display the on/off status of IAR-related features and the Service Portability feature.

ent/dlt/chg/rtrv-srvsel

The service selector commands are used to provision and display service selector information for the ttr service that is used by the IAR Base feature.

ent/chg/dlt/rtrv-csl

Common Screening List commands are used to define, change, and display screening requirements of various features. The screenings are performed on digit strings. For the IAR Base feature, 3 screening lists are used. Each screening list is based on digit strings.

GT screening list - The SCCP CdPA is compared to this list to determine if IAR Base feature processing should be applied to the message. If not found, the message is dismissed.
CCNC screening list - The conditioned TCAP DN in international format is compared to this list. If not found, the message is dismissed.
TRIG screening list - The TRIGTYPE from the incoming message is compared to this list. If not found, the message is dismissed.

chg/rtrv-tatropts

The TATR Options commands are used to provision the configuration options for the IAR Base, IAR NP, and Service Portability features. The options control number portability, Service Portability, and NPP processing for incoming messages and formatting of response messages.

chg/rtrv-sccpopts

The SCCP Options commands are used to provision SCCP options for the EAGLE. The SUBDFRN option is used to turn on and off the S-Port Subscriber Differentiation function.

ent/chg/dlt/rtrv-dstn

The destination commands are used to provision destination point codes (DPCs). The IAR Base feature uses the flag that is set by the homescp=yes parameter to identify a DPC as a Home SCP.

chg/rtrv-tatr-msg, tst-msg

The chg/rtrv-tatr-msg commands are used to enter and display up to 10 test messages in the TESTMSG table. The messages can be sent by the tst-msg command to the provisioned IAR Base feature to verify call flow.