After my last epistle, a number of you seem to identify with the Old Guy Who Breaks Things (hereby referred to as OGWBT) - and since there may be more of us than I thought, let’s look more deeply into the key skill areas of the role.
It's day 2 at Microsoft Ignite Orlando, and we've had the announcement many of us in the industry have been waiting for: Skype for Business Server 2019 will be released towards the end of 2018.
The IT Department of the University of Tasmania looks down on Sandy Bay from the top of the campus. The Centenary Building overlooks the footy oval at the bottom of the hill. So there was nothing for it but to wheel a 55” Surface Hub, in contravention of University statutes and presumably Microsoft’s official guidance, out the back door, across a main road and, zig-zagging between ramps and lifts, all the way down the hill…
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.
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.