These meeting minutes were taken by Barry Lewin, Bellcore. Thanks, Barry

Walt

Meeting minutes - ICC Test Team meeting - June 12, 1997, 350 Orleans,

4th Floor, Chicago (hosted by Ameritech) [approximately 17 attendees]

Agenda:

1. Action Items

2. FCC Guidelines Letter

3. NIIF update; review of test plan

4. Operator Services (incl. LIDB)

5. Test plan update (matrix)

6. Number pooling

7. Next Meeting

Action Item 1. Review of Action Items:

Issue 006a - NPAC Test Plan

Walt will be going to next week s NPAC meeting. He hopes to get a

response then.

Issue 12 - Choke network -

Desire to have a region wide choke network has not been adopted and it

is unclear if testing during the trial is appropriate. Although it is

useful to have test scripts for this, it appears inappropriate to test

during the trial. At least in MSA 1, the choke network solution as

discussed won t be implemented (in an LRN environment). To discuss with

Barry Bishop (Operations Committee) agreed that this issue is not

LRN/LNP and should be closed. Barry agreed to write wording regarding

the resolution for archive purposes.

Issue 18 - E911 test cases

The test cases have been written, provided to Bill Belshaw, on

ported.com under the 911 section. The scripts will be in the 1.4 version

of the test plan (the 1.4 version hasn t been released as yet).

Issue 24 - Failure scenario testing - to be discussed during FCC

Guidance discussion.

Issue 25 - LEC-to-LEC interface tests

Bill Belshaw working on these. It is assumed these will be in version

1.4.

Issue 26 - Test scripts for porting process flows

Bill Belshaw working on these. It is assumed these will be in version

1.4. These flows (to be useful) should be submitted before the July

meeting. Walt to contact Bill to determine if they will be available

before July meeting. Jim Joerger spoke with Bill Belshaw and reported

that porting flows should be available for the SPOC meeting next week.

Issue 28 - Test cases for post dial delay

Dick sent info to Bill. CLOSED last time.

Issue 29 - Test cases for LSMS section

CLOSED last time.

Issue 30 - SCP looping test

Walt will take this item and build script(s) based on what he does

internally. This will be discussed again in FCC guidance discussion.

Issue 32 - List of NXXs and DNs for each company

Dick has a great deal of information from several participants. The NPAC

is looking for this info. Dick pointed out that the info would go to the

NPAC regardless and this action item is just a back up. We (Walt and

Dick) will raise this issue at next week s NPAC meeting.

Issue 34 - Picture reference for each test case

The only area of concern is with ISDN. Because only Ameritech (and

perhaps Sprint) wants to test ISDN, it may not be a major concern. Walt

was planning to publish (via conference call) the tests that will be

run. This will close after the walk through of the ISDN scripts.

Issue 44 - SCP committee to write looping test script

CLOSED last time.

Issue 45 - Develop test procedure for looping test

CLOSED last time but the Test Team may want to re-consider a looping

test.

Issue 46 - Update to Section 4.4

Redundant with porting test scripts (issue 26). CLOSE issue 46.

Issue 47 - Update to section 4.3 for Operations

To ask Barry Bishop of status. Per Barry, this is still awaiting FCC

desires.

Issue 48 - Is there a TTN issue?

Remains open with Walt and Jeff not connecting. The resolution does not

impact the Chicago MSA test, although it may result in subsequent test

script changes later. Walt will attempt to connect with Jeff again.

Nevertheless, this issue will be CLOSED.

Agenda item 2. FCC Guidance document

Background discussion: FCC cam to Brent Struthers looking to provide

input to trial without impacting the very tight schedule. The FCC is not

asking us to do much - it is more of an impact on the report than the

testing.

1. The report should accurately evaluate LRN or other solutions. The

trial will focus on LRN.

2. This is a repeat of many of our internal issues/guidelines. Relative

to multiple database failures, they are looking for multiple LSMS

failures and the effect on switches. Action item 47 (rolling/cascading

overloads) addresses this item. [note that it is referred to as NPAC

databases and they intend it to mean LSMS]. Question centered on this

being destructive testing while live traffic is moving. Dick pointed out

that wording could be put together that discussed the known result of

various multiple failure scenarios and why it wasn t tested. Barry

suggested that the SCP folks provide this wording.

Item (b) discusses switch-based failure scenarios. This wouldn t be done

in a live network either. Optional responses are to develop off-line

test scenarios or provide wording indicating why such testing wasn t

done. Another option is to ask the vendors to provide results of

internal failure scenarios or to refer this item to the Network Test

Committee (NTC). Jim Joerger pointed out that without resolution of the

funding issue, it is highly unlikely that the NTC will do any testing

this year.

Item (c) relates to test conditions and "pre-conditioning" of networks.

We have said that everyone must pre-test and we have allocated

sufficient time before cooperative testing begins (e.g., two months of

in-house soaking in advance of testing). As long as we can run through

all the porting scenarios, we probably addressed the installation piece.

Barry Bishop agreed that appropriate wording could be put together to

meet this FCC need.

3. This addresses an item similar to 2c.

4. This should be covered by the NPAC team(?). The NPAC will not let

them do uploads unless the information specified here is provided. This

will be brought up by Dick at next week s meeting.

5. CLASS, LIDB, 800/888, etc. are all included in the test plan. Once

the SPOC committee decides on the sequencing of tests it should

sufficiently meet this need.

6. Our target is better than 30 days, so meeting this should not be

problematic.

Agenda Item 3. NIIF update; review of test plan

Robin reported that NIIF is doing a cut-and-paste on the test plan and

pulling out interconnection pieces to work on. At the end of that

exercise they will take the inteconnect test plan and the ICC test plan

and keep it in their "living" document list. The first pass has started

and will conclude by the end of next week. Target initial availability

is August, final availability is October.

Agenda Item 4. Operator Services (incl. LIDB)

This week, Carmen began testing various Operator Services/LIDB

scenarios. Essentially, an NPA NXX was opened for portability. Some test

calls were made (0+ dialed calls internal to the network). It worked

(call completed). Using access codes he tried other carriers networks

(AT&T-LD worked; MCI, Sprint failed). The failed problems were related

to gateway screening and those failures successfully completed after

some translations changes. There was some difficulty on some (maybe one)

carrier. This testing is continuing today and the current info is that

the sub-system code was placed in the called party address field and

troubleshooting is on-going. Queries came in and got out and clearly met

the two second time-out criteria. The real purpose of this testing is to

determine if the LIDB address has changed. Alternatively it is testing

the message relay function. This was characterized as regression

testing. Carmen pointed out that time permitting, additional testing

will continue.

Agenda Item 5. Test plan update (matrix)

The issue is what is the minimum set of tests that needs to be run.

Clearly it is dependent upon which services are offered by which

company. In addition, there may be a need to create a basic

feature-by-feature minimum set. Another alternative is to simply test

what can be tested and report on those that are tested.

Walt pointed out that he selected a minimum set based on (1)what he

cannot run in his own lab and (2)what he would already have tested in

the trial [if the test was run once in the trial, it may not be

necessary to run with the next carrier]. Running 911 tests should happen

in all cases where it is appropriate (some areas may not have 911

features available).

SPOC group is working this issue currently.

Agenda Item 6. Number pooling

ICC would like a number pooling (thousands group) plan in place by

August 1. We should be prepared to answer questions surrounding the

effect of number pooling on the existing test plan. Over the last two

days, the Operations group has concentrated on how the flows would

change. We should anticipate a request to test the network before

January 1.

Agenda Item 7. Next Meeting

Next meeting will be July 10 at 350 Orleans, Room 437. July 11 was set

aside for the SPOCs, but Dick will verify the date and find a room. Test

committee will then meet August 22 in Chicago. Perhaps conference calls

could be handled in between. September 11-12, 1997 set aside for

potential next meetings. Conference call for the test team will be on

July 24 1:00 to 3:00 PM CDT.