microsoft teams skype for business integration

TRAP service is used by Microsoft Teams and Skype for Business/Lync 2013 clients with a different logic (Lync 2010 cannot leverage this service). This service is used by Microsoft Teams and, for now, by some O365 tenant allowing users to connect to the closest Transport Service to send real time traffic. Together with Microsoft Teams, a new service called Transport Relay (TRAP) is being rolled out to Office 365. If until now this problem was limited to a few on-premises companies, in the cloud era where all the users are connected “from outside” and in mobility, the network optimization became really important. Travelling across the sea has a cost in terms of performance and we all know how important the network performance is when it comes to Real Time communication. The same problem happens also on Skype for Business Online when an user belonging to an European tenant wants to use the Media Relay service when connected from another region.Īs you see in the flow above, when the user B is using the Media Relay server, he is connecting to the server in Europe.

This means that a user homed on that specific pool will always use that Edge server to relay the Media, no matter where the user is connected from. In Skype for Business an Edge media Relay is associated to a specific Front End pool.

One of the most frequent problems you probably faced when implementing a Skype for Business architecture was related to the media relay capabilities for users travelling around the world.

Microsoft teams skype for business integration