This article describes all requirements and set-up steps for Skype for Business in order to use it with the Pexip Service Virtual Meeting Rooms (VMRs).
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:
- Ports and protocols for internal servers in Skype for Business Server
- Set up your network for Skype for Business Online (excl. in China operated by 21Vianet)
How do I configure my Office 365 to access Pexip Service VMRs?
Open the Microsoft 365 Portal and go to “Admin” -> “service settings”
Select “IM, meetings, and conferencing” and switch “external communication” to ON
Please note that you may have to wait for up to 24 hours before the setting takes effect.
How do I configure my Microsoft A/V Edge Server to access Pexip Service VMRs?
You need to allow external user access on your Lync server in order to connect to a Virtual Meeting Room. We do support both Dynamic and Enhanced federation. The following configuration on the Lync server is needed to be able to dial from a Microsoft Lync client to a Virtual Meeting Room.
How to set up Dynamic Federation on my Microsoft A/V Edge server.
|The only configuration you need to add is under “External User Access” -> “Access Edge Configuration”. Here you need to enable “Enable federation” and “Enable partner domain discovery”.|
How to set up Enhanced or Direct Federation on my Microsoft A/V Edge server.
|The only configuration you need to add is under “External User Access” -> “Federated Domains”. Here you need to add a new ‘Allowed domain’ and fill out the ‘Domain name’. The domain name should be vmr.vc.|
Can I use the same domain for Skype for Business (Lync) users and video endpoints?
No. 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. There are no records of this user externally. Registering the same domain for Skype for Business and another service infrastructure breaks the combined protocol architecture of DNS and SIP (it is violating the RFCs).
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 (example.com). When the Skype for Business user calls the VMR (1), a connection is established. 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. As the user is not registered, there is no route back to the endpoint and the connection terminates.
Figure 1 - Skype for Business and other video users are on the same domain
With separate domains between Skype for Business and other video users, the Skype for Business domain will not be registered on Pexip's service, and the route back to the Skype for Business user is maintained throughout the call. To avoid additional costs for purchasing multiple domains, the calling domain for the Pexip Service can be a subdomain (e.g. vc.example.com). See Figure 2 below.
Figure 2 - Skype for Business and other video users are on separate domains
Please also see this site for additional information: https://lyncdude.com/2014/05/29/complete-guide-troubleshooting-lync-federation/