You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   150-154    
 
Author Message
25 new of 154 responses total.
flem
response 125 of 154: Mark Unseen   Sep 18 16:57 UTC 2000

I was supposed to call Ameritech and tell them to drop the two lines (why me?
I'm not entirely sure; that's just how it seemed to happen, eh?), as soon as
someone told me "which ones to drop".  I have no idea what information is
actually necessary (e.g. are there specific phone numbers that I'll have to
tell them, or "lines 12 and 13", or something else entirely?), so.   
  I believe that when people started discussing which phone lines to drop,
we got sidetracked by discussion of whether or not we could drop the ISDN
line(s) as well.  
aruba
response 126 of 154: Mark Unseen   Sep 18 18:10 UTC 2000

You need to tell them the phone numbers to drop.  Probably they should be
the last two numbers in the hunt group.  Scott, what are the last two
numbers in the hunt group?
scott
response 127 of 154: Mark Unseen   Sep 18 23:12 UTC 2000

According to the "phones" command, the last two numbers are 761-9671 and
761-5159.  That's assuming the phones list was updated since the last cut,
but I think it's accurate.
krj
response 128 of 154: Mark Unseen   Sep 19 06:46 UTC 2000

Also, regardless of the outcome of the exploration of future use for 
the ISDN line at the Pumpkin, the ISDN line which is NOT at the Pumpkin
should be disconnected; I don't see any future in which that line is 
used.
janc
response 129 of 154: Mark Unseen   Sep 25 15:29 UTC 2000

New stats.  The previous listing for July was only part of the month.
The first column is number of lines in use, the second is total number of
hours the system had that many lines in use, and the third column is the
percent of the time we had that level of dial-in use.

Usage between Sat Jul  1 00:00:00 2000 and Mon Jul 31 23:59:59 2000
of IP addresses: 204.212.46.132
  0:     246.99         33.20%
  1:     249.12         33.48%
  2:     143.82         19.33%
  3:      68.51          9.21%
  4:      23.88          3.21%
  5:       8.01          1.08%
  6:       2.27           .305%
  7:       0.92           .124%
  8:       0.29           .039%
  9:       0.02           .0027%

Usage between Tue Aug  1 00:00:00 2000 and Thu Aug 31 23:59:59 2000
of IP addresses: 216.93.104.37 216.93.104.36 204.212.46.132
  0:     211.67         28.45%
  1:     266.46         35.81%
  2:     166.04         22.32%
  3:      66.62          8.95%
  4:      23.77          3.12%
  5:       6.54           .879%
  6:       2.32           .312%
  7:       0.29           .0390%
  8:       0.24           .0323%
  9:       0.03           .00403%

Usage between Tue Aug  1 00:00:00 2000 and Mon Sep 25 11:24:51 EDT 2000
of IP addresses: 216.93.104.37 216.93.104.36 204.212.46.132
  0:     215.88         36.86%
  1:     217.57         37.04%
  2:     101.39         17.26%
  3:      38.34          6.52%
  4:      11.02          1.88%
  5:       2.71           .461%
  6:       0.41           .0698%
  7:       0.01           .00170%

I still think 6 lines would be plenty.

I don't know how many we actually have right now.
scott
response 130 of 154: Mark Unseen   Sep 25 15:32 UTC 2000

We have eleven.
spooked
response 131 of 154: Mark Unseen   Sep 25 17:12 UTC 2000

Right, six would be ample.

janc
response 132 of 154: Mark Unseen   Sep 25 17:13 UTC 2000

Did we ever cut the ones we voted to cut?
gelinas
response 133 of 154: Mark Unseen   Sep 26 01:57 UTC 2000

Not if we still have eleven.
eeyore
response 134 of 154: Mark Unseen   Sep 26 05:56 UTC 2000

Well, since Greg was not given the information....(although I think that was
taken care of tonight. :)
flem
response 135 of 154: Mark Unseen   Sep 28 19:26 UTC 2000

I just got off the phone with Ameritech.  I had them drop two dial in lines:
761-9671 and 761-5159, and the four ISDN lines:  761-5416, 761-5676, 761-3590, 
and 761-7066.  
other
response 136 of 154: Mark Unseen   Sep 29 00:10 UTC 2000

What does that save us in monthly phone bills?
aruba
response 137 of 154: Mark Unseen   Sep 29 03:46 UTC 2000

That should save us approximately $135/month.
carson
response 138 of 154: Mark Unseen   Sep 29 04:01 UTC 2000

(awesome.)
dpc
response 139 of 154: Mark Unseen   Oct 11 13:37 UTC 2000

Hm.  It looks like we could actually get by with 4 phone lines
without inconveniencing anyone too much.
keesan
response 140 of 154: Mark Unseen   Nov 13 19:52 UTC 2000

I just got a busy number twice in two minutes a few minute ago.  Waited two
minutes and go through.  This is my first busy number in several months.  I
would not mind getting a busy number once or twice a week.
davel
response 141 of 154: Mark Unseen   Nov 14 15:26 UTC 2000

As long as we're not talking about an hour of redialing that often, yes.
keesan
response 142 of 154: Mark Unseen   Nov 16 18:58 UTC 2000

How many dialin lines do we have now, and might we drop two more?
Could this be discussed at the board meeting?
janc
response 143 of 154: Mark Unseen   Nov 16 19:13 UTC 2000

The last cut was so recent that it would be hard to come up with very
significant statistics for the post-cut period.  I'd wait 6 months before
re-examining it.
keesan
response 144 of 154: Mark Unseen   Nov 16 22:26 UTC 2000

I thought the previous statistics showed that we only need 4 lines most of
the time, and we had cut from 11 to 9.  I dial in up to 10 times a day, maybe
more, and got a busy line on only one occasion since the lines were cut, which
lasted only two minutes.  Around 3-4 pm, an unusually busy time.  What is the
usage (in %) for the busiest hour of the day, for each line?
keesan
response 145 of 154: Mark Unseen   Nov 17 00:59 UTC 2000

Just now (before 8 pm) I had to redial for 30 sec before getting through. 
8 pm is the other busy time of the day, I think.  I could have waited five
minutes instead.  What is the longest other people are willing to wait?
janc
response 146 of 154: Mark Unseen   Nov 17 04:44 UTC 2000

Based on the last statistics, the board decided to cut only two lines.  I
wanted to cut more, but lost out.  If we have no new statistics, why should
the board reconsider?
keesan
response 147 of 154: Mark Unseen   Nov 17 22:54 UTC 2000

Six months of two unnecessary phone lines at $20/line times 2 = $240.
I am asking if anyone analyzed how many minutes a week, or what percentage
of the time between 3-4 and 7-8 pm, the last two lines are in use, and what
the maximum acceptable number of minutes is that people would tolerate getting
a busy signal.  I could tolerate 5 minutes, easily, and have never had more
than 30 sec busy signal.  This is probably much shorter than people are
waiting on the telnet queue.  (How long is the maximum telnet wait?).
keesan
response 148 of 154: Mark Unseen   Nov 17 23:08 UTC 2000

I just calculated that .124% busy equals 12 minutes/week and .305% busy = 30
minutes/week.  These figures were for lines 6 and 7 (before dropping 8 and
9).  If these two lines were used only between 3-4 and 7-8 pm, M-F, 12 minutes
in 10 hours for line 7 is about 2 busy minutes each between 3-4 and 7-8 pm.
It was apparently an accident that I got busy signals at both these times.
Or maybe traffic has gone up a bit and the count should be redone.  Line 6,
using the old numbers, 30 minutes in 10 hours, would be 3 minutes busy out
of 60 between 3-4 or 7-8.  I could easily wait 3 minutes to try again.  Is
there someone who could not?  Does it make sense to pay $20/month for a line
that is used 12 minutes/week (50 minutes a month for $20 - 40 cents/minute).
Please correct my arithmetic if it is off somewhere.

Is it common to wait 3 minutes or longer in the telnet queue?
carson
response 149 of 154: Mark Unseen   Nov 17 23:16 UTC 2000

(depends on the time of day.  early weekend mornings, yes.  other times,
no, not really.  YMMV.)
 0-24   25-49   50-74   75-99   100-124   125-149   150-154    
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss