NANC 239

Document the current process for Resynchronization

Origination Date :09/25/1998

Originator:National Number Pooling Sub-Com'ttee

Description:

While reviewing the Natl N Pool requirements, it was noted that the resynchronization functionality is NOT documented in the FRS.

It has been requested by the Sub-Committee to update this information in the FRS.

Also make sure resync functionality for Time Range and NPA-NXX Range, is also documented.

In recovery mode, a full failure SV is NOT sent to the LSMS.

The NPAC uses the Last Modified Timestamp to determine if the SV falls within the resyncing timerange.

3/31/99, Tekelec request.  NPAC-LSMS Resynchronization procedure needed when resource limitation exists.

In Appendix B of the NPAC SMS IIS - NANC Version 2.0.0 in section B.7.1, there needs to be a message flow added which describes the proper action(s) to be taken when the NPAC sends a CMISE primitive error: processingFailure/resourceLimitation instead of a successful M-ACTION response with lnpRecovery data.

This change order is a superset of NANC 275.

Final Resolution:

Backwards Compatible:  YES

This will be put into the queue of CMA updates to the FRS/IIS.  No date has been scheduled.

Apr LNPAWG (DC), another request from the team is to add all five return codes (in M-ACTION reply), and provide some suggested behavior.

Tekelec to look at the CMIP errors, and see if those are needed as well.

May LNPAWG (Baltimore), reported discussion on telecon call, 4/20.  The CMA will work on the updates as time permits.

Jul LNPAWG (Ottawa), Aug LNPAWG (Portland), Sep LNPAWG (Chicago), reviewed separate document write-up.  See revised version.

Oct LNPAWG (KC), group accepted updates.  Move to next doc category.

Related Release:

3.0.1

Status: Implemented