home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!cs.utexas.edu!sun-barr!lll-winken!telecom-request
- From: birchall@pilot.njin.net (Shag)
- Newsgroups: comp.dcom.telecom
- Subject: Rutgers Exchange-Changing Mayhem
- Message-ID: <telecom13.19.1@eecs.nwu.edu>
- Date: 11 Jan 93 22:16:32 GMT
- Sender: Telecom@eecs.nwu.edu
- Organization: Screaming in Digital, the Queensryche Digest
- Lines: 64
- Approved: Telecom@eecs.nwu.edu
- X-Submissions-To: telecom@eecs.nwu.edu
- X-Administrivia-To: telecom-request@eecs.nwu.edu
- X-Telecom-Digest: Volume 13, Issue 19, Message 1 of 10
-
- Rutgers University has an outlying campus in Camden, NJ. The campus
- is in exchange 609-757, with some businesses. Since that exchange has
- become full, the campus is being moved to a new exchange, 609-225,
- which went into service on Friday (1/8/93).
-
- Banners to this effect were placed on the campus dialins early this
- week.
-
- Within a day, several users of a public system at Rutgers had left
- posts saying that they would no longer be able to call in for free,
- because NJ Bell had told them the new exchange wasn't local to them.
-
- Naturally, since the "localness" of a call is based on the distance
- between CO's (at least in NJ), and the CO's were quite obviously right
- where they'd always been, this caused a lot of confusion for the rest
- of us, who were quite certain it would be a free call, as always.
-
- It turned out that a scenario like this was being repeatedly carried
- out:
-
- User calls the operator to ask about 225.
- Operator keys 225 into the computer.
- Since 609-225 doesn't _exist_ yet, the computer decides that
- they must (of course) mean 908-225, which is some 60 miles
- away (and, coincidentally, a local call from a _different_
- Rutgers campus).
- Operator tells user that it's not local.
- User panics.
-
- When I called NJ Bell, and explained to the operator that it was a
- Rutgers campus changing exchanges, the operator's response was, "Oh, I
- remember when they did that up here in New Brunswick, it'll still be
- local."
-
- Convincing all the users who had been told by NJ Bell that it _wasn't_
- local was a bit of a challenge, though!
-
- When I mentioned this to a friend in Rutgers Telecom (T.P. Brisco), he
- pointed out another bit of trivia:
-
- "I understand when we split from 908-932 to 908-932 and 908-445,
- that originally NJB proposed that we take the newly available
- 809 exchange (instead of 445). We rescinded that proposal on
- the grounds that a phone number like 908-809-xxxx would lead to
- too many typographical errors, and confusion with the newly
- minted 908 area code. Maybe we should've asked for 923 instead
- of 445?"
-
- T.P. also posted a followup message mentioning that people had better
- specify 609-225 when they called the operator.
-
- I think all the users have caught onto the idea now, but there's bound
- to be a few who stop calling in (particularly people from outside
- Rutgers who just dial in to use the public system). Of course, those
- few who continue believing it's a toll call after all our explaining
- are probably modem-incompetent anyway.
-
-
- Shag
- birchall@pilot.njin.net, shag@glia.biostr.washington.edu, birchall@njin.bitnet
- Operator of ShagNet - Rutgers/NJIN dialup access for Burlington County, NJ
- Happy and informative user of a PPI 14400 FaxModem and GeoWorks Pro
- Editor of the Queensryche E-mail Digest - "Screaming in Digital"
-