Nortel's fascinating move into open source telephony... but NOT with Asterisk
Nortel and "open source telephony"? Huh?
That was admittedly my thought when I received the list of who was going to be on the panel I moderated last week at VoiceCon on open source telephony. The other two panelists were obvious choices: Bill Miller was from Digium (makers of Asterisk) and Raza was from 3Com who have recently announced that they would be reselling a version of Digium's Asterisk Business Edition. Both Bill and Raza made sense to me. But Tony Pereira of Nortel? Nortel does not leap out at me as a company working with open source telephony - what in the world are they doing with it, I wondered?
It turns out that the answer is... "quite a bit!"
As Tony Pereira outlined in our panel as well as in conversations afterwards, Nortel is in the process of launching their "Software Communications Server 500" (SCS 500) targeted at small businesses and built using open source telephony software!
Interestingly, though, it does NOT use Asterisk.
Instead Nortel is using the "other" major player in open source telephony, the "sipXecs" product from SIPfoundry.org. (Previously called "sipX" but renamed "sipXecs" about a year ago.) I've not written all that much about sipX here but it certainly has been a product I've known of over the years. It started out as a PBX product from Pingtel which they then released as an open source version ("sipX" and now "sipXecs") and also had a commercial version called "SIPxchange". sipX garnered perhaps its most attention back in October 2006 when it was announced that Amazon.com would be using it for their internal phone systems (see the links on the SIPFoundry.org site). At a fundamental level, sipX provides similar functionality to Asterisk but where Asterisk is focused on being a "platform" for telephony that can work with a wide range of protocols, sipX is focused exclusively on SIP and also provides an extensive GUI management tool. (Pingtel provides a (obviously biased) comparison of sipXecs vs Asterisk on their wiki.)
From what I learned at our panel, Nortel is essentially creating their own supported version of "sipXecs" that they will sell as the "SCS 500". It will have full commercial support from Nortel. Target market will apparently be "small" businesses. No info really available on Nortel's site yet, although glimpses are visible through support documents (such as here and here(although this appears to be about an earlier 1.0 version last year)).
All in all it's to me a fascinating move by the folks at Nortel and I look forward to learning more about the SCS500 product over the next weeks and months as they launch it. It's a rather nice boost for the whole world of "open source telephony", too, to have Nortel making this move as well.
Technorati Tags: nortel, open source, asterisk, sipx, sipxecs, pingtel, voip, sip

I'm down in Orlando this week for
FYI, I will be down at
Those of you interested in Asterisk and open source telephony may be interested in the "
Digium
"It's about an open platform, stupid!" While I didn't include Google when I first wrote
Imagine you are a customer service rep (CSR) at a small/medium company and a phone call comes in from a customer. As your phone rings, up on your screen pops all the information about that customer, pulled from your CRM database in Salesforce.com or SugarCRM, plus other information from other databases and finally a nice Google Map showing you where that customer is located and potentially other information like the locations of your nearest offices. During the call, the CSR needs to bring in a subject matter expert so the CSR consults their web panel and looks at the presence information displayed for each of the other people in the business. The CSR can then contact someone showing as available and potentially bring them into the call.


In watching Jay Phillips do his great presentation here today at AstriCon about Ruby and his
Here in Phoenix, Arizona, AstriCon has kicked off with two pre-conference sessions that run all day. "Asterisk 101" is running next door and providing a basic introduction to Asterisk. I'm sitting in the "Developer 101" session (pictured) where there are about 100 people gathered in the room. It turns out that this is about developing with the Asterisk code base, i.e. "how to become an Asterisk developer" versus what I was personally thinking it was, which was "how to develop apps that work with Asterisk"... although that is really just an extension of the first. So far, an hour into the session, lead developer Kevin Fleming has been discussing the various tools you need to use in order to work with the Asterisk code base (ex. subversion, makefiles, etc.). Right now he's been dealing with the fun subject of licensing code, the GPL, and the requirement of developers to sign a disclaimer over to Digium that: a) asserts that the developer can contribute the code (i.e. it is original), that it is not patent-encumbered, etc. and b) gives Digium the right to redistribute the developer's code under a different license.










