Path: utzoo!attcan!uunet!umich!accuvax.nwu.edu!nucsrl!telecom-request
From: ehopper@ehpcb.wlk.com (Ed Hopper)
Newsgroups: comp.dcom.telecom
Subject: Re: Another Problem With Centrex
Message-ID: <14108@accuvax.nwu.edu>
Date: 28 Oct 90 16:24:30 GMT
Sender: news@accuvax.nwu.edu
Organization: Ed Hopper's BBS - Houston, Texas 713-997-7575
Lines: 16
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 771, Message 10 of 11


Here's another Centrex problem I ran into once.  Downtown Phoenix,
Arizona was heavily Centrexed at one time.  Phoenix Main CO had a ton
of Centrexes working in it including major banks and other firms.

My customer was in another business.  One day, the TCM tried to make a
toll call and got fast busy intercept.  She dialed 0 to be connected
to the Centrex console.  She asked to be patched to the WATS line.
The operator (i.e., the company employee at the console, not the telco
operator) asked her for her departmental accounting code.  "What do
you mean by that?" she asked.  "Well, " the operator replied, "Every
XYZ Bank department has an accounting code."

Somehow, in all of the mass of translation changes that occured each
day in Phoenix Main, someone screwed up and put a Company X extension
in the Centrex of Company Y.