This procedure is used to add an allowed affected point code screen to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Adding an Allowed Affected Point Code Screen” in Database Administration - GWS User's Guide.

If you wish to use any of these items in adding the allowed affected point code screen to the database, perform the “Adding an Allowed Affected Point Code Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed affected point code screen being added to the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.

• If gateway screening stop action sets are assigned to the allowed affected point code screen being added.

This procedure is used to remove an allowed affected point code screen from the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Removing an Allowed Affected Point Code Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in removing the allowed affected point code screen from the database, perform the “Removing an Allowed Affected Point Code Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed affected point code screen being removed from the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the screens referencing the allowed affected point code screen being removed.

  Figure 5-2 Removing an Allowed Affected Point Code Screen from the SEAS Terminal

This procedure is used to change an allowed affected point code screen in the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Changing an Allowed Affected Point Code Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in changing the allowed affected point code screen in the database, perform the “Changing an Allowed Affected Point Code Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed affected point code screen being changed in the database uses ITU-I point codes (with or without the pcst or npcst parameters), 14-bit ITU-N point codes (with or without the pcst or ncpst parameters), or 24-bit ITU-N point codes. The pcst and ncpst parameters can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the allowed affected point code screen being changed.

  Figure 5-3 Changing an Allowed Affected Point Code Screen from the SEAS Terminal

This procedure is used to add an allowed called party address screen to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Adding an Allowed Called Party Address Screen” in Database Administration - GWS User's Guide.

If you wish to use any of these items in adding the allowed called party address screen to the database, perform the “Adding an Allowed Called Party Address Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed called party address screen being added to the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.

• If gateway screening stop action sets are assigned to the allowed called party address screen being added.

Sheet 2 of 2

This procedure is used to remove an allowed called party address screen from the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Removing an Allowed Called Party Address Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in removing the allowed called party address screen from the database, perform the “Removing an Allowed Called Party Address Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed called party address screen being removed from the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the screens referencing the allowed called party address screen being removed.

  Figure 5-5 Removing an Allowed Called Party Address Screen from the SEAS Terminal

  
  
  

  Sheet 1 of 3

  
  
  

  Sheet 2 of 3

  
  
  

  Sheet 3 of 3

This procedure is used to change an allowed called party address screen in the database. This procedure uses the EAGLE command. For more information on this procedure, see “Changing an Allowed Called Party Address Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in changing the allowed called party address screen in the database, perform the “Changing an Allowed Called Party Address Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed called party address screen being changed in the database uses ITU-I point codes (with or without the pcst or npcst parameters), 14-bit ITU-N point codes (with or without the pcst or npcst parameters), or 24-bit ITU-N point codes. The pcst and npcst parameters can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the allowed called party address screen being changed.

  Figure 5-6 Changing an Allowed Called Party Address Screen from the SEAS Terminal

  
  
  

This procedure is used to add an allowed translation type screen to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Adding an Allowed Translation Type Screen” in Database Administration - GWS User's Guide.

If gateway screening stop action sets are to be assigned to the allowed translation type screen being added to the database, perform the “Adding an Allowed Translation Type Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

Sheet 2 of 2

This procedure is used to remove an allowed translation type screen from the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Removing an Allowed Translation Type Screen” in Database Administration - GWS User's Guide.

If gateway screening stop action sets are assigned to the screens referencing the allowed translation type screen being removed from the database, perform the “Removing an Allowed Translation Type Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

This procedure is used to change an allowed translation type screen in the database. This procedure uses the EAGLE command. For more information on this procedure, see “Changing an Allowed Translation Type Screen” in Database Administration - GWS User's Guide.

If gateway screening stop action sets are to be assigned to the allowed translation type screen being changed in the database, perform the “Changing an Allowed Translation Type Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

This procedure is used to add an allowed calling party address screen to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Adding an Allowed Calling Party Address Screen” in Database Administration - GWS User's Guide.

If you wish to use any of these items in adding the allowed calling party address screen to the database, perform the “Adding an Allowed Calling Party Address Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed calling party address screen being added to the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the allowed calling party address screen being added.
• If you wish to use the sccpmt parameter of the EAGLE command ent-scr-cgpa.

Sheet 2 of 3

Sheet 3 of 3

This procedure is used to remove an allowed calling party address screen from the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Removing an Allowed Calling Party Address Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in removing the allowed calling party address screen from the database, perform the “Removing an Allowed Calling Party Address Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed calling party address screen being removed from the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the screens referencing the allowed calling party address screen being removed.
• If you wish to use the sccpmt parameter of the EAGLE command dlt-scr-cgpa.

  Figure 5-11 Removing an Allowed Calling Party Address Screen from the SEAS Terminal

  
  
  

  Sheet 1 of 5

  
  
  

  Sheet 2 of 5

  
  
  

  Sheet 3 of 5

  
  
  

  Sheet 4 of 5

  
  
  

  Sheet 5 of 5

This procedure is used to change an allowed calling party address screen in the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Changing an Allowed Calling Party Address Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in changing the allowed calling party address screen in the database, perform the “Changing an Allowed Calling Party Address Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed calling party address screen being changed in the database uses ITU-I point codes (with or without the pcst or npcst parameters), 14-bit ITU-N point codes (with or without the pcst or npcst parameters), or 24-bit ITU-N point codes. The pcst and npcst parameters can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the allowed calling party address screen being changed.
• If you wish to use the sccpmt and nsccpmt parameters of the EAGLE command chg-scr-cgpa.

  Figure 5-12 Changing an Allowed Calling Party Address Screen from the SEAS Terminal

  
  
  

  Sheet 1 of 3

  
  
  

  Sheet 2 of 3

  
  
  

  Sheet 3 of 3

This procedure is used to remove an allowed affected destination field screen to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Adding an Allowed Affected Destination Field Screen” in Database Administration - GWS User's Guide.

If you wish to use any of these items in adding the allowed affected destination field screen to the database, perform the “Adding an Allowed Affected Destination Field Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed affected destination field screen being added to the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.

• If gateway screening stop action sets are assigned to the allowed affected destination field screen being added.

This procedure is used to remove an allowed affected destination screen to the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Removing an Allowed Affected Destination Field Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in removing the allowed affected destination screen from the database, perform the “Removing an Allowed Affected Destination Field Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed affected destination screen being removed from the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the screens referencing the allowed affected destination screen being removed.

  Figure 5-14 Removing an Allowed Affected Destination Screen from the SEAS Terminal

  
  
  

  Sheet 1 of 3

  
  
  

  Sheet 2 of 3

  
  
  

  Sheet 3 of 3

This procedure is used to remove an allowed affected destination field screen to the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Changing an Allowed Affected Destination Field Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in changing the allowed affected destination field screen in the database, perform the “Changing an Allowed Affected Destination Field Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed affected destination field screen being changed in the database uses ITU-I point codes (with or without the pcst or npcst parameters), 14-bit ITU-N point codes (with or without the pcst or npcst parameters), or 24-bit ITU-N point codes. The pcst and npcst parameters can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the allowed affected destination field screen being changed.

  Figure 5-15 Changing an Allowed Affected Destination Screen from the SEAS Terminal

This procedure is used to add a blocked destination point code screen to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Adding a Blocked DPC Screen” in Database Administration - GWS User's Guide.

If you wish to use any of these items in adding the blocked destination point code screen to the database, perform the “Adding a Blocked DPC Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the blocked destination point code screen being added to the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.

• If gateway screening stop action sets are assigned to the blocked destination point code screen being added.

Sheet 2 of 4

Sheet 3 of 4

Sheet 4 of 4

This procedure is used to remove a blocked destination point code screen from the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Removing a Blocked DPC Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in removing the blocked destination point code screen from the database, perform the “Removing a Blocked DPC Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the blocked destination point code screen being removed from the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the screens referencing the blocked destination point code screen being removed.

Sheet 2 of 5

Sheet 3 of 5

Sheet 4 of 5

Sheet 5 of 5

This procedure is used to change a blocked destination point code screen in the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Changing a Blocked DPC Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in changing the blocked destination point code screen in the database, perform the “Changing a Blocked DPC Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the blocked destination point code screen being changed in the database uses ITU-I point codes (with or without the pcst or npcst parameters), 14-bit ITU-N point codes (with or without the pcst or npcst parameters), or 24-bit ITU-N point codes. The pcst and npcst parameters can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the blocked destination point code screen being changed.

Sheet 2 of 4

Sheet 3 of 4

Sheet 4 of 4

This procedure is used to add an allowed destination point code screen to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Adding an Allowed DPC Screen” in Database Administration - GWS User's Guide.

If you wish to use any of these items in adding the allowed destination point code screen to the database, perform the “Adding an Allowed DPC Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed destination point code screen being added to the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.

• If gateway screening stop action sets are assigned to the allowed destination point code screen being added.

Sheet 2 of 5

Sheet 3 of 5

Sheet 4 of 5

Sheet 5 of 5

This procedure is used to remove an allowed destination point code screen from the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Removing an Allowed DPC Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in removing the allowed destination point code screen from the database, perform the “Removing an Allowed DPC Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed destination point code screen being removed from the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the screens referencing the allowed destination point code screen being removed.

  Figure 5-20 Removing an Allowed DPC Screen from the SEAS Terminal

  
  
  

  Sheet 1 of 4

  
  
  

  Sheet 2 of 4

  
  
  

  Sheet 3 of 4

  
  
  

  Sheet 4 of 4

This procedure is used to change an allowed destination point code screen in the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Changing an Allowed DPC Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in changing the allowed destination point code screen in the database, perform the “Changing an Allowed DPC Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed destination point code screen being changed in the database uses ITU-I point codes (with or without the pcst or npcst parameters), 14-bit ITU-N point codes (with or without the pcst or npcst parameters), or 24-bit ITU-N point codes. The pcst and npcst parameters can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the allowed destination point code screen being changed.

  Figure 5-21 Changing an Allowed DPC Screen from the SEAS Terminal

  
  
  

  Sheet 1 of 5

  
  
  

  Sheet 2 of 5

  
  
  

  Sheet 3 of 5

  
  
  

  Sheet 4 of 5

  
  
  

  Sheet 5 of 5

This procedure is used to add an allowed SIO screen to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Adding an Allowed SIO Screen” in Database Administration - GWS User's Guide.

If gateway screening stop action sets are to be assigned to the allowed SIO screen being added to the database, perform the “Adding an Allowed SIO Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

Sheet 2 of 7

Sheet 3 of 7

Sheet 4 of 7

Sheet 5 of 7

Sheet 6 of 7

Sheet 7 of 7

This procedure is used to remove an allowed SIO screen from the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Removing an Allowed SIO Screen” in Database Administration - GWS User's Guide.

If gateway screening stop action sets are assigned to the screens referencing the allowed SIO screen being removed from the database, perform the “Removing an Allowed SIO Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

Sheet 2 of 3

Sheet 3 of 3

This procedure is used to change an allowed SIO screen in the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Changing an Allowed SIO Screen” in Database Administration - GWS User's Guide.

If gateway screening stop action sets are to be assigned to the allowed SIO screen being changed in the database, perform the “Changing an Allowed SIO Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

Sheet 2 of 7

Sheet 3 of 7

Sheet 4 of 7

Sheet 5 of 7

Sheet 6 of 7

Sheet 7 of 7

This procedure is used to add a blocked origination point code screen to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Adding a Blocked OPC Screen” in Database Administration - GWS User's Guide.

If you wish to use any of these items in adding the blocked origination point code screen to the database, perform the “Adding a Blocked OPC Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the blocked origination point code screen being added to the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.

• If gateway screening stop action sets are assigned to the blocked origination point code screen being added.

Sheet 2 of 5

Sheet 3 of 5

Sheet 4 of 5

Sheet 5 of 5

This procedure is used to remove a blocked origination point code screen from the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Removing a Blocked OPC Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in removing the blocked origination point code screen from the database, perform the “Removing a Blocked OPC Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the blocked origination point code screen being removed from the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the screens referencing the blocked origination point code screen being removed.

Sheet 2 of 2

This procedure is used to change a blocked origination point code screen in the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Changing a Blocked OPC Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in changing the blocked origination point code screen in the database, perform the “Changing a Blocked OPC Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the blocked origination point code screen being changed in the database uses ITU-I point codes (with or without the pcst or npcst parameters), 14-bit ITU-N point codes (with or without the pcst or npcst parameters), or 24-bit ITU-N point codes. The pcst and npcst parameters can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the blocked origination point code screen being changed.

Sheet 2 of 5

Sheet 3 of 5

Sheet 4 of 5

Sheet 5 of 5

This procedure is used to add an allowed origination point code screen to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Adding an Allowed OPC Screen” in Database Administration - GWS User's Guide.

If you wish to use any of these items in adding the allowed origination point code screen to the database, perform the “Adding an Allowed OPC Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed origination point code screen being added to the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.

• If gateway screening stop action sets are assigned to the allowed origination point code screen being added.

Sheet 2 of 6

Sheet 3 of 6

Sheet 4 of 6

Sheet 5 of 6

Sheet 6 of 6

This procedure is used to remove an allowed origination point code screen from the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Removing an Allowed OPC Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in removing the allowed origination point code screen from the database, perform the “Removing an Allowed OPC Screen” procedure in the Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed origination point code screen being removed from the database uses ITU-I point codes (with or without the pcst parameter), 14-bit ITU-N point codes (with or without the pcst parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the screens referencing the allowed origination point code screen being removed.

This procedure is used to change an allowed origination point code screen in the database. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Changing an Allowed OPC Screen” in Database Administration - GWS User's Guide.

If any of the following items are used in changing the allowed origination point code screen in the database, perform the “Changing an Allowed OPC Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands:

• If the allowed origination point code screen being changed in the database uses ITU-I point codes (with or without the pcst or npcst parameters), 14-bit ITU-N point codes (with or without the pcst or npcst parameters), or 24-bit ITU-N point codes. The pcst and npcst parameters can be used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.
• If gateway screening stop action sets are assigned to the allowed origination point code screen being changed.

  Figure 5-30 Changing an Allowed OPC Screen from the SEAS Terminal

  
  
  

  Sheet 1 of 6

  
  
  

  Sheet 2 of 6

  
  
  

  Sheet 3 of 6

  
  
  

  Sheet 4 of 6

  
  
  

  Sheet 5 of 6

  
  
  

  Sheet 6 of 6

This procedure is used to add a gateway linkset to the database. This procedure performs the same functions as the “Adding an SS7 Linkset” procedure on in Database Administration - SS7 User's Guide and the “Adding a Screen Set” in Database Administration - GWS User's Guide. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db.

On the EAGLE, the linkset name can have a maximum of 10 characters. The SEAS interface supports a linkset name with a maximum of eight characters. Linkset names specified in this procedure can have a maximum of eight characters. For linkset names provisioned on the EAGLE that have more than eight characters, the SEAS interface truncates the linkset name to the first eight characters when that linkset name is displayed on the SEAS interface.

Supplier Specific Parameters

The EAGLE accepts the values for these parameters as supplier specific parameters: gwsa, gwsm, gwsd, actname, and destfld. Table 5-1 shows how the EAGLE parameter values are mapped to the SEAS values and a definition of each parameter.

For more information on the gwsa, gwsm, and gwsd parameters, see “Adding an SS7 Linkset” in Database Administration – SS7 User's Guide and “Gateway Screening States” in Database Administration - GWS User's Guide.

For more information on the actname parameter, see “Configuring Gateway Screening Stop Action Sets” in Database Administration - GWS User's Guide.

For more information on the destfld parameter, see “Automatic Destination Field Screening” in Database Administration - GWS User's Guide.

The supplier specific parameters must be entered in this order.

:"[GWSA], [GWSM], [GWSD], [ACTNAME], [DESTFLD]":

The supplier specific parameters are optional. The default value will be entered for any supplier specific parameter not specified when adding the gateway linkset. The default values for the supplier specific parameters are:

• GWSA = 0 (off)
• GWSM = 0 (off)
• GWSD = 0 (off)
• ACTNAME = No actname value is specified
• DESTFLD = 1 (yes)

If the characters :: are specified for the supplier specific parameters, the EAGLE sets the Gateway Screening GWSA, GWSM, GWSD parameter values to their default values.

If the characters :",,,,": are specified for the supplier specific parameters, values for all the supplier specific parameters are not changed from the current values.

When the gateway linkset is displayed, the supplier specific parameter values are displayed in this order.

GWSA, GWSM, GWSD, ACTNAME, DESTFLD, SCRN

Gateway Screening States

Gateway screening on a particular gateway linkset can be set to be in one of four states:

NO SCREENING – Screening is not performed. All message signaling units (MSUs) are passed. This state is set by specifying the supplier specific parameters gwsa and gwsm equal to 0 (off).

SCREEN AND REPORT – Screening is performed. When an MSU fails screening it is discarded, an output message is generated, and measurements are pegged. This state is set by specifying the supplier specific parameters gwsa and gwsm equal to 1 (on).

SCREENANDDON'T REPORT – Screening is performed. When an MSU fails screening it is discarded and measurements are pegged, but no output message is generated. This state is set by specifying the supplier specific parameters gwsa to 1 (on) and gwsm to 0 (off).

SCREEN TEST MODE – Screening is performed, but all MSUs are passed. When an MSU fails screening, an output message is generated, but the MSU is still passed. This state is set by specifying the supplier specific parameters gwsa to 0 (off) and gwsm to 1 (on).

If a gateway screening stop action set is to be assigned to the gateway linkset, the name of the gateway screening stop action set must be defined in the database. The gateway screening stop action sets in the database can be shown using the EAGLE command rtrv-gws-actset. For more information on the gateway screening stop action sets, see “Configuring Gateway Screening Stop Action Sets” in Database Administration - GWS User's Guide.

The gwsd parameter allows the discarding of messages that should have gone through the gateway screening process, but did not. The gwsd parameter is only intended to be used with the Database Transport Access (DTA) feature. If you are not using the DTA feature, the gwsd parameter should not be specified or should be set to no (gwsd=0). for more information on the DTA feature, see “Database Transport Access (DTA) Configuration” in Database Administration - Features User's Guide.

Sheet 2 of 8

Sheet 3 of 8

Sheet 4 of 8

Sheet 5 of 8

Sheet 6 of 8

Sheet 7 of 8

Sheet 8 of 8

This procedure is used to remove a gateway linkset from the database. This procedure uses the EAGLE command chg-db. This procedure performs the same functions as the “Removing a Linkset Containing SS7 Signaling Links” on in Database Administration - SS7 User's Guide and the “Removing a Screen Set” in Database Administration - GWS User's Guide.

On the EAGLE, the linkset name can have a maximum of 10 characters. The SEAS interface supports a linkset name with a maximum of eight characters. Linkset names specified in this procedure can have a maximum of eight characters. For linkset names provisioned on the EAGLE that have more than eight characters, the SEAS interface truncates the linkset name to the first eight characters when that linkset name is displayed on the SEAS interface. If the linkset name of the linkset being removed was configured on the EAGLE with more than eight characters, only the first eight characters of the linkset name can be specified in this procedure.

This procedure is used to change a gateway linkset in the database. This procedure uses the EAGLE command chg-db. This procedure performs the same functions as the “Changing an SS7 Linkset” in Database Administration Manual - SS7 and the “Changing a Screen Set” in Database Administration - GWS User's Guide.

On the EAGLE, the linkset name can have a maximum of 10 characters. The SEAS interface supports a linkset name with a maximum of eight characters. Linkset names specified in this procedure can have a maximum of eight characters. For linkset names provisioned on the EAGLE that have more than eight characters, the SEAS interface truncates the linkset name to the first eight characters when that linkset name is displayed on the SEAS interface.

Supplier Specific Parameters

The EAGLE accepts the values for these parameters as supplier specific parameters: gwsa, gwsm, gwsd, actname, and destfld Table 5-2. shows how the EAGLE parameter values are mapped to the SEAS values and a definition of each parameter.

For more information on the gwsa, gwsm, and gwsd parameters, see “Changing an SS7 Linkset” in Database Administration - SS7 User's Guide and “Gateway Screening States” in Database Administration - GWS User's Guide.

For more information on the actname parameter, see “Configuring Gateway Screening Stop Action Sets” in Database Administration - GWS User's Guide.

For more information on the destfld parameter, see “Automatic Destination Field Screening” in Database Administration - GWS User's Guide.

The supplier specific parameters must be entered in this order.

:"[GWSA], [GWSM], [GWSD], [ACTNAME], [DESTFLD]":

The supplier specific parameters are optional. The current value of any supplier specific parameter that is not specified when changing the linkset is not changed.

If the characters :: are specified for the supplier specific parameters, the EAGLE sets the Gateway Screening GWSA, GWSM, GWSD parameter values to their default values and possibly change any values that were previously set for these parameters.

If the characters :",,,,": are specified for the supplier specific parameters, the values for all the supplier specific parameters are not changed.

When the gateway linkset is displayed, the supplier specific parameter values are displayed in this order.

GWSA, GWSM, GWSD, ACTNAME, DESTFLD, SCRN

Gateway Screening States

Gateway screening on a particular linkset can be set to be in one of four states:

NO SCREENING – Screening is not performed. All message signaling units (MSUs) are passed. This state is set by specifying the supplier specific parameters gwsa and gwsm equal to 0 (off).

SCREEN AND REPORT – Screening is performed. When an MSU fails screening it is discarded, an output message is generated, and measurements are pegged. This state is set by specifying the supplier specific parameters gwsa and gwsm equal to 1 (on).

SCREENANDDON'T REPORT – Screening is performed. When an MSU fails screening it is discarded and measurements are pegged, but no output message is generated. This state is set by specifying the supplier specific parameters gwsa to 1 (on) and gwsm to 0 (off).

SCREEN TEST MODE – Screening is performed, but all MSUs are passed. When an MSU fails screening, an output message is generated, but the MSU is still passed. This state is set by specifying the supplier specific parameters gwsa to 0 (off) and gwsm to 1 (on).

If a gateway screening stop action set is to be assigned to the gateway linkset, the name of the gateway screening stop action set must be defined in the database. The gateway screening stop action sets in the database can be shown using the EAGLE command rtrv-gws-actset. For more information on the gateway screening stop action sets, see “Configuring Gateway Screening Stop Action Sets” in Database Administration - GWS User's Guide.

The gwsd parameter allows the discarding of messages that should have gone through the gateway screening process, but did not. The gwsd parameter is only intended to be used with the Database Transport Access (DTA) feature. If you are not using the DTA feature, the gwsd parameter should not be specified or should be set to no (gwsd=0). for more information on the DTA feature, see “Database Transport Access (DTA) Configuration,” in Database Administration - Features User's Guide.

Sheet 2 of 8

Sheet 3 of 8

Sheet 4 of 8

Sheet 5 of 8

Sheet 6 of 8

Sheet 7 of 8

Sheet 8 of 8

This procedure is used to set the threshold for reporting these gateway screening activities.

• The threshold for MSUs received on a gateway link set.
• The threshold for MSUs rejected on a gateway link set because of screening.

This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Setting the Threshold for Reporting Gateway Screening Activity” in Database Administration - GWS User's Guide.

This procedure is used to configure the maximum number of UIMs sent to the terminal and the amount of time during which the UIMs are sent. This procedure uses the EAGLE command chg-db. For more information on this procedure, see “Setting the Maximum Number of Gateway Screening Rejected Messages” in Database Administration - GWS User's Guide.

This procedure is used to add an allowed ISUP message type screen to the database. This procedure uses the EAGLE commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Adding an Allowed ISUP Message Type Screen” in Database Administration - GWS User's Guide.

If you wish to assign gateway screening stop action sets to the allowed ISUP message type screen, or use the tupmt parameter of the EAGLE’s ent-scr-isup command, perform the “Adding an Allowed ISUP Message Type Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

The tupmt parameter (TUP message type) of the EAGLE’s ent-scr-isup command is not supported by SEAS. A screen can be provisioned to screen for TUP messages using the SEAS interface by provisioning an allowed SIO screen with the service indicator value of 4, with the NSFI value of ISUP, and the screening reference name (NSR) of the allowed ISUP screen to be used to screen for TUP messages. Go to one of these procedures to provision the allowed SIO screen:

• Adding an Allowed SIO Screen
• Changing an Allowed SIO Screen.

This procedure is used to remove an allowed ISUP message type screen from the database. This procedure uses the EAGLE chg-db command. For more information on this procedure, see “Removing an Allowed ISUP Message Type Screen” in Database Administration - GWS User's Guide.

If you wish to use the tupmt parameter of the EAGLE’s dlt-scr-isup command, perform the “Changing an Allowed ISUP Message Type Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

Sheet 2 of 3

Sheet 3 of 3

This procedure is used to change the attributes of an allowed ISUP message type screen in the database. This procedure uses the EAGLE chg-db command. For more information on this procedure, see “Changing an Allowed ISUP Message Type Screen” in Database Administration - GWS User's Guide.

If you wish to assign gateway screening stop action sets to the allowed ISUP message type screen being changed, or use the tupmt and ntupmt parameters of the EAGLE’s chg-scr-isup command, perform the “Changing an Allowed ISUP Message Type Screen” procedure in Database Administration - GWS User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

The tupmt and ntupmt parameters (TUP message type) of the EAGLE’s chg-scr-isup command are not supported by SEAS. A screen can be provisioned to screen for TUP messages using the SEAS interface by provisioning an allowed SIO screen with the service indicator value of 4, with the NSFI value of ISUP, and the screening reference name (NSR) of the allowed ISUP screen to be used to screen for TUP messages. Go to one of these procedures to provision the allowed SIO screen:

• Adding an Allowed SIO Screen
• Changing an Allowed SIO Screen.

  Figure 5-38 Changing an Allowed ISUP Message Type Screen from the SEAS Terminal