diagerma.blogg.se

In this scenario, let the elasticity of the Skype for Business Server media endpoints absorb the difference between the traffic volume and the peak traffic level, at the cost of some reduction in the voice quality. In an under-provisioned network, the ability of the Skype for Business Server media endpoints to dynamically deal with varying network conditions (for example, temporary high packet loss) is reduced.įor network links where provisioning is very costly and difficult, you may have to consider provisioning for a lower volume of traffic. Do not assume that this adaptability will mask the problem when a network is under-provisioned. To cope with unexpected spikes in traffic and increased usage over time, Skype for Business Server media endpoints can adapt to varying network conditions and support three times the throughput for audio and video while still maintaining acceptable quality. Video will likewise use 1000 Kbps total to carry an upstream and downstream connection. A two-way audio or video session uses two streams, so a simple audio/phone connection will require 130Kbps to cover each stream. Provision the network links to support throughput of 65 kilobits per second (Kbps) per audio stream and 500 Kbps per video stream, if they are enabled, during peak usage periods. To provide optimal media quality, do the following: If you use Internet Protocol security (IPsec), we recommend disabling IPsec over the port ranges used for A/V traffic. If your organization uses a Quality of Service (QoS) infrastructure, the media subsystem is designed to work within this existing infrastructure. For details, see Edge Server scenarios in Skype for Business Server. If you have an Edge pool and are using a hardware load balancer, you must use public IP addresses on the Edge Servers and you can't use NAT for the servers or the pool at your NAT-capable device (for example, a firewall appliance or LAN switch. For details, see Port and firewall planning. You can't configure the internal firewall to perform NAT. If you are deploying a single Edge Server or an Edge pool using DNS load balancing, you can configure the external firewall to perform network address translation (NAT). Network requirements for audio/video (A/V) in a Skype for Business Server deployment include the following: In Enterprise Edition topologies, most servers should be in a network that supports more than 1 Gbps, especially when supporting audio/video (A/V) conferencing and application sharing.įor public switched telephone network (PSTN) integration, you can integrate by using either T1/E1 lines or SIP trunking. In Standard Edition topologies, servers should be in a network that supports 1 Gbps Ethernet or equivalent. The size of the LAN depends on the size of the topology: In general, you should connect all server roles within the Skype for Business Server topology using a low latency and high bandwidth local area network (LAN). The network adapter of each server in the Skype for Business Server topology must support at least 1 gigabit per second (Gbps). Likewise, if your network involves wi-fi as well as wired access, the whitepaper Delivering Lync 2013 Real-Time Communications over Wi-Fi is a good reference and is equally applicable to Skype for Business Server. While the content refers explicitly to Lync 2010 and Lync 2013, the considerations for Skype for Business Server are unchanged. The information in these topics is also discussed in the whitepaper Network Planning, Monitoring, and Troubleshooting with Lync Server with additional details and depth.

Summary: Review the network component considerations below before implementing Skype for Business Server.