Tuesday, June 23, 2015

MS Ignite BRK3151 - Interoperability with Skype for Business

As promised in my Microsoft Ignite 2015 - Sessions, Venue, Expo post, here comes another summary / review of one of the Ignite Skype for business sessions.

Presented by Adam Gent, Enghouse.

Two programs exist, one older (mainly for Lync) and one newer for Skype for business.
There are many areas where interoperability comes into play when implementing a Lync / Skype for business system.

Use this like a checklist

The interoperability program started with telephony equipment, this is natural since telephony is much more real-time sensitive and business critical than email or instant messaging. First gateways were used heavily and later SIP Trunking became increasingly popular, both types of PSTN connection is now in the interoperability programs.

Why would we put a SBC in front of the mediation server when doing SIP Trunking?
A SBC can handle "malformed" SIP-packets and keep the mediation going even if the traffic is bad (but to what use?) A mediation server is not built to do policing on the incoming traffic while a SBC is. A SBC can also act as a firewall to protect an internal network.

How should an internal Wifi network with Skype for business mobile clients be handled?
Treat it like an external network and let all traffic go through the Edge/RevProxy.

What is the difference between Compatible, Certified and Optimized in the interoperability program?
It is a terminology mess that should be cleaned up. Not all "levels" exist for all types of devices / solutions.

No comments:

Post a Comment