I’m working on a fairly complex IP Telephony deployment for a client, the complexity comes because of their security requirements, plus the level of services they require.
At present, it’s pretty much about dialtone but immediately round the corner will be the requirement to deliver all wonderful services atop this such as presence, IM and Unified Messaging. This is where OCS comes in.
Now, over the years I’ve installed a number of integrated voice solutions for clients, years ago thinking a voicemail ending up in Exchange 5.5 was almost black-magic. However, I’ve never actually used such a system in anger (the companies I’ve worked for prefer eating pizza rather than dog-food, it seems).
Therefore, it seemed like a good-a-time-as-any to install OCS and have a play.
As I run a new-wave business, my office is also my home and the communications requirement consists of a business ADSL line and normal POTS, with a smattering of Blackberries, windows mobiles and 3G. First challenge was getting “permission” to play past the “boss”. I offered the idea that wouldn’t it be nice if when someone left an answering machine message, instead of being left at home, it was emailed to us. She agreed!
Firstly, it’s not much use if I cannot communicate with the outside world (and meet the key requirement of voicemail to email).
In a “real” scenario, this would either be delivered as a SIP provider assigning a number of trunks over an IP connection, or something like an ISDN30 with media convertors. But a quick Google tells me there are little boxes that’ll convert a simple analogue line to IP/SIP. And better still, they are cheap on ebay!
So, to the OCS deployment. Being ultra cutting-edge, I chose Windows 7 Server ….. Sorry Windows 2008 R2 as my OS of choice. Turns out OCS 2007 R2 doesn’t support that without a little hacking of the installer with orca.
The installer is certainly heavyweight and demanding. The out-of-the-box stripped down roles feature of 2008 is great, but if you are wanting to have a geeky play with tech it certainly adds a lot of hoops to jump through. In fact, it reminded me of installing an app in unix, where you find you have to download and make a dependency, which in itself needs another program……
But we get there. Just. Then I find out that realistically OCS is a 3-box deployment, and there’s no way to coexist. And I realise my Sunday should probably be better spent doing something than playing with technology.
Tune in for the next episode where hopefully I’ll have OCS talking (to something!)