EAGLE/SEAS Compliance Matrix

A EAGLE/SEAS Compliance Matrix

Appendix A, EAGLE/SEAS Compliance Matrix

A.1 Introduction

This appendix lists the SEAS requirements, conditional requirements, and objectives that the EAGLE 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 conditional requirement number as defined in the Telcordia document, the EAGLE’s level of compliance with the requirement, objective, or conditional requirement, and any comments that may apply to these items.

A requirement is a feature or function of an STP that Telcordia has determined must be a part of the STP 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 necessary in certain applications, depending on how the STP is deployed. A conditional requirement may depend on other requirements, objectives, or conditional requirements. A conditional requirement is identified in 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 or function for the STP to have, but not required to have. An objective is identified in this appendix with the 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 be found. The table of contents entries for this appendix are based on the table captions.

A.2 SEAS-STP Interface Specification, GR-310-CORE, Issue 1, November 1994

Table A-1 Section 4. Message Headers and UPL/Lower-Layer Interactions

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(R) 4-1	Fully Compliant
(R) 4-2	Fully Compliant
(R) 4-3	Fully Compliant
(O) 4-4	Not Applicable	This objective does not apply to the EAGLE because confirmation options “2” and ”3” are not supported by the current UAL implementations.
(R) 4-5	Fully Compliant
(R) 4-6	Fully Compliant
(R) 4-7	Fully Compliant
(O) 4-8	Not Applicable	This objective does not apply to the EAGLE because confirmation options “2” and ”3” are not supported by the current UAL implementations.
(O) 4-9	Not Applicable	This objective does not apply to the EAGLE because confirmation options “2” and ”3” are not supported by the current UAL implementations.
(R) 4-10	Fully Compliant
(R) 4-11	Fully Compliant
(R) 4-12	Fully Compliant
(R) 4-13	Fully Compliant
(R) 4-14	Fully Compliant
(R) 4-15	Fully Compliant
(R) 4-16	Fully Compliant
(R) 4-17	Fully Compliant

Table A-2 Section 5. UPL Interactions and Message Syntax Requirements

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(R) 5-1	Fully Compliant
(O) 5-2	Not Compliant	This function is not currently implemented in the EAGLE.
(CR) 5-3	Not Applicable	This does not apply to the EAGLE because the EAGLE does not comply with objective 5-2.
(CR) 5-4	Fully Compliant	The EAGLE is able to handle the burden of duplicate commands.
(R) 5-5	Not Applicable	This requirement does not apply to the EAGLE because the version management mechanism is a SEAS post-7.0 feature.
(R) 5-6	Not Applicable	This requirement does not apply to the EAGLE because the version management mechanism is a SEAS post-7.0 feature.
(R) 5-7	Fully Compliant
(R) 5-8	Fully Compliant
(R) 5-9	Fully Compliant
(R) 5-10	Partially Compliant	The EAGLE only reports the first error on input detected.
(R) 5-11	Partially Compliant	The EAGLE only reports the first error on execution detected.
(R) 5-12	Fully Compliant
(R) 5-13	Fully Compliant
(R) 5-14	Fully Compliant
(R) 5-15	Fully Compliant

Table A-3 Section 6. Data Collection Messages

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(R) 6-1	Partially Compliant	The EAGLE does not currently support the service measurement (P_SERV), network management on-demand measurement (D_NM), hourly maintenance (on-demand) measurement (D_MTCH), and maintenance status indicator (on demand) (D_MTCS) schedules. Also, the EAGLE does not support MTP special study data collection, which is a SEAS deferred feature. Also, the EAGLE does not currently support ranges for, or any other compound form of, the period parameter.
(R) 6-2	Partially Compliant	The EAGLE does not currently support the service measurement (P_SERV), network management on-demand 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 per processor (PROC), and the per bus (BUS) measured entity types. Also, the EAGLE does not support MTP special study data collection and translation type mapping, which are SEAS deferred features.
(R) 6-3	Fully Compliant
(R) 6-4	Partially Compliant	The EAGLE cannot guarantee that the report will be transmitted no later than 15 seconds after the end of each five-minute interval. The EAGLE does not currently support the per link (LINK) exception data and the per processor (PROC) exception data measured entity types.
(R) 6-5	Partially Compliant	The EAGLE does not currently support the service measurement (P_SERV), network management on-demand measurement (D_NM), hourly maintenance (on-demand) measurement (D_MTCH), and maintenance status indicator (on-demand) (D_MTCS) schedules. Also, the EAGLE does not support MTP special study data collection, which is a SEAS deferred feature.
(R) 6-6	Partially Compliant	The EAGLE 5 ISS does not support all of the required measurement schedules, entity types, and registers (seeTable A-11 and Table A-12).

Table A-4 Section 7. Recent Change and Verify (RC&V) Messages

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(R) 7-1	Partially Compliant	The EAGLE does not currently support entity sets L and M. Entity set J is supported only by using the Flow-Through interface. Entity sets H, N, O, P, Q, R, and S are SEAS post-7.0 entity sets.
(CR) 7-2	Partially Compliant	The EAGLE does not currently support functions 1 through 3. It does support functions 24 through 26, but only by using the Flow-Through interface. Functions 15 through 17 and 30 through 46 are SEAS post-7.0 functions.
(R) 7-3	Partially Compliant	The EAGLE does not currently support function 1. It does support function 10, but only by using the Flow-Through interface. Functions 7 and 13 through 18 are SEAS post-7.0 functions.
(R) 7-4	Fully Compliant
(R) 7-5	Partially Compliant	The EAGLE supports only immediate activation.
(R) 7-6	Fully Compliant
(R) 7-7	Fully Compliant
(R) 7-8	Fully Compliant
(R) 7-9	Fully Compliant
(O) 7-10	Fully Compliant
(R) 7-11	Not Compliant	The EAGLE does expect all destination identifiers to be unique.
(R) 7-12	Fully Compliant
(R) 7-13	Fully Compliant
(R) 7-14	Fully Compliant	The EAGLE already supports the destination entity set, therefore no upgrade is necessary.
(R) 7-15	Fully Compliant	The EAGLE already supports the destination entity set, therefore no upgrade is necessary.
(R) 7-16	Fully Compliant	The EAGLE already supports the destination entity set, therefore no upgrade is necessary.
(R) 7-17	Fully Compliant
(R) 7-18	Fully Compliant
(R) 7-19	Fully Compliant
(R) 7-20	Fully Compliant
(R) 7-21	Fully Compliant
(O) 7-22	Not Applicable	The EAGLE does not support supplier-specific parameters for these entities with the standard SEAS interface. The EAGLE’s supplier-specific parameters can be modified by using the SEAS Flow-Through interface.
(CR) 7-23	Not Applicable	The EAGLE does not support supplier-specific parameters with the standard SEAS interface.
(R) 7-24	Fully Compliant
(O) 7-25	Not Applicable	The EAGLE does not support supplier-specific parameters for these entities with the standard SEAS interface. The EAGLE’s supplier-specific parameters can be modified by using the SEAS Flow-Through interface.
(CR) 7-26	Not Applicable	The EAGLE does not support supplier-specific parameters with the standard SEAS interface.
(CR) 7-27	Not Applicable	The EAGLE does not support supplier-specific parameters with the standard SEAS interface.
(R) 7-28	Fully Compliant	All supplier-specific parameter strings for both input and output are null.
(R) 7-29	Not Applicable	This requirement does not apply to the EAGLE because the TFA/TCA broadcast minimum link quantity attribute for linksets is a SEAS post-7.0 feature.
(R) 7-30	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because this is a SEAS post-7.0 enhancement.
(R) 7-31	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because this is a SEAS post-7.0 enhancement.
(R) 7-32	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because this is a SEAS post-7.0 enhancement.
(R) 7-33	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because this is a SEAS post-7.0 enhancement.
(R) 7-34	Fully Compliant
(R) 7-35	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the SCCP application entity set is a SEAS post-7.0 feature.
(R) 7-36	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the multi-step GTT process is a SEAS post-7.0 feature.
(R) 7-37	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the STP Options entity set a SEAS post-7.0 feature.
(R) 7-38	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because vacant global title addresses is a SEAS post-7.0 feature.
(CR) 7-39	Not Compliant	The EAGLE 5 ISS does not support storage consolidation for entries of an entity set with like attributes.
(CR) 7-40	Not Compliant	The EAGLE 5 ISS does not support storage consolidation for entries of an entity set with like attributes.
(CR) 7-41	Not Compliant	The EAGLE 5 ISS does not support storage consolidation for entries of an entity set with like attributes.
(CR) 7-42	Partially Compliant	The EAGLE 5 ISS does not support the functions for delayed activation.
(CR) 7-43	Not Compliant	The EAGLE 5 ISS does not support the `ACTV-OR` command.
(CR) 7-44	Not Compliant	The EAGLE 5 ISS does not support the `DLT-OR` command.
(CR) 7-45	Not Compliant	The EAGLE 5 ISS does not support the `CANC-ORACTV` command.
(CR) 7-46	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation.
(CR) 7-47	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation.
(CR) 7-48	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation.
(CR) 7-49	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. Also, the EAGLE 5 ISS does not support all wildcarding as specified.
(CR) 7-50	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. Also, the EAGLE 5 ISS cannot change the value of the destination point code attribute with this command.
(CR) 7-51	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. Also, the EAGLE 5 ISS does not support needed linkset recent change and verify enhancements, because it is a SEAS post-7.0 feature.
(CR) 7-52	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation.
(CR) 7-53	Partially Compliant	The EAGLE 5 ISS does not support the changing of the new far-end CLLI parameter unless the new far-end point code parameter is being changed as well. In this case the new far-end CLLI must match the destination identifier of the linkset’s new far-end point code. The EAGLE 5 ISS does not support the parameters for delayed activation. Also, the EAGLE 5 ISS does not support needed linkset recent change and verify enhancements, because this is a SEAS post-7.0 feature.
(CR) 7-54	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. Also, the EAGLE 5 ISS does not support 1.5 Mbps link speed, because this is a SEAS post-7.0 feature.
(CR) 7-55	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation.
(CR) 7-56	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. The EAGLE 5 ISS only supports the new link service state parameter. Also, the EAGLE 5 ISS does not support 1.5 Mbps link speed, because this is a SEAS post-7.0 feature.
(CR) 7-57	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. The EAGLE 5 ISS does not support the relative cost parameter, although because the `RC` parameter is required, the EAGLE 5 ISS accepts the parameter. Also, the EAGLE 5 ISS does not support residual modifications to support SS7 cluster routing and management, and vacant global title addresses, because these are SEAS post-7.0 features.
(CR) 7-58	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. EAGLE 5 ISS does not support the destination point code and subsystem number parameters, although because they are required, it accepts the parameters. Also, the EAGLE 5 ISS does not support vacant global title addresses, because this is SEAS post-7.0 feature.
(CR) 7-59	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation, nor does the EAGLE 5 ISS support the new relative cost new destination point code, and new subsystem number parameters. Also, the EAGLE 5 ISS does not support residual modifications to support SS7 cluster routing and management, and vacant global title addresses, because these are SEAS post-7.0 features.
(CR) 7-60	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. Also, the EAGLE 5 ISS does not support residual modifications to support SS7 cluster routing and management, because this is a SEAS post-7.0 feature.
(CR) 7-61	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation.
(CR) 7-62	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. Also, the EAGLE 5 ISS does not support residual modifications to support SS7 cluster routing and management, because this is a SEAS post-7.0 feature.
(CR) 7-63	Partially Compliant	The EAGLE 5 ISS does not support the `ASGN-SPCSP` command. The EAGLE 5 ISS supports only the shared concerned signaling point lists for its subsystem prohibited concerned signaling points entity set. However, this feature is a SEAS post-7.0 feature, therefore the EAGLE 5 ISS cannot support this command until this feature is implemented in SEAS. The Flow-Through commands can still be used to manipulate this entity set.
(CR) 7-64	Not Compliant	The EAGLE 5 ISS does not support the `DLT-SPCSP` command. The EAGLE 5 ISS supports only shared concerned signaling point lists for its subsystem prohibited concerned signaling points entity set. However, this feature is a SEAS post-7.0 feature, therefore the EAGLE 5 ISS cannot support this command until this feature is implemented in SEAS. The Flow-Through commands can still be used to manipulate this entity set.
(CR) 7-65	Not Compliant	The EAGLE 5 ISS does not support the `CHG-SPCSP` command.
(CR) 7-66	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. Also, the EAGLE 5 ISS does not support MTP circular route (loop) detection, because this is a SEAS post-7.0 feature.
(CR) 7-67	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation.
(CR) 7-68	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. Also, the EAGLE 5 ISS does not support MTP circular route (loop) detection, because this is a SEAS post-7.0 feature.
(CR) 7-69	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because MTP circular route (loop) detection is a SEAS post-7.0 feature.
(CR) 7-70	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify support for SCCP application data is a SEAS post-7.0 feature.
(CR) 7-71	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify support for SCCP application data is a SEAS post-7.0 feature.
(CR) 7-72	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify support for SCCP application data is a SEAS post-7.0 feature.
(CR) 7-73	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify for the STP OPTIONS entity set is a SEAS post-7.0 feature.
(CR) 7-74	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because multi-step global title translation (GTT) is a SEAS post-7.0 feature.
(CR) 7-75	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because multi-step global title translation (GTT) is a SEAS post-7.0 feature.
(CR) 7-76	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because multi-step global title translation (GTT) is a SEAS post-7.0 feature.
(CR) 7-77	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because multi-step global title translation (GTT) is a SEAS post-7.0 feature.
(CR) 7-78	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because multi-step global title translation (GTT) is a SEAS post-7.0 feature.
(CR) 7-79	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because multi-step global title translation (GTT) is a SEAS post-7.0 feature.
(CR) 7-80	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because multi-step global title translation (GTT) is a SEAS post-7.0 feature.
(CR) 7-81	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because multi-step global title translation (GTT) is a SEAS post-7.0 feature.
(CR) 7-82	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because multi-step global title translation (GTT) is a SEAS post-7.0 feature.
(CR) 7-83	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify for SCCP ISNI message routing is a SEAS post-7.0 feature.
(CR) 7-84	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify for SCCP ISNI message routing is a SEAS post-7.0 feature.
(CR) 7-85	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify for SCCP ISNI message routing is a SEAS post-7.0 feature.
(CR) 7-86	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify for SCCP ISNI message routing is a SEAS post-7.0 feature.
(CR) 7-87	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify for SCCP ISNI message routing is a SEAS post-7.0 feature.
(CR) 7-88	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify for SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) 7-89	Not Compliant	The EAGLE 5 ISS does not support the `ACTV-OR` command.
(R) 7-90	Not Compliant	The EAGLE 5 ISS does not support the `ACTV-OR` command.
(R) 7-91	Not Compliant	The EAGLE 5 ISS does not support the `DLT-OR` command.
(R) 7-92	Not Compliant	The EAGLE 5 ISS does not support the `CANC-ORACTV` command.
(R) 7-93	Fully Compliant
(R) 7-94	Fully Compliant
(R) 7-95	Fully Compliant
(R) 7-96	Fully Compliant
(CR) 7-97	Fully Compliant
(CR) 7-98	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because the EAGLE 5 ISS supports the changing of the CLLI and DPC values using the `ASGN-SID` command.
(R) 7-99	Fully Compliant
(R) 7-100	Fully Compliant
(R) 7-101	Fully Compliant
(R) 7-102	Not Compliant	The EAGLE 5 ISS does not support supplier-specific parameters.
(R) 7-103	Fully Compliant
(R) 7-104	Fully Compliant	The EAGLE 5 ISS does not support multi-step global title translation (GTT) nor recent change and verify for SCCP ISNI message routing, because they are SEAS post-7.0 features.
(R) 7-105	Fully Compliant
(R) 7-106	Fully Compliant
(R) 7-107	Partially Compliant	The EAGLE 5 ISS enforces rule a, e, and g, but not rules b, c, d, and f because those parameters are not supported by the EAGLE 5 ISS’s `chg-rte` command. Also, the EAGLE 5 ISS does not support multi-step global title translation (GTT) nor recent change and verify for SCCP ISNI message routing, because they are SEAS post-7.0 features.
(R) 7-108	Fully Compliant
(R) 7-109	Not Compliant	The EAGLE 5 ISS does not support supplier-specific parameters.
(R) 7-110	Fully Compliant
(R) 7-111	Fully Compliant
(R) 7-112	Fully Compliant
(R) 7-113	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the EAGLE 5 ISS does not support parameters for the needed linkset recent change and verify enhancements. This is a SEAS post-7.0 feature.
(R) 7-114	Not Compliant	The EAGLE 5 ISS does not support supplier-specific parameters.
(R) 7-115	Fully Compliant
(R) 7-116	Partially Compliant	The EAGLE 5 ISS does not support the changing of the new far-end CLLI parameter unless the new far-end point code parameter is being changed as well. In this case the new far-end CLLI must match the destination identifier of the linkset’s new far-end point code.
(R) 7-117	Partially Compliant	The EAGLE 5 ISS enforces rules a and b. The EAGLE 5 ISS enforces only part of rule c because the EAGLE 5 ISS does not require links in a linkset to be disabled in order to change the linkset type attribute. The EAGLE 5 ISS does not enforce rule d because the EAGLE 5 ISS does not support supplier-specific parameters. The EAGLE 5 ISS does not enforce rules e and f because the EAGLE 5 ISS does not support needed linkset recent change and verify enhancements, because this is a SEAS post-7.0 feature.
(CR) 7-118	Fully Compliant	The EAGLE 5 ISS does not support needed linkset recent change and verify enhancements, because this is a SEAS post-7.0 feature. The EAGLE 5 ISS does permit changes to all supported parameters while the linkset’s signaling links are active, but only the far-end CLLI is supported for this conditional requirement.
(R) 7-119	Not Compliant	The EAGLE 5 ISS does not list the signaling links in the linkset that are enabled when the `CHG-LS` command is rejected, or when attempting to change the point code of the linkset because the EAGLE 5 ISS does not require the signaling links in the linkset to be disabled to make these changes.
(R) 7-120	Not Compliant	The EAGLE 5 ISS does not support supplier-specific parameters.
(R) 7-121	Fully Compliant
(R) 7-122	Fully Compliant
(R) 7-123	Fully Compliant
(R) 7-124	Fully Compliant
(R) 7-125	Fully Compliant
(R) 7-126	Fully Compliant
(R) 7-127	Not Compliant	The EAGLE 5 ISS does not support supplier-specific parameters.
(R) 7-128	Fully Compliant
(R) 7-129	Fully Compliant
(R) 7-130	Fully Compliant
(R) 7-131	Fully Compliant
(R) 7-132	Fully Compliant
(R) 7-133	Fully Compliant	Rule c is does not apply to the EAGLE 5 ISS because the EAGLE 5 ISS does not support the SCCP application entity set, because this is a SEAS post-7.0 feature.
(R) 7-134	Partially Compliant	The EAGLE 5 ISS does not support the destination point code and subsystem number parameters, but because these parameters are required by SEAS, the EAGLE 5 ISS accepts the parameters.
(R) 7-135	Partially Compliant	The EAGLE 5 ISS does not enforce rule 1 because the EAGLE 5 ISS does not support the destination point code and subsystem number parameters, but because these parameters are required by SEAS, the EAGLE 5 ISS accepts these parameters. The EAGLE 5 ISS enforces rules 2, 3, and 4. Rule 5 does not apply to the EAGLE 5 ISS because the EAGLE 5 ISS does not support the SCCP application entity set. This is a SEAS post-7.0 feature.
(R) 7-136	Fully Compliant	Rule 2 does not apply to the EAGLE 5 ISS because the EAGLE 5 ISS does not support the SCCP application entity set. This is a SEAS post-7.0 feature.
(R) 7-137	Fully Compliant
(R) 7-138	Fully Compliant	Rule 2 does not apply to the EAGLE 5 ISS because the EAGLE 5 ISS does not support the SCCP application entity set. This is a SEAS post-7.0 feature.
(CR) 7-139	Not Compliant	The EAGLE 5 ISS does not support the `ASGN-SPCSP` command.
(R) 7-140	Not Compliant	The EAGLE 5 ISS does not support the `ASGN-SPCSP` command.
(CR) 7-141	Not Compliant	The EAGLE 5 ISS does not support the `DLT-SPCSP` command.
(R) 7-142	Not Compliant	The EAGLE 5 ISS does not support the `DLT-SPCSP` command.
(R) 7-143	Not Compliant	The EAGLE 5 ISS does not support the `DLT-SPCSP` command.
(CR) 7-144	Not Compliant	The EAGLE 5 ISS does not support the `CHG-SPCSP` command.
(R) 7-145	Not Compliant	The EAGLE 5 ISS does not support the `CHG-SPCSP` command.
(R) 7-146	Not Compliant	The EAGLE 5 ISS does not support the `CHG-SPCSP` command.
(R) 7-147	Partially Compliant	The EAGLE 5 ISS does not verify this rule for the `bei` parameter.
(R) 7-148	Fully Compliant
(R) 7-149	Partially Compliant	The EAGLE 5 ISS does not support the far-end CLLI attribute for its linkset entities.
(R) 7-150	Not Compliant	The EAGLE 5 ISS does not support supplier-specific parameters.
(R) 7-151	Fully Compliant
(R) 7-152	Fully Compliant
(R) 7-153	Partially Compliant	The EAGLE 5 ISS does not verify this rule for the `nbei` parameter.
(R) 7-154	Fully Compliant
(R) 7-155	Partially Compliant	The EAGLE 5 ISS does not support the far-end CLLI attribute for its linkset entities.
(R) 7-156	Not Compliant	The EAGLE 5 ISS does not support supplier-specific parameters.
(R) 7-157	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `RST-DSTN` command is a SEAS post-7.0 feature.
(R) 7-158	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `RST-DSTN` command is a SEAS post-7.0 feature.
(R) 7-159	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `RST-DSTN` command is a SEAS post-7.0 feature.
(R) 7-160	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `RST-DSTN` command is a SEAS post-7.0 feature.
(R) 7-161	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-SCCPAPL` command is a SEAS post-7.0 feature.
(R) 7-162	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-SCCPAPL` command is a SEAS post-7.0 feature.
(R) 7-163	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `DLT-SCCPAPL` command is a SEAS post-7.0 feature.
(R) 7-164	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `DLT-SCCPAPL` command is a SEAS post-7.0 feature.
(R) 7-165	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `DLT-SCCPAPL` command is a SEAS post-7.0 feature.
(R) 7-166	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-SCCPAPL` command is a SEAS post-7.0 feature.
(R) 7-167	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-SCCPAPL` command is a SEAS post-7.0 feature.
(R) 7-168	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-SCCPAPL` command is a SEAS post-7.0 feature.
(R) 7-169	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `UPD-STPOPTS` command is a SEAS post-7.0 feature.
(R) 7-170	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-MGTT-TTSSN` command is a SEAS post-7.0 feature.
(R) 7-171	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-MGTT-TTSSN` command is a SEAS post-7.0 feature.
(R) 7-172	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `DLT-MGTT-TTSSN` command is a SEAS post-7.0 feature.
(R) 7-173	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-MGTT-TTSSN` command is a SEAS post-7.0 feature.
(R) 7-174	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-175	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-176	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-177	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-178	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `DLT-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-179	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `DLT-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-180	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `DLT-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-181	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `DLT-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-182	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-183	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-184	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-185	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-186	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-MGTT-ORDPC` command is a SEAS post-7.0 feature.
(R) 7-187	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-MGTT-ORDPC` command is a SEAS post-7.0 feature.
(R) 7-188	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `DLT-MGTT-ORDPC` command is a SEAS post-7.0 feature.
(R) 7-189	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-MGTT-ORDPC` command is a SEAS post-7.0 feature.
(R) 7-190	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-MGTT-ORDPC` command is a SEAS post-7.0 feature.
(R) 7-191	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-ISNI-CICICN` command is a SEAS post-7.0 feature.
(R) 7-192	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-ISNI-CICICN` command is a SEAS post-7.0 feature.
(R) 7-193	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `DLT-ISNI-CICICN` command is a SEAS post-7.0 feature.
(R) 7-194	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `DLT-ISNI-CICICN` command is a SEAS post-7.0 feature.
(R) 7-195	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-ISNI-CICICN` command is a SEAS post-7.0 feature.
(R) 7-196	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-ISNI-CICICN` command is a SEAS post-7.0 feature.
(R) 7-197	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `ADD-ISNI-ICNDPC` command is a SEAS post-7.0 feature.
(R) 7-198	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `DLT-ISNI-ICNDPC` command is a SEAS post-7.0 feature.
(R) 7-199	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `CHG-ISNI-ICNDPC` command is a SEAS post-7.0 feature.
(CR) 7-200	Fully Compliant
(CR) 7-201	Not Compliant	This conditional requirement does not apply to the EAGLE 5 ISS because the EAGLE 5 ISS does not support the `VFY-OR` command.
(CR) 7-202	Fully Compliant
(CR) 7-203	Partially Compliant	Conformance testing with Telcordia indicated that the syntax for the `VFY-RTE` command is implemented differently by the SEAS mainframe than that specified in the SEAS-STP Interface Specification, GR-310-CORE, Issue 1, November 1994. However, the EAGLE 5 ISS does support both the implemented syntax and the specified syntax. The EAGLE 5 ISS is fully compliant with the implemented syntax. In the specified syntax, the EAGLE 5 ISS does not support ranges for the destination address parameter, nor does it support wildcards, except for the --*, ni-nc-, and ni-nc-*** combinations. Also, the output syntax appears to have been implemented differently, but currently this issue has yet to be resolved.
(CR) 7-204	Fully Compliant	The EAGLE 5 ISS does not support needed link set recent change and verify enhancements, because this is a SEAS post-7.0 feature.
(CR) 7-205	Partially Compliant	The EAGLE 5 ISS does not support ranges for the member number parameter. Also, the EAGLE 5 ISS does not support 1.5 Mbps link speed, because this is a SEAS post-7.0 feature.
(CR) 7-206	Fully Compliant
(CR) 7-207	Partially Compliant	The EAGLE 5 ISS does not support the relative cost parameter. On input, the EAGLE 5 ISS ignores this parameter. On output, EAGLE 5 ISS displays the value of fifty (50) since this parameter is mandatory in the output syntax. The EAGLE 5 ISS can also display a blank (‘ ’) value for the routing indicator attribute under certain conditions when this value has been configured locally. Also, the EAGLE 5 ISS does not support vacant global title addresses, because this is SEAS post-7.0 feature.
(CR) 7-208	Fully Compliant
(CR) 7-209	Not Compliant	The EAGLE 5 ISS does not support the `VFY-SPCSP` command. The EAGLE 5 ISS supports only shared concerned signaling point lists for its subsystem prohibited concerned signaling points entity set. However, this feature is a SEAS post-7.0 feature, therefore the EAGLE 5 ISS cannot support this command until this feature is implemented in SEAS. The Flow-Through commands can still be used to retrieve this entity set.
(CR) 7-210	Partially Compliant	The EAGLE 5 ISS does not support ranges for the destination address parameter, nor does it support every combination of wildcards for this parameter. Also, the reporting of PRML (prohibited due to MTP loop detection, for example, circular routing) as the status for a route is not supported. Even though the EAGLE 5 ISS MTP (LIM) cards detect circular routing, they report the circular routing condition not on a route basis, but on a destination basis. The MTP card does not change the route’s status to PROHIBITED in every situation where circular routing is detected on the route. Reporting of ULP (unavailable due to MTP loop detected) for a destination’s routeset (DA) is supported. Finally, route status blocks in the output report will contain null (“”) values for the `FECLLI` parameter (that is, CLLI of the linkset’s adjacent point code) if no CLLI has been defined locally for the APC. The SEAS-STP Interface Specification, GR-310-CORE, Issue 1, November 1994, does not explicitly state that reporting a null CLLI is allowed. The SEAS-STP Interface Specification, GR-310-CORE, Issue 1, November 1994, does state that the CLLI reported for the `DI` output value can be null, but it makes no similar statement regarding the `FECLLI` value, thus the implication that the `FECLLI` value can not be null.
(CR) 7-211	Partially Compliant	The EAGLE 5 ISS does not support ranges for the destination address parameter, nor does it support wildcards, except for the --*, ni-nc-, and ni-nc-* combinations. Also, the EAGLE 5 ISS does not support MTP circular route (loop) detection, because this is a SEAS** post-7.0 feature.
(CR) 7-212	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify support for SCCP application data is a SEAS post-7.0 feature.
(CR) 7-213	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify for the STP options entity set is a SEAS post-7.0 feature.
(CR) 7-214	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because multi-step global title translation (GTT) is a SEAS post-7.0 feature.
(CR) 7-215	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because multi-step global title translation (GTT) is a SEAS post-7.0 feature.
(CR) 7-216	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because multi-step global title translation (GTT) is a SEAS post-7.0 feature.
(CR) 7-217	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify for SCCP ISNI message routing is a SEAS post-7.0 feature.
(CR) 7-218	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because recent change and verify for SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) 7-219	Not Compliant	The EAGLE 5 ISS does not support the merge process for data output.
(R) 7-220	Fully Compliant
(R) 7-221	Not Compliant	The EAGLE 5 ISS does not support the merge process for data output.
(R) 7-222	Fully Compliant
(O) 7-223	Not Compliant	The EAGLE 5 ISS does not support the sorting of ordered route data for output.
(CR) 7-224	Not Compliant
(R) 7-225	Fully Compliant
(R) 7-226	Fully Compliant
(R) 7-227	Fully Compliant
(R) 7-228	Fully Compliant
(R) 7-229	Fully Compliant
(R) 7-230	Fully Compliant
(R) 7-231	Fully Compliant
(R) 7-232	Fully Compliant
(CR) 7-233	Not Compliant	The EAGLE 5 ISS does not support the merge process for data output.
(R) 7-234	Fully Compliant
(CR) 7-235	Fully Compliant
(R) 7-236	Fully Compliant
(R) 7-237	Fully Compliant
(R) 7-238	Fully Compliant
(R) 7-239	Fully Compliant
(R) 7-240	Fully Compliant
(CR) 7-241	Not Compliant	The EAGLE 5 ISS does not support the `VFY-SPCSP` command.
(R) 7-242	Not Compliant	The EAGLE 5 ISS does not support the `VFY-SPCSP` command.
(R) 7-243	Not Compliant	The EAGLE 5 ISS does not support the `VFY-SPCSP` command.
(R) 7-244	Not Compliant	The EAGLE 5 ISS does not support the `VFY-SPCSP` command.
(R) 7-245	Fully Compliant
(R) 7-246	Fully Compliant
(R) 7-247	Not Compliant	The EAGLE 5 ISS does not support the reporting of congestion status for a given destination for the `VFY-SRSAPST` command. The EAGLE 5 ISS MTP cards (LIMs) are aware of destination congestion, but they use this information internally and do not report congestion status to the maintenance subsystem. Thus, information is not available to the `VFY-SRSAPST` command.
(R) 7-248	Fully Compliant
(R) 7-249	Fully Compliant
(CR) 7-250	Fully Compliant
(R) 7-251	Fully Compliant
(R) 7-252	Fully Compliant
(R) 7-253	Fully Compliant
(O) 7-254	Partially Compliant	The EAGLE 5 ISS maintains the routeset sorted in increasing relative cost, thus the output report will list the individual routes in increasing relative cost order, as required. However, if two routes have the same relative cost, then the requirement states that the routes be output sorted by linkset name. This may not always occur.
(R) 7-255	Fully Compliant
(R) 7-256	Fully Compliant
(R) 7-257	Fully Compliant
(R) 7-258	Not Compliant	The EAGLE 5 ISS does not support the merge process for data output.
(R) 7-259	Fully Compliant
(R) 7-260	Not Compliant	The EAGLE 5 ISS does not support the merge process for data output.
(R) 7-261	Fully Compliant
(O) 7-262	Not Compliant	The EAGLE 5 ISS does not support the sorting of destination data output.
(CR) 7-263	Not Compliant	The EAGLE 5 ISS does not support the sorting of destination data output.
(CR) 7-264	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because the `VFY-SCCPAPL` command is a SEAS post-7.0 feature.
(CR) 7-265	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because the `VFY-MGTT-TTSSN` command is a SEAS post-7.0 feature.
(R) 7-266	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `VFY-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(O) 7-267	Not Applicable	This objective does not apply to the EAGLE 5 ISS because the `VFY-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(R) 7-268	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the `VFY-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(CR) 7-269	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because the `VFY-MGTT-GTADPC` command is a SEAS post-7.0 feature.
(CR) 7-270	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because the `VFY-MGTT-ORDPC` command is a SEAS post-7.0 feature.
(CR) 7-271	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because the `VFY-ISNI-CICICN` command is a SEAS post-7.0 feature.
(CR) 7-272	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because the `VFY-ISNI-CICICN` command is a SEAS post-7.0 feature.
(CR) 7-273	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because the `VFY-ISNI-ICNDPC` command is a SEAS post-7.0 feature.

Table A-5 Section 8. On-Occurrence Autonomous Messages

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(CR) 8-1	Not Compliant	The EAGLE 5 ISS does not currently support the `REPT-RCINT` message.
(CR) 8-2	Fully Compliant
(CR) 8-3	Fully Compliant
(CR) 8-4	Fully Compliant
(CR) 8-5	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for cluster routing and management is a SEAS post-7.0 feature.
(CR) 8-6	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for cluster routing and management is a SEAS post-7.0 feature.
(CR) 8-7	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for cluster routing and management is a SEAS post-7.0 feature.
(CR) 8-8	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for cluster routing and management is a SEAS post-7.0 feature.
(CR) 8-9	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because MTP circular route (loop) detection is a SEAS post-7.0 feature.
(CR) 8-10	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because MTP circular route (loop) detection is a SEAS post-7.0 feature.
(CR) 8-11	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because MTP circular route (loop) detection is a SEAS post-7.0 feature.
(CR) 8-12	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because XUDT message processing surveillance is a SEAS post-7.0 feature.
(CR) 8-13	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because XUDT message processing surveillance is a SEAS post-7.0 feature.
(CR) 8-14	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for SCCP ISNI message routing is a SEAS post-7.0 feature.
(CR) 8-15	Fully Compliant
(CR) 8-16	Fully Compliant
(CR) 8-17	Fully Compliant
(CR) 8-18	Fully Compliant
(CR) 8-19	Fully Compliant
(CR) 8-20	Fully Compliant
(CR) 8-21	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-22	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-23	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-24	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-25	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-26	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-27	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-28	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-29	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-30	Partially Compliant	The EAGLE 5 ISS reports the threshold parameter as MSUs instead of MSU octets for its threshold calculations.
(CR) 8-31	Partially Compliant	The EAGLE 5 ISS reports the threshold parameter as MSUs instead of MSU octets for its threshold calculations.
(CR) 8-32	Fully Compliant
(CR) 8-33	Fully Compliant
(CR) 8-34	Partially Compliant	The EAGLE 5 ISS does not currently support reporting of the following codes for the `REPT-LKF` message: `XLR`, `MMR`, `SLT`, `RMI`, `LPO`, `MBL`, `MRS`, and `MMA`. Also, the EAGLE 5 ISS does not support surveillance for link oscillation filter - delayed link restoration, because this is a SEAS post-7.0 feature.
(CR) 8-35	Fully Compliant
(CR) 8-36	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance of manually caused link outages is a SEAS post-7.0 feature.
(CR) 8-37	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance of manually caused link outages is a SEAS post-7.0 feature.
(CR) 8-38	Not Compliant	The EAGLE 5 ISS does not currently support the `REPT-ADMPR-CGST` message.
(CR) 8-39	Not Compliant	The EAGLE 5 ISS does not currently support the `REPT-ADMPR-CGST` message.
(R) 8-40	Not Compliant	The EAGLE 5 ISS does not support storage of autonomous messages for retransmission.
(R) 8-41	Fully Compliant
(R) 8-42	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the EAGLE 5 ISS does not support storage of autonomous messages for retransmission.
(R) 8-43	Fully Compliant	The EAGLE 5 ISS supports the limiting of output using the required default values. The EAGLE 5 ISS does not support the administration of these values through the `UPD-STPOPTS` command as the STP options entity set is a SEAS post-7.0 feature.
(R) 8-44	Fully Compliant	The EAGLE 5 ISS supports the limiting of output using the required default values. The EAGLE 5 ISS does not support the administration of these values through the `UPD-STPOPTS` command as the STP options entity set is a SEAS post-7.0 feature.
(R) 8-45	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because XUDT message processing surveillance is a SEAS post-7.0 feature.
(CR) 8-46	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because XUDT message processing surveillance is a SEAS post-7.0 feature.
(R) 8-47	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because XUDT message processing surveillance is a SEAS post-7.0 feature.
(R) 8-48	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because surveillance for SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) 8-49	Not Compliant	The EAGLE 5 ISS does not support storage of autonomous messages for retransmission.
(O) 8-50	Not Compliant	The EAGLE 5 ISS does not support storage of autonomous messages for retransmission.
(O) 8-51	Not Applicable	This objective does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(O) 8-52	Not Applicable	This objective does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(R) 8-53	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(R) 8-54	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(R) 8-55	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(R) 8-56	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-57	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-58	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-59	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(CR) 8-60	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(O) 8-61	Not Applicable	This objective does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(O) 8-62	Not Applicable	This objective does not apply to the EAGLE 5 ISS because surveillance for MTP restart and STP processor overload is a SEAS post-7.0 feature.
(R) 8-63	Not Compliant	The EAGLE 5 ISS does not support storage of autonomous messages for retransmission.
(R) 8-64	Not Compliant	The EAGLE 5 ISS does not support storage of autonomous messages for retransmission.
(O) 8-65	Not Compliant	The EAGLE 5 ISS does not support storage of autonomous messages for retransmission.
(R) 8-66	Fully Compliant
(R) 8-67	Fully Compliant
(R) 8-68	Fully Compliant
(R) 8-69	Fully Compliant
(O) 8-70	Not Compliant	The EAGLE 5 ISS does not guarantee sequencing of messages on output.
(R) 8-71	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because surveillance of manually caused link outages is a SEAS post-7.0 feature.
(O) 8-72	Not Applicable	This objective does not apply to the EAGLE 5 ISS because surveillance of manually caused link outages is a SEAS post-7.0 feature.
(R) 8-73	Fully Compliant
(R) 8-74	Fully Compliant
(R) 8-75	Fully Compliant

Table A-6 Section 9. STP Application Control Commands

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(CR) 9-1	Not Compliant	The EAGLE 5 ISS does not support the `INH-COLL` command.
(CR) 9-2	Not Compliant	The EAGLE 5 ISS does not support the `ALW-COLL` command.
(CR) 9-3	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because MTP special study parameter administration is a SEAS deferred feature.
(CR) 9-4	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because MTP special study parameter administration is a SEAS deferred feature.
(CR) 9-5	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because MTP special study parameter administration is a SEAS deferred feature.
(CR) 9-6	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because MTP special study parameter administration is a SEAS deferred feature.
(CR) 9-7	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because administration of marginal link performance thresholds for maintenance is a SEAS deferred feature.
(CR) 9-8	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because administration of SS7 network management parameters is a SEAS deferred feature.
(CR) 9-9	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because administration of SS7 network management parameters is a SEAS deferred feature.
(CR) 9-10	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because STP data base administration is a SEAS deferred feature.

Table A-7 Section 10. Transparent Mode (Flow-Through) Messages

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(O) 10-1	Fully Compliant
(CR) 10-2	Fully Compliant
(R) 10-3	Fully Compliant

Table A-8 Section 11. Performance and Capacity

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(O) 11-1	Fully Compliant
(CR) 11-2	Fully Compliant
(R) 11-3	Partially Compliant	The completion responses to verify commands that contain large amounts of data could take greater than 60 seconds. The error response on input `TMC=SG99` will take much longer than 60 seconds.
(R) 11-4	Fully Compliant
(O) 11-5	Fully Compliant
(O) 11-6	Fully Compliant
(O) 11-7	Not Compliant	The EAGLE 5 ISS does not support storage of autonomous messages for retransmission.
(R) 11-8	Not Compliant	The EAGLE 5 ISS does not support storage of autonomous messages for retransmission.

Table A-9 Section 12. Message Priority and Routing

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(R) 12-1	Fully Compliant
(R) 12-2	Fully Compliant
(O) 12-3	Not Compliant	The EAGLE 5 ISS does not provide a means for configuring message loads among the non-time critical channels.
(R) 12-4	Fully Compliant
(R) 12-5	Fully Compliant
(R) 12-6	Fully Compliant

Table A-10 Section 13. Routing Verification Test Messages

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(CR) 13-1	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-2	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-3	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-4	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-5	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-6	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-7	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-8	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-9	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-10	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-11	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-12	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-13	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-14	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-15	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-16	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-17	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.
(CR) 13-18	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because OMAP routing verification tests are a SEAS post-7.0 feature.

Table A-11 Appendix A. Data Collection Request Structure

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(R) A-1	Not Compliant	The EAGLE 5 ISS does not support supplier-specific data collection mnemonics for non-standard collection schedules.
(R) A-2	Fully Compliant
(R) A-3	Not Compliant	The EAGLE 5 ISS does not support supplier-specific data collection mnemonics for non-standard measured entity types.
(R) A-4	Not Compliant	The EAGLE 5 ISS does not support supplier-specific data collection mnemonics for non-standard measured entity types.
(R) A-5	Partially Compliant	The new non-standard measurement registers defined for Release 21.0 and beyond conform to supplier-specific data collection mnemonics.
(R) A-6	Partially Compliant	The new non-standard measurement registers defined for Release 21.0 and beyond conform to supplier-specific data collection mnemonics.
(R) A-7	Fully Compliant
(R) A-8	Fully Compliant
(R) A-9	Fully Compliant
(R) A-10	Fully Compliant
(R) A-11	Fully Compliant
(R) A-12	Fully Compliant
(R) A-13	Fully Compliant
(R) A-14	Fully Compliant

Table A-12 Appendix B. Standard Data Collection Schedules

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(R) B-1	Fully Compliant
(R) B-2	Fully Compliant
(R) B-3	Fully Compliant
(R) B-4	Fully Compliant
(R) B-5	Fully Compliant
(R) B-6	Fully Compliant
(R) B-7	Fully Compliant
(R) B-8	Fully Compliant
(R) B-9	Fully Compliant
(O) B-10	Fully Compliant
(R) B-11	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(R) B-12	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(R) B-13	Fully Compliant
(R) B-14	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(R) B-15	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(O) B-16	Not Compliant	The EAGLE 5 ISS does not support this measurement in its STP system totals (P_SYSTOT) measurements schedule.
(O) B-17	Not Compliant	The EAGLE 5 ISS does not support this measurement in its STP system totals (P_SYSTOT) measurements schedule.
(R) B-18	Fully Compliant
(R) B-19	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-20	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because SCCP ISNI message routing is a SEAS post-7.0 feature.
(O) B-21	Not Applicable	This objective does not apply to the EAGLE 5 ISS because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-22	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-23	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-24	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-25	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-26	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-27	Fully Compliant
(O) B-28	Fully Compliant
(O) B-29	Not Applicable	This objective does not apply to the EAGLE 5 ISS because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(O) B-30	Not Applicable	This objective does not apply to the EAGLE 5 ISS because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(R) B-31	Fully Compliant
(R) B-32	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(R) B-33	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(O) B-34	Not Compliant	The EAGLE 5 ISS does not support the TT entity type.
(R) B-35	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because SCCP application support is a SEAS post-7.0 feature.
(R) B-36	Fully Compliant
(R) B-37	Fully Compliant
(R) B-38	Fully Compliant
(R) B-39	Fully Compliant
(O) B-40	Not Compliant	The EAGLE 5 ISS does not support this measurement in its component (P_COMP) measurements schedule.
(R) B-41	Fully Compliant
(R) B-42	Fully Compliant
(R) B-43	Fully Compliant
(O) B-44	Not Compliant	The EAGLE 5 ISS does not support this measurement in its component (P_COMP) measurements schedule.
(O) B-45	Not Compliant	The EAGLE 5 ISS does not support this measurement in its component (P_COMP) measurements schedule.
(R) B-46	Fully Compliant
(R) B-47	Fully Compliant
(O) B-48	Fully Compliant
(R) B-49	Fully Compliant
(R) B-50	Fully Compliant
(O) B-51	Not Compliant	The EAGLE 5 ISS does not support this measurement in its component (P_COMP) measurements schedule.
(R) B-52	Fully Compliant
(R) B-53	Fully Compliant
(O) B-54	Not Compliant	The EAGLE 5 ISS does not support this measurement in its component (P_COMP) measurements schedule.
(R) B-55	Fully Compliant
(R) B-56	Fully Compliant
(R) B-57	Not Compliant	The EAGLE 5 ISS does not support this measurement in its component (P_COMP) measurements schedule.
(O) B-58	Not Compliant	The EAGLE 5 ISS does not support this measurement in its component (P_COMP) measurements schedule.
(O) B-59	Not Compliant	The EAGLE 5 ISS does not support this measurement in its component (P_COMP) measurements schedule.
(O) B-60	Not Compliant	The EAGLE 5 ISS does not support this measurement in its component (P_COMP) measurements schedule.
(O) B-61	Not Compliant	The EAGLE 5 ISS does not support this measurement in its component (P_COMP) measurements schedule.
(O) B-62	Not Compliant	The EAGLE 5 ISS does not support this measurement in its component (P_COMP) measurements schedule.
(O) B-63	Not Compliant	The EAGLE 5 ISS does not support this measurement in its component (P_COMP) measurements schedule.
(R) B-64	Fully Compliant
(R) B-65	Fully Compliant
(R) B-66	Fully Compliant
(R) B-67	Fully Compliant
(R) B-68	Fully Compliant
(R) B-69	Fully Compliant
(R) B-70	Fully Compliant
(R) B-71	Fully Compliant
(R) B-72	Fully Compliant
(R) B-73	Fully Compliant
(O) B-74	Not Compliant	The EAGLE 5 ISS does not support the BFRGRP entity type.
(O) B-75	Not Compliant	The EAGLE 5 ISS does not support the BUFFR entity type.
(O) B-76	Not Compliant	The EAGLE 5 ISS does not support the BUFFR entity type.
(O) B-77	Not Compliant	The EAGLE 5 ISS does not support the BUFFR entity type.
(O) B-78	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(CR) B-79	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(CR) B-80	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(O) B-81	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(R) B-82	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(CR) B-83	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(CR) B-84	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(O) B-85	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(CR) B-86	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(CR) B-87	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(O) B-88	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(CR) B-89	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(CR) B-90	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(O) B-91	Not Compliant	The EAGLE 5 ISS does not support the PROC entity type.
(O) B-92	Not Compliant	The EAGLE 5 ISS does not support the PROCGRP entity type.
(O) B-93	Not Compliant	The EAGLE 5 ISS does not support the PROCGRP entity type.
(O) B-94	Not Compliant	The EAGLE 5 ISS does not support the PROCGRP entity type.
(O) B-95	Not Compliant	The EAGLE 5 ISS does not support the PROCGRP entity type.
(O) B-96	Not Compliant	The EAGLE 5 ISS does not support the PROCGRP entity type.
(O) B-97	Not Compliant	The EAGLE 5 ISS does not support the PROCGRP entity type.
(O) B-98	Not Compliant	The EAGLE 5 ISS does not support the PROCGRP entity type.
(O) B-99	Not Compliant	The EAGLE 5 ISS does not support the PROCGRP entity type.
(O) B-100	Not Compliant	The EAGLE 5 ISS does not support the PROCGRP entity type.
(O) B-101	Not Compliant	The EAGLE 5 ISS does not support the PROCGRP entity type.
(O) B-102	Not Compliant	The EAGLE does not support the PROCGRP entity type.
(O) B-103	Not Compliant	EAGLE does not support the PROCGRP entity type.
(O) B-104	Not Compliant	EAGLE does not support the PROCGRP entity type.
(O) B-105	Not Compliant	The EAGLE does not support the PROCGRP entity type.
(O) B-106	Not Compliant	The EAGLE does not support the BUS entity type.
(O) B-107	Not Compliant	The EAGLE does not support the BUS entity type.
(O) B-108	Not Compliant	The EAGLE does not support the BUS entity type.
(O) B-109	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(O) B-110	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(O) B-111	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(O) B-112	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(O) B-113	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(O) B-114	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(O) B-115	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(O) B-116	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(O) B-117	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(O) B-118	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(R) B-119	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(R) B-120	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(R) B-121	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(R) B-122	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(R) B-123	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(R) B-124	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(R) B-125	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(R) B-126	Not Compliant	The EAGLE does not support the service measurements (P_SERV) schedule.
(CR) B-127	Not Applicable	This conditional requirement does not apply to the EAGLE because the special study measurements (P_SPST) schedule is a SEAS deferred feature.
(CR) B-128	Not Applicable	This conditional requirement does not apply to the EAGLE because the special study measurements (P_SPST) schedule is a SEAS deferred feature.
(CR) B-129	Not Applicable	This conditional requirement does not apply to the EAGLE because the special study measurements (P_SPST) schedule is a SEAS deferred feature.
(CR) B-130	Not Applicable	This conditional requirement does not apply to the EAGLE because the special study measurements (P_SPST) schedule is a SEAS deferred feature.
(CR) B-131	Not Applicable	This conditional requirement does not apply to the EAGLE because the special study measurements (P_SPST) schedule is a SEAS deferred feature.
(CR) B-132	Not Applicable	This conditional requirement does not apply to the EAGLE because the special study measurements (P_SPST) schedule is a SEAS deferred feature.
(CR) B-133	Not Applicable	This conditional requirement does not apply to the EAGLE because the special study measurements (P_SPST) schedule is a SEAS deferred feature.
(CR) B-134	Not Applicable	This conditional requirement does not apply to the EAGLE because the special study measurements (P_SPST) schedule is a SEAS deferred feature.
(O) B-135	Fully Compliant
(O) B-136	Fully Compliant
(O) B-137	Fully Compliant
(O) B-138	Fully Compliant
(O) B-139	Fully Compliant
(O) B-140	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-141	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-142	Fully Compliant
(O) B-143	Fully Compliant
(O) B-144	Fully Compliant
(O) B-145	Fully Compliant
(O) B-146	Fully Compliant
(O) B-147	Fully Compliant
(O) B-148	Fully Compliant
(O) B-149	Fully Compliant
(O) B-150	Not Applicable	This objective does not apply because this measurement is currently unassigned and reserved for future use by SEAS.
(O) B-151	Fully Compliant
(O) B-152	Fully Compliant
(O) B-153	Fully Compliant
(O) B-154	Fully Compliant
(O) B-155	Fully Compliant
(O) B-156	Fully Compliant
(O) B-157	Fully Compliant
(O) B-158	Fully Compliant
(O) B-159	Fully Compliant
(O) B-160	Fully Compliant
(O) B-161	Fully Compliant
(O) B-162	Fully Compliant
(O) B-163	Fully Compliant
(O) B-164	Fully Compliant
(O) B-165	Fully Compliant
(O) B-166	Fully Compliant
(O) B-167	Fully Compliant
(O) B-168	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-169	Fully Compliant
(O) B-170	Fully Compliant
(O) B-171	Fully Compliant
(O) B-172	Fully Compliant
(O) B-173	Fully Compliant
(O) B-174	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-175	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-176	Fully Compliant
(O) B-177	Fully Compliant
(O) B-178	Fully Compliant
(O) B-179	Fully Compliant
(CR) B-180	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-181	Not Compliant	The EAGLE does not support the PROCGRP entity type.
(O) B-182	Fully Compliant
(O) B-183	Fully Compliant
(O) B-184	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-185	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-186	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-187	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-188	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-189	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-190	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-191	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-192	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-193	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-194	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-195	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-196	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-197	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-198	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-199	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-200	Partially Compliant	This register is reported on a per-link basis and not part of the LNKSET entity type.
(O) B-201	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-202	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-203	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-204	Not Compliant	The EAGLE does not support the BFRGRP entity type.
(O) B-205	Not Compliant	The EAGLE does not support the BFRGRP entity type.
(O) B-206	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-207	Not Compliant	This register is both not supported and not reported.
(O) B-208	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-209	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-210	Partially Compliant	The value reported is hardcoded and non-provisionable.
(O) B-211	Partially Compliant	The value reported is hardcoded and non-provisionable.
(O) B-212	Partially Compliant	The value reported is hardcoded and non-provisionable.
(O) B-213	Partially Compliant	The value reported is hardcoded and non-provisionable.
(O) B-214	Partially Compliant	The value reported is hardcoded and non-provisionable.
(O) B-215	Partially Compliant	The value reported is hardcoded and non-provisionable.
(O) B-216	Partially Compliant	The value reported is hardcoded and non-provisionable.
(O) B-217	Partially Compliant	The value reported is hardcoded and non-provisionable.
(O) B-218	Partially Compliant	The value reported is hardcoded and non-provisionable.
(O) B-219	Fully Compliant
(O) B-220	Fully Compliant
(O) B-221	Fully Compliant
(O) B-222	Fully Compliant
(O) B-223	Fully Compliant
(O) B-224	Fully Compliant	.
(O) B-225	Fully Compliant
(O) B-226	Fully Compliant
(O) B-227	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-228	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-229	Not Compliant	The EAGLE does not support this measurement in its in-service record base (P_RBASE) measurements schedule.
(O) B-230	Not Compliant	The EAGLE does not support the BUFFR entity type.
(O) B-231	Not Compliant	The EAGLE does not support the BUFFR entity type.
(O) B-232	Not Compliant	The EAGLE does not support the supplier-specific entity types.
(O) B-233	Fully Compliant
(O) B-234	Fully Compliant
(O) B-235	Fully Compliant
(R) B-236	Fully Compliant
(R) B-237	Fully Compliant
(R) B-238	Fully Compliant
(O) B-239	Fully Compliant
(O) B-240	Not Applicable	This objective does not apply to the EAGLE because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(O) B-241	Not Applicable	This objective does not apply to the EAGLE because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(O) B-242	Fully Compliant
(O) B-243	Not Applicable	This objective does not apply to the EAGLE because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(O) B-244	Not Applicable	This objective does not apply to the EAGLE because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(O) B-245	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(R) B-246	Fully Compliant
(R) B-247	Fully Compliant
(R) B-248	Fully Compliant
(O) B-249	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-250	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-251	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(CR) B-252	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(CR) B-253	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(CR) B-254	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(CR) B-255	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(R) B-256	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(R) B-257	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(R) B-258	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(R) B-259	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-260	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-261	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(CR) B-262	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(CR) B-263	Not Compliant	The EAGLE 5 ISS does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(CR) B-264	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(CR) B-265	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(R) B-266	Fully Compliant
(R) B-267	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-268	Not Applicable	This objective does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-269	Not Applicable	This requirement does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-270	Not Applicable	This requirement does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-271	Not Applicable	This requirement does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-272	Not Applicable	This requirement does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-273	Not Applicable	This requirement does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-274	Not Applicable	This requirement does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-275	Not Applicable	This requirement does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-276	Fully Compliant
(R) B-277	Fully Compliant
(O) B-278	Fully Compliant
(R) B-279	Fully Compliant
(R) B-280	Fully Compliant
(R) B-281	Fully Compliant
(R) B-282	Partially Compliant	The value is approximated by dividing the number of octets received by the link speed (in octets/second)
(O) B-283	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(R) B-284	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-285	Fully Compliant
(O) B-286	Fully Compliant
(R) B-287	Fully Compliant
(O) B-288	Fully Compliant
(O) B-289	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(R) B-290	Partially Compliant	This value is the number of signaling units received with bad CRC.
(O) 2-291	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) 2-292	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(R) B-293	Fully Compliant
(O) B-294	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-295	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-296	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-297	Fully Compliant
(O) B-298	Fully Compliant
(O) B-299	Fully Compliant
(O) B-300	Fully Compliant
(O) B-301	Fully Compliant
(O) B-302	Fully Compliant
(O) B-303	Fully Compliant
(O) B-304	Fully Compliant
(O) B-305	Fully Compliant
(R) B-306	Fully Compliant
(O) B-307	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(R) B-308	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(R) B-309	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-310	Fully Compliant
(R) B-311	Fully Compliant
(R) B-312	Fully Compliant
(R) B-313	Fully Compliant
(O) B-314	Fully Compliant
(O) B-315	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-316	Fully Compliant
(O) B-317	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-318	Fully Compliant
(O) B-319	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-320	Fully Compliant
(O) B-321	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-322	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-323	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-324	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-325	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-326	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-327	Not Compliant	The EAGLE does not support this measurement in its daily maintenance (P_MTCD) measurements schedule.
(O) B-328	Not Compliant	The EAGLE does not support the PROCGRP entity type.
(O) B-329	Not Compliant	The EAGLE does not support the PROCGRP entity type.
(O) B-330	Not Compliant	The EAGLE does not support the PROCGRP entity type.
(O) B-331	Not Compliant	The EAGLE does not support the PROC entity type
(O) B-332	Not Compliant	The EAGLE does not support the PROC entity type
(O) B-333	Not Compliant	The EAGLE does not support the PROC entity type
(O) B-334	Not Compliant	The EAGLE does not support the PROC entity type
(O) B-335	Not Compliant	The EAGLE does not support the PROC entity type
(R) B-336	Not Compliant	The EAGLE does not support the PROC entity type
(O) B-337	Not Compliant	The EAGLE does not support the supplier-specific entity types.
(O) B-338	Not Compliant	The EAGLE does not support the supplier-specific entity types.
(O) B-339	Not Compliant	The EAGLE does not support the supplier-specific entity types.
(O) B-340	Not Compliant	The EAGLE does not support the network management on-demand measurements (D_NM) schedule.
(O) B-341	Not Compliant	The EAGLE does not support the network management on-demand measurements (D_NM) schedule.
(O) B-342	Not Compliant	The EAGLE does not support the network management on-demand measurements (D_NM) schedule.
(O) B-343	Not Compliant	The EAGLE 5 ISS does not support the network management on-demand measurements (D_NM) schedule.
(O) B-344	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-345	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-346	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-347	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-348	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-349	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-350	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-351	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-352	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-353	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(CR) B-354	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(CR) B-355	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(CR) B-356	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-357	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-358	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-359	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-360	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-361	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-362	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-363	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-364	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-365	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-366	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-367	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-368	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-369	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-370	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-371	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-372	Not Compliant	The EAGLE 5 ISS does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-373	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-374	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-375	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-376	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(R) B-377	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-378	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-379	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-380	Not Compliant	The EAGLE does not support the hourly maintenance (on-demand) measurements (D_MTCH) schedule.
(O) B-381	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(O) B-382	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(O) B-383	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(O) B-384	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(O) B-385	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(O) B-386	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(O) B-387	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(O) B-388	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(O) B-389	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(O) B-390	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(O) B-391	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(O) B-392	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(O) B-393	Not Compliant	The EAGLE does not support the maintenance status indicators (on-demand) measurements (D_MTCS) schedule.
(R) B-394	Fully Compliant
(R) B-395	Fully Compliant
(R) B-396	Fully Compliant
(R) B-397	Fully Compliant
(R) B-398	Fully Compliant
(R) B-399	Fully Compliant
(R) B-400	Fully Compliant
(R) B-401	Fully Compliant
(R) B-402	Fully Compliant
(O) B-403	Fully Compliant
(R) B-404	Not Applicable	This requirement does not apply to the EAGLE because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(R) B-405	Not Applicable	This requirement does not apply to the EAGLE because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(R) B-406	Fully Compliant
(R) B-407	Not Applicable	This requirement does not apply to the EAGLE because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(R) B-408	Not Applicable	This requirement does not apply to the EAGLE because GTT (and MTP routing) error surveillance improvements is a SEAS post-7.0 feature.
(O) B-409	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(O) B-410	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(O) B-411	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(O) B-412	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(O) B-413	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(O) B-414	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(O) B-415	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(O) B-416	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(O) B-417	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(O) B-418	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(O) B-419	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(O) B-420	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(R) B-421	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(R) B-422	Not Compliant	The EAGLE does not support this measurement in its network management measurements (A_NM) schedule.
(O) B-423	Not Applicable	This objective does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-424	Not Applicable	This requirement does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(O) B-425	Not Applicable	This objective does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(O) B-426	Not Applicable	This objective does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(O) B-427	Not Applicable	This objective does not apply to the EAGLE because SCCP ISNI message routing is a SEAS post-7.0 feature.
(R) B-428	Fully Compliant
(R) B-429	Fully Compliant
(R) B-430	Fully Compliant
(R) B-431	Fully Compliant
(R) B-432	Fully Compliant
(R) B-433	Fully Compliant
(R) B-434	Fully Compliant
(R) B-435	Fully Compliant
(R) B-436	Fully Compliant
(R) B-437	Fully Compliant
(R) B-438	Fully Compliant
(R) B-439	Fully Compliant
(R) B-440	Fully Compliant
(R) B-441	Not Compliant	The EAGLE does not support the PROC entity type.
(R) B-442	Not Compliant	The EAGLE does not support the PROC entity type.
(R) B-443	Not Compliant	The EAGLE does not support the PROC entity type.

A.3 SEAS-STP Gateway Function Interface Specification, GR-778-CORE, Issue 1, November 1994

Table A-13 Section 3. Recent Change and Verify Gateway Messages

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(R) 3-1	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation, the link set group identifier parameter, the remarks parameter, nor the supplier-specific parameter block. Also, the EAGLE 5 ISS does not support new input validations, because this is a SEAS post-7.0 feature.
(R) 3-2	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. Also, the EAGLE 5 ISS does not support new input validations, because this is a SEAS post-7.0 feature.
(R) 3-3	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation, the new link set group identifier parameter, the new remarks parameter, nor the new supplier-specific parameter block. also, the EAGLE 5 ISS does not support new input validations, because this is a SEAS post-7.0 feature.
(R) 3-4	Partially Compliant	The EAGLE 5 ISS does not support ranges the parameters for delayed activation, the remarks parameter, nor the supplier-specific parameter block. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, because these are SEAS post-7.0 features.
(R) 3-5	Partially Compliant	The EAGLE 5 ISS does not support deleting all OPCs for a screening reference (the value ‘’ for the `NC` and `NCM` parameters), nor the parameters for delayed activation. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, because these are SEAS** post-7.0 features.
(R) 3-6	Partially Compliant	The EAGLE 5 ISS does not support changing all OPCs for a screening reference (the value ‘’ for the `NC` and `NCM` parameters), the parameters for delayed activation, the new remarks parameter, nor the new supplier-specific parameter block. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, because these are SEAS** post-7.0 features.
(R) 3-7	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation, the remarks parameter, nor the supplier-specific parameter block. Also, the EAGLE 5 ISS does not support ISUP message type screening, rejection message suppression on a per screen basis, and new input validations, because these are SEAS post-7.0 features.
(R) 3-8	Partially Compliant	The EAGLE 5 ISS does not support deleting all DPCs for a screening reference (the value ‘’ for the `NC` and `NCM` parameters), nor the parameters for delayed activation. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, because these are SEAS** post-7.0 features.
(R) 3-9	Partially Compliant	The EAGLE 5 ISS does not support changing all DPCs for a screening reference (the value ‘’ for the current `NC` and current `NCM` parameters), the parameters for delayed activation, the new remarks parameter, nor the new supplier-specific parameter block. Also, the EAGLE 5 ISS does not support ISUP message type screening, rejection message suppression on a per screen basis, and new input validations, because these are SEAS** post-7.0 features.
(R) 3-10	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation, the remarks parameter, nor the supplier-specific parameter block. Also, the EAGLE 5 ISS does not support new input validations, because this is a SEAS post-7.0 feature.
(R) 3-11	Partially Compliant	The EAGLE 5 ISS does not support deleting all blocked OPCs for a screening reference (the value ‘’ for the `NC` and `NCM` parameters), nor the parameters for delayed activation. Also, the EAGLE 5 ISS does not support new input validations, because this is a SEAS** post-7.0 feature.
(R) 3-12	Partially Compliant	The EAGLE 5 ISS does not support changing all blocked OPCs for a screening reference (the value ‘’ for the current `NC` and current `NCM` parameters), the parameters for delayed activation, the new remarks parameter, nor the new supplier-specific parameter block. Also, the EAGLE 5 ISS does not support new input validations, because this is a SEAS** post-7.0 feature.
(R) 3-13	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation, the remarks parameter, nor the supplier-specific parameter block. Also, the EAGLE 5 ISS does not support ISUP message type screening and new input validations, because these are SEAS post-7.0 features.
(R) 3-14	Partially Compliant	The EAGLE 5 ISS does not support deleting all blocked DPCs for a screening reference (the value ‘’ for the `NC` and `NCM` parameters), nor the parameters for delayed activation. Also, the EAGLE 5 ISS does not support ISUP message type screening and new input validations, because these are SEAS** post-7.0 features.
(R) 3-15	Partially Compliant	The EAGLE 5 ISS does not support changing all blocked DPCs for a screening reference (the value ‘’ for the current `NC` and current `NCM` parameters), the parameters for delayed activation, the new remarks parameter, nor the new supplier-specific parameter block. Also, the EAGLE 5 ISS does not support new input validations, because this is a SEAS** post-7.0 feature.
(R) 3-16	Partially Compliant	The EAGLE 5 ISS does not support ranges for the service indicator and network indicator parameters, the parameters for delayed activation, the remarks parameter, nor the supplier-specific parameter block. Also, the EAGLE 5 ISS does not support ISUP message type screening, rejection message suppression on a per screen basis, and new input validations, because these are SEAS post-7.0 features.
(R) 3-17	Partially Compliant	The EAGLE 5 ISS does not support deleting all SIOs for a screening reference (the ‘’ value for the network indicator and message priority parameters), ranges for the service indicator (`SI`) and network indicator (`NIC`) parameters, the parameters for delayed activation, nor the message priority parameter. Also, the EAGLE 5 ISS does not support ISUP message type screening, rejection message suppression on a per screen basis, and new input validations, because these are SEAS** post-7.0 features.
(R) 3-18	Partially Compliant	The EAGLE 5 ISS does not support changing all SIOs for a screening reference (the value ‘’ for the current network indicator and current message priority parameters), ranges for the current service indicator, new service indicator, current network indicator or new network indicator parameters, the parameters for delayed activation, the new remarks parameter, nor the new supplier-specific parameter block. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, because these are SEAS** post-7.0 features.
(R) 3-19	Partially Compliant	The EAGLE 5 ISS does not support ranges for the subsystem number parameter, the parameters for delayed activation, the link set group identifier parameter, the remarks parameter, nor the supplier-specific parameter block. Also, the EAGLE 5 ISS does not support SCCP message type screening and rejection message suppression on a per screen basis, because these are SEAS post-7.0 features.
(R) 3-20	Partially Compliant	The EAGLE 5 ISS does not support deleting all CGPAs for a screening reference (the value ‘’ for the `NC`, `NCM`, and routing indicator parameters), ranges for the subsystem number parameter, the parameters for delayed activation, nor the link set group identifier parameter. Also, the EAGLE 5 ISS does not support SCCP message type screening and rejection message suppression on a per screen basis, because these are SEAS** post-7.0 features.
(R) 3-21	Partially Compliant	The EAGLE 5 ISS does not support changing all CGPAs for a screening reference (the value ‘’ for the current `NC`, current `NCM`, and current routing indicator parameters), ranges for the current subsystem number and new subsystem number parameters, the parameters for delayed activation, the link set group identifier parameter, the new link set identifier parameter, the new remarks parameter, nor the new supplier-specific parameter block. Also, the EAGLE 5 ISS does not support SCCP message type screening and rejection message suppression on a per screen basis, because these are SEAS** post-7.0 features.
(R) 3-22	Partially Compliant	The EAGLE 5 ISS does not support ranges for the subsystem number parameter, the parameters for delayed activation, the remarks parameter, nor the supplier-specific parameter block. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis, because this is a SEAS post-7.0 feature.
(R) 3-23	Partially Compliant	The EAGLE 5 ISS does not support deleting all CDPAs for a screening reference (the value ‘’ for the `NC`, `NCM`, and SCMG format identifier parameters), ranges for the subsystem number parameter, nor the parameters for delayed activation. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis, because this is a SEAS** post-7.0 feature.
(R) 3-24	Partially Compliant	The EAGLE 5 ISS does not support changing all CDPAs for a screening reference (the value ‘’ for the current `NC`, current `NCM`, and current SCMG format identifier parameters), ranges for the current subsystem number and new subsystem number parameters, the parameters for delayed activation, the new remarks parameter, nor the new supplier-specific parameter block. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis, because this is a SEAS** post-7.0 feature.
(R) 3-25	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation, the remarks parameter, nor the supplier-specific parameter block. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, because these are SEAS post-7.0 features.
(R) 3-26	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, because these are SEAS post-7.0 features.
(R) 3-27	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation, the new remarks parameter, nor the new supplier-specific parameter block. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, because these are SEAS post-7.0 features.
(R) 3-28	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation, the remarks parameter, nor the supplier-specific parameter block. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, as these are SEAS post-7.0 features.
(R) 3-29	Partially Compliant	The EAGLE 5 ISS does not support deleting all DESTFLDs for a screening reference (the value ‘’ for the `NC` and `NCM` parameters), nor the parameters for delayed activation. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, as these are SEAS** post-7.0 features.
(R) 3-30	Partially Compliant	The EAGLE 5 ISS does not support changing all DESTFLDs for a screening reference (the value ‘’ for the current `NC` and current `NCM` parameters), the parameters for delayed activation, the new remarks parameter, nor the new supplier-specific parameter block. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, as these are SEAS** post-7.0 features.
(R) 3-31	Partially Compliant	The EAGLE 5 ISS does not support ranges for the subsystem number parameter, the parameters for delayed activation, the remarks parameter, nor the supplier-specific parameter block. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, as these are SEAS post-7.0 features
(R) 3-32	Partially Compliant	The EAGLE 5 ISS does not support deleting all AFTPCs for a screening reference (the value ‘’ for the `NC`, `NCM`, and subsystem number parameters), ranges for the subsystem number parameter, nor the parameters for delayed activation. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, as these are SEAS** post-7.0 features.
(R) 3-33	Partially Compliant	The EAGLE 5 ISS does not support changing all AFTPCs for a screening reference (the value ‘’ for the current `NC`, current `NCM`, and current subsystem number parameters), ranges for the current subsystem number and new subsystem number parameters, the parameters for delayed activation, the new remarks parameter, nor the new supplier-specific parameter block. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, as these are SEAS** post-7.0 features.
(R) 3-34	Partially Compliant	The EAGLE 5 ISS does not support the parameters for delayed activation, the New Remarks parameter, nor the New Supplier-Specific Parameter block. Also, the EAGLE 5 ISS does not support Rejection Message Suppression on a per screen basis and New Input Validations as these are SEAS post-7.0 feature.
(R) 3-35	Partially Compliant	The EAGLE 5 ISS does not support deleting all ISUP Message types for a screening reference (the null value for the ISUP parameter), the parameters for delayed activation, the New Remarks parameter, nor the New Supplier-Specific Parameter block. Also, the EAGLE 5 ISS does not support Rejection Message Suppression on a per screen basis and New Input Validations as these are SEAS post-7.0 feature.
(R) 3-36	Partially Compliant	The EAGLE 5 ISS does not support changing all ISUP Message Types for a screening reference (the null value for the ISUP and NISUP parameters), the parameters for delayed activation, the new remarks parameter, nor the new supplier-specific parameter block. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, as these are SEAS post-7.0 features.
(CR) 3-37	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because translation type mapping is a SEAS deferred feature.
(CR) 3-38	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because translation type mapping is a SEAS deferred feature.
(CR) 3-39	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because translation type mapping is a SEAS deferred feature.
(CR) 3-40	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because translation type mapping is a SEAS deferred feature.
(R) 3-41	Fully Compliant	The EAGLE 5 ISS does not support new input validations, as this is a SEAS post-7.0 feature.
(R) 3-42	Fully Compliant	The EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, because these are SEAS post-7.0 features.
(R) 3-43	Fully Compliant	The EAGLE 5 ISS does not support ISUP message type screening, rejection message suppression on a per screen basis, and new input validations, because these are SEAS post-7.0 features.
(R) 3-44	Fully Compliant	The EAGLE 5 ISS does not support new input validations, because this is a SEAS post-7.0 feature.
(R) 3-45	Fully Compliant	The EAGLE 5 ISS does not support ISUP message type screening and new input validations, because these are SEAS post-7.0 features.
(R) 3-46	Partially Compliant	The EAGLE 5 ISS does not support ranges for the service indicator and network indicator parameters. Also, the EAGLE 5 ISS does not support ISUP message type screening, rejection message suppression on a per screen basis, and new input validations, as these are SEAS post-7.0 features
(R) 3-47	Partially Compliant	The EAGLE 5 ISS does not support ranges for the subsystem number parameter, nor does it support the link set identifier parameter. also, the EAGLE 5 ISS does not support SCCP message type screening and rejection message suppression on a per screen basis, as these are SEAS post-7.0 features.
(R) 3-48	Partially Compliant	The EAGLE 5 ISS does not support ranges for the subsystem number parameter. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis, as this is a SEAS post-7.0 feature.
(R) 3-49	Fully Compliant	The EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, because these are SEAS post-7.0 features.
(R) 3-50	Fully Compliant	The EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, as these are SEAS post-7.0 features.
(R) 3-51	Partially Compliant	The EAGLE 5 ISS does not support ranges for the subsystem number parameter. Also, the EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, because these are SEAS post-7.0 features.
(R) 3-52	Fully Compliant	The EAGLE 5 ISS does not support rejection message suppression on a per screen basis and new input validations, as these are SEAS post-7.0 features.
(R) 3-53	Partially Compliant	This requirement does not apply to the EAGLE 5 ISS because translation type mapping is a SEAS deferred feature.
(R) 3-54	Partially Compliant	The EAGLE 5 ISS does not support translation type mapping, because this is a SEAS deferred feature.
(R) 3-55	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-56	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-57	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-58	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-59	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-60	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-61	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-62	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-63	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-64	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-65	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-66	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-67	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-68	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.
(R) 3-69	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new screening errors is a SEAS post-7.0 feature.

Table A-14 Section 4. Gateway On-Occurrence Autonomous Messages

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(R) 4-1	Fully Compliant
(R) 4-2	Partially Compliant	The EAGLE 5 ISS currently only supports the “GTWYLS” value for the entity set name parameter. The EAGLE 5 ISS does not support ISUP message type screening, SS7 message inclusion in rejection message, and additional fields that support PCS applications, as these are SEAS post-7.0 features.
(R) 4-3	Not Compliant	The EAGLE 5 ISS does not currently support the `REPT-SCRERR` message.

Table A-15 Section 5. Gateway Application Control Messages

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(R) 5-1	Not Compliant	The EAGLE 5 ISS does not support the `INH-COLL` command.
(R) 5-2	Not Compliant	The EAGLE 5 ISS does not support the `ALW-COLL` command.
(R) 5-3	Partially Compliant	The new values are set and used immediately. The current (possibly in-use) values are replaced.
(R) 5-4	Partially Compliant	New values are set and used immediately. The current (possibly in-use) values are replaced. The EAGLE 5 ISS does not support the SS7 message inclusion indicator parameter as this is a SEAS post-7.0 feature
(R) 5-5	Not Compliant	The EAGLE 5 ISS does not currently support the `SET-SCRERR-PRMTRS` message.
(R) 5-6	Fully Compliant
(R) 5-7	Fully Compliant
(R) 5-8	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new input validations is a SEAS post-7.0 feature.
(R) 5-9	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new input validations is a SEAS post-7.0 feature.
(R) 5-10	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new input validations is a SEAS post-7.0 feature.
(R) 5-11	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because new input validations is a SEAS post-7.0 feature.

Table A-16 Section 6. STP Gateway Data Collection

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(R) 6-1	Partially Compliant	See Table A-3.
(R) 6-2	Partially Compliant	The P_GTWY measurements schedule is being supported with the limitation that only the STP, ORIGNI, ORIGNINC, LNKSET, LSDESTNI and LSORIGNI entity types are supported. The ALL and ACTIVE values for the period parameter to the `SEND-DEM-MEAS` and `SEND-SCH-MEAS` is not supported for this schedule. Furthermore, the number of 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)
(O) 6-3	Not Applicable	This objective does not apply to the EAGLE 5 ISS because the gateway STP detailed rejection (P_GWREJ) measurement schedule is a SEAS deferred feature.
(R) 6-4	Not Compliant	The EAGLE 5 ISS does not currently support the gateway daily maintenance (P_GMTCD) measurement schedule.
(R) 6-5	Not Compliant	The EAGLE 5 ISS does not currently support the gateway hourly maintenance (P_GMTCH) measurement schedule.
(R) 6-6	Partially Compliant	The EAGLE 5 ISS does not currently support per originating network identifier, per translation type (ORIGNITT), per originating network identifier, per originating network cluster, per translation type (ONIONCTT), per link set, per originating network identifier, per destination point code, per service identifier (LSONDPSI), per link set, per originating network identifier, per affected destination field (LSONDEST), per link set, per originating network identifier, per calling party address PC and SSN, per translation type (LSONCGTT), per link set, per originating network identifier per calling party address PC and SSN, per DPC and called party address SSN (LSONCGCD), and per link set, per originating network identifier, measured entity types. Also, the EAGLE 5 ISS does not support the per 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 - NC combinations whose network indicator is in the range from 1 to 5 (inclusive).
(CR) 6-7	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because translation type mapping is a SEAS deferred feature.
(O) 6-8	Fully Compliant
(R) 6-9	Fully Compliant
(R) 6-10	Partially Compliant	See Table A-3
(O) 6-11	Not Compliant	The EAGLE 5 ISS does not currently report the particular field that failed in a gateway message.
(R) 6-12	Partially Compliant	The EAGLE 5 ISS does not currently support service (P_SERV) and gateway daily maintenance (P_GMTCD) measurement schedules.
(R) 6-13	Partially Compliant	The EAGLE 5 ISS does not currently support service (P_SERV), gateway daily maintenance (P_GMTCD), and gateway hourly maintenance (P_GMTCH) measurement schedules, as well as per buffer group (BFRGRP), per buffer (BUFFR), per processor group (PROCGRP), per processor (PROC), per originating network identifier (ORIGNI), per originating network identifier, per originating network cluster (ORIGNINC), per originating network identifier, per translation type (ORIGNITT), per originating network identifier, per originating network cluster, per translation type (ONIONCTT), per link set, per link set, per originating network identifier, per destination point code, per service identifier (LSONDPSI), per link set, per originating network identifier, per affected destination field (LSONDEST), per link set, per originating network identifier, per calling party address PC and SSN, per translation type (LSONCGTT), per link set, per originating network identifier per calling party address PC and SSN, per DPC and called party address SSN (LSONCGCD), and per link set, per originating network identifier, measured entity types. The EAGLE 5 ISS does not support the per link set, per translation type (LSTT) and the per translation type (TT) measured entity types, as those are SEAS deferred features. Also, the EAGLE 5 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 supported for schedule P_GTWY.
(R) 6-14	Partially Compliant	The EAGLE 5 ISS does not currently support the service (P_SERV), and gateway daily maintenance (P_GMTCD) measurement schedules.
(R) 6-15	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because gateway STP detailed rejection measurements is a SEAS deferred feature.

Table A-17 Section 8. Performance and Capacity Requirements

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(R) 8-1	Partially Compliant	Completion responses to commands that contain large amounts of data could take greater than 60 seconds.
(R) 8-2	Partially Compliant	The error response on input `TMC=SG99` will take much longer than 60 seconds.
(R) 8-3	Partially Compliant	Error responses on execution to commands that contain large amounts of data could take greater than 60 seconds.
(R) 8-4	Fully Compliant
(R) 8-5	Not Compliant	The EAGLE 5 ISS does not currently support the `INH-COLL` or `ALW-COLL` application control commands.
(R) 8-6	Not Compliant	The EAGLE 5 ISS does not currently support the `INH-COLL` or `ALW-COLL` application control commands.
(R) 8-7	Fully Compliant	The EAGLE 5 ISS does not support the gateway STP detailed rejection (P_GWREJ) measurement schedule, because this is a SEAS deferred feature.
(R) 8-8	Not Compliant	The EAGLE 5 ISS does not currently support the gateway daily maintenance (P_GMTCD) measurement schedule.
(R) 8-9	Not Compliant	The EAGLE 5 ISS does not currently support the gateway hourly maintenance (P_GMTCH) measurement schedule.
(R) 8-10	Fully Compliant
(R) 8-11	Not Compliant	The EAGLE 5 ISS does not currently support the `REPT-SCRERR` message.
(R) 8-12	Fully Compliant
(R) 8-13	Not Compliant	The EAGLE 5 ISS does not support storage of autonomous messages for retransmission.
(R) 8-14	Not Compliant	The EAGLE 5 ISS does not support storage of autonomous messages for retransmission.
(R) 8-15	Not Compliant	The EAGLE 5 ISS does not support storage of autonomous messages for retransmission.
(R) 8-16	Not Compliant	The EAGLE 5 ISS does not support storage of autonomous messages for retransmission.

Table A-18 Appendix B. Gateway Measurement Definitions and Standard Register Labels

Telcordia Requirement	Level of Compliance	Comments/Exceptions
(O) B-1	Fully Compliant
(O) B-2	Fully Compliant
(O) B-3	Not Compliant	The EAGLE 5 ISS does not support this measurement in its STP gateway administration measurements (P_GTWY) schedule.
(O) B-4	Fully Compliant
(O) B-5	Fully Compliant
(O) B-6	Fully Compliant
(O) B-7	Fully Compliant
(O) B-8	Fully Compliant
(O) B-9	Fully Compliant
(O) B-10	Fully Compliant
(O) B-11	Fully Compliant
(O) B-12	Fully Compliant
(O) B-13	Fully Compliant
(O) B-14	Fully Compliant
(O) B-15	Fully Compliant
(O) B-16	Fully Compliant
(O) B-17	Fully Compliant
(O) B-18	Fully Compliant
(CR) B-19	Fully Compliant
(R) B-20	Not Compliant	The EAGLE 5 ISS does not support this measurement in its STP gateway administration measurements (P_GTWY) schedule.
(R) B-21	Fully Compliant
(O) B-22	Fully Compliant
(O) B-23	Fully Compliant
(O) B-24	Fully Compliant
(R) B-25	Not Compliant	The EAGLE 5 ISS does not support this measurement in its STP gateway administration measurements (P_GTWY) schedule.
(R) B-26	Fully Compliant
(O) B-27	Fully Compliant
(O) B-28	Fully Compliant
(O) B-29	Fully Compliant
(O) B-30	Not Compliant	The EAGLE 5 ISS does not support this measurement in its STP gateway administration measurements (P_GTWY) schedule.
(R) B-31	Not Compliant	The EAGLE 5 ISS does not support the ORIGNITT entity type.
(R) B-32	Not Compliant	The EAGLE 5 ISS does not support the ORIGNITT entity type.
(O) B-33	Not Compliant	The EAGLE 5 ISS does not support the ORIGNITT entity type.
(R) B-34	Not Compliant	The EAGLE 5 ISS does not support the ONIONCTT entity type.
(R) B-35	Not Compliant	The EAGLE 5 ISS does not support the ONIONCTT entity type.
(O) B-36	Not Compliant	The EAGLE 5 ISS does not support the ONIONCTT entity type.
(R) B-37	Fully Compliant
(R) B-38	Fully Compliant
(R) B-39	Fully Compliant
(R) B-40	Fully Compliant
(R) B-41	Fully Compliant
(R) B-42	Fully Compliant
(R) B-43	Fully Compliant
(R) B-44	Fully Compliant
(R) B-45	Fully Compliant
(R) B-46	Fully Compliant
(R) B-47	Fully Compliant
(R) B-48	Fully Compliant
(R) B-49	Fully Compliant
(R) B-50	Fully Compliant
(R) B-51	Fully Compliant
(R) B-52	Fully Compliant
(R) B-53	Fully Compliant
(R) B-54	Fully Compliant
(O) B-55	Not Compliant	The EAGLE 5 ISS does not support this measurement in its STP gateway administration measurements (P_GTWY) schedule.
(R) B-56	Fully Compliant
(R) B-57	Fully Compliant
(R) B-58	Fully Compliant
(R) B-59	Fully Compliant
(R) B-60	Fully Compliant
(O) B-61	Not Compliant	The EAGLE 5 ISS does not support this measurement in its STP gateway administration measurements (P_GTWY) schedule.
(R) B-62	Fully Compliant
(R) B-63	Fully Compliant
(R) B-64	Fully Compliant
(R) B-65	Fully Compliant
(R) B-66	Fully Compliant
(R) B-67	Fully Compliant
(R) B-68	Fully Compliant
(R) B-69	Fully Compliant
(R) B-70	Fully Compliant
(R) B-71	Fully Compliant
(R) B-72	Fully Compliant
(O) B-73	Fully Compliant
(O) B-74	Fully Compliant
(O) B-75	Fully Compliant
(O) B-76	Fully Compliant
(O) B-77	Fully Compliant
(O) B-78	Fully Compliant
(O) B-79	Fully Compliant
(O) B-80	Not Compliant	The EAGLE 5 ISS does not support this measurement in its STP gateway administration measurements (P_GTWY) schedule.
(CR) B-81	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because translation type mapping is a SEAS deferred feature.
(CR) B-82	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because translation type mapping is a SEAS deferred feature.
(O) B-83	Not Applicable	This objective does not apply to the EAGLE 5 ISS because translation type mapping is a SEAS deferred feature.
(CR) B-84	Not Applicable	This conditional requirement does not apply to the EAGLE 5 ISS because translation type mapping is a SEAS deferred feature.
(O) B-85	Not Applicable	This objective does not apply to the EAGLE 5 ISS because translation type mapping is a SEAS deferred feature.
(R) B-86	Fully Compliant
(O) B-87	Not Applicable	Not Implemented.
(R) B-88	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the gateway STP detailed rejection (P_GWREJ) measurement schedule is a SEAS deferred feature.
(O) B-89	Not Applicable	This objective does not apply to the EAGLE 5 ISS because the gateway STP detailed rejection (P_GWREJ) measurement schedule is a SEAS deferred feature.
(R) B-90	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the gateway STP detailed rejection (P_GWREJ) measurement schedule is a SEAS deferred feature.
(R) B-91	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the gateway STP detailed rejection (P_GWREJ) measurement schedule is a SEAS deferred feature.
(O) B-92	Not Applicable	This objective does not apply to the EAGLE 5 ISS because the gateway STP detailed rejection (P_GWREJ) measurement schedule is a SEAS deferred feature.
(R) B-93	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the gateway STP detailed rejection (P_GWREJ) measurement schedule is a SEAS deferred feature.
(O) B-94	Not Applicable	This objective does not apply to the EAGLE 5 ISS because the gateway STP detailed rejection (P_GWREJ) measurement schedule is a SEAS deferred feature.
(R) B-95	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the gateway STP detailed rejection (P_GWREJ) measurement schedule is a SEAS deferred feature.
(R) B-96	Not Applicable	This requirement does not apply to the EAGLE 5 ISS because the gateway STP detailed rejection (P_GWREJ) measurement schedule is a SEAS deferred feature.
(O) B-97	Not Applicable	This objective does not apply to the EAGLE 5 ISS because the gateway STP detailed rejection (P_GWREJ) measurement schedule is a SEAS deferred feature.
(R) B-98	Not Compliant	The EAGLE 5 ISS does not support the STP gateway daily maintenance measurements (P_GMTCD) schedule.
(O) B-99	Not Compliant	The EAGLE 5 ISS does not support the STP gateway daily maintenance measurements (P_GMTCD) schedule.
(CR) B-100	Not Compliant	The EAGLE 5 ISS does not support the STP gateway daily maintenance measurements (P_GMTCD) schedule.
(O) B-101	Not Compliant	The EAGLE 5 ISS does not support the STP gateway daily maintenance measurements (P_GMTCD) schedule.
(CR) B-102	Not Compliant	The EAGLE 5 ISS does not support the STP gateway daily maintenance measurements (P_GMTCD) schedule.
(CR) B-103	Not Compliant	The EAGLE 5 ISS does not support the STP gateway daily maintenance measurements (P_GMTCD) schedule.
(O) B-104	Not Compliant	The EAGLE 5 ISS does not support the STP gateway daily maintenance measurements (P_GMTCD) schedule.
(R) B-105	Not Compliant	The EAGLE 5 ISS does not support the STP gateway daily maintenance measurements (P_GMTCD) schedule.
(O) B-106	Not Compliant	The EAGLE 5 ISS does not support the STP gateway daily maintenance measurements (P_GMTCD) schedule.