Slashdot Mirror
IBM and 3Com Plan First Internet Telephony Suite
TechnoGuyRob writes "IBM and 3Com, a company best known for its computer network infrastructure products, are teaming up to provide the world's first IP telephony suite. From the article: 'IBM and 3Com intend to offer the 3Com VCX suite of IP telephony Relevant Products/Services from solutions on IBM's System i business-computing platform... This means clients will be able to run business and telephony applications simultaneously managed by the System i's tools.' The application is intended for the Linux-on-Power operating system; so yes, it will run Linux."
...other than Asterisk, right? Or is this somehow much better?
Dewey, what part of this looks like authorities should be involved?
Also, link an article that actually says something useful. This looks like a press release. It doesn't give any details as to how, where, or even when (and if I had a dollar for every time something on Slashdot was "announced" without a market date and never actually was released, well, I'd buy Slashdot...or something).
For a business to really base itself on an internet telephony platform, they need it hooked into a set of software allowing reporting, processing, etc. In its current incarnation, Asterisk provides a very simple Call Data Record output to ODBC or MySql. That's about it. Beyond that, the programmer has to invoke Perl AGI scripts along the way or make SQL queries from inside Asterisk's clunky extensions.conf configuration language.
Bottom line is that your business intelligence platform winds up being a bunch of homebrew Perl scripts. Not my idea of a fun time.
What IBM will put together is a set of tools where you can build the business intelligence platform alongside the PBX functionality that Asterisk makes in a completely integrated fashion, using object oriented tools, etc. Anyone considering building a mission-critical system on Asterisk should read over the extensions.conf file format for a little bit. It uses line numbers and Goto as its major flow control mechanisms. I thought those went out with Commodore 64 BASIC programming.
It's true that a few big companies use Asterisk. In each case they've had to tweak and rework it dramatically to make it useful. I predict this new system will blow Asterisk away.
Free Conference Call -- No Spam, High Quality
I didn't think 3Com survive the dot-com-go-busty cycle. What has it been doing since spinning off Palm and not being swallowed up by Cisco?
On a side note, my first modem was a USR 2400 internal.
"3Com" tag gets filtered out..
Read the Information Week article. The system already runs on Linux. It's being ported to i5/OS.
This remind me of a story a friend of mine told me. He told his company NOT to purchase a 3com VoIP system, but they didn't listen. They had nothing but grief thereafter. The 3com VoIP system would not read line voltages correctly from a Vonage ATA (they were using Vonage for phone lines for some reason). Further, it would not work with 'SIP', as 3com had their own proprietary protocol. It was later found out that 3com firmware had a bug in it that prevented the Vonage line from hanging up. SO they downgraded... then other things broke.
This is exactly why we are dumping our Nortel phone system for Asterisk. Proprietary stuff is junk! The Nortel crashes, drops calls, is clunky. The ACD monitoring software (Cinphony) REQUIRES that it be run on an IIS server as 'Administrator' rather then the Internet account. When questioned the company said "yeah don't put that server on the outside of your firewall". I said what?! That's not acceptable, you can't run an application as 'administrator'. They said 'well that is how it runs, sorry'.
Problem is, once you have a large system like that put in for a call center, you can't exactly "just return it". We spent the good part of 2 years fighting the company that put in the Nortel and Cintech (Makers of Cinphony) to get it to work right. To this day it only transfers a call out of a queue to a land-line when it feels like it.
Oh and don't even get me started about "The routing resources needed for this call are not available" if you have a transfer to an external number from one of the menu trees on the Nortel.... apparently you can only have 1 outbound transfer from a CCR tree?!?!
This is why I hate proprietary software.... it doesn't work, and they don't support it!
Only thing that concerns me concerning competetiveness, are the new fcc telco rules and related pending legislation, the stuff that will make it easy for monsters like IBM and 3com to pay premiums for better ISP service.
All people talk about is Asterisk. Meanwhile there's the OpenSource solution (even GPL) called Yate; which handles a magnitude larger number of calls than Asterisk on the same hardware, it has the (currently still unique) perfect NAT-proof algorithm for SIP, it has excellent support for H.323, and, last but not least, the company supporting it insists to do paid work only when it results in (new) GPLed code.
Yate handles business-logic integration just fine with predefined hooks (I used a PostgreSQL backend to integrate it with).
Check out Yate, it's open source, and scalable, and is in use in many callcenters in Europe without problems.
This is a interesting opensource project started by someguys, we're currently testing it out at work, so far theres no issues. voip suite
It is THEIR first telephony suite, perhaps, but not THE first. Reminds me of old AT&T claims about "firsts" things that had debuted elsewhere.
It did get me to RTFA, which is the purpose of a headline, but it was misleading. The actual article was not particularly interesting.
the support costs of a iSeries? Linux might save you a bit for software support, but that harware support, and arm-twisting upgrade schedule will have you pulling your hair.
Other than this text, there is no discernible information contained in this sig.
I can't speak for the IBM contributions, but I worked on some of the old NBX stuff when 3Com bought them out.
There's more than just the software aspect of this - there's a lot of hardware to interface to T1/E1, ISDN BRI, modems, faxes etc. Dealing with analog lines, generating / recognising pulse dialling / DTMF, echo cancellation, mostly DSP stuff (although I bet modern CPUs can easily do the DSP stuff now).
Not sure is Asterix handles all that... I don't know it at all. But 3Com do sell some specialised hardware that can't easily be done in software.
(I don't work for 3Com anymore.)
I knew you were going to say that!
It's not offtopic, dumbass. It's orthogonal.
AHEM. You can setup a full blown system using Ruby on Rails + RAGI (Ruby Asterisk Gateway Interface). I created one from scratch and in under a week I had a system that communicated via Jabber, persisted data with Rails, and called people taking some poll information. I did it for my WoW guild so that all the guild members could be notified when one of the green dragons spawned (Lethon, Emeriss, etc). The phone call would ask the user if they would be able to come online, and that information would be then persisted.
:-D
This took 1 week, with unit tests, web framework, jabber framework, and asterisk functionality. Check out our guild, The Transcendent on Medivh
"It will run Linux"? I would rather have "It will run on Linux"?
Leave to /. to talk briefly about the content of the article and the solution and focus in on the syntax of the post itself...sheesh. Anyway, enough of that rant.
3Com was at the Spring COMMON user group conference (for System i) in Minneapolis last week showing this.While at the moment they're running it on an xSeries server, the System i port is forthcoming. I had some time to speak with them about it, and like what I see.
I have to say this was a really slick solution and as a System i, iSeries bigot, a great use of the platform.
K.
This was invented, coded, utilized and eventually faded away into oblivion by a company named Dynamicsoft back in 1999. However, since Dynamicsoft did not believe in patents and insisted on open standards for everything, as well as targeting massively sized telephony operators that loved to toss them around like a dog's chew toy rather than getting decent money for enterprise solutions, they were eventually purchased by Cisco for penny's on the dollar, just days before the electricity was to be shut off.
No, I am not bitter... ok... yes, I am bitter.