Print this page Print NPIF » NANC Change Orders » NANC 245

NANC 245

Subsequent Ports of Active SV with a Failed SP List

Origination Date :11/12/1998

Originator:AT&T

Description:

While performing 1.4 testing, AT&T ran into a situation of a subsequent port (from a currently active Subscription Version with LNP Type of POOL), with a Failed SP List.  The Illinois Pooling (NPAC 1.4) and existing NPAC functionality (FRS 1.10) allow this subsequent port to occur.

Should this be allowed under all conditions?

Arguments for allowing the subsequent port:

  • The NPAC should NOT restrict a customer’s ability to port their number to another provider, just because an SP didn’t successfully process the modify active request.
  • Even if this data was re-sent or re-synced at a later time after the subsequent port, the previous SV would have migrated to “Old”, and the new/current SV would not be affected.

Arguments against allowing the subsequent port:

  • One or more SP’s networks are out of sync, and the NPAC should clean up the failed SP List before allowing more activity on the TN(s).
  • The NPAC will need to add additional functionality to clean up the Failed SP List for the currently active SV, when a subsequent Activate is sent by the New SP.  This is needed to prevent the re-send or re-sync from being sent to the discrepant SP.
  • If the Failed SP List is not cleaned up, then a re-send or re-sync creates meaningless traffic over the NPAC SMS to Local SMS Interface, for the modify active request (since this SV has migrated to “Old”).

NPAC SMS considerations:

  • If the subsequent port is allowed, the Failed SP List should be zeroed out (on the old SV), once the new SV gets activated.
  • A Service Provider should only be allowed on the Failed SP List for 1 (one) SV for any given TN. 

Final Resolution:

Nov LNPAWG (Dallas), John will provide a separate write-up for Service Providers to take back internally and discuss.

Dec LNPAWG (Atlanta), discussed separate write-up.

This also applies for Old with a Failed SP List, so it really is just for Failed SP List, and not tied to any specific status.  We should NOT allow any subsequent activity (other than resend or resync) as long as Failed SP List.  Also, no network data mods of NPA-NXX or LRN data for this one.

MCI, still leave on open list.  Discuss next time.

Jan LNPAWG (Atlanta), still want to allow the subsequent port (even if have Failed List).  Want to keep the two bullet points of NPAC consideration, but put into new change order.

So, this change order is closed out.  Refer to “sister” change order, NANC 254 for new NPAC requirements on Failed SP List of subsequent ports.

Feb LNPAWG (San Ramon), leave on delete pending list for now.  BST evaluating 245 and 254, to see if O.K. with clearing out the Failed List on previous port, when they are the Old SP.

Mar LNPAWG (Denver), BST O.K. with clearing out Failed List.  Move to Implemented List (Delete section). 

Related Release:

N/A

Status: Closed