29 Years of the Digest ... founded August 21, 1981Add this Digest to your personal or   The Telecom Digest for April 02, 2011
====== 29 years of TELECOM Digest -- Founded August 21, 1981 ====== | ||||||||
Telecom and VOIP (Voice over Internet Protocol) Digest for the
Internet. All contents here are copyrighted by Bill Horne and
the individual writers/correspondents. Articles may be used in other
journals or newsgroups, provided the writer's name and the Digest are
included in the fair use quote. By using -any name or email address-
included herein for -any- reason other than responding to an article
herein, you agree to pay a hundred dollars to the recipients of the
email.
Addresses herein are not to be added to any mailing list, nor to be sold or given away without explicit written consent. Chain letters, viruses, porn, spam, and miscellaneous junk are definitely unwelcome. We must fight spam for the same reason we fight crime: not because we are naive enough to believe that we will ever stamp it out, but because we do not want the kind of world that results when no one stands against crime. - Geoffrey Welsh See the bottom of this issue for subscription and archive details and the name of our lawyer, and other stuff of interest. |
Date: Fri, 01 Apr 2011 06:31:32 -0700 From: Sam Spade <sam@coldmail.com> To: telecomdigestmoderator.remove-this@and-this-too.telecom-digest.org. Subject: Re: No-Call List Enforcement In USA: Dead or Dying? Message-ID: <QpudnTbbLf4pTgjQnZ2dnUVZ_q6dnZ2d@giganews.com> Pete Cresswell wrote: > > Since reading this http://tinyurl.com/qhvwrr , I suspect that a > fix will be forthcoming within a year or two max. > > My hope is that said fix doesn't involve something that costs too > much for us peons. > If you believe he is doing anything other than grandstanding...well, enjoy. The FTC doesn't have the staff to change anything.
Date: Fri, 01 Apr 2011 10:30:09 -0700 From: RonTheGuy <not@null.invalid.telecom-digest.org> To: telecomdigestmoderator.remove-this@and-this-too.telecom-digest.org. Subject: Label for PoE-powered device? Message-ID: <not-E916EE.10300901042011@h46.4.82.166.static.ip.windstream.net> What do manufacturers put on their product label for power input specification on a product powered by PoE? Give the max voltage as 57V DC? Show a spec for current? Anything else? Ron
Date: Fri, 1 Apr 2011 09:22:36 -0400 From: "AJB Consulting" <ajbcs@frontier.com> To: telecomdigestmoderator.remove-this@and-this-too.telecom-digest.org. Subject: Re: Does FiOS support rotary phones? Message-ID: <000a01cbf06f$e2a98e30$01fea8c0@dell8100> There seems to be some misconceptions in this thread that need clearing up. I realize this is about three weeks late, but as the saying goes, better late than never. The most important point to remember is that with any modern consumer "box" that provides a POTS interface for the end user, whether or not certain standard phones will work has nothing to do with how the box connects to the service provider. This applies irrespective of the connection type and protocol that your service provider uses between the box and the CO. It could be an ATA [Analog Telephone Adapter] furnished by a VoIP provider, a box from a CATV company, a FiOS ONT [Optical Network Termination], or even an SLT [Single Line Telephone] port on a modern electronic key system. In all of these cases, whatever you dial with your POTS phone to set up a call is digested completely by your local box, which then does whatever it has to do to set up your call. It all comes down to what types of phones the makers of said box decide to support.[1] For the record, FiOS uses a real-time 64 kbps channel[2] for each phone number that appears at the POTS interface connections on the ONT. This channel is just a tiny part of the optical bitstreams between the end user and the CO, and at the CO end, in many cases, it simply goes through a digital cross-connect and presents as a DS0 to an existing 5ESS switch. I don't have access to the written practices that would detail call setup, but more than likely the necessary information is passed on to the same switch much in the same way it would be for a voice channel in an ISDN/PRI [23+D]. The more things change, the more they stay the same. So does the FiOS ONT support rotary-dial phones? That is the million dollar question, and the only way to answer it is to get your mitts on the manufacturer's documentation for the ONT. Earlier FiOS installs in this area used an ONT made by a company whose name escapes me [they were later bought by Tellabs]. More recent installs in this area use an ONT made by Alcatel-Lucent, and here is where you will run into a brick wall. Documentation for end-user Lucent equipment remains readily available under the Alcatel regime, but anything in the carrier equipment line requires a log-in and password, which you can get by having an active service provider account with them. Bill, you probably have much better connections in this area than most of us - perhaps it is time to call in a favor. Here are the footnotes, if the reader can stand any more: [1] The biggest beef most people have with these boxes is that they do not conform to long-established standards for an FXS [POTS] interface. Ringing is the most common complaint, as the boxes seldom provide true 90 VAC sinusoidal current properly imposed on DC loop voltage to enable answer detection. The makers of this equipment either don't know or don't care about the standards, and they wind up reinventing the wheel. Their new wheel often comes out square, which is especially amusing when one considers that there are numerous readily available ASIC chips on the market that could do all of this for them - all they had to do was open a catalog. Other common complaints about these boxes include DC loop current and/or voltage that is not within established standards, sloppy answer [off-hook] detection, lack of CPC support, and so on. [2] Pseudo real-time. It is contained in the ATM data stream, but does not have to go through the gyrations of packetized IP data. Jim Bennett ************************************************** Speaking from a secure undisclosed location.
TELECOM Digest is an electronic journal devoted mostly to telecom- munications topics. It is circulated anywhere there is email, in addition to Usenet, where it appears as the moderated newsgroup 'comp.dcom.telecom'. TELECOM Digest is a not-for-profit, mostly non-commercial educational service offered to the Internet by Bill Horne. All the contents of the Digest are compilation-copyrighted. You may reprint articles in some other media on an occasional basis, but please attribute my work and that of the original author. The Telecom Digest is moderated by Bill Horne.
Contact information: | Bill Horne Telecom Digest 43 Deerfield Road Sharon MA 02067-2301 781-784-7287 bill at horne dot net |
Subscribe: | telecom-request@telecom-digest.org?body=subscribe telecom |
Unsubscribe: | telecom-request@telecom-digest.org?body=unsubscribe telecom |
This Digest is the oldest continuing e-journal about telecomm- unications on the Internet, having been founded in August, 1981 and published continuously since then. Our archives are available for your review/research. We believe we are the oldest e-zine/mailing list on the internet in any category! URL information: http://telecom-digest.org Copyright (C) 2009 TELECOM Digest. All rights reserved. Our attorney is Bill Levant, of Blue Bell, PA. --------------------------------------------------------------- Finally, 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. A suggested donation of fifty dollars per year per reader is considered appropriate. See our address above. Please make at least a single donation to cover the cost of processing your name to the mailing list. 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.