With separate domains between Skype for Business and other video users, the Skype for Business domain will not be registered on the Pexip Service, and the route back to the Skype for Business user is maintained throughout the call. As the user is not registered, there is no route back to the endpoint and the connection terminates.įigure 1 - Skype for Business and other video users are on the same domain
However, when the VMR sends a first SIP UPDATE message (2), the Pexip Service recognizes the domain is registered in own infrastructure and searches for the user. When the Skype for Business user calls the VMR (1), a connection is established. In Figure 1 below, the Skype for Business user (sfb_user) and the other video conferencing system (meeting_room) are both registered on the same domain (). Registering the same domain for Skype for Business and another service infrastructure breaks the combined protocol architecture of DNS and SIP (it violates the RFCs). There are no records of this user externally. The service will not be able to find a route back to the caller, as the Skype for Business user is local to the customer’s network only.
For Skype for Business on-premises server deployments, Skype for Business Edge Server is needed for communication with external users. Please follow the Microsoft documentation for each of the different environment deployments to ensure that firewalls are not blocking any communication of your Skype for Business clients or servers: System Requirements Microsoft Server : Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019, Office365. This article describes the requirements and environment set-up steps for Skype for Business to use it with Pexip Service Virtual Meeting Rooms (VMRs). Skype for Business requirements for use with Pexip VMRs