Date: Sun, 30 Aug 1992 13:32:00 GMT
From: deej@cbnewsf.cb.att.com (david.g.lewis)
Newsgroups: comp.dcom.telecom
Subject: Re: 800 Portability
Organization: AT&T
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 12, Issue 669, Message 5 of 9

In article <telecom12.661.6@eecs.nwu.edu> wah@zach.fit.edu (Bill
Huttig) writes:

> I was just wondering about the 800 portability area ... will this mean
> that all 800 exchanges will be come portable at once? or will they be
> phased in?

It's phased, but not the way you're thinking.  At some point in time,
LECs will begin doing SCP (database) queries of 800 numbers in
parallel with six-digit translations in switches; these queries will
do six-digit translations in the SCP.  At first, these queries will
not be used for call processing, just to test the system.  After some
soak period, the query responses will begin to be used for call
processing and the six-digit translations in the switches will be
deactivated.  After some additional soak period, the SCPs will begin
doing ten-digit translations (instead of six-digit translations).  At
this point, "800 number portability" is available for all 800-NXXs.

> Will every possible exchange become avaiable?

I believe so, save for some which may be reserved for testing or for
network use.

> Will the residential user be able to switch carriers just as easily as
> a large company?
> Who will control the number space and be reponsiable for routing
> problems?

I believe the bid for 800 DBA (Database Administrator) is still open,
but I'm not sure.  The 800 DBA will effectively control the 800 number
space, because the 800 DBA is the organization which updates the
database.  I don't know if the upstream information flows (customer ->
800 DBA) have been well-defined yet.  (For that matter, I don't know
how well-defined the downstream information flows -- 800 DBA -> 800
SMSs -> 800 SCPs -- are ... but given the organizations involved, I
have a little more confidence in that area than in the upstream
area...)

As to responsibility for routing problems, that's an interesting
question.  Issues of incorrect routing will have to be resolved by the
originating LEC, the 800 DBA, the customer, and any and all involved
800 service providers.  This is one of the operational issues that is
critical to the success of 800 number portability, and probably one of
the ones that some companies (among which my employer is one) have
been insisting must be well-defined before 800 NP is implemented.

> I assume that the customer could have different carriers at different
> times of day and location along with multi termination points ... (I
> would hate to have to write that database).

Bellcore calls these "vertical services"; I believe the plan is that
they are a "phase 2" implementation of the 800 database service.

Disclaimer 1: This information is drawn from memory of another AT&T person's
presentation on the 800 number portability implementation plan.  I accept
full responsibility for any errors... is there anyone out there, say, from
Bellcore SS7 Project Management who might be able to correct any of them?

Disclaimer 2: My views, not AT&T's, etc., etc.


David G Lewis      AT&T Bell Laboratories
david.g.lewis@att.com or !att!houxa!deej     Switching & ISDN Implementation