Return-Path: <swillcox@MIT.EDU>
Received: from central-city-carrier-station.mit.edu by po11.mit.edu (8.9.2/4.7) id SAA06853; Thu, 22 Aug 2002 18:25:07 -0400 (EDT)
Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.7.71])
	by central-city-carrier-station.mit.edu (8.9.2/8.9.2) with ESMTP id SAA08527
	for <nutso-flaming-pikans@MIT.EDU>; Thu, 22 Aug 2002 18:24:13 -0400 (EDT)
Received: from mass-toolpike.mit.edu (MASS-TOOLPIKE.MIT.EDU [18.7.16.71])
	by manawatu-mail-centre.mit.edu (8.9.2/8.9.2) with ESMTP id SAA05640
	for <nutso-flaming-pikans@mit.edu>; Thu, 22 Aug 2002 18:24:13 -0400 (EDT)
Received: (from swillcox@localhost) by mass-toolpike.mit.edu (8.9.3)
	id SAA00305; Thu, 22 Aug 2002 18:24:13 -0400 (EDT)
Message-Id: <200208222224.SAA00305@mass-toolpike.mit.edu>
To: nutso-flaming-pikans@MIT.EDU
Subject: phones 
Date: Thu, 22 Aug 2002 18:24:13 -0400
From: "J. Scott Willcox" <swillcox@MIT.EDU>


I think it is high time for pika to be the first MIT ILG with a
communicator system. Some of us made plans for one back in the day
based on small FM base stations in each room. Wireless tech has come a
long way since then, so how hard can it really be?
Scott

------- Forwarded Message

Return-Path: <nathanw@MIT.EDU>
Received: from central-city-carrier-station.mit.edu by po12.mit.edu (8.9.2/4.7) id OAA24365; Thu, 22 Aug 2002 14:23:18 -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 OAA07224
	for <in-house-pikans@mit.edu>; Thu, 22 Aug 2002 14:23:07 -0400 (EDT)
Received: from contents-vnder-pressvre.mit.edu (CONTENTS-VNDER-PRESSVRE.MIT.EDU [18.7.16.67])
	by melbourne-city-street.mit.edu (8.9.2/8.9.2) with ESMTP id OAA12701
	for <in-house-pikans@MIT.EDU>; Thu, 22 Aug 2002 14:23:07 -0400 (EDT)
Received: (from nathanw@localhost) by contents-vnder-pressvre.mit.edu (8.9.3)
	id OAA18645; Thu, 22 Aug 2002 14:23:07 -0400 (EDT)
To: in-house-pikans@mit.edu
Subject: Re: Phone system.
References: <200208221738.NAA07397@buzzword-bingo.mit.edu>
From: nathanw@MIT.EDU (Nathan J. Williams)
Date: 22 Aug 2002 14:23:07 -0400
In-Reply-To: <200208221738.NAA07397@buzzword-bingo.mit.edu>
Message-ID: <mtufzx6iwhg.fsf@contents-vnder-pressvre.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


So, it sounds like people want two different things:

1) "Ring-to-room", so that someone in their room can pick up the call
   for them if the murph and dining room are empty and/or VERY LAME.

2) voicemail, so that people can get messages in case of lameness or
   house emptiness or simply not being there.

I don't know what the capabilites of the present system are (I sort of
miss Merlin, myself), but I don't think (1) is very useful: it fails
when you're in the loo, computer room, roofdeck, workbench, whatever;
it requires maintaining the room -> person mapping, which is both
annoying to maintain and, as Elaine mentions, possibly more revealing
than people want. 

Therefore, I'd suggest just doing (2), and having numbers that are
assigned to people for the duration of their stay at pika. The
downside is that people can still miss calls in realtime when the
people downstairs are lame, and also have to manually check for
messages - but unless I've missed something, the house hasn't been
rewired with digital phones in any room, so this would be necessary
anyway. It's also more like the way other phone systems in the world
work.

If the system is flexible enough and the number-space large enough,
there could be a range of numbers that rings to rooms, and another
range that goes to no real phones but just to personal voicemail; I
would then leave it at individual residents' discretion to explain how
to do ring-to-room to their potential callers.

        - Nathan

------- End of Forwarded Message

