Slashdot Mirror


Industry-Standard VOIP Phone Using All Free Software

Ralf Ackermann writes: "Voice over IP on a HardPhone running Linux and just using Open Source software became real. We have sucessfully installed and tested (interoperability with Cisco 7960 as well as Pingtel xPressa in an environment with a partysip SIP registrar and proxy) the linphone SIP phone on a StrongARM based TuxScreen. Here is the link describing the steps for others to use the setup as well: TuxScreen running SIP. All the infos for setting up a comparable installation can be found on the URL, please also feel free to ask or drop opinions. Many thanks to the linphone developers as well as to my student Florian Winterstein (for working on a console linphonec version). The setup (on a StrongARM system) is well suited for PDA (iPAQ) or wearable environments as well."

16 of 138 comments (clear)

  1. What about SNOM? by DragonWyatt · · Score: 4, Interesting

    Check this out for another linux-based VoIP, standards-compliant (both SIP *and* H323) phone.

    It's been out for quite awhile, over a year. My company is a reseller. They're cheap (~ $199 each) and they rock.

    --
    Don't sweat the petty things. But do pet the sweaty things.
    1. Re:What about SNOM? by DragonWyatt · · Score: 3, Informative

      ...is there plugin or module of some sort included for encryption? If not, is it easy to tunnel through ssh? It seems to me that a VoIP telephone directory could also serve the public key (or fingerprint at least).
      Nothing that I know of, but that's an awesome idea. It would probably require a new extension (well, codec).

      The way we've solved that problem to date is with VPNs, which incidentally solve other problems, such as QOS.

      --
      Don't sweat the petty things. But do pet the sweaty things.
    2. Re:What about SNOM? by glitch! · · Score: 3, Funny

      "Hey, Pinkie! Are you pondering what I'm pondering?"

      "Well, I think so, Brain. But how can we launch a VoIP phone directory with just a couple of servers and a database? I mean (NARF!) even before we add the public key fingerprints and web-of-trust links, we are talking about gigabytes! And we're just a couple of mice!"

      --
      A dingo ate my sig...
  2. Xeyes by exceed · · Score: 3, Funny

    They just -had- to include the Xeyes in the screenshot.

    --

    void women (int money, time_t time);
  3. Re:SIP by Wesley+Felter · · Score: 3, Informative

    Most of the SIP phones I've seen (like the Cisco and Pingtel ones mentioned in the article) cost as much as a low-end PC, so maybe open source SIP software can help to bring down the cost of SIP phones in the future.

    And there's also the hack value. :-)

  4. One step closer... by Justen · · Score: 3, Interesting

    The company I work for has been looking at VoIP for several months now. Since we have several offices across the country, it would be very advantageous, technologically, for us to use VoIP for the end-user phones, rather than the hodge-podge of systems we use today.

    Unfortunately, the prohibiting factor has been the cost of the phones themselves. The cost for an actual system is within reason, but some VoIP telephones run into the $700 range.

    At this pricepoint, it seems much more affordable and reasonable. And while the GUI would need work to make it dummy-friendly, we have no shortage of graphics designers and programmers who could make that work.

    One step closer to VoIP from beginning to end makes me happy. And I know it'd make our CFO happy, too. =)

    jrbd

  5. Civil rights restored? by heretic108 · · Score: 3, Funny

    Just mix in a few 1000 digit primes.
    Chop fish into 128 pieces, add and blow.
    Simmer and stir, and allow 1-3 secs for CPU to cool.
    Talk when done.

    --
    -- In the beginning was the WORD, and the WORD was UNSIGNED, and the main(){} was without form and void...
  6. Why so low market penetration? by peterdaly · · Score: 3, Interesting

    I do not understand why IP phones
    a) have so low market penetration
    b) cost so much
    -- I know part of the problem with a is b.

    What I think really is needed is a low cost, high quality server system for one of these systems. Based on what little research I have done, it costs almost as much, if not more, for hardware for a small office system as it would to get a real small PBX like phone system.

    I don't think a phone really needs a 9" LCD screen, or whatever was in the screen shot, but the "Java Phone" from the other company has a screen size perfect for the company phone directory. That I think could be the "killer app" for these things.

    Anyway, anyone know of low cost PBX software (if that is even what is is called in the IP phone world)? Open Source, under a BSD like license would be cool, and lower the barrier to market entry for companies wanting to roll a system like this out. Of course, cards to hook up to a POTS connection would also be needed. Voicemail over the web, via shoutcast or something would rock. I havn't listened to my voicemail at work in 3 months. With a better interface, I may stop refusing to use it.

    -Pete

    1. Re:Why so low market penetration? by rjch · · Score: 3, Funny

      Unfortunately, the reason is all too clear.

      a) VoIP phones have such a low market penetration because...
      b) VoIP phones cost so much because...
      a) VoIP phones have such a low market penetration because...
      b) VoIP phones cost so much because...
      a) VoIP phones have such a low market penetration because...
      b) VoIP phones cost so much because...
      a) VoIP phones have such a low market penetration because...
      b) VoIP phones cost so much because...

      ...and so on and so forth...

  7. Open source IP PBX software by Wesley+Felter · · Score: 3, Informative
  8. The next step by FueledByRamen · · Score: 4, Interesting

    This is fine for intraoffice communication, but what about the real world? I think that a solution for connection VoIP -> POTS could be easy, with a little knowledge of Linux drivers.

    Get an older box (P2 400 or so), with plenty of PCI slots, and preferrably an onboard NIC also. Get some Winmodems equal to the # of pci slots.

    WinModems, even in all of their Microsoft-sponsored godless evil towards open source platforms, are basically A/D and D/A converters hooked to a phone jack. It should be relatively simple to talk (no pun intended) to them in software and use one as an interface to POTS. It has all of the neccesary hardware, and writing a sound driver for it shouldn't be too difficult. A brand of WinModem with fairly standard hardware could be decided on by the implementer, and drivers written for that. (Winmodems? Standard? ...)

    Client software with available source code could be modified to use those, as well as control the phone-line functions. Just run an instance per WinModem.

    Honestly, I think that this could work, and it would be a great hack to accomplish. Anyone fancy a go at it?

    --
    Every cloud has a silver lining (except for the mushroom shaped ones, which have a lining of Iridium & Strontium 90)
    1. Re:The next step by elandal · · Score: 3, Interesting

      I think that'd be pretty inefficient. Rather, get a card that talks to PRI. Don't know of any such cards, but they're very likely to exist. And if they don't exist, find a small engineering shop nearby and ask what would it take to put one together.

      Think about it.. A box with six PCI slots and mobo-NIC using six WinModems could handle six phone lines - old analog lines at that. While a single PRI-card could handle 30 lines, and considering that each ISDN line is just 64000bps (8000 samples at 8bits per second - if I remember correctly), it doesn't really all that much computing power, so a single PC should easily handle it.

      Of course a small shop doesn't need 30 phone lines, and could do with the WinModem-based setup, and those that need can get the VoIP from the telco, not needing their own VoIP-POTS conversion.

  9. Open-source speech coding by jmv · · Score: 5, Informative

    (shameless plug) Take a look at Speex, an open-source, patent-free speech codec (Speex is to speech what Vorbis is to music). Speex should soon be available in Linphone too!

  10. FYI by Cyberdeck · · Score: 4, Interesting
    Just a couple of points I'd like to comment on.
    Open Source VoIP and telephony is tracked at http://www.linuxtelephony.org.


    VoIP hardware (PCI cards) is IIRC $79, gateways are $179, drivers have been in the kernel since (again IIRC) 2.2.16. http://www.quicknet.net.


    VoIP in the U.S. is almost pointless because the PSTN is too good. No one wants near perfect when perfect is cheap and easy. In the third world, if you can get a phone circuit it averages $1.27 per minute, whereas VoIP through a hop-off provider like Net2Phone (http://www.net2phone.com) runs average about $0.23 per minute or less. Straight IP to IP (like across a VPN from company branch to branch) is just the cost of the ISP (usually flat rate). So VoIP cafes are a popular way for the non-super-rich and powerful to make calls to their relatives in the first world.


    Personally, the VoIP calls I have made have an almost imperceptible latency problem and sounded *far* better than any GSM call I have ever heard. Then again, these calls were during business hours so net congestion was not an issue for me.


    The Ogg Vorbis has a low bit rate mode that is useful for VoIP telephony, and is grossly better than GSM to my ear.


    Finally, VoIP is used by the big players here in the US. Qwest and Sprint use VoIP in preference to ATM due to cost of the equipment (Bits per second/price of hardware. IP is more efficient than ATM due to less overhead). Any cross-country call is VoIP nowadays.


    Just my two bits.


    -C

    1. Re:FYI by Sycraft-fu · · Score: 3, Informative

      Cox (tha cable company) seems to disagree with you. They receantly told us (as in the people I work with) that they'd installed their las PBX, they were going all VoIP now.

      End users will start wanting VoIP too. For one thing other providers, like cable companies, will be able to offer it where they can't offer PSTN service. As with all competition, this should give lower prices and more features.

      Speaking of features, VoIP has plenty of cool ones. I really like the Cisco phones (other probably have it too, they are jsut what we tried) ability to be logged in to. You log into a phone, it acquires your number and all your preferences.

      However where it will probably be the biggest winner is for bussinesses. Whenever we setup a remote site they have to have enough T1s to cover all the phone lines they need plus T1s for data. With VoIP, we could elimante a bunch of those since with PSTN you have to have a B channel for every phoneline and with VoIP you need only enough bandwidth to cover your peak line usage. These palces never hit 100% usage and probably rarely hit even 30%, hence all that overhead can be eliminated. It also would simply things on our cable plan. We'd only need fibre to a building, then all vocie and data would run over that.

      Personally I think that VoIP is sort of a slow inevitability. IT won't happen overnight, but it makes so much ecenomic sense that we'll migrate totally to it eventually.

  11. Re:Phone companies had 50+ years to become efficie by demaria · · Score: 3, Insightful

    How often does your Internet connection go down? How often does your router or Ethernet switch crash? Do you ever get a guarenteed or consistant data and latency rate?

    Now how often do your telephone systems crash? How often does the quality of the call degrade or drop during the call?

    Traditional phone systems are consistant, rock solid stable, and can handle a large user base.