1. EAGLE ATINP User's Guide
  2. ATINP Configuration

4 ATINP Configuration

This chapter provides procedures for configuring the ATINP feature for use in the EAGLE.

Introduction

The ATINP feature is configured on the EAGLE and on the EPAP. This chapter describes prerequisites and procedures for the EAGLE configuration only. The EPAP configuration is covered in the Administration Guide for EPAP. This chapter also includes procedures for configuration of the Service Portability feature for use with ATINP, and for provisioning options to allow the use of the GRN for ROP information.

ATINP Configuration Procedure lists the steps for enabling and turning on the ATINP feature and the Service Portability 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. Refer to Commands User's Guide for complete descriptions of the commands used in these procedures.

The ATINP feature and other related 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.

Note:

For an in-service environment, contact unresolvable-reference.html#GUID-F6B3D647-C34D-4046-83F4-3D37AC9F2F63 before continuing to configure the ATINP feature. For an environment that is not yet in-service, continue with the configuration.

EPAP Entity Provisioning

Oracle recommends that EPAP entity (SP or RN) administration not be performed until after the Point Code and/or Subsystem Number has been entered into the EAGLE MAP table.
  • EPAP-administered entity data can become out-of-sync with the EAGLE MAP table when the creation of Point Codes and/or Subsystem Numbers in the MAP table is performed after EPAP database administration.
  • If this mismatch is discovered in real-time operations, a UIM is sent to the EAGLE maintenance terminal. (Example UIMs: SCCP did not route - DPC not in MAP tbl, SCCP did not route - SS not in MAP tbl.)

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 rtrv-serial-num command to display the serial number and its locked status.

Verify that the displayed serial number is correct for the system.

If no serial number is displayed, enter the ent-serial-num command (without the lock parameter) to provision the serial number that appears on the control shelf label. Enter the rtrv-serial-num command and verify that the serial number was entered correctly.

Enter the ent-serial-num command with the lock=yes parameter to lock the serial number in the system.

A sufficient number of Service Module cards must be equipped.

Enter the rept-stat-card:appl=vsccp command to list the Service Module cards in the system.

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 rtrv-feat command to display the GTT feature status.

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.

ATINP Feature Prerequisites

Before the ATINP feature can be enabled, the following prerequisites are required in the system:

Table 4-2 ATINP Feature Prerequisite

Prerequisite Verification and Provisioning
The ANSIGFLEX system option cannot be set to Yes.

Enter the rtrv-stpopts command.

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 rtrv-ctrl-feat command.

If the LNP feature is on, shown with a quantity greater than zero for the LNP ported TNs entry in the command output, the feature described in this manual cannot be enabled.

ATINP Configuration Procedure

The EAGLE configuration of the ATINP feature consists of the following steps. The steps contain links and references to detailed procedures and information needed to complete each step.

  1. Verify, and provision if needed, the system prerequisites. See System Prerequisites.
  2. Verify, and provision if needed, the feature prerequisites. See ATINP Feature Prerequisites.
  3. Enable the ATINP feature, set system STP options, and turn on the ATINP feature. See Enabling ATINP, Setting STP Options, and Turning On ATINP.
  4. Enable the Service Portability feature, if it will be used with ATINP. See Enabling the Service Portability Feature.
  5. Change the self identification of the EAGLE node to include true point codes and ATINP capability point codes. See Provisioning True Point Codes and Capability Point Codes and refer to the procedures in Database Administration - SS7 User's Guide.
  6. Refer to the procedures in Database Administration - GTT User's Guide to provision the following items:
    • Translation types and mappings
    • Mated Application table entries for the ATINP feature that contain the EAGLE true point codes, the ATINP capability point codes, and the ATINPQ subsystem number. Only solitary and dominant loadsharing are supported.

    The ATINPQ 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 ATINPQ 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:
    1. ANSI
    2. ITU-N
    3. ITU-N Spare
    4. ITU-I
    5. ITU-I Spare
  7. Provision state and subsystem number for the ATINPQ local subsystem application. See Adding the ATINPQ Local Subsystem Application.
  8. Provision the service selector mechanism to route MSUs to the ATINPQ subsystem. See Adding an ATINP Service Selector.

    The ATINP service is atinp.

    The Translation Type and Subsystem Number are the values assigned for the ATINP local subsystem when the MAP table entries were defined. See Step 4 in this procedure.

    ATINP supports ANSI, ITU-I, and ITU-N Global Title Indicators; ITU-N24 is not supported.

    The Nature of Address Indicator and Numbering Plan are required when the GTI value is 4, and not allowed when the GTI value is 2.

    ATINP does not support the Service Nature of Address or the Service Numbering Plan.

  9. Provision ATINP options, including options for Service Portability and GRN data processing if required. See Provisioning the ATINP Options.
  10. Activate the ATINP local subsystem. See Activating the ATINPQ Local Subsystem.
  11. Turn on the Service Portability feature, if it will be used with ATINP. See Turning On the Service Portability Feature.
  12. Configure the Measurements Platform feature or the E5-OAM Integrated Measurements feature if measurements are to be collected for ATINPQ.

    Refer to the procedures in Database Administration - System Management User's Guide for configuring the Measurements Platform feature, the E5-OAM Integrated Measurements feature, and the EAGLE OA&M IP Security feature in the EAGLE. OAM-based measurements reports are not available for ATINPQ.

Enabling ATINP, Setting STP Options, and Turning On ATINP

This procedure is used to enable the ATINP feature, set the system STP options, and turn on the ATINP feature in the EAGLE.

  • The ATINP feature must be enabled using the ATINP feature part number 893022101 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 ATINP feature is enabled, it is permanently enabled. The ATINP feature cannot be temporarily enabled.

    Note:

    Provisioning of ATINP options and other information can be done after the feature is enabled and before the feature is turned on.

  • After the ATINP feature has been enabled, the STP option for the default country code must be changed from NONE to an appropriate value for ATINP.

    The chg-stpopts and rtrv-stpopts commands support the defcc and dsmaud parameters for the ATINP feature.

    In the rtrv-stpopts command output, the defcc parameter is displayed with value NONE when the ATINP feature is enabled.

  • After the ATINP feature has been enabled, the STP options are set, and database provisioning is complete, the ATINP feature status must be set to on (the feature must be “turned on”).

    After the ATINP feature is enabled and turned on, the ATINP feature can be turned off again.

    When the feature is turned on:
    • The defcc parameter value cannot be set to NONE.
    • The DSM audit running state (dsmaud) parameter of the chg-stpopts command can be provisioned for ATINP.
    • The dsmaud parameter is displayed with value off when the ATINP feature is turned on.
  1. Enable the ATINP feature, by entering the enable-ctrl-feat command.
    enable-ctrl-feat:partnum=893022101:fak=<feature access key>

    Note:

    The Feature Access Key (FAK) is provided by Oracle. If you do not have the controlled feature part number or the Feature Access Key for the feature, contact your Oracle Sales Representative or Account Representative.

    When the feature is enabled, the ATINP entry appears in the output of the rtrv-ctrl-feat command. 

        rlghncxa03w 08-08-29 16:40:40 EST  EAGLE5 39.2.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    ATINP                     893022101  off         ----
;
  2. Verify that the defcc STP option parameter value is not NONE. Enter the rtrv-stpopts command.
    • If the value is not NONE, continue with 3.
    • If the defcc parameter value is NONE, use the chg-stpopts command to provision a new value. Then continue with 3.

    Note:

    Database provisioning of ATINP options can be done here, before the ATINP feature is turned on in the system.
  3. Turn on the ATINP feature. Enter the chg-ctrl-feat command.
    chg-ctrl-feat:partnum=893022101:status=on

    When the feature is turned on, the status changes to on in the rtrv-ctrl-feat command output. 

        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    ATINP                     893022101  on          ----
;
  4. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    The following messages appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first.

    BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

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.

The Service Portability feature must be enabled using the feature part number 893034301 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 S-Port feature is enabled, it is permanently enabled. The S-Port feature cannot be temporarily enabled. After the S-Port feature is enabled and turned on, the S-Port feature can be turned off again.

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.

  1. Display the status of the controlled features that are controlled with Feature Access Keys (FAKs). Enter the rtrv-ctrl-feat command. The output lists the enabled features in the system and shows the on/off status for each feature. 
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
;

    If the Service Portability entry appears in the rtrv-ctrl-feat output, performing this procedure is not necessary.

  2. Enable the S-Port feature, by entering the enable-ctrl-feat command.
    enable-ctrl-feat:partnum=893034301:fak=<feature access key>

    When the feature is enabled, the Service Portability entry appears in the output of the rtrv-ctrl-feat command. 

        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    Service Portability       893034301  off         ----
 ;
  3. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    The following messages appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first. 

    BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Provisioning True Point Codes and Capability Point Codes

This procedure explains briefly how to provision EAGLE true point codes, and capability point codes for EPAP-based features. Refer to the detailed procedures in Database Administration - SS7 User's Guide for provisioning true and capability point codes, and the CLLI if needed.

For the ATINPQ subsystem, the EAGLE supports ANSI, ITU-I, ITU-N, ITU-I Spare, and ITU-N Spare capability point code types. including group codes. ITU-N24 capability point codes are not supported.

This procedure explains how to provision EAGLE true point codes and ATINP capability point codes.

  1. Display the true and capability point codes in the system. Enter the rtrv-sid command. 
        tekelecstp 08-07-22 15:07:48 EST  EAGLE 39.2.0

       PCA             PCI          PCN                CLLI              PCTYPE
       -----------     -------      -----              tekelecstp        ANSI
;
  2. Verify that the desired EPAP-based feature is enabled and turned on, by entering the rtrv-ctrl-feat command. 
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012701  on            64
    ATINP                     893022101  on          ----
;
    • If the feature entry appears in the command output, and the feature status is on, continue with 3.
    • If the feature entry does not appear in the command output or if the feature status in the entry is off, go to the procedure in this manual to enable and turn on the EPAP-based feature. Continue with 3.
  3. Change the true point codes and capability point codes as needed, using the chg-sid command.
    Refer to the procedures in Database Administration - SS7 User's Guide for changing the Self-Identification of the EAGLE. The system might need to be initialized for the point code changes to take effect. This must be done carefully to minimize traffic loss.
  4. Verify the changes with the rtrv-sid command. 
        tekelecstp 08-08-22 15:07:48 EST  EAGLE 39.2.0

       PCA             PCI          PCN                CLLI              PCTYPE
       001-001-001     2-002-2      01234              tekelecstp        ANSI

       CPCA (ATINP)
       004-004-004

       CPCI (ATINP)
       5-012-0

       CPCN (ATINP)
       12345

;
  5. Back up the changes using the chg-db:action=backup:dest=fixed command.

    The following messages appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first.

    BACKUP (FIXED): MASP A - Backup starts on active MASP.
BACKUP (FIXED): MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED): MASP A - Backup starts on standby MASP.
BACKUP (FIXED): MASP A - Backup on standby MASP to fixed disk complete.

Provisioning the ATINPQ Local Subsystem

The following procedures in this section are used to add or remove a local subsystem application:

See the procedures in Changing the State of a Subsystem Application to take the subsystem application online or offline.

Note:

The EAGLE supports the operation of two or more local subsystems for EPAP-related features in the system at one time. For example, the local subsystems for INP and EIR can coexist in the system.

Adding the ATINPQ Local Subsystem Application

This procedure is used to define the ATINPQ 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 ATINPQ subsystem application can be added to the database, the following conditions must exist in the system:

Table 4-3 ATINPQ Local Subsystem Prerequisites

Prerequisite Verification
The ATINP feature must be enabled and turned on

Enter the rtrv-ctrl-feat command.

If the ATINP entry with Status of on does not appear in the output, see the Enabling ATINP, Setting STP Options, and Turning On ATINP procedure.

The application specified by the appl parameter (atinpq) cannot already be in the database.

Enter the rtrv-ss-appl command.

If the ATINPQ entry appears in the output, this procedure cannot be performed.
EAGLE true point codes and ATINP capability point codes must be defined, and entered in the Mated Application table with a subsystem number to be used for the ATINPQ 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 rtrv-sid command, and verify that the true and capability point codes needed for the feature are correct. If changes are required, see Provisioning True Point Codes and Capability Point Codes

Enter the rtrv-map command, and verify that the MAP table entries are correct for the ATINPQ local subsystem. If changes are required, refer to the procedures in Database Administration - GTT User's Guide for provisioning solitary and dominant mated applications.

The examples in this procedure reserve the subsystem number 100 for the ATINPQ subsystem application and set the ATINPQ subsystem application status to online.

  1. Add the ATINPQ application and subsystem number, using the ent-ss-appl command.

    If the stat parameter is not specified, the status defaults to offline.

    ent-ss-appl:appl=atinpq:ssn=100:stat=online
  2. Verify the changes with the rtrv-ss-appl command. 
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT
    ATINPQ 100   online            
 
    SS-APPL TABLE IS 25% FULL (1 OF 4)
;
  3. Back up the changes using the chg-db:action=backup:dest=fixed command. The following messages appear;, the active Maintenance and Administration Subsystem Processor (MASP) appears first.
    BACKUP (FIXED): MASP A - Backup starts on active MASP.
BACKUP (FIXED): MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED): MASP A - Backup starts on standby MASP.
BACKUP (FIXED): MASP A - Backup on standby MASP to fixed disk complete.

Removing a Local Subsystem Application

This procedure is used to remove a subsystem application from the database. The subsystem application to be removed must be in the database and the subsystem must be out of service.

  1. Display the subsystem application number for the local subsystem application in the database, by entering the rtrv-ss-appl command.
  2. Display the operating status of the local subsystem, by entering the rept-stat-sccp command.
    If the subsystem is out of service , shown by an entry containing OOS-MT-DSBLD for the subsystem in the rept-stat-sccp output, go to 5.
  3. Place the local subsystem application out of service. Enter the inh-map-ss command and specify the subsystem number displayed in 1.
    inh-map-ss:ssn=11 
    rlghncxa03w 08-06-28 14:42:38 GMT EAGLE 39.2.0
Inhibit map subsystem command sent to all SCCP cards.
Command Completed.
    When this command has successfully completed, the following message appears. If the force=yes parameter is not specified, wait for a message that indicates the subsystem is inhibited. 
    rlghncxa03w 08-06-28 14:42:38 GMT EAGLE 39.2.0
Inhibit map subsystem command sent to all SCCP cards.
Command Completed.
  4. Verify that the local subsystem is out of service (OOS-MT-DSBLD), by entering the rept-stat-sccp command. If the local subsystem is not out of service, return to 3 and enter the inh-map-ss command with the force=yes parameter specified.
  5. Remove the local subsystem application from the database, by entering the dlt-ss-appl command.
    dlt-ss-appl:appl=<subsystem>
  6. Verify the changes by entering the rtrv-ss-appl command. The deleted entry should not appear in the output.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT

    SS-APPL TABLE IS 0% FULL (0 OF 4)
;
  7. Back up the changes using the chg-db:action=backup:dest=fixed command.
    The following messages appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first.
    BACKUP (FIXED): MASP A - Backup starts on active MASP.
BACKUP (FIXED): MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED): MASP A - Backup starts on standby MASP.
BACKUP (FIXED): MASP A - Backup on standby MASP to fixed disk complete.

Provisioning the ATINP Service Selector

The procedures in this section describe how to add, change, and remove a service selector. The included information is specific to ATINP.

Adding an ATINP Service Selector

This procedure is used to add a service selector for the ATINP feature.

The ATINP feature must be enabled and turned on before an ATINP service selector can be added.

  1. Verify that the ATINP feature is enabled and turned on, by entering the rtrv-ctrl-feat command.

    If the ATINP feature is enabled and turned on, the status of the ATINP entry is on. 

        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    ATINP                     893024401  on          ----
 ;
  2. Display any existing ATINP service selectors in the database, by entering the rtrv-srvsel:serv=atinp command.
        rlghncxa03w 08-06-28 14:42:38 GMT  EAGLE 41.1.0

    GTII  TT   NP       NAI   SSN  SNP   SNAI   SERV

    4     1    e164     intl  3    ---   ---    atinp
    4     2    e164     intl  *    ---   ---    atinp
 

    GTIN  TT   NP       NAI   SSN  SNP   SNAI   SERV

    4     4    e164     natl  4    ---   ---    atinp
 

    SRV SELECTOR table is (3 of 20992) 1 % full 
;
  3. Add new ATINP service selectors, using the ent-srvsel command. For example, enter commands like these:

    ent-srvsel:serv=atinp:tt=35:ssn=100:gtin=4:np=e214:nai=natl

    ent-srvsel:serv=atinp:tt=57:ssn=75:gtin=2

  4. Verify the changes by entering the rtrv-srvsel command with the parameters and values used in 3.
        rlghncxa03w 08-06-28 14:42:38 GMT  EAGLE 41.1.0

    GTII  TT   NP       NAI   SSN  SNP   SNAI   SERV

    4     1    e164     intl  3    ---   ---    atinp
    4     2    e164     intl  *    ---   ---    atinp
 

    GTIN  TT   NP       NAI   SSN  SNP   SNAI   SERV

    4     4    e164     natl  4    ---   ---    atinp
    4     35   e214     natl  100  ---   ---    atinp
    2     57   ---      ---   75   ---   ---    atinp
 

    SRV SELECTOR table is (5 of 20992) 1 % full 
;
  5. Back up the changes using the chg-db:action=backup:dest=fixed command.
    The following messages appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    BACKUP (FIXED): MASP A - Backup starts on active MASP.
BACKUP (FIXED): MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED): MASP A - Backup starts on standby MASP.
BACKUP (FIXED): MASP A - Backup on standby MASP to fixed disk complete.

Removing a Service Selector

This procedure is used to remove a service selector from the database.

The GTI, GTII, GTIN, tt, and ssn parameter values can be used to limit the amount of information displayed with the rtrv-srvsel command.

  1. Display the service selectors in the database, by entering the rtrv-srvsel command.
        rlghncxa03w 08-06-28 14:42:38 GMT  EAGLE 39.2.0
    GTII  TT   NP       NAI   SSN  SNP   SNAI   SERV

    4     1    e214     intl  4    e164  intl   gport

    4     1    e214     intl  5    e164  intl   smsmr

    4     2    e214     intl  5    e164  intl   mnpsms

    4     2    e164     intl       ---   ---    vflex

 

    GTIN  TT   NP       NAI   SSN  SNP   SNAI   SERV

    4     4    e214     natl  75   e164  intl   gflex

    4     9    e214     natl  100  e164  intl   gflex

    4     35   e214     natl  100  ---   ---    atinp

    2     57   e214     natl  75   ---   ---    vflex

 

    SRV SELECTOR table is (8 of 20992)   1 % full

;
  2. Remove the service selector from the database, using the dlt-srvsel command. For example, enter commands like these.

    dlt-srvsel:serv=atinp:tt=35:ssn=100:gtin=4:np=e214:nai=natl

    dlt-srvsel:serv=atinp:tt=57:ssn=75:gtin=2

    To remove a service selector, the GTI, GTII, GTIN, tt, and ssn parameter values must be entered as shown in the rtrv-srvsel command output.

  3. Verify the changes by entering the rtrv-srvsel command with the parameters and values used in 2.

    rtrv-srvsel:serv=atinp:tt=35:ssn=100:gtin=4:np=e214:nai=natl

        rlghncxa03w 08-06-28 14:42:38 GMT  EAGLE 39.2.0

 

    GTIN  TT   NP       NAI   SSN  SNP   SNAI   SERV

    No SRV Selector found in range

;

    rtrv-srvsel:serv=atinp:tt=57:ssn=75:gtin=2

        tekelecstp 08-08-28 16:35:22 EST  EAGLE 39.2.0
    GTII  TT   NP       NAI   NPV  NAIV  SSN  SNP   SNAI   SERV
    No SRV Selector found in range

;
  4. Back up the changes using the chg-db:action=backup:dest=fixed command.
    The following messages appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first.
    BACKUP (FIXED): MASP A - Backup starts on active MASP.
BACKUP (FIXED): MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED): MASP A - Backup starts on standby MASP.
BACKUP (FIXED): MASP A - Backup on standby MASP to fixed disk complete.

Changing an Existing Service Selector to an ATINP Service Selector

This procedure is used to change an existing non-ATINP service selector to a ATINP service selector.

The only parameters that can be changed using this procedure are:

:nserv
New DSM service type, ATINP
:nsnp
An ATINP service selector cannot contain an SNP value; if the service selector being changed contains an SNP value, this value must be changed to none with this parameter.
:nsnai
An ATINP service selector cannot contain an SNAI value; if the service selector being changed contains an SNAI value, this value must be changed to none with this parameter.

The chg-srvsel command requires that the following 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 a ATINP service selector, use the procedure in Removing a Service Selector to remove the existing service selector. Then use the procedure in Adding an ATINP Service Selector to add the new ATINP service selector with the new parameter information.

:gtii/gtin/gtin24
Global title indicator for ITU international (gtii), ITU national using 14-bit point codes (gtin), and ITU national using 24-bit point codes (gtin24).
:tt
Translation type
:ssn
Subsystem number
:nai
Nature of address indicator
:naiv
Nature of address indicator value
:np
Numbering plan
:npv
Numbering plan value
  1. Display the service selectors in the database, using the rtrv-srvsel command. 
        rlghncxa03w 08-06-28 14:42:38 GMT  EAGLE 39.2.0

 

    GTII  TT   NP       NAI   SSN  SNP   SNAI   SERV

    4     1    e214     intl  4    e164  intl   gport

    4     1    e214     intl  5    e164  intl   smsmr

    4     2    e214     intl  5    e164  intl   mnpsms

    4     2    e164     intl  *    ---   ---    vflex

 

    GTIN  TT   NP       NAI   SSN  SNP   SNAI   SERV

    4     4    e214     natl  34   e164  intl   gflex

    4     9    e214     natl  ---  e164  intl   gflex

 

    SRV SELECTOR table is (6 of 20992)   1 % full

;
  2. Verify that the ATINP feature is enabled and turned on, by entering the rtrv-ctrl-feat command. If the ATINP feature is enabled and turned on, the status of the ATINP entry is on. 
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    ATINP                     893024401  on          ----
 
;
  3. Change the service selector, using a chg-srvsel command similar to the following example.
    chg-srvsel:gtin=4:tt=4:np=e214:nai=natl:ssn=34:nsnp=none:nsnai=none:nserv=atinp

    Note:

    If the SNP or SNAI parameter values are shown as dashes in the rtrv-srvsel output, these parameters cannot be specified with the chg-srvsel command. If the gtii/gtin/gtin24 parameter value is 2, the np, nai, npv, and naiv parameters cannot be specified with the chg-srvsel command.

    If the gtii/gtin/gtin24 parameter value is 4, either the np and nai, or the npv and naiv parameters must be specified with the chg-srvselcommand. The np and nai parameters can be specified in place of the npv and naiv parameters, and the npv and naiv parameters can be specified in place of the np and naiv parameters as long as parameter values be specified correspond to the values shown in the rtrv-srvseloutput.

  4. Verify the changes by entering the rtrv-srvsel command with the serv=atinp parameter and the values for the other parameter that were used in 3.

    rtrv-srvsel:gtin=4:tt=4:np=e214:nai=natl:ssn=34:serv=atinp

        rlghncxa03w 08-06-28 14:42:38 GMT  EAGLE 39.2.0

 

    GTIN  TT   NP       NAI   SSN  SNP   SNAI   SERV

    4     4    e214     natl  34   ---   ---    atinp 

    SRV SELECTOR table is (6 of 20992)   1 % full

;
  5. Back up the changes using the chg-db:action=backup:dest=fixed command.

    The following messages appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first.

    BACKUP (FIXED): MASP A - Backup starts on active MASP.
BACKUP (FIXED): MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED): MASP A - Backup starts on standby MASP.
BACKUP (FIXED): MASP A - Backup on standby MASP to fixed disk complete.

Provisioning the ATINP Options

Refer to ATINP Configuration Options in this manual and to the chg-atinpqopts command description in Commands User's Guide for parameter names, valid parameter values, examples, and dependencies.

  1. Verify that the ATINP feature is enabled, by entering the rtrv-ctrl-feat command.

    If the ATINP feature has not been turned on, the status in the ATINP entry is off. 

        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    ATINP                     893022101  off         ----
;
  2. If the Service Portability feature will be used with ATINP, verify that the Service Portability entry appears in the output in 1.
    • If the Service Portability entry appears in the output, continue with 3.
    • If the Service Portability entry does not appear in the output, go to Enabling the Service Portability Feature to enable the feature. Then continue with 3.
  3. Display the current settings of the ATINP options, using the rtrv-atinpqopts command.
  4. Change the ATINP options to the required settings, by entering the chg-atinpqopts command with at least one of the ATINP option parameters specified. If Service Portability will be used with ATINP, change the ATINP options that apply to Service Portability to the required settings.
    chg-atinpqopts:atinptype=<type>:snai=<snai>:atidlm=<delimiter>
  5. Verify the changes by entering the rtrv-atinpqopts command.
  6. If the ATINP feature was not turned on (status is off in the output in 1), go to Enabling ATINP, Setting STP Options, and Turning On ATINP to turn on the feature.
  7. Back up the changes using the chg-db:action=backup:dest=fixed command.
    These messages appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first.
    BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Activating the ATINPQ Local Subsystem

The procedure in this section explains how to activate the ATINPQ local subsystem.

When all feature configuration is complete, the ATINPQ 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-4 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=atinpq :nstat=online Changes local subsystem status to online. No change to local subsystem status in the database.
chg-ss-appl:appl=atinpq :nstat=offline Command is rejected because the subsystem must be inhibited to go offline. Changes local subsystem database status to offline.
  1. Display the online/offline status of the ATINPQ subsystem application, by entering the rtrv-ss-appl command.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT
    ATINPQ 11   offline            
 
    SS-APPL TABLE IS 25% FULL (1 OF 4)
;
  2. Change the ATINPQ subsystem status to online.
    chg-ss-appl:appl=atinpq:nstat=online
  3. Enter the command to allow the ATINPQ subsystem to begin operation.
    alw-map-ss:ssn=<ATINPQ ssn> 
        integrat40 08-05-24 10:37:22 EST  EAGLE5 39.2.0
    Allow map subsystem command sent to all SCCP cards.
    Command Completed.
;
  4. Display the operating status of the ATINPQ subsystem, by entering the rept-stat-sccp command.

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.

  1. Display the status of the controlled features that are controlled with Feature Access Keys (FAKs). Enter the rtrv-ctrl-feat command. The output lists the enabled features in the system and shows the on/off status for each feature.
    • If the entry for the Service Portability feature appears in the rtrv-ctrl-feat output with status on, performing this procedure is not necessary.
    • If the status of the Service Portability feature in the output is off, continue with 2.
  2. Turn on the S-Port feature, by entering the chg-ctrl-feat command.
    chg-ctrl-feat:partnum=893034301:status=on

    When the feature is turned on, the feature status changes to on in the rtrv-ctrl-feat command output. 

        rlghncxa03w 09-08-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    ATINP                     893022101  on          ----
    Service Portability       893034301  on          ----
;
  3. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    The following messages appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first. 

    BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

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.
  1. Display the status of the controlled features that are controlled with Feature Access Keys (FAKs). Enter the rtrv-ctrl-feat command. The output lists the enabled features in the system and shows the on/off status for each feature.
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    TIF Number Portability    893018901  on          ----
    Service Portability       893034301  on          ---- 
;

    If the entry for the Service Portability feature appears in the rtrv-ctrl-feat output with status off, performing this procedure is not necessary.

    If the status of the Service Portability feature in the output is on, continue with 2.

  2. Turn off the S-Port feature, by entering the chg-ctrl-feat command.
    chg-ctrl-feat:partnum=<893034301>:status=off

    When the feature is turned off, the feature status changes to off in the rtrv-ctrl-feat command output. 

        rlghncxa03w 09-05-29 16:40:40 EST  EAGLE5 41.1.0
    The following features have been permanently enabled:
    Feature Name              Partnum    Status  Quantity
    HC-MIM SLK Capacity       893012707  on            64
    TIF Number Portability    893018901  on          ----
    Service Portability       893034301  off         ----
;
  3. Back up the database changes, by entering the following command.
    chg-db:action=backup:dest=fixed

    The following messages appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first.

    BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

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.

When the EAGLE receives an SOR message from its mated subsystem, it will reply with an SOG message if both of the following conditions are met:
  • 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.

Taking the Subsystem Application Offline

Use the procedure in this section to take a subsystem application offline.

  1. Verify the state of the subsystem application - online or offline, by entering the rtrv-ss-appl command.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT
    ATINPQ 11   online            
 
    SS-APPL TABLE IS 25% FULL (1 OF 4)
;
    If the ATINPQ subsystem application is offline, this procedure does not need to be performed.
  2. Display the operating status of the subsystem by entering the rept-stat-sccp command.
  3. Place the subsystem out of service. Specify the subsystem number displayed in the output in 1.
    inh-map-ss:ssn=100 
        rlghncxa03w 08-06-28 14:42:38 GMT EAGLE 39.2.0
    Inhibit map subsystem command sent to all SCCP cards.
    Command Completed.
;
  4. Verify that the subsystem is out of service, by entering the rept-stat-sccp command.
  5. Take the subsystem offline. Enter the chg-ss-appl command with the nstat=offline parameter.
    chg-ss-appl:appl=atinpq:nstat=offline
  6. Verify the changes by entering the rtrv-ss-appl command.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT
    ATINPQ 11   offline            
 
    SS-APPL TABLE IS 25% FULL (1 OF 4)
;
  7. Back up the new changes using the chg-db:action=backup:dest=fixed command.
    The following messages appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first.
    BACKUP (FIXED): MASP A - Backup starts on active MASP.
BACKUP (FIXED): MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED): MASP A - Backup starts on standby MASP.
BACKUP (FIXED): MASP A - Backup on standby MASP to fixed disk complete.

Taking the Subsystem Application Online

Use the procedure in this section to take the subsystem application online.

  1. Verify the state of the subsystem application - online or offline, by entering the rtrv-ss-appl command.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT
    ATINPQ 11   offline            
 
    SS-APPL TABLE IS 25% FULL (1 OF 4)
;
    If the ATINPQ subsystem is online, this procedure does not need to be performed.
  2. Display the operating status of the subsystem by entering the rept-stat-sccp command.
  3. Take the subsystem application online. Enter the chg-ss-appl command with the nstat=online parameter.
    chg-ss-appl:appl=atinpq:nstat=online
  4. Verify the changes by entering the rtrv-ss-appl command.
        tekelecstp 08-07-25 08:02:22 EST  EAGLE 39.2.0 
    APPL   SSN  STAT
    ATINPQ  11   online            
 
    SS-APPL TABLE IS 25% FULL (1 OF 4)
;
  5. Back up the new changes using the chg-db:action=backup:dest=fixed command.
    The following messages appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first.
    BACKUP (FIXED): MASP A - Backup starts on active MASP.
BACKUP (FIXED): MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED): MASP A - Backup starts on standby MASP.
BACKUP (FIXED): MASP A - Backup on standby MASP to fixed disk complete.