NANC 223
Suppress “snapback” notification to Donor SOA on LISP disconnect
Origination Date :07/06/1998
Originator:Sprint
Description:
On an intra-SP port (LNP Type = LISP), a disconnect is sent to the NPAC to return the TN to the original switch. The disconnect causes a “snapback” notification (subscriptionVersionDonorSP-Customer DisconnectDate) to be sent to the Donor SOA. However, this implies that the TN is available for re-assignment, when in fact, the customer may still be in-service.
Therefore, a request has been made to have the NPAC suppress the “snapback” notification to the Donor SOA on an LISP disconnect.
Final Resolution:
Discussed during 7/16/98 face-to-face T&O meeting. It was determined that the problem stems from the in-ability to send a Port-To-Original (PTO) port on an intra-SP port (LNP Type = LISP).
The business scenario is that a customer is “home” to switch A, then moves down the street and is “home” to switch B (still in same rate center, so was LISP-ed to switch B), then moves back up the street (and needs to be re “home” to switch A, but is still a working number).
In this scenario, the SP would NOT send a disconnect, because the number was still working, and would instead send an LISP PTO activate.
NEXT STEP: all SPs and vendors need to look at this internally, and be prepared to discuss during next telecon.
August T&O (Detroit). The group consensus was to close this change order (since the suppression of the "snapback" notification will violate certain business scenarios) and open a new change order (to capture the new functionality, which is to allow a PTO with a LISP). The new "sister" change order is NANC 230.
Related Release:
N/A
Status: Closed