Slashdot Mirror


FCC Preparing Transition To VoIP Telephone Network

mantis2009 writes "The US Federal Communications Commission (FCC) published a request for public comment (PDF) on an upcoming transition from the decades-old circuit-based Public Switched Telephone Network to a new system run entirely with Voice over Internet Protocol (VoIP) technology. This is perhaps the most serious indication to date that the legacy telephone system will, in the near future, reach the end of its life. This public commenting phase represents a very early stage in what will undoubtedly be a very complex transition that makes this year's bumpy switch from analog to digital television look relatively easy."

5 of 250 comments (clear)

  1. How unfortunate... by Cornwallis · · Score: 3, Interesting

    POTS is and has been stable and secure.

    VOIP... not and never will be.

  2. Re:Come on Google, Give us wi-fi Now! by Trepidity · · Score: 3, Interesting

    Indeed--- as a result, even the poster children of truck shipping, UPS/FedEx, have moved much of their cross-country shipping to rail. If you order something FedEx to Texas from the Northeast, for example, chances are it'll make a stop in Hutchins, Texas.

  3. Re:Dial-up is all there is some places... by tverbeek · · Score: 3, Interesting

    DSL isn't IP over voice. Your typical ADSL configuration is IP running on the same copper alongside voice (or more properly, POTS). It can also be run on copper without POTS (sometimes called "naked DSL"), but the Bells don't like that because it means letting people drop their landlines.

    --
    http://alternatives.rzero.com/
  4. Re:Dial-up is all there is some places... by natehoy · · Score: 3, Interesting

    Paragraph 1 of the attached PDF:

    In the American Recovery and Reinvestment Act of 2009 (“Recovery Act”), Congress directed
    the Commission to create a national broadband plan by February 17, 2010, that seeks to “ensure that all
    people of the United States have access to broadband capability and establish[es] benchmarks for
    meeting that goal.”1 Among other things, the Commission is to provide “an analysis of the most effective
    and efficient mechanism for ensuring broadband access by all people of the United States”2 and “a
    detailed strategy for achieving affordability of such service and maximum utilization of broadband
    infrastructure and service by the public.”

    In other words, they are looking to take your "no broadband available" location and make it a "broadband available" location. At the same time, they are looking to make the transition as cost-effective as possible so they will run whatever wires it takes to give you broadband but at the same time they are looking to eliminate duplicate services (running a nationwide-to-every-American PSTN network *AND* a nationwide-to-every-American Broadband Internet connection). They may even be able to use your existing copper to give you a good Internet connection.

    Needless to say, but I'll say it anyway, any conversion of your actual home telephone to VoIP would occur (if it ever did at all) well AFTER you had sufficient high-speed Internet to support it. The FCC isn't going to convert everyone to VoIP today, disconnect massive numbers of remote customers who lack broadband, then figure out how to connect to all the outlying areas later.

    In fact, I imagine a lot of what they are going to do is sponsor/mandate DSL implementations, including some sort of repeater technology to break the "local loop distance" barrier and give every American household that has a POTS phone line today access to DSL tomorrow.

    There's a very good chance your existing telco will still be allowed to use the voice portion of your copper to send you POTS telephone service just like you are used to today, though many of them will probably want to become pure-play Internet/DSL providers and give you a VoIP box for your phone (but most will probably make that an Analog adapter so you can still use your existing phone) - that way they can use the entire available frequency band on your copper wires to give you the best Internet speed possible, rather than having to have data in one set of frequencies and voice in another. It also greatly simplifies the gear they have to maintain.

    --
    "This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
  5. Wonder what bit rate? by chrysrobyn · · Score: 3, Interesting

    I wonder what bit rate we can push through the copper at most houses in rural America? My father-in-law's old house used to get very bad static on the line when it rained, but voice was still audible. Would this VOIP be capable of service, or does that house require new wiring? Anything requiring a lot of people to change the wires in their walls is going to face some serious problems. I bet new hardware in the field could get 64kbit or maybe 128kbit digital without much problem. If you're not worried about a computer talking on the line at the same time, that is way more than sufficient. Since the FCC solicitation seems to suggest they're using this as a way to force wider broadband deployment, 256kbit might be the minimum for a connection intended to share with a computer, although I'd hesitate to call that "broadband".

    I bet we could help with the reliability of VOIP by putting cheap NiMH batteries in each VOIP device (one per house, at the pedestal? or each device needs its own?). Enough capacity to last a few hours on standby and maybe 15 or 20 minutes of talk time would cover emergencies.

    I think it would be very interesting to be on a technical committee to write a new standard to cover bidirectional communication on low quality twisted pair. There would be interesting coupling challenges with using one wire for send and the other for receive, but using a current sense methodology on a differential signal has its own ugliness too. It would be cheating to take turns every 10-100ms using a training sequence, but there would be power and signal benefits to weigh against the increase in latency and cut in available bandwidth (and if each device gets its own CODEC, having more than 3 people on the phone may have ludicrous latencies).