TO: MIDWEST LNP SCP REQUIREMENTS SUBCOMMITTEE

SUBJECT: CONFERENCE CALL TUESDAY 12/2 10 AM CST

FROM: WAYNE HEINMILLER (847-248-5415 wayne.heinmiller@ameritech.com)

Our next conference call will be Tuesday, December 2 at 10 AM CST.

The call in number is 800-708-XXXX and the passcode is XXXXXX.

CHICAGO LNP

Ameritech is currently postponing activation of LNP for the Chicago

area pending regulatory action relating to cost recovery. As of the

Steering Committee meeting last week, there was no indication of

when the next "favorable alignment" might occur. I believe the

other Chicago carriers have decided they are also postponing their

LNP activation for Chicago until Ameritech is ready to begin.

POOLING

If the NPAC subcommittee's latest work on pooling gets posted to the

web by that time, we'll review their work as it impacts SMS/SCP

needs for pooling. It was to be finalized on 11/20, but has not yet

been posted. (There are changes to the material posted prior to

11/20.) I understand they've agreed to include a pooling indicator

and explicit range capabilities for a potential late May '98 release

of the NPAC interface. They've also addressed defining a

relationship between pooled and ported information. (I'm not sure

of the relationship they've agreed to support, yet.) They have also

addressed the need to continue to support the "old" interface for

those systems that may not be ready to support the changes by May.

Check "www.ported.com" to see if the material has been posted yet.

(It will include process flows as agreed by both the NPAC and

Operations subcommittees, and the documentation for the changes to

the NPAC interface.)

The Steering Committee discussed the possibility of beginning

pooling for NPA 847 perhaps in March '98 on a manual basis,

following with a more automated process in June following the new

release for the NPAC interface. There was a general feeling that

using a manual process for 2-3 months in advance of the new NPAC

capabilites would be about everyone's limit.

REQUIREMENTS UPDATE

I'm continuing to update the errata sheet to document the changes

we've agreed to the last issue of the requirements document during

the past year. (The last errata sheet was distributed in the

spring.) I'm not sure it will get distributed sufficiently in

advance of our call to be able to discuss it on Tuesday. So a

review of the errata sheet will be performed at our next conference

call (12/16, see below).

STANDARDS

T1S1 will be using the Midwest requirements documents as one of the

starting points for their work. Besides distributing the SCP

requirements errata sheet to this distribution list, I will also ask

Barry to post it to Ported.Com. That way T1S1 participants should

be able to access it prior to their January '98 meeting.

LIDB QUERY ROUTING

The LIDB user's group sponsored by Bellcore will be discussing the

LIDB query routing issue in January. (This is the issue that LNP

routing may route LIDB queries for ported customers to networks that

may not be expecting to process messages from the originating

source, causing the messages to be rejected.) This forum includes

LIDB providers, LIDB vendors, SS7 hub networks, and some (but not

all) LIDB users. I believe they will be informing USTA this will be

an agenda item in January. They have not yet determined whether

this will be on the agenda of their regularly scheduled meeting

(week of 1/12) or whether it will be the topic of a separate meeting

the following week (week of 1/19).

NPA SPLIT PROCESSING

The additional/revised NPAC requirements for NPA split processing

have been posted to Ported.Com. You should review them for possible

impacts on your products and operations.

OTHER UPDATES FROM THE STEERING COMMITTEE

- RFP for interim number pooling administrator was released 11/18,

and has also been posted to Ported.Com.

- There has been discussion about whether a switch needs an LRN

assigned for each rate center it serves. This is expected to be

addressed through the T1S1 LNP activity.

- Local Service Provider ID issues are also expected to be addresed

through T1S1.

COMMUNICATIONS

Our datacom staff has promised an update to Ameritech's mail gateway

in the next couple of weeks. They have indicated it will impact my

external e-mail capability, but they won't tell me how until after

the upgrade. I'm hoping the impact will be minimal, but I wanted to

warn everyone in advance.

FUTURE CONFERENCE CALLS

We will have a conference call on Tuesday, December 16 at 10 AM

CST. I will distribute a call in number in a later message.