The LNPA Number Pooling Subcommittee prepared the original and revised schedules for release 3.0. Neustar was asked if they expect the LNPA to be involved in any further schedule changes. Neustar responded that they expected LLCs to handle coordination with LNPA. It was determined that the contractual relationship is between Neustar and the LLCs, but that the LLCs can request LNPA participation in scheduling decisions. Concern was expressed that the LNPA only meets once a month, and that this requires a quicker response. Several LNPA members indicated they would be available for more frequent conference calls to discuss the schedule if required.

Dianne indicated that the testing call minutes went out yesterday.

The WNPSC will post the version of this test plan that includes updates from this week’s meetings on the LNPA website. Carriers are requested to review this document and provide comments to the November LNPA-WG meeting. The test plan will also be reviewed at the NNPO meeting in November.

A brief history of the wireless test planning process was provided: The wireless test planning subcommittee was kicked off by the WNPSC. Participation was solicited from the regional operations teams and the LNPA-WG. The wireless testing subcommittee’s goal was to create a baseline document that carriers can use to negotiate the details of inter-company testing in a manner similar to the way the Illinois LNP test plan was used for wireline LNP testing.

The NNPO will manage any operations issues for wireless/wireline implementation. Wireless to wireless LNP testing will be facilitated by a testing subcommittee of the wireless operations team and the NNPO will create a separate wireless to wireline testing subcommittee.

The wireless LNP test plan covers both wireless to wireless testing and wireless to wireline testing. The test plan does not cover vertical services. The testing of vertical services is left to the discretion of individual service providers. It was noted that testing of vertical services was part of the wireline LNP testing in the Northeast and Southeast regions.

It was pointed out the FCC order requires ported customers to receive the same level of service as non-ported customers, and that companies who offer vertical services need to validate those services work with ported numbers. The optional testing of vertical services is based on the optional nature of offering vertical services.

The test plan considers each carrier as a "black box". That means that the plan addresses the communications and passing of information between companies, but does not address the internal processes carriers use to meet their commitments.

Testing will be planned between carriers. Each service provider is expected to identify a Testing Coordinator to be the point of contact other SPs will use to initiate test planning. Contact information for the test coordinators will be posted on a public website.

The LNPA asked to have the following statement added to the testing assumptions: "Test coordinators will disconnect their test accounts when testing is completed." The details of the logistics for testing will be worked out by the wireless testing subcommittees.

Will be moved to the accepted list. This affects "modify service provider profile" but not any other functionality.

Requirement RR3-49: Users should be able to do a mass update on blocks using either the new or old NPA during the permissive dialing period. The current software only allows mass updates on blocks with the new NPA. (defect 71311) It was recommended that rather than consider this a defect, we change the requirements to only allow the new NPA. (Mass update is an NPAC personnel only operation.) We will review a document only change order at the next meeting) The LNPA will recommend changing expected results of the test case which uses the old NPA.

The LLCs have removed change orders from the release 4.0 package and asked Neustar for re-pricing. Because the final makeup of release 4.0 has not been established, and we will want to consider the dropped change orders for release 5.0, the LNPA will wait until the LLCs complete the release 4.0 contract before prioritizing release 5.0.

Change NPAC Time References to Central Standard Time (Year Round). We discussed the options for 310 listed in the September minutes.

NANC-294 Will fix many (but not all) of the scenarios where the GMT date change issue impacts operations.

It was suggested that we create a list of all the operational problems associated with working in GMT. We will review the operational problems and test to see if the change order(s) solve those operational problems.

Action Item: Company reps are requested to identify scenarios where date and time issues with GMT cause operational problems and e-mail those to Jean Anthony by Thursday 10/19.

We will start change order review with NANC 310 next month, then move on to Illinois 23.

There is a proposal that we consider adding an edit to the NPAC that will prevent creation of subscription versions with LRNs from a different LATA than the TN.

We will change the phrase "two new issues were identified" to "one new issue was identified". We will accomplish the change by providing a replacement page containing the corrected text.

December 11 - 14 Qwest, Phoenix AZ

July 9 – 12    Canadian Consortium, Ottawa

August 13 - 16 AT&T, Seattle

September 10 - 13 Verizon, Baltimore

October 8 – 11 SBC, San Francisco

November 12 - 15 Neustar, New Orleans

December 10 – 13 Qwest, Phoenix