Got Enough Bandwidth for OCS R2?

One quick point for today. When implementing an OCS 2007 R2 setup, make sure there's plenty of bandwidth available. Standard or Enterprise edition. With or without VoIP built-in.

One of our clients (a nationwide energy firm) uses OCS to communicate between branches. Initially this was facilitated by T1 lines. However a few weeks ago, we upgraded them to a DS3 line.

They'd had some issues beforehand - garbled calls, lost IM transmissions, general stability. Most of it came from problems the Unified Messaging server had.

That all vanished when the DS3 line was put in. Poof. More bandwidth = no more connection troubles. Just like that.

Not sure how much bandwidth you have available? Use Speakeasy's Bandwidth Speed Test. Compare the results to the Three UC Amigos' OCS 2007 Bandwidth Requirements . (Alternate reference: Mark Garcia's OCS Web Conferencing Bandwidth Charts.)

Which Voice Gateway Should You Use for OCS?

Here’’s a list (Microsoft Technet) of Direct SIP Gateway and IP-PBXs approved for use with Office Communications Server.
http://technet.microsoft.com/en-us/office/ocs/bb735838.aspx#direct

Obviously, we haven”t tested them all. I can only give you what we”ve learned on our own install (and subsequent client installs).

Aculab - The ApplianX Gateway

The ApplianX Gateway for OCS 2007 was the first voice gateway we tested.

This gateway was designed to interface between OCS-based VoIP and the regular PSTN. One of the first to do so in the world, in fact.

The ApplianX Gateway is capable of handling 240 VoIP calls at once. In terms of voice quality, it’’s great, but I did notice one thing: the longer you were on a call, the more packets got lost. Words would start falling out of the conversation. I”m not sure this was a problem with the gateway however, or with our bandwidth allocations.

I do know that it went away before we switched to Dialogic.

Dialogic - The DMG2000 Media Gateway

When we upgraded our OCS to R2, we switched to a Dialogic Media Gateway. I don”t see any reason to change again.

None of the fabled VoIP problems happen - no “I can hear myself in echo,” “They can”t hear my voice,” or “The calls break up on us all the time.” Client installs have gone smoothly.

Another handy thing about Dialogic is the guides they post on their site. You can downoad white papers, datasheets and configuration guides for all their media gateways, free.
Dialogic.com Downloads

Other Choices

  • Quintum’’s Tenor Gateway is highly-rated in the industry.
  • Cisco has a gateway available, but some interoperability issues do exist. See the Cisco Interoperability Portal for more on that.
  • As a general rule, avoid a gateway that isn”t rated for R2. You”re almost guaranteed problems when OCS 2010 is released.

Which is the Best Choice for a Voice Gateway?

The best gateway choice is the one that will allow everyone in your office to make voice calls, handle the load, and still be open for expansion down the line. So it pays to consider these factors in your research.

Size of business. If you”re a smaller business or startup, try Aculab or Dialogic. Over 40 employees? Dialogic is my first recommendation, but the Quintum may work well for you.
Expected call volume. If you”re enterprise-level and have a call volume in the hundreds (or thousands), consider the devices rated for “Direct Sip via IP-PBX.” Otherwise, look at Cisco or Dialogic’’s Enterprise Media Gateway.
OCS version. The Aculab ApplianX Gateway isn”t certified for use with R2. I”m hoping for an upgraded version by the time OCS 2010 rolls out. Go with any of the others rated for R2.

Four Predictions on OCS in 2010

Welcome to 2010! Are we back to scrambling already?

Before we get too crazy, let me make a few predictions about OCS. (It’’s the thing to do this time of year.) We”re headed for another year of big shake-ups and racing towards better-priced options. I”m sure Office Communications Server will be involved in some of it. Though I”ll freely admit, I may deny one or two of these by the time 2011 rolls around.

Prediction #1: OCS 2010′’s release will come with calls to end the PBX. It won”t…not yet.

Office Communications Server 2010 is slated for release either in Q2 or Q3 2010. We”ll hear a lot of buzz beforehand, along with calls to 100% replace PBX phone systems with OCS. (I”m not actually the first to say this.)

If it truly is a PBX-killer - and I”m hopeful it is - then these calls will be justified. However, OCS adoption over PBX won”t begin in earnest until 2011. It takes time to make such a big change - time to get used to the idea, and time to plan the change itself. Smaller companies will get a jump on OCS 2010 instead. They don”t always have a PBX to replace.

Prediction #2: OCS 2007 R2 will grow as a hosted service, even with OCS 2010′’s release.

I”m no economist; I won”t even try predicting what the markets will do this year. What I will say is that more companies will look for more ways to save. Startup costs, trying to grow without much budget, no desire to buy all-new servers…these factors will push more companies toward hosted services as a lower-cost option. Judging from the adoption rates and interest we”ve received, I”m expecting companies in the mid-to-upper range of SMBs to take the most advantage here.

Prediction #3: We”ll see a growing comfort with VoIP as a phone system.

Voice over IP is becoming a more accepted alternative to regular phone lines. In a way, we have Google and Skype to thank for this. The rampant popularity of Google Voice, and the popularity of Skype (even in business use) shows people are more comfortable with the idea of using the Web for voice communication now.

When OCS 2007 first came out, many people didn”t trust its VoIP capability as a reliable phone system. That was just 2 years ago. Now that technology has caught up and social adoption is higher, that lack of trust won”t be applied to OCS 2010.

Prediction #4: OCS 2010′’s 64-bit structure may discourage some from upgrading.

There is a problem in all this. OCS 2007 R2 is available only in 64-bit. Exchange 2010 just shipped with a 64-bit version. It’’s not hard to imagine that OCS 2010 will be 64-bit only. This will cause some sticking for those companies who haven”t moved to 64-bit servers yet; upgrading to OCS 2010 would mean buying new 64-bit servers. For those companies looking to SAVE on communications, spending extra is a contradiction. And a big upgrade objection.

(There’’s always the hosted option though!)

A few things to think about. Overall I think OCS” prospects are good, even with the 64-bit snag. Some will say the new smartphones coming out are a danger to OCS, but I think they have a more complementary role than a competitive one. We”ll have to see where 2010 takes us, won”t we?

Technorati Tags: