Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Cisco VoIP Ditched for Open-Source Asterisk

Posted by Zonk on Sat Sep 16, 2006 06:16 AM
from the more-power-to-ya dept.
An anonymous reader writes "Sam Houston State University (SHSU) is moving 6,000 users off a Cisco VoIP platform to an open-source VoIP network based on Asterisk. One big driver, of course, is cost. From the article: 'We thought that it will be more cost effective in the long run to go with an open source solution, because of the massive amounts of licensing fees required to keep the Cisco CallManager network up and running,' says Aaron Daniel, senior voice analyst at SHSU."
+ -
story

Related Stories

[+] Ask Slashdot: Which Asterisk Or Other VoIP System To Deploy? 91 comments
ubercombatwombat is looking for a bit of advice: "On the 9th of November, I have a meeting to discuss an Asterisk based phone system for a new elementary school. I am the network admin for the district. Currently, we are migrating from a T-1 based Nortel (option 61, 2 x option 11 and 7 x Norstar 8x32's, for those who care) to 1GB data fiber and a 2nd pair per site — to allow simple copper-to-fiber for the split T-1/Norstar's. We also just got a 10MB (scalable to 100MB) connect to the Internet. I can keep the VoIP basically on a separate network if need be as well. What do I install? Are there Asterisk vendors that are available and have enough experience?"
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Rob from RPI (4309) <xrobau@gmail.com> on Saturday September 16 2006, @06:28AM (#16119648) Homepage

    I've just released FreePBX 2.1.2, which is a major security upgrade from 2.1.1. Not really relevant to this article, except that they both deal with Asterisk.

    (For those that don't know, FreePBX is the only open source GUI for configuration and management of Asterisk. www.freepbx.org [freepbx.org])

    --Rob
    • $ emerge --search freepbx
      Searching...
      [ Results for search key : freepbx ]
      [ Applications found : 0 ]

      $
      Hmm, shame it's not in portage.
      • Re: (Score:3, Informative)

        It's not, but I was working with a couple of gentoo guys to get it in - they seem to have vanished. The way we do an install and check for versions apparently causes a bit of grief. There are, however, gentoo docs on the wiki [aussievoip.com] - However, just checking over them they seem to be a bit lax (well, ok. A lot lax). The CentOS instructions [aussievoip.com] are far more verbose.

        I'd love for someone with some gentoo clues to help out!

        --Rob
    • Re: (Score:3, Informative)

      Hey Rob, I've seen you on a lot of the forums. Great work on FreePBX by the way! I have seen a number of folks posting about TCO and needing Asterisk experts, etc. I just wanted to mention TrixBox (formerly Asterisk@Home). It is a great, EASY way to play with Asterisk in a test or even real environment. You can start out using this and then move on to a plain vanilla Asterisk install if you feel the need for greater control. That being said a lot of people use TrixBox (or Asterisk@Home) as-is. TrixB
  • SCCP support? (Score:4, Interesting)

    by OffTheLip (636691) on Saturday September 16 2006, @06:38AM (#16119665)
    Seems like the majority of Asterisk support has been for SIP phones. Some support for SCCP phones such as the 7910. Be nice if more low end phone support was available. Overall, Asterisk seems much nice than CCM and does not rely on a OS/Application installation.
    • Re:SCCP support? (Score:5, Informative)

      by Rob from RPI (4309) <xrobau@gmail.com> on Saturday September 16 2006, @07:04AM (#16119717) Homepage
      I was really trying hard not to reply to _every_ post here, but SCCP is an awful protocol. And the 'low end' VoIP phone are all SIP or IAX, so you're barking up the wrong tree a bit. For example - Google for PA1688. This is a VoIP phone _chipset_ that the manufacturers have open sourced the firmware for. You can usually buy PA1688 based phones for about US$50. Or if you want more of an office phone, the Grandstream GXP2000 has a reasonably professional look, and are around US$100 or so. Going up market from there, you're looking at the Snom 320 or 360. Plenty of buttons and lights, and it runs Linux.

      --Rob
      • Re: (Score:3, Interesting)

        the Grandstream GXP2000 has a reasonably professional look

        A professional look, sure -- but the bloody things crash constantly if they don't like the network they're plugged into, their autoprovisioning is cranky at best, and our order (of about 20) had a very substantial number of duds (we RMA'd at least 3). Also, their speakerphone support doesn't work well -- IIRC, the folks on the remote end hear massive amounts of echo (though it sounds fine locally). I'd call the Sipura SPA-841 a reasonable step up

        • Re: (Score:3, Informative)

          Well yes. Their GXP firmware goes from featureless, to cranky, to bugfix, to feature+, to even more cranky than it was originally. I'm currently running some beta firmware on the GXP on my desk that has all sorts of display corruption issues.

          They did, however, get the speakerphone echo well sorted out a while ago. The snoms, on the other hand, do _not_ have echo cancellation in their speakerphone, which means it can't be all that loud. Which leads to user complaints 8-\ However, apart from that minor niggl
          • The snoms, on the other hand, do _not_ have echo cancellation in their speakerphone, which means it can't be all that loud.

            I have trouble believing that -- our single Snom 360 sounds as good as the (POTS) polycom units when on speakerphone, and we certainly don't run it quiet. Looking through their release notes, it says they added echo cancellation as of firmware version 3.60b. I don't see any complaints about lack of echo cancellation at http://www.voip-info.org/wiki/view/snom+360 [voip-info.org].

            I haven't had a chance t
            • Wups, there you go. I'm quoting outdated information. Sorry. I've got a 360 sitting right next to me too! (Actually, as I was writing that, I was thinking that I hadn't had any bad handsfree echo issues recently, but I hadn't seen anything in the changelogs about it - obviously it went in back then, and they spent a couple of releases cleaning it up and I didn't notice it)

              --Rob
      • Sounds easy but if you already own a couple hundred SCCP only capable phones you lament SCCP support. Such is life...
  • I consult for a small Asterisk host, Lylix.net, and our customers couldn't be happier. It's a bitch to configure (hence we can charge $$$ for the service) but I'll be damned if it isn't a solid piece of FOSS, much like Apache. My hats are off to the Asterisk guys, it's likely to become one of the most important FOSS projects in the next 5 years or so.
    • by Rob from RPI (4309) <xrobau@gmail.com> on Saturday September 16 2006, @06:52AM (#16119694) Homepage
      Actually, Asterisk isn't _really_ FOSS, as you have to sign a disclaimer (before you submit code to them) giving them the right to repackage it in non a FOSS way. This is so they can sell the Asterisk Binary Edition, as well as (unclear, to me) licencing issues with Intel Dialogic cards.

      OpenPBX.org (nothing to do with my FreePBX project, mentioned above) is a pure GPL fork of asterisk from about a year ago, that they've done significant amounts of re-writing on, including working on a new dialplan language, as well as being able to import a lot of Steve Underwoods work (www.soft-switch.org) with software DSP (eg, soft-faxing, T.38 [fax-over-IP], better DTMF detection) that he will only licence under the pure GPL.

      --Rob
      • "Actually, Asterisk isn't _really_ FOSS, as you have to sign a disclaimer (before you submit code to them) giving them the right to repackage it in non a FOSS way."

        Not that I particularly like this practice. But wouldn't pretty much any project with a dual license strategy where one is non-free need to do this?

        Anyone know what mysql and trolltech do?

        all the best,

        drew
        http://www.nanowrimo.org/modules/newbb/viewtopic.p hp?topic_id=33654&forum=157 [nanowrimo.org]
        Coming to IRC this November - live novel writing...
        • by Rutulian (171771) on Saturday September 16 2006, @09:05AM (#16120000)
          Not sure about mysql and trolltech (I think they are mostly developed in house, actually), but Apache uses the Apache license which allows for non-free distribution of the code. The contributors have to license their contributions properly to get them accepted into the main code base, but they don't have to give up their ownership rights.
      • by A.K.A_Magnet (860822) on Saturday September 16 2006, @07:55AM (#16119818) Homepage
        You seem to have a good knowledge of Asterisk, yet I have to correct you on the fact that Asterisk *IS* F/OSS and *IS* released under the GPL. What you're talking about is giving your copyleft to Digium if you want *YOUR CODE* to become part of the official distribution. Nothing new here, it's a common practice, used even by the FSF which *MAY* change the license then, but you can be pretty sure that the FSF won't change it to a non-copyleft license (while Digium uses it to give non-free licenses), but how do you think they'll change all code from GPL 2 to GPL 3 [not counting GPL 2 or later, since some of the GPL'ed software owned by the FSF (ie you give them your copyleft) hadn't the "GPL 2 or Later" clause and they added it later, since the license can only be changed by an agreement of all the copyleft holders, so it's easier if it's a moral entity like the FSF, MySQL AB, Trolltech the Apache Software Foundation (even if they don't use GPL, they still may want to change their license)... or Digium. And they all ask for copyleft transfer.

        My point being: yes, Asterisk is "100%" F/OSS. They just don't allow other copyleft holders in THEIR distribution. Nothing would prevent OpenPBX, to sync with each latest version of Asterisk, but as long as Digium wants to hold all copylefts, they can't include code made by OpenPBX folks. Digium wanting to hold all copylefts is a part of their business model (dual-licensing). Of course, it makes it harder for OpenPBX people to sync because of the two development trees (and I understand why they'd want to keep their copyleft). However, Asterisk remains Free Software. Maybe they're not using the "Open Source development model" at its maximum though, but who cares :). As long as it's Free (with a capital F), it's fine with me.
        • Re: (Score:3, Informative)

          Well, yes and no. When OpenPBX was forked, there was a fair bit of hue and cry about suing them for Trademark violation, which they resolved reasonably quickly (sed s/asterisk/openpbx/i) and then there was threats about licence violations by linking to openssl.. I can't find the exact message in the digium archive, but here's a link [digium.com] to the same issue being discussed about the freebsd port.

          I tend to think that they're a bit over-protective of their code. They release it as GPL to garner community support, th
          • OK, but then again, trademarks have nothing to do with software Freedom (which is at the copyright level); Linux is trademarked too (and the trademark is actively enforced). And regarding the URL you posted, it has nothing to do, I think, with OpenSSL (which is licensed under the Apache License, which is compatible with the GPL), but with Open H323 which is under the MPL (Mozilla Public License, incompatible with the GPL). And Digium could link with OpenH323 by dual licensing the needed component linking wi
            • Re: (Score:3, Informative)

              Woops. My bad, The Apache Software License isn't compatible with the GPL:

              This is a free software license but it is incompatible with the GPL. The Apache Software License is incompatible with the GPL because it has a specific requirement that is not in the GPL: it has certain patent termination cases that the GPL does not require. (We don't think those patent termination cases are inherently a bad idea, but nonetheless they are incompatible with the GNU GPL.)

              And OpenSSL isn't under the Apache Software Lic

      • Your saying its more closed than CCM in some way?
    • Hah. I just clicked on your tagline, and you're reselling Trixbox, which is based on FreePBX. Read the top comment, upgrade your sites 8)

      --Rob
  • by Alistair Cunningham (20266) on Saturday September 16 2006, @06:51AM (#16119691)

    From the article:

    "While Asterisk and the SIP protocol lack some of the more extensive features on the Cisco CallManager..."

    This may be true for vanilla Asterisk, but there is an extensive community adding a wide range of additional features and services to Asterisk. For example, <plug>our Enswitch product [integrics.com]</plug> provides a layer of billing and commercial services on top of Asterisk and SIP Express Router. Having work extensively with both Asterisk and CCM, I would claim that with Asterisk plus all the applications that work with it already surpasses the features of CCM, and Asterisk has the momentum behind it. Over the next few years, CCM will fall further behind, and before long Asterisk will be the dominant telephony platform in the same way Apache is the dominant web server platform now.

  • by HeadbangerSmurf (649736) on Saturday September 16 2006, @06:59AM (#16119705)
    My company sells Asterisk solutions to business clients and we're very happy with it. Once you figure out what you're doing the sky is the limit when it comes to configuration. My only issue with Asterisk is the voicemail subsystem. If Digium would put some time into that I would be the happiest person alive. Tom
    • Once you figure out what you're doing the sky is the limit when it comes to configuration.
      In other words you mean it is not intuitive to use, and will take a while to learn to use. It doesn't seem like a good project for a company to start on its own if it isn't its core business.
      • While I understand what you're saying it makes me wonder what projects you WOULD start if you only look at your current experience. How did you get where you are today? You obviously didn't know everything when you first started. :) Check out the Asterisk forums at http://forums.digium.com./ [forums.digium.com] Using those forums and the Asterisk: The Future of Telephony book from O'Reilly I've learned enough to build some nice systems. Tom
        • Re: (Score:3, Interesting)

          I am not saying Asterisk is a bad product and it is not worth learning. But a general commentary on the OSS community. As far as usability and design for people most (not all but most) OSS just stinks. While for all new products and method there is a learning curve. But there is one thing trying to figure out the learning curve with a text config file that doesn't give you all the options, in order for you to find all the options you need to sift threw pages and pages of documents, go threw the code and
  • by jellomizer (103300) * on Saturday September 16 2006, @07:11AM (#16119727)
    This is not an attempt to troll or anything. But this doesn't seem like to me as a major blow to Cisco. Universities and Corporate and Government user are a much larger sectors at large compared to universities. And dont tell the College recruiters this the rest of the world doesn't follow what universities do. for the following reasons.

    Universities have cheap skilled labor. A slew of talented kids/young adults who are willing towork for free or near minimum wage, but when they leave to the real world they will be demanding $35,000 and up a year for the same job. This is the reason why many Open Source projects work and save money in Universities but when a Corporation gets it, it becomes a money pot. Because for a company it is cheaper to call Cisco and pay them $1000 for a fix to their problems then having a team of 10 people at your company taking a day to fix the problem because they do not have the answer sitting right in front of them or able to contact the engineer who created it. vs. a University where this 10 people 8 bucks an hour are much cheaper then calling Cisco for help.

    Universities are allowed to experiment almost by charter. If something goes wrong this screw all the people who are not getting phone service. You will have wait until we fix the problem, it is not like we are loosing money with the phones down for a couple of hours. Private companies loose money when their communication are done so they want Cisco to come and fix it right away and they better know what they are doing. Being an Education facility it is allowed to experiment in different products while Companies find better value in using what they know works.

    Liberal University vs. Conservative Corporations, basically means if it not exactly what we want we keep on trying and trying until we get it right (perhaps making it worse in the process) or If it does what we need we hold on to it until we find the perfect solution (which guarantees that they are going to use a product they don't like for a long time)

    This is why Open Source is popular in Universities but in Corporate and government use they need to work a little harder to get acceptance.
      • That is assuming the Company can gather a team of Asterisk people. I most cased the person will be hired and do what they learned with Asterisk and use many of the Ideas on Cisco Stuff. Still when they are hired they are going to get paid more money where on the spot Cisco support is cheaper then them figuring out the problem. It is not about the product being bad it is just the Cost savings in the university are far greater then what corporate savings are. Asterisk will have a better chance if there is
  • I work for a SIP hardware provider. We have a whole department dedicated to interoperability testing with other vendors of SIP infrastructure and user agents. Asterisk is approximately the least SIP compliant bit of software out there. It's great if all you want to do is basic calls but the reason why it's perceived as working so well is because vendors (like us) have to hack our software to work with it because our customers demand it, even if it makes us non-RFC compliant. Why has Asterisk never shown
    • by Rob from RPI (4309) <xrobau@gmail.com> on Saturday September 16 2006, @07:24AM (#16119759) Homepage
      That's totally incorrect. OEJ (a leading developer) has taken Asterisk several times to SIP Interoperability Testing meetings, and has acted very proactively to fix perceived or real incompatibilities.

      I just did a quick search of the Digium bugtracker, and I didn't see any 'SIP Incompatibilty' bugs there apart from an issue with sipgate.de.

      I honestly think you're trolling, or you have no concept of how FOSS works. If there's a bug, you fix it, and if you can't fix it, you report it and someone who can fix it, will.

      --Rob
    • And this is [asterisk.org] exactly the link I was thinking about. Please, don't feed the troll.
  • I mean, before bashing on other people, they might just have looked at their own site.. The page contains 160 images (is that really neccesary?)), When I hit back I got a "malformed URL" message, and frankly, it's just an ugly and awkward site IMO.
  • My friend at my last job wrote his own VOIP software and he told me it wasn't very hard. If I had my own voip system, all I'd be doing would be making calls to my friends from the White House, Pentagon, or other famous places for fun.
  • Or, more puzzlingly (that a word?), how do some companies get away with competing against FOSS products with highly expensive proprietary offerings? I'm assuming that the proprietary solution has the same functionality as the other; maybe some bells and whistles on the fringes, but essentially the same.

    They must make their money from licencing fees (and maintenance, but FOSS can do that, too). So why don't customers choose the cheaper option. Don't get me wrong; while I approve of FOSS and use it whenever I can, I won't hestitate to buy a proprietary product if it does what I need and there isn't a viable FOSS alternative.

    I'm no expert in this - which is why I'm puzzled. Can anyone tell me (us) why? Is it any combination of the following?

    1. "Noone was ever fired for buying IBM" (MS/Cisco/etc).
    2. The bells and whistles are what the buyer craves.
    3. Proprietary products have better support.
    4. It's free, so it can't be worth anything.
    5. What's FOSS?
    6. We only run Windows (Solaris, whatever).
    7. Proprietary products are better "rounded" or "easier to use".

    I know that all these have flaws and, sometimes the reason is valid. But overall, I think my question still stands.

    BTW. If anyone can think of anything to add to the list - I'd love to hear it.
    • Re: (Score:3, Insightful)

      It's the support. Company A spends a large amount of money buying (say, Microsoft/Cisco/whatever) and at the same time takes out an expensive support contract. Company B uses FOSS.

      Something goes wrong. Company A gets on the phone, and they have an engineer on-site within the hour, and the problem is fixed within 3 hours. Total cost? Loss of 3 hours business + SLA payouts.

      Company B runs around for a bit trying to figure out what the hell it might have been, before flash-hiring a bunch of software consult

    • Re: (Score:3, Insightful)

      There are several reasons, many of which you have stated.

      One more reason I have observed is that people get used to a particular platform. More often than not, a commercial vendor enters a market first, or even creates the market. So people start using that vendor's products and then it becomes difficult for them to switch and learn something new. Many are satisfied if something just simply works, and they don't want change. In this SIP case, they probably purchase the hardware and software as a bundle.

      This
      • The trunking is a feature of the phone, not of the backend PBX software...
        You can use cisco phones with asterisk, i`m using a 7960 at home with multiple asterisk servers (the 7960 has support for 6 "lines"), and the vlan trunking works on it, although i don't use it at home...
        Many of the Nortel phones support trunking too, tho i can't speak for any of the other vendors.
        In terms of the backend, linux will also support trunking if you need such a facility on the backend.
  • I've used asterisk quite a bit and it works quite well. Also Sipx PBX is another good performer, although slightly harder to set up, easeier to configure. Sipx PBX is another open source solution that can be found over at the Sip Foundry [sipfoundry.org]. They have some good testing code that comes in handy when troubleshooting sip to sip issues. cluge
  • Asterisk? (Score:3, Informative)

    by TCM (130219) on Saturday September 16 2006, @09:02AM (#16119991)
    I know everyone hypes Asterisk and Open Source and all that.

    But has anyone looked at Asterisk close enough? It's the most horrid piece of software I have seen in a long time. Its configuration is awkward at best and downright inconsistent and nonsensical at worst.

    Its documentation is practially non-existent. Nowhere do you find a good documentation written by the programmers. All you have are Wikis and web sites where people try and guess how Asterisk works. Howtos consist of config snippets without explaining what the options mean, let alone explaining the grand scheme behind everything.

    Maybe it works after you configured it based on some other guy's experience, but if you want clean and well-documented software, go look elsewhere.

    Asterisk seems to be the PHP or MySQL of the PBX world.

    </rant>
  • There is some irony to this story - the expensive part of any phone system is (hold your breath) the phones. I will point out that the SHSU could pick an open standard protocol and move the phones from one system to another. Try that with Microsoft Office Communicator some time - you can't. I noticed that this story is under the Linux category and - I will point out that Cisco Call Manager 5.0 runs on linux and can run SIP to phones (as well as many other protocols).

    Now, I know Asterix fairly well, Cisco fairly well, open source VoIP fairly well (as the joke goes I wrote the O'Reilly book), and SIP really really well. As was pointed out in Mark Spencer's Keynote at VON last week, the SIP stack in Asterix certainly has some room for improvement. And given SHSU does not seem to have any intention to support the development of Asterix by buying a support contract from Digium, I sure hope they are doing something to make sure that Asterix get the support that they will need it to have to stay relevant.
  • by mytrip (940886) on Saturday September 16 2006, @09:32AM (#16120086) Homepage Journal
    I work for a Fonality PBXtra reseller and the pbx absolutely rules. Asterisk on linux is the future of PBXs. The menu system, reporting, call queues and gui absolutely kill traditional phone systems. BTW, Vonage runs on Asterisk and so does broadvoice and other VOIP companies.
  • by ipstacks (629748) on Saturday September 16 2006, @10:56AM (#16120378)
    I just deployed an Asterisk phone system powering ~140 wired Polycom phones and ~70 wireless phones covering 31 acres. Here are some tips from what I learned in this process:

    1. Pick a capable vendor for each job you outsource. I looked at Asterisk and decided it is too technical for a Asterisk newbie to build a production system, so I called Digium and they referred me to a dCAP certified Asterisk consultant in my area. Knowing Asterisk is one thing, but knowing how to pull off a great install is more than that. Our vendor developed a workbook that covers many parts of a successful deployment, such as reviewing the network (gear, configs, wiring plant), getting the users (names, current extentions, locations . .), getting the users to think about the dial plan and having them understand their satisfaction with the results is directly related to trying to get it right. When we distributed the phones to each desk, the boxes were labeled and sorted on the pallet this helped save a huge amount of time and allowed us to have the furniture installers help setup phones if we wanted too. Staging the phones: pre-configuring them, having the boxes labeled and sorted on the pallet was well worth doing. The wireless phones we signed out to the employees with some other stuff like work shirts. Having the right vendor to walk us through the process was critical.

    2. Pilot your install before you deploy it. The environment I was choosing Asterisk for is an automall. Phones are a big part of the business (as with many) and setting expectations is important. We formed a phone users group to have them decide how we wanted to route calls (dial plan), the idea was to get them involved because it is really theirs to use. Some departments were easy and some were not. Sales was essentially create a call groups for the differnt brands we sell and have the operators transfer them to the appropriate group. Service was much more complicated, but having live operators helps a ton. Parts was easy as well, but all of that needs some serious consideration. Knowing you will get it wrong and tweaking it on the fly will happen, do it and move on.

    3. We picked Polycom phones and that turned out to be a great choice, the 601's have six "programmable" buttons and great sound quality (handset and speakerphone). The Polycoms have a two port switch built-in and will trunk with the network switch which means the second port on the phone can be a differnt vlan than the phone. So we have them plugged in/wired like this: [network-switch]---[phone]---[computer]. The phones run Cisco CDP, when the switch detects the phone (via CDP) it assigns the phone as a trunk device and allows you to choose what vlan the phone will be on and what vlan the computer port on the phone will be on. Also you can have a differnet vlan if you were to plug the PC directly into the switch. The setup works well and I could go on and on about QoS, edge marking of traffic and PoE issues but I will stop.

    4. The FOP (Flash Operator Panel) is a cool thing, but we had to do some customizing for our needs. We looked at Fonalitys HUD, but FOP works great. You can see which phones are ringing, have voice mail (whether it is new or old), transfer calls by drag and drop, monitor the inbound queues and really not have to touch the phone to work the system as an operator. Nicholas, the guy that wrote FOP is an invaluable resource. He was willing to help and has done a great job. I am asking our vendor and am going to make sure he gets paid in some way.

    5. Wireless WiFi phones (OUCH): We chose the Hitachi IPC-5000 and Meru Networks for the AP's. Okay I was getting a little cutting edge here, but hey why not?! Lessons:

    Meru Networks ROCKS!! They figured out the roaming WiFi thing for sure!

    Hitachi IPC-5000's to be determined: it look like either the phones have a high failure rate or we have a bad batch or something. Also it looks like they aren't nearly as durable as say a cell phone/mobile phone (which is VER
  • by erroneus (253617) on Saturday September 16 2006, @01:04PM (#16120901) Homepage
    Back in the day, well before software was as complex and complicated as it is today, software was just stuff that came with the computers that were sold. Software itself wasn't the "product." But since Microsoft decided to expand their market beyond hardware makers to consumers and wrote that letter about software piracy, the world changed.

    How is this relevant? Again, software is the product. In this case, Cisco and its licensing fees. Most people think of Cisco as a hardware product. While I know it's just a computer with software code that routes information around, it's still, in the minds of many, a hardware product that serves its purposes. But when you are talking about "license fees" you start to think of it differently... more like software. Cisco screwed itself, I think, by moving away from its perception as a reliable hardware product maker. Now you buy their hardware and license the software. It makes people want to shop around more and since the Asterisk product is OSS, well the choice starts to become one of how much money to spend.

    It's unfortunate, but seems to be a potentially strong indication of what OSS is doing and why there is such resistance to it, where it comes from and what forms it takes. Looking at it from this perspective shows a nice angle to why software patents are such an important weapon in the software product world.
    • Re: (Score:2, Insightful)

      I'd be interested to see the total cost of ownership including ongoing maintenance of Asterisk vs Cisco which has an abundance of specialists.
      • I used to work for a company that did a buttload of Call Manager. Well, they still do but I don't. I love Call Manager. It's an incredible platform but it's just so damn expensive. Both systems need care and feeding and I would say that Asterisk needs more of that at this point in time. The Call Manager systems I've worked on ran smoothly and required little to know intervention. Asterisk is a bit more of an attention whore right now but I figure that will change as time goes on. The big thing with A
          • God forbid someone makes a grammar mistake in a long post... jackass.
              • by MightyYar (622222) on Saturday September 16 2006, @09:17AM (#16120037)
                "Know" for "no" is a truly boneheaded error, much more so than "then" for "than".

                You forgot a question mark in your post correcting him - that's an even more bonehead error.

                His message was adequately communicated - you don't need to be annoying and correct him. If you were adding clarity to his post, it would be one thing, but you are just nit-picking. Add something to the conversation or go the hell away.

        • Ditto here. I have numerous asterisk machines, none fancy, around the world (also running on Slackware!). No problems at all. Also with the $169. Polycom 501. Great central administration, excellent sound. The users love them. Hint: DO NOT go cheap and get Polycom 301 phones. They work fine, but the UI is unusable. And NEVER have both in the same office, the people with the 301s will hate you and feel they've been branded as second class citizens.
    • Good question. I'm going to call it Skippy from now on.
      • Re: (Score:3, Informative)

        But if I remember - and I'm too lazy to look it up - SCCP stands for SKINNY Client Control Protocol, and is a modified, scaled-down (skinny) version of H.323. The original Selsius (company Cisco bought in 1998 which gave us Call Manager) designers didn't have a SIP or other protocol to use back then and H.323 was too much, hence why SCCP was first created.