Return-Path: <mrios@MIT.EDU>
Received: from central-city-carrier-station.mit.edu by po11.mit.edu (8.9.2/4.7) id MAA04981; Thu, 22 Aug 2002 12:57:35 -0400 (EDT)
Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])
	by central-city-carrier-station.mit.edu (8.9.2/8.9.2) with ESMTP id MAA25843;
	Thu, 22 Aug 2002 12:56:40 -0400 (EDT)
Received: from 12-248-0-18.client.attbi.com (12-248-0-18.client.attbi.com [12.248.0.18])
	by melbourne-city-street.mit.edu (8.9.2/8.9.2) with ESMTP id MAA04282;
	Thu, 22 Aug 2002 12:56:39 -0400 (EDT)
Date: Thu, 22 Aug 2002 12:56:39 -0400
Subject: Re: Grills and phones
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
Cc: msiverd@mit.edu, scs@eskimo.com, in-house-pikans@mit.edu,
        housecorp@mit.edu
To: "Jamie Browning" <camipco@hotmail.com>
From: Marc Rios <mrios@MIT.EDU>
In-Reply-To: <F40n81V0OzPeDWtpA6j0001ac93@hotmail.com>
Message-Id: <2081DD1C-B5F0-11D6-BA5F-000393828C0A@mit.edu>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.482)

my family members think I hate them because the ratio of messages placed 
to messages received is abysmal. I've also lost calls from employers and 
such. so I am a big fan of phone system reform. I don't know how the 
phone system works or how it is programmed, but it sounds like it is 
pretty flexible.

I'd really prefer a system that indexes by name. tEp has a system that 
dials room by room, but I often have no clue about who lives in what 
room. When the inevitable happens and I am forced to dial the operator, 
some cranky guy answers the phone and he "doesn't know where mim is 
living either". This is what the suggested implementation would do at 
pika, I reckon. A message telling who lives where would also be kind of 
annoying and confusing to the people who aren't acquainted to rooms with 
names like "the lobe". There will be 31 names to listen to.

if not a system that indexes by name, we could all have numerical 
extensions that we will keep the entire time we live at pika. when 
moving day comes around, the ynfcc could change the extension 
assignments to be specific to room. Would this be too difficult? 
Changing the phone system could be a houseduty like anything else.

does this sound reasonable?

summary (I look back and see a confused and not too readable email):
the system doesn't work well
it would be nice to have voicemail indexed by name without an enormous 
message
this could be a houseduty
am I missing any details?



On Thursday, August 22, 2002, at 12:26 PM, Jamie Browning wrote:

>
> I think what we can manage is a pick-up message listing who's in which 
> room. Heck, Fenway manages that. So the extentions fit the rooms, the 
> system doesn't need to be reprogramed, just the intro message needs to 
> be re-recorded. This would be no more difficult than say relabelling 
> the mail boxes and making the list for the peg board.
>
> To answer Steve's question - my problem with the phone system is that 
> it requires people to do a job that a machine can do better. Ned Ludd 
> would be most upset if he wasn't imaginary. Advantage two, it eats 
> telemarketers, and even more annoying those prerecorded message 
> telemarketers and somewhere between the two in annoying, all those 
> empty calls we've been recieving.
>
> The British police spent a good decade chasing Ned Ludd around the 
> country, only to find out that he was entirely fictional. That's my 
> Luddite anecdote for the day.
>
> Cheers
> Jamie
>
>
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos: 
> http://photos.msn.com/support/worldwide.aspx
>

