Towards the end of 2015, it was with great joy that the world welcomed the Polycom Trio 8800 conference room device into being. Prior to this, the conference phone of choice for Lync/Skype for Business deployments was the Polycom CX3000: a somewhat ageing platform that was still running Lync Phone Edition software, which Microsoft is no longer actively developing. Under the hood, the new Trio was running a version of Polycom UCS software, which also supports Polycom's range of Lync/Skype for Business certified VVX handsets. We now had a conference room device that no longer relied on Microsoft's Phone Edition software.
In a previous blog, I discussed the added benefit of PSTN Conferencing capabilities when used in conjunction with Skype for Business Online. Meeting participants could continue to join from their Skype for Business client or a web browser, but now they could also choose to join via phone: very much still an important use case. In addition to this, Microsoft have made available dozens of PSTN access numbers across the globe that your meeting participants can dial and participate in your Skype for Business Online meeting – very handy.
In a previous blog, I walked through how to ensure Trio meeting room devices received the right configuration file from the Polycom Provisioning Server. Whilst the approach I outlined then is still valid, I'd like to share a much simpler way that minimises the possibility of incorrect configuration making it onto your Trio devices.
Late last year saw the release of Polycom’s latest Lync/Skype for Business certified conference phone: the Polycom Trio 8800. Polycom also surprised most of us with not only audio, but video capabilities, when the unit is paired with the Visual+ module. In my opinion, this is the perfect device for the small to medium size meeting spaces that were too small for larger VC infrastructure solutions, but where audio and video capabilities made sense. You can read more about the Trio 8800 here.