database administration manual - seas€¦ · 910-6013-001 revision a, march 2011 ii. changing a...

Tekelec EAGLE® 5

Release 43.0

Database Administration Manual - SEAS910-6013-001 Revision A

March 2011

Copyright 2011 Tekelec. All Rights Reserved. Printed in USA.Legal Information can be accessed from the Main Menu of the optical disc or on the

Tekelec Customer Support web site in the Legal Information folder of the Product Support tab.

Table of Contents

Chapter 1: Introduction.......................................................................9Overview..................................................................................................................................10Scope and Audience...............................................................................................................13Manual Organization..............................................................................................................14Documentation Admonishments..........................................................................................14Customer Care Center............................................................................................................15Emergency Response..............................................................................................................17Related Publications...............................................................................................................17Documentation Availability, Packaging, and Updates.....................................................17Locate Product Documentation on the Customer Support Site.......................................18Maintenance and Administration Subsystem.....................................................................19EAGLE 5 ISS Database Partitions.........................................................................................20

Chapter 2: Configuring Destination Tables..................................24Adding a Cluster Point Code................................................................................................25Changing the Attributes of a Cluster Point Code..............................................................29Adding a Network Routing Point Code..............................................................................33Changing the Self Identification of the EAGLE 5 ISS........................................................36Adding a Destination Point Code.........................................................................................42Removing a Destination Point Code....................................................................................45Changing a Destination Point Code.....................................................................................48

Chapter 3: SS7 Configuration...........................................................50Adding an SS7 Linkset...........................................................................................................51Removing a Linkset Containing SS7 Signaling Links........................................................58Changing an SS7 Linkset........................................................................................................60Adding an SS7 Signaling Link...............................................................................................70Removing an SS7 Signaling Link..........................................................................................87Adding a Route.......................................................................................................................90Changing a Route....................................................................................................................93

Chapter 4: Global Title Translation (GTT) Configuration.........98Provisioning a Mated Application........................................................................................99Removing a Mated Application..........................................................................................101

ii910-6013-001 Revision A, March 2011

Changing a Mated Application...........................................................................................103Adding a Global Title Translation......................................................................................105Removing a Global Title Translation.................................................................................113Changing a Global Title Translation..................................................................................115

Chapter 5: Gateway Screening (GWS) Configuration...............126Adding an Allowed Affected Point Code Screen.............................................................128Removing an Allowed Affected Point Code Screen........................................................129Changing an Allowed Affected Point Code Screen.........................................................130Adding an Allowed Called Party Address Screen...........................................................131Removing an Allowed Called Party Address Screen......................................................133Changing an Allowed Called Party Address Screen.......................................................136Adding an Allowed Translation Type Screen..................................................................138Removing an Allowed Translation Type Screen..............................................................140Changing an Allowed Translation Type Screen...............................................................141Adding an Allowed Calling Party Address Screen.........................................................142Removing an Allowed Calling Party Address Screen.....................................................146Changing an Allowed Calling Party Address Screen......................................................151Adding an Allowed Affected Destination Field Screen..................................................154Removing an Allowed Affected Destination Field Screen..............................................155Changing an Allowed Affected Destination Field Screen..............................................158Adding a Blocked DPC Screen............................................................................................159Removing a Blocked DPC Screen.......................................................................................163Changing a Blocked DPC Screen........................................................................................168Adding an Allowed DPC Screen........................................................................................172Removing an Allowed DPC Screen....................................................................................177Changing an Allowed DPC Screen.....................................................................................181Adding an Allowed SIO Screen..........................................................................................186Removing an Allowed SIO Screen......................................................................................193Changing an Allowed SIO Screen......................................................................................196Adding a Blocked OPC Screen............................................................................................203Removing a Blocked OPC Screen.......................................................................................209Changing a Blocked OPC Screen........................................................................................211Adding an Allowed OPC Screen........................................................................................216Removing an Allowed OPC Screen....................................................................................222Changing an Allowed OPC Screen.....................................................................................223Adding a Gateway Linkset..................................................................................................229Removing a Gateway Linkset.............................................................................................239Changing a Gateway Linkset..............................................................................................240Setting the Threshold for Reporting Gateway Screening Activity................................250

iii910-6013-001 Revision A, March 2011

Setting the Maximum Number of Gateway Screening Rejected Messages..................251Adding an Allowed ISUP Message Type Screen.............................................................252Removing an Allowed ISUP Message Type Screen.........................................................253Changing an Allowed ISUP Message Type Screen..........................................................256

Chapter 6: Enhanced Global Title Translation (EGTT)Configuration.................................................................................258

Provisioning a Mated Application......................................................................................259Removing a Mated Application..........................................................................................261Changing a Mated Application...........................................................................................263Adding Global Title Address Information........................................................................265Removing Global Title Address Information...................................................................275Changing Global Title Address Information....................................................................277

Appendix A: EAGLE 5 ISS/SEAS Compliance Matrix..............290Introduction...........................................................................................................................291SEAS-STP Interface Specification, GR-310-CORE, Issue 1, November 1994 ...............291SEAS-STP Gateway Function Interface Specification, GR-778-CORE, Issue 1,

November 1994 ...............................................................................................................357Glossary..................................................................................................................378

iv910-6013-001 Revision A, March 2011

List of FiguresFigure 1: EAGLE 5 ISS Database Partitions (Legacy Control Cards)..........................................21Figure 2: EAGLE 5 ISS Database Partitions (E5-Based Control Cards).......................................22Figure 3: Adding a Cluster Point Code from the SEAS Terminal................................................25Figure 4: Changing the Attributes of a Cluster Point Code from the SEAS Terminal..............30Figure 5: Adding a Network Routing Point Code from the SEAS Terminal.............................35Figure 6: Changing the Self Identification of the EAGLE 5 ISS from the SEAS Terminal........38Figure 7: Adding a Destination Point Code from the SEAS Terminal........................................43Figure 8: Removing a Destination Point Code from the SEAS Terminal....................................46Figure 9: Changing a Destination Point Code from the SEAS Terminal....................................49Figure 10: Adding an SS7 Linkset from the SEAS Terminal.........................................................55Figure 11: Removing a Linkset Containing SS7 Signaling Links from the SEAS

Terminal..........................................................................................................................................59Figure 12: Changing an SS7 Linkset from the SEAS Terminal.....................................................66Figure 13: Adding an SS7 Signaling Link from the SEAS Terminal............................................77Figure 14: Removing an SS7 Signaling Link from the SEAS Terminal.......................................89Figure 15: Adding a Route from the SEAS Terminal.....................................................................92Figure 16: Changing a Route from the SEAS Terminal.................................................................94Figure 17: Provisioning a Mated Application...............................................................................100Figure 18: Removing a Mated Application...................................................................................103Figure 19: Changing a Mated Application....................................................................................105Figure 20: Adding a Global Title Translation...............................................................................108Figure 21: Removing a Global Title Translation from the SEAS Terminal...............................114Figure 22: Changing a Global Title Translation............................................................................118Figure 23: Adding an Allowed Affected Point Code Screen from the SEAS Terminal..........128Figure 24: Removing an Allowed Affected Point Code Screen from the SEAS Terminal......130Figure 25: Changing an Allowed Affected Point Code Screen from the SEAS Terminal......131Figure 26: Adding an Allowed Called Party Address Screen from the SEAS Terminal........132Figure 27: Removing an Allowed Called Party Address Screen from the SEAS

Terminal........................................................................................................................................134Figure 28: Changing an Allowed Called Party Address Screen from the SEAS Terminal.....137Figure 29: Adding an Allowed Translation Type Screen from the SEAS Terminal................138Figure 30: Removing an Allowed Translation Type Screen from the SEAS Terminal...........141Figure 31: Changing an Allowed Translation Type Screen from the SEAS Terminal............142Figure 32: Adding an Allowed Calling Party Address Screen from the SEAS Terminal.......143Figure 33: Removing an Allowed Calling Party Address Screen from the SEAS

Terminal........................................................................................................................................147

v910-6013-001 Revision A, March 2011

Figure 34: Changing an Allowed Calling Party Address Screen from the SEASTerminal........................................................................................................................................152

Figure 35: Adding an Allowed Affected Destination Screen from the SEAS Terminal.........155Figure 36: Removing an Allowed Affected Destination Screen from the SEAS Terminal.....156Figure 37: Changing an Allowed Affected Destination Screen from the SEAS Terminal......159Figure 38: Adding a Blocked DPC Screen from the SEAS Terminal.........................................160Figure 39: Removing a Blocked DPC Screen from the SEAS Terminal.....................................164Figure 40: Changing a Blocked DPC Screen from the SEAS Terminal......................................169Figure 41: Adding an Allowed DPC Screen from the SEAS Terminal......................................173Figure 42: Removing an Allowed DPC Screen from the SEAS Terminal.................................178Figure 43: Changing an Allowed DPC Screen from the SEAS Terminal..................................182Figure 44: Adding an Allowed SIO Screen from the SEAS Terminal........................................187Figure 45: Removing an Allowed SIO Screen from the SEAS Terminal...................................194Figure 46: Changing an Allowed SIO Screen from the SEAS Terminal....................................197Figure 47: Adding a Blocked OPC Screen from the SEAS Terminal.........................................205Figure 48: Removing a Blocked OPC Screen from the SEAS Terminal.....................................210Figure 49: Changing a Blocked OPC Screen from the SEAS Terminal.....................................212Figure 50: Adding an Allowed OPC Screen from the SEAS Terminal......................................217Figure 51: Removing an Allowed OPC Screen from the SEAS Terminal.................................223Figure 52: Changing an Allowed OPC Screen from the SEAS Terminal..................................224Figure 53: Adding a Gateway Linkset from the SEAS Terminal...............................................232Figure 54: Removing a Gateway Linkset from the SEAS Terminal...........................................240Figure 55: Changing a Gateway Linkset from the SEAS Terminal............................................243Figure 56: Setting the Threshold for Reporting Gateway Screening Activity from the

SEAS Terminal.............................................................................................................................251Figure 57: Setting the Maximum Number of Gateway Screening Rejected Messages from

the SEAS Terminal......................................................................................................................251Figure 58: Adding an Allowed ISUP Message Type Screen from the SEAS Terminal...........252Figure 59: Removing an Allowed ISUP Message Type Screen from the SEAS Terminal......254Figure 60: Changing an Allowed ISUP Message Type Screen from the SEAS Terminal.......257Figure 61: Provisioning a Mated Application...............................................................................260Figure 62: Removing a Mated Application...................................................................................263Figure 63: Changing a Mated Application....................................................................................265Figure 64: Adding Global Title Address Information.................................................................268Figure 65: Removing Global Title Address Information.............................................................276Figure 66: Changing Global Title Address Information..............................................................280

vi910-6013-001 Revision A, March 2011

List of TablesTable 1: Admonishments...................................................................................................................14Table 2: NCAI Supplier Specific Parameter Values.......................................................................25Table 3: NCAI Supplier Specific Parameter Values.......................................................................30Table 4: Adding an SS7 Linkset Supplier Specific Parameters.....................................................52Table 5: Signaling Link Selector (SLS) Conversion (ANSI Linksets Only).................................54Table 6: Changing an SS7 Linkset Supplier Specific Parameters.................................................62Table 7: Signaling Link Selector (SLS) Conversion (ANSI Linksets Only).................................64Table 8: SS7 Signaling Link Card and Application Combinations..............................................71Table 9: Signaling Link Procedures..................................................................................................71Table 10: SS7 Signaling Link Supplier Specific Parameters..........................................................72Table 11: SS7 Signaling Link Parameter Combinations.................................................................74Table 12: Mated Application Subsystem Features.......................................................................102Table 13: EAGLE 5 ISS Changing a Mated Application Procedures.........................................104Table 14: SEAS and EAGLE 5 ISS Global Title Translation Parameter Conversion................106Table 15: SEAS and EAGLE 5 ISS Global Title Translation Parameter Conversion................116Table 16: Gateway Linkset Supplier Specific Parameters...........................................................230Table 17: Gateway Linkset Supplier Specific Parameters...........................................................241Table 18: Mated Application Subsystem Features.......................................................................262Table 19: EAGLE 5 ISS Changing a Mated Application Procedures.........................................264Table 20: SEAS and EAGLE 5 ISS Global Title Address Information Parameter

Conversion...................................................................................................................................266Table 21: SEAS and EAGLE 5 ISS Global Title Address Information Parameter

Conversion...................................................................................................................................278Table 22: Section 4. Message Headers and UPL/Lower-Layer Interactions............................291Table 23: Section 5. UPL Interactions and Message Syntax Requirements...............................293Table 24: Section 6. Data Collection Messages..............................................................................294Table 25: Section 7. Recent Change and Verify (RC&V) Messages............................................295Table 26: Section 8. On-Occurrence Autonomous Messages......................................................317Table 27: Section 9. STP Application Control Commands..........................................................323Table 28: Section 10. Transparent Mode (Flow-Through) Messages.........................................324Table 29: Section 11. Performance and Capacity..........................................................................325Table 30: Section 12. Message Priority and Routing....................................................................325Table 31: Section 13. Routing Verification Test Messages...........................................................326Table 32: Appendix A. Data Collection Request Structure.........................................................328Table 33: Appendix B. Standard Data Collection Schedules......................................................329Table 34: Section 3. Recent Change and Verify Gateway Messages..........................................357Table 35: Section 4. Gateway On-Occurrence Autonomous Messages.....................................366

vii910-6013-001 Revision A, March 2011

Table 36: Section 5. Gateway Application Control Messages.....................................................366Table 37: Section 6. STP Gateway Data Collection.......................................................................367Table 38: Section 8. Performance and Capacity Requirements..................................................370Table 39: Appendix B. Gateway Measurement Definitions and Standard Register

Labels............................................................................................................................................371

viii910-6013-001 Revision A, March 2011

Chapter

1Introduction

Chapter 1, Introduction, contains generalinformation about the database and the organizationof this manual.

Topics:

• Overview.....10• Scope and Audience.....13• Manual Organization.....14• Documentation Admonishments.....14• Customer Care Center.....15• Emergency Response.....17• Related Publications.....17• Documentation Availability, Packaging, and

Updates.....17• Locate Product Documentation on the Customer

Support Site.....18• Maintenance and Administration Subsystem....19• EAGLE 5 ISS Database Partitions.....20

9910-6013-001 Revision A, March 2011

Overview

The Database Administration Manual-SEAS describes the procedures that can be performed from theSignaling Engineering and Administration Center (SEAC) or a Signaling Network Control Center(SNCC) to configure the EAGLE 5 ISS. These procedures contain these items:

• A brief description of the procedure• A reference to the EAGLE 5 ISS procedure in either the Database Administration Manual - SS7,

Database Administration Manual - Gateway Screening, or Database Administration Manual - Global TitleTranslation that contains more information on that procedure.

• A flowchart showing the order that the tasks must be performed.• A list of any EAGLE 5 ISS command parameters that SEAS does not support.

It is possible for two or more users to make changes to the same database element at any time duringtheir database administration sessions. It is strongly recommended that only one user at a time makeany changes to the database.

For those tasks that are compatible with SEAS, the flowchart contains a description of the task to beperformed. For those tasks that are not compatible with SEAS, the flowchart uses the EAGLE 5 ISScommand and parameters with the SEAS FLOW-THRU command to describe the task to be performed.If more information on the EAGLE 5 ISS commands is needed, go to the Commands Manual to find therequired information.

Procedures that contain these requirements cannot be performed from the SEAS interface.

• Procedures that use a removable cartridge (with the MDAL card) or removable media (with theE5-MASP) cannot be performed from the SEAC or SNCC because the removable cartridge orremovable media can only be inserted or removed at the EAGLE 5 ISS’s location.

• Procedures that require using security administration commands because the EAGLE 5 ISS doesnot allow security administration commands to be executed from the SEAS interface.

• Procedures that require SEAS terminals to be placed out of service. This would not allow the SEASinterface to communicate with the EAGLE 5 ISS, so these procedures cannot be performed fromthe SEAS interface.

• Procedures that use EAGLE 5 ISS commands that have no SEAS equivalent commands to performall the steps in the procedure, or that reference other procedures not included in this manual. Toperform these procedures, go to either the Database Administration Manual - SS7, DatabaseAdministration Manual - Gateway Screening, or Database Administration Manual - Global Title Translationand perform these procedures using the SEAS FLOW-THRU command with the EAGLE 5 ISScommands.

The following is a list of the procedures contained in the Database Administration Manual - SS7, DatabaseAdministration Manual - Gateway Screening, or Database Administration Manual - Global Title Translationthat are not included in this manual because they cannot be performed using SEAS commands.

Database Administration Manual - SS7

• These procedures in Chapter 2, “Configuring Destination Tables”

• Changing the DPC Quantity• Changing the Format of ITU National Point Codes• Activating the ITU National and International Spare Point Code Support Feature• Adding a Point Code to the Self-Identification of the EAGLE 5 ISS

10910-6013-001 Revision A, March 2011

IntroductionDatabase Administration Manual - SEAS

• Adding a Secondary Point Code• Removing a Secondary Point Code• Changing the Group Code Assigned to an ITU National Point Code• Changing the Proxy Point Code Quantity

• These procedures in Chapter 3, “SS7 Configuration”

• Enabling the Large System # Links Controlled Feature• Using Proxy Point Codes and Secondary Point Codes when Adding a Linkset• Activating the SLS Bit Rotation by Incoming Linkset Feature• Verifying the New Adjacent Point Code or New Secondary Point Code for a Linkset• Using the MULTGC Parameter when Changing the Attributes of a Linkset• Configuring an ITU Linkset with a Secondary Adjacent Point Code (SAPC)• Removing a Route• Changing Level 2 Timers• Changing Level 3 Timers• Changing a Signaling Link Test Message• Configuring Circular Route Detection• Configuring the TFA/TFR Pacing Rate• Configuring the Frequency of RST Messages on Low Priority Routes• Adding Remote Loopback Points• Removing Remote Loopback Points• Changing Remote Loopback Points• Configuring the EAGLE 5 ISS for Random SLS Generation• Configuring the Options for the TDM Global Timing Interface• Configuring the Restricted Linkset Option• Configuring the Options for Handling TFCs on ITU-I and ITU-N Networks• Changing the High-Capacity Card Temperature Alarm Thresholds• Activating the MTP Origin-Based Routing Feature• Configuring the MTP Origin-Based Routing SCCP OPC Option• Adding an Exception Route Entry• Removing a Route Exception Entry• Changing a Route Exception Entry• Activating the Circular Route Auto-Recovery Feature• Turning the Circular Route Auto-Recovery Feature Off• Activating the Enhanced Far-End Loopback Detection Feature• Turning the Enhanced Far-End Loopback Detection Feature Off• Activating the Multiple Linksets to Single Adjacent PC (MLS) Feature• Configuring the ITU Linkset NI Mapping Options• Configuring the Option for Handling Message Priorities for Messages Crossing into ITU-I and

ITU-N• Activating the 6-Way Load Sharing on Routesets Feature

• All the procedures in Chapter 4, “Point Code and CIC Translation Configuration.”• All the procedures in Appendix A, “E1 Interface.”• All the procedures in Appendix B, “T1 Interface,” except the “Adding a T1Signaling Link,”

procedure. The procedure for configuring T1 signaling links is included in the Adding an SS7Signaling Link procedure.

11910-6013-001 Revision A, March 2011


• All the procedures in Appendix C, “ATM Signaling Link Configuration,” except the “Adding anATM High-Speed Signaling Link,” procedure. This procedure issued to configure both ANSIATMand E1 ATM high-speed signaling links. The procedure for configuring ANSI ATM High-Speedsignaling links is included in the Adding an SS7 Signaling Link procedure. The EAGLE 5 ISS canalso have E1 ATM High-Speed signaling links. The configuration of these signaling links is notsupported by SEAS.

Database Administration Manual - Gateway Screening

• These procedures in Chapter 2, “Gateway Screening (GWS) Overview”

• Adding a GLS Card• Removing a GLS Card• Configuring Gateway Screening Stop Action Sets• Configuring TLNP Gateway Screening Stop Action Sets• Removing Gateway Screening Stop Action Sets• Activating the MTP Routed GWS Stop Action Feature• Turning the MTP Routed GWS Stop Action Feature Off

• All the procedures in Chapter 13, “Screen Set Configuration”• All the procedures in Chapter 14, “Calling Name Conversion Facility (CNCF) Configuration”

Database Administration Manual - Global Title Translation

• These procedures in Chapter 2, “Global Title Translation (GTT) Overview”

• Adding a Service Module• Removing a Service Module• Adding a Mapped SS7 Message Translation Type• Removing a Mapped SS7 Message Translation Type• Changing a Mapped SS7 Message Translation Type• Adding a Concerned Signaling Point Code• Removing Concerned Signaling Point Codes• Provisioning a Solitary Mated Application• Provisioning a Load Shared Mated Application• Provisioning a Combined Dominant/Load Shared Mated Application• Changing the Mated Application Type• Changing the Weight and In-Service Threshold Values of a Mated Application• Changing the MRNSET and MRN Point Code Values of MAP Entries• Provisioning MRN Entries• Removing MRN Entries• Changing the Relative Cost Values of MRN Entries• Changing MRN Entries with the ESWT Parameter• Changing the Weight and Threshold Values of MRN Entries• Adding a GT Conversion Table Entry• Removing a GT Conversion Table Entry• Changing a GT Conversion Table Entry• Changing the ANSI/ITU SCCP Conversion Options• Changing SCCP Class 1 Sequencing Option• Changing the SCCP Alarm Thresholds

12910-6013-001 Revision A, March 2011


• Changing the Transaction-Based GTT Load Sharing Options• Adding a Loopset• Removing a Loopset• Changing the Attributes of a Loopset• Configuring the ANSI to ITU-N SCCP Conversion Option• Configuring an SCCP Test Message• Adding Global Title Modification Information• Removing Global Title Modification Information• Changing Global Title Modification Information

• These procedures in Chapter 3, “Global Title Translation (GTT) Configuration”

• Adding a Translation Type• Removing a Translation Type

• These procedures in Chapter 4, “Enhanced Global Title Translation (EGTT) Configuration”

• Adding a GTT Set• Removing a GTT Set• Changing a GTT Set• Adding a GTT Selector• Removing a GTT Selector• Changing a GTT Selector• Changing the Default GTT Mode Options• Adding a GTT Action• Removing a GTT Action• Changing a GTT Action• Adding a GTT Action Set• Removing a GTT Action Set• Changing a GTT Action Set• Adding a GTT Action Path• Removing a GTT Action Path• Changing a GTT Action Path

• All the procedures in Appendix A, “Controlled Feature Activation Procedures”• All the procedures in Appendix B, “MO SMS B-Party Routing Configuration Procedures"• All the procedures in Appendix C, “MO SMS Prepaid Intercept on B-Party ConfigurationProcedures"

Scope and Audience

This manual is intended for database administration personnel or translations personnel in the SignalingEngineering and Administration Center (SEAC) or the Signaling Network Control Center (SNCC) tocreate, modify, display, and maintain the EAGLE 5 ISS database, and to configure the EAGLE 5 ISS.

13910-6013-001 Revision A, March 2011


Manual Organization

Throughout this document, the terms “database” and “system software” are used. Database refers toall data that can be administered by the user, including shelves, cards, links, routes, global titletranslation tables, and gateway screening tables. System software refers to data that cannot beadministered by the user, including generic program loads (GPLs).

This document is organized into the following sections.

Introduction contains general information about the database and the organization of this manual.

Configuring Destination Tables describes the methods for configuring destination point codes (DPCs)in the database of the EAGLE 5 ISS.

SS7 Configuration describes the procedures necessary to configure the EAGLE 5 ISS to support the SS7network.

Global Title Translation (GTT) Configuration describes the procedures used to administer global titletranslation data.

Gateway Screening (GWS) Configuration describes the procedures used to administer gateway screeningdata.

Enhanced Global Title Translation (EGTT) Configuration describes the procedures used to administer thedata required for the enhanced global title translation feature.

EAGLE 5 ISS/SEAS Compliance Matrix shows how the EAGLE 5 ISS complies with the specificationsfor SEAS as defined in the SEAS-STP Interface Specification, GR-310-CORE, Issue 1, November 1994 andthe SEAS-STP Gateway Function Interface Specification, GR-778-CORE, Issue 1, November 1994.

Documentation Admonishments

Admonishments are icons and text throughout this manual that alert the reader to assure personalsafety, to minimize possible service interruptions, and to warn of the potential for equipment damage.

Table 1: Admonishments

DANGER:

(This icon and text indicate the possibility of personal injury.)

WARNING:

(This icon and text indicate the possibility of equipment damage.)

CAUTION:

(This icon and text indicate the possibility of service interruption.)

14910-6013-001 Revision A, March 2011


Customer Care Center

The Tekelec Customer Care Center is your initial point of contact for all product support needs. Arepresentative takes your call or email, creates a Customer Service Request (CSR) and directs yourrequests to the Tekelec Technical Assistance Center (TAC). Each CSR includes an individual trackingnumber. Together with TAC Engineers, the representative will help you resolve your request.

The Customer Care Center is available 24 hours a day, 7 days a week, 365 days a year, and is linkedto TAC Engineers around the globe.

Tekelec TAC Engineers are available to provide solutions to your technical questions and issues 7days a week, 24 hours a day. After a CSR is issued, the TAC Engineer determines the classification ofthe trouble. If a critical problem exists, emergency procedures are initiated. If the problem is not critical,normal support procedures apply. A primary Technical Engineer is assigned to work on the CSR andprovide a solution to the problem. The CSR is closed when the problem is resolved.

Tekelec Technical Assistance Centers are located around the globe in the following locations:

Tekelec - Global

Email (All Regions): [email protected]

• USA and Canada

Phone:

1-888-FOR-TKLC or 1-888-367-8552 (toll-free, within continental USA and Canada)

1-919-460-2150 (outside continental USA and Canada)

TAC Regional Support Office Hours:

8:00 a.m. through 5:00 p.m. (GMT minus 5 hours), Monday through Friday, excluding holidays• Central and Latin America (CALA)

Phone:

USA access code +1-800-658-5454, then 1-888-FOR-TKLC or 1-888-367-8552 (toll-free)

TAC Regional Support Office Hours (except Brazil):

10:00 a.m. through 7:00 p.m. (GMT minus 6 hours), Monday through Friday, excluding holidays

• Argentina

Phone:

0-800-555-5246 (toll-free)• Brazil

Phone:

0-800-891-4341 (toll-free)


8:30 a.m. through 6:30 p.m. (GMT minus 3 hours), Monday through Friday, excluding holidays• Chile

15910-6013-001 Revision A, March 2011


Phone:

1230-020-555-5468• Colombia

Phone:

01-800-912-0537• Dominican Republic

Phone:

1-888-367-8552• Mexico

Phone:

001-888-367-8552• Peru

Phone:

0800-53-087• Puerto Rico

Phone:

1-888-367-8552 (1-888-FOR-TKLC)• Venezuela

Phone:

0800-176-6497

• Europe, Middle East, and Africa

Regional Office Hours:

8:30 a.m. through 5:00 p.m. (GMT), Monday through Friday, excluding holidays

• Signaling

Phone:

+44 1784 467 804 (within UK)• Software Solutions

Phone:

+33 3 89 33 54 00

• Asia

• India

Phone:

+91 124 436 8552 or +91 124 436 8553


16910-6013-001 Revision A, March 2011


10:00 a.m. through 7:00 p.m. (GMT plus 5 1/2 hours), Monday through Saturday, excludingholidays

• Singapore

Phone:

+65 6796 2288


9:00 a.m. through 6:00 p.m. (GMT plus 8 hours), Monday through Friday, excluding holidays

Emergency Response

In the event of a critical service situation, emergency response is offered by the Tekelec Customer CareCenter 24 hours a day, 7 days a week. The emergency response provides immediate coverage, automaticescalation, and other features to ensure that the critical situation is resolved as rapidly as possible.

A critical situation is defined as a problem that severely affects service, traffic, or maintenancecapabilities, and requires immediate corrective action. Critical problems affect service and/or systemoperation resulting in:

• A total system failure that results in loss of all transaction processing capability• Significant reduction in system capacity or traffic handling capability• Loss of the system’s ability to perform automatic system reconfiguration• Inability to restart a processor or the system• Corruption of system databases that requires service affecting corrective actions• Loss of access for maintenance or recovery operations• Loss of the system ability to provide any required critical or major trouble notification

Any other problem severely affecting service, capacity/traffic, billing, and maintenance capabilitiesmay be defined as critical by prior discussion and agreement with the Tekelec Customer Care Center.

Related Publications

For information about additional publications that are related to this document, refer to the RelatedPublications document. The Related Publications document is published as a part of the ReleaseDocumentation and is also published as a separate document on the Tekelec Customer Support Site.

Documentation Availability, Packaging, and Updates

Tekelec provides documentation with each system and in accordance with contractual agreements.For General Availability (GA) releases, Tekelec publishes a complete EAGLE 5 ISS documentation set.

17910-6013-001 Revision A, March 2011


For Limited Availability (LA) releases, Tekelec may publish a documentation subset tailored to specificfeature content or hardware requirements. Documentation Bulletins announce a new or updatedrelease.

The Tekelec EAGLE 5 ISS documentation set is released on an optical disc. This format allows for easysearches through all parts of the documentation set.

The electronic file of each manual is also available from the Tekelec Customer Support site. This siteallows for 24-hour access to the most up-to-date documentation, including the latest versions of FeatureNotices.

Printed documentation is available for GA releases on request only and with a lead time of six weeks.The printed documentation set includes pocket guides for commands and alarms. Pocket guides mayalso be ordered separately. Exceptions to printed documentation are:

• Hardware or Installation manuals are printed without the linked attachments found in the electronicversion of the manuals.

• The Release Notice is available only on the Customer Support site.

Note: Customers may print a reasonable number of each manual for their own use.

Documentation is updated when significant changes are made that affect system operation. Updatesresulting from Severity 1 and 2 Problem Reports (PRs) are made to existing manuals. Other changesare included in the documentation for the next scheduled release. Updates are made by re-issuing anelectronic file to the customer support site. Customers with printed documentation should contacttheir Sales Representative for an addendum. Occasionally, changes are communicated first with aDocumentation Bulletin to provide customers with an advanced notice of the issue until officiallyreleased in the documentation. Documentation Bulletins are posted on the Customer Support site andcan be viewed per product and release.

Locate Product Documentation on the Customer Support Site

Access to Tekelec's Customer Support site is restricted to current Tekelec customers only. This sectiondescribes how to log into the Tekelec Customer Support site and locate a document. Viewing thedocument requires Adobe Acrobat Reader, which can be downloaded at www.adobe.com.

1. Log into the Tekelec Customer Support site.

Note: If you have not registered for this new site, click the Register Here link. Have your customernumber available. The response time for registration requests is 24 to 48 hours.

2. Click the Product Support tab.3. Use the Search field to locate a document by its part number, release number, document name, or

document type. The Search field accepts both full and partial entries.4. Click a subject folder to browse through a list of related files.5. To download a file to your location, right-click the file name and select Save Target As.

18910-6013-001 Revision A, March 2011


https://secure.tekelec.com/OA_HTML/ibuhpage.jsp

https://secure.tekelec.com/OA_HTML/ibuhpage.jsp

Maintenance and Administration Subsystem

The Maintenance and Administration Subsystem (MAS) is the central management point for theEAGLE 5 ISS. The MAS provides user interface, maintenance communication, peripheral services,alarm processing, system disk interface, and measurements. Management and redundancy are providedby use of two separate subsystem processors.

The MAS resides on two separate sets of Maintenance and Administration Subsystem Processor(MASP) cards and a Maintenance Disk and Alarm card (collectively referred to as control cards). Thecontrol cards are located in slots 1113 through 1118 of the EAGLE 5 ISS control shelf. The control cardscan be either E5-based cards or legacy cards.

Note: In normal operation, the E5-based control cards and the legacy control cards cannot be mixedin one EAGLE 5 ISS control shelf.

Legacy Control Cards

The legacy set of EAGLE 5 ISS control cards consists of the following cards:

• Two MASP card sets; each set contains the following two cards:

• A General Purpose Service Module II (GPSM-II) card• A Terminal Disk Module (TDM) card

• One Maintenance Disk and Alarm (MDAL) card

General Purpose Service Module II (GPSM-II) Card

Each GPSM-II card contains the Communications Processor and the Applications Processor andprovides connections to the IMT bus. The card controls the maintenance and database administrationactivity and performs both application and communication processing. GPSM-II cards are located inslots 1113 and 1115 of the control shelf.

Terminal Disk Module (TDM) Card

Each TDM card provides the Terminal Processor for the 16 I/O ports, and interfaces to the MaintenanceDisk and Alarm (MDAL) card. The TDM card also distributes Composite Clocks and High SpeedMaster clocks throughout the EAGLE 5 ISS, and distributes Shelf ID to the EAGLE 5 ISS. Each TDMcard contains one fixed disk drive that is used to store primary and backup system databases,measurements, and Generic Program Loads (GPLs). The TDM cards are located in slots 1114 and 1116of the control shelf.

Maintenance Disk and Alarm (MDAL) Card

The MDAL card processes alarm requests and provides fan control. There is only one MDAL card ina control card set. Critical, major, and minor system alarms are provided for up to 6 individual frames.In addition to the 3 system alarms, the MDAL card provides the system audible alarm. The MDALcard provides control of fans on a per-frame basis and allows for each fan relay to be set individually.The MDAL card contains a removable cartridge drive; the removable cartridge is used for installingnew software; backing up the system software, the application software, and the database; and fordownloading data for off-line processing. The MDAL card is located in slots 1117 and 1118 of thecontrol shelf.

19910-6013-001 Revision A, March 2011


E5-based Control Cards

The E5-based set of EAGLE 5 ISS control cards consists of the following cards:

• Two Maintenance and Administration Subsystem Processor cards (E5-MASP) cards. Each dual-slotE5-MASP card is made up of the following two modules:

• Maintenance Communication Application Processor (E5-MCAP) card• Terminal Disk Module (E5-TDM) card

• One Maintenance Disk and Alarm card (E5-MDAL card)

Maintenance Communication Application Processor (E5-MCAP) Card

The E5-MCAP card contains the Communications Processor and Applications Processor and providesconnections to the IMT bus. The card controls the maintenance and database administration activityand performs both application and communication processing. E5-MCAP cards are located in slots1113 and 1115 of the control shelf.

Each E5-MCAP card contains two USB ports. One latched USB port is used with removable flashmedia (“thumb drives”), and one flush-mounted USB port is used with a plug-in “credit card” flashdrive. The removable media drive is used to install and back up customer data. The credit card driveis used for upgrade and could be used for disaster recovery.

Terminal Disk Module (E5-TDM) Card

The E5-TDM card provides the Terminal Processor for the 16 I/O ports, and interfaces to theMaintenance Disk and Alarm (E5-MDAL) card and fixed disk storage. The E5-TDM card also distributesComposite Clocks and High Speed Master clocks throughout the EAGLE 5 ISS, and distributes ShelfID to the EAGLE 5 ISS. Each E5-TDM card contains one fixed SATA drive that is used to store primaryand backup system databases, measurements, and Generic Program Loads (GPLs). E5-TDM cards arelocated in slots 1114 and 1116 of the control shelf.

Maintenance Disk and Alarm (E5-MDAL) Card

The E5-MDAL card processes alarm requests and provides fan control. There is only one E5-MDALcard in a control card set. Critical, major, and minor system alarms are provided for up to 6 individualframes. In addition to the 3 system alarms, the E5-MDAL card provides the system audible alarm.The E5-MDAL card provides control of fans on a per-frame basis, and allows for each fan relay to beset individually. The E5-MDAL card does not contain a removable cartridge drive; drives for removablemedia are located on the E5-MCAP card. The E5-MDAL card is located in slots 1117 and 1118 of thecontrol shelf.

EAGLE 5 ISS Database Partitions

The data that the EAGLE 5 ISS uses to perform its functions are stored in two separate areas: the fixeddisk drives, and the removable cartridge. The following sections describe these areas and data that isstored on them. These areas and their partitions are shown in Figure 1: EAGLE 5 ISS Database Partitions(Legacy Control Cards) and Figure 2: EAGLE 5 ISS Database Partitions (E5-Based Control Cards).

20910-6013-001 Revision A, March 2011


Figure 1: EAGLE 5 ISS Database Partitions (Legacy Control Cards)

21910-6013-001 Revision A, March 2011


Figure 2: EAGLE 5 ISS Database Partitions (E5-Based Control Cards)

Fixed Disk Drive

There are two fixed disk drives on the EAGLE 5 ISS. The fixed disk drives contain the “master” set ofdata and programs for the EAGLE 5 ISS. The two fixed disk drives are located on the terminal diskmodules (TDMs). Both disks have the same files. The data stored on the fixed disks is partially replicatedon the various cards in the EAGLE 5 ISS. Changes made during database administration sessions aresent to the appropriate cards.

The data on the fixed disks can be viewed as four partitions.

• Current partition

22910-6013-001 Revision A, March 2011


• Backup partition• Measurements partition• Generic program loads (GPLs) partition

The data which can be administered by users is stored in two partitions on the fixed disk, a currentdatabase partition which has the tables which are changed by on-line administration, and a backupdatabase partition which is a user-controlled copy of the current partition.

All of the on-line data administration commands effect the data in the current partition. The purposeof the backup partition is to provide the users with a means of rapidly restoring the database to aknown good state if there has been a problem while changing the current partition.

A full set of GPLs is stored on the fixed disk, in the GPL partition. There is an approved GPL and atrial GPL for each type of GPL in this set and a utility GPL, which has only an approved version.Copies of these GPLs are downloaded to the EAGLE 5 ISS cards. The GPL provides each card withits functionality. For example, the ss7ansiGPL provides MTP functionality for link interface modules(LIMs).

Measurement tables are organized as a single partition on the fixed disk. These tables are used asholding areas for the measurement counts.

Removable Cartridge or Removable Media

The removable cartridge is used with the legacy MDAL control card in card location 1117. Theremovable media is used with the E5-MCAP card portion of the E5-MASP in card locations 1113 and1115.

The removable cartridge or removable media is used for two purposes.

• To hold an off-line backup copy of the administered data and system GPLs• To hold a copy of the measurement tables

Because of the size of the data stored on the fixed disk drives on the TDMs, a single removable cartridgeor removable media cannot store all of the data in the database, GPL and measurements partitions.

To use a removable cartridge or removable media to hold the system data, it must be formatted forsystem data. To use a removable cartridge or removable media to hold measurements data, it mustbe formatted for measurements data. The EAGLE 5 ISS provides the user the ability to format aremovable cartridge or removable media for either of these purposes. A removable cartridge orremovable media can be formatted on the EAGLE 5 ISS by using the format-disk command. Moreinformation on the format-disk command can be found in the Commands Manual. More informationon the removable cartridge or removable media drives can be found in the Hardware Manual - EAGLE5 ISS.

Additional and preformatted removable cartridges or removable media are available from the CustomerCare Center.

23910-6013-001 Revision A, March 2011


Chapter

2Configuring Destination Tables

Chapter 2, Configuring Destination Tables, describesthe methods for configuring destination point codes(DPCs) in the database of the EAGLE 5 ISS.

Topics:

• Adding a Cluster Point Code.....25• Changing the Attributes of a Cluster Point

Code.....29• Adding a Network Routing Point Code.....33• Changing the Self Identification of the EAGLE 5

ISS.....36• Adding a Destination Point Code.....42• Removing a Destination Point Code.....45• Changing a Destination Point Code.....48

24910-6013-001 Revision A, March 2011

Adding a Cluster Point Code

This procedure is used to add a cluster point code for the cluster routing and management diversityfeature to the database. This procedure uses the EAGLE 5 ISS commands rtrv-feat, chg-feat,rtrv-stpopts, chg-stpopts, rtrv-ctrl-feat, rtrv-dstn, and chg-db. For more informationon this procedure, see “Adding a Cluster Point Code” in the Database Administration Manual – SS7.

Note: Once the cluster routing and management diversity and nested cluster routing features areturned on with the chg-feat command, they cannot be turned off.

The cluster routing and management diversity and nested cluster routing features must be purchasedbefore you turn the features on with the chg-feat command. If you are not sure whether you havepurchased the cluster routing and management diversity and nested cluster routing features, contactyour Tekelec Sales Representative or Account Representative.

Note: A cluster point code cannot be a proxy point code.

If you wish to use the following parameters of the EAGLE 5 ISS’s ent-dstn command: nprst,rcause, sccpmsgcnv, or splitiam parameters, perform the “Adding a Cluster Point Code”procedure in the Database Administration Manual - SS7 using the SEAS FLOW-THRU command with theEAGLE 5 ISS commands.

The EAGLE 5 ISS accepts the values for the ncai parameter as a supplier specific parameters. Table2: NCAI Supplier Specific Parameter Values shows how the EAGLE 5 ISS ncai parameter values aremapped to the SEAS values. For more information on the ncai parameter, see “Adding a ClusterPoint Code” in the Database Administration Manual – SS7 .

Table 2: NCAI Supplier Specific Parameter Values

DefinitionSEASParameter

Value

EAGLE 5ISS

ParameterValue

SupplierSpecific

Parameters

The nested cluster allowed indicator. This parameterspecifies whether or not the route to the cluster point code

1

0

YES

NO

NCAI

can be different from the route to a point code that is amember of the cluster point code.

The supplier specific parameter is optional. The default value for the supplier specific parameter willbe entered if that parameter is not specified when adding a cluster point code. The default value forthe NCAI parameter is NO.

To change the attributes of an existing cluster point code, perform the Changing the Attributes of aCluster Point Code procedure.

To remove a cluster point code from the database, perform the Removing a Destination Point Codeprocedure.

Note: Before executing this procedure, make sure you have purchased the cluster routing andmanagement diversity and nested cluster routing features. If you are not sure if you have purchased

25910-6013-001 Revision A, March 2011

Configuring Destination TablesDatabase Administration Manual - SEAS

the cluster routing and management diversity or nested cluster routing features, contact your TekelecSales Representative or Account Representative.

Enter theFLOW-THRU::::::"chg-feat:crmd=on";

command

ToSheet 2

Enter theFLOW-THRU::::::"rtrv-feat";

command

Is the Cluster Routingand Management Diversity

feature on?

Are nestedcluster point codesbeing configured?

Is the NestedCluster Routing

feature on?

Enter theFLOW-THRU::::::"chg-feat:ncr=on";

command

Yes

Yes

Yes

No

No

No

Sheet 1 of 4Figure 3: Adding a Cluster Point Code from the SEAS Terminal

26910-6013-001 Revision A, March 2011


ToSheet 3

FromSheet 1

Enter theFLOW-THRU::::::"rtrv-dstn";

command

Will the addition of thecluster DPC increase the number ofDPCs the EAGLE 5 ISS can have

beyond the current capacity?

What is the sum of theDESTINATION ENTRIES

ALLOWED and X-LIST ENTRIESALLOWED values shown in the

rtrv-dstn output?

Less than10,500

10,500

Yes

No

Perform the "Changing theDPC Quantity" procedure inthe Database AdministrationManual - SS7 to change thenumber of DPCs allowed in

the system

Perform one of these procedures:"Removing a Destination Point Code"procedure in this chapter to remove a

DPC“Removing a Route Exception Entry”

procedure in the DatabaseAdministration Manual - SS7, with the

SEAS FLOW-THRU command, toremove an exception route.

Sheet 2 of 4

27910-6013-001 Revision A, March 2011


ToSheet 4

No

FromSheet 2

Is the clusterDPC in thedatabase?

Yes Select anothercluster DPC to add

to the database

Will the EAGLE5 ISS maintain a dynamic

exception list for the clusterDPC?

Add the cluster point code tothe database with the ELEIparameter equal to NO and

the supplier specificparameter ncai equal to 0

Add the cluster point code tothe database with the ELEI

parameter equal to YES andthe supplier specific

parameter ncai equal to 0

Yes

No

Is the cluster pointcode to be a nestedcluster point code?

Yes

No

Will the EAGLE5 ISS maintain a dynamic

exception list for the clusterDPC?

Add the cluster point code tothe database with the ELEIparameter equal to NO and

the supplier specificparameter ncai equal to 1

Add the cluster point codeto the database with theELEI parameter equal to

YES and the supplierspecific parameter ncai

equal to 1

Yes

No

Sheet 3 of 4

28910-6013-001 Revision A, March 2011


FromSheet 3

Verify that the cluster point codehas been added to the database

Enter theFLOW-THRU::::::"chg-db:action=backup

:dest=fixed"; command

Do you wish tochange the exception list

parameters?

Yes

No

Enter theFLOW-THRU::::::"chg-stpopts";

command with at least one of theseparameters:

mtplxq=<See Notes>mtpxlet=<0020 - 2400>

mtpxlot=<0 - 100>mtpdpcq=<See Notes>

Enter theFLOW-THRU::::::"rtrv-stpopts";

command


command

Notes:

1. The sum of the values for the mtpdpcq and mtpxlq parameters cannot exceed these values,depending which routeset quantity has been enabled with the EAGLE 5 ISS's enable-ctrl-featcommand, or turned on with the EAGLE 5 ISS's chg-feat command:

5000 routes is not turned on, 6000, 7000, 8000, or 10,000 routesets is not enabled - 2500. Therange of values for the mtpdpcq and mtpxlq parameters is 500 to 2000.

5000 routes is turned on, 6000, 7000, 8000, or 10,000 routesets is not enabled - 5500. The range ofvalues for the mtpdpcq and mtpxlq parameters is 500 to 5000.

6000 routesets are enabled - 6500. The range of values for the mtpdpcq and mtpxlq parameters is500 to 6000.

7000 routesets are enabled - 7500. The range of values for the mtpdpcq parameter is 500 to 7000.The range of values for the mtpxlq parameter is 500 to 6000.

8000 routesets are enabled - 8500. The range of values for the mtpdpcq parameter is 500 to 8000.The range of values for the mtpxlq parameter is 500 to 6000.

10,000 routesets are enabled - 10500. The range of values for the mtpdpcq and mtpxlq parametersis 500 to 10,000.

2. If the DPC quantity or the exception list quantity is being changed, both the mtpdpcq and mtpxlqparameters do not have to be specified unless the resulting sum of the mtpdpcq and mtpxlqparameters would exceed the totals shown in Note 1.

For example, the current mtpdpcq value is 4000 and the current mtpxlq value is 1500, resulting in asum of 5500, and only the 5000 Routes feature is on. To increase either value , both parameters mustbe specified and the sum of the new values cannot exceed 5500. If either value is being decreased,the other parameter can be specified as long as the sum of the values does not exceed 5500.

If in this example, the current mtpdpcq value is 3000 and the current mtpxlq value is 1500, resulting ina sum of 4500, either parameter value can be changed without specifying the other parameter as longas the sum of the values does not exceed 5500.

Sheet 4 of 4

Changing the Attributes of a Cluster Point Code

This procedure is used to change the attributes of a cluster point code for the cluster routing andmanagement diversity feature to the database. This procedure uses the EAGLE 5 ISS commandsrtrv-feat, chg-feat, and chg-db. For more information on this procedure, see “Changing theAttributes of a Cluster Point Code” in the Database Administration Manual – SS7.

29910-6013-001 Revision A, March 2011


Note: Once the nested cluster routing feature is turned on with the chg-feat command, it cannotbe turned off.

If you plan to use the supplier specific parameter ncai with this procedure, the nested cluster routingfeature must be purchased before you turn the feature on with the chg-feat command. If you arenot sure whether you have purchased the nested cluster routing feature, contact your Tekelec SalesRepresentative or Account Representative.

If you wish to use the following parameters of the EAGLE 5 ISS’s chg-dstn command: nprst,rcause, sccpmsgcnv, or splitiam parameters, perform the "Changing the Attributes of a ClusterPoint Code” procedure in the Database Administration Manual - SS7 using the SEAS FLOW-THRUcommand with the EAGLE 5 ISS commands.

The EAGLE 5 ISS accepts the values for the ncai parameter as a supplier specific parameters. Table3: NCAI Supplier Specific Parameter Values shows how the EAGLE 5 ISS ncai parameter values aremapped to the SEAS values. For more information on the ncai parameter, see “Changing the Attributesof a Cluster Point Code” in the Database Administration Manual – SS7.

Table 3: NCAI Supplier Specific Parameter Values


Value

EAGLE 5ISS

ParameterValue

SupplierSpecific

Parameters

The nested cluster allowed indicator. This parameterspecifies whether or not the route to the cluster point code

1

0

YES

NO

NCAI

can be different from the route to a point code that is amember of the cluster point code.

The supplier specific parameter is optional. The current value of any supplier specific parameter isnot changed if the supplier specific parameter is not specified.

To remove a cluster point code from the database, perform the Removing a Destination Point Codeprocedure.

Note: If you plan to use the supplier specific parameter ncai with this procedure, before executingthis procedure, make sure you have purchased the nested cluster routing feature. If you are not sureif you have purchased the nested cluster routing feature, contact your Tekelec Sales Representativeor Account Representative.

30910-6013-001 Revision A, March 2011


Display the DPCs inthe database

Display the selfidentification of the

EAGLE 5 ISS

Is the NCAIparameter value to

be changed?

Yes

No

ToSheet 2

Is the CLLI valuefor the cluster PC to be

changed?

Yes

No

Does the newCLLI value match any CLLIvalues shown in the DPC or

self ID outputs?

Choose a CLLI value thatdoes not match any CLLI

values shown in the DPC orself ID outputs

Yes

No

What is the currentvalue of the ELEI

parameter?



Change the cluster DPCwith the ELEI parameter

equal to NO

Verify that the clusterDPC was changed

Change the cluster DPCwith the ELEI parameter

equal to YES

No

Yes

Sheet 1 of 3Figure 4: Changing the Attributes of a Cluster Point Code from the SEAS Terminal

31910-6013-001 Revision A, March 2011


Display the routes inthe database

Yes

NoWhat is the currentvalue of the NCAI

parameter?

FromSheet 1

Does the clusterpoint code have any

member point codes in thedatabase?

Yes

Are the clusterpoint code and its member

point codes in the samerouteset?

Go to the "Removing a Route"procedure in the Database

Administration Manual - SS7 andremove the routes to the members

of the cluster point code

No

NoYes

ToSheet 3

Change the cluster DPC withthe ELEI parameter equal toNO and the and the supplierspecific parameter ncai equal

to 1



parameter?

Is the ELEIparameter value to be

changed?

Yes

No

No

Yes


to 0

Change the cluster DPC withthe supplier specific parameter

ncai equal to 0



Sheet 2 of 3

32910-6013-001 Revision A, March 2011


FromSheet 2

Change the cluster DPC withthe ELEI parameter equal toYES and the and the supplierspecific parameter ncai equal

to 1



parameter?

Is the ELEIparameter value to be

changed?

Yes

NoNo

Yes


to 1

Change the cluster DPC withthe supplier specific parameter

ncai equal to 1

Is the nestedcluster routing feature on

(NCR = on)?


command

Enter theFLOW-THRU::::::"chg-feat

:ncr=on"; command

Yes

No



Sheet 3 of 3

Adding a Network Routing Point Code

This procedure is used to add a network routing point code for the network routing feature to thedatabase. This procedure uses the EAGLE 5 ISS commands rtrv-feat, chg-feat, rtrv-dstn,rtrv-ctrl-feat, rtrv-sid, and chg-db. For more information on this procedure, see “Addinga Network Routing Point Code” in the Database Administration Manual – SS7.

Notes:

1. Once the network routing feature is turned on with the chg-feat command, it cannot be turnedoff.

33910-6013-001 Revision A, March 2011


The network routing feature must be purchased before you turn the features on with the chg-featcommand. If you are not sure whether you have purchased the network routing feature, contactyour Tekelec Sales Representative or Account Representative.

2. A network routing point code cannot be a proxy point code.

If you wish to use the following parameters of the EAGLE 5 ISS’s ent-dstn command: nprst,rcause, sccpmsgcnv, or splitiam parameters, perform the “Adding a Network Routing PointCode” procedure in the Database Administration Manual - SS7 using the SEAS FLOW-THRU commandwith the EAGLE 5 ISS commands.

To change the attributes of an existing network routing point code, perform the Changing a DestinationPoint Code procedure.

To remove a network routing point code from the database, perform the Removing a Destination PointCode procedure.

Note: Before executing this procedure, make sure you have purchased the network routing feature.If you are not sure if you have purchased the network routing feature, contact your Tekelec SalesRepresentative or Account Representative.

34910-6013-001 Revision A, March 2011


Enter theFLOW-THRU::::::"chg-feat:nrt=on";

command


command

Is the NetworkRouting feature on?

Yes

No


command

ToSheet 2

Will the addition of thenetwork routing DPC increase thenumber of DPCs the EAGLE 5 ISS

can have beyond thecurrent capacity?

What is the sum of theDESTINATION ENTRIES

ALLOWED and X-LIST ENTRIESALLOWED values shown in the

rtrv-dstn output?

Less than10,500

10,500

Yes No

Perform the "Changing theDPC Quantity" procedure inthe Database AdministrationManual - SS7 to change thenumber of DPCs allowed in

the system

Perform one of these procedures:"Removing a Destination Point Code"procedure in this chapter to remove a

DPC“Removing a Route Exception Entry”

procedure in the DatabaseAdministration Manual - SS7, with the

SEAS FLOW-THRU command, toremove an exception route.

Sheet 1 of 2Figure 5: Adding a Network Routing Point Code from the SEAS Terminal

35910-6013-001 Revision A, March 2011


Does the rtrv-dstnoutput show any network

routing point codes?

Yes

No

FromSheet 1

Do any of thenetwork routing point codeshave the network indicators

of 1 to 5?

Yes

No

Do you wish toconfigure network routingpoint codes that have the

network indicators of1 to 5?

No

Yes

What is thePCTYPE value?

Enter theFLOW-THRU::::::"rtrv-sid";

command

OTHER

ANSI

Go to the "Changing the Self Identificationof the EAGLE 5 ISS" procedure in the

Database Administration Manual - SS7 andchange the PCTYPE value to OTHER.

Verify that the network routingDPC has been added to the

database

Is the networkrouting DPC in the

database?

Select another networkrouting DPC to add to the

database

Add the network routingDPC to the database

Yes

No

Enter theFLOW-THRU:::::"chg-db:action=backup


Sheet 2 of 2

Changing the Self Identification of the EAGLE 5 ISS

This procedure is used to change the self identification of the EAGLE 5 ISS. For more information onthis procedure, see the “Changing the Self Identification of the EAGLE 5 ISS” procedure in the DatabaseAdministration Manual – SS7. This procedure uses these EAGLE 5 ISS commands.

36910-6013-001 Revision A, March 2011


rtrv-featrtrv-dstnrtrv-sidinit-sys

rtrv-stpoptschg-eiscopyrtrv-eiscopyrtrv-spc

rtrv-pctchg-dbrtrv-gws-redirectchg-stpopts

If you wish to use the cpctype, pctype, pci, pcn, or pcn24 parameters of the EAGLE 5 ISS’schg-sid command, perform the “Changing the Self Identification of the EAGLE 5 ISS” procedure inthe Database Administration Manual – SS7 using the SEAS FLOW-THRU command with the EAGLE 5ISS commands.

CAUTION: Use this procedure only during periods of low traffic. If the EAGLE 5 ISS’spoint code is changed with the procedure, the EAGLE 5 ISS must be reinitialized with theEAGLE 5 ISS’s init-sys command. The init-sys command reboots the entire EAGLE5 ISS and reloads all cards with the updated self identification information.

CAUTION: When the init-sys command executes, the state of the signaling links,TCP/IP data links, cards, and terminals after the init-sys command executes dependson whether the restore device state option is on or off. The value of this option is shownin the RSTRDEV field of the rtrv-stpopts output.

If the value of the restore device state option is off, the EAGLE 5 ISS does not retain themanually initiated state (for example, OOS-MT-DSBLD) for the signaling links, TCP/IPdata links, cards, or the terminals. After the command executes, the EAGLE 5 ISS attemptsto bring all provisioned links, cards, and terminals on line, including those that werepreviously out of service. You will need to manually put each device back into its previousstate after the EAGLE 5 ISS is back on line. It is, therefore, advisable to print or electronicallycapture the output of the EAGLE 5 ISS’s rept-stat-slk, rept-stat-dlk,rept-stat-card, and rept-stat-trm commands for reference prior to issuing theinit-sys command. To restore a device to its previous state, issue the appropriateinhibit/deactivate command listed in the Commands Manual in the Related Commandssection for each of the above rept-stat commands.

If the value of the restore device state option is on, the state the signaling links, TCP/IPdata links, cards, and terminals is not changed after the init-sys command is performed.No manual intervention is required to put the device back into its previous state after theEAGLE 5 ISS is back on line.

To change the value of the restore device state option, perform the “Changing the RestoreDevice State Option” procedure in the Database Administration Manual - System Management.

37910-6013-001 Revision A, March 2011


Enter theFLOW-THRU::::::"rtrv-sid";

command.

Do you wishto change the EAGLE 5

ISS’s point code?

Do you wishto change the EAGLE 5

ISS’s CLLI value?

Do you wish toadd a new capability

point code?

The new point code valuecannot be shown in the rtrv-dstnoutput or in the rtrv-spc output ifthe Multiple Point Code feature

is turned on. The new point codevalue cannot be shown as an

EPC value in the rtrv-pct output.

The new CLLI value cannot beshown in the rtrv-dstn output.

The new capability point codevalue cannot be shown in the

rtrv-dstn or rtrv-sid outputs, or inthe rtrv-spc output if the MultiplePoint Code feature is turned on.The new capability point codevalue cannot be shown as an

EPC value in the rtrv-pct output.

Yes

Yes

Yes

No

No

No


command.

ToSheet 2

Enter theFLOW-THRU::::::"rtrv-pct";

command.

Sheet 1 of 5Figure 6: Changing the Self Identification of the EAGLE 5 ISS from the SEAS Terminal

38910-6013-001 Revision A, March 2011


Is the GTT turnedon (GTT=on in thertrv-feat output)?

Yes

No

Display the matedapplications in the

database.

FromSheet 1

Is the EAGLE5 ISS’s point code

being changed or a newcapability point code

being added?


command.

Is theMultple Point Codefeature turned on

(MPC=on)?

No

Yes

Yes

Enter theFLOW-THRU::::::"rtrv-spc";

command.

Do any matedapplications reference the

EAGLE 5 ISS's pointcode?

Perform the "Removing a MatedApplication" procedure to remove anymated applications that reference the

EAGLE 5 ISS's point code.

Yes

No

ToSheet 3

No

Is the EAGLE5 ISS’s point codebeing changed?

Yes

No

Sheet 2 of 5

39910-6013-001 Revision A, March 2011


Is the E5ISfeature on?

Yes

No

ToSheet 4

Is the CLLIvalue to bechanged?

Was the rtrv-featcommand executed on

Sheet 2?

No

No

Yes

Yes

FromSheet 2


command.

Enter theFLOW-THRU::::::"rtrv-eisopts";

command.

What isthe EISCOPY

value?

Enter the FLOW-THRU::::::"chg-eisopts:eiscopy=off";

command.

On

Off

Change the self identificationof the EAGLE 5 ISS.

Yes

Enter the FLOW-THRU::::::"chg-eisopts:fcmode=off:fcgpl=all"; command.

NoIs the FCMODE

value for all the GPLsshown in the rtrv-eisopts

output off?

Sheet 3 of 5

40910-6013-001 Revision A, March 2011


FromSheet 3

Was the EAGLE5 ISS’s point code

changed or a new capabilitypoint code added?

Enter theFLOW-THRU::::::"init-sys";

command.This command must be entered

twice within 30 seconds.

Yes

No

ToSheet 5


command.

What is thecurrent RSTRDEV

value?

Do you wish tochange the restore previous

device states afterinit-sys setting?

OffOn

Enter theFLOW-THRU::::::"chg-stpopts

:off=rstrdev "; command.

Yes

No

Enter theFLOW-THRU::::::"chg-stpopts

:on=rstrdev "; command.

Sheet 4 of 5

41910-6013-001 Revision A, March 2011


Was the CLLIvalue changed?

Yes

No

Is the EAGLE 5ISS’s point code that

was shown in the rtrv-sidoutput on Sheet 1 shown in

the rtrv-gws-redirectoutput?

Perform the "Changing theGateway Screening RedirectParameters" procedure in the

Database AdministrationManual – Features to change

the DPC.

Yes

No

FromSheet 4

NoWas theEISCOPY option changed

on Sheet 3?

Yes

Perform the procedures in the“SEAS Over IP ConfigurationProcedures” chapter of the

Database Administration Manual –System Management to update the

CCSMR configuration.

Enter the FLOW-THRU::::::"rtrv-gws-redirect"; command.

Was theEAGLE 5 ISS’s point

code changed?

Yes

No

Verify that the selfidentification of the EAGLE5 ISS has been changed.


:dest=fixed"; command.

This procedure isfinished.

Enter the FLOW-THRU::::::"chg-eisopts"; command with these

parameters.

:fcmode=<value shown in thertrv-eisopts output on Sheet 3>

:fcgpl=<value shown in thertrv-eisopts output on Sheet 3>

Repeat this step for all the GPLsshown in the rtrv-eisopts output on

Sheet 3 as necessary.

Enter the FLOW-THRU::::::"chg-eisopts:eiscopy=on";

command.

Was theFCMODE option changed

on Sheet 3?

Yes

No

Sheet 5 of 5

Adding a Destination Point Code

This procedure is used to add a destination point code to the database. This procedure uses the EAGLE5 ISS commands rtrv-feat, rtrv-dstn, rtrv-ctrl-feat, and chg-db. For more informationon this procedure, see “Adding a Destination Point Code” in the Database Administration Manual –SS7.

If you wish to use the following parameters of the EAGLE 5 ISS’s ent-dstn command: dpci, dpcn,dpcn24, domain, aliasa, aliasi, aliasn, aliasn24, spc, spca, spci, spcn, spcn24, prx=yes,ppc, ppca, ppci, ppcn, ppcn24, nprst, rcause, splitiam, homesmsc, homescp, sccpmsgcnv,

42910-6013-001 Revision A, March 2011


or ipgwapc, or if spare point codes are being added, perform the “Adding a Destination Point Code”procedure in the Database Administration Manual - SS7 using the SEAS FLOW-THRU command with theEAGLE 5 ISS commands.

If you wish to use the ncai parameter the EAGLE 5 ISS’s ent-dstn command or configure a clusterpoint code, perform the Adding a Cluster Point Code procedure.

Display the self identificationof the EAGLE 5 ISS

ToSheet 2

Does the PC orCPC of the EAGLE 5ISS match the DPC

being added?

Yes

No

Choose a point code entrythat does not match the PC

or CPC of the EAGLE 5ISS

Does the CLLIof the EAGLE 5 ISS

match the CLLI beingadded?

Yes

No

Choose a CLLI entry thatdoes not match the CLLI of

the EAGLE 5 ISS


command

Sheet 1 of 3Figure 7: Adding a Destination Point Code from the SEAS Terminal

43910-6013-001 Revision A, March 2011


ToSheet 3

NoWill the additionof the point code exceed

the current capacity?

Yes

10,500

Less than10,500

Perform the "Changing theDPC Quantity" procedure inthe Database AdministrationManual - SS7 and change

the number of DPCs allowedin the EAGLE 5 ISS

Are the DESTINATIONENTRIES ALLOCATED and

the X-LIST ENTRIESALLOCATED fields shown in

the rtrv-dstn output?

What is thecurrent capacity shown

in the rtrv-dstnoutput?

Less than10,000

10,000

What is the sumof the DESTINATION

ENTRIES ALLOCATED andX-LIST ENTRIES

ALLOCATED values?

ToSheet 3

No

Yes

FromSheet 1

Perform one of theseprocedures:

"Removing a DestinationPoint Code" procedure inthis chapter to remove a

DPC“Removing a Route

Exception Entry” procedurein the Database

Administration Manual -SS7, with the SEAS FLOW-THRU command, to remove

an exception route.

Perform one of these procedures:"Removing a Destination Point Code" procedure

in this chapter to remove a DPC“Removing a Route Exception Entry” procedurein the Database Administration Manual - SS7,

with the SEAS FLOW-THRU command, toremove an exception route.

Sheet 2 of 3

44910-6013-001 Revision A, March 2011


Verify that the DPC hasbeen added to the

database

Do any existingDPCs match the DPC

being added?

Yes

No

Choose a DPC that doesnot match any existing

DPCs

Do the CLLIs ofany existing DPCs matchthe CLLI of the DPC being

added?

Yes

NoChoose a CLLI that does

not match the CLLIs of anyexisting DPCs

FromSheet 2

Add the DPC to thedatabase



Sheet 3 of 3

Removing a Destination Point Code

This procedure is used to remove a destination point code from the database. This procedure uses theEAGLE 5 ISS commands rtrv-dstn , rtrv-feat, rtrv-map, rtrv-mrn, rtrv-rmt-appl,rtrv-ctrl-feat, rtrv-rtx, and chg-db. For more information on this procedure, see “Removinga Destination Point Code” in the Database Administration Manual – SS7.

If you wish to remove an ITU international, ITU national destination point code, or a proxy point codefrom the database, perform the “Removing a Destination Point Code” procedure in the DatabaseAdministration Manual – SS7 using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

45910-6013-001 Revision A, March 2011


Display the DPCs inthe database.

Display the routes inthe database.

Are any routesassigned to the DPC

being removed?

Yes

No

Perform the "Removing aRoute" procedure, with the

SEAS FLOW-THRU command,in the Database AdministrationManual – SS7 to remove the

route containing the DPC.

Display the linksetsin the database.


command with this parameter.:dpc=<DPC being removed>

Is the DPCa proxy point

code?

Perform the "Removing aDestination Point Code" procedure

in the Database AdministrationManual – SS7, with the SEAS

FLOW-THRU command, to removethe DPC.

Yes

No

Is the DPCan APC of a

linkset?

No

Yes

Perform the "Removing aLinkset Containing SS7

Signaling Links" procedure toremove the linkset whose APC

is the DPC that is beingremoved.

ToSheet 2

Sheet 1 of 3Figure 8: Removing a Destination Point Code from the SEAS Terminal

46910-6013-001 Revision A, March 2011


FromSheet 1


command.

Is theGTT featureturned on?

No

Yes

Enter theFLOW-THRU::::::"rtrv-map";

command with this parameter.:pc/pca/pci/pcn/pcn24=<pointcode value being removed>

Are any entriesdisplayed?

Perform the "Removing aMated Application"

procedure to remove theentries that contain the DPC

that is being removed.

Yes

NoEnter the

FLOW-THRU::::::"rtrv-ctrl-feat";command with this parameter.

:partnum=893006901

Is the IGTTLSfeature on?

Yes

No

Enter theFLOW-THRU::::::"rtrv-mrn";

command with this parameter.:pc/pca/pci/pcn/pcn24=<pointcode value being removed>


Yes

No

Perform the "Removing anMRN Group or MRN Group

Entry" procedure in theDatabase Administration

Manual – Global TitleTranslation , with the SEASFLOW-THRU command, to

remove the entries thatcontain the DPC that is

being removed.

Enter theFLOW-THRU::::::"rtrv-rmt-appl";

command.

Is the DPCin the rtrv-rmt-appl

output?

Perform the "Removing anEnd Node Internal PointCode" procedure in theDatabase Administration

Manual – IP7 SecureGateway, with the SEAS

FLOW-THRU command, toremove the internal point

code.

Yes No

ToSheet 3

Sheet 2 of 3

47910-6013-001 Revision A, March 2011


FromSheet 2

Is the DPCa member of a cluster

point code?

Yes No


command with this parameter.:dpca=<cluster point code

shown in the previous rtrv-dstnoutput>

What is theNCAI value of

the cluster pointcode?

Enter theFLOW-THRU::::::"rtrv-rtx";

command with this parameter.:dpc/dpca=<point code value

being removed>


Perform the "Removing a Route Exception Entry"procedure in the Database Administration Manual –

SS7, with the SEAS FLOW-THRU command, toremove the exception route entries that are assigned

to the point code that is being removed.

Yes

No

Yes

No

Is theDPC an ANSIpoint code?

No

YesEnter the

FLOW-THRU::::::"rtrv-dstn";command with this parameter.

:dpca=<xxx-yyy-***>xxx is the network value of the

point code and yyy is the clustervalue of the point code.



Remove the DPC from thedatabase.

Verify that the DPC has beenremoved.

Sheet 3 of 3

Changing a Destination Point Code

This procedure is used to change a destination point code in the database. This procedure uses theEAGLE 5 ISS commands rtrv-dstn and chg-db. For more information on this procedure, see“Changing a Destination Point Code” in the Database Administration Manual – SS7.

48910-6013-001 Revision A, March 2011


If you wish to change the attributes of an ITU international, or ITU national destination point code(either a 14-bit ITU-N or 24-bit ITU-N point code), change the attributes of a proxy point code, or usethe ncai, alias, aliasa, aliasi, aliasn, aliasn24, spc, spca, spci, spcn, spcn24, nprst,rcause, splitiam, homesmsc, homescp, sccpmsgcnv, or prx=yes parameters of the EAGLE 5ISS’s chg-dstn command, perform the “Changing a Destination Point Code” procedure in the DatabaseAdministration Manual – SS7 using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

Display the DPCs inthe database

Display the self identificationof the EAGLE 5 ISS

Is the DPCbeing changed?

Yes

No

Go to the "Removing a DestinationPoint Code" procedure and remove

the destination point code

Go to the "Adding a DestinationPoint Code" procedure and add

the destination point code makingsure that the new DPC does notmatch the EAGLE 5 ISS's point

code or capability point code

Change theattributes of the DPC

Verify that the DPC'sattributes have been

changed



Enter theFLOW-THRU::::::"rtrv-dstn

:dpc=<DPC being changed>";command

Is the DPCa proxy point

code or is a proxy pointcode assigned to the

DPC?Perform the "Changing a

Destination Point Code" procedurein the Database Administration

Manual – SS7 to change the DPC.

YesNo

Figure 9: Changing a Destination Point Code from the SEAS Terminal

49910-6013-001 Revision A, March 2011


Chapter

3SS7 Configuration

Chapter 3, SS7 Configuration, describes theprocedures necessary to configure the EAGLE 5 ISSto support the SS7 network.

Topics:

• Adding an SS7 Linkset.....51• Removing a Linkset Containing SS7 Signaling

Links.....58• Changing an SS7 Linkset.....60• Adding an SS7 Signaling Link.....70• Removing an SS7 Signaling Link.....87• Adding a Route.....90• Changing a Route.....93

50910-6013-001 Revision A, March 2011

Adding an SS7 Linkset

This procedure is used to add an SS7 linkset to the database. This procedure uses the EAGLE 5 ISScommands rtrv-feat, chg-feat, chg-stpopts, rtrv-stpopts, and chg-db. For moreinformation on this procedure, see “Adding an SS7 Linkset” in the Database Administration Manual –SS7.

If you wish to use the apci, apcn, apcn24, scrn, gwsa, gwsd, slsocbit, slsrsb, l3tset, itutfr,multgc, gwsm, apcntype, spc, spca, spci, spcn, spcn24, ppc, ppca, ppci, ppcn, ppcn24,lst=prx, cggtmod, islsrsb, or randsls parameters of the EAGLE 5 ISS’s ent-ls command,perform the “Adding an SS7 Linkset” procedure in the Database Administration Manual – SS7 usingthe SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

This procedure cannot be used to provision a linkset whose adjacent point code is assigned to anotherlinkset. If you wish to use the adjacent point code of another linkset as the adjacent point code of thenew linkset, perform the “Adding an SS7 Linkset” procedure in the Database Administration Manual –SS7 using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

If you wish to use the iptps, lsusealm, ipgwapc, slkusealm, ipsg, adapter, asnotif,rcontext, or slktps parameters of the EAGLE 5 ISS’s ent-ls command, perform one of theseprocedures in the Database Administration Manual – IP

7 Secure Gateway using the SEAS FLOW-THRU

command with the EAGLE 5 ISS commands.

• Configuring an IPGWx Linkset• Adding an IPSG M3UA Linkset• Adding an IPSG M2PA Linkset

If you wish to use the gsmscrn parameter (for the GSM MAP Screening feature) of the EAGLE 5 ISS’sent-ls command, perform the “Configuring a Linkset for the GSM MAP Screening Feature” procedurein the Database Administration Manual - Features using the SEAS FLOW-THRU command with theEAGLE 5 ISS commands.

On the EAGLE 5 ISS, the linkset name can have a maximum of 10 characters. The SEAS interfacesupports a linkset name with a maximum of eight characters. Linkset names specified in this procedurecan have a maximum of eight characters. For linkset names provisioned on the EAGLE 5 ISS that havemore than eight characters, the SEAS interface truncates the linkset name to the first eight characterswhen that linkset name is displayed on the SEAS interface.

Supplier Specific Parameters

The EAGLE 5 ISS accepts the values for these parameters as supplier specific parameters: bei, slsci,asl8, sltset, nis, and mtprse. Table 4: Adding an SS7 Linkset Supplier Specific Parameters shows howthe values of these parameters are mapped to the SEAS values and a definition of each parameter. Formore information on these parameters, see “Adding an SS7 Linkset” in the Database AdministrationManual – SS7 .

51910-6013-001 Revision A, March 2011

SS7 ConfigurationDatabase Administration Manual - SEAS

Table 4: Adding an SS7 Linkset Supplier Specific Parameters


Value

EAGLE 5ISS

ParameterValue

SupplierSpecific

Parameters

The broadcast exception indicator. This parameter indicatesthat TFPs are allowed to be broadcast on the linkset or not

1

0

YES

NO

BEI

allowed to be broadcast on the linkset. This parameter istypically used to prevent TFPs from being broadcast toanother vendor’s system.

The parameter value 1 means TFPs are not broadcast onthe linkset. The parameter value 0 means TFPs are broadcaston the linkset.

The slsci parameter indicates that the 5-bit to 8-bit SLSconversion feature is enabled or not enabled. .

1

0

YES

NO

SLSCI

When the 5-bit to 8-bit SLS conversion feature is enabled(parameter value 1), the EAGLE 5 ISS replaces any five-bitSLS values contained in received messages with a random8-bit value before they are used by the EAGLE 5 ISS toselect the outgoing link in that link set.

When the 5-bit to 8-bit SLS conversion feature is not enabled(parameter value 0), the 5-bit to 8-bit SLS conversion is notperformed on messages in the linkset.

The asl8 parameter indicates that the node adjacent to theEAGLE 5 ISS is or is not sending MSUs with 8-bit SLSs.

1

0

YES

NO

ASL8

The parameter value 1 means the node adjacent to theEAGLE 5 ISS is sending MSUs with 8-bit SLSs. Theparameter value 0 means the node adjacent to the EAGLE5 ISS is not sending MSUs with 8-bit SLSs.

The signaling link test message record to be associated withthe linkset.

01-201-20SLTSET

The nis parameter indicates that the National Spare forNetwork Indicator feature is on or off for the specific

1

0

ON

OFF

NIS

linkset. This feature allows the linkset to use the nationalspare value (3) for the network indicator code field in theservice information octet (SIO) of the MSU for ANSI linksetsand ITU national linksets (linksets containing either 14-bitITU-N point codes or 24-bit ITU-N point codes). Thisparameter cannot be specified for ITU international linksets.

52910-6013-001 Revision A, March 2011



Value

EAGLE 5ISS

ParameterValue

SupplierSpecific

Parameters

The parameter value 1 means the National Spare forNetwork Indicator feature is on. The parameter value 0means the National Spare for Network Indicator feature isoff.

The mtprse parameter indicates that the node adjacent tothe EAGLE 5 ISS is or is not equipped with the MTP restartcapability.

1

0

YES

NO

MTPRSE

The parameter value 1 means the node adjacent to theEAGLE 5 ISS is equipped with the MTP restart capabilityThe parameter value 0 means the node adjacent to theEAGLE 5 ISS is not equipped with the MTP restartcapability.

The supplier specific parameters must be entered in this order.

BEI, SLSCI, ASL8, SLTSET, NIS, MTPRSE

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

• BEI = 0 (no)• SLSCI = 0 (no)• ASL8 = 0 (no)• SLTSET = 01• NIS = 0 (off)• MTPRSE = 0 (no)

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

TFATCABMLQ, BEI, SLSCI, ASL8, SLTSET, NIS, MTPRSE

Note: The TFATCABMLQ parameter value can be specified only when changing the attributes of alinkset (see Changing an SS7 Linkset). When a newly added linkset is displayed, the value of theTFATCABMLQ parameter is either 1, for a linkset containing C links, or 0, for a linkset containing eitherA, B, D, or E links. If all linksets in the EAGLE 5 ISS are displayed, only ANSI linksets are displayed.ITU international and ITU national linksets cannot be displayed on the SEAS interface.

To configure the ANSI MTP Restart feature using the supplier specific parameter mtprse, the ANSIMTP Restart feature must be enabled with the chg-feat command. The on=mtprsi and mtprsitparameters of the EAGLE 5 ISS’s chg-stpopts command are also used to configure the ANSI MTPRestart feature.

Note: Once the ANSI MTP Restart feature is turned on with the chg-feat command, it cannot beturned off.

53910-6013-001 Revision A, March 2011


The ANSI MTP Restart feature must be purchased before you turn the features on with the chg-featcommand. If you are not sure whether you have purchased the ANSI MTP restart feature, contactyour Tekelec Sales Representative or Account Representative.

The 5-Bit to 8-Bit SLS Conversion feature is configured using the supplier specific parameters slsciand asl8 and the slscnv parameter of the EAGLE 5 ISS’s chg-stpopts command.

The actions of the supplier specific parameters slsci and asl8 parameters are affected by the slscnvparameter of the EAGLE 5 ISS’s chg-stpopts command. The interaction of these parameters isshown in Table 5: Signaling Link Selector (SLS) Conversion (ANSI Linksets Only).

Table 5: Signaling Link Selector (SLS) Conversion (ANSI Linksets Only)

ResultIncoming LinksetASL8 Parameter

Value

Outgoing LinksetSLSCI Parameter

Value

CHG-STPOPTSSLSCNV

Parameter Value

The adjacent node is sending 8-bit SLSs.No SLS conversion is performed onMSUs received on this linkset.

1Not ApplicableON

The adjacent node is not sending 8-bitSLSs. 5-bit to 8-bit SLS conversion onMSUs received on this linkset.

0Not ApplicableON

The adjacent node is sending 8-bit SLSs.No SLS conversion is performed on anylinksets.

1Not ApplicableOFF

The adjacent node is not sending 8-bitSLSs. 5-bit to 8-bit SLS conversion isnot performed on all linksets.

0Not ApplicableOFF

The adjacent node is sending 8-bit SLSs.No SLS conversion is performed.11PERLS*

The adjacent node is not sending 8-bitSLSs. 5-bit to 8-bit SLS conversion isperformed.

01PERLS*

The adjacent node is sending 8-bit SLSs.No SLS conversion is performed.10PERLS*

The adjacent node is not sending 8-bitSLSs. 5-bit to 8-bit SLS conversion isnot performed.

00PERLS*

* When the slscnv=perls parameter is specified with the EAGLE 5 ISS chg-stpopts command,

54910-6013-001 Revision A, March 2011


ResultIncoming LinksetASL8 Parameter

Value

Outgoing LinksetSLSCI Parameter

Value

CHG-STPOPTSSLSCNV

Parameter Value

5-bit to 8-bit SLS conversion is only performed on the MSUs arriving at the EAGLE 5 ISS on linksetsthat have the asl8=0 parameter assigned to them, and leaving the EAGLE 5 ISS on linksets that havethe slsci=1 parameter assigned to them.

Display the DPCsin the database.

Display the linksets in thedatabase.

Is the APC inthe DPC table?

No

Perform the "Adding aDestination Point

Code" procedure inChapter 2 and add theAPC to the DPC table.

Yes

Display the self IDof the EAGLE 5

ISS.

ToSheet 2

Enter theFLOW-THRU:::::"rtrv-feat";

command.

Is the ANSIMTP restart feature

on?

Enter theFLOW-THRU:::::"chg-feat”;

command with thisparameter.:mtprs=on

Yes

No

Is the MTP Restartfeature to be used on thelinkset being added to the

database?

Yes

No ToSheet 3

Enter the FLOW-THRU:::::"rtrv-rtx";command with this parameter.:dpc/dpca=<New APC for the

linkset>

Is theAPC of the linkset being

added in this procedure inthe rtrv-rtx output?

Do you wish tochoose another APC

for the linkset?

Perform the “Removing aRoute Exception Entry”

procedure, with the SEASFLOW-THRU command, in the

Database AdministrationManual - SS7 to remove all the

entries shown in the rtrv-rtxoutput.

YesYes

No

No

Sheet 1 of 4Figure 10: Adding an SS7 Linkset from the SEAS Terminal

55910-6013-001 Revision A, March 2011


Do you wish tochange the value of the

MTPRSIT field?

No

Yes

What is theMTPRSIvalue?

Yes

No

FromSheet 1

Enter theFLOW-THRU:::::"rtrv-stpopts";

command

ToSheet 3

What is theMTPRSIvalue?

Enter theFLOW-THRU:::::"chg-stpopts";command with this parameter.

:on=mptrsi


:mtprsit= <2000 to 900000milliseconds>

Enter theFLOW-THRU:::::"chg-stpopts";

command with these parameters.:on=mtprsi

:mtprsit= <2000 to 900000milliseconds>


command

Yes

No

Sheet 2 of 4

56910-6013-001 Revision A, March 2011


What is thecurrent value of the

SLSCNV field?


command.

Do you wish toenable 5-bit to 8-bit

SLS conversion on alllinksets?

ToSheet 4

Yes

NoEnter the

FLOW-THRU:::::"chg-stpopts";command with this parameter.

:slscnv=off


:slscnv=on


command.

PERLS


SLSCNV field?

No

Yes

ON orOFF

FromSheets 1

or 2

Yes

NoIs the 5-Bit to 8-Bit

SLS Conversion feature to beused on the linkset being added

to the database?



Add the linkset to the database using an APC value that isin the DPC table, but not in the self ID table.

See the Adding an SS7 Linkset Supplier SpecificParameters table in this procedure for any supplier specificparameters that can be used for the linkset being added to

the database.

See the Signaling Link Selector (SLS) Conversion (ANSILinksets Only) table in this procedure for the combinationsof the ASL8 and SLSCI supplier specific parameters if the

5-bit to 8-bit SLS Conversion feature is being configured forthe linkset.

Verify that the linksethas been added.

Sheet 3 of 4

57910-6013-001 Revision A, March 2011


Do you wish toenable 5-bit to 8-bit SLS

conversion only onspecific linksets?

Yes


:slscnv=off

Enter theFLOW-THRU:::::"chg-stpopts";command wit this parameter.

:slscnv=perls


command.

FromSheet 3

No


conversion on alllinksets?

Yes


:slscnv=perls


:slscnv=on

NoIs the value of theSLSCNV parameter on

or off?

On

Off



Add the linkset to the database using an APC value that isin the DPC table, but not in the self ID table.

See the Adding an SS7 Linkset Supplier SpecificParameters table in this procedure for any supplier specificparameters that can be used for the linkset being added to

the database.

See the Signaling Link Selector (SLS) Conversion (ANSILinksets Only) table in this procedure for the combinationsof the ASL8 and SLSCI supplier specific parameters if the

5-bit to 8-bit SLS Conversion feature is being configured forthe linkset.

Verify that the linksethas been added.

Sheet 4 of 4

Removing a Linkset Containing SS7 Signaling Links

This procedure is used to remove a linkset containing SS7 signaling links from the database. Thisprocedure uses the EAGLE 5 ISS commands rmv-card, rtrv-rtx, rtrv-ls, and chg-db. Formore information on this procedure, see “Removing a Linkset Containing SS7 Signaling Links” in theDatabase Administration Manual – SS7 .

On the EAGLE 5 ISS, the linkset name can have a maximum of 10 characters. The SEAS interfacesupports a linkset name with a maximum of eight characters. Linkset names specified in this procedurecan have a maximum of eight characters. For linkset names provisioned on the EAGLE 5 ISS that havemore than eight characters, the SEAS interface truncates the linkset name to the first eight characterswhen that linkset name is displayed on the SEAS interface. If the linkset name of the linkset being

58910-6013-001 Revision A, March 2011


removed was configured on the EAGLE 5 ISS with more than eight characters, only the first eightcharacters of the linkset name can be specified in this procedure.

Display the linksets inthe database

Display the signalinglinks in the linkset

Perform the "Removing aRoute" procedure in theDatabase Administration

Manual - SS7 to remove theroutes.

ToSheet 2

Do anyroutes specify the

linkset?

Yes

No

Display the routes in thedatabase

Place the signaling links inthe linkset out of service

Display the signaling linksassigned to the card

Enter theFLOW-THRU::::::"rtrv-ls

:lsn=<name of the linkset>";command

Is the linkset typeof the linkset PRX?

Perform the "Removing a LinksetContaining SS7 Signaling Links"

procedure in the DatabaseAdministration Manual – SS7 to

remove the proxy linkset.

YesNo

Sheet 1 of 2Figure 11: Removing a Linkset Containing SS7 Signaling Links from the SEAS Terminal

59910-6013-001 Revision A, March 2011


Enter theFLOW-THRU::::::"rmv-card";

command

Are any signalinglinks the last signaling link

on the card?

Yes

NoRemove the signaling links

in the linkset from thedatabase

Verify that the linksethas been removed

FromSheet 1

Remove the linksetfrom the database



Enter the FLOW-THRU::::::"rtrv-rtx";command with this parameter::lsn=<name of the linkset being

removed>

Do you wishto change the name of

the linkset assigned to the routeexception entries displayed

in the rtrv-rtxoutput?


procedure in this chapter toremove all the entries shown in

the rtrv-rtx output

YesNo

Perform the “Chaning a RouteException Entry” procedure in thischapter to change the name of the

linkset assigned to the routeexception entries displayed in the

rtrv-rtx output

Sheet 2 of 2

Changing an SS7 Linkset

This procedure is used to change the definition of an existing linkset in the database. This procedureuses the EAGLE 5 ISS commands rtrv-feat, chg-feat, chg-stpopts, rtrv-stpopts,rtrv-ss7opts, rtrv-ls, and chg-db. For more information on this procedure, see “Changingan SS7 Linkset” in the Database Administration Manual – SS7 .

60910-6013-001 Revision A, March 2011


If you wish to use the apci, apcn, apcn24, scrn, gwsa, gwsd, gwsm, slsocbit, slsrsb, itutfr,multgc, apcntype, spc, spca, spci, spcn, spcn24, cggtmod, islsrsb, or randsls parametersof the EAGLE 5 ISS chg-ls command, perform the “Changing an SS7 Linkset” procedure in theDatabase Administration Manual – SS7 using the SEAS FLOW-THRU command with the EAGLE 5 ISScommands.

If you wish to change the adjacent point code of the linkset to an adjacent point code that is assignedto another linkset or change the attributes of a proxy linkset, perform the “Changing an SS7 Linkset”procedure in the Database Administration Manual – SS7 using the SEAS FLOW-THRU command withthe EAGLE 5 ISS commands.

If you wish to use the sapci, sapcn, spcn24, or action parameters (for configuring secondaryadjacent point codes) of the EAGLE 5 ISS’s chg-ls command, perform the “Configuring an ITULinkset with a Secondary Adjacent Point Code (SAPC)” procedure in the Database AdministrationManual - SS7 using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

If you wish to use the gsmscrn parameter (for the GSM MAP Screening feature) of the EAGLE 5 ISS’schg-ls command, perform the “Configuring a Linkset for the GSM MAP Screening Feature” procedurein the Database Administration Manual - Features using the SEAS FLOW-THRU command with theEAGLE 5 ISS commands.

If you wish to use the iptps, lsusealm, slkusealm, ipsg, adapter, asnotif, rcontext, orslktps parameters of the EAGLE 5 ISS’s chg-ls command, perform one of these procedures in theDatabase Administration Manual – IP

7 Secure Gateway using the SEAS FLOW-THRU command with the

EAGLE 5 ISS commands.

• Configuring an IPGWx Linkset• Changing an IPSG M3UA Linkset• Changing an IPSG M2PA Linkset

If you wish to use the matelsn or action parameters of the EAGLE 5 ISS’s chg-ls command,perform the “Configuring a Mate IPGWx Linkset” procedure in the Database Administration Manual– IP

7 Secure Gateway using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

On the EAGLE 5 ISS, the linkset name can have a maximum of 10 characters. The SEAS interfacesupports a linkset name with a maximum of eight characters. Linkset names specified in this procedurecan have a maximum of eight characters. For linkset names provisioned on the EAGLE 5 ISS that havemore than eight characters, the SEAS interface truncates the linkset name to the first eight characterswhen that linkset name is displayed on the SEAS interface. If the linkset name of the linkset specifiedin this procedure was configured on the EAGLE 5 ISS with more than eight characters, only the firsteight characters of the linkset name can be specified in this procedure.


The EAGLE 5 ISS accepts the values for these parameters as supplier specific parameters: tfatcabmlq,bei, slsci, asl8, sltset, nis, mtprse, and nlsn. Table 6: Changing an SS7 Linkset Supplier SpecificParameters shows how the values of these parameters are mapped to the SEAS values and a definitionof each parameter. For more information on these parameters, see “Changing an SS7 Linkset” in theDatabase Administration Manual – SS7 .

61910-6013-001 Revision A, March 2011


Table 6: Changing an SS7 Linkset Supplier Specific Parameters


Value

EAGLE 5 ISSParameter

Value

SupplierSpecific

Parameters

The TFA/TCA broadcast minimum link quantityshows the minimum number of signaling links in

00-160-16TFATCABMLQ

the given link set (or in the combined link set inwhich it resides) that must be available for traffic.

The broadcast exception indicator. This parameterindicates that TFPs are allowed to be broadcast

1

0

YES

NO

BEI

on the linkset or not allowed to be broadcast onthe linkset. This parameter is typically used toprevent TFPs from being broadcast to anothervendor’s system.

The parameter value 1 means TFPs are notbroadcast on the linkset. The parameter value 0means TFPs are broadcast on the linkset.

The slsci parameter indicates that the 5-bit to8-bit SLS conversion feature is enabled or notenabled.

1

0

ON

OFF

SLSCI

When the 5-bit to 8-bit SLS conversion feature isenabled (parameter value 1), the EAGLE 5 ISSreplaces any five-bit SLS values contained inreceived messages with a random 8-bit valuebefore they are used by the EAGLE 5 ISS to selectthe outgoing link in that link set.

When the 5-bit to 8-bit SLS conversion feature isnot enabled (parameter value 0), the 5-bit to 8-bitSLS conversion is not performed on messages inthe linkset.

The asl8 parameter indicates that the nodeadjacent to the EAGLE 5 ISS is or is not sendingMSUs with 8-bit SLSs.

1

0

YES

NO

ASL8

The parameter value 1 means the node adjacentto the EAGLE 5 ISS is sending MSUs with 8-bitSLSs. The parameter value 0 means the nodeadjacent to the EAGLE 5 ISS is not sending MSUswith 8-bit SLSs.

The signaling link test message record to beassociated with the linkset.

01-201-20SLTSET

62910-6013-001 Revision A, March 2011



Value


Value

SupplierSpecific

Parameters

The nis parameter indicates that the NationalSpare for Network Indicator feature is on or off

1

0

ON

OFF

NIS

for the specific linkset. This feature allows thelinkset to use the national spare value (3) for thenetwork indicator code field in the serviceinformation octet (SIO) of the MSU for ANSIlinksets and ITU national linksets (linksetscontaining either 14-bit ITU-N point codes or24-bit ITU-N point codes). This parameter cannotbe specified for ITU international linksets.

The parameter value 1 means the National Sparefor Network Indicator feature is on. The parametervalue 0 means the National Spare for NetworkIndicator feature is off.

The mtprse parameter indicates that the nodeadjacent to the EAGLE 5 ISS is or is not equippedwith the MTP restart capability.

1

0

YES

NO

MTPRSE

The parameter value 1 means the node adjacentto the EAGLE 5 ISS is equipped with the MTPrestart capability The parameter value 0 meansthe node adjacent to the EAGLE 5 ISS is notequipped with the MTP restart capability.

The new name of the linkset.1 alpha and upto 7

1 alpha and upto 7

NLSN

alphanumericcharacters

alphanumericcharacters


TFATCABMLQ, BEI, SLSCI, ASL8, SLTSET, NIS, MTPRSE, NLSN

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

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

TFATCABMLQ, BEI, SLSCI, ASL8, SLTSET, NIS, MTPRSE

Note: If all linksets in the EAGLE 5 ISS are displayed, only ANSI linksets are displayed. ITUinternational and ITU national linksets cannot be displayed on the SEAS interface.

When the number of signaling links in the specified linkset is equal to or greater than the value of thesupplier specific parameter tfatcabmlq, the status of the routes that use the specified linkset is setto allowed and can carry traffic. Otherwise, these routes are restricted. The value of the tfatcabmlq

63910-6013-001 Revision A, March 2011


parameter cannot exceed the total number of signaling links contained in the linkset. The systemdefault value for the tfatcabmlq parameter is 0.

When the tfatcabmlq parameter value is 0, the EAGLE 5 ISS broadcasts TFAs/TCAs only when1/2 of the links in the linkset (or in the combined link set in which it resides) become available. Thetfatcabmlq parameter value is 1/2 of the number of signaling links contained in the linkset, or 1when the linkset contains 0 to 3 signaling links. As signaling links are added or removed from thelinkset, the tfatcabmlq parameter value will be changed automatically.

If the linkset type is being changed to C, or if the current linkset type (unchanged) is C, the supplierspecific parameter tfatcabmlq cannot be specified unless the LSRESTRICT SS7 option is on. Thestate of the LSRESTRICT SS7 option is shown in the EAGLE 5 ISS’s rtrv-ss7opts command output.

To configure the ANSI MTP Restart feature using the supplier specific parameter mtprse, the ANSIMTP Restart feature must be enabled with the chg-feat command. The on=mtprsi and mtprsitparameters of the EAGLE 5 ISS’s chg-stpopts command are also used to configure the ANSI MTPRestart feature.

Note: Once the ANSI MTP Restart feature is turned on with the chg-feat command, it cannot beturned off.

The ANSI MTP Restart feature must be purchased before you turn the features on with the chg-featcommand. If you are not sure whether you have purchased the ANSI MTP restart feature, contactyour Tekelec Sales Representative or Account Representative.

The 5-Bit to 8-Bit SLS Conversion feature is configured using the supplier specific parameters slsciand asl8 and the slscnv parameter of the EAGLE 5 ISS’s chg-stpopts command.

The actions of the supplier specific parameters slsci and asl8 are affected by the slscnv parameterof the EAGLE 5 ISS’s chg-stpopts command. The interaction of these parameters is shown in Table7: Signaling Link Selector (SLS) Conversion (ANSI Linksets Only).

Table 7: Signaling Link Selector (SLS) Conversion (ANSI Linksets Only)

Result

IncomingLinkset ASL8

ParameterValue

OutgoingLinkset SLSCI

ParameterValue

CHG-STPOPTSSLSCNVParameter

Value

The adjacent node is sending 8-bit SLSs. No SLSconversion is performed on MSUs received onthis linkset.

1Not ApplicableON

The adjacent node is not sending 8-bit SLSs.5-bit to 8-bit SLS conversion on MSUs receivedon this linkset.

0Not ApplicableON

The adjacent node is sending 8-bit SLSs. No SLSconversion is performed on any linksets.1Not ApplicableOFF

The adjacent node is not sending 8-bit SLSs.5-bit to 8-bit SLS conversion is not performedon all linksets.

0Not ApplicableOFF

64910-6013-001 Revision A, March 2011


Result

IncomingLinkset ASL8

ParameterValue

OutgoingLinkset SLSCI

ParameterValue

CHG-STPOPTSSLSCNVParameter

Value

The adjacent node is sending 8-bit SLSs. No SLSconversion is performed.11PERLS*

The adjacent node is not sending 8-bit SLSs.5-bit to 8-bit SLS conversion is performed.01PERLS*

The adjacent node is sending 8-bit SLSs. No SLSconversion is performed.10PERLS*

The adjacent node is not sending 8-bit SLSs.5-bit to 8-bit SLS conversion is not performed.00PERLS*

* When the slscnv=perls parameter is specified with the EAGLE 5 ISS chg-stpopts command,

5-bit to 8-bit SLS conversion is only performed on the MSUs arriving at the EAGLE 5 ISS on linksetsthat have the asl8=0 parameter assigned to them, and leaving the EAGLE 5 ISS on linksets thathave the slsci=1 parameter assigned to them.

65910-6013-001 Revision A, March 2011


Display the DPCsin the database.

Display the linksets in thedatabase.

Is the new APCin the DPC table?

NoPerform the "Adding a

Destination Point Code"procedure in Chapter 2 to add

the APC to the DPC table.

Yes

Is the APC ofthe linkset being

changed?

YesNo

Display the self ID ofthe EAGLE 5 ISS.

Enter the FLOW-THRU:::::"rtrv-rtx";command with this parameter.

:dpc/dpca/dpci/dpcn/dpcn24=<NewAPC for the linkset>

Is thenew APC of the linkset

shown in the rtrv-rtxoutput?

Do you wish tochoose another APC

for the linkset?


procedure in this chapter toremove all the entries shown in

the rtrv-rtx output.

Yes

Yes No

No

ToSheet 2

Enter theFLOW-THRU::::::"rtrv-ls";

command with this parameter.:lsn=<name of the linkset>

Is thelinkset type of the

linkset PRX?

Perform the "Changingan SS7 Linkset"procedure in the

Database AdministrationManual – SS7 to change

the linkset.

YesNo

Is the new APCof the linkset currentlyassigned to another

linkset?

No

Yes

ToSheet 2

ToSheet 2

Sheet 1 of 5Figure 12: Changing an SS7 Linkset from the SEAS Terminal

66910-6013-001 Revision A, March 2011


Enter theFLOW-THRU:::::"rtrv-feat";

command.

Is theANSI MTP restart

feature on?

Enter theFLOW-THRU:::::"chg-feat";

command with thisparameter.:mtprs=on

Yes No

Is the MTP Restartfeature to be used on the

linkset being changed in thedatabase?

No ToSheet 3

FromSheet 1

Yes


MTPRSIT field?

No

Yes

What isthe MTPRSI

value?

Yes

No


command

ToSheet 3

What isthe MTPRSI

value?


:on=mtprsi


:mtprsit=<2000 to 900000milliseconds>

Enter theFLOW-THRU:::::"chg-stpopts";

command with these parameters.:on=mtprsi

:mtprsit=<2000 to 900000milliseconds>


command.

Yes

No

Sheet 2 of 5

67910-6013-001 Revision A, March 2011


What is thecurrent value of the

SLSCNV field?


command.

Do you wish toenable 5-bit to 8-bit

SLS conversion on alllinksets?

ToSheet 4

Yes

NoEnter the

FLOW-THRU:::::"chg-stpopts";command with this parameter.

:slscnv=off


:slscnv=on


command.

PERLS


SLSCNV field?

ToSheet 5

No

Yes

ON orOFF

FromSheet 2

Yes

NoIs the 5-Bit to 8-Bit

SLS Conversion feature to beused on the linkset being added

to the database?

ToSheet 5

Sheet 3 of 5

68910-6013-001 Revision A, March 2011



conversion only onspecific linksets?

Yes


:slscnv=off


:slscnv=perls


command

FromSheet 3

No


conversion on alllinksets?

Yes


:slscnv=perls


:slscnv=on

NoIs the value ofthe SLSCNV parameter

on or off?

On

Off

ToSheet 5

Sheet 4 of 5

69910-6013-001 Revision A, March 2011


What is theLSRESTRICT

value?

Is thetfatcabmlq parameter

value to bechanged?

Enter theFLOW-THRU:::::"rtrv-ss7opts";

command.

OFF

Yes

ON

No

FromSheet 4

Enter theFLOW-THRU:::::"chg-ss7opts";command with this parameter.:lsrestrict=on (See the Caution)

What is thelinkset type?

A, B,D, E

C

Is the linksettype to be changed

to C?

Yes

No

Caution: Turning the lsrestrict option on changes the way theEAGLE 5 ISS routes messages by using the state of the routealong with the cost of the route to determine the preferred routeto use. With this option on, the preferred route is not the absolutelowest cost available route in the routeset. A route is consideredavailable if its status is either Allowed or Restricted. If the state ofthe absolute lowest cost route in the routeset is Restricted, thepreferred route is the lowest cost route in the routeset whosestatus is Allowed. Make sure that you wish to have the EAGLE 5ISS route messages in this manner before turning the lsrestrictoption on.

Display the signalinglinks in the linkset.

Place the signaling links inthe linkset out of service.



Verify that the linksethas been changed.

Place the signaling links inthe linkset back in service.

Change the linkset in the database. If the APC isbeing changed, choose an APC value that is in the

DPC table, but not in the self ID table.

See the Changing an SS7 Linkset Supplier SpecificParameters table in this procedure for any supplierspecific parameters that can be used for the linkset

being added to the database.

See the Signaling Link Selector (SLS) Conversion(ANSI Linksets Only) table in this procedure for the

combinations of the ASL8 and SLSCI supplierspecific parameters if the 5-bit to 8-bit SLS

Conversion feature is being configured for thelinkset.

Sheet 5 of 5

Adding an SS7 Signaling Link

This procedure is used to add an SS7 signaling link to the database. For more information on thisprocedure, see the “Adding an SS7 Signaling Link” procedure in the Database Administration Manual– SS7. This procedure uses these EAGLE 5 ISS commands.

rtrv-featrept-stat-gplrtrv-slkrtrv-t1rtrv-card

rept-stat-iptpsrept-stat-slkrst-cardrtrv-tpschg-feat

70910-6013-001 Revision A, March 2011


inh-cardrtrv-ctrl-featrept-stat-cardchg-dbrtrv-ls

alw-cardrmv-card

The SS7 signaling link that is configured in this procedure is running the card and applicationcombinations shown in Table 8: SS7 Signaling Link Card and Application Combinations .

Table 8: SS7 Signaling Link Card and Application Combinations

Type of Signaling LinkApplicationCard Type

MPL signaling linkss7ansilimds0

T1 signaling linkss7ansilimt1

limch

ATM high-speed signaling linkatmansilimatm

IP signaling linkiplimdcm

If you wish to configure any of the signaling links shown in Table 9: Signaling Link Procedures, performthe procedures shown in Table 9: Signaling Link Procedures using the SEAS FLOW-THRU command withthe EAGLE 5 ISS commands.

Table 9: Signaling Link Procedures

ProcedureType of Signaling Link

“Adding an SS7 Signaling Link” procedure in theDatabase Administration Manual – SS7

A signaling link on a LIM running the CCS7ITUapplication

“Adding an ATM High-Speed Signaling Link”procedure in the Database Administration Manual– SS7

An E1 ATM high-speed signaling link

One of these procedures in the DatabaseAdministration Manual – IP

7 Secure Gateway.

A signaling link on a LIM running either thess7ipgw, ipgwi, iplimi, or ipsg applications

• Adding an IPLIMx Signaling Link• Adding an IPGWx Signaling Link• Adding an IPSG M3UA Signaling Link• Adding an IPSG M2PA Signaling Link

“Adding an E1 Signaling Link” procedure in theDatabase Administration Manual – SS7

An E1 signaling link

“Adding a T1 Signaling Link” procedure in theDatabase Administration Manual – SS7

A T1 signaling link that is assigned to anunchannelized T1 port

71910-6013-001 Revision A, March 2011


To support more than 1200 signaling links, certain levels of hardware must be installed in the EAGLE5 ISS. Go to Appendix D, “Reference Information,” in the Database Administration Manual - SS7 forthe hardware requirements.

For the EAGLE 5 ISS to contain more than 1200 signaling links, the Large System # Links controlledfeature must be enabled for the desired quantity. Perform the “Enabling the Large System # LinksControlled Feature” in the Database Administration Manual - SS7 to enable the Large System # Linksfeature.


The EAGLE 5 ISS accepts the values for these parameters as supplier specific parameters: l2test,ecm, pcrn1, pcrn2, lpset, atmtsel, vci, vpi, ll, ts, t1port, and t1loc. Table 10: SS7 SignalingLink Supplier Specific Parameters shows how the EAGLE 5 ISS parameter values are mapped to the SEASvalues and a definition of each parameter. For more information on these parameters, see “Addingan SS7 Signaling Link” in the Database Administration Manual – SS7 .

Table 10: SS7 Signaling Link Supplier Specific Parameters


Value


Value

SupplierSpecific

Parameters

The level 2 timer set table. A signaling link may beassigned to any of the twenty tables.

01-201-20L2TSET

Error correction method1

0

BASIC

PCR

ECM

The threshold of the number of MSUs available forretransmission. If the error correction method being

001 - 1271-127PCRN1

used is PCR, and this threshold is reached, no new MSUsor FISUs are sent. The retransmission cycle is continuedup to the last MSU entered into the retransmission bufferin the order in which they were originally transmitted.

The threshold of the number of MSU octets availablefor retransmission. If the error correction method being

0300 - 35500300-3500PCRN2

used is PCR, and this threshold is reached, no new MSUsor FISUs are sent. The retransmission cycle is continuedup to the last MSU entered into the retransmission bufferin the order in which they were originally transmitted.

The link parameter set identifier – the ATM signalingparameter set table. An ATM signaling link can beassigned to any of twenty parameter set tables.

01 - 201-20LPSET

72910-6013-001 Revision A, March 2011



Value


Value

SupplierSpecific

Parameters

The ATM timing selector – The source of the timing forthe ATM signaling link, internal, line, or external.

0

1

LINE

EXTERNAL

ATMTSEL

Internal timing is derived from an internal clock source2INTERNAL operating at 1.544 MHz ± 50 ppm. Line timing is derived

from its received data stream, if present. External timingis derived from a clock source external to the EAGLE 5ISS.

The virtual channel identifier – The identifier of thevirtual channel used by the ATM signaling link forvirtual channel connections.

Note: If a 3 Links per E5-ATM Card quantity is enabled,the VCI parameter value can be from 00000 to 16383.

00000 - 655350-65535VCI

The virtual path identifier – The identifier of the virtualpath used by the ATM signaling link for virtual pathconnections.

0000-40950-4095VPI

The length of the cable used for the ATM signaling link.The value of the ll parameter is from 0 to 7, with eachnumber representing a range of cable lengths.

0-70-7LL

The timeslot on the T1 card or channel card being usedfor the T1 signaling link

01-241-24TS

The T1 port on the T1 card that is servicing the timeslotselected for the T1 signaling link.

1-81-8T1PORT

Note: The values 1 to 8 for this parameter can bespecified only if the T1 card is an HC MIM or an E5-E1T1card. If the T1 card containing the T1 signaling link isan E1/T1 MIM, the value for this parameter is either 1or 2.

The location of the T1 card servicing the timeslot selectedfor the T1 signaling link.

1101-61181101-6118T1LOC


The supplier specific parameters are optional. The default value will be entered for any supplierspecific parameter not specified when adding the signaling link.

When the signaling link is displayed, the supplier specific parameter values are displayed in this order.

L2TSET,,, ECM, PCRN1, PCRN2, LPSET, ATMTSEL, VCI, VPI, LL, TS, T1PORT, T1LOC

73910-6013-001 Revision A, March 2011


The SEAS parameter SVCST is not supported by the EAGLE 5 ISS. When a signaling link is added tothe database using the EAGLE 5 ISS’s ent-slk command, the state of the signaling link is set tounavailable, equivalent to specifying the SVCST=UAV parameter with the SEAS ASGN-SLK command.If a signaling link is added to the database using the SEAS ASGN-SLK command, and the SVCSTparameter is not specified, the state of the signaling link is set to active.

The EAGLE 5 ISS supports only the value N for the SEAS ENCR parameter. If the ENCR=Y parameteris specified, the parameter is rejected with the IDNS message.

The EAGLE 5 ISS does not support the EQOPTS parameter. Any value for this parameter is rejectedby the EAGLE 5 ISS.

Canceling the REPT-STAT-SLK and RTRV-SLK Commands

Because the EAGLE 5 ISS’s rept-stat-slk and rtrv-slk commands used in this procedure canoutput information for a long period of time, the rept-stat-slk and rtrv-slk commands can becanceled and the output of the rept-stat-slk command stopped. To cancel the rept-stat-slkand rtrv-slk commands, enter the EAGLE 5 ISS’s canc-cmd without the trm parameter and withthe SEAS FLOW-THRU command.

For more information about the canc-cmd command, go to the Commands Manual.

SS7 Signaling Link Parameter Combinations

Table 11: SS7 Signaling Link Parameter Combinations shows the four types of SS7 signaling links that canbe provisioned in the database and the parameters and values that can be used to provision each typeof SS7 signaling link.

Table 11: SS7 Signaling Link Parameter Combinations

T1 Signaling LinkIP Signaling LinkATM High-Speed

Signaling Link

MPL Signaling

Link (See Note 1)

Mandatory Parameters

loc = location of theLIM-T1 or LIMCH with

loc = location of theDCM with of the IPLIM

loc = location of theATM high-speed LIM

loc = location of theMPL with the SS7ANSI

of the SS7ANSIapplication and theDCM card type.

with the ATMANSIapplication and theLIMATM card type.

application and theLIMDS0 card type. application. and either

the LIMT1 or LIMCHcard type.

link = See Note 7link = A - A3, B - B3 (SeeNote 8)

link = A4 - A7, B4 - B7(See Note 8)

link = A or B (See Note9)

link = A, A1, A2, A3,

B, B1, B2, or B3

lsn = linkset name (SeeNote 6)




74910-6013-001 Revision A, March 2011



Signaling Link

MPL Signaling

Link (See Note 1)

mn = 00 - 15mn = 00 - 15mn = 00 - 15mn = 00 - 15

lkspd = 56 or 64lkspd = 1536lkspd = 1536 or 1544lkspd = 56


ts = 01 - 24lpset = 01 - 20

default value = 1

l2tset = 01 - 20

default value = 1

t1port = See Note 4atmtsel = 0, 1, 2ecm = 1 or 0

default value = 1default value = 0default value = 1

t1loc = location of theLIM-T1 card (See Notes4 and 5)

vci = 00000 - 65535 or00000 - 16383(See Note3)

default value = 00005

pcrn1 = 001 - 127 (SeeNote 2)

default value =0 76

ecm = 1 or 0vpi = 0000 - 4095pcrn2 = 0300 - 35500(See Note 2) default value = 1default value = 0default value = 3800

pcrn1 = 001 - 127 (SeeNote 2)

ll = 0 - 7

default value = 0default value = 076

pcrn2 = 0300 - 35500(See Note 2)

default value = 3800

Notes:

1. This procedure is not used to configure E1 signaling links. To configure E1 signaling links, go toAppendix A, “E1 Interface,” in the Database Administration Manual - SS7.

2. These parameters can be specified only when the value of the ecm parameter is 0.3. The values 0 - 4 and 6 - 31 cannot be specified for the vci parameter. These values are reserved.

If a 3 Links per E5-ATM Card quantity is enabled, the VCI parameter value can be from 00000 to16383.

4. If the card is a channel card (card type LIMCH), the t1port value cannot be specified. The t1locparameter must be specified if the T1 signaling link is assigned to a channel card. The t1portand t1loc parameters cannot be specified for a channel card. If the card is an HC MIM or E5-E1T1

75910-6013-001 Revision A, March 2011



Signaling Link

MPL Signaling

Link (See Note 1)

card (card type LIMT1), the t1port parameters can be 1 through 8. If the card is an E1/T1MIM(card type LIMT1), the t1port parameter values are either 1 or 2. The HC MIM or E5-E1T1 cardcannot be a channel card.

5. The t1loc parameter can only be specified if the card that the T1 signaling link is being assignedto is a LIMCH card

6. On the EAGLE 5 ISS, the linkset name can have a maximum of 10 characters. The SEAS interfacesupports a linkset name with a maximum of eight characters. Linkset names specified in thisprocedure can have a maximum of eight characters. For linkset names provisioned on the EAGLE5 ISS that have more than eight characters, the SEAS interface truncates the linkset name to thefirst eight characters when that linkset name is displayed on the SEAS interface. If the linksetname of the linkset specified in this procedure was configured on the EAGLE 5 ISS with morethan eight characters, only the first eight characters of the linkset name can be specified in thisprocedure.

7. The range of link parameter values is dependent on the type of LIMT1 card (either an E1/T1MIM, an HC MIM, or E5-E1T1 card) and if the card is an HC MIM, the HC MIM signaling linkquantity that is enabled.

E1/T1 MIM - Link Parameter Values A - A3, B - B3HC MIM - Link Parameter Values A - A31, B - B31. If the Fan feature is off, shown in thertrv-feat output with the entry FAN = off, the link parameter values can only be A - A15,B - B15.E5-E1T1 - Link Parameter Values A - A15, B - B15

8. The link values A - A3 and B - B3 can be specified only if the card is a single-slot EDCM or anE5-ENET card. The link values A4 - A7 and B4 - B7 can be specified only if the card is an E5-ENETcard.

9. The link value A1 and B can be specified only if the card is an E5-ATM.The link value A1 can bespecified only if the feature is enabled and turned on.

76910-6013-001 Revision A, March 2011


Enter the EAGLE 5 ISS commandrtrv-slk with the SEAS

FLOW-THRU command.

YesWhat is the

maximum number of signalinglinks the EAGLE 5 ISS can

have?

Less than2800

2800

Will the additionof the signaling link

exceed the maximum number ofsignaling links the EAGLE

5 ISS can have?

Perform the "Enabling theLarge System # LinksControlled Feature"

procedure to enable thedesired quantity of

signaling links.

No

This procedure cannot beperformed. The EAGLE 5

ISS can contain amaximum of 2800

signaling links.

What type ofsignaling link is being

added?

T1 SignalingLink

IPLIMx Signaling Link orATM High-Speed

Signaling LinkOther Low-Speed

Signaling Link

ToSheet 11

Enter the EAGLE 5 ISScommand rtrv-card with the

SEAS FLOW-THRUcommand.

Is therequired low-speed LIM in

the database?

Yes

No

Perform the "Adding a SS7LIM" procedure in the

Database AdministrationManual - System

Management to add therequired card to the

database.

ToSheet 4

ToSheet 2



Is therequired LIM-T1 card in

the database?

Yes

No

Perform the "Adding theLIM-T1 Card" procedure in

the Database AdministrationManual - SS7 to add the

required card in thedatabase.

Sheet 1 of 11Figure 13: Adding an SS7 Signaling Link from the SEAS Terminal

77910-6013-001 Revision A, March 2011


Enter the EAGLE 5 ISScommand rtrv-t1 with the


Are the T1parameters for thesignaling link in the

database?

Perform the "Adding T1Interface Parameters"

procedure in theDatabase AdministrationManual - SS7 to add therequired T1 parameters

No

YesFromSheet 1

LIMCH

LIMT1

Enter the EAGLE 5 ISScommand rept-stat-gpl with theSEAS FLOW-THRU command

and with this EAGLE 5 ISSparameter.

:gpl=ss7hc

Is the LIMT1 cardlocation shown in therept-stat-gpl output?

The LIMT1 cardis an HC MIM.

No

Yes

Enter the EAGLE 5 ISS commandrept-stat-gpl with the SEAS

FLOW-THRU command and withthis EAGLE 5 ISS parameter.

:gpl=ss7epm

Is the LIMT1 cardlocation shown in therept-stat-gpl output?

No

Yes The LIMT1 cardis an E5-E1T1

card.

The LIMT1 cardis an E1/T1

MIM.

ToSheet 11

ToSheet 3

To which cardtype is the T1 signaling

link being assigned?

Sheet 2 of 11

78910-6013-001 Revision A, March 2011


Enter the EAGLE 5 ISScommand rtrv-feat with the


FromSheet 2

Is the Fanfeature turned

on?

No

Yes

Enter the EAGLE 5 ISS commandchg-feat with the SEAS

FLOW-THRU command and withthis EAGLE 5 ISS parameter.

:fan=on

Verify that fans have beeninstalled on the shelf

containing the HC MIM.

Have the fansbeen installed?

Go to the Installation Manual andinstall the fans on the shelf containing

the HC MIM.Note: The fans must be installed andworking properly before an HC MIMcan be placed in the EAGLE 5 ISS.

ToSheet 11

No

Yes

Are link valuesA16-A31 or B16-B31

being specified for the T1signaling link?

When thesignaling links were

displayed on Sheet 1, were linkvalues A16-A31 or B16-B31 shown

for any T1 signalinglinks?

No

Yes

No

Yes

Sheet 3 of 11

79910-6013-001 Revision A, March 2011


FromSheet 1

Is an IPor ATM high-speedsignaling link being

added?

Yes

Enter the EAGLE 5 ISScommand rept-stat-gpl with theSEAS FLOW-THRU command

and with this EAGLE 5 ISSparameter.

:gpl=iplhc

Is the IPLIMx cardlocation shown in therept-stat-gpl output?

The IPLIMxcard is an

E5-ENET card.

No

The IPLIMx cardis a single-slot

EDCM.

ToSheet 5

Enter the EAGLE 5 ISScommand rtrv-tps with the


Was a newIPLIMx card added?

Yes

Are signalinglinks assigned to the

card?

No

An IPLIMx card thatcontains signaling

links uses 4000 TPS.

ToSheet 11

Yes

No

ANSI ATMHigh-Speed Signaling

Link

IPLIMxSignaling Link

ToSheet 6



Is therequired IPLIMx card in

the database?

Yes

No

Perform the "Adding anIPLIMx Card" procedure in

the Database AdministrationManual - IP7 Secure

Gateway to add the requiredcard to the database.

Sheet 4 of 11

80910-6013-001 Revision A, March 2011


Yes

Enter the EAGLE 5 ISS command rept-stat-cardwith the SEAS FLOW-THRU command and

with this EAGLE 5 ISS parameter.

:loc=<card location of the card that you wish toadd the signaling link to>

What is the GPLvalue shown in the

rept-stat-card output?

The card is anE5-ATM and can

contain a maximum ofthree signaling links.

No

The card is aLIMATM and

can contain onlyone signaling

link.

Enter the EAGLE 5 ISScommand rtrv-tps with the


Was a newcard for the ANSI

ATM high-speed signalinglink added?

ATMANSI

An ANSI ATMhigh-speed signalinglink uses 1630 TPS.

ATMHC

ToSheet 6



Is therequired card in thedatabase? (See the

Notes)

Yes

No

Perform the "Adding an ATMHigh-Speed LIM" procedure inthe Database Administration

Manual - SS7 to add the requiredcard in the database.

If the LINK values A1 or B will bespecified for the signaling link,the card must be an E5-ATM.

The APPL value of the card mustbe ATMANSI .

FromSheets 4

or 9

Notes:1. ANSI ATM high-speed signalinglinks cannot be added to the card ifthe card contains signaling linkswith the LINK values A, A1, and B.2. The APPL value of the card mustbe ATMANSI .

Sheet 5 of 11

81910-6013-001 Revision A, March 2011


To add the signaling link , one or more of these actionsmust be performed.

The IP TPS values of some IPGWx linksets will haveto be changed.

The MAXSLKTPS values of some IPSG linksets (andthe RSVDSLKTPS values if necessary) will have tobe changed.

Some ATM high-speed signaling links will have to beremoved. An ANSI ATM high-speed signaling linkuses 1630 TPS. An ITU ATM high-speed signalinglink uses 2038 TPS.

Remove an IPLIMx card that contains signaling links.An IPLIMx card that contains signaling links uses4000 TPS.

What isthe maximum total

provisioned system TPSvalue? Seethe Note.

500,000

750,000

Do you wishto change the maximumtotal provisioned system

TPS value?

No

Yes

Perform the “Activating the HIPR2 HighRate Mode Feature” procedure in the

Database Administration Manual –System Management to enable and turnon the HIPR2 High Rate Mode feature.

When the HIPR2 High Rate Modefeature is enabled and turned on, the

maximum total provisioned system TPSvalue is increased to 750,000.

FromSheets 4

or 5

Note: The maximum totalprovisioned system TPS

cannot be increasedbeyond 750,000 TPS.

ToSheet 7

ToSheet 11

Is an ATMhigh-speed signaling link

being added?

No

Yes ToSheet 9

Sheet 6 of 11

82910-6013-001 Revision A, March 2011


FromSheets 6

or 8

Which actiondo you wish to

perform?

Remove ATMHigh-Speed

Signaling Links

Change the TPSof IPGWX or IPSG

Linksets

None of theActions This procedure

cannot be performed.

ToSheet 8

Perform the “Removingan SS7 Signaling Link”procedure to remove

some ATM high-speedsignaling links.

Do you wishto perform other

actions?

Perform the “Removing anSS7 Signaling Link” procedureto remove all of the signalinglinks that are assigned to an

IPLIMx card, but not signalinglinks on the card that this link

will be assigned to.

Remove anIPLIMx Card

No

Yes

Are anyATM high-speed

signaling links shown in thertrv-card output

on Sheet 5?

Yes

No

Are anyIPLIMx cards

containing signaling linksshown in the rtrv-card

output onSheet 4?

Yes

No

ToSheet 11

Is an ATMhigh-speed signaling link

being added?

NoYesToSheet 9

Sheet 7 of 11

83910-6013-001 Revision A, March 2011


Enter the EAGLE 5 ISS commandrept-stat-iptps with the SEAS

FLOW-THRU command.

Enter the EAGLE 5 ISScommand rtrv-ls with the

SEAS FLOW-THRU commandand with this EAGLE 5 ISS

parameter.:lsn=<linkset name shown in

the rept-stat-iptps output>Repeat this step for each

linkset shown in therept-stat-iptps output.

Are any linksetsshown with the valueyes in the IPGWAPC

column?

Change the IP TPS valuesof some or all the existingIPGWx linksets shown in

the rtrv-ls output byperforming the “Configuring

an IPGWx Linkset”procedure in the Database

Administration Manual – IP7Secure Gateway.

Change the MAXSLKTPS valuesof the IPSG linksets (andRSVDSLKTPS values if

necessary) of some or all theexisting IPSG linksets shown inthe rtrv-ls output by performing

these procedures in the DatabaseAdministration Manual – IP7

Secure Gateway as necessary.

“Changing an IPSG M2PA Linkset”

“Changing an IPSG M3UA Linkset”Are any linksetsshown with the value

yes in the IPSGcolumn?

Do you wish tochange the MAXSLKTPS

values on any of theIPSG linksets?

No

Yes

Yes

No

No

Yes

FromSheet 7

Do you wishto perform other

actions?

No

Yes

ToSheet 7

Yes

No

Are anylinksets shown inthe rept-stat-iptps

output?

Yes

No

ToSheet 11

Is an ANSI ATMhigh-speed signaling link

being added?

ToSheet 9

Sheet 8 of 11

84910-6013-001 Revision A, March 2011


Yes

No

Does the rtrv-slk outputon Sheet 1 show any ATM

high-speed signaling links whoseLINK value is A1?

A 3 Links per E5-ATMCard quantity is enabled.

ToSheet 10

A 3 Links per E5-ATM Cardquantity must be enabled.

Enter the EAGLE 5 ISS commandrtrv-ctrl-feat with the SEASFLOW-THRU command.

Is a 3 Linksper E5-ATM Cardquantity enabled?

Yes

No

Perform the “Changing the 3 Linksper E5-ATM Card Quantity”

procedure Database AdministrationManual – SS7 to enable a 3 Links per

E5-ATM Card quantity .

ToSheet 11

Will adding thenew signaling link with the

LINK value A1 exceed the 3 Links perE5-ATM Card quantity

shown in the rtrv-ctrl-featoutput?

What is thecurrent quantity?

250

Less than250

The signaling link cannot be added. TheEAGLE 5 ISS can have a maximum of

250 E5-ATMs that can have threesignaling links.

Yes

No ToSheet 10

Does the E5-ATMcontain LINK values A

and B?

Yes

ToSheet 5

No

FromSheets 6, 7,

or 8

What will be theLINK value of the new ATMhigh-speed signaling link?

A or B

A1

Enter the EAGLE 5 ISS commandrtrv-ctrl-feat with the SEASFLOW-THRU command.

ToSheet 11

Sheet 9 of 11

85910-6013-001 Revision A, March 2011


FromSheet 9

Is the state of all thesignaling links shown in the

previous stepOOS-MT-DSBLD?

Enter the EAGLE 5 ISS commandrept-stat-card with the SEAS

FLOW-THRU command and with thisEAGLE 5 ISS parameter.

:loc=<card location of the card thatyou wish to add the signaling link to>

Is the state of thecard shown in the previous

step OOS-MT-DSBLD?

ToSheet 11

Yes

No

No

Yes

Place the signaling links shown in therept-stat-slk output out of service.

Perform this step for each signaling linkshown in the rept-stat-slk output whose

state is not OOS-MT-DSBLD.

Enter the EAGLE 5 ISS commandsinh-card or rmv-card with the SEASFLOW-THRU command and with

this EAGLE 5 ISS parameter.

:loc=<card location of the card thatyou wish to add the signaling link to>

Was the rept-stat-cardcommand on Sheet 5

performed?

Yes

No

Sheet 10 of 11

86910-6013-001 Revision A, March 2011


Enter the EAGLE 5 ISS commandchg-db with the SEAS FLOW-THRU

command and with these EAGLE 5 ISSparameters.

:action=backup

:dest=fixed

Put the signaling link in service.If the link=a1 parameter was

specified for an ATM high -speedsignaling link, perform this step

for all the signaling links that areassigned to the card.

Is the signalinglink the first signaling link

on the card or was the link=a1parameter specified for the

ATM high-speedsignaling link?

Enter the EAGLE 5 ISS commandalw-card or rst-card with the SEAS

FLOW-THRU command and with thisEAGLE 5 ISS parameter.

:loc=<the card location of the signalinglink that was added>

Enter the EAGLE 5 ISS commandrept-stat-slk with the SEAS FLOW-THRUcommand and with these EAGLE 5 ISS

parameters.

:loc=<the card location of the signaling linkthat was added>

:link=<the link value of the signaling link thatwas added>

Yes

No

Verify that thesignaling link has been added

to the database.

Add the signaling link to the database. Usethe SS7 Signaling Link Supplier Specific

Parameters table and the SS7 Signaling LinkParameter Combinations table in this

procedure as a guide for determining theparameters and values to specify when

adding the signaling link.If adding the new signaling link will result in

more than 700 signaling links in the databaseand the OAMHCMEAS value in the EAGLE 5

ISS’s rtrv-measopts output is on, thescheduled UI measurement reports will be

disabled.If a 3 Links per E5-ATM Card quantity is

enabled, the vci parameter value can be only0 to 16383.

FromSheets 1, 2,3, 4, 6, 7, 8,

9, or 10

Display the linksets inthe database.

Is therequired linkset in the

database?

Perform the "Adding anSS7 Linkset" procedure

to add the requiredlinkset.

Yes

No

Sheet 11 of 11

Removing an SS7 Signaling Link

This procedure is used to remove an SS7 signaling link to the database. For more information on thisprocedure, see the “Removing an SS7 Signaling Link” procedure in the Database Administration Manual– SS7. This procedure uses these EAGLE 5 ISS commands.

87910-6013-001 Revision A, March 2011


rept-stat-slkdlt-slkrtrv-ss7optsrtrv-lsrtrv-slk

chg-dbdact-lbprept-stat-lfsrmv-card

To remove a signaling link assigned to an IP card running either the ss7ipgw, ipgwi, iplim, oriplimi applications, perform one of these procedures in the Database Administration Manual – IP

7

Secure Gateway using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

• Removing an IPLIMx Signaling Link• Removing an IPGWx Signaling Link• Removing an IPSG M3UA Signaling Link• Removing an IPSG M2PA Signaling Link

Canceling the REPT-STAT-SLK Command

Because the EAGLE 5 ISS’s rept-stat-slk command used in this procedure can output informationfor a long period of time, the rept-stat-slk command can be canceled and the output of therept-stat-slk command stopped. To cancel the rept-stat-slk command, enter the EAGLE 5ISS’s canc-cmd without the trm parameter and with the SEAS FLOW-THRU command.

For more information about the canc-cmd command, go to the Commands Manual.

88910-6013-001 Revision A, March 2011


Enter theFLOW-THRU::::::"rtrv-slk";

command.

Enter theFLOW-THRU::::::"rtrv-ls";

command with this parameter.:lsn=<the name of the linkset thatcontains the signaling link that is

being removed>

What is thelinkset type of the linksetdisplayed in the previous

step?

C

A, B, D,E, or PRX

ToSheet 2

Enter theFLOW-THRU::::::"rtrv-ss7opts";

command.

What is theLSRESTRICT

value?

Off

On

When the signalinglink is removed, will the

number of signaling links in thelinkset be less than the

TFATCABMLQ value of thelinkset ?

NoYes

Do you wishto change the

TFATCABMLQ value forthe linkset to 0?

Yes

No

The signaling link cannot beremoved. The remainder ofthis procedure cannot be

performed.

Enter the FLOW-THRU::::::"chg-ls";command with these parameters.:lsn=<the name of the linkset thatcontains the signaling link that is

being removed>:tfatcabmlq=0

Note: Changing the tfatcabmlqvalue to 0 sets the minimumnumber of signaling links in thelinkset that are available for trafficto 50% of the number ofprovisioned signaling links in thelinkset.

Sheet 1 of 2Figure 14: Removing an SS7 Signaling Link from the SEAS Terminal

89910-6013-001 Revision A, March 2011


Is a link faultsectionalization (LFS) test

being performed in the signalinglink to be removed from the

database?

Yes

NoEnter theFLOW-THRU::::::"rept-stat-lfs";

command.

Enter theFLOW-THRU::::::"dact-lbp"; command with

these parameters.:loc=<card location of the signaling link>

:link=<signaling link assigned to the card>

Place the signaling linkout of service.

Enter theFLOW-THRU::::::"rept-stat-slk"; command

with these parameters.:loc=<card location of the signaling link>

:link=<signaling link assigned to the card>

Enter the FLOW-THRU::::::"chg-db:action=backup:dest=fixed";

command.

Verify that the signaling linkhas been removed from the

database.

Is the signalinglink the last signaling

link on the card?

Yes

No

Enter theFLOW-THRU::::::"rmv-card";

command with this parameter.:loc=<location of the signaling link>

Is the signalinglink the last signalinglink on the linkset?

Enter theFLOW-THRU::::::"dlt-slk";

command with theseparameters.

:loc=<card location of thesignaling link>

:link=<signaling linkassigned to the card>

:force=yesSee the Note.

Remove the signaling linkfrom the database.

See the Note.

No

Yes

Note: If removing the signaling linkwill result in 700 or less signaling

links in the database and theOAMHCMEAS value in the EAGLE

5 ISS’s rtrv-measopts commandoutput is on, the scheduled UImeasurement reports will be

enabled.

FromSheet 1

Sheet 2 of 2

Adding a Route

This procedure is used to add a route to the database. This procedure uses the EAGLE 5 ISS commandsrept-stat-rte , rtrv-ls, rtrv-dstn, and chg-db. For more information on this procedure, seeeither “Adding a Route Containing an SS7 DPC” or “Adding a Route Containing a Cluster Point Code”in the Database Administration Manual – SS7.

90910-6013-001 Revision A, March 2011


If you wish to use the dpci, dpcn, dpcn24, or force parameters of the EAGLE 5 ISS’s ent-rtecommand, or assign the route being added to the database to an IPGWx linkset, perform the Addinga Route Containing an IPGWx Linkset procedure in the Database Administration Manual – SS7 usingthe SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

If the route will contain a proxy linkset (LST=PRX), or the DPC of the route will contain a proxy pointcode, perform the “Adding a Route Containing an SS7 DPC” procedure in the Database AdministrationManual – SS7.

On the EAGLE 5 ISS, the linkset name can have a maximum of 10 characters. The SEAS interfacesupports a linkset name with a maximum of eight characters. Linkset names specified in this procedurecan have a maximum of eight characters. For linkset names provisioned on the EAGLE 5 ISS that havemore than eight characters, the SEAS interface truncates the linkset name to the first eight characterswhen that linkset name is displayed on the SEAS interface. If the linkset name of the linkset specifiedin this procedure was configured on the EAGLE 5 ISS with more than eight characters, only the firsteight characters of the linkset name can be specified in this procedure.

91910-6013-001 Revision A, March 2011


Display the routes in thedatabase.

Display the linksets inthe database.


database?

Go to the "Adding an SS7Linkset" procedure to add

the required linkset.

Yes

No

Display the DPCs in thedatabase.

Enter theFLOW-THRU::::::"rtrv-ls

:lsn=<name of the linkset>";command.

Is the linksettype of the linkset

PRX?

Perform the "Adding a RouteContaining an SS7 DPC" procedure

in the Database AdministrationManual – SS7 to add the route.

Yes

No

Is theDPC of the route in

the DPC table?

Go to the "Adding aDestination Point Code"

procedure in Chapter 2 toadd the required DPC.

Yes

No

Perform the "Adding a RouteContaining an SS7 DPC" procedure

in the Database AdministrationManual – SS7 to add the route.

Enter theFLOW-THRU::::::"rtrv-dstn

:dpc=<DPC being changed>";command.

Is a proxy pointcode assigned to the

DPC?

Yes No ToSheet 2

Sheet 1 of 2Figure 15: Adding a Route from the SEAS Terminal

92910-6013-001 Revision A, March 2011


FromSheet 1

Will more than tworoutes in the routeset

have the same relativecost value?

No

Yes

Is the 6-WayLoadsharing on Routesets

feature enabled andturned on?

Perform the “Activating the 6-WayLoadsharing on Routesets Feature”

procedure in the DatabaseAdministration Manual – SS7 toenable and turn on the 6-Way

Loadsharing on Routesets feature.

Yes

No

Are routesets thatcontain more than

two routes shown in thedatabase?

Yes

No

Enter theFLOW-THRU::::::"rtrv-ctrl-feat>";command with this parameter.

:partnum=893019801

Add the route to thedatabase.

Verify that the route has beenadded to the database.



Enter theFLOW-THRU::::::"rept-stat-rte";

command.

Sheet 2 of 2

Changing a Route

This procedure is used to change the attributes of a route in the database. This procedure uses theEAGLE 5 ISS commands rtrv-ls , rtrv-dstn, rtrv-ctrl-feat, and chg-db. For moreinformation on this procedure, see “Changing a Route” in the Database Administration Manual – SS7.

This procedure is used only to change the attributes of a route assigned to a linkset containing an SS7adjacent point code. If you wish to use the dpci, dpcn, or dpcn24 parameters of the EAGLE 5 ISS

93910-6013-001 Revision A, March 2011


chg-rte command, perform the “Changing a Route” procedure in the Database Administration Manual– SS7 using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

On the EAGLE 5 ISS, the linkset name can have a maximum of 10 characters. The SEAS interfacesupports a linkset name with a maximum of eight characters. Linksets configured through the SEASinterface will have linkset names with a maximum of eight characters. If linksets configured on theEAGLE 5 ISS have more than eight characters and are displayed on the SEAS interface, the SEASinterface truncates the linkset name to the first eight characters.

If the ipgwapc parameter of the linkset assigned to the route is yes, the route is an IPGWx route (aroute that contains an IPGWx linkset). The IPGWx route can contain only one linkset. The DPC of anIPGWx route must either be the APC of the IPGWx linkset or the SAPC assigned to the IPGWx linkset.The DPC of the route cannot be changed. The SAPC can be assigned to only one linkset. As a result,the linkset assigned to the IPGWx route cannot be changed. Only the RC value assigned to the routecan be changed.

Enter the FLOW-THRU::::::"rtrv-ls";command with this parameter:

:lsn=<name of the linkset currentlyassigned to the route>

What is the valueof the IPGWAPC

parameter?

No

Yes

The route is an IPGWx route.

The DPC of a IPGWx route must either be the APC ofthe linkset or the SAPC of the linkset.

The DPC of a IPGWx route, or any type of route, cannotbe changed.

The SAPC can be assigned to only one linkset.

As a result, the linkset assigned to the IPGWx routecannot be changed.

Only the RC value of the IPGWx route can be changed.

Do you wishto change the RC

value?

Yes

No

No further action can beperformed. This procedure is

finished.


ToSheet 2

ToSheet 5

Sheet 1 of 4Figure 16: Changing a Route from the SEAS Terminal

94910-6013-001 Revision A, March 2011


ToSheet 3

FromSheet 1

Are the APC of thelinkset and the DPC ofthe route the same?

Yes

No

Enter the FLOW-THRU::::::"rtrv-ls";command with this parameter::lsn=<the name of the linkset

whose APC is the same as theDPC of the route>

Enter the FLOW-THRU::::::"rtrv-dstn";command with this parameter:

:dpc/dpca/dpci/dpcn/dpcn24=<theDPC of the route>

Does the linksetcontain the proxy point codethat is also assigned to the

DPC of the route?

Is the linkset a proxylinkset (LST=PRX) containing

a proxy point code?

No

Yes

No

No

This linkset assigned to the route cannot bechanged using this procedure.

However, the RC value for this linkset can bechanged.

Do you wish tochange just the RC value

for this linkset?

Perform the “Removing a Route” procedure inthe Database Administration Manual – SS7 toremove this linkset from the DPC of the route.

After the route has been removed, performthe “Adding a Route Containing an SS7 DPC”

procedure in the Database AdministrationManual – SS7 and add the new linkset to the

DPC of the route.

Yes

No

Sheet 2 of 4

95910-6013-001 Revision A, March 2011


FromSheet 2

Will more than tworoutes in the routeset

have the same relativecost value?

No

Yes

Is the 6-WayLoadsharing on Routesets

feature enabled andturned on?

Perform the “Activating the 6-WayLoadsharing on Routesets Feature”

procedure in the DatabaseAdministration Manual – SS7 toenable and turn on the 6-Way

Loadsharing on Routesets feature.

Yes

No

ToSheet 4

Are routesets thatcontain more than

two routes shown in thedatabase?

Yes

No

Enter theFLOW-THRU::::::"rtrv-ctrl-feat>";command with this parameter.

:partnum=893019801

Sheet 3 of 4

96910-6013-001 Revision A, March 2011


Display the linksets inthe database


database?

Go to the "Adding an SS7Linkset" procedure to add

the required linkset

Yes

No

Change the specifiedroute

Verify that the route has beenchanged in the database



Is the linksetname assigned to the route

to be changed?

Yes

No

FromSheet 3

FromSheet 1

Sheet 4 of 4

97910-6013-001 Revision A, March 2011


Chapter

4Global Title Translation (GTT) Configuration

Chapter 4, Global Title Translation (GTT)Configuration, describes the procedures used toadminister global title translation data.

Topics:

• Provisioning a Mated Application.....99• Removing a Mated Application.....101• Changing a Mated Application.....103• Adding a Global Title Translation.....105• Removing a Global Title Translation.....113• Changing a Global Title Translation.....115

98910-6013-001 Revision A, March 2011

Provisioning a Mated Application

This procedure is used to add a dominant mated application to the database.

The only parameters that can be specified with this procedure are the primary point code, primarysubsystem number, mate point code, and mate subsystem number. The EAGLE 5 ISS relative costparameters cannot be specified in this procedure. When the mated application is added to the databasewith this procedure, the relative cost value for the primary point code and subsystem is defaulted to10. The relative cost value for the mate point code and subsystem is defaulted to 50. This creates adominant mated application with only two entries.

This procedure uses the EAGLE 5 ISS commands rtrv-map, rtrv-ctrl-feat, rtrv-dstn, andchg-db. For more information on provisioning mated applications, refer to one of the “Provisioninga Mated Application” procedures in the Database Administration Manual - Global Title Translation .

If you wish to use the pci, pcn, pcn24, mpci, mpcn, mpcn24, srm, grp, mrc, rc, materc, , or mapset,wt, mwt, thr , mrnset, or mrnpc parameters of the EAGLE 5 ISS’s ent-map command, the subsystemassigned to the mated application is the LNP, INP, V-Flex, ATINPQ, AIQ, or EIR subsystem, or youwish to create another type of MAP group or MAP set, perform one of the “Provisioning a MatedApplication” procedures in the Database Administration Manual - Global Title Translation using theSEAS FLOW-THRU command with the EAGLE 5 ISS commands.

Mated application groups in the EAGLE 5 ISS database can contain up to 32 entries, the primary pointcode, and up to 31 mate point codes. SEAS allows the user to configure only two entries for each MAPgroup. To add more entries to the MAP group, up to 30, after performing this procedure, perform oneof the “Provisioning a Mated Application” procedures in the Database Administration Manual - GlobalTitle Translation using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands. The rcand materc parameters must be specified with the EAGLE 5 ISS’s chg-map command. The maximumnumber of mated application entries that can be provisioned in the EAGLE 5 ISS is 1024, 2000, or 3000,depending on the quantity that is enabled.

If the Flexible GTT Load Sharing feature is enabled, shown by the MAPSET field in the EAGLE 5 ISSrtrv-map output, by default the mated application is assigned to the default MAP set. To assign amated application to a MAP set other than the default MAP set, perform one of the “Provisioning aMated Application” procedures in the Database Administration Manual - Global Title Translationusing the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

A proxy point code cannot be assigned to any point code that will be assigned to a mated application.

99910-6013-001 Revision A, March 2011

Global Title Translation (GTT) ConfigurationDatabase Administration Manual - SEAS


command

Will the addition of themated application increase the

number of mated applications theEAGLE 5 ISS can have beyond


What is the currentmaximum number of matedapplications the EAGLE 5

ISS can have?

1024or

2000

3000

Enter theFLOW-THRU::::::"rtrv-ctrl-feat";

command

Is the XMAPTable Expansion feature

enabled and activated for thedesired number of

mated applications?

Perform the "Enabling the XMAP TableExpansion Controlled Feature," in the

Database Administration Manual -Global Title Translation to enable andactivate the XMAP Table Expansion

feature for the desired number of matedapplications

Yes

No

ToSheet 2

Yes

No

ToSheet 2

Sheet 1 of 2Figure 17: Provisioning a Mated Application

100910-6013-001 Revision A, March 2011


Are thenecessary routes in

the database?

Yes

No

Perform the "Adding a Route"procedure in Chapter 3 of this manual

to add the required routes with theprimary or mate point code (as

required) as the DPC of the route to thedatabase. A proxy point code cannotbe assigned to the point code that willbe assigned to the mated application.

FromSheet 1


Is the EAGLE5 ISS's true point codeto be assigned to themated application?

Display the EAGLE 5ISS's true point code

No

Yes

Enter theFLOW-THRU::::::"rtrv-dstn"; command with

this parameter::dpc/dpca=<the DPC of the route>

Perform this step for each point code thatwill be assigned to the mated application.

A proxy point code cannotbe assigned to the point

code that will be assignedto the mated application.

Is a proxy pointcode assigned to any of

the point codes shown in thertrv-dstn output?

Choose another route touse instead of the routewhose DPC contains a

proxy point code.

Yes No

Verify that the matedapplication has been added

to the database



Add the mated application to the database withthese values:

Primary ANSI point code from the routingtable or the EAGLE 5 ISS's true point code

Primary subsystem numberMate ANSI point code of the mate from the

routing tableMate subsystem number

Note: If the Flexible GTT Load Sharing featureis enabled, shown by the MAPSET field in theEAGLE 5 ISS rtrv-map output on Sheet 1, bydefault the mated application is assigned to thedefault MAP set.

Sheet 2 of 2

Removing a Mated Application

This procedure is used to remove a mated application from the database. This procedure uses theEAGLE 5 ISS commands rtrv-feat, rtrv-ctrl-feat, rtrv-ss-appl, dlt-map, and chg-db.For more information on this procedure, see “Removing a Mated Application” in the DatabaseAdministration Manual - Global Title Translation.

101910-6013-001 Revision A, March 2011


If you wish to use the pci, pcn, pcn24, all, mapset , or mrnset parameters of the EAGLE 5 ISS’sdlt-map command, perform the “Removing a Mated Application” procedure in the DatabaseAdministration Manual - Global Title Translation using the SEASFLOW-THRU command with the EAGLE5 ISS commands.

If the Flexible GTT Load Sharing feature is enabled, only entries in the default MAP set are displayedfrom the SEAS terminal. Performing this procedure removes only mated application entries in thedefault MAP set. To remove entries from a MAP set other than the default MAP set, perform the“Removing a Mated Application” procedure in the Database Administration Manual - Global TitleTranslation using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

The output from the EAGLE 5 ISS command rtrv-ctrl-feat shows whether or not the FlexibleGTT Load Sharing feature is enabled.

The EAGLE 5 ISS's point code and subsystem can be assigned to the mated application. If the matedapplication contains EAGLE 5 ISS's point code and the subsystem shown in Table 12: Mated ApplicationSubsystem Features, perform the “Removing a Mated Application” procedure in the DatabaseAdministration Manual - Global Title Translation using the SEASFLOW-THRU command with the EAGLE5 ISS commands.

Table 12: Mated Application Subsystem Features

SubsystemFeature StatusFeature

INPEnabled and Turned OnINP

INPEnabled and Turned OnANSI-41 INP Query

EIREnabled and Turned OnEIR

V-FLEXEnabled and Turned OnV-FLEX

ATINPQEnabledATINP

LNPEnabledLNP

AIQEnabledANSI41 AIQ

102910-6013-001 Revision A, March 2011


Display the matedapplications in the database

Are any of thefeatures shown in the Mated

Application Subystem Features tableenabled, and turned

on if required?


command

No

Yes

Enter theFLOW-THRU::::::"rtrv-ss-appl";

command

Is the subystem ofthe mated application shown in

the Mated Application SubystemFeatures table?

Yes

No

Go to the "Removing a Mated Application"procedure in the Database Administration Manual- Global Title Translation and remove the matedapplication using the EAGLE 5 ISS commands

with the SEAS FLOW-THRU command.


command

Are all the matedapplications and subsystems

for a specified point codebeing removed?

Verify that the specified matedapplication has been removed

from the database

Yes

NoEnter the

FLOW-THRU::::::"dlt-map:pca=<Primary

ANSI point code>:all=yes"; command

Remove the specifiedmated application from the

database



Figure 18: Removing a Mated Application

Changing a Mated Application

This procedure is used to change an existing mated application in the database. The only parametersthat can be specified in this procedure are the primary point code, primary subsystem number, mate

103910-6013-001 Revision A, March 2011


point code, and mate subsystem number. The EAGLE 5 ISS relative cost parameters cannot be specifiedin this procedure. When the mated application is added to the database with this procedure, the relativecost value for the primary point code and subsystem is defaulted to 10. The relative cost value for themate point code and subsystem is defaulted to 50. This creates a dominant mated application withtwo entries.

If you wish to use the pci, pcn, pcn24, mpci, mpcn, mpcn24, srm, grp, mrc, rc, materc, sso,mapset, eswt, wt, mwt, grpwt, thr , mrnset, or mrnpc parameters of the EAGLE 5 ISS’s chg-mapcommand, or if the subsystem assigned to the mated application is the LNP, EIR, V-Flex, ATINPQ,AIQ, or INP subsystem, perform any of the procedures from the Database Administration Manual -Global Title Translation that are shown in Table 13: EAGLE 5 ISS Changing a Mated Application Proceduresusing the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

Table 13: EAGLE 5 ISS Changing a Mated Application Procedures

Changing the Attributes of a Mated Application

Changing the Mated Application Type

Changing the Weight and In-Service Threshold Values of a Mated Application

Changing the MRNSET and MRN Point Code Values of MAP Entries

If you plan to change the existing MAP group to another type of MAP group, perform the Changingthe Mated Application Type procedure in the Database Administration Manual - Global Title Translationusing the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

The mate point code cannot be changed to the EAGLE 5 ISS’s true point code.

This procedure uses the EAGLE 5 ISS commands chg-db and rtrv-dstn . For more informationabout changing a mated application, refer to the procedures from the Database Administration Manual- Global Title Translation that are shown in Table 13: EAGLE 5 ISS Changing a Mated Application Procedureson this procedure, see “Changing a Mated Application” in the Database Administration Manual - GlobalTitle Translation .

No new entries can be added to a mated application group with this procedure. Mated applicationgroups in the EAGLE 5 ISS database can contain up to 32 eight entries, the primary point code, andup to 31 seven mate point codes. SEAS allows the user to configure only two entries for each MAPgroup. To add more entries to the MAP group, up to 30 six, perform one of the “Provisioning a MatedApplication” procedures in the Database Administration Manual - Global Title Translation using the SEASFLOW-THRU command with the EAGLE 5 ISS commands. The rc and materc parameters must bespecified with the EAGLE 5 ISS’s chg-map command. The maximum number of mated applicationentries that can be provisioned in the EAGLE 5 ISS is 1024, 2000, or 3000, depending on the quantitythat is enabled.

If the Flexible GTT Load Sharing feature is enabled, only entries in the default MAP set are displayedfrom the SEAS terminal. Performing this procedure changes only mated application entries in thedefault MAP set. To change entries in a MAP set other than the default MAP set, perform any of theprocedures from the Database Administration Manual - Global Title Translation that are shown in Table13: EAGLE 5 ISS Changing a Mated Application Procedures using the SEAS FLOW-THRU command withthe EAGLE 5 ISS commands



104910-6013-001 Revision A, March 2011


Is an existing MAPgroup being changed to either a

solitary, load shared, or combineddominant/load shared group?

No

Yes


Perform the "Changing theMated Application Type"

procedure in the DatabaseAdministration Manual -

Global Title Translation tochange the mated

application using the EAGLE5 ISS commands with the


Is the matepoint code in the

database?

Yes

No


Perform the "Adding a Route"procedure in Chapter 3 of this

manual to add the requiredroutes with the mate point codeas the DPC of the route to thedatabase. A proxy point code

cannot be assigned to the pointcode that will be assigned to

the mated application.





Is a proxy pointcode assigned to the pointcode shown in the rtrv-dstn

output?


proxy point code.

Yes

No

Verify that the matedapplication has been

changed in the database



Change the mated application to thedatabase with these values:

Primary ANSI point code of the matedapplication

Primary subsystem number

New Mate ANSI point code of themate from the routing table

New Mate subsystem number

Figure 19: Changing a Mated Application

Adding a Global Title Translation

This procedure is used to add a global title translation to the database. This procedure uses the EAGLE5 ISS commands rtrv-ctrl-feat, rtrv-feat, chg-feat, rtrv-card, rtrv-tt, rtrv-gtt,

105910-6013-001 Revision A, March 2011


rtrv-dstn, rtrv-gttsel, and chg-db. For more information on this procedure, see “Adding aGlobal Title Translation” in the Database Administration Manual - Global Title Translation.

The following parameters of the EAGLE 5 ISS’s ent-gtt command are not supported by SEAS:typei, typeis, typen, typens, typen24, pci, pcn, pcn24, ttn, xlat, gtmodid , force,mrnset, mapset, loopset, or cggtmod.

SEAS does not support hexadecimal digits as the value of the global title address parameter. If youwish to use any of these parameters, or use hexadecimal digits as the value for the global title addressparameter, perform the “Adding a Global Title Translation” procedure in the Database AdministrationManual - Global Title Translation using the SEAS FLOW-THRU command with the EAGLE 5 ISScommands.

If the Flexible GTT Load Sharing feature is enabled, shown by the MRNSET field in the EAGLE 5 ISSrtrv-gtt output, and the routing indicator of the global title translation is G (the EAGLE 5 ISS valueGT), by default, the global title translation is assigned to the default MRN set. To assign the global titletranslation to an MRN set other than the default MRN set, perform the “Adding a Global TitleTranslation” procedure in the Database Administration Manual - Global Title Translation using theSEAS FLOW-THRU command with the EAGLE 5 ISS commands.

If the Flexible GTT Load Sharing feature is enabled, shown by the MAPSET field in the EAGLE 5 ISSrtrv-gtt output, and the routing indicator of the global title translation is D (the EAGLE 5 ISS valueSSN), by default, the global title translation is assigned to the default MAP set. To assign the globaltitle translation to a MAP set other than the default MAP set, perform the “Adding a Global TitleTranslation” procedure in the Database Administration Manual - Global Title Translation using theSEAS FLOW-THRU command with the EAGLE 5 ISS commands.

The EAGLE 5 ISS XLAT parameter does not have a SEAS equivalent. When global title translationsare configured at the SEAS interface, the values for the SEAS parameters RI, DPC, and SSN, allmandatory parameters for the SEAS ADD-GTT and CHG-GTT commands, are converted to the EAGLE5 ISS parameters and values shown in Table 14: SEAS and EAGLE 5 ISS Global Title Translation ParameterConversion.

The RC parameter of the SEAS ADD-GTT command is not supported by the EAGLE 5 ISS. While theRC parameter must be specified with the SEAS ADD-GTT command, the RC parameter is discardedwhen the SEAS ADD-GTT command is processed by the EAGLE 5 ISS.

A proxy point code cannot be assigned to any point code that will be assigned to a global titletranslation.

Table 14: SEAS and EAGLE 5 ISS Global Title Translation Parameter Conversion

SSN

EAGLE 5ISS GTT

Parameter

PC/PCA

EAGLE 5ISS GTT

Parameter

RI

EAGLE 5ISS GTT

Parameter

XLAT

EAGLE 5ISS GTT

Parameter

SSN

SEAS GTTParameter

DPC

SEAS GTTParameter

RI

SEAS GTTParameter

NotSpecifiedxxx-xxx-xxxGTDPC000xxx-xxx-xxxG

002-255xxx-xxx-xxxSSNDPCSSN002-255xxx-xxx-xxxD

106910-6013-001 Revision A, March 2011


SSN

EAGLE 5ISS GTT

Parameter

PC/PCA

EAGLE 5ISS GTT

Parameter

RI

EAGLE 5ISS GTT

Parameter

XLAT

EAGLE 5ISS GTT

Parameter

SSN

SEAS GTTParameter

DPC

SEAS GTTParameter

RI

SEAS GTTParameter

002-255xxx-xxx-xxxGTDPCSSN002-255xxx-xxx-xxxG

NotSpecified*xxx-xxx-xxxSSNDPC000xxx-xxx-xxxD

* The MSU being translated already contains the subsystem number. The DPC is translated andreplaced, and the existing subsystem number in the MSU is unchanged and routed based on thenew DPC and the existing subsystem number.

General Notes:

• The SEAS RI=G parameter denotes global title routing, further global title translation is required.• The SEAS RI=D parameter denotes DPC routing, no further global title translation is required.• The EAGLE 5 ISS RI=GT parameter denotes further global title translation is required and uses

MTP routing.• The EAGLE 5 ISS RI=SSN parameter denotes final global title translation and uses MAP routing.• The EAGLE 5 ISS XLAT=DPC parameter indicates that the DPC & RI values in the MSU are to be

replaced.• The EAGLE 5 ISS XLAT=DPCSSN parameter indicates that the DPC, RI, & SSN values in the MSU

are to be replaced.• The EAGLE 5 ISS XLAT=DPCNGT parameter indicates that the DPC, RI, & TT values in the MSU

are to be replaced.

107910-6013-001 Revision A, March 2011


ToSheet 2

Enter theFLOW-THRU::::::"rtrv-ctrl-feat

:partnum=893015401"; command

Is the FlexibleGTT Load Sharingfeature enabled?

No

Yes

By default, the global titletranslation being added in thisprocedure is assigned to the

default MRN set.

Perform the "Adding a Global TitleTranslation " procedure in the Database

Administration Manual - Global TitleTranslation and add the global title

translation. Use the SEAS FLOW-THRUcommand with the EAGLE 5 ISS

commands.

Do you wishto assign this global

title translation to an MRN setother than the default

MRN set?

No

Yes

What is the routingindicator value for the global

title translation being added inthis procedure?

G(EAGLE 5 ISS

Value GT)

D(EAGLE 5 ISS

Value SSN)


default MAP set.


title translation to a MAP setother than the default

MAP set?

No

Yes

Sheet 1 of 6Figure 20: Adding a Global Title Translation

108910-6013-001 Revision A, March 2011


Enter theFLOW-THRU::::::"rtrv-tt";

command

Is the requiredtranslation type in the

database?

Perform the "Adding a Translation Type " procedure inthe Database Administration Manual - Global Title

Translation to add the translation type to the database.Use the SEAS FLOW-THRU command with the

EAGLE 5 ISS commands.

Yes

No

ToSheet 3

Enter the FLOW-THRU::::::"rtrv-feat”

command.

Is the EGTTfeature turned

on?

Yes

No

Do all theentries have default

values for the advancedGTT parameters? See

the note.

Yes

No

The translation type cannotbe assigned to the GTTentry. Choose another

translation type.

Note: The advanced GTT parameters and their defaultvalues are:

NAI = dflt – ITU GTT selectors onlyNP = dflt – ITU GTT selectors onlyCGSSN – dashesSELID = noneLSN=any

An ITU translation type must have an entry with the GTI=2and GTI=4 values, with the default values for the advancedGTT parameters.

An ANSI translation type must have an entry with the GTI=2value, with the default values for the advanced GTTparameters.

Enter theFLOW-THRU::::::"rtrv-ctrl-feat”

command.

Enter the FLOW-THRU::::::"rtrv-gttsel” command.

If the Origin-Based SCCP Routing feature is notenabled, and the Flexible Linkset Optional BasedRouting feature is not enabled and turned on, specifythis parameter with the rtrv-gttsel command.

:gttsn=<TTN value assigned translation type that willbe assigned to the GTT entry>

If only the Origin-Based SCCP Routing feature isenabled, specify these commands.

rtrv-gttsel:cdgtasn=<TTN value assigned translationtype that will be assigned to the GTT entry>

rtrv-gttsel:cggtasn=<TTN value assigned translationtype that will be assigned to the GTT entry>

If the Flexible Linkset Optional Based Routingfeature is enabled and turned on, specify thesecommands.

rtrv-gttsel:cdgttsn=<TTN value assigned translationtype that will be assigned to the GTT entry>

rtrv-gttsel:cggttsn=<TTN value assigned translationtype that will be assigned to the GTT entry>

ToSheet 3

FromSheet 1

Sheet 2 of 6

109910-6013-001 Revision A, March 2011


Are translationtypes that contain 11 – 16

different GTA lengths shownin the rtrv-tt output?

ToSheet 4

No

YesThe Support for 16

GTT Lengths in VGTTfeature is enabled and

turned on.

Are translationtypes that contain 2 – 10

different GTA lengths shownin the rtrv-tt output?

No Yes

The VGTT featureis turned on .

ToSheet 4

Will thetranslation type have more

than 10 different lengthGTAs assigned to it?

No Yes

FromSheet 2

No

Is theVGTT feature

on?

Yes

Are the correctservice modules

provisioned in the EAGLE 5 ISS?(See the Service Module and FeatureCombinations table in the Database

Administration Manual –Global TitleTranslation ) The correct service modules must be in the

EAGLE 5 ISS before the VGTT feature can beturned on. Refer to the Service Module andFeature Combinations table in the Database

Administration Manual – Global TitleTranslation to determine the service modules that

are required. If any service modules must bereplaced, contact the Customer Care Center

before replacing any service modules. Refer tothe “Customer Care Center” section in Chapter 1

for the contact information.

No

Yes

Will thetranslation type have more

than 10 different lengthGTAs assigned to it?

No

Yes

Will thetranslation type have morethan one different length

GTA assigned to it?

No

Yes

Enter theFLOW-THRU::::::"rtrv-card";

commandEnter the FLOW-

THRU::::::"chg-feat:vgtt=on"; command.

No

Is theSupport for 16 GTT

Lengths in VGTT featureis enabled and

turned on?

Yes

Perform the “Activating the Support for16 GTT Lengths in VGTT Feature”

procedure in the DatabaseAdministration Manual – Global TitleTranslation to enable and turn on theSupport for 16 GTT Lengths in VGTT

feature.

Use the SEAS FLOW-THRU commandwith the EAGLE 5 ISS commands.

Enter the FLOW-THRU::::::"rtrv-ctrl-feat

:partnum=893024801";command

ToSheet 4

Sheet 3 of 6

110910-6013-001 Revision A, March 2011


Is this global titletranslation a final global

title translation?

ToSheet 6

Yes

No

Display the routes in thedatabase.

Is the EAGLE5 ISS's true point codeto be used in the global

title translation?

Yes

No

ToSheet 6

FromSheet 3

Is therequired route inthe database?

Yes

No


to add the required route to thedatabase. A proxy point code cannotbe assigned to the point code that will

be assigned to the global titletranslation.

ToSheet 4

What is the currentmaximum number of global

title translations the EAGLE 5ISS can have?

Less than1,000,000

1,000,000

Will the number ofglobal title translations be more

than the current maximum numberof global title translations?

Perform the "Enabling the XGTTTable Expansion Controlled

Feature" procedure to enablethe XGTT Table Expansion

feature for either a quantity of400,000 or 1,000,000 global title

translations as required.

YesNo

Enter the FLOW-THRU::::::"rtrv-gtt:type=<translation type>";

command.

Sheet 4 of 6

111910-6013-001 Revision A, March 2011



title translation?

ToSheet 6

Yes

No

FromSheet 4


Yes

No

Perform the "Adding aRoute" procedure in Chapter3 of this manual to add the

required route to thedatabase. A proxy point code

cannot be assigned to thepoint code that will be

assigned to the global titletranslation.


this parameter.:dpc/dpca=<the DPC of the route>

A proxy point codecannot be assigned tothe point code that will

be assigned to theglobal title translation.


output?

Choose anotherroute to use insteadof the route whose

DPC contains aproxy point code.

Yes

No

Verify that the global titletranslation data has beenadded to the database.


command.

Enter theglobal title translation with these mandatory

parameter values.

Translation type

Global title address

ANSI point code from the routing table

Routing indicator G

Subsystem number = 000, or 002-255

Relative cost = 00-99 (The relative costvalue is not used in the EAGLE 5 ISSand is discarded when the EAGLE 5 ISSprocesses this command.)

The end global title address is optional and isonly required if entering a range of global title

addresses.

Was a newroute added on

Sheet 4?

Yes

No

Sheet 5 of 6

112910-6013-001 Revision A, March 2011


Is the matedapplication in the

database?

Yes

No

Go to the"Provisioning a MatedApplication" procedure

and add the matedapplication to the

database.

FromSheets 4

or 5


database.

Verify that the global titletranslation data has been

added to the database



Is the subsystemnumber 000 to be specified

with the global titletranslation?

Enter theglobal title translation with these

mandatory parameter values.Translation type


ANSI point code from the routingtable

Routing indicator D

Subsystem number = 000

Relative cost = 00-99 (The relativecost value is not used in the EAGLE5 ISS and is discarded when theEAGLE 5 ISS processes thiscommand.)

The end global title address is optionaland is only required if entering a range of

global title addresses.

Yes No

Is the EAGLE5 ISS's true point code tobe used in the global title

translation?

Yes

No

Display the EAGLE 5ISS's true point code.

Enter theglobal title translation with these

mandatory parameter values:Translation type


ANSI point code from the routingtable or the EAGLE 5 ISS's true pointcode

Routing indicator D

Subsystem number = 002-255




Sheet 6 of 6

Removing a Global Title Translation

This procedure is used to remove a global title translation from the database. This procedure uses theEAGLE 5 ISS commands rtrv-tt, rtrv-gtt, rtrv-feat, rtrv-gttset, rtrv-gta,rtrv-gttapath, and chg-db. For more information on this procedure, see “Removing a GlobalTitle Translation” in the Database Administration Manual - Global Title Translation.

If you wish to use the typei, typeis , typen, typens , typen24, or ttn parameter of the EAGLE5 ISS’s dlt-gtt command, perform the “Removing a Global Title Translation” procedure in theDatabase Administration Manual - Global Title Translation using the SEAS FLOW-THRU command withthe EAGLE 5 ISS commands.

113910-6013-001 Revision A, March 2011


The DPC and SSN parameters of the SEAS DLT-GTT command are not supported by the EAGLE 5 ISS.While these parameters must be specified with the SEAS DLT-GTT command, these parameters arediscarded when the SEAS DLT-GTT command is processed by the EAGLE 5 ISS.

Enter theFLOW-THRU::::::"rtrv-tt”

command.

Is theEGTT feature

on?

Yes

No

Enter theFLOW-THRU::::::"rtrv-gttset”

command with this parameter.:gttsn=<the TTN value

assigned to the translation typethat is assigned to the GTT

entry being removed>

What isthe NETDOM value

assigned to the entry thatyou wish to

remove?

ITU or Cross

ANSI

The GTT entry cannot beremoved with this procedure.

Perform the “Removing GlobalTitle Address Information”

procedure to remove the GTTentry.

ToSheet 2

Enter theFLOW-THRU::::::"rtrv-feat”

command.

Is theGTT feature

on?

This procedure cannotbe performed. There are

no GTT entries toremove.

Yes

No

Enter the FLOW-THRU::::::"rtrv-gta” command

with this parameter.:gttsn=<the TTN value

specified with the rtrv-gttsetcommand>

What isthe XLAT value assigned to

the entry that you wish toremove?

None

DPC,DPCNGT, or

DPCSSNToSheet 2

Enter theFLOW-THRU::::::"rtrv-gtt”

command with this parameter.:type/typea=<the translation typecontaining the GTT entry being

removed>

Sheet 1 of 2Figure 21: Removing a Global Title Translation from the SEAS Terminal

114910-6013-001 Revision A, March 2011


Is the range ofglobal title addresses

being split?

Yes

No

Will the numberof GTT entries exceed themaximum number of GTT

entries?

Less than1,000,000

1,000,000 What is themaximum number of global

title addresses?


Feature" procedure in the DatabaseAdministration Manual – GlobalTitle Translation to enable the

XGTT Table Expansion feature foreither a quantity of 400,000 or

1,000,000 global title translations asrequired.

Yes

No


:dest=fixed” command.

Remove the global titletranslation data in the

database.

Verify that the global title translationdata has been removed from the

database.

Enter the FLOW-THRU::::::"rtrv-gttapath”command with these parameters.:cdgttsn=<TTN value shown in the

rtrv-gtt output or the GTTSN value in thertrv-gta output on Sheet 1>

:cdgta=<GTA value shown in the rtrv-gttoutput or in the rtrv-gta output on Sheet 1>


No

Yes

FromSheet 1

Perform one of these proceduresin the Database Administration

Manual – Global TitleTranslation .

"Removing a GTT Action PathEntry” to remove the entriesdisplayed in the rtrv-gttapathoutput.

"Changing a GTT Action PathEntry” to change GTT set that isbeing referenced to the valuenone or to another GTT set forthe entries displayed in thertrv-gttapath output.

The range ofglobal titleaddresses

cannot be split.

Sheet 2 of 2

Changing a Global Title Translation

This procedure is used to change an existing global title translation in the database. This procedureuses the EAGLE 5 ISS commands rtrv-gtt, rtrv-mrn, rtrv-map, rtrv-tt, rtrv-dstn,rtrv-feat, rtrv-ctrl-feat, rtrv-gttsel, and chg-db. For more information on this procedure,see “Changing a Global Title Translation” in the Database Administration Manual - Global Title Translation.

The following parameters of the EAGLE 5 ISS’s chg-gtt command are not supported by SEAS:typei, typeis, typen, typens, typen24, pci, pcn, pcn24, ttn, xlat, gtmodid, force, mrnset,mapset, split, loopset, or cggtmod. SEAS does not support hexadecimal digits as the value ofthe global title address parameter. If you wish to use any of these parameters or use hexadecimal digits

115910-6013-001 Revision A, March 2011


as the value for the global title address parameter, perform the “Changing a Global Title Translation”procedure in the Database Administration Manual - Global Title Translation using the SEAS FLOW-THRUcommand with the EAGLE 5 ISS commands.

If the Flexible GTT Load Sharing feature is enabled, shown by the MRNSET field in the EAGLE 5 ISSrtrv-gtt output, and the routing indicator of the global title translation is G (the EAGLE 5 ISS valueGT), the global title translation can be changed in this procedure only if the global title translation isassigned to the default MRN set. All the attributes of the global title translation can be changed exceptfor the following:

• The MRNSET value cannot be changed.• The routing indicator value cannot be changed.• If the point code is changed, the new point code must be assigned to the default MRN set.

If the Flexible GTT Load Sharing feature is enabled, shown by the MAPSET field in the EAGLE 5 ISSrtrv-gtt output, and the routing indicator of the global title translation is D (the EAGLE 5 ISS valueSSN), the global title translation can be changed in this procedure only if the global title translation isassigned to the default MAP set. All the attributes of the global title translation can be changed exceptfor the following:

• The MAPSET value cannot be changed.• The routing indicator value cannot be changed.• If the point code is changed, the new point code must be assigned to the default MAP set.

The EAGLE 5 ISS XLAT parameter does not have a SEAS equivalent. When global title translationsare configured at the SEAS interface, the values for the SEAS parameters RI, DPC, and SSN, allmandatory parameters for the SEAS ADD-GTT and CHG-GTT commands, are converted to the EAGLE5 ISS parameters and values shown in Table 15: SEAS and EAGLE 5 ISS Global Title Translation ParameterConversion.


Table 15: SEAS and EAGLE 5 ISS Global Title Translation Parameter Conversion

SSN

EAGLE GTTParameter

PC/PCA

EAGLE GTTParameter

RI

EAGLE GTTParameter

XLAT

EAGLE GTTParameter

SSN

SEAS GTTParameter

DPC

SEAS GTTParameter

RI

SEAS GTTParameter



002-255xxx-xxx-xxxGTDPCSSN002-255xxx-xxx-xxxG

NotSpecified*xxx-xxx-xxxSSNDPC000xxx-xxx-xxxD

116910-6013-001 Revision A, March 2011


SSN

EAGLE GTTParameter

PC/PCA

EAGLE GTTParameter

RI

EAGLE GTTParameter

XLAT

EAGLE GTTParameter

SSN

SEAS GTTParameter

DPC

SEAS GTTParameter

RI

SEAS GTTParameter

* The MSU being translated already contains the subsystem number. The DPC is translated andreplaced, and the existing subsystem number in the MSU is unchanged and routed based on thenew DPC and the existing subsystem number.

General Notes:





are to be replaced.

The DPC, SSN and NRC parameters of the SEAS CHG-GTT command are not supported by the EAGLE5 ISS. While these parameters must be specified with the SEAS CHG-GTT command, these parametersare discarded when the SEAS CHG-GTT command is processed by the EAGLE 5 ISS.

The range of global title addresses assigned to a global title translation can be extended or reduced tocreate a new range of global title addresses. The range can be extended so long as the new range ofglobal title addresses does not overlap an existing range of global title addresses. The range can bereduced so long as the new end global title address parameter value is not smaller than the global titleaddress parameter value.

For example, a global title translation contains this range of global title addresses: 9194600000 -9194603000. The range of global title addresses can be extended to 9194604500 by specifying an endglobal title address value of 9194604500 parameter with the SEAS CHG-GTT command. However, ifanother range of global title addresses begins with the value 9194604000, the end global title addressvalue of 9194604500 cannot be specified with the SEAS CHG-GTT command as the new range createdwith the end global title address value of 9194604500 would overlap the range of global title addressesbeginning with the value 9194604000. In this situation, the maximum value for the end global titleaddress value would be 9194603999.

Using the same example, the range of global title addresses can be reduced to 9194600000 - 9194601500by specifying the end global title address value of 9194601500 with the SEAS CHG-GTT command. Thenew range must lie inside of the original range. You cannot create the range 9194595000 - 9194600000by specifying the end global title address value of 9194595000 parameter with the SEAS CHG-GTTcommand.

CAUTION: Changes to the range of global title addresses occur only if the both the globaltitle address and end global title address parameters are specified and the values for eitherof these parameters, or both parameters are different from the original values in the globaltitle translation. If the global title address and end global title address parameters are

117910-6013-001 Revision A, March 2011


specified for the global title translation being changed, and you do not wish to changeeither of these values, make sure the original global title address and end global titleaddress values are specified in the SEAS CHG-GTT command.

Enter theFLOW-THRU::::::"rtrv-tt";

command

Enter the FLOW-THRU::::::"rtrv-feat”

command.

Is the EGTTfeature turned

on?

Yes

No

Do all theentries have default

values for the advanced GTTparameters? See

the note.

Yes

No

The GTT entry cannot bechanged. Choose another GTT

entry to change.

Note: The advanced GTT parameters and their default values are:NAI = dflt – ITU GTT selectors onlyNP = dflt – ITU GTT selectors onlyCGSSN – dashesSELID = noneLSN=any

An ITU translation type must have an entry with the GTI=2 andGTI=4 values, with the default values for the advanced GTTparameters.

An ANSI translation type must have an entry with the GTI=2 value,with the default values for the advanced GTT parameters .

Enter the FLOW-THRU::::::"rtrv-ctrl-feat”

command.

Enter the FLOW-THRU::::::"rtrv-gttsel” command.

If the Origin-Based SCCP Routing feature is not enabled,and the Flexible Linkset Optional Based Routing feature isnot enabled and turned on, specify this parameter with thertrv-gttsel command.

:gttsn=<TTN value assigned translation type that isassigned to the GTT entry>

If only the Origin-Based SCCP Routing feature is enabled,specify these commands.

rtrv-gttsel:cdgtasn=<TTN value assigned translation typethat is assigned to the GTT entry>

rtrv-gttsel:cggtasn=<TTN value assigned translation typethat is assigned to the GTT entry>

If the Flexible Linkset Optional Based Routing feature isenabled and turned on, specify these commands.

rtrv-gttsel:cdgttsn=<TTN value assigned translation typethat is assigned to the GTT entry>

rtrv-gttsel:cggttsn=<TTN value assigned translation typethat is assigned to the GTT entry>

ToSheet 2

Sheet 1 of 8Figure 22: Changing a Global Title Translation

118910-6013-001 Revision A, March 2011


The attributes of the global titletranslation can be changed in thisprocedure with these exceptions:

The MRN set value cannot be changed.The routing indicator value cannot be

changed.If the point code assigned to the global

title translation is changed, the new pointcode must be assigned to the default

MRN set.

FromSheet 1

Is the new pointcode shown in the default

MRN set?

Yes

No

Is the point code inthe global title translation

being changed?

Yes

No

ToSheet 4


command with this EAGLE 5 ISSparameter::mrnset=dflt

Perform the “Provisioning MRN Entries”procedure in the Database AdministrationManual - Global Title Translation and add

the new point code to the default MRN set.Use the SEAS FLOW-THRU command with

the EAGLE 5 ISS commands.

Enter theFLOW-THRU::::::"rtrv-gtt"; command with

this EAGLE 5 ISS parameter.:type=<translation type from the previousstep containing the global title translation

you wish to change>

What is theMRNSET value?

DFLT

Is the MRNSETfield displayed in the

rtrv-gtt output?

Yes

No

What is the RIparameter value of the

global title translation youwish to change?

GT

SSN

This procedure can be performedonly on a global title translation

assigned to the default (DFLT) MRNset.

Either start this procedure again andselect a global title translation

assigned to the default MRN set, orperform the "Changing a Global Title

Translation " procedure in theDatabase Administration Manual -

Global Title Translation and changethe global title translation. Use theSEAS FLOW-THRU command with


A Numbered Valueor the Value NONE

ToSheet 5

ToSheet 3

Sheet 2 of 8

119910-6013-001 Revision A, March 2011


FromSheet 2



being changed?

Yes

No

ToSheet 4


Yes

No





:dpc/dpca=<the DPC of the route>


code that will be assignedto the global title

translation.


output?


proxy point code.

Yes No

Sheet 3 of 8

120910-6013-001 Revision A, March 2011


FromSheets 2

or 3


changed

Enter the FLOW-THRU::::::"chg-db:action=backup:dest=fixed"; command

Is the subsystemnumber 000 to be

specified with the globaltitle translation?

Yes

No

Change the global title translation withthese mandatory parameter values:

Translation typeGlobal title addressCurrent ANSI point code assigned to theglobal title address (See Note 1)Current subsystem number (See Note 1)

and these optional parameter values:

New ANSI point code from the routingtable (See Note 2)New subsystem number = 002-255

New routing indicator G

New relative cost = 00-99 (See Note 1)End global title address - only required ifspecifying a range of global titleaddresses. (See Note 3)

Change the global title translation withthese mandatory parameter values:

Translation typeGlobal title addressCurrent ANSI point code assigned to theglobal title address (See Note 1)Current subsystem number (See Note 1)


New ANSI point code from the routingtable (See Note 2)New subsystem number = 000



Notes:

1. The new relative cost, current point code, and current subsystem values arenot used in the EAGLE 5 ISS and are discarded when the EAGLE 5 ISSprocesses this command.

2. If the global title translation is assigned to the default MRN set (shown in thertrv-gtt output on Sheet 1) the new point code must be assigned to the defaultMRN set (shown in the rtrv-mrn output on Sheet 2). A proxy point code cannotbe assigned to the new point code of the global title translation.

3. The range of global title addresses assigned to a global title translation can beextended or reduced to create a new range of global title addresses. The rangecan be extended so long as the new range of global title addresses does notoverlap an existing range of global title addresses.

Changes to the range of global title addresses occur only if the both the globaltitle address and end global title address parameters are specified and thevalues for either of these parameters, or both parameters are different from theoriginal values in the global title translation. If the global title address and endglobal title address parameters are specified for the global title translation beingchanged, and you do not wish to change either of these values, make sure theoriginal global title address and end global title address values are specified inthe SEAS CHG-GTT command. The length of the end global title address mustbe the same as the length of the global title address.

Sheet 4 of 8

121910-6013-001 Revision A, March 2011


What is theMAPSET value?

DFLT

Is the MAPSET fielddisplayed in the rtrv-gtt

output?

Yes

No ToSheet 6

This procedure can be performed only ona global title translation assigned to the

default (DFLT) MAP set.Either start this procedure again and

select a global title translation assigned tothe default MAP set, or perform the

"Changing a Global Title Translation "procedure in the Database Administration

Manual - Global Title Translation andchange the global title translation. Usethe SEAS FLOW-THRU command with


A NumberedValue or theValue NONE


The MAP set value cannot bechanged.

The routing indicator value cannotbe changed.

If the point code and subsystemassigned to the global title

translation is changed, the newpoint code and subsystem must beassigned to the default MAP set.

FromSheet 2

ToSheet 7

Is the new pointcode and SSN shown in

the default MAP set?

Yes

No

Is the pointcode and SSN in theglobal title translation

being changed?

Yes

No ToSheet 7


command with this EAGLE 5 ISSparameter:

:mapset=dflt

Perform either the “Provisioning aMated Application” or “Changing a

Mated Application” procedures in theDatabase Administration Manual -

Global Title Translation and add thenew point code and SSN to the defaultMAP set. Use the SEAS FLOW-THRU

command with the EAGLE 5 ISScommands.

Sheet 5 of 8

122910-6013-001 Revision A, March 2011




title translation?

Yes

No


ToSheet 8

FromSheet 5


Yes

No




Enter the FLOW-THRU::::::"rtrv-dstn"; command with this

parameter::dpc/dpca=<the DPC of the route>



translation.


output?


proxy point code.

Yes No ToSheet 7

Sheet 6 of 8

123910-6013-001 Revision A, March 2011



database?

Yes

No

Go to the "Provisioning a MatedApplication" procedure and add

the mated application to thedatabase

FromSheets 5

or 6


database



Yes

No ToSheet 8

Is the MAPSET fielddisplayed in the rtrv-gtt

output?

Yes

No


changed



Change theglobal title translation with these mandatory

parameter values:Translation typeGlobal title addressCurrent ANSI point code assigned to theglobal title address (See Note1 on Sheet 8)Current subsystem number (See Note 1 onSheet 8)

and these optional parameter values:New ANSI point code from the routing table

(See Note 2 on Sheet 8)New subsystem number = 000New routing indicator DNew relative cost = 00-99 (See Note1 onSheet 8 )End global title address - only required ifspecifying a range of global title addresses.

(See Note 3 on Sheet 8)

Sheet 7 of 8

124910-6013-001 Revision A, March 2011


FromSheets 7


changed


Change theglobal title translation with these mandatory

parameter values:Translation typeGlobal title addressCurrent ANSI point code assigned to theglobal title address (See Note 1)Current subsystem number (See Note 1)


New ANSI point code from the routing tableor the EAGLE 5 ISS's true point code

(See Note 2)New subsystem number = 002-255

(See Note 2)New routing indicator D

New relative cost = 00-99 (See Note 1)End global title address - only required ifspecifying a range of global title addresses.

(See Note 3)

Notes:

1. The new relative cost, current point code, and current subsystem values are not used in the EAGLE 5 ISSand are discarded when the EAGLE 5 ISS processes this command.

2. If the global title translation is assigned to the default MAP set (shown in the rtrv-gtt output on Sheet 1),the new point code and SSN must be assigned to the default MAP set (shown in the rtrv-map output onSheet 5). A proxy point code cannot be assigned to the new point code of the global title translation.

3. The range of global title addresses assigned to a global title translation can be extended or reduced tocreate a new range of global title addresses. The range can be extended so long as the new range of globaltitle addresses does not overlap an existing range of global title addresses.

Changes to the range of global title addresses occur only if the both the global title address and end globaltitle address parameters are specified and the values for either of these parameters, or both parameters, aredifferent from the original values in the global title translation. If the global title address and end global titleaddress parameters are specified for the global title translation being changed, and you do not wish tochange either of these values, make sure the original global title address and end global title address valuesare specified in the SEAS CHG-GTT command. The length of the end global title address must be the sameas the length of the global title address.

Sheet 8 of 8

125910-6013-001 Revision A, March 2011


Chapter

5Gateway Screening (GWS) Configuration

Chapter 5, Gateway Screening (GWS) Configuration,describes the procedures used to administer gatewayscreening data.

Topics:

• Adding an Allowed Affected Point CodeScreen.....128

• Removing an Allowed Affected Point CodeScreen.....129

• Changing an Allowed Affected Point CodeScreen.....130

• Adding an Allowed Called Party AddressScreen.....131

• Removing an Allowed Called Party AddressScreen.....133

• Changing an Allowed Called Party AddressScreen.....136

• Adding an Allowed Translation Type Screen...138• Removing an Allowed Translation Type

Screen.....140• Changing an Allowed Translation Type

Screen.....141• Adding an Allowed Calling Party Address

Screen.....142• Removing an Allowed Calling Party Address

Screen.....146• Changing an Allowed Calling Party Address

Screen.....151• Adding an Allowed Affected Destination Field

Screen.....154• Removing an Allowed Affected Destination Field

Screen.....155• Changing an Allowed Affected Destination Field

Screen.....158• Adding a Blocked DPC Screen.....159• Removing a Blocked DPC Screen.....163• Changing a Blocked DPC Screen.....168• Adding an Allowed DPC Screen.....172• Removing an Allowed DPC Screen.....177

126910-6013-001 Revision A, March 2011

• Changing an Allowed DPC Screen.....181• Adding an Allowed SIO Screen.....186• Removing an Allowed SIO Screen.....193• Changing an Allowed SIO Screen.....196• Adding a Blocked OPC Screen.....203• Removing a Blocked OPC Screen.....209• Changing a Blocked OPC Screen.....211• Adding an Allowed OPC Screen.....216• Removing an Allowed OPC Screen.....222• Changing an Allowed OPC Screen.....223• Adding a Gateway Linkset.....229• Removing a Gateway Linkset.....239• Changing a Gateway Linkset.....240• Setting the Threshold for Reporting Gateway

Screening Activity.....250• Setting the Maximum Number of Gateway

Screening Rejected Messages.....251• Adding an Allowed ISUP Message Type

Screen.....252• Removing an Allowed ISUP Message Type

Screen.....253• Changing an Allowed ISUP Message Type

Screen.....256

127910-6013-001 Revision A, March 2011

Gateway Screening (GWS) ConfigurationDatabase Administration Manual - SEAS

Adding an Allowed Affected Point Code Screen

This procedure is used to add an allowed affected point code screen to the database. This procedureuses the EAGLE 5 ISS commands rtrv-feat, chg-feat, and chg-db. For more information onthis procedure, see “Adding an Allowed Affected Point Code Screen” in the Database AdministrationManual – Gateway Screening .

Note: Once the gateway screening feature is turned on with the chg-feat command, it cannot beturned off.

The gateway screening feature must be purchased before you turn the features on with the chg-featcommand. If you are not sure whether you have purchased the gateway screening feature, contactyour Tekelec Sales Representative or Account Representative.

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 the Database AdministrationManual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands:

• If the allowed affected point code screen being added to the database uses ITU-I point codes (withor 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-Npoint codes and cannot be used with SEAS.

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

Note: Before executing this procedure, make sure you have purchased the gateway screening feature.If you are not sure if you have purchased the gateway screening feature, contact your Tekelec SalesRepresentative or Account Representative.

128910-6013-001 Revision A, March 2011



command

Is the gatewayscreening feature

on?


:gws=on"; command

Yes

No

Display the Allowed AFTPCscreens in the database

Add the new AllowedAFTPC screen to the

database

Verify that the new AllowedAFTPC screen has beenadded to the database



Figure 23: Adding an Allowed Affected Point Code Screen from the SEAS Terminal

Removing an Allowed Affected Point Code Screen

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

If any of the following items are used in removing the allowed affected point code screen from thedatabase, perform the “Removing an Allowed Affected Point Code Screen” procedure in the DatabaseAdministration Manual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE5 ISS 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 pcstparameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bitITU-N point codes and cannot be used with SEAS.

• If gateway screening stop action sets are assigned to the screens referencing the allowed affectedpoint code screen being removed.

129910-6013-001 Revision A, March 2011



Go to the "Changing an AllowedCalled Party Address Screen"

procedure and change theAllowed CDPA screen with theNSFI equal to stop and no NSR

Display the Allowed CDPA screensthat reference the Allowed AFTPC

screen being removed

Do any screensreference the screen being

removed?

Will screeningstop?


procedure and change the AllowedCDPA screen with the NSFI equalto AFTPC and the NSR set to an

Allowed AFTPC screeningreference name not being removed

No

No

Yes

Yes



Verify that the Allowed AFTPCscreen has been removed

Remove the specifiedAllowed AFTPC screen

Figure 24: Removing an Allowed Affected Point Code Screen from the SEAS Terminal

Changing an Allowed Affected Point Code Screen

This procedure is used to change an allowed affected point code screen in the database. This procedureuses the EAGLE 5 ISS command chg-db. For more information on this procedure, see “Changing anAllowed Affected Point Code Screen” in the Database Administration Manual - Gateway Screening .

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 the DatabaseAdministration Manual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE5 ISS commands:

130910-6013-001 Revision A, March 2011


• 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 thepcst or ncpst parameters), or 24-bit ITU-N point codes. The pcst and ncpst parameters canbe 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 beingchanged.

Display the Allowed AFTPC screensin the database.

Change the AllowedAFTPC screen.

Verify that the new AllowedAFTPC screen has beenchanged in the database.



Figure 25: Changing an Allowed Affected Point Code Screen from the SEAS Terminal

Adding an Allowed Called Party Address Screen

This procedure is used to add an allowed called party address screen to the database. This procedureuses the EAGLE 5 ISS commands rtrv-feat, chg-feat, and chg-db. For more information onthis procedure, see “Adding an Allowed Called Party Address Screen” in the Database AdministrationManual - Gateway Screening .



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 the DatabaseAdministration Manual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE5 ISS commands:

• If the allowed called party address screen being added to the database uses ITU-I point codes (withor 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-Npoint codes and cannot be used with SEAS.

131910-6013-001 Revision A, March 2011


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



command


on?


:gws=on"; command

Yes

No

To Sheet2

Display the Allowed CDPAscreens in the database

Will screening stopwith this screen?

Yes

No

Add the new AllowedCDPA screen with theNSFI equal to STOP

Verify that the new AllowedCDPA screen has beenadded to the database



Sheet 1 of 2Figure 26: Adding an Allowed Called Party Address Screen from the SEAS Terminal

132910-6013-001 Revision A, March 2011



Is the requiredscreen in the

database

Verify that the new AllowedCDPA screen has beenadded to the database



Yes

No

FromSheet 1

Add the new Allowed CDPA screenwith these values:

NSFI equal to AFTPCNSR equal to the Allowed AFTPC

screening reference nameSSN equal to 1Specify the SCMGFID value

Go to the "Adding anAllowed Affected Point

Code Screen" procedureand add the required

screen

Is a newAllowed AFTPC screen

to be added to thedatabase?

Yes

No

Go to the "Changing an AllowedAffected Point Code Screen"procedure and change the

required screen

Sheet 2 of 2

Removing an Allowed Called Party Address Screen

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

If any of the following items are used in removing the allowed called party address screen from thedatabase, perform the “Removing an Allowed Called Party Address Screen” procedure in the DatabaseAdministration Manual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE5 ISS 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

133910-6013-001 Revision A, March 2011


parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bitITU-N point codes and cannot be used with SEAS.

• If gateway screening stop action sets are assigned to the screens referencing the allowed calledparty address screen being removed.


To Sheet2

Go to the "Changing an AllowedSIO Screen" procedure and

change the Allowed SIO screenwith the NSFI equal to stop and no

NSR

Display the Allowed SIO screensthat reference the Allowed CDPA



removed?

Will screeningstop?


change the Allowed SIO screenwith the NSFI equal to CDPA andthe NSR set to an Allowed CDPA

screening reference name notbeing removed

No

No

Yes

Yes

Sheet 1 of 3Figure 27: Removing an Allowed Called Party Address Screen from the SEAS Terminal

134910-6013-001 Revision A, March 2011


To Sheet3

Go to the "Changing an AllowedCalling Party Address Screen"

procedure and change theAllowed CGPA screen with theNSFI equal to stop and no NSR

Display the Allowed CGPA screensthat reference the Allowed CDPA



removed?

Will screeningstop?


procedure and change the AllowedCGPA screen with the NSFI equalto CDPA and the NSR set to an

Allowed CDPA screening referencename not being removed

No

No

Yes

Yes

FromSheet 1

Sheet 2 of 3

135910-6013-001 Revision A, March 2011


Go to the "Changing an AllowedTranslation Type Screen "procedure and change the

Allowed TT screen with the NSFIequal to stop and no NSR

Display the Allowed TT screens thatreference the Allowed CDPA screen

being removed


removed?

Will screeningstop?

Go to the "Changing an AllowedTranslation Type Screen "

procedure and change the AllowedTT screen with the NSFI equal to

CDPA and the NSR set to anAllowed CDPA screening reference

name not being removed

No

No

Yes

Yes

FromSheet 2



Verify that the Allowed CDPAscreen has been removed

Remove the specifiedAllowed CDPA screen

Sheet 3 of 3

Changing an Allowed Called Party Address Screen

This procedure is used to change an allowed called party address screen in the database. This procedureuses the EAGLE 5 ISS command . For more information on this procedure, see “Changing an AllowedCalled Party Address Screen” in the Database Administration Manual - Gateway Screening.

If any of the following items are used in changing the allowed called party address screen in thedatabase, perform the “Changing an Allowed Called Party Address Screen” procedure in the DatabaseAdministration Manual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5ISS 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

136910-6013-001 Revision A, March 2011


pcst or npcst parameters), or 24-bit ITU-N point codes. The pcst and npcst parameters canbe 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 beingchanged.

Display the Allowed CDPAscreens in the database.


Yes

No

Change the Allowed CDPAscreen with the NSFI equal

to STOP.

Verify that the new AllowedCDPA screen has been

changed in the database.





database

Verify that the AllowedCDPA screen has been

changed



Yes

No

Change the Allowed CDPAscreen with these values:

NSFI equal to AFTPCNSR equal to the Allowed AFTPC

screening reference nameSSN equal to 1Specify the SCMGFID value

Go to the "Adding anAllowed Affected Point

Code Screen" procedureand add the required

screen

Is a newAllowed AFTPC screen


Yes

No

Go to the "Changing an AllowedAffected Point Code Screen"procedure and change the

required screen

Figure 28: Changing an Allowed Called Party Address Screen from the SEAS Terminal

137910-6013-001 Revision A, March 2011


Adding an Allowed Translation Type Screen

This procedure is used to add an allowed translation type screen to the database. This procedure usesthe EAGLE 5 ISS commands rtrv-feat, chg-feat, and chg-db. For more information on thisprocedure, see “Adding an Allowed Translation Type Screen” in the Database Administration Manual- Gateway Screening .



If gateway screening stop action sets are to be assigned to the allowed translation type screen beingadded to the database, perform the “Adding an Allowed Translation Type Screen” procedure in theDatabase Administration Manual - Gateway Screening using the SEAS FLOW-THRU command with theEAGLE 5 ISS commands.


138910-6013-001 Revision A, March 2011



command


on?


:gws=on"; command

Yes

No

To Sheet2

Display the Allowed TTscreens in the database


Yes

No

Add the new Allowed TTscreen with the NSFI equal

to STOP

Verify that the new AllowedTT screen has been added

to the database



Sheet 1 of 2Figure 29: Adding an Allowed Translation Type Screen from the SEAS Terminal

139910-6013-001 Revision A, March 2011




database

Verify that the new AllowedTT screen has been added

to the database



Yes

No

FromSheet 1

Add the new Allowed TT screenwith the NSFI equal to CDPA and

the NSR equal to the AllowedCDPA screening reference name

Go to the "Adding anAllowed Called Party

Address Screen"procedure and add the

required screen

Is a newAllowed CDPA screen


Yes

No


procedure and change therequired screen

Sheet 2 of 2

Removing an Allowed Translation Type Screen

This procedure is used to remove an allowed translation type screen from the database. This procedureuses the EAGLE 5 ISS command chg-db. For more information on this procedure, see “Removingan Allowed Translation Type Screen” in the Database Administration Manual - Gateway Screening .

If gateway screening stop action sets are assigned to the screens referencing the allowed translationtype screen being removed from the database, perform the “Removing an Allowed Translation TypeScreen” procedure in the Database Administration Manual - Gateway Screening using the SEASFLOW-THRU command with the EAGLE 5 ISS commands:

140910-6013-001 Revision A, March 2011




procedure and change theAllowed CGPA screen with theNSFI equal to stop and no NSR

Display the Allowed CGPA screensthat reference the Allowed TT screen

being removed


removed?

Will screeningstop?


procedure and change the AllowedCGPA screen with the NSFI equal

to TT and the NSR set to anAllowed TT screening reference


No

No

Yes

Yes



Verify that the Allowed TTscreen has been removed

Remove the specifiedAllowed TT screen

Figure 30: Removing an Allowed Translation Type Screen from the SEAS Terminal

Changing an Allowed Translation Type Screen

This procedure is used to change an allowed translation type screen in the database. This procedureuses the EAGLE 5 ISS command . For more information on this procedure, see “Changing an AllowedTranslation Type Screen” in the Database Administration Manual - Gateway Screening.

If gateway screening stop action sets are to be assigned to the allowed translation type screen beingchanged in the database, perform the “Changing an Allowed Translation Type Screen” procedure inthe Database Administration Manual - Gateway Screening using the SEAS FLOW-THRU command withthe EAGLE 5 ISS commands.

141910-6013-001 Revision A, March 2011


Display the Allowed TT screensin the database.


Yes

No

Change the Allowed TTscreen with the NSFI equal

to STOP.

Verify that the new AllowedTT screen has been changed

in the database.





database

Verify that the Allowed TTscreen has been changed



Yes

No

Change the Allowed TT screen withthe NSFI equal to CDPA and theNSR equal to the Allowed CDPA

screening reference name



required screen



Yes

No



Figure 31: Changing an Allowed Translation Type Screen from the SEAS Terminal

Adding an Allowed Calling Party Address Screen

This procedure is used to add an allowed calling party address screen to the database. This procedureuses the EAGLE 5 ISS commands rtrv-feat, chg-feat, and chg-db. For more information onthis procedure, see “Adding an Allowed Calling Party Address Screen” in the Database AdministrationManual - Gateway Screening .

142910-6013-001 Revision A, March 2011




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 the DatabaseAdministration Manual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE5 ISS 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 pcstparameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bitITU-N point codes and cannot be used with SEAS.

• If gateway screening stop action sets are assigned to the allowed calling party address screen beingadded.

• If you wish to use the sccpmt parameter of the EAGLE 5 ISS command ent-scr-cgpa.


143910-6013-001 Revision A, March 2011



command


on?


:gws=on"; command

Yes

No

Display the Allowed CGPAscreens in the database


Yes

No

Add the new AllowedCGPA screen with theNSFI equal to STOP

Verify that the new AllowedCGPA screen has beenadded to the database



To Sheet3

To Sheet2

What is theNSFI of the next screen

in the gateway screeningprocess?

TT

CDPA

Sheet 1 of 3Figure 32: Adding an Allowed Calling Party Address Screen from the SEAS Terminal

144910-6013-001 Revision A, March 2011




database




Yes

No

FromSheet 1

Add the new Allowed CGPA screenwith the NSFI equal to TT and the

NSR equal to the Allowed TTscreening reference name. Therouting indicator value must beeither 0 (route on the global title

address) or *.

Go to the "Adding anAllowed Translation Type

Screen" procedure and addthe required screen

Is a newAllowed TT screento be added to the

database?

Yes

No


required screen

Sheet 2 of 3

145910-6013-001 Revision A, March 2011




database




Yes

No

FromSheet 1

Add the new Allowed CGPA screenwith the NSFI equal to CDPA and

the NSR equal to the AllowedCDPA screening reference name .

The routing indicator value must beeither 1 (route on the DPC and

SSN in the CDPA) or *.



required screen



Yes

No



Sheet 3 of 3

Removing an Allowed Calling Party Address Screen

This procedure is used to remove an allowed calling party address screen from the database. Thisprocedure uses the EAGLE 5 ISS command chg-db. For more information on this procedure, see“Removing an Allowed Calling Party Address Screen” in the Database Administration Manual -Gateway Screening .

If any of the following items are used in removing the allowed calling party address screen from thedatabase, perform the “Removing an Allowed Calling Party Address Screen” procedure in the DatabaseAdministration Manual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE5 ISS 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

146910-6013-001 Revision A, March 2011


parameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bitITU-N point codes and cannot be used with SEAS.

• If gateway screening stop action sets are assigned to the screens referencing the allowed callingparty address screen being removed.

• If you wish to use the sccpmt parameter of the EAGLE 5 ISS command dlt-scr-cgpa.


To Sheet2

Go to the "Changing an AllowedOPC Screen" procedure and

change the Allowed OPC screenwith the NSFI equal to stop and no

NSR

Display the Allowed OPC screensthat reference the Allowed CGPA



removed?

Will screeningstop?


change the Allowed OPC screenwith the NSFI equal to CGPA andthe NSR set to an Allowed CGPA


No

No

Yes

Yes

Sheet 1 of 5Figure 33: Removing an Allowed Calling Party Address Screen from the SEAS Terminal

147910-6013-001 Revision A, March 2011


To Sheet3

Go to the "Changing a BlockedOPC Screen" procedure and

change the Blocked OPC screenwith the NSFI equal to stop and no

NSR

Display the Blocked OPC screensthat reference the Allowed CGPA



removed?

Will screeningstop?


change the Blocked OPC screenwith the NSFI equal to CGPA andthe NSR set to an Allowed CGPA


No

No

Yes

Yes

FromSheet 1

Sheet 2 of 5

148910-6013-001 Revision A, March 2011


To Sheet4



NSR

Display the Allowed SIO screens thatreference the Allowed CGPA screen

being removed


removed?

Will screeningstop?


change the Allowed SIO screenwith the NSFI equal to CGPA andthe NSR set to an Allowed CGPA


No

No

Yes

Yes

FromSheet 2

Sheet 3 of 5

149910-6013-001 Revision A, March 2011


Go to the "Changing an AllowedDPC Screen" procedure and

change the Allowed DPC screenwith the NSFI equal to stop and no

NSR

Display the Allowed DPC screensthat reference the Allowed CGPA



removed?

Will screeningstop?


change the Allowed DPC screenwith the NSFI equal to CGPA andthe NSR set to an Allowed CGPA


No

No

Yes

Yes

FromSheet 3

To Sheet5

Sheet 4 of 5

150910-6013-001 Revision A, March 2011


Go to the "Changing a BlockedDPC Screen" procedure and

change the Blocked DPC screenwith the NSFI equal to stop and no

NSR

Display the Blocked DPC screensthat reference the Allowed CGPA



removed?

Will screeningstop?


change the Blocked DPC screenwith the NSFI equal to CGPA andthe NSR set to an Allowed CGPA


No

No

Yes

Yes

FromSheet 4



Verify that the Allowed CGPAscreen has been removed

Remove the specifiedAllowed CGPA screen

Sheet 5 of 5

Changing an Allowed Calling Party Address Screen

This procedure is used to change an allowed calling party address screen in the database. This procedureuses the EAGLE 5 ISS command chg-db. For more information on this procedure, see “Changing anAllowed Calling Party Address Screen” in the Database Administration Manual - Gateway Screening.

If any of the following items are used in changing the allowed calling party address screen in thedatabase, perform the “Changing an Allowed Calling Party Address Screen” procedure in the DatabaseAdministration Manual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE5 ISS 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

151910-6013-001 Revision A, March 2011



• If gateway screening stop action sets are assigned to the allowed calling party address screen beingchanged.

• If you wish to use the sccpmt and nsccpmt parameters of the EAGLE 5 ISS commandchg-scr-cgpa.

Display the Allowed CGPAscreens in the database.

ToSheet 2


Yes

No

Change the Allowed CGPAscreen with the NSFI equal

to STOP.

Verify that the new AllowedCGPA screen has been




ToSheet 3



TT

CDPA

Sheet 1 of 3Figure 34: Changing an Allowed Calling Party Address Screen from the SEAS Terminal

152910-6013-001 Revision A, March 2011




database

Verify that the AllowedCGPA screen has been

changed



Yes

No

FromSheet 1

Change the Allowed CGPA screenwith the NSFI equal to TT and the

NSR equal to the Allowed TTscreening reference name. Therouting indicator value must beeither 0 (route on the global title

address) or *.

Go to the "Adding anAllowed Translation Type

Screen" procedure and addthe required screen

Is a newAllowed TT screento be added to the

database?

Yes

No


required screen

Sheet 2 of 3

153910-6013-001 Revision A, March 2011




database

Verify that the AllowedCGPA screen has been

changed



Yes

No

FromSheet 1

Change the Allowed CGPA screenwith the NSFI equal to CDPA and

the NSR equal to the AllowedCDPA screening reference name .

The routing indicator value must beeither 1 (route on the DPC and

SSN in the CDPA) or *.



required screen



Yes

No



Sheet 3 of 3

Adding an Allowed Affected Destination Field Screen

This procedure is used to remove an allowed affected destination field screen to the database. Thisprocedure uses the EAGLE 5 ISS commands rtrv-feat, chg-feat, and chg-db. For moreinformation on this procedure, see “Adding an Allowed Affected Destination Field Screen” in theDatabase Administration Manual - Gateway Screening .



154910-6013-001 Revision A, March 2011


If you wish to use any of these items in adding the allowed affected destination field screen to thedatabase, perform the “Adding an Allowed Affected Destination Field Screen” procedure in theDatabase Administration Manual - Gateway Screening using the SEAS FLOW-THRU command with theEAGLE 5 ISS 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 pcstparameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bitITU-N point codes and cannot be used with SEAS.

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



command


on?


:gws=on"; command

Yes

No

Display the Allowed DESTFLDscreens in the database

Add the new AllowedDESTFLD screen to the

database

Verify that the new AllowedDESTFLD screen has been




Figure 35: Adding an Allowed Affected Destination Screen from the SEAS Terminal

Removing an Allowed Affected Destination Field Screen

This procedure is used to remove an allowed affected destination screen to the database. This procedureuses the EAGLE 5 ISS command chg-db. For more information on this procedure, see “Removing

155910-6013-001 Revision A, March 2011


an Allowed Affected Destination Field Screen” in the Database Administration Manual - GatewayScreening .

If any of the following items are used in removing the allowed affected destination screen from thedatabase, perform the “Removing an Allowed Affected Destination Field Screen” procedure in theDatabase Administration Manual - Gateway Screening using the SEAS FLOW-THRU command with theEAGLE 5 ISS 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 pcstparameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bitITU-N point codes and cannot be used with SEAS.

• If gateway screening stop action sets are assigned to the screens referencing the allowed affecteddestination screen being removed.


To Sheet2



NSR

Display the Allowed SIO screens thatreference the Allowed DESTFLD



removed?

Will screeningstop?


change the Allowed SIO screenwith the NSFI equal to DESTFLDand the NSR set to an AllowedDESTFLD screening reference


No

No

Yes

Yes

Sheet 1 of 3Figure 36: Removing an Allowed Affected Destination Screen from the SEAS Terminal

156910-6013-001 Revision A, March 2011


To Sheet3



NSR

Display the Allowed DPC screensthat reference the Allowed DESTFLD



removed?

Will screeningstop?


change the Allowed DPC screenwith the NSFI equal to DESTFLDand the NSR set to an AllowedDESTFLD screening reference


No

No

Yes

Yes

FromSheet 1

Sheet 2 of 3

157910-6013-001 Revision A, March 2011




NSR

Display the Blocked DPC screensthat reference the Allowed DESTFLD



removed?

Will screeningstop?


change the Blocked DPC screenwith the NSFI equal to DESTFLDand the NSR set to an AllowedDESTFLD screening reference


No

No

Yes

Yes

FromSheet 2



Verify that the Allowed DESTFLDscreen has been removed

Remove the specifiedAllowed DESTFLD screen

Sheet 3 of 3

Changing an Allowed Affected Destination Field Screen

This procedure is used to remove an allowed affected destination field screen to the database. Thisprocedure uses the EAGLE 5 ISS command chg-db. For more information on this procedure, see“Changing an Allowed Affected Destination Field Screen” in the Database Administration Manual -Gateway Screening .

If any of the following items are used in changing the allowed affected destination field screen in thedatabase, perform the “Changing an Allowed Affected Destination Field Screen” procedure in theDatabase Administration Manual - Gateway Screening using the SEAS FLOW-THRU command with theEAGLE 5 ISS commands:

• If the allowed affected destination field screen being changed in the database uses ITU-I pointcodes (with or without the pcst or npcst parameters), 14-bit ITU-N point codes (with or without

158910-6013-001 Revision A, March 2011


the pcst or npcst parameters), or 24-bit ITU-N point codes. The pcst and npcst parameterscan 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 screenbeing changed.

Display the Allowed DESTFLDscreens in the database.

Change the AllowedDESTFLD screen.

Verify that the new AllowedDESTFLD screen has beenchanged in the database.



Figure 37: Changing an Allowed Affected Destination Screen from the SEAS Terminal

Adding a Blocked DPC Screen

This procedure is used to add a blocked destination point code screen to the database. This procedureuses the EAGLE 5 ISS commands rtrv-feat, chg-feat, and chg-db. For more information onthis procedure, see “Adding a Blocked DPC Screen” in the Database Administration Manual - GatewayScreening .



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 the Database Administration Manual -Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS 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 pcstparameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bitITU-N point codes and cannot be used with SEAS.

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

159910-6013-001 Revision A, March 2011




command

Is the gatewayscreening feature on?


:gws=on"; command

Yes

No

Display the Blocked DPCscreens in the database


Yes

No

Verify that the new BlockedDPC screen has been added to

the database



Is this entrythe first entry for

this screen?

YesNo

Add the new Blocked DPCscreen with the NSFI equal

to FAIL

Add the new Blocked DPCscreen with the NSFI equal toSTOP and the value C for the

point code

To Sheet2

To Sheet3



CGPA

DESTFLD

To Sheet4

ISUP

Sheet 1 of 4Figure 38: Adding a Blocked DPC Screen from the SEAS Terminal

160910-6013-001 Revision A, March 2011


Is the requiredscreen in thedatabase?

Verify that the new BlockedDPC screen has been added

to the database



Yes

No

FromSheet 1

Go to the "Adding an AllowedAffected Destination Field

Screen" procedure and add therequired screen

Add the new Blocked DPC screen withthe NSFI equal to DESTFLD and theNSR equal to the Allowed DESTFLD



Is a newAllowed DESTFLD

screen to be added tothe database?

Yes

No

Go to the "Changing an AllowedAffected Destination Field

Screen" procedure and changethe required screen

Sheet 2 of 4

161910-6013-001 Revision A, March 2011




to the database



Yes

No

FromSheet 1

Go to the "Adding an AllowedCalling Party Address Screen"

procedure and add the requiredscreen

Add the new Blocked DPC screen withthe NSFI equal to CGPA and the NSRequal to the Allowed CGPA screening

reference name


Is a newAllowed CGPA screen


Yes

No



Sheet 3 of 4

162910-6013-001 Revision A, March 2011




to the database



Yes

No

FromSheet 1

Go to the "Adding an AllowedISUP Message Type Screen"


Add the new Blocked DPC screen withthe NSFI equal to ISUP and the NSRequal to the Allowed ISUP screening

reference name

Display the Allowed ISUPscreens in the database

Is a newAllowed ISUP screen


Yes

No

Go to the "Changing an AllowedISUP Message Type Screen"


Sheet 4 of 4

Removing a Blocked DPC Screen

This procedure is used to remove a blocked destination point code screen from the database. Thisprocedure uses the EAGLE 5 ISS command chg-db. For more information on this procedure, see“Removing a Blocked DPC Screen” in the Database Administration Manual - Gateway Screening .

If any of the following items are used in removing the blocked destination point code screen from thedatabase, perform the “Removing a Blocked DPC Screen” procedure in the Database AdministrationManual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands:

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

• If gateway screening stop action sets are assigned to the screens referencing the blocked destinationpoint code screen being removed.

163910-6013-001 Revision A, March 2011



To Sheet2

Go to the "Changing a GatewayLinkset" procedure and change

the gateway linkset with the NSFIequal to stop and no NSR

Display the gateway linksets thatreference the Blocked DPC screen

being removed

Will screeningstop?

Go to the "Changing a GatewayLinkset" procedure and change the

gateway linkset with a differentNSFI and NSR combination

No

No

Yes

Yes

Do any gatewaylinksets reference the

screen beingremoved?

Sheet 1 of 5Figure 39: Removing a Blocked DPC Screen from the SEAS Terminal

164910-6013-001 Revision A, March 2011


To Sheet3

Go to the "Changing an AllowedOPC Screen" procedure to


NSR

Display the Allowed OPC screensthat reference the Blocked DPC



removed?

Will screeningstop?

Go to the "Changing an AllowedOPC Screen" procedure to changethe Allowed OPC screen with theNSFI equal to BLKDPC and the

NSR set to an Blocked DPCscreening reference name

not being removed

No

No

Yes

Yes

FromSheet 1

Sheet 2 of 5

165910-6013-001 Revision A, March 2011


To Sheet4

Go to the "Changing a BlockedOPC Screen" procedure to


NSR

Display the Blocked OPC screensthat reference the Blocked DPC



removed?

Will screeningstop?

Go to the "Changing a BlockedOPC Screen" procedure to changethe Blocked OPC screen with theNSFI equal to BLKDPC and the


not being removed

No

No

Yes

Yes

FromSheet 2

Sheet 3 of 5

166910-6013-001 Revision A, March 2011


To Sheet5

Go to the "Changing an AllowedSIO Screen" procedure to changethe Allowed SIO screen with theNSFI equal to stop and no NSR

Display the Allowed SIO screens thatreference the Blocked DPC screen

being removed


removed?

Will screeningstop?

Go to the "Changing an AllowedSIO Screen" procedure to changethe Allowed SIO screen with theNSFI equal to BLKDPC and the


not being removed

No

No

Yes

Yes

FromSheet 3

Sheet 4 of 5

167910-6013-001 Revision A, March 2011


Go to the "Changing an AllowedDPC Screen" procedure to


NSR

Display the Allowed DPC screensthat reference the Blocked DPC



removed?

Will screeningstop?

Go to the "Changing an AllowedDPC Screen" procedure to changethe Allowed DPC screen with theNSFI equal to BLKDPC and the

NSR set to an Blocked DPCscreening reference name not

being removed

No

No

Yes

Yes

FromSheet 4



Verify that the Blocked DPCscreen has been removed

Remove the specifiedBlocked DPC screen

Sheet 5 of 5

Changing a Blocked DPC Screen

This procedure is used to change a blocked destination point code screen in the database. This procedureuses the EAGLE 5 ISS command chg-db. For more information on this procedure, see “Changing aBlocked DPC Screen” in the Database Administration Manual - Gateway Screening .

If any of the following items are used in changing the blocked destination point code screen in thedatabase, perform the “Changing a Blocked DPC Screen” procedure in the Database AdministrationManual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS 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 thepcst or npcst parameters), or 24-bit ITU-N point codes. The pcst and npcst parameters canbe used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.

168910-6013-001 Revision A, March 2011


• If gateway screening stop action sets are assigned to the blocked destination point code screenbeing changed.


Yes

No

Verify that the new BlockedDPC screen has been





this screen?

YesNo

Change the Blocked DPCscreen with the NSFI equal

to FAIL.

Change the Blocked DPCscreen with the NSFI equalto STOP and the value C

for the point code.

To Sheet2

To Sheet3



CGPA

DESTFLD

Display the Blocked DPCscreens in the database.

To Sheet4

ISUP

Sheet 1 of 4Figure 40: Changing a Blocked DPC Screen from the SEAS Terminal

169910-6013-001 Revision A, March 2011



Verify that the Blocked DPCscreen has been changed



Yes

No

FromSheet 1



Change the Blocked DPC screen withthe NSFI equal to DESTFLD and theNSR equal to the Allowed DESTFLD





Yes

No



Sheet 2 of 4

170910-6013-001 Revision A, March 2011






Yes

No

FromSheet 1



Change the Blocked DPC screen withthe NSFI equal to CGPA and the NSRequal to the Allowed CGPA screening

reference name




Yes

No



Sheet 3 of 4

171910-6013-001 Revision A, March 2011






Yes

No

FromSheet 1



Change the Blocked DPC screen withthe NSFI equal to ISUP and the NSRequal to the Allowed ISUP screening

reference name




Yes

No



Sheet 4 of 4

Adding an Allowed DPC Screen

This procedure is used to add an allowed destination point code screen to the database. This procedureuses the EAGLE 5 ISS commands rtrv-feat, chg-feat, and chg-db. For more information onthis procedure, see “Adding an Allowed DPC Screen” in the Database Administration Manual - GatewayScreening .



172910-6013-001 Revision A, March 2011


If you wish to use any of these items in adding the allowed destination point code screen to thedatabase, perform the “Adding an Allowed DPC Screen” procedure in the Database AdministrationManual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS 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 pcstparameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bitITU-N point codes and cannot be used with SEAS.

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



command



:gws=on"; command

Yes

No

Display the Allowed DPCscreens in the database


Yes

No

Add the new Allowed DPCscreen with the NSFI equal

to STOP

Verify that the new AllowedDPC screen has beenadded to the database



To Sheet3

To Sheet4

To Sheet2



BLKDPC

CGPA

DESTFLD

To Sheet5

ISUP

Sheet 1 of 5Figure 41: Adding an Allowed DPC Screen from the SEAS Terminal

173910-6013-001 Revision A, March 2011



Verify that the new AllowedDPC screen has been added

to the database



Yes

No

FromSheet 1

Go to the "Adding a BlockedDPC Screen" procedure and add

the required screen

Add the new Allowed DPC screen withthe NSFI equal to BLKDPC and the

NSR equal to the Blocked DPCscreening reference name


Is a newBlocked DPC screen


Yes

No

Go to the "Changing a BlockedDPC Screen" procedure andchange the required screen

Sheet 2 of 5

174910-6013-001 Revision A, March 2011




to the database



Yes

No

FromSheet 1



Add the new Allowed DPC screen withthe NSFI equal to DESTFLD and theNSR equal to the Allowed DESTFLD





Yes

No



Sheet 3 of 5

175910-6013-001 Revision A, March 2011




to the database



Yes

No

FromSheet 1



Add the new Allowed DPC screen withthe NSFI equal to CGPA and the NSRequal to the Allowed CGPA screening

reference name




Yes

No



Sheet 4 of 5

176910-6013-001 Revision A, March 2011




to the database



Yes

No

FromSheet 1



Add the new Allowed DPC screen withthe NSFI equal to ISUP and the NSRequal to the Allowed ISUP screening

reference name




Yes

No



Sheet 5 of 5

Removing an Allowed DPC Screen

This procedure is used to remove an allowed destination point code screen from the database. Thisprocedure uses the EAGLE 5 ISS command chg-db. For more information on this procedure, see“Removing an Allowed DPC Screen” in the Database Administration Manual - Gateway Screening .

If any of the following items are used in removing the allowed destination point code screen from thedatabase, perform the “Removing an Allowed DPC Screen” procedure in the Database AdministrationManual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands:

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

• If gateway screening stop action sets are assigned to the screens referencing the allowed destinationpoint code screen being removed.

177910-6013-001 Revision A, March 2011



To Sheet2



Display the gateway linksets thatreference the Allowed DPC screen

being removed

Will screeningstop?



No

No

Yes

Yes



Sheet 1 of 4Figure 42: Removing an Allowed DPC Screen from the SEAS Terminal

178910-6013-001 Revision A, March 2011


To Sheet3



NSR

Display the Allowed OPC screensthat reference the Allowed DPC



removed?

Will screeningstop?


change the Allowed OPC screenwith the NSFI equal to DPC andthe NSR set to an Allowed DPC

screening reference namenot being removed

No

No

Yes

Yes

FromSheet 1

Sheet 2 of 4

179910-6013-001 Revision A, March 2011


To Sheet4



NSR

Display the Blocked OPC screensthat reference the Allowed DPC



removed?

Will screeningstop?


change the Blocked OPC screenwith the NSFI equal to DPC andthe NSR set to an Allowed DPC

screening reference namenot being removed

No

No

Yes

Yes

FromSheet 2

Sheet 3 of 4

180910-6013-001 Revision A, March 2011




NSR

Display the Allowed SIO screens thatreference the Allowed DPC screen

being removed


removed?

Will screeningstop?


change the Allowed SIO screenwith the NSFI equal to DPC andthe NSR set to an Allowed DPCscreening reference name not

being removed

No

No

Yes

Yes

FromSheet 3



Verify that the Allowed DPCscreen has been removed

Remove the specifiedAllowed DPC screen

Sheet 4 of 4

Changing an Allowed DPC Screen

This procedure is used to change an allowed destination point code screen in the database. Thisprocedure uses the EAGLE 5 ISS command chg-db. For more information on this procedure, see“Changing an Allowed DPC Screen” in the Database Administration Manual - Gateway Screening .

If any of the following items are used in changing the allowed destination point code screen in thedatabase, perform the “Changing an Allowed DPC Screen” procedure in the Database AdministrationManual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS 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 thepcst or npcst parameters), or 24-bit ITU-N point codes. The pcst and npcst parameters canbe used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.

181910-6013-001 Revision A, March 2011


• If gateway screening stop action sets are assigned to the allowed destination point code screenbeing changed.

Display the Allowed DPCscreens in the database.

To Sheet2


Yes

No

Change the Allowed DPCscreen with the NSFI equal

to STOP.

Verify that the new AllowedDPC screen has been




To Sheet4

To Sheet3



BLKDPC

DESTFLD

CGPA

To Sheet5

ISUP

Sheet 1 of 5Figure 43: Changing an Allowed DPC Screen from the SEAS Terminal

182910-6013-001 Revision A, March 2011



Verify that the Allowed DPCscreen has been changed



Yes

No

FromSheet 1


the required screen

Change the Allowed DPC screen withthe NSFI equal to BLKDPC and the





Yes

No


Sheet 2 of 5

183910-6013-001 Revision A, March 2011






Yes

No

FromSheet 1



Change the Allowed DPC screen withthe NSFI equal to DESTFLD and theNSR equal to the Allowed DESTFLD





Yes

No



Sheet 3 of 5

184910-6013-001 Revision A, March 2011






Yes

No

FromSheet 1



Change the Allowed DPC screen withthe NSFI equal to CGPA and the NSRequal to the Allowed CGPA screening

reference name




Yes

No



Sheet 4 of 5

185910-6013-001 Revision A, March 2011






Yes

No

FromSheet 1



Change the Allowed DPC screen withthe NSFI equal to ISUP and the NSRequal to the Allowed ISUP screening

reference name




Yes

No



Sheet 5 of 5

Adding an Allowed SIO Screen

This procedure is used to add an allowed SIO screen to the database. This procedure uses the EAGLE5 ISS commands rtrv-feat, chg-feat, and chg-db. For more information on this procedure,see “Adding an Allowed SIO Screen” in the Database Administration Manual - Gateway Screening .



If gateway screening stop action sets are to be assigned to the allowed SIO screen being added to thedatabase, perform the “Adding an Allowed SIO Screen” procedure in the Database AdministrationManual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

186910-6013-001 Revision A, March 2011




command



:gws=on"; command

Yes

No

To Sheet2

Display the Allowed SIOscreens in the database


Yes

No

Add the new Allowed SIOscreen with the NSFI equal

to STOP

Verify that the new AllowedSIO screen has been




To Sheet4

To Sheet6

To Sheet5

To Sheet3



DPC

BLKDPC

CGPA

DESTFLD

CDPA

To Sheet7

ISUP

Sheet 1 of 7Figure 44: Adding an Allowed SIO Screen from the SEAS Terminal

187910-6013-001 Revision A, March 2011



Verify that the new AllowedSIO screen has been added

to the database



Yes

No

FromSheet 1

Go to the "Adding an AllowedDPC Screen" procedure and add

the required screen

Add the new Allowed SIO screen withthe NSFI equal to DPC and the NSRequal to the Allowed DPC screening

reference name


Is a newAllowed DPC screento be added to the

database?

Yes

No

Go to the "Changing an AllowedDPC Screen" procedure andchange the required screen

Sheet 2 of 7

188910-6013-001 Revision A, March 2011



Verify that the new AllowedSIO screen has been added

to the database



Yes

No

FromSheet 1


the required screen

Add the new Allowed SIO screen withthe NSFI equal to BLKDPC and the





Yes

No


Sheet 3 of 7

189910-6013-001 Revision A, March 2011






FromSheet 1

Add the new Allowed SIO screen with thesevalues:

The service indicator value equal to 0The NSFI equal to DESTFLDThe NSR equal to the Allowed DESTFLD




Yes

NoGo to the "Adding an Allowed

Affected Destination FieldScreen" procedure and add the

required screen



Yes

No



Sheet 4 of 7

190910-6013-001 Revision A, March 2011






FromSheet 1


The service indicator value equal to 3The NSFI equal to CGPAThe NSR equal to the Allowed CGPA




Yes

NoGo to the "Adding an AllowedCalling Party Address Screen"




Yes

No



Sheet 5 of 7

191910-6013-001 Revision A, March 2011






FromSheet 1


The service indicator value equal to 3The NSFI equal to CDPAThe NSR equal to the Allowed CDPA




Yes

NoGo to the "Adding an AllowedCalled Party Address Screen"




Yes

No



Sheet 6 of 7

192910-6013-001 Revision A, March 2011






FromSheet 1


The service indicator value equal to either 4 or 5The NSFI equal to ISUPThe NSR equal to the Allowed ISUP


Note: The service indicator value of 5 indicatesan ISUP message. The service indicator value of4 indicates a TUP message. The EAGLE 5 ISSuses the ISUP screening table to screen for bothISUP messages and TUP messages.



Yes

NoGo to the "Adding an AllowedISUP Message Type Screen"




Yes

No



Sheet 7 of 7

Removing an Allowed SIO Screen

This procedure is used to remove an allowed SIO screen from the database. This procedure uses theEAGLE 5 ISS command chg-db. For more information on this procedure, see “Removing an AllowedSIO Screen” in the Database Administration Manual - Gateway Screening .

193910-6013-001 Revision A, March 2011


If gateway screening stop action sets are assigned to the screens referencing the allowed SIO screenbeing removed from the database, perform the “Removing an Allowed SIO Screen” procedure in theDatabase Administration Manual - Gateway Screening using the SEAS FLOW-THRU command with theEAGLE 5 ISS commands.


To Sheet2



Display the gateway linksets thatreference the Allowed SIO screen

being removed

Will screeningstop?



No

No

Yes

Yes



Sheet 1 of 3Figure 45: Removing an Allowed SIO Screen from the SEAS Terminal

194910-6013-001 Revision A, March 2011


To Sheet3



NSR

Display the Allowed OPC screensthat reference the Allowed SIO



removed?

Will screeningstop?


change the Allowed OPC screenwith the NSFI equal to SIO and the

NSR set to an Allowed SIOscreening reference name

not being removed

No

No

Yes

Yes

FromSheet 1

Sheet 2 of 3

195910-6013-001 Revision A, March 2011




NSR

Display the Blocked OPC screensthat reference the Allowed SIO



removed?

Will screeningstop?


change the Blocked OPC screenwith the NSFI equal to SIO and the

NSR set to an Allowed SIOscreening reference name not

being removed

No

No

Yes

Yes

FromSheet 2



Verify that the Allowed SIOscreen has been removed

Remove the specifiedAllowed SIO screen

Sheet 3 of 3

Changing an Allowed SIO Screen

This procedure is used to change an allowed SIO screen in the database. This procedure uses theEAGLE 5 ISS command chg-db. For more information on this procedure, see “Changing an AllowedSIO Screen” in the Database Administration Manual - Gateway Screening .

If gateway screening stop action sets are to be assigned to the allowed SIO screen being changed inthe database, perform the “Changing an Allowed SIO Screen” procedure in the Database AdministrationManual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

196910-6013-001 Revision A, March 2011


Display the Allowed SIOscreens in the database.

To Sheet2


Yes

No

Change the Allowed SIOscreen with the NSFI equal

to STOP.





To Sheet4

To Sheet6

To Sheet5

To Sheet3



DPC

BLKDPC

CGPA

DESTFLD

CDPA

To Sheet7

ISUP

Sheet 1 of 7Figure 46: Changing an Allowed SIO Screen from the SEAS Terminal

197910-6013-001 Revision A, March 2011



Verify that the AllowedSIO screen has been changed



Yes

No

FromSheet 1

Go to the "Adding an AllowedDPC Screen" procedure and add

the required screen

Change the Allowed SIO screen withthe NSFI equal to DPC and the NSRequal to the Allowed DPC screening

reference name



database?

Yes

No


Sheet 2 of 7

198910-6013-001 Revision A, March 2011



Verify that the AllowedSIO screen has been changed



Yes

No

FromSheet 1


the required screen

Change the Allowed SIO screen withthe NSFI equal to BLKDPC and the





Yes

No


Sheet 3 of 7

199910-6013-001 Revision A, March 2011


Verify that the Allowed SIOscreen has been changed



FromSheet 1

Change the Allowed SIO screen withthese values:

The service indicator value equal to 0The NSFI equal to DESTFLDThe NSR equal to the Allowed DESTFLD




Yes

NoGo to the "Adding an Allowed

Affected Destination FieldScreen" procedure and add the

required screen



Yes

No



Sheet 4 of 7

200910-6013-001 Revision A, March 2011





FromSheet 1


The service indicator value equal to 3The NSFI equal to CGPAThe NSR equal to the Allowed CGPA




Yes

NoGo to the "Adding an AllowedCalling Party Address Screen"




Yes

No



Sheet 5 of 7

201910-6013-001 Revision A, March 2011





FromSheet 1


The service indicator value equal to 3The NSFI equal to CDPAThe NSR equal to the Allowed CDPA




Yes

NoGo to the "Adding an AllowedCalled Party Address Screen"




Yes

No



Sheet 6 of 7

202910-6013-001 Revision A, March 2011





FromSheet 1


The service indicator value equal to either 4 or 5The NSFI equal to ISUPThe NSR equal to the Allowed ISUP


Note: The service indicator value of 5 indicatesan ISUP message. The service indicator value of4 indicates a TUP message. The EAGLE 5 ISSuses the ISUP screening table to screen for bothISUP messages and TUP messages.



Yes

NoGo to the "Adding an AllowedISUP Message Type Screen"




Yes

No



Sheet 7 of 7

Adding a Blocked OPC Screen

This procedure is used to add a blocked origination point code screen to the database. This procedureuses the EAGLE 5 ISS commands rtrv-feat, chg-feat, and chg-db. For more information onthis procedure, see “Adding a Blocked OPC Screen” in the Database Administration Manual - GatewayScreening .

203910-6013-001 Revision A, March 2011




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 the Database Administration Manual -Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS 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 pcstparameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bitITU-N point codes and cannot be used with SEAS.

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


204910-6013-001 Revision A, March 2011



command



:gws=on"; command

Yes

No

Display the Blocked OPCscreens in the database


Yes

No

Verify that the new BlockedOPC screen has beenadded to the database




this screen?

YesNo

Add the new BlockedOPC screen with the NSFI

equal to FAIL

Add the new Blocked OPCscreen with the NSFI equalto STOP and the value C

for the point code

To Sheet2

To Sheet3



CGPA

SIO

To Sheet4

To Sheet5

DPC

BLKDPC

Sheet 1 of 5Figure 47: Adding a Blocked OPC Screen from the SEAS Terminal

205910-6013-001 Revision A, March 2011


Verify that the new BlockedOPC screen has been added

to the database



Yes

FromSheet 1

Add the new Blocked OPC screen withthe NSFI equal to SIO and the NSRequal to the Allowed SIO screening

reference name

Display the Allowed SIO screensin the database


NoGo to the "Adding anAllowed SIO Screen"

procedure and add therequired screen

Is a newAllowed SIO screento be added to the

database?

Yes

No

Go to the "Changing an AllowedSIO Screen" procedure andchange the required screen

Sheet 2 of 5

206910-6013-001 Revision A, March 2011



to the database



Yes

FromSheet 1

Add the new Blocked OPC screen withthe NSFI equal to DPC and the NSRequal to the Allowed DPC screening

reference name

Display the Allowed DPC screensin the database


NoGo to the "Adding anAllowed DPC Screen"procedure and add the

required screen


database?

Yes

No


Sheet 3 of 5

207910-6013-001 Revision A, March 2011



to the database



Yes

FromSheet 1

Add the new Blocked OPC screen withthe NSFI equal to BLKDPC and the




NoGo to the "Adding a

Blocked DPC Screen"procedure and add the

required screen



Yes

No


Sheet 4 of 5

208910-6013-001 Revision A, March 2011



to the database



Yes

FromSheet 1

Add the new Blocked OPC screen withthe NSFI equal to CGPA and the NSRequal to the Allowed CGPA screening

reference name



No

Go to the "Adding anAllowed Calling Party


required screen



Yes

No



Sheet 5 of 5

Removing a Blocked OPC Screen

This procedure is used to remove a blocked origination point code screen from the database. Thisprocedure uses the EAGLE 5 ISS command chg-db. For more information on this procedure, see“Removing a Blocked OPC Screen” in the Database Administration Manual - Gateway Screening .

If any of the following items are used in removing the blocked origination point code screen from thedatabase, perform the “Removing a Blocked OPC Screen” procedure in the Database AdministrationManual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands:

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

• If gateway screening stop action sets are assigned to the screens referencing the blocked originationpoint code screen being removed.

209910-6013-001 Revision A, March 2011


Display the Blocked OPC screensin the database

To Sheet2



Display the gateway linksets thatreference the Blocked OPC screen

being removed

Will screeningstop?



No

No

Yes

Yes



Sheet 1 of 2Figure 48: Removing a Blocked OPC Screen from the SEAS Terminal

210910-6013-001 Revision A, March 2011




NSR

Display the Allowed OPC screensthat reference the Blocked OPC



removed?

Will screeningstop?


change the Allowed OPC screenwith the NSFI equal to BLKOPCand the NSR set to an BlockedOPC screening reference name

not being removed

No

No

Yes

Yes

FromSheet 2



Verify that the Blocked OPCscreen has been removed

Remove the specifiedBlocked OPC screen

Sheet 2 of 2

Changing a Blocked OPC Screen

This procedure is used to change a blocked origination point code screen in the database. This procedureuses the EAGLE 5 ISS command chg-db. For more information on this procedure, see “Changing aBlocked OPC Screen” in the Database Administration Manual - Gateway Screening .

If any of the following items are used in changing the blocked origination point code screen in thedatabase, perform the “Changing a Blocked OPC Screen” procedure in the Database AdministrationManual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS 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 thepcst or npcst parameters), or 24-bit ITU-N point codes. The pcst and npcst parameters canbe used only with ITU-I or 14-bit ITU-N point codes and cannot be used with SEAS.

211910-6013-001 Revision A, March 2011


• If gateway screening stop action sets are assigned to the blocked origination point code screenbeing changed.


Yes

No

Verify that the BlockedOPC screen has been





this screen?

YesNo

Change the BlockedOPC screen with the NSFI

equal to FAIL.

Change the Blocked OPCscreen with the NSFI equalto STOP and the value C

for the point code.

To Sheet2

To Sheet3



CGPA

SIO

To Sheet4

To Sheet5

DPC

BLKDPC

Display the Blocked OPC screens inthe database.

Sheet 1 of 5Figure 49: Changing a Blocked OPC Screen from the SEAS Terminal

212910-6013-001 Revision A, March 2011


Verify that the Blocked OPCscreen has been changed



Yes

FromSheet 1

Change the Blocked OPC screen withthe NSFI equal to SIO and the NSRequal to the Allowed SIO screening

reference name






database?

Yes

No


Sheet 2 of 5

213910-6013-001 Revision A, March 2011





Yes

FromSheet 1

Change the Blocked OPC screen withthe NSFI equal to DPC and the NSRequal to the Allowed DPC screening

reference name




required screen


database?

Yes

No


Sheet 3 of 5

214910-6013-001 Revision A, March 2011





Yes

FromSheet 1

Change the Blocked OPC screen withthe NSFI equal to BLKDPC and the






required screen



Yes

No


Sheet 4 of 5

215910-6013-001 Revision A, March 2011


Verify that the Blocked OPCscreen has been change



Yes

FromSheet 1

Change the Blocked OPC screen withthe NSFI equal to CGPA and the NSRequal to the Allowed CGPA screening

reference name



No



required screen



Yes

No



Sheet 5 of 5

Adding an Allowed OPC Screen

This procedure is used to add an allowed origination point code screen to the database. This procedureuses the EAGLE 5 ISS commands rtrv-feat, chg-feat, and chg-db. For more information onthis procedure, see “Adding an Allowed OPC Screen” in the Database Administration Manual - GatewayScreening .



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 the Database Administration Manual -Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands:

216910-6013-001 Revision A, March 2011


• 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 pcstparameter), or 24-bit ITU-N point codes. The pcst parameter can be used only with ITU-I or 14-bitITU-N point codes and cannot be used with SEAS.

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



command



:gws=on"; command

Yes

No

To Sheet2

Display the Allowed OPCscreens in the database


Yes

No

Add the new Allowed OPCscreen with the NSFI equal

to STOP

Verify that the new AllowedOPC screen has beenadded to the database



To Sheet4

To Sheet6

To Sheet5

To Sheet3



BLKOPC

SIO

DPC

BLKDPC

CGPA

Sheet 1 of 6Figure 50: Adding an Allowed OPC Screen from the SEAS Terminal

217910-6013-001 Revision A, March 2011


Verify that the new AllowedOPC screen has been added

to the database



Yes

FromSheet 1

Add the new Allowed OPC screen withthe NSFI equal to BLKOPC and the

NSR equal to the Blocked OPCscreening reference name




Blocked OPC Screen"procedure and add the

required screen

Is a newBlocked OPC screen


Yes

No

Go to the "Changing a BlockedOPC Screen" procedure andchange the required screen

Sheet 2 of 6

218910-6013-001 Revision A, March 2011



to the database



Yes

FromSheet 1

Add the new Allowed OPC screen withthe NSFI equal to SIO and the NSRequal to the Allowed SIO screening

reference name






database?

Yes

No


Sheet 3 of 6

219910-6013-001 Revision A, March 2011



to the database



Yes

FromSheet 1

Add the new Allowed OPC screen withthe NSFI equal to DPC and the NSRequal to the Allowed DPC screening

reference name




required screen


database?

Yes

No


Sheet 4 of 6

220910-6013-001 Revision A, March 2011



to the database



Yes

FromSheet 1

Add the new Allowed OPC screen withthe NSFI equal to BLKDPC and the






required screen



Yes

No


Sheet 5 of 6

221910-6013-001 Revision A, March 2011



to the database



Yes

FromSheet 1

Add the new Allowed OPC screen withthe NSFI equal to CGPA and the NSRequal to the Allowed CGPA screening

reference name



No



required screen



Yes

No



Sheet 6 of 6

Removing an Allowed OPC Screen

This procedure is used to remove an allowed origination point code screen from the database. Thisprocedure uses the EAGLE 5 ISS command chg-db. For more information on this procedure, see“Removing an Allowed OPC Screen” in the Database Administration Manual - Gateway Screening .

If any of the following items are used in removing the allowed origination point code screen from thedatabase, perform the “Removing an Allowed OPC Screen” procedure in the Database AdministrationManual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands:

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

• If gateway screening stop action sets are assigned to the screens referencing the allowed originationpoint code screen being removed.

222910-6013-001 Revision A, March 2011


Display the Allowed OPC screensin the database



Display the gateway linksets thatreference the Allowed OPC screen

being removed



Will screeningstop?



No

No

Yes

Yes



Verify that the Allowed OPCscreen has been removed

Remove the specifiedAllowed OPC screen

Figure 51: Removing an Allowed OPC Screen from the SEAS Terminal

Changing an Allowed OPC Screen

This procedure is used to change an allowed origination point code screen in the database. Thisprocedure uses the EAGLE 5 ISS command chg-db. For more information on this procedure, see“Changing an Allowed OPC Screen” in the Database Administration Manual - Gateway Screening .

If any of the following items are used in changing the allowed origination point code screen in thedatabase, perform the “Changing an Allowed OPC Screen” procedure in the Database AdministrationManual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE 5 ISS 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

223910-6013-001 Revision A, March 2011



• If gateway screening stop action sets are assigned to the allowed origination point code screenbeing changed.

Display the Allowed OPC screens inthe database.

To Sheet2


Yes

No

Change the Allowed OPCscreen with the NSFI equal

to STOP.

Verify that the new AllowedOPC screen has been




To Sheet4

To Sheet6

To Sheet5

To Sheet3



BLKOPC

SIO

DPC

BLKDPC

CGPA

Sheet 1 of 6Figure 52: Changing an Allowed OPC Screen from the SEAS Terminal

224910-6013-001 Revision A, March 2011


Verify that the Allowed OPCscreen has been changed



Yes

FromSheet 1

Change the Allowed OPC screen withthe NSFI equal to BLKOPC and the

NSR equal to the Blocked OPCscreening reference name




Blocked OPC Screen"procedure and add the

required screen



Yes

No


Sheet 2 of 6

225910-6013-001 Revision A, March 2011





Yes

FromSheet 1

Change the Allowed OPC screen withthe NSFI equal to SIO and the NSRequal to the Allowed SIO screening

reference name






database?

Yes

No


Sheet 3 of 6

226910-6013-001 Revision A, March 2011





Yes

FromSheet 1

Change the Allowed OPC screen withthe NSFI equal to DPC and the NSRequal to the Allowed DPC screening

reference name




required screen


database?

Yes

No


Sheet 4 of 6

227910-6013-001 Revision A, March 2011





Yes

FromSheet 1

Change the Allowed OPC screen withthe NSFI equal to BLKDPC and the






required screen



Yes

No


Sheet 5 of 6

228910-6013-001 Revision A, March 2011





Yes

FromSheet 1

Change the Allowed OPC screen withthe NSFI equal to CGPA and the NSRequal to the Allowed CGPA screening

reference name



No



required screen



Yes

No



Sheet 6 of 6

Adding a Gateway Linkset

This procedure is used to add a gateway linkset to the database. This procedure performs the samefunctions as the “Adding an SS7 Linkset” procedure on in the Database Administration Manual - SS7and the “Adding a Screen Set” in the Database Administration Manual - Gateway Screening. This procedureuses the EAGLE 5 ISS commands rtrv-feat, chg-feat, and chg-db.



On the EAGLE 5 ISS, the linkset name can have a maximum of 10 characters. The SEAS interfacesupports a linkset name with a maximum of eight characters. Linkset names specified in this procedurecan have a maximum of eight characters. For linkset names provisioned on the EAGLE 5 ISS that have

229910-6013-001 Revision A, March 2011


more than eight characters, the SEAS interface truncates the linkset name to the first eight characterswhen that linkset name is displayed on the SEAS interface.


The EAGLE 5 ISS accepts the values for these parameters as supplier specific parameters: gwsa, gwsm,gwsd, actname, and destfld. Table 16: Gateway Linkset Supplier Specific Parameters shows how theEAGLE 5 ISS 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 theDatabase Administration Manual – SS7 and “Gateway Screening States” in the Database AdministrationManual – Gateway Screening.

For more information on the actname parameter, see “Configuring Gateway Screening Stop ActionSets” in the Database Administration Manual – Gateway Screening.

For more information on the destfld parameter, see “Automatic Destination Field Screening” in theDatabase Administration Manual – Gateway Screening.

Table 16: Gateway Linkset Supplier Specific Parameters


Value


Value

SupplierSpecific

Parameters

Gateway screening action – This parameterdetermines whether gateway screening (GWS) is onor off for the specified link set.

1

0

ON

OFF

GWSA

Gateway screening messaging – This parameter isused to turn on or off the display of messages

1

0

ON

OFF

GWSM

generated for each screened message. When an MSUis rejected by gateway screening, a message is outputto alert personnel of the event.

Gateway screening MSU discard – This parameteris used to turn on or off the discarding of MSUs onthe linkset.

1

0

ON

OFF

GWSD

The gateway screening stop action setup to 6alphanumericcharacters

up to 6alphanumericcharacters

ACTNAME

name – This parameter defines the additional actionsthe EAGLE 5 ISS can perform on MSUs that passgateway screening and can only be specified whenthe NSFI of the screen is stop.

The destfld parameter shows whether or notnetwork management messages are screened

1

0

YES

NO

DESTFLD

automatically by gateway screening withoutconfiguring an Allowed Affected Destination Fieldscreen.

230910-6013-001 Revision A, March 2011



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

The supplier specific parameters are optional. The default value will be entered for any supplierspecific parameter not specified when adding the gateway linkset. The default values for the supplierspecific 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 5 ISS sets the GatewayScreening GWSA, GWSM, GWSD parameter values to their default values.

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

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

GWSA, GWSM, GWSD, ACTNAME, DESTFLD, SCRN

Note: The SCRN parameter value is used by the EAGLE 5 ISS’s linkset commands to associate a screenset created by the EAGLE 5 ISS’s gateway screening screen set commands with a linkset. The SEASlinkset commands do not contain parameters that make this association. The association of a linksetto a gateway screening screen set in SEAS is made with the gateway linkset commands. However, theSEAS gateway linkset commands do not contain a parameter to give the screen set a name, as theEAGLE 5 ISS’s gateway screening screen set commands do, but the EAGLE 5 ISS’s rtrv-scrsetcommand will display the screen sets created by the SEAS gateway linkset commands. For thertrv-scrset command to display these screen sets, the EAGLE 5 ISS creates a unique screen setname, beginning with the numeric character 0, and this screen set name is shown by the SCRN parametervalue when a gateway linkset is displayed in SEAS.

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. Thisstate 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, anoutput message is generated, and measurements are pegged. This state is set by specifying the supplierspecific parameters gwsa and gwsm equal to 1 (on).

SCREEN AND DON'T REPORT – Screening is performed. When an MSU fails screening it is discardedand measurements are pegged, but no output message is generated. This state is set by specifying thesupplier 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 failsscreening, an output message is generated, but the MSU is still passed. This state is set by specifyingthe supplier specific parameters gwsa to 0 (off) and gwsm to 1 (on).

231910-6013-001 Revision A, March 2011


CAUTION: When Gateway Screening is in the screen test mode, as defined by the linksetparameters gwsa=0 and gwsm=1, the gateway screening action in the gateway screeningstop action set specified by the actname parameter will be performed.

If a gateway screening stop action set is to be assigned to the gateway linkset, the name of the gatewayscreening stop action set must be defined in the database. The gateway screening stop action sets inthe database can be shown using the EAGLE 5 ISS command rtrv-gws-actset. For more informationon the gateway screening stop action sets, see “Configuring Gateway Screening Stop Action Sets” inthe Database Administration Manual – Gateway Screening.

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



command


on?


:gws=on"; command

Yes

No

To Sheet4

Display the gatewaylinksets in the database

Will screeningstop with this gateway

linkset?

Yes

No To Sheet6

To Sheet8

To Sheet7

To Sheet5



OPC

SIO

DPC

BLKDPC

BLKOPC

To Sheet2

Sheet 1 of 8Figure 53: Adding a Gateway Linkset from the SEAS Terminal

232910-6013-001 Revision A, March 2011


FromSheet 1

Enter theFLOW-THRU::::::"rtrv-gws-actset";

command

Is the requiredgateway screening stop

action set in thedatabase?

Is a gatewayscreening stop action set tobe assigned to the gateway

linkset?

Go to the "Configuring GatewayScreening Stop Action Sets"procedure in the Database

Administration Manual - GatewayScreening and configure the

required gateway screening stopaction set in the database

ToSheet 3

Yes

Yes

No

NoIs automatic

affected destinationscreening enabled for this

gateway linkset?

No

Yes

Verify that the gatewaylinkset has been added to

the database



Add the gateway linksetwith the NSFI equal toSTOP and with these

supplier specific parametervalues:

destfld = 0actname = the name of the

gateway screening stopaction set

gwsa = 0 or 1gwsm = 0 or 1gwsd = 0 or 1

(See Note)Add the gateway linkset withthe NSFI equal to STOP andwith these supplier specific

parameter values:destfld = 1

actname = the name of thegateway screening stop action

setgwsa = 0 or 1gwsm = 0 or 1gwsd = 0 or 1

(See Note)Note: See the Gateway Linkset

Supplier Specific Parameters tableand the "Gateway Screening States"

section in this procedure forinformation on the supplier specific

parameters and on the gwsa, gwsm,and gwsd parameter combinations.

Sheet 2 of 8

233910-6013-001 Revision A, March 2011


FromSheet 2

Is automaticaffected destination

screening enabled for thisgateway linkset?

No

Yes


the database



Add the gateway linkset withthe NSFI equal to STOP andwith these supplier specific

parameters:destfld = 0


(See Note)

Add the gateway linkset with theNSFI equal to STOP and with these

supplier specific parameters:destfld = 1


(See Note)

Note: See the Gateway LinksetSupplier Specific Parameters table

and the "Gateway Screening States"section in this procedure for

information on the supplier specificparameters and on the gwsa, gwsm,and gwsd parameter combinations.

Sheet 3 of 8

234910-6013-001 Revision A, March 2011



database


the databaseEnter the

FLOW-THRU::::::"chg-db:action=backup:dest=fixed"; command

Yes

No

FromSheet 1




Add the gateway linksetwith the NSFI equal to

OPC, the NSR equal to theAllowed OPC screening

reference name, and withthese supplier specific



(See Note)

Add the gateway linkset withthe NSFI equal to OPC, the

NSR equal to the Allowed OPCscreening reference name, and

with these supplier specificparameters:destfld = 1


(See Note)

Yes

No




Go to the "Adding anAllowed OPC Screen"procedure and add the

required screen

Is a newAllowed OPC screen


Yes

No

Go to the "Changing an AllowedOPC Screen" procedure andchange the required screen

Sheet 4 of 8

235910-6013-001 Revision A, March 2011



database




Yes

No

FromSheet 1





BLKOPC, the NSR equalto the Blocked OPC

screening reference name,and with these supplier

specific parameters:destfld = 0


(See Note)

Add the gateway linkset withthe NSFI equal to BLKOPC, theNSR equal to the Blocked OPCscreening reference name, and



(See Note)

Yes

No




Go to the "Adding aBlocked OPC Screen"procedure and add the

required screen



Yes

No


Sheet 5 of 8

236910-6013-001 Revision A, March 2011



database




Yes

No

FromSheet 1




Add the gateway linksetwith the NSFI equal to SIO,

the NSR equal to theAllowed SIO screening

reference name, and withthese supplier specific



(See Note)

Add the gateway linkset withthe NSFI equal to SIO, the

NSR equal to the Allowed SIOscreening reference name, and



(See Note)

Yes

No




Go to the "Adding anAllowed SIO Screen"



database?

Yes

No


Sheet 6 of 8

237910-6013-001 Revision A, March 2011



database




Yes

No

FromSheet 1





DPC , the NSR equal tothe Allowed DPC




(See Note)

Add the gateway linkset withthe NSFI equal to DPC , the

NSR equal to the Allowed DPCscreening reference name, and



(See Note)

Yes

No




Go to the "Adding anAllowed DPC Screen "procedure and add the

required screen

Is a newAllowed DPC screen


Yes

No

Go to the "Changing an AllowedDPC Screen " procedure andchange the required screen

Sheet 7 of 8

238910-6013-001 Revision A, March 2011



database




Yes

No

FromSheet 1





BLKDPC , the NSR equalto the Blocked DPC




(See Note)

Add the gateway linkset withthe NSFI equal to BLKDPC , theNSR equal to the Blocked DPCscreening reference name, and



(See Note)

Yes

No




Go to the "Adding aBlocked DPC Screen "procedure and add the

required screen



Yes

No

Go to the "Changing a BlockedDPC Screen " procedure andchange the required screen

Sheet 8 of 8

Removing a Gateway Linkset

This procedure is used to remove a gateway linkset from the database. This procedure uses the EAGLE5 ISS command chg-db. This procedure performs the same functions as the “Removing a LinksetContaining SS7 Signaling Links” on in the Database Administration Manual - SS7 and the “Removinga Screen Set” in the Database Administration Manual - Gateway Screening .

On the EAGLE 5 ISS, the linkset name can have a maximum of 10 characters. The SEAS interfacesupports a linkset name with a maximum of eight characters. Linkset names specified in this procedure

239910-6013-001 Revision A, March 2011


can have a maximum of eight characters. For linkset names provisioned on the EAGLE 5 ISS that havemore than eight characters, the SEAS interface truncates the linkset name to the first eight characterswhen that linkset name is displayed on the SEAS interface. If the linkset name of the linkset beingremoved was configured on the EAGLE 5 ISS with more than eight characters, only the first eightcharacters of the linkset name can be specified in this procedure.


Remove the gateway linksetfrom the database



Verify that the gateway linksethas been removed from the

database

Figure 54: Removing a Gateway Linkset from the SEAS Terminal

Changing a Gateway Linkset

This procedure is used to change a gateway linkset in the database. This procedure uses the EAGLE5 ISS command chg-db. This procedure performs the same functions as the “Changing an SS7 Linkset”in the Database Administration Manual - SS7 and the “Changing a Screen Set” in the DatabaseAdministration Manual - Gateway Screening.

On the EAGLE 5 ISS, the linkset name can have a maximum of 10 characters. The SEAS interfacesupports a linkset name with a maximum of eight characters. Linkset names specified in this procedurecan have a maximum of eight characters. For linkset names provisioned on the EAGLE 5 ISS that havemore than eight characters, the SEAS interface truncates the linkset name to the first eight characterswhen that linkset name is displayed on the SEAS interface.


The EAGLE 5 ISS accepts the values for these parameters as supplier specific parameters: gwsa, gwsm,gwsd, actname, and destfld Table 17: Gateway Linkset Supplier Specific Parameters. shows how theEAGLE 5 ISS 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” inthe Database Administration Manual – SS7 and “Gateway Screening States” in the Database AdministrationManual – Gateway Screening.

For more information on the actname parameter, see “Configuring Gateway Screening Stop ActionSets” in the Database Administration Manual – Gateway Screening.

240910-6013-001 Revision A, March 2011


For more information on the destfld parameter, see “Automatic Destination Field Screening” in theDatabase Administration Manual – Gateway Screening.


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

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

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

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

Table 17: Gateway Linkset Supplier Specific Parameters


Value


Value

SupplierSpecific

Parameters

Gateway screening action – This parameterdetermines whether gateway screening (GWS) is onor off for the specified link set.

1

0

ON

OFF

GWSA

Gateway screening messaging – This parameter isused to turn on or off the display of messages

1

0

ON

OFF

GWSM

generated for each screened message. When an MSUis rejected by gateway screening, a message is outputto alert personnel of the event.

Gateway screening MSU discard – This parameteris used to turn on or off the discarding of MSUs onthe linkset.

1

0

ON

OFF

GWSD

The gateway screening stop action setup to 6alphanumericcharacters

up to 6alphanumericcharacters

ACTNAME

name – This parameter defines the additional actionsthe EAGLE 5 ISS can perform on MSUs that passgateway screening and can only be specified whenthe NSFI of the screen is stop.

The destfld parameter shows whether or notnetwork management messages are screened

1

0

YES

NO

DESTFLD

automatically by gateway screening withoutconfiguring an Allowed Affected Destination Fieldscreen.

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

241910-6013-001 Revision A, March 2011


GWSA, GWSM, GWSD, ACTNAME, DESTFLD, SCRN

Note: The SCRN parameter value is used by the EAGLE 5 ISS’s linkset commands to associate a screenset created by the EAGLE 5 ISS’s gateway screening screen set commands with a linkset. The SEASlinkset commands do not contain parameters that make this association. The association of a linksetto a gateway screening screen set in SEAS is made with the gateway linkset commands. However, theSEAS gateway linkset commands do not contain a parameter to give the screen set a name, as theEAGLE 5 ISS’s gateway screening screen set commands do, but the EAGLE 5 ISS’s rtrv-scrsetcommand will display the screen sets created by the SEAS gateway linkset commands. For thertrv-scrset command to display these screen sets, the EAGLE 5 ISS creates a unique screen setname, beginning with the numeric character 0, and this screen set name is shown by the SCRN parametervalue when a gateway linkset is displayed in SEAS.

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. Thisstate 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, anoutput message is generated, and measurements are pegged. This state is set by specifying the supplierspecific parameters gwsa and gwsm equal to 1 (on).

SCREEN AND DON'T REPORT – Screening is performed. When an MSU fails screening it is discardedand measurements are pegged, but no output message is generated. This state is set by specifying thesupplier 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 failsscreening, an output message is generated, but the MSU is still passed. This state is set by specifyingthe supplier specific parameters gwsa to 0 (off) and gwsm to 1 (on).

CAUTION: When Gateway Screening is in the screen test mode, as defined by the linksetparameters gwsa=0 and gwsm=1, the gateway screening action in the gateway screeningstop action set specified by the actname parameter will be performed.

If a gateway screening stop action set is to be assigned to the gateway linkset, the name of the gatewayscreening stop action set must be defined in the database. The gateway screening stop action sets inthe database can be shown using the EAGLE 5 ISS command rtrv-gws-actset. For more informationon the gateway screening stop action sets, see “Configuring Gateway Screening Stop Action Sets” inthe Database Administration Manual – Gateway Screening.

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

242910-6013-001 Revision A, March 2011



command


on?


:gws=on"; command

Yes

No

To Sheet4


Will screeningstop with this gateway

linkset?

Yes

No To Sheet6

To Sheet8

To Sheet7

To Sheet5



OPC

SIO

DPC

BLKDPC

BLKOPC

To Sheet2

Sheet 1 of 8Figure 55: Changing a Gateway Linkset from the SEAS Terminal

243910-6013-001 Revision A, March 2011


FromSheet 1

Enter theFLOW-THRU::::::"rtrv-gws-actset";

command

Is the requiredgateway screening stop

action set in thedatabase?

Is a gatewayscreening stop action set tobe assigned to the gateway

linkset?

Go to the "Configuring GatewayScreening Stop Action Sets"procedure in the Database

Administration Manual - GatewayScreening and configure the

required gateway screening stopaction set in the database

ToSheet 3

Yes

Yes

No

NoIs automatic

affected destinationscreening enabled for this

gateway linkset?

No

Yes

Verify that the gatewaylinkset has been changed



Change the gatewaylinkset with the NSFI equal

to STOP and with thesesupplier specific parameter

values:destfld = 0

actname = the name of thegateway screening stop

action setgwsa = 0 or 1gwsm = 0 or 1gwsd = 0 or 1

(See Note)Change the gateway linkset with

the NSFI equal to STOP andwith these supplier specific

parameter values:destfld = 1

actname = the name of thegateway screening stop action

setgwsa = 0 or 1gwsm = 0 or 1gwsd = 0 or 1

(See Note)Note: See the Gateway Linkset

Supplier Specific Parameters tableand the "Gateway Screening States"

section in this procedure forinformation on the supplier specific

parameters and on the gwsa, gwsm,and gwsd parameter combinations.

Sheet 2 of 8

244910-6013-001 Revision A, March 2011


FromSheet 2



No

Yes




Change the gateway linkset withthe NSFI equal to STOP andwith these supplier specific



(See Note)

Change the gateway linkset with theNSFI equal to STOP and with these

supplier specific parameters:destfld = 1


(See Note)




Sheet 3 of 8

245910-6013-001 Revision A, March 2011



database




Yes

No

FromSheet 1




Change the gatewaylinkset with the NSFI equalto OPC, the NSR equal to

the Allowed OPCscreening reference name,

and with these supplierspecific parameters:

destfld = 0gwsa = 0 or 1gwsm = 0 or 1gwsd = 0 or 1

(See Note)

Change the gateway linkset withthe NSFI equal to OPC, the

NSR equal to the Allowed OPCscreening reference name, and



(See Note)

Yes

No




Go to the "Adding anAllowed OPC Screen"procedure and add the

required screen

Is a newAllowed OPC screen


Yes

No

Go to the "Changing an AllowedOPC Screen" procedure andchange the required screen

Sheet 4 of 8

246910-6013-001 Revision A, March 2011



database




Yes

No

FromSheet 1





to BLKOPC, the NSRequal to the Blocked OPCscreening reference name,



(See Note)

Change the gateway linkset withthe NSFI equal to BLKOPC, theNSR equal to the Blocked OPCscreening reference name, and



(See Note)

Yes

No




Go to the "Adding aBlocked OPC Screen"procedure and add the

required screen



Yes

No


Sheet 5 of 8

247910-6013-001 Revision A, March 2011



database




Yes

No

FromSheet 1




Change the gatewaylinkset with the NSFI equalto SIO, the NSR equal to

the Allowed SIO screeningreference name, and with

these supplier specificparameters:destfld = 0


(See Note)

Change the gateway linkset withthe NSFI equal to SIO, the

NSR equal to the Allowed SIOscreening reference name, and



(See Note)

Yes

No




Go to the "Adding anAllowed SIO Screen"



database?

Yes

No


Sheet 6 of 8

248910-6013-001 Revision A, March 2011



database




Yes

No

FromSheet 1




Change the gatewaylinkset with the NSFI equalto DPC , the NSR equal to

the Allowed DPCscreening reference name,



(See Note)

Change the gateway linkset withthe NSFI equal to DPC , the

NSR equal to the Allowed DPCscreening reference name, and



(See Note)

Yes

No




Go to the "Adding anAllowed DPC Screen "procedure and add the

required screen

Is a newAllowed DPC screen


Yes

No

Go to the "Changing an AllowedDPC Screen " procedure andchange the required screen

Sheet 7 of 8

249910-6013-001 Revision A, March 2011



database




Yes

No

FromSheet 1





to BLKDPC , the NSRequal to the Blocked DPCscreening reference name,



(See Note)

Change the gateway linkset withthe NSFI equal to BLKDPC , theNSR equal to the Blocked DPCscreening reference name, and



(See Note)

Yes

No




Go to the "Adding aBlocked DPC Screen "procedure and add the

required screen



Yes

No

Go to the "Changing a BlockedDPC Screen " procedure andchange the required screen

Sheet 8 of 8

Setting the Threshold for Reporting Gateway Screening Activity

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.

250910-6013-001 Revision A, March 2011


This procedure uses the EAGLE 5 ISS command chg-db. For more information on this procedure,see “Setting the Threshold for Reporting Gateway Screening Activity” in the Database AdministrationManual - Gateway Screening .

Display the gatewayscreening activity thresholds.

Display the gateway linksetsin the database.

Set the gateway screeningactivity thresholds for a gateway

linkset in the database.

Verify that the gatewayscreening activity threshold

has been set.



Figure 56: Setting the Threshold for Reporting Gateway Screening Activity from the SEAS Terminal

Setting the Maximum Number of Gateway Screening Rejected Messages

This procedure is used to configure the maximum number of UIMs sent to the terminal and the amountof time during which the UIMs are sent. This procedure uses the EAGLE 5 ISS command chg-db.For more information on this procedure, see “Setting the Maximum Number of Gateway ScreeningRejected Messages” in the Database Administration Manual - Gateway Screening .

Display the gateway screeningmessage reject parameters.

Set the gateway screeningmessage reject parameters.

Verify that the gatewayscreening message rejectparameters have been set.



Figure 57: Setting the Maximum Number of Gateway Screening Rejected Messages from the SEASTerminal

251910-6013-001 Revision A, March 2011


Adding an Allowed ISUP Message Type Screen

This procedure is used to add an allowed ISUP message type screen to the database. This procedureuses the EAGLE 5 ISS commands rtrv-feat, chg-feat, and chg-db. For more information onthis procedure, see “Adding an Allowed ISUP Message Type Screen” in the Database AdministrationManual - Gateway Screening .



If you wish to assign gateway screening stop action sets to the allowed ISUP message type screen, oruse the tupmt parameter of the EAGLE 5 ISS’s ent-scr-isup command, perform the “Adding anAllowed ISUP Message Type Screen” procedure in the Database Administration Manual - GatewayScreening using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

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

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


252910-6013-001 Revision A, March 2011



command


on?


:gws=on"; command

Yes

No


Add the new Allowed ISUPscreen to the database

Verify that the new AllowedISUP screen has been added

to the database



Figure 58: Adding an Allowed ISUP Message Type Screen from the SEAS Terminal

Removing an Allowed ISUP Message Type Screen

This procedure is used to remove an allowed ISUP message type screen from the database. Thisprocedure uses the EAGLE 5 ISS chg-db command. For more information on this procedure, see“Removing an Allowed ISUP Message Type Screen” in the Database Administration Manual - GatewayScreening .

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

253910-6013-001 Revision A, March 2011


Display the Allowed ISUP screensin the database

To Sheet2



NSR

Display the Allowed SIO screens thatreference the Allowed ISUP screen

being removed


removed?

Will screeningstop?


change the Allowed SIO screenwith the NSFI equal to ISUP andthe NSR set to an Allowed ISUPscreening reference name not

being removed

No

No

Yes

Yes

Sheet 1 of 3Figure 59: Removing an Allowed ISUP Message Type Screen from the SEAS Terminal

254910-6013-001 Revision A, March 2011


To Sheet3



NSR

Display the Allowed DPC screensthat reference the Allowed ISUP



removed?

Will screeningstop?


change the Allowed DPC screenwith the NSFI equal to ISUP andthe NSR set to an Allowed ISUPscreening reference name not

being removed

No

No

Yes

Yes

FromSheet 1

Sheet 2 of 3

255910-6013-001 Revision A, March 2011




NSR

Display the Blocked DPC screensthat reference the Allowed ISUP



removed?

Will screeningstop?


change the Blocked DPC screenwith the NSFI equal to ISUP andthe NSR set to an Allowed ISUPscreening reference name not

being removed

No

No

Yes

Yes

FromSheet 2



Verify that the Allowed ISUPscreen has been removed

Remove the specifiedAllowed ISUP screen

Sheet 3 of 3

Changing an Allowed ISUP Message Type Screen

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

If you wish to assign gateway screening stop action sets to the allowed ISUP message type screenbeing changed, or use the tupmt and ntupmt parameters of the EAGLE 5 ISS’s chg-scr-isupcommand, perform the “Changing an Allowed ISUP Message Type Screen” procedure in the DatabaseAdministration Manual - Gateway Screening using the SEAS FLOW-THRU command with the EAGLE5 ISS commands.

The tupmt and ntupmt parameters (TUP message type) of the EAGLE 5 ISS’s chg-scr-isupcommand are not supported by SEAS. A screen can be provisioned to screen for TUP messages using

256910-6013-001 Revision A, March 2011


the SEAS interface by provisioning an allowed SIO screen with the service indicator value of 4, withthe NSFI value of ISUP, and the screening reference name (NSR) of the allowed ISUP screen to be usedto 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.

Display the Allowed ISUPscreens in the database.

Change the AllowedISUP screen.

Verify that the new AllowedISUP screen has been




Figure 60: Changing an Allowed ISUP Message Type Screen from the SEAS Terminal

257910-6013-001 Revision A, March 2011


Chapter

6Enhanced Global Title Translation (EGTT) Configuration

Chapter 6, Enhanced Global Title Translation(EGTT) Configuration, describes the procedures

Topics:

• Provisioning a Mated Application.....259 used to administer the data required for theenhanced global title translation feature.• Removing a Mated Application.....261

• Changing a Mated Application.....263• Adding Global Title Address Information.....265• Removing Global Title Address Information....275• Changing Global Title Address Information....277

258910-6013-001 Revision A, March 2011

Provisioning a Mated Application

This procedure is used to add a dominant mated application to the database.

The only parameters that can be specified with this procedure are the primary point code, primarysubsystem number, mate point code, and mate subsystem number. The EAGLE 5 ISS relative costparameters cannot be specified in this procedure. When the mated application is added to the databasewith this procedure, the relative cost value for the primary point code and subsystem is defaulted to10. The relative cost value for the mate point code and subsystem is defaulted to 50. This creates adominant mated application with only two entries.

This procedure uses the EAGLE 5 ISS commands rtrv-map, rtrv-ctrl-feat, rtrv-dstn, andchg-db. For more information on provisioning mated applications, refer to one of the “Provisioninga Mated Application” procedures in the Database Administration Manual - Global Title Translation .

If you wish to use the pci, pcn, pcn24, mpci, mpcn, mpcn24, srm, grp, mrc, rc, materc, , or mapset,wt, mwt, thr , mrnset, or mrnpc parameters of the EAGLE 5 ISS’s ent-map command, the subsystemassigned to the mated application is the LNP, INP, V-Flex, ATINPQ, AIQ, or EIR subsystem, or youwish to create another type of MAP group or MAP set, perform one of the “Provisioning a MatedApplication” procedures in the Database Administration Manual - Global Title Translation using theSEAS FLOW-THRU command with the EAGLE 5 ISS commands.

Mated application groups in the EAGLE 5 ISS database can contain up to 32 entries, the primary pointcode, and up to 31 mate point codes. SEAS allows the user to configure only two entries for each MAPgroup. To add more entries to the MAP group, up to 30, after performing this procedure, perform oneof the “Provisioning a Mated Application” procedures in the Database Administration Manual - GlobalTitle Translation using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands. The rcand materc parameters must be specified with the EAGLE 5 ISS’s chg-map command. The maximumnumber of mated application entries that can be provisioned in the EAGLE 5 ISS is 1024, 2000, or 3000,depending on the quantity that is enabled.

If the Flexible GTT Load Sharing feature is enabled, shown by the MAPSET field in the EAGLE 5 ISSrtrv-map output, by default the mated application is assigned to the default MAP set. To assign amated application to a MAP set other than the default MAP set, perform one of the “Provisioning aMated Application” procedures in the Database Administration Manual - Global Title Translationusing the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.


259910-6013-001 Revision A, March 2011

Enhanced Global Title Translation (EGTT)Configuration

Database Administration Manual - SEAS


command

Will the addition of themated application increase the

number of mated applications theEAGLE 5 ISS can have beyond


What is the currentmaximum number of matedapplications the EAGLE 5

ISS can have?

1024or

2000

3000


command

Is the XMAPTable Expansion feature

enabled and activated for thedesired number of

mated applications?

Perform the "Enabling the XMAP TableExpansion Controlled Feature," in the

Database Administration Manual -Global Title Translation to enable andactivate the XMAP Table Expansion

feature for the desired number of matedapplications

Yes

No

ToSheet 2

Yes

No

ToSheet 2

Sheet 1 of 2Figure 61: Provisioning a Mated Application

260910-6013-001 Revision A, March 2011



Are thenecessary routes in

the database?

Yes

No


to add the required routes with theprimary or mate point code (as

required) as the DPC of the route to thedatabase. A proxy point code cannotbe assigned to the point code that willbe assigned to the mated application.

FromSheet 1


Is the EAGLE5 ISS's true point codeto be assigned to themated application?


No

Yes



Perform this step for each point code thatwill be assigned to the mated application.



Is a proxy pointcode assigned to any of

the point codes shown in thertrv-dstn output?


proxy point code.

Yes No

Verify that the matedapplication has been added

to the database



Add the mated application to the database withthese values:

Primary ANSI point code from the routingtable or the EAGLE 5 ISS's true point code

Primary subsystem numberMate ANSI point code of the mate from the

routing tableMate subsystem number

Note: If the Flexible GTT Load Sharing featureis enabled, shown by the MAPSET field in theEAGLE 5 ISS rtrv-map output on Sheet 1, bydefault the mated application is assigned to thedefault MAP set.

Sheet 2 of 2

Removing a Mated Application

This procedure is used to remove a mated application from the database. This procedure uses theEAGLE 5 ISS commands rtrv-feat, rtrv-ctrl-feat, rtrv-ss-appl, dlt-map, and chg-db.For more information on this procedure, see “Removing a Mated Application” in the DatabaseAdministration Manual - Global Title Translation.

261910-6013-001 Revision A, March 2011



If you wish to use the pci, pcn, pcn24, all, mapset , or mrnset parameters of the EAGLE 5 ISS’sdlt-map command, perform the “Removing a Mated Application” procedure in the DatabaseAdministration Manual - Global Title Translation using the SEASFLOW-THRU command with the EAGLE5 ISS commands.

If the Flexible GTT Load Sharing feature is enabled, only entries in the default MAP set are displayedfrom the SEAS terminal. Performing this procedure removes only mated application entries in thedefault MAP set. To remove entries from a MAP set other than the default MAP set, perform the“Removing a Mated Application” procedure in the Database Administration Manual - Global TitleTranslation using the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.


The EAGLE 5 ISS's point code and subsystem can be assigned to the mated application. If the matedapplication contains EAGLE 5 ISS's point code and the subsystem shown in Table 18: Mated ApplicationSubsystem Features, perform the “Removing a Mated Application” procedure in the DatabaseAdministration Manual - Global Title Translation using the SEASFLOW-THRU command with the EAGLE5 ISS commands.

Table 18: Mated Application Subsystem Features

SubsystemFeature StatusFeature

INPEnabled and Turned OnINP

INPEnabled and Turned OnANSI-41 INP Query

EIREnabled and Turned OnEIR

V-FLEXEnabled and Turned OnV-FLEX

ATINPQEnabledATINP

LNPEnabledLNP

AIQEnabledANSI41 AIQ

262910-6013-001 Revision A, March 2011




Are any of thefeatures shown in the Mated

Application Subystem Features tableenabled, and turned

on if required?


command

No

Yes

Enter theFLOW-THRU::::::"rtrv-ss-appl";

command

Is the subystem ofthe mated application shown in

the Mated Application SubystemFeatures table?

Yes

No

Go to the "Removing a Mated Application"procedure in the Database Administration Manual- Global Title Translation and remove the matedapplication using the EAGLE 5 ISS commands

with the SEAS FLOW-THRU command.


command

Are all the matedapplications and subsystems

for a specified point codebeing removed?

Verify that the specified matedapplication has been removed

from the database

Yes

NoEnter the

FLOW-THRU::::::"dlt-map:pca=<Primary

ANSI point code>:all=yes"; command

Remove the specifiedmated application from the

database



Figure 62: Removing a Mated Application

Changing a Mated Application

This procedure is used to change an existing mated application in the database. The only parametersthat can be specified in this procedure are the primary point code, primary subsystem number, mate

263910-6013-001 Revision A, March 2011



point code, and mate subsystem number. The EAGLE 5 ISS relative cost parameters cannot be specifiedin this procedure. When the mated application is added to the database with this procedure, the relativecost value for the primary point code and subsystem is defaulted to 10. The relative cost value for themate point code and subsystem is defaulted to 50. This creates a dominant mated application withtwo entries.

If you wish to use the pci, pcn, pcn24, mpci, mpcn, mpcn24, srm, grp, mrc, rc, materc, sso,mapset, eswt, wt, mwt, grpwt, thr , mrnset, or mrnpc parameters of the EAGLE 5 ISS’s chg-mapcommand, or if the subsystem assigned to the mated application is the LNP, EIR, V-Flex, ATINPQ,AIQ, or INP subsystem, performany of the procedures from the Database Administration Manual - GlobalTitle Translation that are shown in Table 19: EAGLE 5 ISS Changing a Mated Application Procedures usingthe SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

Table 19: EAGLE 5 ISS Changing a Mated Application Procedures

Changing the Attributes of a Mated Application

Changing the Mated Application Type

Changing the Weight and In-Service Threshold Values of a Mated Application

Changing the MRNSET and MRN Point Code Values of MAP Entries

If you plan to change the existing MAP group to another type of MAP group, perform the Changingthe Mated Application Type procedure in the Database Administration Manual - Global Title Translationusing the SEAS FLOW-THRU command with the EAGLE 5 ISS commands

The mate point code cannot be changed to the EAGLE 5 ISS’s true point code.

This procedure uses the EAGLE 5 ISS commands chg-db and rtrv-dstn . For more informationabout changing a mated application, refer to the procedures from the Database Administration Manual- Global Title Translation that are shown in Table 19: EAGLE 5 ISS Changing a Mated Application Procedureson this procedure, see “Changing a Mated Application” in the Database Administration Manual - GlobalTitle Translation .

No new entries can be added to a mated application group with this procedure. Mated applicationgroups in the EAGLE 5 ISS database can contain up to 32 eight entries, the primary point code, andup to 31 seven mate point codes. SEAS allows the user to configure only two entries for each MAPgroup. To add more entries to the MAP group, up to 30 six, perform one of the “Provisioning a MatedApplication” procedures in the Database Administration Manual - Global Title Translation using the SEASFLOW-THRU command with the EAGLE 5 ISS commands. The rc and materc parameters must bespecified with the EAGLE 5 ISS’s chg-map command. The maximum number of mated applicationentries that can be provisioned in the EAGLE 5 ISS is 1024, 2000, or 3000, depending on the quantitythat is enabled.

If the Flexible GTT Load Sharing feature is enabled, only entries in the default MAP set are displayedfrom the SEAS terminal. Performing this procedure changes only mated application entries in thedefault MAP set. To change entries in a MAP set other than the default MAP set, perform any of theprocedures from the Database Administration Manual - Global Title Translation that are shown in Table19: EAGLE 5 ISS Changing a Mated Application Procedures using the SEAS FLOW-THRU command withthe EAGLE 5 ISS commands.



264910-6013-001 Revision A, March 2011



Is an existing MAPgroup being changed to either a

solitary, load shared, or combineddominant/load shared group?

No

Yes


Perform the "Changing theMated Application Type"

procedure in the DatabaseAdministration Manual -

Global Title Translation tochange the mated

application using the EAGLE5 ISS commands with the


Is the matepoint code in the

database?

Yes

No


Perform the "Adding a Route"procedure in Chapter 3 of this

manual to add the requiredroutes with the mate point codeas the DPC of the route to thedatabase. A proxy point code

cannot be assigned to the pointcode that will be assigned to

the mated application.






output?


proxy point code.

Yes

No

Verify that the matedapplication has been

changed in the database



Change the mated application to thedatabase with these values:

Primary ANSI point code of the matedapplication

Primary subsystem number

New Mate ANSI point code of themate from the routing table

New Mate subsystem number

Figure 63: Changing a Mated Application

Adding Global Title Address Information

This procedure is used to add global title address information to the database. This procedure usesthe EAGLE 5 ISS commands rtrv-ctrl-feat, rtrv-gttset, rtrv-feat, chg-feat, rtrv-card,

265910-6013-001 Revision A, March 2011



rtrv-gta, rtrv-dstn, and chg-db. For more information on this procedure, see “Adding GlobalTitle Address Information” in the Database Administration Manual - Global Title Translation.

The following parameters of the EAGLE 5 ISS’s ent-gta command are not supported by SEAS: pci,pcn, pcn24, xlat, actsn , ccgt, force, gtmodid , ppmeasreqd , mrnset, mapset, opcsn,cgpc/cgpca/cgpci/cgpcn/cgpcn24, opc/opca/opci/opcn/opcn24,dpc/dpca/dpci/dpcn/dpcn24 , cgssn, ecgssn, loopset, optsn, cdssn, ecdssn, cgselid,cdselid, fallback, testmode, cgcnvsn, family, opcode, pkgtype, acn, or cggtmod. SEASdoes not support hexadecimal digits as the value of the global title address parameter. If you wish touse any of these parameters or use hexadecimal digits as the value for the global title address parameter,perform the “Adding Global Title Address Information” procedure in the Database AdministrationManual - Global Title Translation using the SEASFLOW-THRU command with the EAGLE 5 ISS commands.

If the Flexible GTT Load Sharing feature is enabled, shown by the MRNSET field in the EAGLE 5 ISSrtrv-gta output, and the routing indicator of the global title translation is G (the EAGLE 5 ISS valueGT), by default, the global title translation is assigned to the default MRN set. To assign the global titletranslation to an MRN set other than the default MRN set, perform the “Adding Global Title AddressInformation” procedure in the Database Administration Manual - Global Title Translation using theSEAS FLOW-THRU command with the EAGLE 5 ISS commands.

If the Flexible GTT Load Sharing feature is enabled, shown by the MAPSET field in the EAGLE 5 ISSrtrv-gta output, and the routing indicator of the global title translation is D (the EAGLE 5 ISS valueSSN), by default, the global title translation is assigned to the default MAP set. To assign the globaltitle translation to a MAP set other than the default MAP set, perform the “Adding a Global TitleAddress Information” procedure in the Database Administration Manual - Global Title Translationusing the SEAS FLOW-THRU command with the EAGLE 5 ISS commands.

The EAGLE 5 ISS XLAT parameter does not have a SEAS equivalent. When global title addressinformation is configured at the SEAS interface, the values for the SEAS parameters RI, DPC, and SSN,all mandatory parameters for the SEAS ADD-GTT and CHG-GTT commands, are converted to theEAGLE 5 ISS parameters and values shown in Table 20: SEAS and EAGLE 5 ISS Global Title AddressInformation Parameter Conversion.


Table 20: SEAS and EAGLE 5 ISS Global Title Address Information Parameter Conversion

SSN

EAGLE 5ISS GTT

Parameter

PC/PCA

EAGLE 5ISS GTT

Parameter

RI

EAGLE 5ISS GTT

Parameter

XLAT

EAGLE 5ISS GTT

Parameter

SSN

SEAS GTTParameter

DPC

SEAS GTTParameter

RI

SEAS GTTParameter



Notes:

• The SEAS RI=G parameter denotes global title routing, further global title translation is required.• The SEAS RI=D parameter denotes DPC routing, no further global title translation is required.

266910-6013-001 Revision A, March 2011



SSN

EAGLE 5ISS GTT

Parameter

PC/PCA

EAGLE 5ISS GTT

Parameter

RI

EAGLE 5ISS GTT

Parameter

XLAT

EAGLE 5ISS GTT

Parameter

SSN

SEAS GTTParameter

DPC

SEAS GTTParameter

RI

SEAS GTTParameter

• The EAGLE 5 ISS RI=GT parameter denotes further global title translation is required and usesMTP routing.

• The EAGLE 5 ISS RI=SSN parameter denotes final global title translation and uses MAP routing.• The EAGLE 5 ISS XLAT=DPC parameter indicates that the DPC & RI values in the MSU are to be



are to be replaced

The RC parameter of the SEAS ADD-GTT command is not supported by the EAGLE 5 ISS. While theRC parameter must be specified with the SEAS ADD-GTT command, the RC parameter is discardedwhen the SEAS ADD-GTT command is processed by the EAGLE 5 ISS.

267910-6013-001 Revision A, March 2011



ToSheet 2

Enter theFLOW-THRU::::::"rtrv-ctrl-feat

:partnum=893015401"; command

Is the FlexibleGTT Load Sharingfeature enabled?

No

Yes


default MRN set.

Perform the "Adding Global Title AddressInformation" procedure in the Database

Administration Manual - Global TitleTranslation and add the global title

translation. Use the SEAS FLOW-THRUcommand with the EAGLE 5 ISS

commands.


title translation to an MRN setother than the default

MRN set?

No

Yes

What is the routingindicator value for the global

title translation being added inthis procedure?

G(EAGLE 5 ISS

Value GT)

D(EAGLE 5 ISS

Value SSN)


default MAP set.


title translation to a MAP setother than the default

MAP set?

No

Yes

Sheet 1 of 8Figure 64: Adding Global Title Address Information

268910-6013-001 Revision A, March 2011



Is the requiredGTT set in the

database?

Perform the "Adding a GTT Set"procedure in the Database

Administration Manual - GlobalTitle Translation to add the GTT

set to the database. Use theSEAS FLOW-THRU command

with the EAGLE 5 ISScommands.

Yes

No

Are GTT setsthat contain 11 – 16 different

GTA lengths shown in thertrv-gttset output?

ToSheet 5

No

YesThe Support for 16

GTT Lengths in VGTTfeature is enabled and

turned on.

Are GTT setsthat contain 2 – 10 differentGTA lengths shown in the

rtrv-tt output?

No

Yes The VGTT featureis turned on .

ToSheet 5

ToSheet 3

Will theGTT set have more than 10

different length GTAsassigned to it?

No

Yes

ToSheet 4

Enter the FLOW-THRU::::::"rtrv-gttset";

command

FromSheet 1

Sheet 2 of 8

269910-6013-001 Revision A, March 2011



No

Is theVGTT feature

on?

Yes

Are the correctservice modules

provisioned in the EAGLE 5 ISS?(See the Service Module and FeatureCombinations table in the Database

Administration Manual –Global TitleTranslation )

The correct service modules must be in theEAGLE 5 ISS before the VGTT feature canbe turned on. Refer to the Service Module

and Feature Combinations table in theDatabase Administration Manual – GlobalTitle Translation to determine the servicemodules that are required. If any servicemodules must be replaced, contact the

Customer Care Center before replacing anyservice modules. Refer to the “CustomerCare Center” section in Chapter 1 for the

contact information.

No

Yes


command

FromSheet 2

Will theGTT set have more than

10 different lengthGTAs assigned to it?

No

Yes

Will theGTT set have more thanone different length GTA

assigned to it?

NoYes ToSheet 4

Enter theFLOW-THRU::::::"rtrv-card";

command

Enter the FLOW-THRU::::::"chg-feat:vgtt=on"; command

No

Is theSupport for 16 GTT

Lengths in VGTT featureis enabled and

turned on?

Yes

Perform the “Activating the Supportfor 16 GTT Lengths in VGTT

Feature” procedure in the DatabaseAdministration Manual – Global

Title Translation to enable and turnon the Support for 16 GTTLengths in VGTT feature.

Use the SEAS FLOW-THRUcommand with the EAGLE 5 ISS

commands.

Enter the FLOW-THRU::::::"rtrv-ctrl-feat

:partnum=893024801";command

ToSheet 4

Sheet 3 of 8

270910-6013-001 Revision A, March 2011



What is the currentmaximum number of global

title translations the EAGLE 5ISS can have?

269,999

400,000 1,000,000


than 269,999?


than 400,000?

ToSheet 5

Perform the "Enabling the XGTT TableExpansion Controlled Feature" procedure inthe Database Administration Manual - GlobalTitle Translation and enable the XGTT Table

Expansion feature for either a quantity of400,000 or 1,000,000 global title translations

as required.Use the SEAS FLOW-THRU command with


No

Yes

YesNo

FromSheets 2

or 3

Enter the FLOW-THRU::::::"rtrv-gta:gttsn=<GTT set name>";

command

Sheet 4 of 8

271910-6013-001 Revision A, March 2011




title translation?

ToSheet 8

ToSheet 7

Yes

No



title translation?

Yes

No


FromSheet 4


Yes

No




ToSheet 6

Sheet 5 of 8

272910-6013-001 Revision A, March 2011




title translation?

ToSheet 7

ToSheet 8

Yes

No

FromSheet 6


Yes

No

Perform the "Adding aRoute" procedure in Chapter3 of this manual to add the

required route to thedatabase. A proxy point code

cannot be assigned to thepoint code that will be

assigned to the global titletranslation.



A proxy point codecannot be assigned tothe point code that will

be assigned to theglobal title translation.


output?

Choose anotherroute to use insteadof the route whose

DPC contains aproxy point code.

Yes

No

Sheet 6 of 8

273910-6013-001 Revision A, March 2011




database?

Yes

No



FromSheets 5

or 6


database







Enter theglobal title address information withthese mandatory parameter values:Translation type



Routing indicator D





Yes

No

Enter theglobal title address information withthese mandatory parameter values:Translation type


ANSI point code from the routingtable or the EAGLE 5 ISS's true pointcode

Routing indicator D





Sheet 7 of 8

274910-6013-001 Revision A, March 2011



FromSheets 5

or 6




command



Enter theglobal title address information withthese mandatory parameter values:

Translation type



Routing indicator G


Relative cost = 00-99 (The relativecost value is not used in theEAGLE 5 ISS and is discardedwhen the EAGLE 5 ISS processesthis command.)

The end global title address is optionaland is only required if entering a range

of global title addresses.

Yes

No

Enter theglobal title address information withthese mandatory parameter values:

Translation type



Routing indicator G


Relative cost = 00-99 (The relativecost value is not used in theEAGLE 5 ISS and is discardedwhen the EAGLE 5 ISS processesthis command.)

The end global title address is optionaland is only required if entering a range

of global title addresses.

Sheet 8 of 8

Removing Global Title Address Information

This procedure is used to remove global title address information from the database. This procedureuses the EAGLE 5 ISS commands rtrv-gttset, rtrv-gta, rtrv-gttapath , and chg-db. Formore information on this procedure, see “Removing Global Title Address Information” in the DatabaseAdministration Manual - Global Title Translation.

The following parameters of the EAGLE 5 ISS’s dlt-gta command are not supported by SEAS:cgpc/cgpca/cgpci/cgpcn/cgpcn24, opc/opca/opci/opcn/opcn24,dpc/dpca/dpci/dpcn/dpcn24 cgssn, ecgssn, cdssn, ecdssn, family, opcode, pkgtype, oracn. SEAS does not support hexadecimal digits as the value of the global title address parameters. Ifyou wish to use any of these parameters or use hexadecimal digits as the value for the global titleaddress parameters, perform the “Removing Global Title Address Information” procedure in theDatabase Administration Manual - Global Title Translation using the SEAS FLOW-THRU command withthe EAGLE 5 ISS commands.

The DPC and SSN parameters of the SEAS DLT-GTT command are not supported by the EAGLE 5 ISS.While these parameters must be specified with the SEAS DLT-GTT command, these parameters arediscarded when the SEAS DLT-GTT command is processed by the EAGLE 5 ISS.

275910-6013-001 Revision A, March 2011



Enter theFLOW-THRU::::::"rtrv-gttset”

command.

Enter theFLOW-THRU::::::"rtrv-gta”

command with this parameter.:gttsn=<GTT set name containing

the GTA entry being removed>

Is the range ofglobal title addresses

being split?

No


Feature" procedure in the DatabaseAdministration Manual – GlobalTitle Translation to enable the

XGTT Table Expansion feature foreither a quantity of 400,000 or

1,000,000 global title translations asrequired.

ToSheet 2

Will the numberof global title address entries

exceed the maximum number ofglobal title address

entries?

Less than1,000,000

1,000,000What is themaximum number of global

title addresses?

Yes

No

The range of globaltitle addresses cannot

be split.

Yes

Sheet 1 of 2Figure 65: Removing Global Title Address Information

276910-6013-001 Revision A, March 2011



FromSheet 1

Enter the FLOW-THRU::::::"rtrv-gttapath”command with one of these parameters.

If the GTT set type is CDGTA -:cdgttsn=<the GTT set name shown in thertrv-gta output on Sheet 1>

If the GTT set type is CGGTA -:cggttsn=<the GTT set name shown in thertrv-gta output on Sheet 1>


No

Yes

Perform one of these procedures in the DatabaseAdministration Manual – Global Title Translation .

"Removing a GTT Action Path Entry” to removethe entries displayed in the rtrv-gttapath output.

"Changing a GTT Action Path Entry” to changeGTT set that is being references to the valuenone for the entries displayed in the rtrv-gttapathoutput.

Is the set type of theGTT set that contains the GTA

entry that is being removedCDGTA or CGGTA ?

No

Yes


:dest=fixed” command.

Remove the global titleaddress information in the

database.

Verify that the global title addressinformation has been removed

from the database.

Sheet 2 of 2

Changing Global Title Address Information

This procedure is used to change existing global title address information in the database. Thisprocedure uses the EAGLE 5 ISS commands rtrv-gttset, rtrv-gta, rtrv-mrn, rtrv-map,rtrv-dstn, and chg-db. For more information on this procedure, see “Changing Global Title AddressInformation” in the Database Administration Manual - Global Title Translation.

277910-6013-001 Revision A, March 2011



The following parameters of the EAGLE 5 ISS’s chg-gta command are not supported by SEAS: pci,pcn, pcn24, xlat, actsn , ccgt, force, gtmodid , mrnset, mapset, opcsn, ppmeasreqd ,cgpc/cgpca/cgpci/cgpcn/cgpcn24, opc/opca/opci/opcn/opcn24,dpc/dpca/dpci/dpcn/dpcn24 cgssn, ecgssn, split, loopset, optsn, cdssn, ecdssn,cgselid, cdselid, fallback, testmode, cgcnvsn, family, opcode, pkgtype, acn, or cggtmod.SEAS does not support hexadecimal digits as the value of the global title address parameter. If youwish to use any of these parameters or use hexadecimal digits as the value for the global title addressparameter, perform the “Changing Global Title Address Information” procedure in the DatabaseAdministration Manual - Global Title Translation using the SEAS FLOW-THRU command with theEAGLE 5 ISS commands.

If the Flexible GTT Load Sharing feature is enabled, shown by the MRNSET field in the EAGLE 5 ISSrtrv-gta output, and the routing indicator of the global title translation is G (the EAGLE 5 ISS valueGT), the global title translation can be changed in this procedure only if the global title translation isassigned to the default MRN set. All the attributes of the global title translation can be changed exceptfor the following:

• The MRNSET value cannot be changed.• The routing indicator value cannot be changed.• If the point code is changed, the new point code must be assigned to the default MRN set.

If the Flexible GTT Load Sharing feature is enabled, shown by the MAPSET field in the EAGLE 5 ISSrtrv-gta output, and the routing indicator of the global title translation is D (the EAGLE 5 ISS valueSSN), the global title translation can be changed in this procedure only if the global title translation isassigned to the default MAP set. All the attributes of the global title translation can be changed exceptfor the following:

• The MAPSET value cannot be changed.• The routing indicator value cannot be changed.• If the point code is changed, the new point code must be assigned to the default MAP set.

The EAGLE 5 ISS XLAT parameter does not have a SEAS equivalent. When global title translationsare configured at the SEAS interface, the values for the SEAS parameters RI, DPC, and SSN, allmandatory parameters for the SEAS ADD-GTT and CHG-GTT commands, are converted to the EAGLE5 ISS parameters and values shown in Table 21: SEAS and EAGLE 5 ISS Global Title Address InformationParameter Conversion.


Table 21: SEAS and EAGLE 5 ISS Global Title Address Information Parameter Conversion

SSN

EAGLE GTTParameter

PC/PCA

EAGLE GTTParameter

RI

EAGLE GTTParameter

XLAT

EAGLE GTTParameter

SSN

SEAS GTTParameter

DPC

SEAS GTTParameter

RI

SEAS GTTParameter



278910-6013-001 Revision A, March 2011



SSN

EAGLE GTTParameter

PC/PCA

EAGLE GTTParameter

RI

EAGLE GTTParameter

XLAT

EAGLE GTTParameter

SSN

SEAS GTTParameter

DPC

SEAS GTTParameter

RI

SEAS GTTParameter

Notes:





are to be replaced.

The DPC, SSN and NRC parameters of the SEAS CHG-GTT command are not supported by the EAGLE5 ISS. While these parameters must be specified with the SEAS CHG-GTT command, these parametersare discarded when the SEAS CHG-GTT command is processed by the EAGLE 5 ISS.

The range of global title addresses assigned to a global title translation can be extended or reduced tocreate a new range of global title addresses. The range can be extended so long as the new range ofglobal title addresses does not overlap an existing range of global title addresses. The range can bereduced so long as the new end global title address parameter value is not smaller than the global titleaddress parameter value.

For example, a global title translation contains this range of global title addresses: 9194600000 -9194603000. The range of global title addresses can be extended to 9194604500 by specifying an endglobal title address value of 9194604500 parameter with the SEAS CHG-GTT command. However, ifanother range of global title addresses begins with the value 9194604000, the end global title addressvalue of 9194604500 cannot be specified with the SEAS CHG-GTT command as the new range createdwith the end global title address value of 9194604500 would overlap the range of global title addressesbeginning with the value 9194604000. In this situation, the maximum value for the end global titleaddress value would be 9194603999.

Using the same example, the range of global title addresses can be reduced to 9194600000 - 9194601500by specifying the end global title address value of 9194601500 with the SEAS CHG-GTT command. Thenew range must lie inside of the original range. You cannot create the range 9194595000 - 9194600000by specifying the end global title address value of 9194595000 parameter with the SEAS CHG-GTTcommand.

CAUTION: Changes to the range of global title addresses occur only if the both the globaltitle address and end global title address parameters are specified and the values for eitherof these parameters, or both parameters are different from the original values in the globaltitle translation. If the global title address and end global title address parameters arespecified for the global title translation being changed, and you do not wish to changeeither of these values, make sure the original global title address and end global titleaddress values are specified in the SEAS CHG-GTT command.

279910-6013-001 Revision A, March 2011



Enter the FLOW-THRU::::::"rtrv-gttset";

command

What is theMRNSET value?

DFLT

Is the MRNSET fielddisplayed in the rtrv-gta

output?

Yes

No

What is the RIparameter value of the

global title translation youwish to change?

GT

SSN

This procedure can be performed only on aglobal title translation assigned to the default

(DFLT) MRN set.Either start this procedure again and select aglobal title translation assigned to the defaultMRN set, or perform the "Changing GlobalTitle Address Information" procedure in the

Database Administration Manual - Global TitleTranslation and change the global title

translation. Use the SEAS FLOW-THRUcommand with the EAGLE 5 ISS commands.

Enter theFLOW-THRU::::::"rtrv-gta"; command with

this EAGLE 5 ISS parameter::gttset=<the name of the GTT set from the

previous step containing the global titletranslation you wish to change>


ToSheet 5

ToSheet 3

ToSheet 2

Sheet 1 of 10Figure 66: Changing Global Title Address Information

280910-6013-001 Revision A, March 2011



The attributes of the global title translation canbe changed in this procedure with these

exceptions:The MRN set value cannot be changed.

The routing indicator value cannot be changed.If the point code assigned to the global title

translation is changed, the new point code mustbe assigned to the default MRN set.

FromSheet 1

Is the new pointcode shown in the default

MRN set?

Yes

No


being changed?

Yes

No

ToSheet 4


command with this EAGLE 5 ISSparameter::mrnset=dflt

Perform the “Provisioning MRN Entries”procedure in the Database AdministrationManual - Global Title Translation and add

the new point code to the default MRN set.Use the SEAS FLOW-THRU command with


Sheet 2 of 10

281910-6013-001 Revision A, March 2011



FromSheet 1



being changed?

Yes

No

ToSheet 4


Yes

No





:dpc/dpca=<the DPC of the route>



translation.


output?


proxy point code.

Yes No

Sheet 3 of 10

282910-6013-001 Revision A, March 2011



FromSheets 2

or 3

Verify that the global titleaddress information has

been changed




Yes

No

Change the global title address informationwith these mandatory parameter values:Translation typeGlobal title addressCurrent ANSI point code assigned to theglobal title address (See Note 1)Current subsystem number (See Note 1)


New ANSI point code from the routingtable (See Note 2)New subsystem number = 002-255



Change the global title address informationwith these mandatory parameter values:Translation typeGlobal title addressCurrent ANSI point code assigned to theglobal title address (See Note 1)Current subsystem number (See Note 1)


New ANSI point code from the routingtable (See Note 2)New subsystem number = 000



Notes:

1. The new relative cost, current point code, and current subsystem values are not used in theEAGLE 5 ISS and are discarded when the EAGLE 5 ISS processes this command.

2. If the global title translation is assigned to the default MRN set (shown in the rtrv-gtt output onSheet 1) the new point code must be assigned to the default MRN set (shown in the rtrv-mrn outputon Sheet 2). A proxy point code cannot be assigned to the new point code of the global titletranslation.

3. The range of global title addresses assigned to a global title translation can be extended orreduced to create a new range of global title addresses. The range can be extended so long as thenew range of global title addresses does not overlap an existing range of global title addresses.

Changes to the range of global title addresses occur only if the both the global title address and endglobal title address parameters are specified and the values for either of these parameters, or bothparameters are different from the original values in the global title translation. If the global titleaddress and end global title address parameters are specified for the global title translation beingchanged, and you do not wish to change either of these values, make sure the original global titleaddress and end global title address values are specified in the SEAS CHG-GTT command. Thelength of the end global title address must be the same as the length of the global title address.

Sheet 4 of 10

283910-6013-001 Revision A, March 2011



What is theMAPSET value?

DFLT

Is the MAPSET fielddisplayed in the rtrv-gta

output?

Yes

No ToSheet 7

This procedure can be performed only ona global title translation assigned to the

default (DFLT) MAP set.Either start this procedure again and

select a global title translation assigned tothe default MAP set, or perform the

"Changing a Global Title Translation "procedure in the Database Administration

Manual - Global Title Translation andchange the global title translation. Usethe SEAS FLOW-THRU command with




The MAP set value cannot bechanged.

The routing indicator value cannotbe changed.

If the point code and subsystemassigned to the global title

translation is changed, the newpoint code and subsystem must beassigned to the default MAP set.

FromSheet 1

ToSheet 6

Sheet 5 of 10

284910-6013-001 Revision A, March 2011



FromSheet 5

ToSheet 8

Is the new pointcode and SSN shown in

the default MAP set?

Yes

No

Is the pointcode and SSN in theglobal title translation

being changed?

Yes

No ToSheet 8


command with this EAGLE 5 ISSparameter:

:mapset=dflt

Perform either the “Provisioning aMated Application” or “Changing a

Mated Application” procedures in theDatabase Administration Manual -

Global Title Translation and add thenew point code and SSN to the defaultMAP set. Use the SEAS FLOW-THRU

command with the EAGLE 5 ISScommands.

Sheet 6 of 10

285910-6013-001 Revision A, March 2011





title translation?

Yes

No


ToSheet 9

FromSheet 5


Yes

No




Enter the FLOW-THRU::::::"rtrv-dstn"; command with this

parameter::dpc/dpca=<the DPC of the route>



translation.


output?


proxy point code.

Yes No ToSheet 8

Sheet 7 of 10

286910-6013-001 Revision A, March 2011




database?

Yes

No



FromSheets 6

or 7


database



Yes

No ToSheet 10

Is the MAPSET fielddisplayed in the rtrv-gta

output?

Yes

No

ToSheet 9

Sheet 8 of 10

287910-6013-001 Revision A, March 2011



FromSheet 8

Verify that the global titleaddress information has been

changed



Change theglobal title address information with these

mandatory parameter values:Translation typeGlobal title addressCurrent ANSI point code assigned to theglobal title address (See Note1)Current subsystem number (See Note 1)

and these optional parameter values:New ANSI point code from the routing table

(See Note 2)New subsystem number = 000New routing indicator DNew relative cost = 00-99 (See Note1 )End global title address - only required ifspecifying a range of global title addresses.

(See Note 3)

Notes:

1. The new relative cost, current point code, and current subsystem values are not used in the EAGLE5 ISS and are discarded when the EAGLE 5 ISS processes this command.

2. If the global title translation is assigned to the default MAP set (shown in the rtrv-gtt output on Sheet1) the new point code must be assigned to the default MAP set (shown in the rtrv-map output onSheet 6). A proxy point code cannot be assigned to the new point code of the global title translation.

3. The range of global title addresses assigned to a global title translation can be extended or reducedto create a new range of global title addresses. The range can be extended so long as the new rangeof global title addresses does not overlap an existing range of global title addresses.

Changes to the range of global title addresses occur only if the both the global title address and endglobal title address parameters are specified and the values for either of these parameters, or bothparameters are different from the original values in the global title translation. If the global titleaddress and end global title address parameters are specified for the global title translation beingchanged, and you do not wish to change either of these values, make sure the original global titleaddress and end global title address values are specified in the SEAS CHG-GTT command. Thelength of the end global title address must be the same as the length of the global title address.

Sheet 9 of 10

288910-6013-001 Revision A, March 2011



FromSheets 8

Verify that the global titleaddress information has been

changed


Change theglobal title address information with these

mandatory parameter values:Translation typeGlobal title addressCurrent ANSI point code assigned to theglobal title address (See Note 1)Current subsystem number (See Note 1)


New ANSI point code from the routing tableor the EAGLE 5 ISS's true point code

(See Note 2)New subsystem number = 002-255

(See Note 2)New routing indicator D

New relative cost = 00-99 (See Note 1)End global title address - only required ifspecifying a range of global title addresses.

(See Note 3)

Notes:

1. The new relative cost, current point code, and current subsystem values are not used in theEAGLE 5 ISS and are discarded when the EAGLE 5 ISS processes this command.

2. If the global title translation is assigned to the default MAP set (shown in the rtrv-gtt output onSheet 1) the new point code and SSN must be assigned to the default MAP set (shown in the rtrv-map output on Sheet 6). A proxy point code cannot be assigned to the new point code of the globaltitle translation.

3. The range of global title addresses assigned to a global title translation can be extended orreduced to create a new range of global title addresses. The range can be extended so long as thenew range of global title addresses does not overlap an existing range of globaltitle addresses.

Changes to the range of global title addresses occuronly if the both the global title address and end global title address parameters are specified and thevalues for either of these parameters, or both parameters are different from the original values in theglobal title translation. If the global title address and end global title address parameters are specifiedfor the global title translation being changed, and you do not wish to change either of these values,make sure the original global title address and end global title address values are specified in theSEAS CHG-GTT command. The length of the end global title address must be the same as thelength of the global title address.

Sheet 10 of 10

289910-6013-001 Revision A, March 2011



Appendix

AEAGLE 5 ISS/SEAS Compliance Matrix

Appendix A, EAGLE 5 ISS/SEAS ComplianceMatrix

Topics:

• Introduction.....291• SEAS-STP Interface Specification, GR-310-CORE,

Issue 1, November 1994 .....291• SEAS-STP Gateway Function Interface

Specification, GR-778-CORE, Issue 1, November1994 .....357

290910-6013-001 Revision A, March 2011

Introduction

This appendix lists the SEAS requirements, conditional requirements, and objectives that the EAGLE5 ISS complies with as defined in these Telcordia documents.

• SEAS-STP Interface Specification, GR-310-CORE, Issue 1, November 1994• SEAS-STP Gateway Function Interface Specification, GR-778-CORE, Issue 1, November 1994

The compliance matrix is a table listing the requirement number, objective number, or conditionalrequirement number as defined in the Telcordia document, the EAGLE 5 ISS’s level of compliancewith the requirement, objective, or conditional requirement, and any comments that may apply tothese items.

A requirement is a feature or function of an STP that Telcordia has determined must be a part of theSTP to function properly. A requirement is identified in this appendix with the letter R in parentheses,(R).

A conditional requirement is a feature or function of an STP that Telcordia has determined is necessaryin certain applications, depending on how the STP is deployed. A conditional requirement may dependon other requirements, objectives, or conditional requirements. A conditional requirement is identifiedin this appendix with the letters CR in parentheses, (CR).

An objective is a feature or function of an STP that Telcordia has determined is a desirable feature orfunction for the STP to have, but not required to have. An objective is identified in this appendix withthe letter O in parentheses, (O).

There are four levels of compliance used in this compliance matrix.

• Fully compliant• Partially compliant• Not compliant• Not applicable

The table caption for each table refers to the section of the Telcordia document where the item can befound. The table of contents entries for this appendix are based on the table captions.

SEAS-STP Interface Specification, GR-310-CORE, Issue 1, November 1994

Table 22: Section 4. Message Headers and UPL/Lower-Layer Interactions

Comments/ExceptionsLevel of ComplianceTelcordiaRequirement

Fully Compliant(R) 4-1


291910-6013-001 Revision A, March 2011

EAGLE 5 ISS/SEAS Compliance MatrixDatabase Administration Manual - SEAS



This objective does not apply to the EAGLE 5 ISS becauseconfirmation options “2” and ”3” are not supported by thecurrent UAL implementations.

Not Applicable(O) 4-4
















292910-6013-001 Revision A, March 2011


Table 23: Section 5. UPL Interactions and Message Syntax Requirements



This function is not currently implemented in the EAGLE5 ISS.Not Compliant(O) 5-2

This does not apply to the EAGLE 5 ISS because the EAGLE5 ISS does not comply with objective 5-2.Not Applicable(CR) 5-3

The EAGLE 5 ISS is able to handle the burden of duplicatecommands.Fully Compliant(CR) 5-4

This requirement does not apply to the EAGLE 5 ISSbecause the version management mechanism is a SEASpost-7.0 feature.

Not Applicable(R) 5-5

This requirement does not apply to the EAGLE 5 ISSbecause the version management mechanism is a SEASpost-7.0 feature.





The EAGLE 5 ISS only reports the first error on inputdetected.Partially Compliant(R) 5-10

The EAGLE 5 ISS only reports the first error on executiondetected.Partially Compliant(R) 5-11





293910-6013-001 Revision A, March 2011


Table 24: Section 6. Data Collection Messages


The EAGLE 5 ISS does not currently support the servicemeasurement (P_SERV), network management on-demand

Partially Compliant(R) 6-1

measurement (D_NM), hourly maintenance (on-demand)measurement (D_MTCH), and maintenance status indicator(on demand) (D_MTCS) schedules. Also, the EAGLE 5 ISSdoes not support MTP special study data collection, whichis a SEAS deferred feature.

Also, the EAGLE does not currently support ranges for, orany other compound form of, the period parameter.



measurement (D_NM), hourly maintenance (on-demand)measurement (D_MTCH), maintenance status indicator(on-demand) (D_MTCS) schedules, the per translation type(TT), the per buffer group (BFRGRP), the per buffer(BUFFR), the per processor group (PROCGRP), the perprocessor (PROC), and the per bus (BUS) measured entitytypes. Also, the EAGLE 5 ISS does not support MTP specialstudy data collection and translation type mapping, whichare SEAS deferred features.


The EAGLE 5 ISS cannot guarantee that the report will betransmitted no later than 15 seconds after the end of each

Partially Compliant(R) 6-4 five-minute interval. The EAGLE 5 ISS does not currentlysupport the per link (LINK) exception data and the perprocessor (PROC) exception data measured entity types.


Partially Compliant(R) 6-5measurement (D_NM), hourly maintenance (on-demand)measurement (D_MTCH), and maintenance status indicator(on-demand) (D_MTCS) schedules. Also, the EAGLE 5 ISSdoes not support MTP special study data collection, whichis a SEAS deferred feature.

The EAGLE 5 ISS does not support all of the requiredmeasurement schedules, entity types, and registers (seeTablePartially Compliant(R) 6-6 32: Appendix A. Data Collection Request Structure and Table33: Appendix B. Standard Data Collection Schedules).

294910-6013-001 Revision A, March 2011


Table 25: Section 7. Recent Change and Verify (RC&V) Messages


The EAGLE 5 ISS does not currently support entity sets Land M. Entity set J is supported only by using thePartially Compliant(R) 7-1 Flow-Through interface. Entity sets H, N, O, P, Q, R, and Sare SEAS post-7.0 entity sets.

The EAGLE 5 ISS does not currently support functions 1through 3. It does support functions 24 through 26, but onlyPartially Compliant(CR) 7-2 by using the Flow-Through interface. Functions 15 through17 and 30 through 46 are SEAS post-7.0 functions.

The EAGLE 5 ISS does not currently support function 1. Itdoes support function 10, but only by using thePartially Compliant(R) 7-3 Flow-Through interface. Functions 7 and 13 through 18 areSEAS post-7.0 functions.


The EAGLE 5 ISS supports only immediate activation.Partially Compliant(R) 7-5





Fully Compliant(O) 7-10

The EAGLE 5 ISS does expect all destination identifiers tobe unique.Not Compliant(R) 7-11



The EAGLE 5 ISS already supports the destination entityset, therefore no upgrade is necessary.Fully Compliant(R) 7-14

295910-6013-001 Revision A, March 2011










The EAGLE 5 ISS does not support supplier-specificparameters for these entities with the standard SEASNot Applicable(O) 7-22 interface. The EAGLE 5 ISS’s supplier-specific parameterscan be modified by using the SEAS Flow-Through interface.

The EAGLE 5 ISS does not support supplier-specificparameters with the standard SEAS interface.Not Applicable(CR) 7-23


The EAGLE 5 ISS does not support supplier-specificparameters for these entities with the standard SEASNot Applicable(O) 7-25 interface. The EAGLE 5 ISS’s supplier-specific parameterscan be modified by using the SEAS Flow-Through interface.



All supplier-specific parameter strings for both input andoutput are null.Fully Compliant(R) 7-28

296910-6013-001 Revision A, March 2011



This requirement does not apply to the EAGLE 5 ISSbecause the TFA/TCA broadcast minimum link quantityattribute for linksets is a SEAS post-7.0 feature.


This requirement does not apply to the EAGLE 5 ISSbecause this is a SEAS post-7.0 enhancement.Not Applicable(R) 7-30





This requirement does not apply to the EAGLE 5 ISSbecause the SCCP application entity set is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the multi-step GTT process is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the STP Options entity set a SEAS post-7.0 feature.Not Applicable(R) 7-37

This requirement does not apply to the EAGLE 5 ISSbecause vacant global title addresses is a SEAS post-7.0feature.


The EAGLE 5 ISS does not support storage consolidationfor entries of an entity set with like attributes.Not Compliant(CR) 7-39



297910-6013-001 Revision A, March 2011



The EAGLE 5 ISS does not support the functions for delayedactivation.Partially Compliant(CR) 7-42

The EAGLE 5 ISS does not support the ACTV-OR command.Not Compliant(CR) 7-43

The EAGLE 5 ISS does not support the DLT-OR command.Not Compliant(CR) 7-44

The EAGLE 5 ISS does not support the CANC-ORACTVcommand.Not Compliant(CR) 7-45

The EAGLE 5 ISS does not support the parameters fordelayed activation.Partially Compliant(CR) 7-46



The EAGLE 5 ISS does not support the parameters fordelayed activation. Also, the EAGLE 5 ISS does not supportall wildcarding as specified.

Partially Compliant(CR) 7-49

The EAGLE 5 ISS does not support the parameters fordelayed activation. Also, the EAGLE 5 ISS cannot changePartially Compliant(CR) 7-50 the value of the destination point code attribute with thiscommand.

The EAGLE 5 ISS does not support the parameters fordelayed activation. Also, the EAGLE 5 ISS does not supportPartially Compliant(CR) 7-51 needed linkset recent change and verify enhancements,because it is a SEAS post-7.0 feature.


The EAGLE 5 ISS does not support the changing of the newfar-end CLLI parameter unless the new far-end point code

Partially Compliant(CR) 7-53parameter is being changed as well. In this case the newfar-end CLLI must match the destination identifier of thelinkset’s new far-end point code. The EAGLE 5 ISS doesnot support the parameters for delayed activation. Also,the EAGLE 5 ISS does not support needed linkset recent

298910-6013-001 Revision A, March 2011



change and verify enhancements, because this is a SEASpost-7.0 feature.

The EAGLE 5 ISS does not support the parameters fordelayed activation. Also, the EAGLE 5 ISS does not support1.5 Mbps link speed, because this is a SEAS post-7.0 feature.



The EAGLE 5 ISS does not support the parameters fordelayed activation. The EAGLE 5 ISS only supports the new

Partially Compliant(CR) 7-56 link service state parameter. Also, the EAGLE 5 ISS doesnot support 1.5 Mbps link speed, because this is a SEASpost-7.0 feature.

The EAGLE 5 ISS does not support the parameters fordelayed activation. The EAGLE 5 ISS does not support the


relative cost parameter, although because the RC parameteris required, the EAGLE 5 ISS accepts the parameter. Also,the EAGLE 5 ISS does not support residual modificationsto support SS7 cluster routing and management, and vacantglobal title addresses, because these are SEAS post-7.0features.

The EAGLE 5 ISS does not support the parameters fordelayed activation. EAGLE 5 ISS does not support the

Partially Compliant(CR) 7-58 destination point code and subsystem number parameters,although because they are required, it accepts theparameters. Also, the EAGLE 5 ISS does not support vacantglobal title addresses, because this is SEAS post-7.0 feature.

The EAGLE 5 ISS does not support the parameters fordelayed activation, nor does the EAGLE 5 ISS support the

Partially Compliant(CR) 7-59new relative cost new destination point code, and newsubsystem number parameters. Also, the EAGLE 5 ISS doesnot support residual modifications to support SS7 clusterrouting and management, and vacant global title addresses,because these are SEAS post-7.0 features.

The EAGLE 5 ISS does not support the parameters fordelayed activation. Also, the EAGLE 5 ISS does not supportPartially Compliant(CR) 7-60 residual modifications to support SS7 cluster routing andmanagement, because this is a SEAS post-7.0 feature.

299910-6013-001 Revision A, March 2011




The EAGLE 5 ISS does not support the parameters fordelayed activation. Also, the EAGLE 5 ISS does not supportPartially Compliant(CR) 7-62 residual modifications to support SS7 cluster routing andmanagement, because this is a SEAS post-7.0 feature.

The EAGLE 5 ISS does not support the ASGN-SPCSPcommand. The EAGLE 5 ISS supports only the shared


concerned signaling point lists for its subsystem prohibitedconcerned signaling points entity set. However, this featureis a SEAS post-7.0 feature, therefore the EAGLE 5 ISS cannotsupport this command until this feature is implemented inSEAS. The Flow-Through commands can still be used tomanipulate this entity set.

The EAGLE 5 ISS does not support the DLT-SPCSPcommand. The EAGLE 5 ISS supports only shared

Not Compliant(CR) 7-64

concerned signaling point lists for its subsystem prohibitedconcerned signaling points entity set. However, this featureis a SEAS post-7.0 feature, therefore the EAGLE 5 ISS cannotsupport this command until this feature is implemented inSEAS. The Flow-Through commands can still be used tomanipulate this entity set.

The EAGLE 5 ISS does not support the CHG-SPCSPcommand.Not Compliant(CR) 7-65

The EAGLE 5 ISS does not support the parameters fordelayed activation. Also, the EAGLE 5 ISS does not supportPartially Compliant(CR) 7-66 MTP circular route (loop) detection, because this is a SEASpost-7.0 feature.


The EAGLE 5 ISS does not support the parameters fordelayed activation. Also, the EAGLE 5 ISS does not supportPartially Compliant(CR) 7-68 MTP circular route (loop) detection, because this is a SEASpost-7.0 feature.

300910-6013-001 Revision A, March 2011



This conditional requirement does not apply to the EAGLE5 ISS because MTP circular route (loop) detection is a SEASpost-7.0 feature.

Not Applicable(CR) 7-69

This conditional requirement does not apply to the EAGLE5 ISS because recent change and verify support for SCCPapplication data is a SEAS post-7.0 feature.






This conditional requirement does not apply to the EAGLE5 ISS because recent change and verify for the STPOPTIONS entity set is a SEAS post-7.0 feature.


This conditional requirement does not apply to the EAGLE5 ISS because multi-step global title translation (GTT) is aSEAS post-7.0 feature.












301910-6013-001 Revision A, March 2011









This conditional requirement does not apply to the EAGLE5 ISS because recent change and verify for SCCP ISNImessage routing is a SEAS post-7.0 feature.












The EAGLE 5 ISS does not support the ACTV-OR command.Not Compliant(R) 7-89

The EAGLE 5 ISS does not support the ACTV-OR command.Not Compliant(R) 7-90

The EAGLE 5 ISS does not support the DLT-OR command.Not Compliant(R) 7-91

302910-6013-001 Revision A, March 2011



The EAGLE 5 ISS does not support the CANC-ORACTVcommand.Not Compliant(R) 7-92





Fully Compliant(CR) 7-97

This conditional requirement does not apply to the EAGLE5 ISS because the EAGLE 5 ISS supports the changing ofthe CLLI and DPC values using the ASGN-SID command.





The EAGLE 5 ISS does not support supplier-specificparameters.Not Compliant(R) 7-102


The EAGLE 5 ISS does not support multi-step global titletranslation (GTT) nor recent change and verify for SCCPFully Compliant(R) 7-104 ISNI message routing, because they are SEAS post-7.0features.



The EAGLE 5 ISS enforces rule a, e, and g, but not rules b,c, d, and f because those parameters are not supported byPartially Compliant(R) 7-107the EAGLE 5 ISS’s chg-rte command. Also, the EAGLE5 ISS does not support multi-step global title translation

303910-6013-001 Revision A, March 2011



(GTT) nor recent change and verify for SCCP ISNI messagerouting, because they are SEAS post-7.0 features.






This requirement does not apply to the EAGLE 5 ISSbecause the EAGLE 5 ISS does not support parameters forNot Applicable(R) 7-113 the needed linkset recent change and verify enhancements.This is a SEAS post-7.0 feature.



The EAGLE 5 ISS does not support the changing of the newfar-end CLLI parameter unless the new far-end point code

Partially Compliant(R) 7-116 parameter is being changed as well. In this case the newfar-end CLLI must match the destination identifier of thelinkset’s new far-end point code.

The EAGLE 5 ISS enforces rules a and b. The EAGLE 5 ISSenforces only part of rule c because the EAGLE 5 ISS does


not require links in a linkset to be disabled in order tochange the linkset type attribute. The EAGLE 5 ISS doesnot enforce rule d because the EAGLE 5 ISS does notsupport supplier-specific parameters. The EAGLE 5 ISSdoes not enforce rules e and f because the EAGLE 5 ISSdoes not support needed linkset recent change and verifyenhancements, because this is a SEAS post-7.0 feature.

The EAGLE 5 ISS does not support needed linkset recentchange and verify enhancements, because this is a SEASFully Compliant(CR) 7-118post-7.0 feature. The EAGLE 5 ISS does permit changes toall supported parameters while the linkset’s signaling links

304910-6013-001 Revision A, March 2011



are active, but only the far-end CLLI is supported for thisconditional requirement.

The EAGLE 5 ISS does not list the signaling links in thelinkset that are enabled when the CHG-LS command is

Not Compliant(R) 7-119 rejected, or when attempting to change the point code ofthe linkset because the EAGLE 5 ISS does not require thesignaling links in the linkset to be disabled to make thesechanges.














Rule c is does not apply to the EAGLE 5 ISS because theEAGLE 5 ISS does not support the SCCP application entityset, because this is a SEAS post-7.0 feature.


305910-6013-001 Revision A, March 2011



The EAGLE 5 ISS does not support the destination pointcode and subsystem number parameters, but because thesePartially Compliant(R) 7-134 parameters are required by SEAS, the EAGLE 5 ISS acceptsthe parameters.

The EAGLE 5 ISS does not enforce rule 1 because theEAGLE 5 ISS does not support the destination point code


and subsystem number parameters, but because theseparameters are required by SEAS, the EAGLE 5 ISS acceptsthese parameters. The EAGLE 5 ISS enforces rules 2, 3, and4. Rule 5 does not apply to the EAGLE 5 ISS because theEAGLE 5 ISS does not support the SCCP application entityset. This is a SEAS post-7.0 feature.

Rule 2 does not apply to the EAGLE 5 ISS because theEAGLE 5 ISS does not support the SCCP application entityset. This is a SEAS post-7.0 feature.



Rule 2 does not apply to the EAGLE 5 ISS because theEAGLE 5 ISS does not support the SCCP application entityset. This is a SEAS post-7.0 feature.


The EAGLE 5 ISS does not support the ASGN-SPCSPcommand.Not Compliant(CR) 7-139

The EAGLE 5 ISS does not support the ASGN-SPCSPcommand.Not Compliant(R) 7-140

The EAGLE 5 ISS does not support the DLT-SPCSPcommand.Not Compliant(CR) 7-141

The EAGLE 5 ISS does not support the DLT-SPCSPcommand.Not Compliant(R) 7-142

The EAGLE 5 ISS does not support the DLT-SPCSPcommand.Not Compliant(R) 7-143

The EAGLE 5 ISS does not support the CHG-SPCSPcommand.Not Compliant(CR) 7-144

306910-6013-001 Revision A, March 2011



The EAGLE 5 ISS does not support the CHG-SPCSPcommand.Not Compliant(R) 7-145

The EAGLE 5 ISS does not support the CHG-SPCSPcommand.Not Compliant(R) 7-146

The EAGLE 5 ISS does not verify this rule for the beiparameter.Partially Compliant(R) 7-147


The EAGLE 5 ISS does not support the far-end CLLIattribute for its linkset entities.Partially Compliant(R) 7-149




The EAGLE 5 ISS does not verify this rule for the nbeiparameter.Partially Compliant(R) 7-153


The EAGLE 5 ISS does not support the far-end CLLIattribute for its linkset entities.Partially Compliant(R) 7-155


This requirement does not apply to the EAGLE 5 ISSbecause the RST-DSTN command is a SEAS post-7.0 feature.Not Applicable(R) 7-157



307910-6013-001 Revision A, March 2011




This requirement does not apply to the EAGLE 5 ISSbecause the ADD-SCCPAPL command is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the ADD-SCCPAPL command is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the DLT-SCCPAPL command is a SEAS post-7.0feature.






This requirement does not apply to the EAGLE 5 ISSbecause the CHG-SCCPAPL command is a SEAS post-7.0feature.






This requirement does not apply to the EAGLE 5 ISSbecause the UPD-STPOPTS command is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the ADD-MGTT-TTSSN command is a SEAS post-7.0feature.


308910-6013-001 Revision A, March 2011



This requirement does not apply to the EAGLE 5 ISSbecause the ADD-MGTT-TTSSN command is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the DLT-MGTT-TTSSN command is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the CHG-MGTT-TTSSN command is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the ADD-MGTT-GTADPC command is a SEASpost-7.0 feature.








This requirement does not apply to the EAGLE 5 ISSbecause the DLT-MGTT-GTADPC command is a SEASpost-7.0 feature.








309910-6013-001 Revision A, March 2011



This requirement does not apply to the EAGLE 5 ISSbecause the CHG-MGTT-GTADPC command is a SEASpost-7.0 feature.








This requirement does not apply to the EAGLE 5 ISSbecause the ADD-MGTT-ORDPC command is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the ADD-MGTT-ORDPC command is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the DLT-MGTT-ORDPC command is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the CHG-MGTT-ORDPC command is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the CHG-MGTT-ORDPC command is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the ADD-ISNI-CICICN command is a SEASpost-7.0 feature.


This requirement does not apply to the EAGLE 5 ISSbecause the ADD-ISNI-CICICN command is a SEASpost-7.0 feature.


310910-6013-001 Revision A, March 2011



This requirement does not apply to the EAGLE 5 ISSbecause the DLT-ISNI-CICICN command is a SEASpost-7.0 feature.


This requirement does not apply to the EAGLE 5 ISSbecause the DLT-ISNI-CICICN command is a SEASpost-7.0 feature.


This requirement does not apply to the EAGLE 5 ISSbecause the CHG-ISNI-CICICN command is a SEASpost-7.0 feature.


This requirement does not apply to the EAGLE 5 ISSbecause the CHG-ISNI-CICICN command is a SEASpost-7.0 feature.


This requirement does not apply to the EAGLE 5 ISSbecause the ADD-ISNI-ICNDPC command is a SEASpost-7.0 feature.


This requirement does not apply to the EAGLE 5 ISSbecause the DLT-ISNI-ICNDPC command is a SEASpost-7.0 feature.


This requirement does not apply to the EAGLE 5 ISSbecause the CHG-ISNI-ICNDPC command is a SEASpost-7.0 feature.



This conditional requirement does not apply to the EAGLE5 ISS because the EAGLE 5 ISS does not support the VFY-ORcommand.



Conformance testing with Telcordia indicated that thesyntax for the VFY-RTE command is implemented

Partially Compliant(CR) 7-203differently by the SEAS mainframe than that specified inthe SEAS-STP Interface Specification, GR-310-CORE, Issue1, November 1994. However, the EAGLE 5 ISS does supportboth the implemented syntax and the specified syntax. TheEAGLE 5 ISS is fully compliant with the implementedsyntax. In the specified syntax, the EAGLE 5 ISS does not

311910-6013-001 Revision A, March 2011



support ranges for the destination address parameter, nordoes it support wildcards, except for the **-**-***, ni-nc-**,and ni-nc-*** combinations. Also, the output syntax appearsto have been implemented differently, but currently thisissue has yet to be resolved.

The EAGLE 5 ISS does not support needed link set recentchange and verify enhancements, because this is a SEASpost-7.0 feature.


The EAGLE 5 ISS does not support ranges for the membernumber parameter. Also, the EAGLE 5 ISS does not support1.5 Mbps link speed, because this is a SEAS post-7.0 feature.



The EAGLE 5 ISS does not support the relative costparameter. On input, the EAGLE 5 ISS ignores this


parameter. On output, EAGLE 5 ISS displays the value offifty (50) since this parameter is mandatory in the outputsyntax. The EAGLE 5 ISS can also display a blank (‘ ’) valuefor the routing indicator attribute under certain conditionswhen this value has been configured locally. Also, theEAGLE 5 ISS does not support vacant global title addresses,because this is SEAS post-7.0 feature.


The EAGLE 5 ISS does not support the VFY-SPCSPcommand. The EAGLE 5 ISS supports only shared


concerned signaling point lists for its subsystem prohibitedconcerned signaling points entity set. However, this featureis a SEAS post-7.0 feature, therefore the EAGLE 5 ISS cannotsupport this command until this feature is implemented inSEAS. The Flow-Through commands can still be used toretrieve this entity set.

The EAGLE 5 ISS does not support ranges for thedestination address parameter, nor does it support every

Partially Compliant(CR) 7-210combination of wildcards for this parameter. Also, thereporting of PRML (prohibited due to MTP loop detection,for example, circular routing) as the status for a route is notsupported. Even though the EAGLE 5 ISS MTP (LIM) cardsdetect circular routing, they report the circular routingcondition not on a route basis, but on a destination basis.

312910-6013-001 Revision A, March 2011



The MTP card does not change the route’s status toPROHIBITED in every situation where circular routing isdetected on the route. Reporting of ULP (unavailable dueto MTP loop detected) for a destination’s routeset (DA) issupported. Finally, route status blocks in the output reportwill contain null (“”) values for the FECLLI parameter (thatis, CLLI of the linkset’s adjacent point code) if no CLLI hasbeen defined locally for the APC. The SEAS-STP InterfaceSpecification, GR-310-CORE, Issue 1, November 1994, doesnot explicitly state that reporting a null CLLI is allowed.The SEAS-STP Interface Specification, GR-310-CORE, Issue1, November 1994, does state that the CLLI reported for theDI output value can be null, but it makes no similarstatement regarding the FECLLI value, thus the implicationthat the FECLLI value can not be null.

The EAGLE 5 ISS does not support ranges for thedestination address parameter, nor does it support

Partially Compliant(CR) 7-211 wildcards, except for the **-**-***, ni-nc-**, and ni-nc-***combinations. Also, the EAGLE 5 ISS does not support MTPcircular route (loop) detection, because this is a SEASpost-7.0 feature.



This conditional requirement does not apply to the EAGLE5 ISS because recent change and verify for the STP optionsentity set is a SEAS post-7.0 feature.








313910-6013-001 Revision A, March 2011







The EAGLE 5 ISS does not support the merge process fordata output.Not Compliant(R) 7-219




The EAGLE 5 ISS does not support the sorting of orderedroute data for output.Not Compliant(O) 7-223










The EAGLE 5 ISS does not support the merge process fordata output.Not Compliant(CR) 7-233

314910-6013-001 Revision A, March 2011










The EAGLE 5 ISS does not support the VFY-SPCSPcommand.Not Compliant(CR) 7-241

The EAGLE 5 ISS does not support the VFY-SPCSPcommand.Not Compliant(R) 7-242





The EAGLE 5 ISS does not support the reporting ofcongestion status for a given destination for the

Not Compliant(R) 7-247VFY-SRSAPST command. The EAGLE 5 ISS MTP cards(LIMs) are aware of destination congestion, but they usethis information internally and do not report congestionstatus to the maintenance subsystem. Thus, information isnot available to the VFY-SRSAPST command.



315910-6013-001 Revision A, March 2011







The EAGLE 5 ISS maintains the routeset sorted in increasingrelative cost, thus the output report will list the individual

Partially Compliant(O) 7-254 routes in increasing relative cost order, as required.However, if two routes have the same relative cost, thenthe requirement states that the routes be output sorted bylinkset name. This may not always occur.








The EAGLE 5 ISS does not support the sorting of destinationdata output.Not Compliant(O) 7-262

The EAGLE 5 ISS does not support the sorting of destinationdata output.Not Compliant(CR) 7-263

This conditional requirement does not apply to the EAGLE5 ISS because the VFY-SCCPAPL command is a SEASpost-7.0 feature.


316910-6013-001 Revision A, March 2011



This conditional requirement does not apply to the EAGLE5 ISS because the VFY-MGTT-TTSSN command is a SEASpost-7.0 feature.


This requirement does not apply to the EAGLE 5 ISSbecause the VFY-MGTT-GTADPC command is a SEASpost-7.0 feature.


This objective does not apply to the EAGLE 5 ISS becausethe VFY-MGTT-GTADPC command is a SEAS post-7.0feature.


This requirement does not apply to the EAGLE 5 ISSbecause the VFY-MGTT-GTADPC command is a SEASpost-7.0 feature.


This conditional requirement does not apply to the EAGLE5 ISS because the VFY-MGTT-GTADPC command is a SEASpost-7.0 feature.


This conditional requirement does not apply to the EAGLE5 ISS because the VFY-MGTT-ORDPC command is a SEASpost-7.0 feature.


This conditional requirement does not apply to the EAGLE5 ISS because the VFY-ISNI-CICICN command is a SEASpost-7.0 feature.


This conditional requirement does not apply to the EAGLE5 ISS because the VFY-ISNI-CICICN command is a SEASpost-7.0 feature.


This conditional requirement does not apply to the EAGLE5 ISS because the VFY-ISNI-ICNDPC command is a SEASpost-7.0 feature.


Table 26: Section 8. On-Occurrence Autonomous Messages


The EAGLE 5 ISS does not currently support theREPT-RCINT message.Not Compliant(CR) 8-1

317910-6013-001 Revision A, March 2011






This conditional requirement does not apply to the EAGLE5 ISS because surveillance for cluster routing andmanagement is a SEAS post-7.0 feature.














This conditional requirement does not apply to the EAGLE5 ISS because XUDT message processing surveillance is aSEAS post-7.0 feature.




318910-6013-001 Revision A, March 2011



This conditional requirement does not apply to the EAGLE5 ISS because surveillance for SCCP ISNI message routingis a SEAS post-7.0 feature.








This conditional requirement does not apply to the EAGLE5 ISS because surveillance for MTP restart and STPprocessor overload is a SEAS post-7.0 feature.














319910-6013-001 Revision A, March 2011







The EAGLE 5 ISS reports the threshold parameter as MSUsinstead of MSU octets for its threshold calculations.Partially Compliant(CR) 8-30

The EAGLE 5 ISS reports the threshold parameter as MSUsinstead of MSU octets for its threshold calculations.Partially Compliant(CR) 8-31



The EAGLE 5 ISS does not currently support reporting ofthe following codes for the REPT-LKF message: XLR, MMR,

Partially Compliant(CR) 8-34 SLT, RMI, LPO, MBL, MRS, and MMA. Also, the EAGLE 5 ISSdoes not support surveillance for link oscillation filter -delayed link restoration, because this is a SEAS post-7.0feature.


This conditional requirement does not apply to the EAGLE5 ISS because surveillance of manually caused link outagesis a SEAS post-7.0 feature.


This conditional requirement does not apply to the EAGLE5 ISS because surveillance of manually caused link outagesis a SEAS post-7.0 feature.


The EAGLE 5 ISS does not currently support theREPT-ADMPR-CGST message.Not Compliant(CR) 8-38

The EAGLE 5 ISS does not currently support theREPT-ADMPR-CGST message.Not Compliant(CR) 8-39

The EAGLE 5 ISS does not support storage of autonomousmessages for retransmission.Not Compliant(R) 8-40

320910-6013-001 Revision A, March 2011




This requirement does not apply to the EAGLE 5 ISSbecause the EAGLE 5 ISS does not support storage ofautonomous messages for retransmission.


The EAGLE 5 ISS supports the limiting of output using therequired default values. The EAGLE 5 ISS does not support

Fully Compliant(R) 8-43 the administration of these values through theUPD-STPOPTS command as the STP options entity set is aSEAS post-7.0 feature.

The EAGLE 5 ISS supports the limiting of output using therequired default values. The EAGLE 5 ISS does not support

Fully Compliant(R) 8-44 the administration of these values through theUPD-STPOPTS command as the STP options entity set is aSEAS post-7.0 feature.

This requirement does not apply to the EAGLE 5 ISSbecause XUDT message processing surveillance is a SEASpost-7.0 feature.




This requirement does not apply to the EAGLE 5 ISSbecause XUDT message processing surveillance is a SEASpost-7.0 feature.


This requirement does not apply to the EAGLE 5 ISSbecause surveillance for SCCP ISNI message routing is aSEAS post-7.0 feature.



The EAGLE 5 ISS does not support storage of autonomousmessages for retransmission.Not Compliant(O) 8-50

This objective does not apply to the EAGLE 5 ISS becausesurveillance for MTP restart and STP processor overloadis a SEAS post-7.0 feature.


321910-6013-001 Revision A, March 2011





This requirement does not apply to the EAGLE 5 ISSbecause surveillance for MTP restart and STP processoroverload is a SEAS post-7.0 feature.




















322910-6013-001 Revision A, March 2011










The EAGLE 5 ISS does not guarantee sequencing ofmessages on output.Not Compliant(O) 8-70

This requirement does not apply to the EAGLE 5 ISSbecause surveillance of manually caused link outages is aSEAS post-7.0 feature.


This objective does not apply to the EAGLE 5 ISS becausesurveillance of manually caused link outages is a SEASpost-7.0 feature.





Table 27: Section 9. STP Application Control Commands


The EAGLE 5 ISS does not support the INH-COLLcommand.Not Compliant(CR) 9-1

323910-6013-001 Revision A, March 2011



The EAGLE 5 ISS does not support the ALW-COLLcommand.Not Compliant(CR) 9-2

This conditional requirement does not apply to the EAGLE5 ISS because MTP special study parameter administrationis a SEAS deferred feature.








This conditional requirement does not apply to the EAGLE5 ISS because administration of marginal link performancethresholds for maintenance is a SEAS deferred feature.


This conditional requirement does not apply to the EAGLE5 ISS because administration of SS7 network managementparameters is a SEAS deferred feature.


This conditional requirement does not apply to the EAGLE5 ISS because administration of SS7 network managementparameters is a SEAS deferred feature.


This conditional requirement does not apply to the EAGLE5 ISS because STP data base administration is a SEASdeferred feature.


Table 28: Section 10. Transparent Mode (Flow-Through) Messages




324910-6013-001 Revision A, March 2011




Table 29: Section 11. Performance and Capacity




The completion responses to verify commands that containlarge amounts of data could take greater than 60 seconds.Partially Compliant(R) 11-3 The error response on input TMC=SG99 will take muchlonger than 60 seconds.






Table 30: Section 12. Message Priority and Routing




The EAGLE 5 ISS does not provide a means for configuringmessage loads among the non-time critical channels.Not Compliant(O) 12-3


325910-6013-001 Revision A, March 2011





Table 31: Section 13. Routing Verification Test Messages


This conditional requirement does not apply to the EAGLE5 ISS because OMAP routing verification tests are a SEASpost-7.0 feature.
















326910-6013-001 Revision A, March 2011























327910-6013-001 Revision A, March 2011


Table 32: Appendix A. Data Collection Request Structure


The EAGLE 5 ISS does not support supplier-specific datacollection mnemonics for non-standard collection schedules.Not Compliant(R) A-1

Fully Compliant(R) A-2

The EAGLE 5 ISS does not support supplier-specific datacollection mnemonics for non-standard measured entitytypes.

Not Compliant(R) A-3

The EAGLE 5 ISS does not support supplier-specific datacollection mnemonics for non-standard measured entitytypes.

Not Compliant(R) A-4

The new non-standard measurement registers defined forRelease 21.0 and beyond conform to supplier-specific datacollection mnemonics.

Partially Compliant(R) A-5

The new non-standard measurement registers defined forRelease 21.0 and beyond conform to supplier-specific datacollection mnemonics.

Partially Compliant(R) A-6









328910-6013-001 Revision A, March 2011


Table 33: Appendix B. Standard Data Collection Schedules


Fully Compliant(R) B-1









Fully Compliant(O) B-10

This requirement does not apply to the EAGLE 5 ISSbecause GTT (and MTP routing) error surveillanceimprovements is a SEAS post-7.0 feature.

Not Applicable(R) B-11








The EAGLE 5 ISS does not support this measurement in itsSTP system totals (P_SYSTOT) measurements schedule.Not Compliant(O) B-16

329910-6013-001 Revision A, March 2011



The EAGLE 5 ISS does not support this measurement in itsSTP system totals (P_SYSTOT) measurements schedule.Not Compliant(O) B-17


This requirement does not apply to the EAGLE 5 ISSbecause SCCP ISNI message routing is a SEAS post-7.0feature.




This objective does not apply to the EAGLE 5 ISS becauseSCCP ISNI message routing is a SEAS post-7.0 feature.Not Applicable(O) B-21













This objective does not apply to the EAGLE 5 ISS becauseGTT (and MTP routing) error surveillance improvementsis a SEAS post-7.0 feature.

Not Applicable(O) B-29

330910-6013-001 Revision A, March 2011










The EAGLE 5 ISS does not support the TT entity type.Not Compliant(O) B-34

This requirement does not apply to the EAGLE 5 ISSbecause SCCP application support is a SEAS post-7.0feature.






The EAGLE 5 ISS does not support this measurement in itscomponent (P_COMP) measurements schedule.Not Compliant(O) B-40






331910-6013-001 Revision A, March 2011














The EAGLE 5 ISS does not support this measurement in itscomponent (P_COMP) measurements schedule.Not Compliant(R) B-57






332910-6013-001 Revision A, March 2011














The EAGLE 5 ISS does not support the BFRGRP entity type.Not Compliant(O) B-74

The EAGLE 5 ISS does not support the BUFFR entity type.Not Compliant(O) B-75



The EAGLE 5 ISS does not support the PROC entity type.Not Compliant(O) B-78

The EAGLE 5 ISS does not support the PROC entity type.Not Compliant(CR) B-79



The EAGLE 5 ISS does not support the PROC entity type.Not Compliant(R) B-82

333910-6013-001 Revision A, March 2011












The EAGLE 5 ISS does not support the PROCGRP entitytype.Not Compliant(O) B-92








334910-6013-001 Revision A, March 2011






EAGLE 5 ISS does not support the PROCGRP entity type.Not Compliant(O) B-103

EAGLE 5 ISS does not support the PROCGRP entity type.Not Compliant(O) B-104


The EAGLE 5 ISS does not support the BUS entity type.Not Compliant(O) B-106



The EAGLE 5 ISS does not support the servicemeasurements (P_SERV) schedule.Not Compliant(O) B-109







335910-6013-001 Revision A, March 2011






The EAGLE 5 ISS does not support the servicemeasurements (P_SERV) schedule.Not Compliant(R) B-119








This conditional requirement does not apply to the EAGLE5 ISS because the special study measurements (P_SPST)schedule is a SEAS deferred feature.

Not Applicable(CR) B-127



336910-6013-001 Revision A, March 2011




















The EAGLE 5 ISS does not support this measurement in itsin-service record base (P_RBASE) measurements schedule.Not Compliant(O) B-140



337910-6013-001 Revision A, March 2011










This objective does not apply because this measurement iscurrently unassigned and reserved for future use by SEAS.Not Applicable(O) B-150













338910-6013-001 Revision A, March 2011




















The EAGLE 5 ISS does not support this measurement in itsin-service record base (P_RBASE) measurements schedule.Not Compliant(CR) B-180

339910-6013-001 Revision A, March 2011






This register is reported on a per-link basis and not part ofthe LNKSET entity type.Partially Compliant(O) B-184












340910-6013-001 Revision A, March 2011














This register is both not supported and not reported.Not Compliant(O) B-207



The value reported is hardcoded and non-provisionable.Partially Compliant(O) B-210


341910-6013-001 Revision A, March 2011















.Fully Compliant(O) B-224







342910-6013-001 Revision A, March 2011




The EAGLE 5 ISS does not support the supplier-specificentity types.Not Compliant(O) B-232

















The EAGLE 5 ISS does not support this measurement in itsdaily maintenance (P_MTCD) measurements schedule.Not Compliant(O) B-245


343910-6013-001 Revision A, March 2011








The EAGLE 5 ISS does not support this measurement in itsdaily maintenance (P_MTCD) measurements schedule.Not Compliant(CR) B-252




The EAGLE 5 ISS does not support this measurement in itsdaily maintenance (P_MTCD) measurements schedule.Not Compliant(R) B-256






344910-6013-001 Revision A, March 2011






















345910-6013-001 Revision A, March 2011











The value is approximated by dividing the number of octetsreceived by the link speed (in octets/second)Partially Compliant(R) B-282








This value is the number of signaling units received withbad CRC.Partially Compliant(R) B-290

The EAGLE 5 ISS does not support this measurement in itsdaily maintenance (P_MTCD) measurements schedule.Not Compliant(O) 2-291

346910-6013-001 Revision A, March 2011



The EAGLE 5 ISS does not support this measurement in itsdaily maintenance (P_MTCD) measurements schedule.Not Compliant(O) 2-292

















347910-6013-001 Revision A, March 2011




















348910-6013-001 Revision A, March 2011








The EAGLE 5 ISS does not support the PROC entity typeNot Compliant(O) B-331





The EAGLE 5 ISS does not support the PROC entity typeNot Compliant(R) B-336




The EAGLE 5 ISS does not support the networkmanagement on-demand measurements (D_NM) schedule.Not Compliant(O) B-340


349910-6013-001 Revision A, March 2011





The EAGLE 5 ISS does not support the hourly maintenance(on-demand) measurements (D_MTCH) schedule.Not Compliant(O) B-344



The EAGLE 5 ISS does not support the hourly maintenance(on-demand) measurements (D_MTCH) schedule.Not Compliant(R) B-347







The EAGLE 5 ISS does not support the hourly maintenance(on-demand) measurements (D_MTCH) schedule.Not Compliant(CR) B-354


350910-6013-001 Revision A, March 2011

















351910-6013-001 Revision A, March 2011














The EAGLE 5 ISS does not support the maintenance statusindicators (on-demand) measurements (D_MTCS) schedule.Not Compliant(O) B-381



352910-6013-001 Revision A, March 2011



















353910-6013-001 Revision A, March 2011
















The EAGLE 5 ISS does not support this measurement in itsnetwork management measurements (A_NM) schedule.Not Compliant(O) B-409





354910-6013-001 Revision A, March 2011










The EAGLE 5 ISS does not support this measurement in itsnetwork management measurements (A_NM) schedule.Not Compliant(R) B-421

The EAGLE 5 ISS does not support this measurement in itsnetwork management measurements (A_NM) schedule.Not Compliant(R) B-422







355910-6013-001 Revision A, March 2011



















356910-6013-001 Revision A, March 2011


SEAS-STP Gateway Function Interface Specification, GR-778-CORE, Issue1, November 1994

Table 34: Section 3. Recent Change and Verify Gateway Messages


The EAGLE 5 ISS does not support the parameters fordelayed activation, the link set group identifier parameter,

Partially Compliant(R) 3-1 the remarks parameter, nor the supplier-specific parameterblock. Also, the EAGLE 5 ISS does not support new inputvalidations, because this is a SEAS post-7.0 feature.

The EAGLE 5 ISS does not support the parameters fordelayed activation. Also, the EAGLE 5 ISS does not supportPartially Compliant(R) 3-2 new input validations, because this is a SEAS post-7.0feature.

The EAGLE 5 ISS does not support the parameters fordelayed activation, the new link set group identifier

Partially Compliant(R) 3-3 parameter, the new remarks parameter, nor the newsupplier-specific parameter block. also, the EAGLE 5 ISSdoes not support new input validations, because this is aSEAS post-7.0 feature.

The EAGLE 5 ISS does not support ranges the parametersfor delayed activation, the remarks parameter, nor the

Partially Compliant(R) 3-4 supplier-specific parameter block. Also, the EAGLE 5 ISSdoes not support rejection message suppression on a perscreen basis and new input validations, because these areSEAS post-7.0 features.

The EAGLE 5 ISS does not support deleting all OPCs for ascreening reference (the value ‘**’ for the NC and NCM

Partially Compliant(R) 3-5 parameters), nor the parameters for delayed activation.Also, the EAGLE 5 ISS does not support rejection messagesuppression on a per screen basis and new inputvalidations, because these are SEAS post-7.0 features.

The EAGLE 5 ISS does not support changing all OPCs fora screening reference (the value ‘**’ for the NC and NCM

Partially Compliant(R) 3-6 parameters), the parameters for delayed activation, the newremarks parameter, nor the new supplier-specific parameterblock. Also, the EAGLE 5 ISS does not support rejection

357910-6013-001 Revision A, March 2011



message suppression on a per screen basis and new inputvalidations, because these are SEAS post-7.0 features.

The EAGLE 5 ISS does not support the parameters fordelayed activation, the remarks parameter, nor the

Partially Compliant(R) 3-7 supplier-specific parameter block. Also, the EAGLE 5 ISSdoes not support ISUP message type screening, rejectionmessage suppression on a per screen basis, and new inputvalidations, because these are SEAS post-7.0 features.

The EAGLE 5 ISS does not support deleting all DPCs for ascreening reference (the value ‘**’ for the NC and NCM

Partially Compliant(R) 3-8 parameters), nor the parameters for delayed activation.Also, the EAGLE 5 ISS does not support rejection messagesuppression on a per screen basis and new inputvalidations, because these are SEAS post-7.0 features.

The EAGLE 5 ISS does not support changing all DPCs fora screening reference (the value ‘**’ for the current NC and


current NCM parameters), the parameters for delayedactivation, the new remarks parameter, nor the newsupplier-specific parameter block. Also, the EAGLE 5 ISSdoes not support ISUP message type screening, rejectionmessage suppression on a per screen basis, and new inputvalidations, because these are SEAS post-7.0 features.


Partially Compliant(R) 3-10 supplier-specific parameter block. Also, the EAGLE 5 ISSdoes not support new input validations, because this is aSEAS post-7.0 feature.

The EAGLE 5 ISS does not support deleting all blockedOPCs for a screening reference (the value ‘**’ for the NC and

Partially Compliant(R) 3-11 NCM parameters), nor the parameters for delayed activation.Also, the EAGLE 5 ISS does not support new inputvalidations, because this is a SEAS post-7.0 feature.

The EAGLE 5 ISS does not support changing all blockedOPCs for a screening reference (the value ‘**’ for the current

Partially Compliant(R) 3-12NC and current NCM parameters), the parameters for delayedactivation, the new remarks parameter, nor the newsupplier-specific parameter block. Also, the EAGLE 5 ISSdoes not support new input validations, because this is aSEAS post-7.0 feature.

358910-6013-001 Revision A, March 2011




Partially Compliant(R) 3-13 supplier-specific parameter block. Also, the EAGLE 5 ISSdoes not support ISUP message type screening and newinput validations, because these are SEAS post-7.0 features.

The EAGLE 5 ISS does not support deleting all blockedDPCs for a screening reference (the value ‘**’ for the NC and

Partially Compliant(R) 3-14 NCM parameters), nor the parameters for delayed activation.Also, the EAGLE 5 ISS does not support ISUP message typescreening and new input validations, because these areSEAS post-7.0 features.

The EAGLE 5 ISS does not support changing all blockedDPCs for a screening reference (the value ‘**’ for the current

Partially Compliant(R) 3-15NC and current NCM parameters), the parameters for delayedactivation, the new remarks parameter, nor the newsupplier-specific parameter block. Also, the EAGLE 5 ISSdoes not support new input validations, because this is aSEAS post-7.0 feature.

The EAGLE 5 ISS does not support ranges for the serviceindicator and network indicator parameters, the parameters

Partially Compliant(R) 3-16for delayed activation, the remarks parameter, nor thesupplier-specific parameter block. Also, the EAGLE 5 ISSdoes not support ISUP message type screening, rejectionmessage suppression on a per screen basis, and new inputvalidations, because these are SEAS post-7.0 features.

The EAGLE 5 ISS does not support deleting all SIOs for ascreening reference (the ‘**’ value for the network indicator


and message priority parameters), ranges for the serviceindicator (SI) and network indicator (NIC) parameters, theparameters for delayed activation, nor the message priorityparameter. Also, the EAGLE 5 ISS does not support ISUPmessage type screening, rejection message suppression ona per screen basis, and new input validations, because theseare SEAS post-7.0 features.

The EAGLE 5 ISS does not support changing all SIOs for ascreening reference (the value ‘**’ for the current network

Partially Compliant(R) 3-18 indicator and current message priority parameters), rangesfor the current service indicator, new service indicator,current network indicator or new network indicatorparameters, the parameters for delayed activation, the new

359910-6013-001 Revision A, March 2011



remarks parameter, nor the new supplier-specific parameterblock. Also, the EAGLE 5 ISS does not support rejectionmessage suppression on a per screen basis and new inputvalidations, because these are SEAS post-7.0 features.

The EAGLE 5 ISS does not support ranges for the subsystemnumber parameter, the parameters for delayed activation,

Partially Compliant(R) 3-19the link set group identifier parameter, the remarksparameter, nor the supplier-specific parameter block. Also,the EAGLE 5 ISS does not support SCCP message typescreening and rejection message suppression on a per screenbasis, because these are SEAS post-7.0 features.

The EAGLE 5 ISS does not support deleting all CGPAs fora screening reference (the value ‘**’ for the NC, NCM, and


routing indicator parameters), ranges for the subsystemnumber parameter, the parameters for delayed activation,nor the link set group identifier parameter. Also, the EAGLE5 ISS does not support SCCP message type screening andrejection message suppression on a per screen basis, becausethese are SEAS post-7.0 features.

The EAGLE 5 ISS does not support changing all CGPAs fora screening reference (the value ‘**’ for the current NC,


current NCM, and current routing indicator parameters),ranges for the current subsystem number and newsubsystem number parameters, the parameters for delayedactivation, the link set group identifier parameter, the newlink set identifier parameter, the new remarks parameter,nor the new supplier-specific parameter block. Also, theEAGLE 5 ISS does not support SCCP message typescreening and rejection message suppression on a per screenbasis, because these are SEAS post-7.0 features.


Partially Compliant(R) 3-22 the remarks parameter, nor the supplier-specific parameterblock. Also, the EAGLE 5 ISS does not support rejectionmessage suppression on a per screen basis, because this isa SEAS post-7.0 feature.

The EAGLE 5 ISS does not support deleting all CDPAs fora screening reference (the value ‘**’ for the NC, NCM, and

Partially Compliant(R) 3-23 SCMG format identifier parameters), ranges for thesubsystem number parameter, nor the parameters fordelayed activation. Also, the EAGLE 5 ISS does not support

360910-6013-001 Revision A, March 2011



rejection message suppression on a per screen basis, becausethis is a SEAS post-7.0 feature.

The EAGLE 5 ISS does not support changing all CDPAs fora screening reference (the value ‘**’ for the current NC,


current NCM, and current SCMG format identifierparameters), ranges for the current subsystem number andnew subsystem number parameters, the parameters fordelayed activation, the new remarks parameter, nor thenew supplier-specific parameter block. Also, the EAGLE 5ISS does not support rejection message suppression on aper screen basis, because this is a SEAS post-7.0 feature.


Partially Compliant(R) 3-25 supplier-specific parameter block. Also, the EAGLE 5 ISSdoes not support rejection message suppression on a perscreen basis and new input validations, because these areSEAS post-7.0 features.

The EAGLE 5 ISS does not support the parameters fordelayed activation. Also, the EAGLE 5 ISS does not support

Partially Compliant(R) 3-26 rejection message suppression on a per screen basis andnew input validations, because these are SEAS post-7.0features.

The EAGLE 5 ISS does not support the parameters fordelayed activation, the new remarks parameter, nor the

Partially Compliant(R) 3-27 new supplier-specific parameter block. Also, the EAGLE 5ISS does not support rejection message suppression on aper screen basis and new input validations, because theseare SEAS post-7.0 features.


Partially Compliant(R) 3-28 supplier-specific parameter block. Also, the EAGLE 5 ISSdoes not support rejection message suppression on a perscreen basis and new input validations, as these are SEASpost-7.0 features.

The EAGLE 5 ISS does not support deleting all DESTFLDsfor a screening reference (the value ‘**’ for the NC and NCMPartially Compliant(R) 3-29parameters), nor the parameters for delayed activation.Also, the EAGLE 5 ISS does not support rejection message

361910-6013-001 Revision A, March 2011



suppression on a per screen basis and new inputvalidations, as these are SEAS post-7.0 features.

The EAGLE 5 ISS does not support changing all DESTFLDsfor a screening reference (the value ‘**’ for the current NC


and current NCM parameters), the parameters for delayedactivation, the new remarks parameter, nor the newsupplier-specific parameter block. Also, the EAGLE 5 ISSdoes not support rejection message suppression on a perscreen basis and new input validations, as these are SEASpost-7.0 features.


Partially Compliant(R) 3-31 the remarks parameter, nor the supplier-specific parameterblock. Also, the EAGLE 5 ISS does not support rejectionmessage suppression on a per screen basis and new inputvalidations, as these are SEAS post-7.0 features

The EAGLE 5 ISS does not support deleting all AFTPCs fora screening reference (the value ‘**’ for the NC, NCM, and

Partially Compliant(R) 3-32subsystem number parameters), ranges for the subsystemnumber parameter, nor the parameters for delayedactivation. Also, the EAGLE 5 ISS does not support rejectionmessage suppression on a per screen basis and new inputvalidations, as these are SEAS post-7.0 features.

The EAGLE 5 ISS does not support changing all AFTPCsfor a screening reference (the value ‘**’ for the current NC,


current NCM, and current subsystem number parameters),ranges for the current subsystem number and newsubsystem number parameters, the parameters for delayedactivation, the new remarks parameter, nor the newsupplier-specific parameter block. Also, the EAGLE 5 ISSdoes not support rejection message suppression on a perscreen basis and new input validations, as these are SEASpost-7.0 features.

The EAGLE 5 ISS does not support the parameters fordelayed activation, the New Remarks parameter, nor the

Partially Compliant(R) 3-34 New Supplier-Specific Parameter block. Also, the EAGLE5 ISS does not support Rejection Message Suppression ona per screen basis and New Input Validations as these areSEAS post-7.0 feature.

362910-6013-001 Revision A, March 2011



The EAGLE 5 ISS does not support deleting all ISUPMessage types for a screening reference (the null value for

Partially Compliant(R) 3-35the ISUP parameter), the parameters for delayed activation,the New Remarks parameter, nor the New Supplier-SpecificParameter block. Also, the EAGLE 5 ISS does not supportRejection Message Suppression on a per screen basis andNew Input Validations as these are SEAS post-7.0 feature.

The EAGLE 5 ISS does not support changing all ISUPMessage Types for a screening reference (the null value for


the ISUP and NISUP parameters), the parameters fordelayed activation, the new remarks parameter, nor thenew supplier-specific parameter block. Also, the EAGLE 5ISS does not support rejection message suppression on aper screen basis and new input validations, as these areSEAS post-7.0 features.

This conditional requirement does not apply to the EAGLE5 ISS because translation type mapping is a SEAS deferredfeature.








The EAGLE 5 ISS does not support new input validations,as this is a SEAS post-7.0 feature.Fully Compliant(R) 3-41

The EAGLE 5 ISS does not support rejection messagesuppression on a per screen basis and new inputvalidations, because these are SEAS post-7.0 features.


The EAGLE 5 ISS does not support ISUP message typescreening, rejection message suppression on a per screenFully Compliant(R) 3-43 basis, and new input validations, because these are SEASpost-7.0 features.

363910-6013-001 Revision A, March 2011



The EAGLE 5 ISS does not support new input validations,because this is a SEAS post-7.0 feature.Fully Compliant(R) 3-44

The EAGLE 5 ISS does not support ISUP message typescreening and new input validations, because these areSEAS post-7.0 features.


The EAGLE 5 ISS does not support ranges for the serviceindicator and network indicator parameters. Also, the

Partially Compliant(R) 3-46 EAGLE 5 ISS does not support ISUP message typescreening, rejection message suppression on a per screenbasis, and new input validations, as these are SEAS post-7.0features

The EAGLE 5 ISS does not support ranges for the subsystemnumber parameter, nor does it support the link set identifier

Partially Compliant(R) 3-47 parameter. also, the EAGLE 5 ISS does not support SCCPmessage type screening and rejection message suppressionon a per screen basis, as these are SEAS post-7.0 features.

The EAGLE 5 ISS does not support ranges for the subsystemnumber parameter. Also, the EAGLE 5 ISS does not supportPartially Compliant(R) 3-48 rejection message suppression on a per screen basis, as thisis a SEAS post-7.0 feature.

The EAGLE 5 ISS does not support rejection messagesuppression on a per screen basis and new inputvalidations, because these are SEAS post-7.0 features.


The EAGLE 5 ISS does not support rejection messagesuppression on a per screen basis and new inputvalidations, as these are SEAS post-7.0 features.


The EAGLE 5 ISS does not support ranges for the subsystemnumber parameter. Also, the EAGLE 5 ISS does not support

Partially Compliant(R) 3-51 rejection message suppression on a per screen basis andnew input validations, because these are SEAS post-7.0features.

The EAGLE 5 ISS does not support rejection messagesuppression on a per screen basis and new inputvalidations, as these are SEAS post-7.0 features.


364910-6013-001 Revision A, March 2011



This requirement does not apply to the EAGLE 5 ISSbecause translation type mapping is a SEAS deferredfeature.


The EAGLE 5 ISS does not support translation typemapping, because this is a SEAS deferred feature.Partially Compliant(R) 3-54

This requirement does not apply to the EAGLE 5 ISSbecause new screening errors is a SEAS post-7.0 feature.Not Applicable(R) 3-55












365910-6013-001 Revision A, March 2011






Table 35: Section 4. Gateway On-Occurrence Autonomous Messages



The EAGLE 5 ISS currently only supports the “GTWYLS”value for the entity set name parameter. The EAGLE 5 ISS

Partially Compliant(R) 4-2 does not support ISUP message type screening, SS7 messageinclusion in rejection message, and additional fields thatsupport PCS applications, as these are SEAS post-7.0features.

The EAGLE 5 ISS does not currently support theREPT-SCRERR message.Not Compliant(R) 4-3

Table 36: Section 5. Gateway Application Control Messages


The EAGLE 5 ISS does not support the INH-COLLcommand.Not Compliant(R) 5-1

The EAGLE 5 ISS does not support the ALW-COLLcommand.Not Compliant(R) 5-2

The new values are set and used immediately. The current(possibly in-use) values are replaced.Partially Compliant(R) 5-3

New values are set and used immediately. The current(possibly in-use) values are replaced. The EAGLE 5 ISS does


366910-6013-001 Revision A, March 2011



not support the SS7 message inclusion indicator parameteras this is a SEAS post-7.0 feature

The EAGLE 5 ISS does not currently support theSET-SCRERR-PRMTRS message.Not Compliant(R) 5-5



This requirement does not apply to the EAGLE 5 ISSbecause new input validations is a SEAS post-7.0 feature.Not Applicable(R) 5-8




Table 37: Section 6. STP Gateway Data Collection


See Table 24: Section 6. Data Collection Messages.Partially Compliant(R) 6-1

The P_GTWY measurements schedule is being supportedwith the limitation that only the STP, ORIGNI, ORIGNINC,


LNKSET, LSDESTNI and LSORIGNI entity types aresupported. The ALL and ACTIVE values for the periodparameter to the SEND-DEM-MEAS and SEND-SCH-MEASis not supported for this schedule. Furthermore, the numberof entities is limited to the given value for the following(new) entity types:

ORIGNI = 60

ORIGNINC = 800

LSDESTNI = 3000 (and limited to 60 per linkset)

LSORIGNI = 1000 (and limited to 60 per linkset)

367910-6013-001 Revision A, March 2011



This objective does not apply to the EAGLE 5 ISS becausethe gateway STP detailed rejection (P_GWREJ)measurement schedule is a SEAS deferred feature.


The EAGLE 5 ISS does not currently support the gatewaydaily maintenance (P_GMTCD) measurement schedule.Not Compliant(R) 6-4

The EAGLE 5 ISS does not currently support the gatewayhourly maintenance (P_GMTCH) measurement schedule.Not Compliant(R) 6-5

The EAGLE 5 ISS does not currently support per originatingnetwork identifier, per translation type (ORIGNITT), per


originating network identifier, per originating networkcluster, per translation type (ONIONCTT), per link set, peroriginating network identifier, per destination point code,per service identifier (LSONDPSI), per link set, peroriginating network identifier, per affected destination field(LSONDEST), per link set, per originating networkidentifier, per calling party address PC and SSN, pertranslation type (LSONCGTT), per link set, per originatingnetwork identifier per calling party address PC and SSN,per DPC and called party address SSN (LSONCGCD), andper link set, per originating network identifier, measuredentity types. Also, the EAGLE 5 ISS does not support theper ISUP message type (LSONISMT) measured entity type,because this is a SEAS post-7.0 feature.

Note: The ORIGNINC entities will only exist for NI - NCcombinations whose network indicator is in the range from1 to 5 (inclusive).





See Table 24: Section 6. Data Collection MessagesPartially Compliant(R) 6-10

The EAGLE 5 ISS does not currently report the particularfield that failed in a gateway message.Not Compliant(O) 6-11

368910-6013-001 Revision A, March 2011



The EAGLE 5 ISS does not currently support service(P_SERV) and gateway daily maintenance (P_GMTCD)measurement schedules.


The EAGLE 5 ISS does not currently support service(P_SERV), gateway daily maintenance (P_GMTCD), and


gateway hourly maintenance (P_GMTCH) measurementschedules, as well as per buffer group (BFRGRP), per buffer(BUFFR), per processor group (PROCGRP), per processor(PROC), per originating network identifier (ORIGNI), peroriginating network identifier, per originating networkcluster (ORIGNINC), per originating network identifier,per translation type (ORIGNITT), per originating networkidentifier, per originating network cluster, per translationtype (ONIONCTT), per link set, per link set, per originatingnetwork identifier, per destination point code, per serviceidentifier (LSONDPSI), per link set, per originating networkidentifier, per affected destination field (LSONDEST), perlink set, per originating network identifier, per calling partyaddress PC and SSN, per translation type (LSONCGTT),per link set, per originating network identifier per callingparty address PC and SSN, per DPC and called partyaddress SSN (LSONCGCD), and per link set, per originatingnetwork identifier, measured entity types. The EAGLE 5ISS does not support the per link set, per translation type(LSTT) and the per translation type (TT) measured entitytypes, as those are SEAS deferred features. Also, the EAGLE5 ISS does not support per ISUP message type (LSONISMT)measured entity type, as this is a SEAS post-7.0 feature.

Note: “ACTIVE” period measurements are not supportedfor schedule P_GTWY.

The EAGLE 5 ISS does not currently support the service(P_SERV), and gateway daily maintenance (P_GMTCD)measurement schedules.


This requirement does not apply to the EAGLE 5 ISSbecause gateway STP detailed rejection measurements is aSEAS deferred feature.


369910-6013-001 Revision A, March 2011


Table 38: Section 8. Performance and Capacity Requirements


Completion responses to commands that contain largeamounts of data could take greater than 60 seconds.Partially Compliant(R) 8-1

The error response on input TMC=SG99 will take muchlonger than 60 seconds.Partially Compliant(R) 8-2

Error responses on execution to commands that containlarge amounts of data could take greater than 60 seconds.Partially Compliant(R) 8-3


The EAGLE 5 ISS does not currently support the INH-COLLor ALW-COLL application control commands.Not Compliant(R) 8-5

The EAGLE 5 ISS does not currently support the INH-COLLor ALW-COLL application control commands.Not Compliant(R) 8-6

The EAGLE 5 ISS does not support the gateway STPdetailed rejection (P_GWREJ) measurement schedule,because this is a SEAS deferred feature.


The EAGLE 5 ISS does not currently support the gatewaydaily maintenance (P_GMTCD) measurement schedule.Not Compliant(R) 8-8

The EAGLE 5 ISS does not currently support the gatewayhourly maintenance (P_GMTCH) measurement schedule.Not Compliant(R) 8-9


The EAGLE 5 ISS does not currently support theREPT-SCRERR message.Not Compliant(R) 8-11




370910-6013-001 Revision A, March 2011





Table 39: Appendix B. Gateway Measurement Definitions and Standard Register Labels




The EAGLE 5 ISS does not support this measurement in itsSTP gateway administration measurements (P_GTWY)schedule.

Not Compliant(O) B-3












371910-6013-001 Revision A, March 2011







Fully Compliant(CR) B-19


Not Compliant(R) B-20






Not Compliant(R) B-25







The EAGLE 5 ISS does not support the ORIGNITT entitytype.Not Compliant(R) B-31

372910-6013-001 Revision A, March 2011



The EAGLE 5 ISS does not support the ORIGNITT entitytype.Not Compliant(R) B-32

The EAGLE 5 ISS does not support the ORIGNITT entitytype.Not Compliant(O) B-33

The EAGLE 5 ISS does not support the ONIONCTT entitytype.Not Compliant(R) B-34

The EAGLE 5 ISS does not support the ONIONCTT entitytype.Not Compliant(R) B-35

The EAGLE 5 ISS does not support the ONIONCTT entitytype.Not Compliant(O) B-36














373910-6013-001 Revision A, March 2011
























374910-6013-001 Revision A, March 2011




















This objective does not apply to the EAGLE 5 ISS becausetranslation type mapping is a SEAS deferred feature.Not Applicable(O) B-83



375910-6013-001 Revision A, March 2011



This objective does not apply to the EAGLE 5 ISS becausetranslation type mapping is a SEAS deferred feature.Not Applicable(O) B-85


Not Implemented.Not Applicable(O) B-87

This requirement does not apply to the EAGLE 5 ISSbecause the gateway STP detailed rejection (P_GWREJ)measurement schedule is a SEAS deferred feature.


















376910-6013-001 Revision A, March 2011





The EAGLE 5 ISS does not support the STP gateway dailymaintenance measurements (P_GMTCD) schedule.Not Compliant(R) B-98

The EAGLE 5 ISS does not support the STP gateway dailymaintenance measurements (P_GMTCD) schedule.Not Compliant(O) B-99

The EAGLE 5 ISS does not support the STP gateway dailymaintenance measurements (P_GMTCD) schedule.Not Compliant(CR) B-100





The EAGLE 5 ISS does not support the STP gateway dailymaintenance measurements (P_GMTCD) schedule.Not Compliant(R) B-105


377910-6013-001 Revision A, March 2011


GlossaryA

The gateway screening entity thatidentifies the point code in the

Allowed Affected Destination Field

affected destination field (theconcerned signaling point code) ofincoming MTP networkmanagement messages from anothernetwork that are allowed into theEAGLE 5 ISS. Messages containingthe specified point code are allowedinto the network.

The gateway screening entity thatidentifies the destination point codes

Allowed DPC

that are allowed to receive SS7messages from the EAGLE 5 ISS.Messages containing the specifieddestination point codes go on to thenext step in the gateway screeningprocess, or are allowed into thenetwork if the gateway screeningprocess stops with this entity.

The gateway screening entity thatidentifies the ISUP or TUP message

Allowed ISUP

types that are allowed into thenetwork.

The gateway screening entity thatidentifies the originating point codes

Allowed OPC

that are allowed to send SS7messages into the network. Messagescontaining the specified originatingpoint codes go on to the next step inthe gateway screening process, orare allowed into the network if thegateway screening process stopswith this entity.

The gateway screening entity thatidentifies the type of MSUs (ISUP,

Allowed SIO

TUP, TCAP, and so forth) that are

378910-6013-001 Revision A, March 2011

A

allowed into the network. Themessage type is determined by thenetwork indicator code (NIC),priority (PRI), and service indicator(SI) fields of the signalinginformation octet (SIO) field in theMSU, and the H0 and H1 headingcodes of the signaling informationfield of the MSU. Messagescontaining the specified messagetype go on to the next step in thegateway screening process, or areallowed into the network if thegateway screening process stopswith this entity.

AIN Number of Digits (in GTTaddress for AIN query)

AND

American National StandardsInstitute

ANSI

An organization that administersand coordinates the U.S. voluntarystandardization and conformityassessment system. ANSI developsand publishes standards. ANSI isa non-commercial,non-government organizationwhich is funded by more than 1000corporations, professional bodies,and enterprises.

Adjacent Point CodeAPC

The point code that identifies a nodeadjacent to the EAGLE 5 ISS. Thisterm is used in link sets and routes.

Adjacent SLS 8-bit IndicatorASL8

Asynchronous Transfer ModeATM

A packet-oriented transfer mode thatuses an asynchronous time division

379910-6013-001 Revision A, March 2011

GlossaryDatabase Administration Manual - SEAS

A

multiplexing technique to multiplexinformation flow in fixed blocks,called cells.

A high-bandwidth, low-delayswitching, and multiplexingtechnology to support applicationsthat include high-speed data, localarea network interconnection,multimedia application and imaging,and residential applications such asvideo telephony and otherinformation-based services.

The application used for high-speedANSI ATM signaling links.

ATMANSI

B

Broadcast Exception IndicatorBEI

C

Carrier Identification CodeCIC

A 4-digit code that controls therouting applied to a message.

Common Language LocationIdentifier

CLLI

The CLLI uniquely identifies the STPin terms of its physical location. It isusually comprised of a combinationof identifiers for the STP’s city (orlocality), state (or province),building, and traffic unit identity.The format of the CLLI is:

The first four characters identify thecity, town, or locality.

The first character of the CLLI mustbe an alphabetical character.

The fifth and sixth charactersidentify state or province.

The seventh and eighth charactersidentify the building.

380910-6013-001 Revision A, March 2011


C

The last three characters identify thetraffic unit.

A group of signaling points whosepoint codes have identical values for

Cluster

the network and cluster fields of thepoint codes. A cluster entry in therouting table is shown as an asterisk(*) in the member field of the pointcode, for example, 111-011-*. Clusterentries can be provisioned only asANSI destination point codes.

Calling Name Conversion FacilityCNCF

CNCF provides a conversion of ISUPIAM messages using calling nameidentification presentation (CNIP)for calling name informationdelivery. CNIP uses eithernon-standard proprietary ISUP partyinformation (PIP) parameter or ANSIstandard ISUP generic name (GN)parameter.

Cards that occupy slots 1113through 1118 of the control shelf

control cards

on an EAGLE 5 ISS and performOAM, TDM, and databasefunctions for the EAGLE 5 ISS. Thelegacy set consists of the single-slotGPSM-II card running the OAMapplication and EOAM GPL, thesingle-slot TDM card, and thedual-slot MDAL card. TheE5-based set consists of thedual-slot E5-MASP card (theE5-MCAP module and the E5-TDMmodule) and the dual-slotE5-MDAL card.

Cluster RoutingCR

Connection Request

381910-6013-001 Revision A, March 2011


C

Cyclic Redundancy CheckCRC

A number derived from, and storedor transmitted with, a block of datain order to detect corruption. Byrecalculating the CRC andcomparing it to the value originallytransmitted, the receiver can detectsome types of transmission errors.

Flash memory credit card-shapeddrive used in the flush-mounted

credit card drive

USB port on an E5-MCAP card forupgrade; it could be used fordisaster recovery.

D

Destination AddressDA

Digit Action

All data that can be administered bythe user, including cards, destination

Database

point codes, gateway screeningtables, global title translation tables,links, LNP services, LNP serviceproviders, location routing numbers,routes, shelves, subsystemapplications, and 10 digit telephonenumbers.

Database Communication ModuleDCM

The DCM provides IP connectivityfor applications. Connection to ahost is achieved through an ethernetLAN using the TCP/IP protocol.

The point code in the affecteddestination field (the concerned

DESTFLD

signaling point code) of incomingMTP network managementmessages from another network thatare allowed into the EAGLE 5 ISS.

382910-6013-001 Revision A, March 2011


D

The node to which the signaling linktraffic is routed. This destination is

Destination

identified by a point code, either afull point code or a cluster pointcode.

Destination Point CodeDPC

DPC refers to the scheme in SS7signaling to identify the receivingsignaling point. In the SS7 network,the point codes are numericaddresses which uniquely identifyeach signaling point. This point codecan be adjacent to the EAGLE 5 ISS,but does not have to be.

Database Transport AccessDTA

A feature in the EAGLE 5 ISS thatencapsulates specific MSUs into thedata portion of SCCP within a newSS7 MSU and sends the new MSUto the destination using global titletranslation. The EAGLE 5 ISS usesgateway screening to determinewhich MSUs are used by the DTAfeature.

E

The European equivalent of T1 thattransmits digital data over atelephone network at 2.048 Mbps.

E1

EPM-based E1/T1 Multi-ChannelInterface Module

E5-E1T1

An EPM-based card that providesE1 and T1 connectivity. The E5indicates the card is for existingEAGLE 5 control and extensionshelves. E1T1 is an abbreviation forthe ITU E1 and ANSI T1 interfaces.Thus the nomenclature defines theshelves where the card can be usedand the physical interface that itprovides.

383910-6013-001 Revision A, March 2011


E

EPM-based Ethernet cardE5-ENET

A high capacity single-slot IPsignaling card (EPM card plus GigEthernet PMC cards).

E5-based dual-slot card thatconsists of the E5-MCAP module

E5-MASP card

(occupies slot 1113 and slot 1115)and the E5-TDM module (occupiesslot 1114 and slot 1116) in anEAGLE 5 ISS control shelf. Usedwhen the E5-MDAL card is used.

The module contains theCommunications Processor and

E5-MCAP card

Applications Processor andprovides connections to the IMTbus. Controls the maintenance anddatabase administration activityand performs both application andcommunication processing. Runsthe OAM application and OAMHCGPL. Occupies slot 1113 and slot1115 in an EAGLE 5 ISS controlshelf. Used when the E5-MDALcard is used. Contains two USBports.

The E5 MDAL card processesalarm requests, provides general

E5-MDAL card

purpose relays, and provides fancontrol. Occupies slots 1117 and1118 in an EAGLE 5 ISS ControlShelf. Used with E5-MASP cards.Does NOT contain a drive forremovable cartridges.

The E5-TDM card provides theEAGLE 5 ISS with 16 ports for user

E5-TDM card

terminals, contains fixed diskstorage and distributes CompositeClocks and High Speed Masterclocks throughout the EAGLE 5

384910-6013-001 Revision A, March 2011


E

ISS. Occupies slot 1114 and slot1116 in an EAGLE 5 ISS ControlShelf. Used when the E5-MDALcard is used.

External condition messageECM

Message that is passed on theexternal condition interface.

Enhanced Database CommunicationModule

EDCM

Enhanced Global Title TranslationEGTT

A feature that is designed for thesignaling connection control part(SCCP) of the SS7 protocol. TheEAGLE 5 ISS uses this feature todetermine to which service databaseto send the query message when aMessage Signaling Unit (MSU)enters the system.

Equipment Identity RegisterEIR

A network entity used in GSMnetworks, as defined in the 3GPPSpecifications for mobile networks.The entity stores lists of InternationalMobile Equipment Identity (IMEI)numbers, which correspond tophysical handsets (not subscribers).Use of the EIR can prevent the useof stolen handsets because thenetwork operator can enter the IMEIof these handsets into a 'blacklist'and prevent them from beingregistered on the network, thusmaking them useless.

See EGTT.Enhanced Global Title Translation

F

385910-6013-001 Revision A, March 2011


F

Hard drive on the TDM card andthe E5-TDM card.

fixed disk drive

USB port on the E5-MCAP card;used with credit card flash memory

flush-mounted USB port

drives for upgrades and could beused for disaster recovery.

G

Generic Loading ServicesGLS

An application that is used by theTSM cards for downloading gatewayscreening to LIM cards.

Generic Program LoadGPL

Software that allows the variousfeatures in the system to work. GPLsand applications are not the samesoftware.

General Purpose Service Module IIGPSM-II card

Contains the communicationsprocessor and applications processorand provides connections to theInterprocessor Message Transport(IMT) bus. The GPSM-II card can runon the OAM, IPS, or MCPapplications.

This card runs various GPLs andapplications in the EAGLE 5 ISS. Asa control card, it runs the OAMapplication and EOAM GPL. Usedwhen the legacy TDM card andMDAL card are used.

Global System for MobileCommunications

GSM

Global Title Routing IndicatorGT

386910-6013-001 Revision A, March 2011


G

Global Title TranslationGTT

A feature of the signaling connectioncontrol part (SCCP) of the SS7protocol that the EAGLE 5 ISS usesto determine which service databaseto send the query message when anMSU enters the EAGLE 5 ISS andmore information is needed to routethe MSU. These service databasesalso verify calling card numbers andcredit card numbers. The servicedatabases are identified in the SS7network by a point code and asubsystem number.

Gateway ScreeningGWS

Used at gateway STPs to limit accessinto the network to authorized users.A gateway STP performsinter-network routing and gatewayscreening functions. GWS controlsaccess to nonhome SS7 networks.Only an MSU that matchespredefined criteria in the EAGLE 5ISS’s database is allowed to enter theEAGLE 5 ISS.

Gateway Screening ActionGWSA

Gateway Screening Application

Gateway Screening MessageDiscard

GWSD

Gateway Screening MessagesGWSM

Gateway Screening Mode

I

Input Data Not SupportedIDNS

INAP-based Number PortabilityINP

387910-6013-001 Revision A, March 2011


I

Tekelec’s INP can be deployed asa stand-alone or an integratedsignal transfer point/numberportability solution. With Tekelec’sstand-alone NP server, no networkreconfiguration is required toimplement number portability. TheNP server delivers a much greatersignaling capability than theconventional SCP-based approach.

Intelligent Network (IN) Portability

Internet ProtocolIP

IP specifies the format of packets,also called datagrams, and theaddressing scheme. The networklayer for the TCP/IP protocol suitewidely used on Ethernet networks,defined in STD 5, RFC 791. IP is aconnectionless, best-effort packetswitching protocol. It providespacket routing, fragmentation andre-assembly through the data linklayer.

Point-to-multipoint MTP-Usersignaling (e.g. ISUP, TCAP) over IP

IPGWx

capability. Typically used for A linkconnectivity which require routingkeys. Far End not required tosupport MTP3. The IPGWx GPLs(IPGWI, SS7IPGW) run on theSSEDCM/E5-ENET cards.

The application used by theSSEDCM/E5-ENET card for IP

IPLIM

point-to-point connectivity for ANSIpoint codes.

Point-to-point MTP3 and MTP3-Usersignaling over IP capability.

IPLIMx

Typically used for B-C-D links butcan be used for A links but does nothave routing key functionality. Far

388910-6013-001 Revision A, March 2011


I

End required to support MTP3. TheIPLIMx GPLs (IPLIMI, IPLIM) runon the SSEDCM/E5-ENET cards.

Intermediate Signaling NetworkIdentification

ISNI

Integrated Signaling SystemISS

ISDN User PartISUP

International TelecommunicationsUnion

ITU

L

On the E5-MCAP card, a USB portwith a lockable latch. Used with

latched USB port

removable media (flash memory”thumb” drives) to install and backup customer data.

The MTP level 2 timers that controlthe operation of signaling links.

Level 2 Timers

The MTP level 3 timers that controlthe operation of link sets.

Level 3 Timers

Link Interface ModuleLIM

Provides access to remote SS7, IPand other network elements, such asa Signaling Control Point (SCP)through a variety of signalinginterfaces (DS0, MPL, E1/T1 MIM,LIM-ATM, E1-ATM, IPLIMx,IPGWx). The LIMs consist of a mainassembly and possibly, an interfaceappliqué board. These appliquésprovide level one and some leveltwo functionality on SS7 signalinglinks.

389910-6013-001 Revision A, March 2011


L

A link interface module (LIM) withthe T1 Appliqué.

LIM-T1

Signaling LinkLink

Signaling Link

Carries signaling within a Link Setusing a specific Association. A Linkcan belong to only one Link Set andone Association. There is generallyone Link per Association in a LinkSet.

Local Number PortabilityLNP

A type of routing used by global titletranslation to route MSUs This type

Load Sharing

of routing is used when a secondpoint code and subsystem is definedfor the primary point code andsubsystem. Traffic is shared equallybetween the replicated point codesand subsystems.

M

SS7 MTP2-User Peer-to-PeerAdaptation Layer

M2PA

SS7 MTP3-User Adaptation LayerM3UA

M3UA enables an MTP3 User Partto be connected to a remote MTP3via a reliable IP transport.

Mobile Application PartMAP

Maintenance and AdministrationSubsystem

MAS

A set of cards located in the ControlShelf, used to provide a centralmanagement point for the EAGLE 5ISS. The MAS provides user

390910-6013-001 Revision A, March 2011


M

interface, maintenancecommunication, peripheral services,alarm processing, system diskinterface, and measurements usingthe following three subassemblies:GPSM-II, TDM, and MDAL.

Maintenance and AdministrationSubsystem Processor

MASP

The Maintenance andAdministration Subsystem Processor(MASP) function is a logical pairingof the GPSM-II card and the TDMcard. The GPSM-II card is connectedto the TDM card by means of anExtended Bus Interface (EBI) localbus.

The MDAL card contains theremovable cartridge drive and alarmlogic. There is only one MDAL cardin the Maintenance andAdministration Subsystem (MAS)and it is shared between the twoMASPs.

The point codes and subsystemnumbers of the service databases

Mated Application

that messages are routed to forglobal title translation.

MegahertzMHz

A parameter of the chg-sltcommand and a field in the

MODE

rtrv-slt command outputshowing the mode used whensending signaling link test messages,regular or special.

special - All SLTMs generated by thelinks in the link set associated withthis SLTM record are designated“special” maintenance messages.

391910-6013-001 Revision A, March 2011


M

regular - All SLTMs generated bythe links in the link set associatedwith this SLTM record aredesignated “regular” maintenancemessages.

Multi-port LIMMPL

Message Reference NumberMRN

An unsolicited numbered message(alarm or information) that isdisplayed in response to an alarmcondition detected by the system orin response to an event that hasoccurred in the system.

Mated Relay Node

A mated relay node (MRN) group isprovisioned in the database toidentify the nodes that the traffic isload shared with, and the type ofrouting, either dominant, loadsharing, or combineddominant/load sharing.

Message Signal UnitMSU

The SS7 message that is sent betweensignaling points in the SS7 networkwith the necessary information toget the message to its destinationand allow the signaling points in thenetwork to set up either a voice ordata connection between themselves.The message contains the followinginformation:

• The forward and backwardsequence numbers assigned tothe message which indicate theposition of the message in thetraffic stream in relation to theother messages.

• The length indicator whichindicates the number of bytes themessage contains.

392910-6013-001 Revision A, March 2011


M

• The type of message and thepriority of the message in thesignaling information octet of themessage.

• The routing information for themessage, shown in the routinglabel of the message, with theidentification of the node thatsent message (originating pointcode), the identification of thenode receiving the message(destination point code), and thesignaling link selector which theEAGLE 5 ISS uses to pick whichlink set and signaling link to useto route the message.

Message Transfer PartMTP

The levels 1, 2, and 3 of the SS7protocol that control all the functionsnecessary to route an SS7 MSUthrough the network

N

Network ClusterNC

Network Code

Not Compliant

Nested Cluster Allowed IndicatorNCAI

Network IndicatorNI

Network OAM&PNO

A server that manages a collectionof SOs and their corresponding MPs.NO servers are deployed inactive/standby pairs.

Next Screening ReferenceNSR

393910-6013-001 Revision A, March 2011


O

Originating Point CodeOPC

P

The rate that the EAGLE 5 ISS sendsthe TFR and TFA messages in an

Pacing Rate

effort to prevent congestion due tocontrolled rerouting. Controlledrerouting is performed when thestatus of the route is changed toallowed (when the route wasrestricted) or restricted (when theroute was prohibited). A burst ofrerouted traffic can occur on thatroute, thus congesting the route. Tohelp keep this from happening, theEAGLE 5 ISS can control the rate thatit broadcasts TFR and TFA messagesto adjacent signaling points. This canregulate the amount of traffic theadjacent signaling points can sendto the EAGLE 5 ISS when the routebecomes allowed or restricted.

Point CodePC

The identifier of a signaling point orservice control point in a network.The format of the point code can beone of the following types:

• ANSI point codes in the formatnetwork indicator-networkcluster-network cluster member(ni-nc-ncm).

• Non-ANSI domestic point codesin the format networkindicator-networkcluster-network cluster member(ni-nc-ncm).

• Cluster point codes in the formatnetwork indicator-networkcluster-* or network indicator-*-*.

• ITU international point codes inthe format zone-area-id.

• ITU national point codes in theformat of a 5-digit number

394910-6013-001 Revision A, March 2011


P

(nnnnn), or 2, 3, or 4 numbers(members) separated by dashes(m1-m2-m3-m4) as defined bythe Flexible Point Code systemoption. A group code is required(m1-m2-m3-m4-gc) when theITUDUPPC feature is turned on.

• 24-bit ITU national point codesin the format main signalingarea-subsignaling area-servicepoint (msa-ssa-sp).

Point Code ANSIPCA

A method of error correction usedfor the SS7 protocol. PCR is an error

PCR

correction method that keeps a copyof each message signal unittransmitted on a signaling link in aretransmission buffer. If thereceivingend of the signaling link receives theMSU with no errors, positiveacknowledgment message is sent tothe transmitting end of the signalinglink. The MSU is then discardedfrom the retransmission buffer. If thetransmitting end of the signaling linkdoes not receive positiveacknowledgment from the receivingend of the signaling link, the MSUis retransmitted until positiveacknowledgment is received. ThePCR error correction method isassigned to SS7 signaling links usingthe ent-slk command.

Personal Communications Service(North American GSM)

PCS

R

MO cartridge used in the drive onthe legacy MDAL card.

removable cartridge

395910-6013-001 Revision A, March 2011


R

Media drive for removable MOcartridges on the legacy MDALcard.

removable cartridge drive

Flash memory or “thumb” drivesused in the latched USB port on an

removable media

E5-MCAP card for installation andbackup of customer data.

The network management state of aroute, link set, or signaling link that

Restricted

is not operating properly and cannotcarry all of its traffic. This conditiononly allows the highest prioritymessages to sent to the databaseentity first, and if space allows,followed by the other traffic. Trafficthat cannot be sent on the restricteddatabase entity must be rerouted orthe traffic is discarded.

Routing IndicatorRI

A signaling path from an LSP to anRSP using a specified Link Set

Route

Route Set TestRST

Routeset Prohibited Test (Msg)

S

Secondary Adjacent Point CodeSAPC

Signaling Connection Control PartSCCP

SCCP ManagementSCMG

SCMG manages the status ofsubsystems and SCCP-capablesignaling points (SPs). It maintains

396910-6013-001 Revision A, March 2011


S

the status of remote SCCP SPs andthat of local subsystems.

A gateway screening tablecontaining a list of rules, or

Screen Set

screening references. The screeningreferences indicate the screeningaction that is to be performed on amessage in a specific linkset.

Screen Set NameSCRN

Signaling Engineering andAdministration Center

SEAC

Signaling Engineering andAdministration System

SEAS

An interface defined by Bellcore andused by the Regional Bell OperatingCompanies (RBOCs), as well as otherBellcore Client Companies (BCCs),to remotely administer and monitorthe signaling points in their networkfrom a central location.

The transmission path connectingthe EAGLE 5 ISS to other signaling

Signaling Link

points in the network and providingaccess to ANSI SS7 and ITU SS7network elements. The signaling linkis connected to the EAGLE 5 ISS atthe link interface module (LIM).

Service Information Octet.SIO

The network indicator code (NIC),priority (PRI), and service indicator(SI) in the SIO field in the messagesignaling unit (MSU). Thisinformation identifies the type ofMSU (ISUP, TCAP, and so forth) thatis allowed in the network where theEAGLE 5 ISS is located.

397910-6013-001 Revision A, March 2011


S

Signaling Link SelectorSLS

SLS Conversion IndicatorSLSCI

The EAGLE ITUInternational/National Spare Point

Spare Point Code

Code feature allows a networkoperator to use the same Point Codesacross two networks (either ITU-I orITU-N). The feature also enablesNational and National Spare trafficto be routed over the same linkset.The EAGLE uses the MSU NetworkIndicator (NI) to differentiate thesame point code of one networkfrom the other. In accordance withthe SS7 standard, unique NetworkIndicator values are defined forPoint Code types ITU-I, ITU-N,ITU-I Spare, and ITU-N Spare.

Signaling System #7SS7

SS7 ANSISS7ANSI

An application used by the LIMcards and the E1/T1 MIM card forthe MTP functionality.

Subsystem NumberSSN

The subsystem number of a givenpoint code. The subsystem numberidentifies the SCP application thatshould receive the message, or thesubsystem number of the destinationpoint code to be assigned to the LNPsubsystem of the EAGLE 5 ISS.

A value of the routing indicatorportion of the global title translationdata commands indicating that nofurther global title translation isrequired for the specified entry.

398910-6013-001 Revision A, March 2011


S

Signal Transfer PointSTP

The STP is a special high-speedswitch for signaling messages in SS7networks. The STP routes core INAPcommunication between the ServiceSwitching Point (SSP) and theService Control Point (SCP) over thenetwork.

T

Transmission Level 1T1

A T1 interface terminates ordistributes T1 facility signals for thepurpose of processing the SS7signaling links carried by the E1carrier.

A leased-line connection capable ofcarrying data at 1,544,000bits-per-second.

Transfer Cluster AllowedTCA

Transmission ControlProtocol/Internet Protocol

TCP/IP

Terminal Disk ModuleTDM

Time Division Multiplexing

TransFer Allowed (Msg)TFA

Transfer RestrictedTFR

See TT.Translation Type

Test StrategyTS

Traffic Server

Technical Specification

399910-6013-001 Revision A, March 2011


T

Translation Type.TT

Resides in the Called Party Address(CdPA) field of the MSU anddetermines which service databaseis to receive query messages. Thetranslation type indicates whichGlobal Title Translation tabledetermines the routing to aparticular service database.

Telephone User PartTUP

U

User Application LayerUAL

Upper Layer ProtocolULP

Receptacle for flash memory driveson personal computers. On the

USB port

E5-MDAL card, a flush-mountedUSB port used with credit cardflash memory drives for upgrade.On the E5-MCAP card, a latchedUSB port for use with flashmemory ”thumb” drives forinstallation and backup ofcustomer data.

V

Virtual Channel IdentifierVCI

Virtual Path IdentifierVPI

X

Translate IndicatorXLAT

Extended User DataXUDT

400910-6013-001 Revision A, March 2011


database administration manual - seas€¦ · 910-6013-001 revision a, march 2011 ii. changing a...

Documents