Polycom Real-time Media eXperience (RMX) Platform is Qualified for Lync 2010
OCS and Lync interoperability along with RMX is nothing new, in fact integration with OCS dates back as far as 2009. Nevertheless the RMX hasn’t (until now) reached the accolades of Microsoft qualification status.
So what does qualification really mean?
In some cases vendors go from zero interoperability/ functionality to qualified status overnight, obviously in this scenario this isn’t the case so qualification means a little less – but it’s still a big deal and I’ll go on to tell you why…
Qualified devices are certified by Microsoft, they undergo weeks of pre-defined testing (100+ test cases) and are version specific, in this case Lync 2010.
Passing these tests results in:
a) the respective vendors device being listed within the Microsoft Unified Communications Open Interoperability Program (UCOIP).
b) customer peace of mind that the equipment adheres to a requirements specification laid out by Microsoft.
c) passing all the associated test cases within a Microsoft lab.
The RMX 7.7 release was submitted as a RMX 1500 qualified configuration (strictly speaking if you followed the Microsoft qualification law only this device has been “blessed” – however near identical software is utilised on the 2000 and 4000 models), which is now available publicly here. In addition to qualification a number of other Microsoft Lync related features are delivered as a part of this release, namely:
- Polycom, Microsoft and Cisco bridge interoperability – this is the ability to host multi-party video conferences on the RMX with video endpoints from multiple vendors. In the case of Cisco, signalling is handled via the integration of Cisco Unified Call Manager (CUCM) and Polycom’s Distributed Media Application (DMA).
- Microsoft RTV forward error correction (FEC) support – with this feature the RMX is able to support Lync error correction in scenarios where there is connection instability.
- ICE over TCP – When ICE over UDP is blocked by a Firewall, the ICE connection automatically uses TCP.
- Media over TCP – as with above, when media is unable to utilise UDP due to Firewall policies etc., the RMX will automatically switch to TCP.
- Additional Virtual Meeting Room (VMR) presence mode – prior to this release VMRs enabled for presence would only display as available, the 7.7 update introduces the busy state when busy or in use.
- Error recovery – RMX 7.7 can automatically recover from short duration network errors (up to 5 seconds), enabling video or audio conference calls in Microsoft Lync to continue without disconnecting.
- Lync AVMCU to RMX Cascading – Last but not least (and a personal favourite) the ability to connect a Lync video conference call to the RMX by transparently joining the two meetings, hosted on their respective MCUs, via end-user drag/drop within the Lync client.
For a full list of features within RMX 7.7, refer to the release notes here
Update: The RMX has now been listed within the UCOIP here