

Web conferencing traffic from your Front End Server or each Front End Or Front End pool to your Edge Server internal interface. Outbound SIP traffic from your Director, Director pool, Front End Server STUN/TURN negotiation of candidates over TCP on port 443 STUN/TURN negotiation of candidates over UDP on port 3478 SfB Edge Port Overview Skype for Business Edge Server Port Overview SfB Edge Port Table Edge ExternalĬlient to Server SIP traffic for external User accessįor federated and public IM connectivity using SIP I put these now in a little graphic with colorized table.

Microsoft has an article describing that for Edge Servers quite fine ( ). When deploying a Skype for Business Edge Server, fulfilling the network requirements is absolutely essential and sometimes challenging.
