Return-Path: <msiverd@MIT.EDU>
Received: from pacific-carrier-annex.mit.edu by po11.mit.edu (8.9.2/4.7) id NAA26580; Thu, 22 Aug 2002 13:47:27 -0400 (EDT)
Received: from figaro.mit.edu (FIGARO.MIT.EDU [18.214.0.96])
	by pacific-carrier-annex.mit.edu (8.9.2/8.9.2) with SMTP id NAA25390
	for <in-house-pikans@MIT.EDU>; Thu, 22 Aug 2002 13:46:33 -0400 (EDT)
Received: (qmail 15957 invoked from network); 22 Aug 2002 17:46:32 -0000
Received: from unknown (HELO FIGARO.MIT.EDU) (18.214.0.96)
  by figaro.mit.edu with SMTP; 22 Aug 2002 17:46:32 -0000
Date: Thu, 22 Aug 2002 13:46:32 -0400 (EDT)
From: "Michael 'Indy' Siverd" <msiverd@MIT.EDU>
To: Jamie Browning <camipco@hotmail.com>, Marc Rios <mrios@mit.edu>
cc: scs@eskimo.com, Of Cabbages and Kings <in-house-pikans@mit.edu>
Subject: Re: Grills and phones
In-Reply-To: <2081DD1C-B5F0-11D6-BA5F-000393828C0A@mit.edu>
Message-ID: <Pine.LNX.4.44.0208221323330.15719-100000@figaro.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 22 Aug 2002, 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.

Good idea.  Very good idea.  I approve.  Give this man a cigar.

On Thu, 22 Aug 2002, Marc Rios wrote:

> names like "the lobe". There will be 31 names to listen to.

Don't make the message the default.

"Hello, you have reached pika.  If know your party's extension you may
dial it now.  If you don't, dial 0 to hear the name listing.  Dial 1
to smash the patriarchy.  Dial 2 to get bent..."

> 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?

No, this is does not.  This means the system would have to be
reprogrammed three times a year.  Reprogramming any PBX system is
difficult, confusing, tedious and often unsuccessful work.  It makes
the grease trap look like a dream job.  I have administratively
brushed elbows with about 10 different PBX systems.  The only one that
was remotely userfriendly cost $12,000 and uses ethernet phones*.

The reason that we threw out Merlin (the old system) was that it had
failure states that we couldn't debug because no one knew how to run
the system any longer.  The blessed pikans that are upgrading the
Panasonic system will spend many frustrating hours trying to figure
out all the proprietary bullshit works.  Don't curse future pikans
into having to repeatedly maintain this useless knowledge.

Mike

*I'm referring to 3Com's NBX, which is one of the coolest new corporate
infrastructure toys that I have seen in a while.

-- 
Mike Siverd -------------- "What is science -----
                --------- without gadgetry?" ---------
                     ------- Vernor Vinge ------- msiverd@alum.mit.edu

