4 Feature Configuration
This chapter provides procedures for configuring the IAR-related features for use in the EAGLE. Procedures are included for configuration of the Service Portability feature and the S-Port Subscriber Differentiation feature for use with the IAR NP feature.
This chapter also provides procedures for configuring the ANSI41 AIQ feature.
Introduction
- IAR-related features (IAR Base, IAR NP, IAR ASD, IAR GRN)
- The Service Portability feature and the S-Port Subscriber Differentiation feature for use with the IAR NP feature
- The ANSI41 AIQ feature
Each section includes a configuration procedure that lists the steps for enabling and turning on each feature, and for the provisioning required for the features. Each step contains a link or reference to information and procedures to use to complete the step. Feature provisioning can be performed after the features are enabled and before the features are turned on.
Note:
Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.System Prerequisites
Before any feature that is described in this manual can be enabled, the prerequisites listed in Table 4-1 are required in the system.
Table 4-1 System Prerequisites
Prerequisite | Verification and Provisioning |
---|---|
The system serial number must be correct and locked. For new installations, the system is shipped with an unlocked serial number. The serial number can be changed if necessary and must be locked after the system is on-site. For systems that are being upgraded, the serial number is usually already verified and locked. |
Note: The serial number cannot be changed after it is entered
and locked in the system.
Locate the serial number for the system on a label affixed to the control shelf (1100). Enter the Verify that the displayed serial number is correct for the system. If no
serial number is displayed, enter the Enter the |
A sufficient number of Service Module cards must be equipped. |
Enter the If more cards or cards of a different type are needed, refer to the procedures in Database Administration - GTT User's Guide to add or remove Service Module cards. |
The GTT feature must be on in the system. Some features require an additional GTT-related feature such as EGTT. See the specific feature prerequisites in this section. |
Enter the If the GTT feature is on, the gtt=on entry appears in the output. If the gtt=off entry appears in the output, use the procedures in Database Administration - GTT User's Guide to turn on and provision the GTT feature and any other GTT-related features and functions that will be used in the system. |
IAR-Related Features Configuration
- Configuration of the Service Portability feature and the S-Port Subscriber Differentiation feature for use with the IAR NP feature
- Configuration of the Gateway Screening (GWS) feature and the MTP Routed GWS Stop Action feature to filter MTP-routed UDT, UDTS, XUDT, and XUDTS SCCP messages for Service Card module processing
- Configuration of the MTP Routed Messages for SCCP Applications feature to forward all MTP-routed AnalyzedInformation messages for Service Module card processing
Configuration Procedure for IAR-Related Features lists the steps for enabling and turning on the features, and for the provisioning required for the features. Each step contains a link or reference to information and procedures to use to complete the step. Feature provisioning can be performed after the features are enabled and before the features are turned on.
Note:
Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.IAR-Related Feature Prerequisites
Before any IAR-related feature can be enabled, the following prerequisites are required in the system:
Table 4-2 IAR-Related Feature Prerequisites
Prerequisite | Verification and Provisioning |
---|---|
The ANSIGFLEX system option cannot be set to Yes. |
Enter the Verify that the ANSIGFLEX entry does not appear in the command output or that the ANSI GFLEX entry shows a value of No. |
The LNP feature cannot be on in the system |
Enter the If the LNP feature is on, shown with a quantity greater than zero for the LNP ported TNs entry in the command output, features described in this manual cannot be enabled. |
If the MTP Routing GWS Stop Action feature will be used to select UDT, UDTS, XDT, and XDTS MTP-routed messages for IAR processing:
|
Refer to the procedures in Database Administration - GWS User's Guide. |
Configuration Procedure for IAR-Related Features
- Verify, and provision if needed, the system prerequisites. See System Prerequisites.
- Verify, and provision if needed, the feature prerequisites. See IAR-Related Feature Prerequisites.
- Verify that the Default Country Code value for the STPOPTS DEFCC parameter is not NONE. Refer to the
chg-stpopts
andrtrv-stpopts
command descriptions in Commands User's Guide to change and display the STPOPTS DEFCC value. - Enable the IAR Base feature, and enable IAR-related features (IAR NP, IAR ASD, IAR GRN) if they are needed. See Enabling IAR-Related Features.
-
Provision NPP for use with IAR features. See Provisioning NPP for IAR-Related features.
- Provision NPP Action Sets and Service Rule Sets
- Provision NAI mapping values for IAR services
- Set the NPP service status to ON for each IAR service
- Enable the Service Portability feature, if it will be used with the IAR Base feature. See Enabling the Service Portability Feature.
- Enable the S-Port Subscriber Differentiation feature if it will be used with the Service Portability feature. See Enabling the S-Port Subscriber Differentiation Feature.
- Provision the service selector for IAR features (ttr). See Provisioning the TTR Service Selector.
- Provision the required Common Screening List (CSL) entries. See Provisioning the Common Screening List for IAR Base.
- Provision TATROPTS options for IAR-related features, and for Service Portability if it will be used with IAR NP. See Provisioning the TATR Options.
- Turn on the Service Portability feature if it will be used with the IAR NP feature. See Turning On the Service Portability Feature.
- Turn on the S-Port Subscriber Differentiation feature if it will be used with the Service Portability feature. See Turning On the S-Port Subscriber Differentiation Feature.
- Provision the SCCPOPTS SUBDFRN option if S-Port Subscriber Differentiation will be used with Service Portability for IAR NP. See Provisioning the S-Port Subscriber Differentiation SCCPOPTS Option.
- Provision IAR test messages for use with the Test Tool. See TATR Test Tool.
- With the IAR Base feature enabled but not turned on, turn on any other enabled IAR-related features. See Turning On IAR-Related Features.
- Use the Test Tool to verify the IAR provisioning. See TATR Test Tool.
- Turn on the IAR Base feature. See Turning On IAR-Related Features.
-
If IAR features will process MTP-routed AnalyzedInformation messages, provision one of the following methods to forward MTP-routed messages to Service Module cards:
-
Use the MTP Routed Messages for SCCP Applications feature to forward all SCCP MTP-routed messages to the Service Module cards.
Provision destination point codes (DPCs) with the Home SCP indicator for any Home SCPs that receive outgoing messages. See Destination-based Configuration Options for IAR Pre-NPP Processing and refer to the procedures in Database Administration - SS7 User's Guide to provision DPCs that include the homescp=yes parameter.
Enable and turn on the MTP Routed Messages for SCCP Applications feature. See Enabling the MTP Routed Messages for SCCP Applications Feature and Turning On the MTP Routed Messages for SCCP Applications Feature.
-
Use the Gateway Screening feature SCCP Stop Action to forward only UDT, UDTS, XDT, and XDTS SCCP MTP-routed messages to the Service Module cards.
Verify that the feature prerequisites for Gateway Screening are provisioned as described in IAR-Related Feature Prerequisites.
-
-
Configure measurements collection and reporting if measurements are to be collected for IAR-related features.
Refer to the procedures in Database Administration - System Management User's Guide for configuring OAM-based measurements, the Measurements Platform feature, the E5-OAM Integrated Measurements feature, and the EAGLE OA&M IP Security feature in the EAGLE.
Enabling IAR-Related Features
This procedure is used to enable IAR-related features in the EAGLE.
- Info Analyzed Relay Base (IAR Base) - Part Number 893034201
- Info Analyzed Relay Number Portability (IAR NP) - Part Number 893026101
- Info Analyzed Relay Additional Subscriber Data (IAR ASD) - Part Number 893035101
- Info Analyzed Relay Generic Routing Number (IAR GRN) - Part Number 893034301
Note:
Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.The IAR Base feature must be enabled before any other IAR-related features can be enabled.
When the IAR-related features are enabled, they are permanently enabled. IAR-related features cannot be temporarily enabled.
Provisioning of TATROPTS options, NPP rules containing the CCNCCHK, CDIAL, and CGPNSVCRQD Service Actions, service selectors, and Common Screening Lists can be done after the IAR Base feature is enabled and before the feature is turned on.
Provisioning of NPP rules containing the CDPNNP and CGPNNP Service Actions can be done after the IAR NP feature is enabled and before the feature is turned on.
Provisioning of NPP rules containing the ASDLKUP and CGPNASDRQD Service Actions can be done after the IAR ASD feature is enabled and before the feature is turned on.
Provisioning of NPP rules containing the GRNLKUP and CGPNGRNRQD Service Actions can be done after the IAR GRN feature is enabled and before the feature is turned on.
After an IAR-related feature has been enabled and database provisioning is complete, the feature status must be set to on before the feature will process MSUs (the feature must be “turned on”). See Turning On IAR-Related Features.
Provisioning the TTR Service Selector
The procedures in this section describe how to add, change, and remove a service selector. The information is indicated that is specific to IAR-related features.
Refer to Commands User's Guide for complete descriptions of the commands used in these procedures, including parameter names, valid values, and output examples for the commands.
Provisioning the Common Screening List for IAR Base
- GT screening list - This list is used in CdPA Screening, to compare the SCCP CdPA from the incoming message to the digit strings for Home SCP GTs in this list. If an exact match is not found, the message is dismissed. (The message GTI value must not be zero and cannot be a value other than 2 or 4.)
- CCNC screening list - This screening list is used to compare the conditioned TCAP DN in international format to the Country Code and National Destination Code digit strings in this list. If not found, NPP processing stops and the message is dismissed.
- TRIG screening list - This screening list is used to compare the TRIGTYPE from the incoming message to the entries in this list. Processing of the message is continued only if an exact match is found.
Provisioning the TATR Options
- The IAR Base feature must be enabled before TATROPTS options can be provisioned for any IAR-related feature.
- The Service Portability feature must be enabled before the TATROPTS option for Service Portability can be provisioned.
Provisioning NPP for IAR-Related features
Refer to Numbering Plan Processor (NPP) User's Guide and Commands User's Guide, and see the IAR feature description in this manual for the required information and procedures to provision NPP components for IAR services.
NPP provisioning is performed in the following sequence for the components that are used for the specified IAR service.
- Provision the FNAI mnemonic values required for filter matches on the NAI values for the service, using the
chg-npp-serv
command. - Provision the NPP Action Sets with the Conditioning Actions, Service Actions, Formatting Actions, and outgoing NAI value that are to be used by IAR-related features, using the
ent-npp-as
.command. - Provision the Service Rule Sets (Rules that specify the filter values and Action Sets) that are to be used by IAR-related features. Enter the
ent-npp-srs
command. - Provision any delimiter values that are used in the outgoing digit string formatting. Enter the
chg-npp-serv
command. - Change the service Status to On to allow NPP processing for the specified service. Enter the
chg-npp-serv:srvn=<service name>:status=on
command.
Turning On IAR-Related Features
Before an IAR-related feature can be turned on, the feature must be enabled in the EAGLE.
Provisioning of TATROPTS options and other information can be done after the feature is enabled and before the feature is turned on.
After a feature has been enabled and database provisioning is complete, the feature status must be set to on (the feature must be “turned on”). messages will not be processed by the feature until the feature is turned on.
- Info Analyzed Relay Base (IAR Base) - Part Number 893034201
- Info Analyzed Relay Number Portability (IAR NP) - Part Number 893026101
- Info Analyzed Relay Additional Subscriber Data (IAR ASD)- Part Number 893035001
- Info Analyzed Relay Generic Routing Number (IAR GRN) - Part Number 893035101
After the IAR Base feature and IAR NP feature are enabled and turned on, they cannot be turned off again. The IAR ASD and IAR GRN features can be turned on and off after they are enabled.
Enabling the MTP Routed Messages for SCCP Applications Feature
This procedure is used to enable the MTP Routed Messages for SCCP Applications feature (MTP Msgs for SCCP Apps) feature in the EAGLE.
The MTP Msgs for SCCP Apps feature must be enabled using feature part number 893017401 and a feature access key.
The GTT feature must be turned on before the MTP Msgs for SCCP Apps feature can be enabled.
A feature that uses the MTP Msgs for SCCP Apps feature to select MTP-routed messages must be enabled before the MTP Msgs for SCCP Apps feature can be enabled.
Note:
Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.When the feature is enabled, it is permanently enabled. The MTP Msgs for SCCP Apps feature cannot be temporarily enabled.
After the MTP Msgs for SCCP Apps feature has been enabled, the feature must be turned on before MTP Msgs for SCCP Apps processing will occur. The feature can be turned off after it has been enabled and turned on.
Turning On the MTP Routed Messages for SCCP Applications Feature
Before the MTP Routed Messages for SCCP Applications (MTP Msgs for SCCP Apps) feature can be turned on, the feature must be enabled and off in the EAGLE.
This procedure is used to turn on the MTP Routed Msgs for SCCP Apps feature in the EAGLE, using the feature part number 893017401.
MSUs are processed by the feature only when the feature is turned on in the system.Turning Off the MTP Routed Msgs for SCCP Apps Feature
Before the MTP Routed Msgs for SCCP Apps feature can be turned off, the feature must be enabled and turned on in the EAGLE.
This procedure is used to turn off the MTP Routed Msgs for SCCP Apps feature in the EAGLE, using the feature part number 893017401.
Note:
MSUs are processed by a feature when the feature is turned on in the system.TATR Test Tool
The TATR Test Tool can be used to send provisioned test messages through parts of the IAR Base feature to test an IAR-related feature configuration before the configuration is used to process real message traffic
The TATR Test Tool can be used when the IAR Base feature is enabled and off. The tst-msg
command operates as though the IAR Base feature is on.
The other IAR-related features can be turned on and off when the IAR Base feature is off. An IAR Base configuration cannot be tested without testing the way in which it uses NPP. The ON/OFF status of the IAR NP, IAR ASD, and IAR GRN features influences the processing performed by several NPP Service Action Handlers; these handlers will do nothing when the feature that controls them is OFF.
- TTR service selection is skipped.
- IAR pre-NPP processing
- TCAP decoding is replaced by test message data retrieval.
- The IAR Base feature supports the
tst-msg
command in such a way that the same IAR pre-NPP processing and NPP processing code that is used for run-time message traffic is also exercised by the test message data. - If the
tst-msg
command is used with data that emulates a MTP-routed GTI=0 message, then the message will pass IAR pre-NPP processing DPC Screening only when there is at least one DPC with Home SCP defined in the EAGLE Destination table.
- IAR post-NPP processing message encoding and routing is replaced by TST-MSG output generation.
The following information can be configured for each TATR test message (default values are underlined.):
Table 4-3 TATR Test Message Table Fields
Field | Description |
---|---|
MSGN | {1..10}
Specifies the number of the test message to be sent for feature service processing; this number identifies the message modified by all of the other parameters. |
CDPAGT | {0, 1, 2, 3 .. 15}
Specifies the CdPA GTI for the message. |
CDPAGTNAI | {0, 1, 2, 3, 4, 5 .. 127}
Specifies the CdPA NAI for the message. |
CDPADGTS | {<s>}, where <s> is a string of between 0 and 15 hexadecimal digits in length, with a default value of 0123456789ABCDE.
Specifies the CdPA GT digits for the message. |
CGPAGT | {0, 1, 2, 3, .., 15}
Specifies the CgPA GTI for the message. |
CGPAGTNAI | {0, 1, 2, 3, 4, 5, .., 127}
Specifies the CgPA NAI for the message. |
CGPADGTS | {<s>}, where <s> is a string of between 0 and 15 hexadecimal digits in length, with a default value of 0123456789ABCDE.
Specifies the CgPA GT digits for the message. |
CDPNNAI | {0,1,2,3,.., 255}
Specifies the CgPN NAI for the message. |
CDPNDGTS | {<s>}, where <s> is a string of between 0 and 32 hexadecimal digits in length, with a default value of 0123456789ABCDE.
Specifies the CdPN GT digits for the message. |
CGPNNAI | {0,1,2,3,.., 255}
Specifies the CgPN NAI for the message. |
CGPNDGTS | {<s>}, where <s> is a string of between 0 and 32 hexadecimal digits in length, with a default value of 0123456789ABCDE.
Specifies the CgPN GT digits for the message. |
ACTIVE | {YES, NO}
Specifies whether the message can be sent to the network card for processing. |
RESET | {YES}
Resets all of the message parameters to their default values. |
TRIGTYPE | {0..36, 37, 38..255}
Specifies the TRIGTYPE for the message as a hexadecimal number. The TRIGTYPE may also be entered as a hexadecimal number; range 00..FF, with a default value of 25. Refer to the "Notes" section of the |
The chg-tatr-msg
command is used to configure the parameter values for each TATR test message. The command must specify the message number (one of up to 10 messages) for the message that is being configured.
The rtrv-tatr-msg
command displays the configured messages in the Test Message table. Configured information for all messages or for one specified message number can be displayed.
The tst-msg
command invokes the test. The command must specify the prot=tatr parameter, the message number for the test, the network card location (loc parameter), the feat=iar parameter, and the mode for displaying the results (full, brief, debug). The most complete and accurate test result information is provided when debug mode is used.
Note:
The specified test message must be set toactive=yes
before the test is invoked for the message.
Refer to the Commands User's Guide for descriptions of the commands, parameter values, and output examples.
Service Portability Feature Configuration Procedures
The procedures in this section are used for configuration of the Service Portability (S-Port) feature.
Enabling the Service Portability Feature
If Service Portability can be applied to the messages processed by a feature described in this guide, use this procedure to enable the Service Portability feature in the EAGLE.
Note:
Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.Provisioning of S-Port options can be done after the feature is enabled and before the feature is turned on.
After the S-Port feature has been enabled and database provisioning is complete, the S-Port feature status must be set to on (the feature must be “turned on”) before S-Port processing will occur.
Turning On the Service Portability Feature
This procedure is used to turn on the Service Portability feature in the EAGLE, using the feature part number 893034301.
Before the Service Portability (S-Port) feature can be turned on, the feature must be enabled in the EAGLE.
Provisioning of S-Port options can be done after the feature is enabled and before the feature is turned on.
After the S-Port feature has been enabled and database provisioning is complete, the Service Portability feature status must be set to on (the feature must be “turned on”). MSUs will not be processed by the Service Portability feature until the feature is turned on.
After the Service Portability feature is enabled and turned on, it can be turned off again. Service Portability processing can occur only when the Service Portability feature is on and a feature that uses S-Port is on.
Turning Off the Service Portability Feature
Before the Service Portability (S-Port) feature can be turned on and off, the feature must be enabled in the EAGLE.
This procedure is used to turn off the Service Portability feature, using its feature part number 8930343001.
Note:
MSUs will not be processed by a feature when the feature is turned off in the system.S-Port Subscriber Differentiation Feature Configuration Procedures
The procedures in this section are used for configuration of the S-Port Subscriber Differentiation feature.
Enabling the S-Port Subscriber Differentiation Feature
If S-Port Subscriber Differentiation will be used with Service Portability for the messages processed by a feature described in this manual, use this procedure to enable the S-Port Subscriber Differentiation feature in the EAGLE.
Note:
Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.After the S-Port Subscriber Differentiation feature has been enabled, the S-Port Subscriber Differentiation feature status must be set to on. See Turning On the S-Port Subscriber Differentiation Feature. The S-Port Subscriber Differentiation feature cannot be turned off after the feature is turned on.
Provisioning of the S-Port Subscriber Differentiation SCCPOPTS configuration option can be done only after the feature is enabled and turned on. See Provisioning the S-Port Subscriber Differentiation SCCPOPTS Option.
Before S-Port Subscriber Differentiation processing of MSUs can occur, the Service Portability feature, the S-Port Subscriber Differentiation feature, the S-Port Subscriber Differentiation option, and a feature that uses Service Portability must be on.
Turning On the S-Port Subscriber Differentiation Feature
This procedure is used to turn on the S-Port Subscriber Differentiation feature in the EAGLE, using the feature part number 893037901.
Before the S-Port Subscriber Differentiation feature can be turned on, the feature must be enabled in the EAGLE.
After the S-Port Subscriber Differentiation feature has been enabled, the S-Port Subscriber Differentiation feature status must be set to on (the feature must be “turned on”). After the S-Port Subscriber Differentiation feature is enabled and turned on, it cannot be turned off again.
Provisioning of the S-Port Subscriber Differentiation option can be done only after the feature is enabled and turned on. The S-Port Differentiation option can be turned on and off.
MSUs will not be processed by the S-Port Subscriber Differentiation feature until the feature and the option are turned on. S-Port Subscriber Differentiation processing can occur only when the Service Portability feature, the S-Port Subscriber Differentiation feature, the S-Port Differentiation option, and a feature that uses Service Portability are all on.
Provisioning the S-Port Subscriber Differentiation SCCPOPTS Option
This procedure is used to provision the SCCPOPTS configuration option for the S-Port Subscriber Differentiation feature.
The S-Port Subscriber Differentiation feature must be enabled and turned on before SCCPOPTS SUBDFRN option can be provisioned.
ANSI41 AIQ Configuration
The ANSI41 AIQ feature is configured on the EAGLE. This section describes prerequisites and procedures for the configuration of the ANSI41 AIQ feature.
ANSI41 AIQ Configuration Procedure lists the steps for enabling and turning on the ANSI41 AIQ feature, and for the provisioning required for the feature. Each step contains a link or reference to information and procedures to use to complete the step. Feature provisioning can be performed after the feature is enabled and before the feature is turned on.
Note:
Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.ANSI41 AIQ Feature Prerequisites
Before the ANSI41 AIQ feature can be enabled, the following prerequisite is required in the system:
Table 4-4 ANSI41 AIQ Feature Prerequisite
Prerequisite | Verification and Provisioning |
---|---|
The LNP feature cannot be on in the system. |
Enter the If the LNP feature is on, shown with a quantity greater than zero for the LNP ported TNs entry in the command output, the ANSI41 AIQ feature cannot be enabled. |
ANSI41 AIQ Configuration Procedure
-
Verify, and provision if needed, the system prerequisites. See System Prerequisites.
-
Verify, and provision if needed, the feature prerequisites. See ANSI41 AIQ Feature Prerequisites.
-
Enable the ANSI41 AIQ feature. See Enabling the ANSI41 AIQ Feature.
- Refer to the procedures in the Database Administration - SS7 User's Guide to change the self identification of the EAGLE node to include true point codes and ANSI41 AIQ capability point codes.
-
Refer to the procedures in the Database Administration - GTT User's Guide to provision the following items:
- Translation types and mappings
- Mated Application (MAP) table entries for the ANSI41 AIQ feature that contain the EAGLE true point codes, the ANSI41 AIQ capability point codes, and the ANSI41 AIQ subsystem number. Only solitary and dominant loadsharing are supported.
The AIQ local subsystem can have a mate subsystem and a concerned point code group assigned to it in the MAP table.
If multiple point code types for ANSI41 AIQ are provisioned in the MAP table, then the point code type for the Subsystem Out-of-Service Request message (SOR) is determined using the following order:- ANSI
- ITU-N
- ITU-N Spare
- ITU-I
- ITU-I Spare
-
Provision the state and subsystem number for the AIQ local subsystem application. See Provisioning the AIQ Local Subsystem.
-
Provision the service selector for the ANSI41 AIQ feature (aiq). See Provisioning the AIQ Service Selector.
-
Provision ANSI41 AIQ (AIQOPTS) options. See Provisioning the ANSI41 AIQ Options.
- Minimum and maximum length for Digits (Dialed), Trigger Type Prefix or Prefix and Incoming Digits (Dialed) response format, and RoutingDigits or Digits (Dialed) Return Result parameter.
- Trigger Type and Prefix pairs
- TCAP Error Code
-
Turn on the ANSI41 AIQ feature. See Turning On the ANSI41 AIQ Feature.
-
Activate the AIQ local subsystem. See Activating the AIQ Local Subsystem.
Enabling the ANSI41 AIQ Feature
-
The ANSI41 AIQ feature must be enabled using the ANSI41 AIQ feature part number 893034901 and a feature access key.
Note:
Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.When the ANSI41 AIQ feature is enabled, it is permanently enabled. The ANSI41 AIQ feature cannot be temporarily enabled.
Provisioning of ANSI41 AIQ options and other information can be done after the feature is enabled and before the feature is turned on. -
After the ANSI41 AIQ feature has been enabled and database provisioning is complete, the ANSI41 AIQ feature status must be set to on (the feature must be “turned on”) to begin operation in the system. See Turning On the ANSI41 AIQ Feature.
After the ANSI41 AIQ feature is enabled and turned on, the ANSI41 AIQ feature can be turned off again.
Provisioning the AIQ Local Subsystem
See the procedures in Changing the State of a Subsystem Application to take the subsystem application online or offline.
Adding the AIQ Local Subsystem Application
This procedure is used to define the AIQ subsystem application. The subsystem application can be taken online when it is defined or later in the configuration process (see Changing the State of a Subsystem Application).
Before the AIQ subsystem application can be added to the database, the following conditions must exist in the system:
Table 4-5 AIQ Local Subsystem Prerequisites
Prerequisite | Verification |
---|---|
The ANSI41 AIQ feature must be enabled and turned on |
Enter the If the ANSI41 AIQ entry with Status of on does not appear in the output, see the Enabling the ANSI41 AIQ Feature and Turning On the ANSI41 AIQ Feature procedures. |
The application specified by the appl parameter (aiq) cannot already be in the database. |
Enter the If the AIQ entry appears in the output, this procedure cannot be performed. |
EAGLE true point codes and AIQ capability point codes must be defined, and entered in the Mated Application table with a subsystem number to be used for the AIQ subsystem application. |
Only one subsystem number for the application can be defined, and must be used for all point code types assigned to the local subsystem. Enter the Enter the |
The examples in this procedure reserve the subsystem number 100 for the AIQ subsystem application and set the AIQ subsystem application status to online.
Provisioning the AIQ Service Selector
The procedures in this section describe how to add, change, and remove a service selector. The information is indicated that is specific to ANSI41 AIQ.
Refer to Commands User's Guide for complete descriptions of the commands used in these procedures, including parameter names, valid values, and output examples for the commands.
Adding an AIQ Service Selector
This procedure is used to add a service selector for the ANSI41 AIQ feature.
The ANSI41 AIQ feature must be enabled before an AIQ service selector can be added.
Changing an Existing Service Selector to an ANSI41 AIQ Service Selector
This procedure is used to change an existing non-AIQ service selector to an AIQ service selector.
The only parameters that can be changed using this procedure are:
The chg-srvsel
command requires that the gtii/gtin, tt, ssn, and serv parameters be specified with the values shown in the rtrv-srvsel
output for the service selector that is being changed. If any of these parameter values need to be changed for an AIQ service selector, use the procedure in Removing a Service Selector to remove the existing service selector. Then use the procedure in Adding an AIQ Service Selector to add the new AIQ service selector with the new parameter information.
Provisioning the ANSI41 AIQ Options
Refer to EAGLE Commands in this manual and to the chg-aiqopts
command description in Commands User's Guide for valid parameter values, input examples, and rules for entering the command correctly.
Turning On the ANSI41 AIQ Feature
After the ANSI41 AIQ feature has been enabled and database provisioning is complete, the ANSI41 AIQ feature status must be set to on (the feature must be “turned on”).
This procedure is used to turn on the ANSI41 AIQ feature in the EAGLE.
Changing the State of a Subsystem Application
The procedures in this section are used to set the state of an existing subsystem application to either online or offline.
The online or offline status of the subsystem application is shown in the STAT field of the rtrv-ss-appl
command output.
The rept-stat-sccp
command displays the operating state (in or out of service) of the subsystem.
If the subsystem application is to be taken online, the subsystem application must be offline.
When the subsystem is taken online (regardless of how the subsystem was taken offline), the EAGLE sends SNR/SSA. A UAM is generated, indicating that the subsystem is ALLOWED.
If the subsystem application is to be taken offline, the subsystem application must be online. The subsystem must be taken out of service (OOS-MT-DSBLD) with the inh-map-ss
command before it can be taken offline.
A subsystem application can be taken offline using coordinated state change, or forced offline without using coordinated state change.
When the inh-map-ss
command is entered for the subsystem, a coordinated shutdown is attempted. If the coordinated shutdown fails, a UIM is generated, indicating that the shutdown failed. If the force parameter is specified, the subsystem is forced to shut down; a coordinated shutdown is not performed.
For coordinated state change, SCMG sends an SOR message to the mated subsystem and will start a Tcoord timer (30 seconds). If SCMG receives an SOG message from the mated subsystem before the Tcoord timer expires, SCMG will broadcast SSPs to the concerned point code group, send SBR/SSP, and take the subsystem offline. A UAM is generated, indicating that the subsystem is PROHIBITED. If the SOG is not received before Tcoord expires, then the inhibit request is denied and a UIM is generated.
When the subsystem is taken offline without coordinated state change, the EAGLE sends SBR/SSPs. A UAM is generated, indicating that the subsystem is PROHIBITED.
- The local subsystem is available
- The total load on the DSM subsystem is less than 45% of its capacity
If either of these conditions is not met, the EAGLE will not reply to the SOR message.
Activating the AIQ Local Subsystem
The procedure in this section explains how to activate the AIQ local subsystem.
When all feature configuration is complete, the AIQ subsystem application must taken online and the local subsystem must be activated to allow it to begin operation.
When the local subsystem operating state is Inhibited, the chg-ss-appl
command can be used to change the online or offline database state of the subsystem. The rtrv-ss-appl
command displays the online or offline provisioned value.
When the first Service Module card is loaded, this state tells whether the subsystem should be considered allowed (online) or inhibited (offline). This is a database state. If the command is accepted, then the change is made to the tables and can be read after an init-sys
command is entered to initialize the system.
When the Service Module cards are in-service and the subsystem application is online, the alw/inh-map-ss
commands can be used to change the dynamic operating state of the local subsystem to allowed or inhibited. The inh-map-ss
command does not necessarily force a state change, because it can fail if the mate does not send an SOG. The force=yes parameter must be specified to bypass the SOR/SOG exchange and inhibit immediately. (There is no rtrv-map-ss
command.)
The procedures in Changing the State of a Subsystem Application explain how to take a local subsystem online and offline.
Table 4-6 Subsystem Allow/Inhibit
Command\ Subsystem State | Offline | Online |
---|---|---|
alw-map-ss
|
Command is rejected because the subsystem must be online to be in the Allowed state. | Attempts to make the local subsystem active. |
inh-map-ss
|
Command accepted, but no action because offline implies inhibited. | Attempts to inhibit the local subsystem. Use of the force=yes parameter bypasses the SOR/SOG exchange and inhibits immediately. |
chg-ss-appl:appl=aiq:nstat=online
|
Changes local subsystem status to online. | No change to local subsystem status in the database. |
chg-ss-appl:appl=aiq:nstat=offline
|
Command is rejected because the subsystem must be inhibited to go offline. | Changes local subsystem database status to offline. |