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.
Within the on-premises world, dial plans have been around for quite some time, and not just within OCS/Lync/Skype for Business. For most organisations, the way users were dialled on traditional PABX systems was by their extension. It was possible to look up a user in a contacts list and then dial them, but ultimately the unique identifier that was being dialled was the user’s extension. In the Microsoft UC world, this is less of a requirement: we search for people we want to communicate with by name, and when we dial, it’s the SIP URI, not a number that we call. That said, there are a few reasons why it’s still desirable to configure a dial plan:
When deploying Cloud Connector Edition, I would have to say that Sonus' CloudLink offering has made life a lot easier. A single 1RU appliance that houses everything I need to enable PSTN access for Skype for Business Online CloudPBX users, and also allow integration with existing on-premises solutions the customer may be migrating away from.
"I didn't know it could do that!" is a phrase we hear all to often.