Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!bellcore!texbell!vector!telecom-gateway
From: gmw1@cunixd.cc.columbia.edu (Gabe M Wiener)
Newsgroups: comp.dcom.telecom
Subject: Operator Service
Message-ID: 
Date: 13 Aug 89 03:48:09 GMT
Sender: news@vector.Dallas.TX.US
Organization: Columbia University
Lines: 15
Approved: telecom-request@vector.dallas.tx.us
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@vector.dallas.tx.us
X-TELECOM-Digest: volume 9, issue 292, message 3 of 5

In New York City, I can dial 0 for a New York Tel operator, or 00 for a
long distance operator.  This works both on ESS and on non-ESS exchanges.

However, up at my weekend house in NW Connecticut, dialing 0 or 00 brings
up the SNET operator.  Now my exchange is definitely ESS (I have call
waiting, 3-way calling, etc) though 10XXX codes do _not_ work.

Shouldn't 00 bring up the AT&T operator directly?  Even on ESS and even
on non Equal Access in NYC, the 00 brings up an AT&T operator.   Why is
SNET any different?  Have they not completely separated from AT&T?

-G

P.S.   What is the purpose of the "beep" you hear right before you reach
the operator?