Has Asterisk NOT “crossed the chasm” for developers? (Key links to read for open source)

jayphillips.jpgJay Phillips is frustrated. He passionately wants to see open source telephony enjoy success all around the world. Yet right now, when people think “open source telephony”, they almost always think of Asterisk… and Jay sees too many challenges for developers embracing Asterisk. Jay, the creator of the Adhearsion telephony framework for Ruby, has spoken about this at recent conferences and pulled together his thoughts in a lengthy post earlier this week entitled “What We’re Not Admitting about Asterisk“.

Jay argues that Asterisk has not crossed the proverbial chasm for developers and outlines some of the issues he sees.

What is perhaps most interesting about Jay’s post is the equally lengthy response by Asterisk creator Mark Spencer. Mark responds to Jay’s various points and in doing so provides some good insight into his views on Asterisk’s connections to developers, APIs, etc., as well as the differences between the markets that Digium, the company, goes after versus the “market” of Asterisk, the raw telephony platform.

Both Jay’s article and Mark’s response are definitely worth reading. I’m friends now with both of them and they both bring immense passion and energy to the world of open source telephony. Ultimately they both make the point that we need better tools for developers to create voice applications. This kind of dialogue is great and will only result in better tools in the end. Please do check out the posts.

P.S. Thomas Howe has also weighed in with a post saying this is a clash in world views, which also makes for good reading. I agree with Thomas that we are in a transition into a world of “web-as-a-platform”… basically a transition “into the cloud”… and so we do need “web-centric” interfaces and APIs. But I disagree with Thomas that Asterisk is “tired”. To me, Asterisk is just… well… “plumbing”. Asterisk is a telephony platform, as is FreeSWITCH… as is Yate… as are all the commercial IP-PBXs. Asterisk is an open source component of the rewiring of our communication infrastructure that we have underway right now. I think anyone, including Mark, would agree that Asterisk has technical challenges it needs to overcome but I, for one, am not ready to write it off yet.

Technorati Tags:
, , , , , , , , ,

3 thoughts on “Has Asterisk NOT “crossed the chasm” for developers? (Key links to read for open source)

  1. Diego Viola

    Even Teliax is switching to FreeSWITCH now, this is so awesome… it means better services with greater quality, happier customers, better for Teliax and FreeSWITCH.
    “We are actually in the process of moving to FreeSWITCH right now. It has taken several months of development and testing but it is currently in production on the atl.teliax.net proxy. Once we get a few more bugs worked out we will be deploying it on the rest of the proxies our 2.0 system use. We are very excited about the transition and have found FreeSWITCH wonderful to work with.
    Thank you,
    Josh”
    Yay for Teliax and FreeSWITCH! 😀

  2. reader

    Great! If you’d like to use another ip pbx, then by all means. Many unfair criticisms of asterisk, but I guess that is to be expected. Its a stepping stone, and has turned out to be a great framework( hardly worth mentioning that then other frameworks are near duplicate forks anyhow…) I for one don’t see the use in biting a feeding hand. If there are problems, everyone should work to improve them. That is it. Make progress. Pandoras box is open now and that’s great for you and I, but let’s not criticize those who got us here. Its not constructive, it just isn’t. If you would like to criticize the project, do so in a code contributing manner, if you believe your problems are solvable for the greater group. Thanks.

  3. reader

    Great! If you’d like to use another ip pbx, then by all means. Many unfair criticisms of asterisk, but I guess that is to be expected. Its a stepping stone, and has turned out to be a great framework( hardly worth mentioning that then other frameworks are near duplicate forks anyhow…) I for one don’t see the use in biting a feeding hand. If there are problems, everyone should work to improve them. That is it. Make progress. Pandoras box is open now and that’s great for you and I, but let’s not criticize those who got us here. Its not constructive, it just isn’t. If you would like to criticize the project, do so in a code contributing manner, if you believe your problems are solvable for the greater group. Thanks.

Comments are closed.