home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 19
/
CD_ASCQ_19_010295.iso
/
vrac
/
tc14_382.zip
/
TC14-382.TXT
< prev
Wrap
Text File
|
1994-10-03
|
28KB
|
541 lines
TELECOM Digest Fri, 30 Sep 94 15:19:00 CDT Volume 14 : Issue
382
Inside This Issue: Editor: Patrick A.
Townson
T1<->23 or 24 BRI Equipment? (Bob Ames)
Switch to Sprint Check/ Must Keep Them 160 Days (D. Castillo)
EDI Billing (Rajiv Gupta)
What Is # Called? (Wes Leatherock)
MF Digit Grabber Wanted (Paul Cook)
RI Installs Speed-Bumps For the Information Superhighway (Michael
Deignan)
UDI vs RDI in ISDN (psyche@metronet.com)
Internet en Mexico (Robert L. McMillin)
Revenue Sharing Between Operators in a Network (Sharad Ketan)
Help CCITT 16kb/s LD-CELP G728 (Ya-di Lin)
UC Berkeley Short Courses on Broadband Communications (Harvey
Stern)
Call For Papers: Malaysian Communications Conference (Mazlan
Abbas)
Need Amp to Boost DTMF Strength (htcink@teleport.com)
Zmodem for Sparc, no XWindows (Ed Martini)
Help Needed With Meridian 9216 (Florence M. Hurley)
TELECOM Digest is an electronic journal devoted mostly but not
exclusively to telecommunications topics. It is circulated anywhere
there is email, in addition to various telecom forums on a variety of
public service systems and networks including Compuserve and America
On Line. It is also gatewayed to Usenet where it appears as the
moderated
newsgroup 'comp.dcom.telecom'.
Subscriptions are available at no charge to qualified organizations
and individual readers. Write and tell us how you qualify:
* telecom-request@eecs.nwu.edu *
The Digest is edited, published and compilation-copyrighted by Patrick
Townson of Skokie, Illinois USA. You can reach us by postal mail, fax
or phone at:
9457-D Niles Center Road
Skokie, IL USA 60076
Phone: 708-329-0571
Fax: 708-329-0572
** Article submission address only: telecom@eecs.nwu.edu **
Our archives are located at lcs.mit.edu and are available by using
anonymous ftp. The archives can also be accessed using our email
information service. For a copy of a helpful file explaining how to
use the information service, just ask.
**********************************************************************
*
* TELECOM Digest is partially funded by a grant from the
*
* International Telecommunication Union (ITU) in Geneva, Switzerland
*
* under the aegis of its Telecom Information Exchange Services (TIES)
*
* project. Views expressed herein should not be construed as
represent-*
* ing views of the ITU.
*
**********************************************************************
*
Additionally, the Digest is funded by gifts from generous readers such
as yourself who provide funding in amounts deemed appropriate. Your
help
is important and appreciated.
All opinions expressed herein are deemed to be those of the author.
Any
organizations listed are for identification purposes only and messages
should not be considered any official expression by the organization.
----------------------------------------------------------------------
From: bob@ccnet.com (Bob Ames)
Subject: T1<->23 or 24 BRI Equipment?
Date: 30 Sep 1994 10:37:39 -0700
Organization: Creative Computer Solutions
What is available to connect two remote offices via T1?
Ideally, I'd like to use a T1 on each end and provide:
*) Intercom service,
*) TCP/IP traffic (Ethernet),
*) (One/Several?) ISDN S/T or U lines. I'd like to be able to use
ISDN phones on one end and on the other end connect to the
Intercom system or to the LD Company via POTS or ISDN. Or to
use, say, a Waverunner on one side and get thru the T1 to the
main office, and then routed into the Ethernet on the other side.
*) Anything else ISDN provides, like FAX.
Do I need a PBX for all of this? Certainly some kind of switch-like
routing seems necessary.
Perhaps just a device which converts T1 into 24 ISDN B channels,
and looks like an ISDN switch and provides, say, some S/T jacks.
How much traffic can fit on an S/T? For example, can I put all 24 B
channels on the S/T bus concurrently without degradation or failure?
(I doubt it)
Bob Ames
UNIX & Telecom Administrator
Creative Computer Solutions
bob@ccnet.com <<address change<< -or- [soon] bob@rush.com
------------------------------
From: castillo@unm.edu (D. Castillo)
Subject: Switch to Sprint Check/ Must Keep Them 160 Days
Date: 30 Sep 1994 11:42:23 -0600
Organization: University of New Mexico, Albuquerque
I just got one of those $50 "cash this and Sprint will be your LD
company." checks. I had gotten one from ATT about one month before,
and cashed that one, planning to switch back to MCI as soon as I was
switched to ATT. I carefully read all the small print on the ATT
check, and it was just standard stuff.
Now this Sprint check has in fine print under the endorsement line "I
agree to remain with Spring for a minimum of 180 days". Is this
legal? I was under the impression that no long distance company could
force you to keep them as your carrier. I want to cash this check as
reimbursement for having to watch Candice Bergen over and over again,
and then switch back to MCI. Is there any (legal) way they can go
after me if I cash it and switch to MCI anyway? Once the check is
cashed, they can't take their $50 back, so what are they going to do?
Sue me? (what's the number for the FCC folks?)
Any input/experiences would be appreciated!
David bcastillo@hydra.unm.edu
[TELECOM Digest Editor's Note: They are not forcing you to use them
as a carrier or keep them any certain period of time. They are saying
if you AGREE to remain that period of time then you can have the money
in exchange for your AGREEMENT. Yes, there is a legal way they can
'go after you' if you switch carriers after accepting their money and
agreeing to their contract (as shown by your signature): they can sue
you for violation of your contract with them. Easiest thing in the
world. Now, will they in fact sue you for fifty dollars? No probably
not. Most deadbeats and con-artists don't get sued for that small an
amount; they just get put on a list of people to not deal with again.
Sprint can list you with credit reporting agencies as a person who
does
not keep his word. It is perfectly legal in business to require some
minimum period of time under which the parties are obligated as part
of the deal. Telcos are no exception to this. AT&T and MCI both have
customers getting special deals in exchange for their agreement to
some period of time the agreement will be in effect, etc.
Where, in the past, the 'agree to service, cash a check, immediatly
switch service' scam has been marginally legal has been in the absence
of a minimum period of service agreement as part of the deal. It looks
like Sprint has wised up. In the past here, we have discussed also
the illegality of tampering with the endorsement on the back of the
check, i.e. scratching out any references to agreements to change,
putting down phalse telephone numbers in an effort to decieve the
carrier,
etc. I would point out that if you erase or render illegible the
reference to the 160 day minimum period required then you have a few
more problems than that of dead-beating simple; now you've got a
federal
rap to deal with also, that of mail fraud and bank fraud. You
certainly
have the right to strike out that requirement and return the check *to
the party who sent it to you* asking that the terms be re-negotiated
in your favor, but you do not have the right to cash the check
deliberatly
knowing that you have no intention of living up to the contract.
And what's this about the FCC? You actually want their number so you
can complain about Sprint? You think the FCC is going to tell you its
okay to defraud a long distance carrier and commit mail fraud and bank
fraud in the process? If I were you, under the circumstances, I would
want to keep my distance from the FCC. Should Sprint choose to file a
complaint about you and the others who pull this scam, the FCC might
make certain recommendations to the Justice Department, if you get my
drift ...
Sounds to me like the carriers have found a new way to combat this
form of petty larceny by requiring six month or longer contracts as
part
of the deal. But congratulations David, yours was the funniest letter
I
have recieved this week. Too bad you lose. PAT]
------------------------------
Date: Thu, 29 Sep 94 23:25:27 PDT
From: qdov01::rajiv@zpovc.enet.dec.com
Subject: EDI Billing
Hi,
I am looking for info on EDI Billing; what structure is followed etc.
Can anyone help me with inputs and if possible details of exsisting
service providersoffering distributed EDI services over multiple
PRMDs.
Rajiv Gupta
Manager - Telecom
Digital Equipment (India) Limited
Tel - ++91-11-3715324/5/6
FAX - ++91-11-3322399
Email rajiv@qdov01.enet.dec.com
------------------------------
From: Wes.Leatherock@f2001.n147.z1.fidonet.org (Wes Leatherock)
Date: 30 Sep 94 07:16:52 -0500
Subject: What Is # Called?
Organization: FidoNet Nameserver/Gateway
[TELECOM Digest Editor's Note: Where were these people when we covered
this topic completely in the Digest about five years ago in a special
issue dealing with the 'Octothorpe'? PAT]
-=> Quoting Patrick Hoepfner hoepfner@haiti.gsfc.nasa.gov <=-
PH> In article <779663044snz@bigbear.demon.co.uk>,
PH> Susan@bigbear.demon.co.uk wrote:
> In article <Cw3DG7.LA1@ncrcae.ColumbiaSC.NCR.COM>
> Craig.Williamson@ColumbiaSC.NCR.COM "Craig Williamson"
writes:
> > >Rattlesnake Stu (whitmore@tahoma.cwu.edu) wrote:
> > >: -] >The airlines call it a "Cross of Lorraine". I know not
why.
> > >What's wrong with octothorpe?
> > Well that works except that many people would look at you and
say
> > "Huh?" I would think that you could call it the number sign
since it
> > used for that also.
PH> I agree. But another problem is that takes to long to say.
When
PH> calling out a Un*x regular expression how many times do you hear
people
PH> say "bang" rather than "Exclamation Point". I think the same
goes for
PH> "octothorpe" or "Cross of Lorraine" versus something like
"pound". And
PH> since Un*x permeates the net (for better or worse) it is in more
common
PH> usage that other "national" languages here. And besides,
"octothorpe"
PH> doesn't even show up in my dictionary. How many people are
going to
PH> know what it is?
> I always call '#' Hash. Isn't that what it is?
While those reading this newsgroup undoubtedly are very Unix
literate, etc., much of the world is not. Every system I have ever
called
with a voice response unit, such as those used to route calls to
departments
or extensions, banks' systems that allow you to get your balance,
lists
of transactions, etc., and various other functions, always call it the
pound sign.
I am pretty well resigned to calling it the pound sign
because,
after all, I rarely have occasion to use any word to describe it on
the
computer (I simply hit the key or read the symbol), but I often have
occasion to use voice response units.
... [text deleted] ...
PH> .... But
PH> whenever I see the * symbol I think of the mark left by a bug on
a
PH> car's windshield! Once it gets in your mind it is kind of hard
to
PH> forget it.
That symbol is always called "star" in voice response units
I
have listened to.
As far as the exclamation point goes, it does not occur on
voice response units because there is no key for it on a touch tone
telephone, so the only time it has to be called anything is when you
are talking to another computer user. So "bang" is as good as
anything there. ("Bang" is not limited to Unix users; MS-DOS users
call it that, too.)
(But if you're talking to a writer, editor, printer,
typesetter,
etc., you'd better call it an exclamation point. They don't
understand
"bang".)
Wes Leatherock
------------------------------
Date: Fri, 30 Sep 94 12:25:00 EST
From: Proctor & Associates <0003991080@mcimail.com>
Subject: MF Digit Grabber Wanted
I'm looking for a hand held MF Digit Grabber, a device that can
display MF (not DTMF) digits monitored on a trunk.
Can anyone point me to a manufacturer?
Paul Cook 206-881-7000
Proctor & Associates MCI Mail 399-1080
15050 NE 36th St. fax: 206-885-3282
Redmond, WA 98052-5378 3991080@mcimail.com
------------------------------
From: md@pstc3.pstc.brown.edu (Michael P. Deignan)
Subject: RI Installs Speed-Bumps For the Information Superhighway
Date: 30 Sep 1994 16:28:16 GMT
Organization: Population Studies & Training Center
Here's the latest from our fine RI legislators:
General Laws Pertaining to Telecommunication Licensing
RIGL 5-69 Withstanding the exceptions contained in section 5-69-7 of
the general laws of the state of RI -- only licensed
telelcommunications
contractors, licensed telecommunications system technicians, and
licensed telecommunications system installers shall engage in, or
design, install, alter, service, or test telecommunication systems in
the state of RI.
Categories requiring licensure are as follows:
Data communications
Telephony
Video Communications
Sound
A "grandfather period" is in effect from July 12, 1994 until January
12, 1995, after that date all applicants for licensing must pass a
written examination.
I guess you have to be licensed to sell modems in computer stores now.
MD
The best way for Bill Clinton to keep his legal fees down is to keep
his pants zipped up.
------------------------------
Date: Thu, 29 Sep 1994 23:00:26 -0500
From: perpetual psycheness <psyche@metronet.com>
Subject: UDI vs RDI in ISDN
Organization: Texas Metronet, Internet for the Individual 214-705-
2901 (info)
In the world of ISDN, what exactly does UDI and RDI mean? And when
would a person know which one to use? (e.g. you try making a UDI call
and then realize that it doesn't work, so then you try RDI? What kind
of indications does the network use to determine what to do?)
I think that UDI is supposed to be a 64kbps clear channel xmission
(and I think you can have an RDI call over a trunk conditioned for
UDI). And I think that RDI means that the data is restricted in the
sense that you can't have some number of contiguous 0's, which
effectively reduces the maximum bit rate to 56kbps, right? But then,
could you try sending data at 64kbps for an RDI call or is one of the
bits for each channel used to keep sync (I'm assuming this is over T1
type trunks for RDI; I guess E1 type trunks don't have this problem
and are 64kbps clear channel trunks by nature?).
But, 64kbps or 56kbps doesn't necessarily mean UDI and RDI,
respectively,
does it?
And how does rate adaption come into the picture? Is it possible to
have 9600bps data stream rate adapted up to 56kbps for RDI? or up to
64kbps for UDI? Is V.120 or V.110 common in the U.S.? What is
commonly used overseas? What are the advantages of V.120 over V.110
or are there not any?
A lot of questions... ;)
Thanks for any information you can provide....
------------------------------
Date: Fri, 30 Sep 94 09:31 PDT
From: rlm@helen.surfcty.com (Robert L. McMillin)
Subject: Internet en Mexico
Perhaps of some interest to the readers of this forum. I've heard of
a few people wanting Internet access across the border. Here's one
provider.
------- Start of forwarded message -------
From: marior@nic.cerf.net (Lic. Silvia V. Vargas Gutierrez)
Newsgroups: la.forsale
Subject: INTERNET EN MEXICO
Date: 29 Sep 1994 15:13:32 PST
Organization: CERFnet Dial n' CERF Customer
Solo una breve nota para notificar a todo el m?_ µL ≈ ε ▒ 2 : ? D j w | é è Å ò £ ƒ Ñ ½ » ╢ ┐ ├ ╬ ╥ ╒ █ ▀ π College, DGi'sDav idIntrod@ucing