**ANNOUNCE** Farewell to Vancouver
Mr. Arlington Hewes
Folks,
I'm sorry to announce that our Vancouver cell has closed. According to mail
I have received from the cell's operator
jac...@repairman.com said:
> Dear Mr. Hewes,
> As per our correspondence last year, the TPC Vancouver cell will be
> disconnected at 2400 Hours on January 2nd, 1998 permanently. Please
> perform the necessary procedures on your server to disable the link to
> the 1604 connection.
> I wish you a happy new year and I thank you and everybody else in the
> group for all the fun I have had.
> Thank you..
We welcome volunteers to reestablish coverage in this lovely region of
Canada - perhaps someone has some pull with the Computing Services folks at
the University of British Columbia? If so, ask them to have a look at
http://www.tpc.int/servers/salespitch.html and get in touch if interested.
Cheers!
-DPN
--
Mr. Arlington Hewes (tpca...@info.tpc.int)
The TPC.INT Subdomain (http://www.tpc.int/)
**************************************************
*** FOR GENERAL INFORMATION ***
*** Mail to tpc...@info.tpc.int ***
*** FOR A LIST OF CURRENT COVERAGE ***
*** Mail to tpcc...@info.tpc.int ***
**************************************************
Jason Currell
How many outgoing phonelines were required for the Vancouver area? Do you
generally have to have long distance access blocked at the phone company
switches or can you do that through the software?
-------------------------------------------------------------
System Administrator for the Vancouver Community Network
Jason Currell | cur...@vcn.bc.ca
voice #: (604)257-3811 | modem #: (604) 257-8778
Mr. Arlington Hewes
>>>>> On Wed, 7 Jan 1998, "JC" == Jason Currell wrote:
JC> How many outgoing phonelines were required for the Vancouver area? Do
JC> you generally have to have long distance access blocked at the phone
JC> company switches or can you do that through the software?
One should be sufficient for quite awhile . . . two should be adequate for ages. We also have another cell coming online in the future (we hope) so it would lighten the load.
The software is, we feel, unspoofable as far as long distance goes. We require the dialstring to be x number of digits, and can do all kinds of regex matching on the dialstring before approving it for dialing, so it should be pretty bulletproof. I would not think long-distance on your line would need to be blocked at all.
I seem to remember we have met - thanks for sticking around and getting interested in what we do! Seems an ideal thing for the freenet to do.