Subject: MIDWEST LNP SCP CALL NOTICE FOR 10/7 AND NOTES
TO: MIDWEST LNP SCP REQUIREMENTS SUBCOMMITTEE
SUBJECT: NOTICE FOR CONFERENCE CALL OCTOBER 7
NOTES FROM STEERING COMMITTEE MEETING OF SEPTEMBER 25
FROM: WAYNE HEINMILLER (847-248-5415 wayne.heinmiller@ameritech.com)
Our next conference call will be 10 AM CDT on Tuesday, October 7,
1997. A call in number will be distributed later. At this time, I
have no specific agenda items for the meeting, and would expect the
call to primarily allow the sharing of information regarding
whatever final rollout schedule is adopted for LNP in Chicago.
NOTES FROM THE ILLINOIS LNP STEERING COMMITTEE MTG 9/25
The start of commercial LNP for Chicago is being delayed a few weeks
to allow correction and confirmation for some items associated with
the NPAC. The carriers have not yet been able to agree on when
these items can expected to be resolved, so a specific start date
has not yet been determined. The carriers expect to determine a new
start date no later than a conference call on 10/1.
There also appears to be some inconsistencies in how each carrier
has implemented support for NPA splits. Apparently NPAC
documentation was not as precise as everyone thought. There will be
an attempt to determine how quickly NPA split functionality can be
corrected, hopefully resulting in identification of the changes
needed no later than 10/1.
The committee determined that any "permissive" arrangements
established in order to perform the trial would expire when the
trial ended. That includes gateway screening changes to allow
passing LIDB messages or other SS7 messaging. So providers may need
to review their existing inter-network agreements to determine if any
changes to those agreements are desirable.
(I pointed out that LNP has two general impacts on SS7 messaging
such as LIDB queries. First, some networks may not have any
agreements with a given provider, and would block any messages from
that provider which they receive as a result of LNP redirection.
Second, some networks may have agreements in place, but may block
messages they receive because those messages arrive over links which
would not normally carry messages from the provider. As a result of
the expiration of the permisive trial arrangments,
carriers/providers need to review their inter-network agreements as
well as inter-network screening to determine if changes are
desirable for LNP.)
The committee also discussed possible target dates for number
pooling for the 847 area code. Feedback from carriers indicated
potential ready dates from 1Q98 through 1Q99. Pooling cannot start
until all carriers are prepared. There appears to be more
willingness to support pooling earlier if carriers can be assured it
will be phased in on a national basis. National carriers are
concerned that widespread, immediate adoption of pooling on a
national basis would overwhelm their LNP resources, which were not
designed for the capacity. Efforts are underway to determine if
their is a way the industry can agree to a phased in approach for
pooling. Everyone is encouraged to continue their efforts to find
ways to resolve roadblocks to number pooling. (I will be pursuing
requests for changes to the NPAC interface as we've discussed with
the NPAC subcommittee.)
UPDATE FROM NPAC SUBCOMMITTEE CALL OF 10/1
The NPAC subcommittee has developed a revised schedule for the start
of commercial availability of LNP in Chicago. They have identified
some details that need to be cleaned up prior to roll-out.
Availability will begin no later than 11/3, and may begin sooner if
the various items get buttoned up sooner.