Is Linux Used in Production Telephony?

jamesva asks: "The telecommunications industry is rapidly converging on Windows NT/2000 for all telephony and voice-related needs. Most ACD systems, virtual operators, and voicemail are being ported to Windows if they're not already running on it. In the past, telephony apps have existed most notably on OS/2, SCO, and even DOS. However, free Unix (or unix-like) platforms have absolutely no penetration in this area, with seemingly no chance on the horizon. The Bayonne app server from the GNU folks seems to be the one exception, but even then there doesn't seem to much built around it or anyone using it. It reached a 1.0 release in September and was met with no fanfare. Even the LinuxTelephony doesn't seem to have much news. Can someone prove me wrong? Why is this the case? I'm interested in finding out if anyone is using Linux (or any free OS) in a production environment for something like voicemail or ACD. These types of systems require high availability and reliability and Linux just seems like a natural fit."

Comments

Simple: complexity

[LiamRandall]

In addition to our WAN/LAN I also run a medium size phone switch (195 nodes / 16 IP Phones / 2 PRIs for switched access / 1 dedicated Long Distance T1). When you get to the corporate level you're buying a solution; not building one in house, because phones are essential to the day to day operation of the company. Period. I think generically when you say phone switch you're referring to everything telco past the demarc; switch T1s/PRIs, operate internal digital stations, provide analog lines, route calls, manage security, reporting/tracking/billing, Voicemail, Auto Attendants, Hunt Groups, Digital Faxing- the whole 7 layer enchilada. Few corporations are going to allow their IT departments to go the Slashdot way w/ so much on the line. A modern phone switch must reliably scale to thousands of nodes including IP devices, support Unified Messaging (receiving faxes & voice mails through PC), have reporting right out of the box, must be easy to use, and work on the first cut over. While the word 'easy' is certainly a very relative word- in my experience most geeks (a word of complimentary endearment in my vocabulary) can easily master telco while the reverse is not often true. Believe it or not, in the old days these were sometimes the roles of separate administrators / departments.

You're right that *nix is a perfect fit for all of this; remember Unix was invented at Bell Labs. The auxiliary applications are there; to support your phone switch you need to reliably record and report all activity across your switch for billing, acct. tracking, etc. I would guess that *nix runs the backbone.

If you'd like you can become a dealer for the company that claims to have 'the world's first Linux technology based voice processing' including Unified Messaging.

By the way I think that Bayonne is encompassed in the umbrella project of GNUComm; hopefully it's just a matter of time before someone finishes the Embedded Linux Phone Switch. As an incentive to anyone who develops and releases a free system: even used handsets cost big money for a particular phone switch; pick wisely 'cause you're most likely stuck with it for a little while. Caveat: you will most likely be pushed out of the market by softphones.

Since you're in the market and I just went through this myself contact me off list and I'll share my experience with Inter-Tel Technologies which is one of the fastest growing companies in the US (short version: no I don't work there and overall positive).