Add your comments
DLS Archives
May 2012
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 | ||
Essential Windows Apps | Do Not Track | Microsoft Office | SayNow | LibreOffice | Zeam Android Launcher | Dead Space iPhone | Firefox 4 Mobile | Firefox 4 Release | PlayStation iPhone App | Excel Tips | Android Launcher | Google One Pass | Dead Space | Google Cloud Print | Songbird for Android | NBA Jam | Internet Explorer 9 | Windows 7 Connector for Mac | Office Mac 2011 | IE9 RC
Reader Comments (Page 1 of 1)
(Unverified)Oct 15th 2007 11:11PM
Woah guys what's with the sensationalism? I'm no fan of Microsoft, but honestly I have to say that it makes a lot of sense for a software company to stick with a software-only solution for a PBX. There are a lot of situations where a PBX does not need to interface with anything more than SIP phones and SIP trunks, and when it does it's far simpler for the PBX to only deal with SIP and let a gateway device (contrary to the writeup presented here, FXO, FXS, ISDN, PRI, etc. are both inexpensive and readily available) deal with the interface to the non-ip network, particularly if you want to try to wedge your software into every market in the world.
The notion of what has traditionally been considered a "phone system" is long gone, so I'm not sure what exactly the author means here when he uses the term. I know plenty of companies using IP-only "phone systems" and the Asterisk system I manage myself at work could easily be made "IP-only" if I implemented a different solution for faxes.
(Note that I have no idea what the call routing capabilities of OCS are, but surely it is enough to build a simple PBX out of!)