NEW PHASE II REQUIREMENTS (submitted by MCI) 5/22/97

- Marking of "Ported" vs. "Vacant Numbers." Requirement would facilitate

maintenance activities. For example, marking a number as "ported-out"

at the donor switch to alert craft personnel to the fact that the DN

is no longer resident on the switch. In addition, marking of a number

as "ported-in" at the recipient switch will alert craft personnel to

the fact that the NPA-NXX is "non-native" to the switch, implying that

the NPA-NXX functions as an office code and thus supports equipped DNs

served by the switch.

- Administrative Report on "ported out" numbers. Supports requirement

to support the marking of a number as ported out at the donor

switch. Report provides audit function of ported-out marking in the

switch against the number's status in the SCP to allow verification

of the integrity of the marking.

- No specific limit on the number of LRNs used to identify an LNP SSP

should be implied by design. The switch shall support as a minimum

number of LRNs based upon the number of rate centers served by

the switch assuming also 2 LRNs per rate center.

- AMA recording made at a terminating network's tandem or end office

should include an originating LNP module if the calling number was

ported. For Mutual compensation purposes.

- For calls made at an originating switch and completed to a ported DN

on the same switch, no query is performed. In the case of unbundling

(where CLEC may buy switch capacity to serve their customer) an LNP

module is needed on the originating and terminating sides to identify

the correct wire center in order to calculate the mileage component of

unbundling.

- Append an LNP module (720 or 719) to all originating AMA records generated

from a ported DN's including an origination LNP, not just access recording.

for Mutual compensation, identification of the real service provider

is critical to avoid settlement with the incorrect company.