Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: leichter@lrw.com (LEICHTER-JERRY@CS.YALE.EDU)
Newsgroups: comp.dcom.telecom
Subject: Annoying Intercept Behavior
Message-ID: <9607@accuvax.nwu.edu>
Date: 11 Jul 90 00:00:44 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 21
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 474, Message 6 of 10


Here in Stamford - and in my experience most of Connecticut - we have
to dial 1+7 for calls outside the local calling area, omit the 1 for
calls in it.  Do it the wrong way and you get an intercept.

The oddity is the way the intercept is implemented.  It doesn't take
place immediately after the last digit - not to mention after the
exchange, which is possible.  Instead, you get two or three normal
rings and THEN a long, wordy message telling you exactly what you
should have done.

This is a real time-waster when you are dialing an unfamiliar number,
as you sit there convinced that you've made it through.  I find that a
good fraction of the time, but the time I get the intercept I've
closed the telephone book or put away the business card with the
number on it.  Then I get to start over again.

Why would anyone set up intercepts this way?  Is it done this way
elsewhere?

		-- Jerry