Received: from MIT-Multics.ARPA by buit1.bu.edu (3.2/4.7) id AA19386; Mon, 15 Jun 87 22:32:58 EDT Date: Mon, 15 Jun 87 22:22 EDT From: "Roger A. Roach" Subject: TELECOM Digest V7 #12 To: telecom-request@BUIT1.BU.EDU Message-Id: <870616022252.952149@MIT-Multics.ARPA> Forum-Transaction: [0381] in the >site>arpa_mail_dir>Telecom meeting Transaction-Entered-By: Network_Server.Daemon@MIT-Multics.ARPA Transaction-Entered-Date: 6 Jun 87 14:10 EDT Status: RO From: jsol@buit1.bu.edu@buita TELECOM Digest Sat, 6 Jun 87 13:23:45 EDT Volume 7 : Issue 12 Today's Topics: Administrivia re:help!!! DMS100 Nurse, Get Me A Telephone phonevision Maryland phone prefixes Horror stories wanted ---------------------------------------------------------------------- Date: Thu, 4 Jun 87 19:12:00 EDT From: jsol@buit1.bu.edu To: telecom Subject: Administrivia I am using an experimental delivery mechanism for TELECOM now. I have in place a "second queue", specially for TELECOM. It takes a quick two line modification to sendmail itself, and some configuration hacking to do it. I did this because bu-cs (our mail gateway) was overloaded by TELECOM distributions, so I made a system that I could move around from site to site as the needs change and as the load changes (if we really lose I can have my workstation deliver the digest). The incoming mailboxes, telecom and telecom-request will always be at BUIT1.BU.EDU (unless we change the host name). There are some folks who have "copyrighted" their submissions. I am going to return unsubmitted any message that is copyrighted because TELECOM is in the public domain and in order for it to remain a valuable asset to the community, it must remain so. I don't want to get involved with the legal issues of copyrighted material. Note that also, any material that comes from the AP or UPI newswire will not be submitted either. This policy is consistent with my previous notes about message content. If you announce the latest batch of "illegal sprint codes" I will not publish that either, in fact that is the main reason why TELECOM is a moderated digest. I think we have pretty much settled down from the move. We still get duplicates, but I suspect that this is being tracked down and will slowly become a non-issue. I will continue to the best of my ability weed out the duplicates. ------------------------------ Date: 04-Jun-1987 1823 From: lippis%delni.DEC@decwrl.DEC.COM (Nick Lippis DS Strategic Planning) To: telecom@xx.lcs.mit.edu Subject: re:help!!! DMS100 From: DELNI::LIPPIS "Nick Lippis DS Strategic Planning" 8-MAY-1987 10:37 To: RHEA::DECWRL::"telecom@xx.lcs.mit.edu",LIPPIS Subj: re: help!!! DMS100 From: TELCOM::MCMILLAN 8-MAY-1987 09:53 To: DELNI::LIPPIS When we (DEC) had problems in MKO our problems mostly were with intra SL-100 calls and local CO calls. We found that the SL-100 was hitting the data sets with too high a level and the modems (DF124 & DF112 but not DF03) were having their receiver circuitry saturated. This is due to a diifference in design between modems. We also had some local CO problems. But for the most part our long distance data calls were not any more of a problem than they were before. Now if these people have put in some new carriers to service their long distance service (e.g. T-spans) they may have different problems than they had previously. It is difficult to answer your question, we don't have much detail (i.e. what type modems we talking about, how is your paddata table set-up, what did you have before DMS, what was changed with DMS install, etc., etc.) George ------------------------------ Date: Fri, 5 Jun 87 13:01:20 EDT From: "Michael A. Patton" Subject: Nurse, Get Me A Telephone To: TELECOM@XX.LCS.MIT.EDU Cc: MAP@AI.AI.MIT.EDU The following item appears in the Business Notes section of the Time magazine dated June 8, 1987. It appears with a photograph captioned "In hospitals, these devices make money" and which shows what appears to be a standard cheap one-piece phone being plugged into a modular jack by a patient (you can tell by the wrist band ID (which is readable). New Products: Nurse, Get Me A Telephone Disposable razors have long been a consumer staple, and throwaway cameras are a new photographic fad. Now the latest items to use and lose are telephones. Several companies, including Mini-Phone, Diversified Communications and International Connectors, are selling an estimated 100,000 lightweight, disposable phones a year, and the market is growing fast. The best customers are not individuals but hospitals, which sell the phones to patients as a moneymaking venture. Health-care institutions pay a manufacturer about $9 a phone, then charge patients about $12 to use the instrument during their stay. And since many patients formerly walked off with standard-issue phones (average price: $75), the theft of a disposable phone is less costly. Says Kendall Gallagher, a Mini-Phone vice president: ``A patient confronted with a hospital bill might feel he's entitled to everything in the room, including the phone.'' Philadelphia's Mercy Catholic Medical Center estimates that it saves between $50,000 and $75,000 a year by installing the discardable devices. Indeed, they have proved so popular that throw-away phones will soon be sold in the hospital's gift shop--at 30% over cost. ------------------------------ From: SPGDCM%UCBCMSA.Berkeley.EDU@berkeley.edu Date: Fri, 05 Jun 87 14:12:33 PDT To: telecom@buit1.bu.edu Subject: phonevision MSG:FROM: SPGDCM --UCBCMSA TO: NETWORK --NETWORK 06/05/87 14:12:31 To: NETWORK --NETWORK Network Address From: Doug Mosher Title: MVS/Tandem Systems Manager (415)642-5823 Office: Evans 257, Univ. of California, Berkeley, CA 94720 Subject: phonevision to: telecom@buit1.bu.edu Phonevision (TV pic + audio phones) may hit us from a slightly different angle. A recent brochure from Datapoint notes their addition of MINX to their Starbuilder network architecture. MINX adds what they call "voice and full-motion video" to PC communication networks. It appears that you add a Datapoint monitor-camera combination to some sort of IBM PC; presumably the same monitor is used at other times for high quality color graphic monitor use. I have no idea what quality; certainly some teleconferencing video is limited scan, like 2 per second or whatever; their term "full-motion" is interesting. It seems to be a contest as more features are added to one's telephone and networked pc workstation, until they meet in the middle. (But then at that point you'll have TWO of them on every desk....) Remembering also that the Datapoint co. stimulated the whole pc business in the first place in about 1975 by their chip activity and the Intel 8004, 8008... Thanks, Doug phonevision ------------------------------ Date: Sat, 6 Jun 87 3:50:46 EDT From: Carl Moore (VLD/VMB) To: telecom@BRL.ARPA Subject: Maryland phone prefixes Area code 301 here (202 also useable near DC). There are some hints that prefixes are in short supply in Maryland. I checked with the operator just now and got 286 Berwyn and 878 Fort Ritchie. 286 had been listed in older directories as Clarksville (since Clarksville has 531 for Columbia service and 988 for Ellicott City service--531 local to Balt. city and 988 for Balt. metro area service--you wonder what now appears on the pay phones in Clarksville). 878 does appear in the Md. suburban direc- tory as Silver Spring (Fort Ritchie is far outside DC area); some older sour- ces have 878 as Fort Ritchie (Balt. City service). 369 is listed as Laurel (Berwyn service, which is to DC metro). 703-369 is at Manassas, Va., immediately adjacent to the calling area from DC proper. (There already is 301-490 at Laurel, Md. and 703-490 at Woodbridge, Va.) 738 is listed at Rockville, in the DC area. Previously, there was no 301- 738, but there's a 738 at Ridgely, W. Va., across the Potomac from, and local to, Cumberland, Md., causing me to wonder if it was "protected"; if that 738 is still there, you can now call 738-xxxx from Cumberland to Ridgely (W.Va.) and 1-738-xxxx from Cumberland to Rockville. ------------------------------ Date: Sat, 6 Jun 87 08:33:28 EDT From: Simson L. Garfinkel To: telecom@buit1.bu.edu Subject: Horror stories wanted I am currently gathering research data (ie: stories) for horror-experiences with equal access and hotel PBX's. That is, I am collecting stories of people who have tried to use the carrier of their choice while staying at hotels and have found out that they have no choice and must instead use the carrier the hotel has chosen. Please send your story to simsong@media-lab.mit.edu Your story may be used in a class-action law suit against hotel operators. Please include your full name, address, and phone number. Thanks.. ...simson ------------------------------ End of TELECOM Digest *********************