Things to consider with non-certified OCS Voice Endpoints

This was something I came across for customers who are buying non-certified UC endpoints since this has been a popular direction in Education:


What does it mean to for a voice endpoint to be certified for OCS 2007?


The OCS Voice endpoint needs to have the logo above for it to be certified for OCS 2007.



This is an excerpt from the UC product team:

Where are the certified OCS devices listed?

As part of a customer's OCS voice deployment, Microsoft recommends telephony devices that carry the "Optimized for Microsoft Office Communicator" designation.  Microsoft has certified these devices for use with Microsoft Office Communications Server and Microsoft Office Communicator.  Certified devices offer plug-and-play installation, seamlessly integrate with Office Communicator, and support wideband audio to deliver an optimal end user communications experience.  The current list of certified devices can be found at:

How do non-certified devices work with OCS?

We understand that some IP phone vendors are offering IP phones that are advertised as working with Office Communications Server as native endpoints.  This is possible because Microsoft has published the open-standards-based interoperability specifications for Office Communications Server and Office Communicator as a part of the Office Protocol Documentation found here:

Any IP phone advertising OCS compatibility that is not listed at is not a certified device. Because these IP phones have not gone through the certification process, Microsoft takes no position on the level of compatibility that these phones offer with OCS.  Non-certified IP phones are neither guaranteed nor supported by Microsoft to work with Office Communications Server or Office Communicator.  Further, they may not offer the benefits of plug-and-play, wideband audio and tight hardware/software integration of  certified devices.

What should I be aware of with Non-certified Voice Endpoints?

  • Does the vendor provide a complete detailed list of supported OC client features? Are all client features implemented in a way that is compliant with OCS architecture
    (multiparty voice calls, firewall traversal)?
  • Does the product work in all supported OCS topologies (Federation, mobile user)? How extensively and in what scenarios has the vendor tested compatibility of their device?
  • Is the vendor committed to updating the device and firmware to align with future releases of OCS? What terms does the vendor offer for keeping the device up to date with the latest OCS releases?
  • Does the vendor offer worldwide product availability?
  • What are the vendor's warranty terms against defective software and design? What is the support model offered by the vendor?

Microsoft recommends the purchase of certified devices.  Microsoft cannot offer any support or assurances as to the compatibility of non-certified devices with Office Communications Server.    Ultimately, it is a decision between the customer and the vendor whether to utilize non-certified devices.  Microsoft cannot participate in this process in any way beyond what is outlined above.

What else should I consider?

Current and  Office Communications Server Future Feature Support

- Upgrade path and compatibility with future releases of Office Communications Server

- Unified Messaging

- Voice Mail integration

- Multi-party ad-hoc conferencing

- Desktop integration

User Support

- PIN based provisioning

- Remote-troubleshooting

- Device manageability

Telephony Services

- E911

- Call Parking

- Malicious Call Trace

Comments (2)

  1. markga says:


    Understood, I took that quote from the product team.

    The point of the post was to clarify the differences between OCS certified and OCS ready. The good thing is you do have choices in your UC endpoints and if snom works for your environment great just be informed about the differences.

    I don’t run the certification program so I can’t comment on that but I would love to see more UC endpoints certified including snom.

  2. A happy snom 820 OCS edition user says:

    Hello Mark,

    thanks for this excerpt. One small part needs a correction: "We understand that snom IP phone vendor is offering IP phones…" 😉

    It must be a singular not plural 🙂 Anyway one newsletter which included this excerpt to all MS UC partners was the best advertisement for the vendor ever. They never received so much requests on one firmware. 🙂

    I agree with all considerations mentioned before and also understand the challenge in support politic. But please also keep in mind there is no OIP program atm for ip-phone vendors to qualify or certify. Even all qualified devices are not certified, if you
    read the logo literal. Have you ever tried to get support from LG-Nortel or Polycom regarding the optimized for Communicator devices? Normally they will not be able to help and refer you to MS.

    Please don’t judge the big portfolio of unexpected devices too early. I think it is worth to get hands on the devices an see what they can. If you look at Tim’s Blog you get a feeling for the potential. Additionally you can combine this with the 870 movie on youtube


    Jan Boguslawski

    btw: I am not a snom employee, just a principal supporter, who will not have any financial benefit.

Skip to main content