Slashdot Mirror


Cisco's Wi-Fi Phone

Forbes.com has a quick look at Wi-Fi-enabled VOIP phone. If a company deploys it in more than one location you can take the phone with you, and it acts just like the phone on your desk. Calls across the country or potentially across the ocean can be as free as a call across the office. There's also plans to incorporate support for wireless phone networks.

33 of 134 comments (clear)

  1. More on a previous /. news post... by Chicane-UK · · Score: 3, Informative

    Information on the release date, and other info was posted on this /. posting from a two weeks ago.

    --
    "Hey! Unless this is a nude love-in, get the hell off my property!!"
  2. Wireless phone networks? by antiher0 · · Score: 2, Funny

    Phones without cords? What is this world coming to?

  3. Dupe. by E1ven · · Score: 3, Funny

    I wonder if it's compatible with this phone?

    -Colin

    --
    Colin Davis
  4. This is cool! by sipmeister · · Score: 4, Interesting

    Finally the time has come for affordable IP phones (as Cisco announced a $130 desktop IP phone as well). The technology to make all this useful has been developed over the last couple of years, and as much as this is being touted for the enterprise, it will impact the consumer market as well. I'm already using a Cisco 7960 hooked up to my DSL, using a SIP enabled router (Intertex IX66) to call people all over the world (for free!).

  5. VOIP by camken · · Score: 2, Insightful

    I for one welcome the day that VoIP can be a reality,
    but let's face it, with the ammount of data that it requires, a WiFi enabled VoIP call would just eat up the bandwidth that others need to use to do their work. let's focus on bringing sellular technology to the IP network, rather than the other way around.

    --
    Moo.
    1. Re:VOIP by HeadbangerSmurf · · Score: 2, Interesting

      Amount of data? A g.711 call requires about 80Kbps of data when there is data to be transmitted. That is, if you're not talking there's nothing there to send. Also, last time I checked, when I'm working on a project or surfing the web, there's a bunch of time in there where I'm not transmitting or receiving anything on my machine. Unless I'm on a porn downloading spree I don't see how this phone is going to impact any of the work I'm doing. What surprises me the most is that this technology has been out for a few years and people are just now getting excited over this. I set up my first system last summer using one Call Manager to run four offices, three of which were connected by 384Kbps lines. Even then you could unplug your phone and go to another office where it would re-register and work just like normal. The only downside I can see with any of this is that the phones are prohibitively expensive. 7960s are $450 or so each! The 7910s are $300+ and they are (or were) the bottom end. What's REALLY cool is that you can run a key system out of a Cisco router now. IP Telephony Services on a 1751 will allow you to run 24 phones with at least 4 outgoing lines. That is damn cool. Tom

  6. Traditional Phone Companies by tindur · · Score: 2, Funny

    Will this have any impact on traditional phone companies?

    1. Re:Traditional Phone Companies by John3 · · Score: 2, Interesting

      Probably will impact their revenues for long distance and regional toll calls. The regional bells are clueless when it comes to new technology, so they won't move fast on this.

      --
      "We make our world significant by the courage of our questions and by the depth of our answers." Carl Sagan
  7. Wow by Dr_LHA · · Score: 3, Funny

    I was wondering when somebody was going to invent a kind of "Mobile Phone". Imagine being able to make calls from whereever you like? Its an amazing idea - I can throw away my 100 ft telephone extension cable now! I hope these "Mobile Phones" catch on!

  8. We need everything rolled into one device by pmbuko · · Score: 5, Interesting

    What they need to do now is create a hybrid cell/wi-fi/VoIP phone with bluetooth that can auto-sense where it is in relation to your desk and/or office building.

    When at your desk, your wired desk phone rings. When in the hallway/bathroom/break room, your wireless phone rings. When outside the building, calls are forwarded to your cell number on the same device.

    You would be able to customize each of the 3 zones (office, building, world) with its own call-handling rule set. Higher-end models would also auto-sense when you were in the bathroom, so you could avoid those embarrasing moments without thinking twice.

  9. yikes! by EvilStein · · Score: 2, Funny

    "The devices will start shipping in June with a list price of about $595 a handset."

    Wow, that's a costly phone..

    "Sir, I think that we can save the company money by NOT buying those expensive phones and just letting employees actually return their voicemails when they get to the office. No need to spend $595 per phone just to bug people when they're on lunch!" ;)

    1. Re:yikes! by Erwos · · Score: 4, Insightful

      It _seems_ costly, until you start doing some math. I know the price shocked me, too.

      That $600 is one time cost. There's no recurring fees on the phone, just maintenance of the VoIP network. While that might not be cheap, it's infrastructure, and infrastructure spending is easy to justify in a case like this, where you can show clear cost savings.

      A good cellular plan runs at, what, $60 or so a month in the USA. This phone is not as flexible as a cell phone, in that you can't take it everywhere and use it. But at $720 a year, a cell phone costs way, way more than this one.

      But, aha! The next year, you've saved all $720 on each phone, sans the support of the VoIP network. If you've got 1000 cell phones on your company account and replace them all with VoIP phones, you've saved nearly $720,000 - let's call it $500k with VoIP support costs. That's one hell of a lot of money.

      Not everyone needs the flexibility of a cell phone. If all you want is a comfortable wireless phone to use at work, this is a good deal. In fact, it has a goodly amount of potential for telecommuters, too - imagine patching your home system to your employer's VoIP system via the internet. No more phone bills to justify, auditing, etc.

      -Erwos

      --
      Plausible conjecture should not be misrepresented as proof positive.
    2. Re:yikes! by gujo-odori · · Score: 3, Informative
      It _seems_ costly, until you start doing some math. I know the price shocked me, too.

      I just finished a pilot VOIP install in an extremely rural area of Vietnam, about 250 km or so northwest of Hanoi, as part of a feasability study for bringing VOIP to rural areas. The system consists of a few IP phones in three locations (one of which, a high school, had no telephone at all before the VOIP install) and a couple of PCs for Internet access.

      The main site has a satellite uplink and is connected to the first remote site over an 802.11b WAN link using a wireless router with a directional antenna at one end and an omni-directional antenna at the other. The first remote site is connected to the second remote site, about 200 meters away, which has a small directional antenna pointed at the omnidirectional one at the first remote site. The voice quality is outstanding, and we tested it with calls to as far away as Ho Chi Minh City, a distance of 1600 kilometers or so.

      The initial cost of the equipment (Cisco VOIP gateway and call manager), a layer 3 fast ethernet switch, the satellite equipment, the IP phones, etc., looks expensive, but when you compare that to the cost of running landlines over nearly vertical mountains to a place that is an hour's drive over dirt roads from the nearest town big enough to even have lodging, you can see that if such a project is expanded from pilot program to full deployment, the costs scale very well. Even if a POTS network used microwave links over the mountains and only needed a wired network locally, the cost of building that wired network and putting up the microwave towers over the mountains would at least equal the cost of the a VOIP network with satellite uplink, and probably exceed it.

      Once the one-time costs are over, operating a wireless VOIP network in such an area would certainly have a lower running cost than operating a POTS network. I wish we had had Cisco's new wireless IP phones available for the install instead of the wired ones we used. Just not having to install ethernet cabling and surface conduits in concrete-walled buildings would have saved us at least a full day's work, which would have recovered the higher cost of the wireless AP and NICs compared to the cost of a cheap switch, cable, and wired NICs.

      In short, 802.11b IP phones are a significant and very promising development that will offer a significant cost savings over both POTS networks and wired Ethernet networks in remote locations.

  10. Nice Phone by Anonymous Coward · · Score: 2, Informative

    I had this phone to play with at work last thursday and friday. I was very impressed with it compared to the spectralink phones we currently have. It did do a lockup/reboot on me once though. Otherwise, great phone!

  11. Add vpn to make it complete by binaryDigit · · Score: 3, Insightful

    Right now the phone will only work in travel mode when you are connected to your own companies network. The next step would be to have a vpn client embedded in the phone, this way it can be used anywhere there is a wifi signal.

    1. Re:Add vpn to make it complete by _Sprocket_ · · Score: 2, Insightful
      Oddly enough, this is covered in the article:

      Cisco has big plans for this product line. Marthin De Beer, vice president and general manager of Cisco's IP Wireless business unit, says that down the road Cisco wants to build a virtual private networking capability into the handset so that the phone will work at public hotspots. Using a VPN lets you connect back to your corporate network over any Internet connection while encrypting the traffic to prevent eavesdroppers and network snoops from seeing your data. What it would allow in this case is the potential for the Wi-Fi network at an airport to become a connection for a Wi-Fi handset--again allowing you to make and receive calls as though you were at your desk.

  12. Dropped by Superfreaker · · Score: 4, Interesting

    I use vonage business VoIP services. I have calls drop and poor sound quality as is, now if I brought the unpredictability of Wi-Fi connections into play, it would only get worse.

    VoIP is still not a complete solution, at least not for reliable service just yet, IMHO. Unless you go with a dedicated network. Services like vonage are affordable, but they use the net and are vulnerable to the usual traffic issues, etc...

    1. Re:Dropped by Kunta+Kinte · · Score: 3, Insightful
      VoIP is still not a complete solution, at least not for reliable service just yet, IMHO.

      You're right in your case.

      But for many, many organizations, VOIP makes perfect sense.

      Many organizations have under utilized gig backbones. I know ours do. The Wan link is never enough, but the LAN backbone load never goes above 5 percent in our case.

      VOIP works well in these situation; Saves a lot of money ( they're bypassing phone drops entirely in some locations ), and quality is fine.

      VoIP on WiFi, seems like another story. I dunno about that :)

      --
      Based on upvotes, Ageism is the only "-ism" Slashdotters care about and think isn't SJW
    2. Re:Dropped by Florian+Weimer · · Score: 2, Insightful

      QoS is the key. You can make voice work in a very congested link if you turn the right knobs.

      This is usually much more complicated than just increasing the bandwidth. 8-(

  13. You know... by Faust7 · · Score: 5, Funny

    But wander from your desk long enough and chances are high that you'll come back to a telephone with that red voice-mail light glowing, meaning you've missed a call.

    Sometimes that's the whole idea.

  14. Could IP phones be the thing that IPv6 needs? by jonr · · Score: 5, Interesting

    I just can't help to wonder if IP phones will be the driving force behind IPv6. Millions of phones need their IP numbers. Of course it can be used with NATs and VPNs, but a real IP number would make much more sense.
    J.

  15. Re:I tried it once... by Tmack · · Score: 3, Interesting
    Well... Cisco has been doing VOIP for some time now, on a more commercial level. I work for a telecom company that uses cisco routers to deploy VOIP telephony to our customers via T1 (bandwidth not in use by voice traffic is used for internet access). The largest problem (trouble ticket wise) seems to be more at the physical level with T1's failing (which we get through de-regulation from the baby bells), where as your problem sounds like network lag and bandwidth limits. Granted, our network was designed specifically for voice traffic, but any company that sets up a Wi-Fi VOIP network should be able to do the same, so long as no one runs the microwave thats in the break room...

    TM

    --
    Support TBI Research: http://www.raisinhope.org
  16. Re:Wow! by morcheeba · · Score: 2, Informative

    That's not much more than Cisco's 7960 corded IP phone @ $500. It's a nice phone.

  17. Star Trek style communicators on the way? by NanoGator · · Score: 2, Insightful

    I think it'd be kinda cool to have VOIP networks at the office that yield more insntantaneous communications.

    Right now my company's building a couple of systems and we've got ppl running around all over the place. It's hard to reach people at their desks. It'd be kinda cool if we had a form of walkie talkie with a list of ppl we wanna talk to on it, tap their name and start talking. Beats using cell phones, plus we only bug the particular person we wanna bug. (as opposed to having broadcast convos over a walkie-talkie...)

    It's not something we'd spend a whole lotta money on right now as it's not solving that big of problem (small office...) but if we did have it it'd be a huge help. I'd like to call over to the guy in charge of the database just to ask a quick question rather than run to the other side of the office with the error message I'm seeing memorized.

    Well I can dream.

    --
    "Derp de derp."
  18. Re:Backdoor by pantropik · · Score: 3, Insightful

    Another instance of trading personal freedom and/or privacy for security?

    Hard to say. I mean, I live in Florida, near the capital, but you don't have to drive far in any direction to be in the middle of the National Forest (read: nowhere). If I'm driving out in the middle of nowhere, get in a wreck and end up mangled I want someone to be able to pinpoint my location if I dial 911 from my cell phone.

    What if I barely have time to hit the emergency button on the phone before I lose consciousness? What if I just can't talk for some reason? What if I don't really have a clue where I am or I'm just too addled to describe the location clearly? Around here, it's really easy to be on a 50-mile stretch of road that's just trees and more trees with lots of smaller roads branching off to who knows where.

    It's more a case of when and how the location technology is used than whether there should be such technology. It has life-saving uses, but as with so many other things the potential for abuse is huge, especially by an administration that considers accountability, honesty and transparency nothing more than obstacles that must be overcome.

    Maybe I'm too cynical ... that would suck. The only thing that would suck worse is if I'm not being cynical enough ...

  19. Whoops! by RNLockwood · · Score: 2, Interesting

    Scenario
    1. The router (or gateway or something) dies so no email. Ok, I'll use the phone. Whoops.

    2. Have a fire that knocked out power, got to call the FD. Whoops.

    I'll wait.

    --
    Nate
  20. commodity product by g4dget · · Score: 3, Insightful
    Cisco has big plans for this product line

    Cisco may be able to make lots of money on corporate accounts with an initial version of this, but if IP telephony catches on, then this sort of thing will just become a commodity, sold at cut-rate prices alongside Linksys wireless gateways (with VOIP) and non-name USB 802.11b dongles.

  21. and it'll be illegal in... by Dubber · · Score: 4, Informative

    ...at least 7 states:
    Delaware, Illinois, Maryland, Michigan, Pennsylvania, Wyoming, and Virginia
    if not more later this year or next:
    Arkansas, Colorado, Florida, Georgia, Massachusetts, Oregon, South Carolina, Tennessee, and Texas.
    Check out http://www.freedom-to-tinker.com/superdmca.html for status updates.

    For Tennessee activities against this bill see: The Tennessee Digital Freedom pages

    --
    Your complaints about being offended offend me.
  22. Cost of implementation by psyconaut · · Score: 4, Informative

    Did the original poster realize that you need a Catalyst switch and a bunch of other expensive Cisco software to get this thing working?!

    Granted, compared to a large scale Merdiain 1 implementation it ain't expensive, but it's not quite as simple as buying a $595 phone and a WiFi base station!

    -psy

  23. Re:Where did the numbers go? by dildofire · · Score: 2, Informative

    there's an RFC dealing with that exact problem.

    basically what they're proposing to do is use DNS to map phone numbers to ip addresses. if your voip phone is assigned a phone number of 5125551212, you would send a dns query with an address of 5.1.2.5.5.5.1.2.1.2.e164.arpa in order to get the ip address assigned to that number. as far as i know this hasn't been implemented yet, but it's a pretty cool hack nonetheless.

  24. Re:More to it than meets the eye by Phil+Karn · · Score: 4, Interesting
    That answers the question I was about to ask. Cisco has really crippled their VoIP phones by having them speak only their proprietary "skinny" protocol. Without an expensive and proprietary server, these phones are totally useless. At the very least, these phones ought to speak basic H.323/SIP/whatever without any outside help beyond IP dialtone and a DHCP server.

    The real market for these things is in the home. I would love to junk my crappy cordless phones and use 802.11-speaking phones on my existing wireless network. Not only would that reduce the number of boxes I have to plug in, but if it caught on it could really help reduce the persistent interference problems between 2.4GHz cordless phones and 802.11 networks.

    But most people aren't going to want to run (and rely on) a PC 24/7 just to be able to make phone calls -- much less a dedicated Cisco VoIP server! And tunneling through some server on some distant network isn't going to work either, given the extra latency and decreased reliability that will introduce.

  25. Great for managers, not for developers by YetAnotherName · · Score: 3, Insightful

    From the article: But wander from your desk long enough and chances are high that you'll come back to a telephone with that red voice-mail light glowing, meaning you've missed a call.

    Oh no! You've MISSED a call! Oh, horrors! Just think, you were discussing unwinding a recursion on a whiteboard in the hallway with a coworker, doing a walkthrough of some code on the lawn, or typing up nearly 500 new lines of code in the last hour while the ringer was muted. And you MISSED a call. Your productivity was dangerously high---just think what your phone could've done to cure that!

    I'll just use WiFi for email, thank you.

  26. Symbol had this 3-4 yrs ago by ckuhtz · · Score: 2, Insightful
    I was working on a disruptive technologies study 4 yrs ago, and we had a 'cordless' VoIP phone from Symbol Technologiesin our lab. Production release back then. In fact, they still make one it seems.

    Spoke H.323 and allowed you to call by IP addr as well as by E.164 address. Spoke 802.11b.

    So, this isn't really a new idea. Just Cisco's edition.

    --

    Poof.