A Peek at Next Year's Model - More Features of Communications Server 14
Filed under: OCS 2007 R2, OCS 2010, Unified Communications
I'm back! I'd talk about my trip, but it's not OCS-related.
However, we did get a few responses to last week's query. The majority were questions about Communications Server “14.”
And as luck would have it, we have something to discuss along those lines!
Brent Kelly of the “No Jitter” blog posted a VERY thorough overview of Communications Server 14 on Sunday. (With pictures!)
He obviously gleaned much from the TechEd conference. The six-page article is a comprehensive discussion of CS14's capabilities, changes from OCS 2007, and so on. Read it for yourself here (but after you finish this post!):
Under the Hood of Microsoft Communications Server 14 - NoJitter.com
Really, I can't do a better job. All I want to do today is give a thumbs-up to Brent for his good work. And highlight a few of the points from his article here.
Four More CS 14 Features to Note
- The “physical server requirement” that hampered OCS 2007 has been removed. CS14 allows you to host many of its servers on one physical server. Instead of four.
- (This is a separate consideration from the virtualization I mentioned last time. Virtualization is not necessary in this case - but you can still use it.)
- CS 14 will support E911.
- You'll be able to control the whole CS 14 from its new Silverlight-based Control Panel Interface. Configuration, routing, and policy rules are all accessible from there.
- The “contact card” that shows a person's information has been expanded. It also comes up when you hover over the contact's name, instead of hitting Alt+Enter as in OCS 2007.
Finally, just something for OCS fans to remember. An official name for the next version of OCS has not been officially announced yet. So far, all the names by which this version's going are:
- OCS 2010
- Communications Server 2010
- Communications Server “14″
- “CS 14″
When the official name is announced, you'll see it right here!
No Response, Please Try Your Call Again
The OCS Insider will be back next week. I'm heading out for a business trip in just a few minutes. I'll be back in time for next week's post.
Speaking of, which of these topics would you like to hear more about?
- OCS 2007 R2 Support
- OCS 2010
- Voice over IP
- Using OCS for Conferencing (audio or video)
- OCS-Related Hardware
- Usability Tips
Leave a comment, or email me and let me know! Catch you all later.
Rename and a Revamp - New Features of Communications Server 14
Filed under: Conferencing, OCS 2007 R2, OCS 2010, Unified Communications, Voice over IP
Last week at TechEd, Microsoft announced the new features of Communications Server 14. Frankly, I”m not sure why the new version is named “14.” But that's not what I wanted to write about anyway.
What I'm blogging about today is a few of the features announced. More specifically, how those features translate into new benefits for small business OCS users.
Many of 14's updates focus on simplification: Easier administration, more unified front-end interface (Unified Communication - get it?). The main small-business advantage comes from a more comprehensive client application. All communication channels ready and waiting for you.
1. The Rise of Communicator 14
Every service goes through the Communicator 14 client. Live Meeting was originally separate from the Office Communicator 2007 client. (They were developed separately at first.) Communicator 14 has it built in. All conferencing capabilities, in fact…along with IM, voice calls, Presence, even a visual Voicemail menu.
2. More Roles Virtually Capable
In 14 there's support for virtualizing almost all OCS server roles (AV Conferencing, Archiving, Edge Mediation, etc.). Putting in a new Communications Server 14 setup becomes more appealing if there are fewer physical servers needed than for OCS.
3. Web Client Following You Around
14 includes a new Silverlight-based web client version of Communicator. Very handy if you have people who live on netbooks or smartphones. I've played with Silverlight a little too; this client is almost guaranteed to be much faster than CWA.
4. Avoid the Media (Server) and Still Call the Office
There's a new media bypass, reducing the need for a mediation server. It allows a front-end server to go “direct SIP,” meaning you can call into (supported) PBX phone systems without mediation. In other words, simpler setup, and you can still call non-VoIP phones.
5. Alert! Call #2467 is Failing!
I really like this one. There's a new Monitoring Pack in Communications Server 14. If calls are failing or their quality drops, alerts will show in the Monitoring Pack. You can even boost the audio quality if it’’s degrading!
6. SQL Backend Moved to Express Lane
The Director server role will include a SQL Express database in 14. So there's no more need for a separate SQL backend. That means even fewer servers running.
There's even more features than these too. A very thorough overview is on the “Inside OCS” blog.
A smaller, more streamlined communications system. Appealing to small business cost and space concerns, wouldn't you say?
What are you looking forward to in Communications Server 14? Drop us a comment and let's talk.
When Support Calls Go Awry!
Filed under: Conferencing, OCS 2007, OCS 2007 R2, Unified Communications
Or, The Many Components Involved in Running OCS-Based VoIP
A client of ours had lots of trouble getting Conferencing to work lately. We put in OCS for them only 4-5 months ago. Naturally, they called us and said,
“Your OCS is broken! We can”t conference now!”
“Quick, Fix It!” “Which Part?”
Of course we sent an engineer out at once. He quickly determined that the problem was not OCS by communicating with our office from it. But he COULD reproduce the conferencing problem.
So what was causing it?
It’’s times like this when we all remember that OCS is one part of a VoIP phone system. A critical part, but a part nonetheless. It’’s just the part that faces the user every day, in form of the Office Communicator application. So it gets the blame when another system component won”t behave.
And that’’s what happened with our client. After some investigation, it turns out the phone company providing SIP lines to their office was having issues. They told our engineer it would be fixed by the next day. It was.
To check, we conferenced with the client a day later. Sure enough, they heard us just fine.
Glad to Help, Once We Find the Problem
OCS has multiple components - servers (Standard, Edge, Mediation and CWA), SIP Trunking, IP-PBX Gateway, Internet connections, and Office Communicator. And sometimes it only takes one breaking to mess up the others. Aggravating, I know.
I figured this was a good opportunity to remind everyone about the many things involved in running VoIP. Every IT system has components. And they do their jobs for us. Most of the time.
Yes, OCS Works for the Small Business Market
Filed under: OCS 2007 R2, OCS 2010, Unified Communications, Voice over IP
Microsoft recently announced that they are discontinuing the Response Point small-business VoIP system.
They decided that while demand was encouraging, it wasn't enough to sustain Response Point as a standalone business. The Response Point Team suggests Microsoft OCS as an alternative.
This announcement was written about on several other websites, including ZDNet. Commenters on these posts had basically two things to say:
1. Response Point was a nice solution and they're sad to see it go.
2. A full OCS VoIP system is overkill for small businesses.
Is it? That's a question worth exploring. Does OCS actually work as a VoIP phone system for the small business market?
Frankly? Yes, it does. Very well in fact.
Hosted OCS Has an Easier Small-Business Setup
The key to this is in what kind of infrastructure a small business uses. In the past, there was pretty much one way to build an infrastructure - install servers in-house, wire a network and set up the workstations to use its capabilities.
Now with cheap broadband and hosted/cloud-based IT services gaining popularity, we have a viable middle-ground. One where up-front cost is low and competitors can offer more affordable pricing structures.
Microsoft said that Response Point didn't have high enough demand as a standalone business. Maybe an in-house OCS system might seem like overkill. But nobody said a hosted OCS solution wouldn't fit the small-business bill in Response Point's place.
Voice Over IP In the Coming Years
Response Point was a VoIP replacement for a small business PBX. Technologically, this can be done in OCS 2007 as well. OCS 2007 just needs phones.
Any good OCS partner worth their salt should have a VoIP option available. Suited for small business needs and budget.
With all that said, we can give a couple responses to the main question.
- VoIP options are growing all the time. Certainly small-business options will grow as well.
- With OCS 2007 R2 out for a couple years now, manufacturers have been creating more VoIP phone systems.
- There will be more VoIP emphasis in OCS 2010. This has been known for a while now.
- A small business communications system using OCS does work. Here are two examples, one using VoIP and one not:
- WITH VOIP
- Hosted OCS 2007 R2 for Instant Messaging, Conferencing and Voice over IP
- VoIP Phones
- WITHOUT VOIP
- Hosted OCS 2007 R2 for Instant Messaging and conferencing
- Cellphones for Voice
Were I to speculate on this, I'd say Microsoft folded some of its Response Point team into OCS 2010 development. I fully expect OCS 2010 to have full VoIP capability and then some. At a level small businesses can use easily.
