Europe, no additional clustering configuration is required on the Pexip platform. The deployment process assumes that the Management Node and the Conferencing Nodes have already been configured with basic settings, such as an IP address and NTP server, and that the Conferencing Nodes have already been configured with one or more Virtual Meeting Room aliases for the SIP domain to be used, such as all of the Conferencing Nodes in the application pool are all deployed in the same system location e.g. * Note that where this documentation refers to " SfB/Lync", it represents both Microsoft Skype for Business and Lync unless stated otherwise. In Skype for Business / Lync deployments it is essential that a Conferencing Node can discover its NAT address. However, if the Conferencing Nodes are behind a NAT then they do need access to a STUN/TURN server so that each node can discover its NAT address.
Conferencing Nodes do not need to use a TURN server for media routing to remote or federated SfB/Lync clients, providing they can reach the public-facing interface of the SfB/Lync Edge server. In this type of integration the Pexip Infinity Conferencing Nodes typically will reside on a private IP network. This topic describes the configuration required on the Pexip platform to integrate Pexip Infinity with an on-premises Skype for Business / Lync * environment. Pexip Infinity configuration for an on-premises Skype for Business environment
0 kommentar(er)
