Blogged via wireless handheld.



I
am heading to New York, back from Channel Partners and onto SpeechTek in
Manhattan. More to come soon.
Blogged via wireless handheld.



Blog Response for The Hyperconnected Enterprise Post
Presented with the disruptive threat of open source Asterisk, and the recent momentum seen in commercial channels and the enterprise, Nortel acquired sipXecs. Can you buy your way into open source credibility? Nortel's not the first old-line company to try. Is open source a marketing bullet point for Nortel ? Its certainly not inherent behavior that's woven into the fabric of the company!
Hey, I can't blame them -- if you were Nortel, and saw Digium and Asterisk on one side and Microsoft on the other, threatening to eat into your core business, what would you do?
So: Bravo, Nortel! Welcome to the next generation of telephony. But you'll need to learn the strengths and limitations of what you just bought. As we have learned from our commercial customers as well as the countless numbers of Open Source Asterisk installations, SIP is not the entirety of UC. True, Asterisk isn't a SIP proxy -- because a SIP proxy alone cannot provide services the world has come to expect from phones.
To pick a specific example of the rather misleading comments in your article: It's incorrect when you claim that all Asterisk calls go through a centralized system. We assume you've just been misinformed, but your claim that Asterisk is designed to always handle media streams is just incorrect. You should recognize that the Asterisk rhetoric from the sipXecs and FreeSwitch teams refers to Asterisk over 4 years and several versions ago when they last looked at the feature set. In some cases, the Pingtel/sipXecs team in particular likes to compare against specific SMB packaged systems and not native Asterisk, which would provide a more "same page" comparison. The SCS500 scales to 500 users. It certainly does not need the power already in Asterisk today.
Let's talk real numbers. Asterisk community members have quickly created testbed platforms which process 300 SIP calls per second capacity. When RTP is managed by an Asterisk instance, we have demonstrated as many as 1900 concurrent G.711 channels on inexpensive off-the-shelf hardware. The open source versions of Asterisk were designed to handle hundreds of thousands (yes, hundreds of thousands) of end users in different circumstances, spread across multiple machines with functional role distribution in a way completely unlike a PBX. Of course, smaller SMB solutions are selling well for our Switchvox line as well as a dozen or more other companies who repackage Asterisk with limited hardware or license caps - that is their business. But please be a bit more forthcoming in your comparisons - Asterisk is being run in systems spanning huge user PBX and service delivery populations.
For sipXecs to compare themselves against the pre-packaged SMB offerings of Asterisk in different flavors is misleading. That's like saying the Apache web server on my embedded-processor webcam can only handle 2 simultaneous streams, therefore Apache doesn't scale on any platform. So while Asterisk can serve as a PBX, it can (and for countless customers and projects already does) also serve as an incredibly flexible service-delivery platform for UC services, custom application development, or carrier VoIP integration. It can be used on even the smallest embedded platforms (Linksys WRT54G, AA50) or on the largest voice server farms such as Integrics' Enswitch which directly supports over 100,000 end points and over 6,000 concurrent calls just for one of their 40+ customers and integrates easily through Asterisk APIs to multiple billing solutions.
As the "wildcard" name suggests, Asterisk works with numerous protocols and codecs. When required for communication between disparate endpoints, Asterisk will intelligently negotiate and transcode between them. If the two are compatible, Asterisk will hand off the call and get out of the way. Asterisk has the flexibility of handling media if desired, but RTP between endpoints is the preferred design for larger systems, including video, which Asterisk has handled for several years now.
In contrast, the sipXecs architecture enforces the requirement that all endpoints be uniform, which pulls along all sorts of ugly forklift-upgrade requirements for businesses looking to grow into the future, or uses expensive media gateways to do what Asterisk can do in software. We can confidently say that Asterisk does UC and that sipXecs is simply a SIP platform that requires lots of other moving parts to get the job done. Don't take our word for it--read their comparison posts, which say sipXecs needs other components to complete their system. Asterisk handles the "U" in UC (as well as the "C") and has for some time now.
The only claim that seems to be correct in Tony Rybczynski's post is that for large Asterisk installations, there is no comprehensive management interface for all possible aspects of the system. There are multiple web-based interfaces available for small/medium enterprise PBX-style installations - FreePBX is the most popular open source tool, and Digium's Switchvox being an excellent representative of a commercial packaging. Both of these examples include automatic phone configuration and provisioning. However, Digium has found that large enterprise developers who wish to harness the true power of the system typically want to have call control at a much more fundamental level than what a GUI typically offers or what a vendor might consider "simplified." Therefore, Asterisk is available as a telephony toolkit - a suite of programs and fundamental tools that allows a developer to quickly deploy new voice apps or extend existing legacy platforms if they so choose - it is as flexible as the circumstances require.
One final observation counterpoint to a comment you made: As the progenitors of the venerable DMS-100, Nortel should know by now that the age of code -- or lines of source -- mean nothing when compared against other software. Do more lines of code indicate more features or quality? Do fewer lines evidence efficient, bug-free code? Lines of code are typically irrelevant in doing anything other than measuring platforms against themselves over time or measuring individual coding productivity.
It's going to take more than this acquisition to, as Tony says, solidify Nortel's "leadership in the global open source ecosystem." We hope that this purchase creates a more viable and useful application that can be used by the open source community - we hope this isn't a repeat of the Vovida(Vocal)/Cisco purchase and subsequent smothering. But for the sake of the open source telephony movement that Digium started, Nortel, we welcome you to the open source revolution.
Contrasted to Silicon Valley where companies seem to pop up and then get acquired by Cisco or Oracle faster than the time it will take you to read this article, Dallas has some telecom companies which have been around for years.
So as you can imagine -- in order to do my job well as traveling editor, covering all that's important in communications and technology, I stop by Texas often.
One of my stops on my latest Dallas area road-trip was at Iwatsu, a 70+ year-old Japanese phone maker catering to the SMB. The company has high-quality phone systems and although they are not as well known in the US as they are in Japan, Iwatsu has a reputation for designing solid products.
While in the company's Irving headquarters I was shown some information on how energy efficient the company's phone systems are. Since the phone systems are convection cooled they are greener than much of the competition as they don't use fans. Equipment that does not use fans is almost always more reliable as well.
Iwatsu has never been afraid to use advanced technology and partner with other companies to give their dealers an edge. For example they resell a reverse 911 service allowing large amounts of people to be contacted in case of emergencies. This same service has been sold to retail companies as well. For example car dealers use the service to quickly contact existing customers when a new model comes out.
Another interesting area of focus for the company is phones and there is still a focus on providing TDM as well as IP endpoints. In fact, you can even send text messages to TDM endpoints.
In addition the company is adding bluetooth capability into some of its models and testing has been done with 50 different bluetooth headsets. The system software can even increase or decrease transmit and receive audio levels of the phones if needed
Iwatsu Voice Networks President David Carissimi shows off bluetooth features of Iwatsu phones
The company's Gateway Server holds applications from call accounting to ACD and includes an SDK and all software comes with a 90 day free trial. For VARs this is the ultimate in puppy dog sales - you know, giving the puppy to a family to play with for a weekend always means they will come in Monday morning and buy it.
I also had a chance to look at the company's Precot phone which is one of the most advanced phones on the market. Sadly, It is only available in Japan at the moment.
The Precot has integrated videoconferencing, can offer a scalable web browser, touch screen/stylus support, support for click-to-dial from web pages, soft keyboard support, mouse support, external monitor support, S Video RCA video out/in and RCA audio out.
The semi-famous Iwatsu Precot phone
With all these connectors, the phone seems as comfortable connected to your home stereo system as it is on your desk.
Another interesting feature of the device is the ability to control panning and zooming of remote video cameras via the phone. Finally, you can also associate other video cameras with phones on the network, meaning you could have a security camera aiming at a hallway phone associated with the hallway phone. So when a call comes in from this extension you could be watching the person making the call.
My Dallas trip was certainly very informative and one of the highlights was seeing how advanced the Precot phone is. Whether companies will actually pay for phones with such advanced features is the next question I am wondering about but I can see the security-based vertical markets as a natural for this phone. This means, schools, government, military and other segments of the market could be very interested in getting their hands on the Precot. I too am certainly hoping I get my hands on one if it does ever show up as a production model in the states.






In many cases they do but if one company has it's way this will no longer be the case. A company named AppTrigger is looking to bring the old applications into the new world of next-generation networks while simultaneously allowing many of the next-gen services to be available to subscribers on legacy networks.
The company even rolled out a new program called the Application Session
Controller Advantage Program, a new integrated program that provides a construct for evaluating current application business models as service providers examine the risks and rewards of advanced network migration strategies.
Of course this begs the question, what is an Application Session Controller or ASC? To answer this question I travelled to Richardson, Texas where the company is based to learn more.
While there I spoke with Tamye Oshman Dir of Marketing, Wally Beck (blue shirt) Senior Director of Marketing and Patrick Fitzgerald (white checkered shirt), Senior Vice President Sales and Marketing and in my meeting on a scorching Texas day I got to learn about how the company evolved from a media gateway company into what they are today.
Moreover, I learned about how the company has partnered with Unisys and now Microsoft and their focus on North America, EMEA and APAC and Latin America.
But I promised to tell you about the ASC - it is a pre-IMS network element which sits between the application layer and Network Element.
The ASC allows an application such as enterprise VPN currently running on an IN network to be introduced on an IMS network without rewriting or repurchasing of the application.
I am told the ASC supports all the APIs (a bold statement but check with the company for details) and some media such as record, playback and SMS.
So should service providers work with a company like AppTrigger? It depends really. In a world which is getting more and more complicated for carriers, do you need to keep your applications more organized and maximize the revenue of each of them by allowing users on all networks to use them? Of course the decision is up to you but it seems logical that going forward, ASCs will become common network elements in many service provider networks. Once this happens, we should hopefully see more revenue potential for carriers and more opportunities to use disparate services regardless of the network they are on.