Slashdot Mirror


Canadian Telco Telus Moves All Call Traffic to the Net

justice0x1 writes "An article on the Tornonto Star about Canada's Telus making a large scale motion to move all call trafic over to IP caught my eye today. 'Telus will become the first dominant phone carrier in North America to make the risky transition, a move much talked about and which Telus will make happen on a dramatic scale.' Since I work in the Telus Internet Service department, it will be interesting to see exactly how this new technology fares. Seems almost premature to me, but I guess it's all or nothing with telecomunications these days; you need to get an edge on the competition somehow. Why not start by moving youre entire long distance network over to IP?"

51 of 250 comments (clear)

  1. Let's Call Mom!!! by yoey · · Score: 4, Insightful

    Hi, mom? How're you doing? All is well wi....

  2. Bandwidth? by Anonymous Coward · · Score: 5, Interesting

    What kind of bandwidth would this require?

    1. Re:Bandwidth? by PerlGuru · · Score: 4, Informative

      I use Vonage VOIP for my home phone and they require 90kbps both ways in their default config. They have an option to reduce the call quality, and thus the size. 90kbs is about 2/3rds the way to standard phone quality comming from cell phone quality, if that makes since to you.

    2. Re:Bandwidth? by AmunRa · · Score: 5, Informative

      In europe, traditional circuit-switched telephone networks use channelised E1s, which basically have 15 64kbit/s data channels, along with a 64kbit/s control channel, giving a 2Mbit/s channel.

      Using H.323 (the main VoIP standard) you can choose from a number of compression codecs, from 32kbits upwards, although there exists a couple of codecs which sound pretty good (coparable to a average analogue phone line) at 64kbit/s, to you can make the transition without effecting you capacity.

      I was involved in some trials here in the UK, and (IIRC) we were using about 90kbits, and that was _crystal clear_ - the thing you most notice is that when no-one is talking, it is actually *silent* - you don't realise it until you try VoIP howe much noise is in a normal analog call.

      This is fact one of the advantages of VoIP, you can have in effect variable bitrate encoding, as if no-one is talking, then you don't have any data to encode!

      --
      " To steal ideas from one person is plagiarism; to steal from many is research. "
    3. Re:Bandwidth? by jcdr · · Score: 4, Informative

      Nope!

      E1 is 30 B channels at 64kbits/s + 1 D channel at 64kbits/s for signalisation plus 1 synchronisation and misc operator stuff at 64kbits/s. So E1 is 32*64k=2048Mbits/s.

      Some operators have services for 10, 12, 15, 20 or 24 channels depending of the offert but this is simply a limit of concurrent B channels open in a 30 B channles capacity E1 line.

    4. Re:Bandwidth? by Citizen+of+Earth · · Score: 2, Interesting

      Pumping data through a CPU do to intensive compression isn't exactly the best way to do this.

      On an Athlon XP2100+ box, I can encode Vorbis files at 9x realtime speed. You could do realtime encoding on 1/9th this amount of 'box'. OTOH, Vorbis is not necessarily optimized for speech.

    5. Re:Bandwidth? by RovingSlug · · Score: 3, Interesting
      the thing you most notice is that when no-one is talking, it is actually *silent* - you don't realise it until you try VoIP howe much noise is in a normal analog call.

      The background white noise in an analog phone call is artificially inserted ("comfort" noise). Studies showed users were not comfortable with a "dead" line, where the static reassures them the connection is still active.

    6. Re:Bandwidth? by atomico · · Score: 2, Informative
      You can take my word for it - they do insert so called 'comfort noise' to avoid having thousands of users hanging because "the line went dead". BTW, I am a telecommunication engineer.


      Try entering the term in Google, I got 540,000 hits.

    7. Re:Bandwidth? by Anonymous Coward · · Score: 2, Informative

      Actually the sample rate is 56kbit/sec on voice calls, which is where the 56k maximum theoretical speed of a modem comes from. 64kbit/sec is a full B channel. In the old days everything telco related was based around B channels (A T1 is 24 B channels for example). Most of the "old" telcos still around are still based on this. The newer companies have to work with it to interoperate but internally their networks probably aren't based on it.
      There's a big difference between desirable internet traffic flow and desirable voice traffic flow though. Voice traffic is sensitive to latency and changes in latency far beyond most internet traffic. Voice phone calls are supposed to be real-time two way conversations, if data arrives "late" in a phone call you may as well just discard it.
      Your minimum overhead is going to be something like (Layer 2 header per pkt + IP Header per pkt + higher protocol headers per pkt) / ( 56kbit/sec * (maximum acceptable one-way latency) ) so if you're willing to accept > 1 second worth of latency in each direction then you can get that down to about 1% overhead, if you're aiming for 1/100th of a second one-way latency you'll have about 85% overhead. These are just minimum latency values attributed to buffering a certain amount of data before sending it - as required for a packet based network - nothing says upstream or lower layer handling wont add more on top of that (and since it takes some finite amount of time to transmit the data it surely will, but hopefully not anything noticable).
      IP isn't designed for this kind of thing at all though. Surely it can carry any data you want it to, but when you're talking about wanting to send data in 30 byte chunks to minimize the latency between the first sample encoding at the source end and decoding at the far end, the IP header is going to contain a lot more information than is practical.
      But hey, if you have piles of money it doesn't matter if you go about things ass-backwards. Just type in "osprey crashes" to google for a good military example!

    8. Re:Bandwidth? by billstewart · · Score: 2, Interesting

      90kbps is 64kbps uncompressed audio with IP overhead. Sure, they can compress it to 6.5kbps and get cellphone-quality speech, but if they don't have to compress it for bandwidth reasons, it simplifies a lot of other things. I'd have expected the IP overhead to be a bit lower, but not a lot lower, and one of the problems with VOIP is that the IP overhead doesn't shrink just because the voice does, because the voice needs to send 100 or more samples per second to sound good, so they're all tinygrams.

      --

      Bill Stewart
      New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    9. Re:Bandwidth? by halbritt · · Score: 2, Interesting

      The encoding traditionally used by telcos (but *not* VOIP) is 64kbps ADPCM for each call. There are compression and silence-suppression technologies that can get this down to around 8kbps per call, however compression isn't something really considered for "carrier-grade" voice service. For a sense of scale, an OC-192 will handle 150,000 voice calls. I know that this isn't the first US carrier to move all of it's long-distance traffic over IP, though it may be the first to publicly do so. It's not too far-fetched really as long as the carriers that do it have their own IP backbones, it's just another form of switching.

    10. Re:Bandwidth? by oh · · Score: 2, Interesting
      Wow. Ogg Vorbis music files encoded at 45-kbps sound very close to the original. I think they need to use some better quality.

      You don't really care how long it takes to encode a music file, and you can compress in chunks as large as you like. What matteres to a telephone conversation is lag, if I say something I don't want to have to wait 10 seconds for a reply. I can't record 10 seonds worth of data, compress it, and send it. I have to record something like 10ms worth (80 samples), compress this, and send it.

      This limits the size of the packets, down to the point that the IP header takes up a substantial portion of the bandwidth. In additon, with only 80 samples, there isn't really much you can work with when compressing.
      --
      Democracy isn't about no one telling you what to do. It's about everyone telling you what to do.
  3. New error messages by wiggys · · Score: 4, Funny

    "Sorry, but your call could not be connected at this time due to a 404 error. Please reconfigure your phone line and try again."

    --

    Sorry, but my karma just ran over your dogma.

    1. Re:New error messages by muonzoo · · Score: 4, Funny
      That's not just funny, it's in the SIP [a common VoIP protocol] spec! :

      RFC 3261 Section 21.4.5 clearly states:

      21.4.5 404 Not Found

      The server has definitive information that the user does not exist at
      the domain specified in the Request-URI. This status is also
      returned if the domain in the Request-URI does not match any of the
      domains handled by the recipient of the request.

      I see them every day at work if I misdial from my Cisco 7960.

      Made me laugh the first time; now it just makes me cry. :-)
  4. And So we move closer to integrated communication by SkArcher · · Score: 5, Interesting

    Turnabout is fair play it seems. No more than 5 years ago, I was using a phone line to access the internet. Soon i'll be using the internet to make telephone calls.

    --

    An infinite number of monkeys will eventually come up with the complete works of /.
  5. Not the public Internet (I hope) by Zarhan · · Score: 4, Insightful

    It should be noted that altough everything is transporter over IP, they are (probably :)) not transferring their voice over public Internet and it is not even connected to Internet in any way.

    It's still a private network, they are just shifting to a more generic and cost-effective infrastructure. So I suppose you still can not slashdot the phone network..

    1. Re:Not the public Internet (I hope) by Realistic_Dragon · · Score: 4, Funny

      So I suppose you still can not slashdot the phone network.

      My sister has been trying to DoS the phone network through overuse for many years now, so far to no effect.

      --
      Beep beep.
    2. Re:Not the public Internet (I hope) by n3k5 · · Score: 4, Informative
      I very much doubt that they'll route calls over the public internet.
      You _doubt_ it, your parent says _probably_ not. Well, they're _definitely_ not connected to the Internet in any way, which becomes apparent if you just read the first few paragrphs of the article. The /. headline says something different, of course. Great job, timothy!
      --
      but what do i know, i'm just a model.
  6. A matter of time by RosCabezas · · Score: 5, Interesting

    In fact it was just a matter of time. At last, telcos are realizing that technology is a helper and not a foe. Probably 3rd generation as designed is not going to generate the expected revenue and some side paths need to be found.

  7. I wonder by mericet · · Score: 3, Interesting

    I wonder how much bandwidth they are going to allocate to a phone call once it's pure VoIP? and will it change according to load? what will be the effect on modem/fax data?

  8. Great! by Anonymous Coward · · Score: 4, Funny

    I used to have to yell at my roommates to get off the phone and stop hogging the phone line.

    Now I'll have to yell at them to get off the phone and stop hogging the bandwidth.

  9. Re:IP != The Net by 8282now · · Score: 5, Informative

    Just because it's VoIP, it doesn't mean it has to flow over the "public" IP network. They can simply point the VoIP over their own network and still see massive savings.

    For the VoIP/PSTN imparied, VoIP traffic can be optimized (that's compressed) down to 8K (or more, but a cost of clarity) as opposed to 56K for traditional circuit switched telephony traffic.
    And yes I have worked with the technology.

  10. not 'to the net' by delmoi · · Score: 3, Interesting

    Dude, using IP dosn't mean they are transfering call trafic over the general internet. I really doubt they are going to give each phone line a real IP address rather then a 'local' one.

    It would be pretty cool if they did. Imagine an RFC standard phone protocol that was implemented on lots of telephone like devices. In conjunction with DHCP you could have an internet phone that worked as simply as a regular phone. And you could talk to anyone with a PC and/or another phone (maybe by typing in the IP address? :P probably not).

    Well, I can dream, can't I? (or is this not that far off? I know you can buy IP phones today, but I don't think that they can work with both the general internet and the general phone system)

    --

    ReadThe ReflectionEngine, a cyberpunk style n
  11. It's worth a try by GMontag · · Score: 2, Insightful

    This method certainly can't make them go out of business any faster than the other Canadian telcos.

  12. Having read a little deeper by SkArcher · · Score: 5, Insightful

    The benefits, however, are enormous and noticeable, particularly on a carrier's balance sheet. Telus stands to substantially lower its operating and capital costs with the new infrastructure, and will be in a position to offer customers new business services that can combine voice, video and data. "We literally have three infrastructures," says Pathak, explaining that separate networks exist today to carry phone calls, Internet and data services, and video. "The goal is to merge into one simple platform.

    So their ultimate plan is to have Video, Phone and Data linked into the same system? An Extreme bandwidth use, but one that would raise some hopes of breaking down the current 'methods of communication' fragmentation and simply leaving us with one single, integrated, communications method.

    Now that raises all sorts of possibilities in terms of remote conferencing, especially as the younger, technically proficient generations move into higher echelons of the decision making process in government and corporations.

    Any ideas on what OS is used to control this?

    --

    An infinite number of monkeys will eventually come up with the complete works of /.
  13. "normal" call ? by Rosco+P.+Coltrane · · Score: 4, Funny

    In fact, the quality of the transmission was so good, so much like being there, that Telus engineers added a bit of noise to make the call sound, well, more normal.

    They should drop calls and overcharge customers too to complete the picture.

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
  14. Having worked for Telus by Frederique+Coq-Bloqu · · Score: 4, Interesting

    a bit outside of Québec City (I no longer work for them), I would say this is a generally good move. Most of the equipment, at least in Québec is shoddy stuff late 1950s. Needs constant maintainence. I can definitely see why they're upgrading.

  15. MPLS by Anonymous Coward · · Score: 2, Interesting

    They're not going to go on general IP network but with a carrier-class MPLS network. Lets see who they will choose for their backbone, Cisco, Juniper or perhaps Chiaro or Hyperchip??

  16. IPv6? by HaloZero · · Score: 2, Interesting

    Will the software used for this transition support IPv6? Will it be BASED on IPv6? I mean, the point of IPv6 is to give us more IP addresses than the initial 256 * 256* 256 * 256, and moving an entire phone network would only make the IP addressing problem worse (if not using v6...), right?

    --
    Informatus Technologicus
  17. The future is convergence by metz2000 · · Score: 2, Interesting

    From what I can see everything is heading toward one device - the PC. The PC of the future, as many of us know, will be compact enough to put on a table top (or under your TV) and will be a compliment to your lounge/living room as it may be well designed and stylish.

    So, what's going to come through this little wonder? Well pretty much everything. People will have wireless digital phones which connect to this 'base unit' via bluetooth or other wireless tech. All this telephone traffic will travel across a VoIP system and additional features will most probably be video links through built-in cams and possibly a text message feature to send info such as telephone numbers or addresses through on-the-fly without having to talk it out loud on the phone.

    Also coming down the high speed net links will be television on demand. No more arial/satellite systems, just pure internet provided media. It could be argued that radio is very much internet based already - I for one have no arial set up for FM signals.

    The international network coupled with a micro-PC in every home is the way of the future. Faster internet backbones will provide a media-rich lifestyle.

  18. Spam by Rosco+P.+Coltrane · · Score: 4, Funny

    By treating voices and video like any other piece of data, such as e-mail

    Soon Canadians will be getting enlarge-your-penis and invest-in-nigeria phone calls.

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
  19. For more info. by AmunRa · · Score: 2, Informative

    The main VoIP standard is H.323 - Check out OpenH323, an open-source implentation of this technology.

    --
    " To steal ideas from one person is plagiarism; to steal from many is research. "
  20. Dude! I got this chick's number! 127.0.0.1! by gatesh8r · · Score: 4, Funny

    I'm going to have to call her later on. She's like, into Lord of the Rings and other geeky stuff. BTW, what's Linux???

    --
    Karma whorin' since 1999
  21. I'm already fully converted... by caffeinex36 · · Score: 2, Informative

    ..I use Vonage for my phone at home. I do not even have a land-line installed in my apartment. I find the features to blow any phone company away, and the price and service is excellent.

    Besides the overall geekness of being totally VoiP, I have had nothing but good experiences with it.

    And I get to have an LA and NY number....
    Rob

    1. Re:I'm already fully converted... by Talez · · Score: 2, Funny

      That's scary.

      You can call Sydney cheaper than I can and I live in Australia!

  22. Goddamnit! by Ryvar · · Score: 2, Funny

    In fact, the quality of the transmission was so good, so much like being there, that Telus engineers added a bit of noise to make the call sound, well, more normal.

    Damnit! Damnit! Damnit!

    I was going to use a modem over VoIP! Curse you, Telus!

  23. IPv6 by Luguber123 · · Score: 2, Insightful

    Are they using IPv6 for the voice transmissions? It sounds like a good idea to me (not beeing a field expert tho..) since there are a lot of QoS features and security features in v6, wich would require a lot of extra hassle with v4.

    Anyways I'm moving as far away from telco business as possible. After 20 years, as a customer, I'm less than satisfied with the 'competitive' pricing of services.

  24. Death of Alaxander Gram Bell's invention by zakezuke · · Score: 4, Interesting

    Remarkably enough, telephone technology hasn't really changed all that much since it's invention. the infrastructure has changed vastly, but for the most part, you can still use a first generation telephone over copper, with the exception of the cellular model. This is probally why it's no great shock to me that mobile phones are the first to actually experiment with adapting.

    My first reaction to this move to tcp/ip based voice communication is great, dispite the fact that the telephone it self has a remarkable level of simplisity to it. Speaker, amp, microphone, even without a touch tone generator most networks i'm familar with still permit the rotery system, a call can be placed by touching wires together in that rythmic fasion.

    So what is there to be gained by TCP/IP transport for telephone use, assuming we are talking about the classic land line as well as the mobile, a great deal i'd say. Fax machines for one thing will no longer be barred by that pesky 9600/14000 bandwidth issue, color faxing can be an option. A "mobile" could in theory be jacked into a land line and calls can be recieved regardless of reception, eliminating the need for features like call forwarding. A push to upgrade to this cheeper form of transport could push the telcos to actually upgrade way out of the way regions to this new digital system, so even Farmer Joe miles away from the CO could get reliable network access. Let alone the boom to the deaf community.. even with present mobile text and instent messaging it has practicaly rendered ye old TDD terminal obsolete.

    But... there is a major downside. It puts control of network access back to the telcos, well not like they don't have it already. We create a dependence on high technology, requiring all homes being essentally wired for network. We also create a dependence on power, not that classic telephone doesn't take a bit of juice, but imagine if everyone's house had additional DA converters, and essentally hubs rather then splitters. Privacy could be made a think of the past, as packet sniffers could be employed to actually track specific people without the physical access that is presently required.

    But I'm leaning more tward the side of the fact that there is just so much crap I want rendered obsolete, and a level of digital intrigration I would like to achieve. I no longer want to be barred by the limits of dialup service being the only thing that can be actived on demand, I want phones to be TCP/IP ready.

    And yes... I want mobile phones to actually provide high speed internet and I want it everywhere! And if this means I can't use my circa 1970's phone that I bought specificly to be compatable with my first acustic(sp) modem and so be it.

    --
    There is no sanctuary. There is no sanctuary. SHUT UP! There is no shut up. There is no shut up.
  25. Re:And So we move closer to integrated communicati by SEWilco · · Score: 4, Funny
    "Dear Sir,

    I am writing this letter to request ISP service from you. After that is completed, I will be able to telephone you to arrange a domain transfer.

    Incidentally, do you know to whom I can write to arrange for water service so I can watch CNN?"

  26. Hold the phone. by FreeLinux · · Score: 5, Informative

    As a few posts have already descibed, VoIP is not the same as voice over the internet. The VoIP that Telus is using is actually being carried over dedicated data circuits which offer, not only high speed (OC-12 +), but also end to end Quality of Service control. Indeed, these dedicated data circuits may well carry some internet traffic as well, but Telus is able to run the voice traffic at a higher priority than the less time sensitive data.

    In fact, this is already being done by several carriers including Sprint, MCI, Intermedia, Verizon and probably others.

    I have also installed numerous private networks utilizing Nortel or Cisco equipment to carry VoIP over dedicated private networks, usually frame-relay WANs. These VoIP calls are 100% reliable and are perfectly clear.

    In two cases standard internet connections (cable, xDSL, frame-relay) were used to carry calls between several different offices in the United States, Canada, Europe and Mexico. These connections are not always as clear as those running on private WANs but, they have proven to be 98% reliable and are indistinguishable from regular land lines, in terms of clarity, 85% of the time.

  27. Re:Bandwidth - ITU recommends G723.1 - 6.3kb/s by fact0r · · Score: 3, Interesting
    VoIP Standards are all made by ITU-T.

    The most widely used VoIP protocol is H.323. H323 allows negotiation of a compression CoDec. The base (worst) codec which must be supported is G.711 (64kb/s - this is what goes down an ISDN line - this is regarded as lossless digital encoding).

    Latency is dealt with by using QoS. I make calls from Australia to Europe through a VoIP carrier at a cost of about 3cents/minute. The round trip delay appears less than 0.2 seconds. The recommended CoDec is G.723.1 which is 5.3 or 6.3 kb/s (switches dependent on complexity I believe). This CoDec gives speech quality better than a mobile network will give you.

    The bandwidth is only required in the direction of speech - when there is silence going the other way the bandwidth drops to near zero (just comfort noise generation and control signals send down the line). Comfort noise generation is done by a funny little algorithm that tells the other end the type of "silence" (static) to produce.

  28. Tornonto by Apostata · · Score: 3, Funny

    Meanwhile, in hockey news, the Ananheim Mighty Ducks face the Newn Jersney Devils.

    (I see the upcoming pot de-regulation is having it's effect)

    --

    This wasn't just plain terrible, this was fancy terrible. This was terrible with raisins in it. - Dorothy Parker
  29. IANALuddite, but... by gobbo · · Score: 2

    you'll get my old black rotary phone with the real metal bells and indestructible hard shiny plastic and nice neck-cradling handset when you pry it from my cold dead hands.

    No electricity? no problem, it still works. Plus, analog has nostalgia value, too!

    Maybe there's a cool mod someone's done for old phones like this so that we can convert them to VOIP...

  30. Re:quality of sound by parc · · Score: 2, Informative

    The article is not technical, and this is pure market speak. What they were adding was probably "comfort noise." Comfort noise is placed in the dead air where you aren't actually sending sound (to save bandwidth).

    Another thing normally added is near-end echo. This is the sound of your own voice piped back at you with reduced volume, something that happens in the standard phone system naturally. People have become so used to hearing the echo that they think something is wrong if they don't get it. Because of this, you see a lot of people yelling at their cell phones.

  31. Re:I guarantee this will fail by EQ · · Score: 3, Informative

    Try learning more modern stuff than whatever antiquated VoIP crap your company was using.

    As an example, I was working with VoIP stuff 3 years ago with Cisco, T-Mobile and Level 3: we had a project that took a GSM signal, put it onto a local (in building only) network, and from there to VoIP and onto the Cisco Call Manager system. This allowed the cell phone to be your internal company phone extension while on campus, but automatically switch back when off campus. We faced many of the same problems you cited but all were solved by the end of the "beta" test.

    Also we deployed a nation-wide softswitch infrastraucture that allowed us to hook Cisco VoIP phones at any point in the network and make toll-quality calls out from the main PBX back in Broomfield. This saved the company from having to drag a copper pair to each and every little regeneration site onthe fiber right of way, which is not an inconsiderable amount of cash when you figure the extent of Level 3's network.

    Update your knowledge base. IP is starting to be picked up now that the private IP networks Like Level 3, Genuity, plus parts of AT&T and Sprint have worked out the problems. Draft Martini (Read the IETF documents) has been delivering standard phone services like ATM and FR over IP for a year. And Level 3, where I used to work, has had an all IP infrastructure for several years now, using the old XCom (Now VIPER) sofswitch. Want to know where those cheap long distance calling cards are coming from? They probably travel over Level 3's all IP network, converting at the edges on the softswitched architecture. And a good percentage of Worldcom/MCI long distance moves on Level 3's all IP network as well.

    Secondly, the VoIP mentioned here is primarily in the backhaul, behind the CO switches (RTFA again!). For Inter and Intra-LATA carriage, VoIP is highly reliable, and much less expensive than the TDM stuff.

    As for the "silence", RTFA. Seriously, they solved this one a long time ago with a little echo back on the reciever side, as well as "comfort noise" from the IP switch. This technique goes back several years.

    Seriously, you need to learn more - and RTFA, because you are "mistaken about a great many thing"....

    --
    Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo! http://goo.gl/J9bkO
  32. Re:IP != The Net by ashitaka · · Score: 2, Informative

    Read my subject again, you know what "!=" means right?

    The article *title* "Canadian Telco Telus Moves All Call Traffic to the Net" implies that Telus will be using the public Internet.

    The *article* says several things but doesn't clearly state for non-technical readers that the network that Telus will be using for this VoIP service is their *private* network. The article talks about the poor quality of previous Internet phone call implementations without qualifying that assertion with something like "but Telus will use their own network instead of the Internet."

    Others have pointed out the same thing. The title is misleading.

    --
    If you don't want to repeat the past, stop living in it.
  33. Re:IP != The Net by esobofh · · Score: 2, Informative

    Indeed, the title is misleading. The traffic will flow over TELUS's national Private IP network which, incidentally, happens to be the fastest optical/IP network in north america end-to-end.

    --

    ----------------------------
    Esobofh - Currently drinking fresh mango juice.
  34. Hell, use the inet for phone today... by ehintz · · Score: 2, Insightful

    I already am. Vonage runs $40/mo for unlimited calling within the US and Canada. I did the math, and found that I could double my DSL upload speeds (which was needed as the 1.5/128k ADSL connection I had was not quite enough upload) and slightly reduce my monthly telco/internet costs. Since I'm on DSL, I still had to keep a landline, but it's the uber cheap one ($13/mo), had I been on cable the savings would've been even better. I'm totally happy with it. I did need to setup queueing on my outbound router to prioritize VOIP (so somebody hammering my webserver wouldn't kill my phone) but on a normal home network the thing would be plug and play. For that matter, if your home servers are low load you probably wouldn't need to bother prioritizing at the router; I found packet loss in testing (having a freind hammer the server while we were on the phone) but it took me 3 weeks before I got around to setting up the router and we never had a problem in actual use. But I was more than happy to have an excuse to play with altq. ;-)

    --
    ehintz
  35. Don't Worry... companies like BELL will ruin it by zaqattack911 · · Score: 2, Interesting

    Why not start by moving youre entire long distance network over to IP?

    Quite simply Large monopoly Telco's have invested large amounts of cash in the already existing (and out of date) telephone network, and would rather blow up the planet than see that change. Have a look at this .

    Bell , AT&T will start whining to governments for compensation or tax immediatly.

    All I'd like to know is when did the government make it a priority to start protecting large corps from the consumers, instead of protecting the consumers from corps.

  36. Internet via VPN by redback · · Score: 2, Interesting

    I assume that eventually they plan to run some kind of IP service to peoples houses, and use VoIP phones. What would be nice if you could use say, some kind of VPN, to get to a internet router, and obtain a public IP.

    Theres your broadband......

  37. Actually you CAN slashdot the PSTN. by Ungrounded+Lightning · · Score: 2, Informative

    So I suppose you still can not slashdot the phone network..

    Actually you CAN slashdot the PSTN (Public Switched Telephone Netowork). And you always could. The equipment is sized to handle the expected peak loads with some slop. But there is nowhere near enough equipment in place to handle every phone being connected to another phone.

    You can slashdot it at several levels. The commonest is the "all-trunks busy" level - where all the routes from the calling phone to the called number (that the switching equipment knows how to use) are busy. In the older exchanges that produced the tones that sounded like a busy signal but twice as fast. Modern stuff gives you a recording.

    You can also tie up all the equipment that gives you a dial tone and collects the digits you dial, by getting enough people on the exchange to try to make calls at once. Usually this just means you wait a second or so for a dial tone - and maybe not even notice it. If it's REALLY severe you might wait seconds, or minutes, and then it is really noticible. But it's also really rare.

    The last time I recall that actually happening where I lived was the Loma Prieta earthquake, and the time before was the assassination of JFK. Before that was at an old relay-based exchange (using line-finders rather than registers) where the line finders didn't time out, and a tornado had shorted out enough lines - which made them look "off-hook" - to busy out all the line-finders that could give my phone a dial tone.

    Again, modern equipment is more informative: When things get hairy the people operating the network can switch it to a mode where, when you take your phone off the hook, it first connects you to a recording asking you to hold off unless it's an emergency, then giving you a delay followed by a fair chance at a dialtone. (I THINK it actually deliberately delays you a bit even if it COULD have given you a dial tone right away, both to throttle you and to give you a chance to hang up if it wasn't urgent.)

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way