OR1 32 1.0 11/2017-E White Paper KARL STORZ OR1 FUSION IP Unified Communication and Virtual Meeting Rooms WHITE PAPER
Contents 1 Description KARL STORZ OR1 FUSION... 3 2 Microsoft Skype for Business (SfB)... 3 3 Information flow between KARL STORZ OR1 FUSION and the Hospital LAN... 4 3.1 Architecture for OR1 FUSION Clients... 4 4 Connectivity requirements... 5 4.1 Connectivity background information... 5 4.2 Bandwidth requirements: Skype for Business audio... 6 4.3 Quality of Service for Skype for Business... 6 5 Abstract Technical Specifications... 9 5.1 Unified Communication (UC) S4B cloud solution vs. backend server solution... 9 5.1.1 S4B cloud solution... 9 5.1.2 S4B backend server solution... 9 5.2 UC Video standard... 9 5.3 UC Network conditions... 9 5.4 Virtual Meeting Room (VMR) connection to non-unified Communication solutions... 10 5.4.1 VMR Protocols... 10 5.4.2 VMR Video standards... 10 5.4.3 VMR Audio standards... 10 5.4.4 VMR Network conditions... 10 2
1 Description KARL STORZ OR1 FUSION KARL STORZ OR1 FUSION is the name for a product aiming at integrating typical audio/video, documentation, checklist/workflow requirements, features, and functionalities for the OR environment into one single integrated system. 2 Microsoft Skype for Business (SfB) The KARL STORZ OR1 FUSION system optionally supports a videoconferencing module based on Microsoft Skype for Business (SfB). This module consists of a customized client coded to the Lync 2013 API. Therefore, it requires a backend Skype for Business server, whether it be in the cloud (e.g. Microsoft Office 365) or the hospital s own local or remote Skype for Business server. Unique new Skype for Business accounts are created for each OR on the Skype for Business system and the corresponding credentials are entered into the KARL STORZ OR1 FUSION videoconference modules configuration screen. No other configuration is needed for the router or the KARL STORZ OR1 FUSION system. KARL STORZ video system with Skype for Business Connectivity Skype for Business user with different endpoints Skype for Business PC endpoint LEGEND Skype for Business Laptop endpoint Skype for Business Mobile endpoint Skype for Business Browser endpoint * all systems require an active internet connection with appropriate bandwidth for the video down-/upstream Microsoft s Office 365 Cloud Service on the public internet* 3
3 Information flow between KARL STORZ OR1 FUSION and the Hospital LAN KARL STORZ SE & Co. KG (hereinafter: KARL STORZ) is a leading global manufacturer and distributor of endoscopes, medical instruments, and devices. Dimension Data supports KARL STORZ to provide a video service for endoscopic devices. Dimension Data provides a standardized approach for the solution and service required by customers of KARL STORZ. Endoscopic devices of KARL STORZ are video-capable and go beyond just transmitting video. KARL STORZ and Dimension Data partner to deliver a more collaborative, reliable, device independent and scalable video service. The video solution is seamlessly integrated into KARL STORZ endoscopic video systems. Today s endoscopic video system solution is based on Skype for Business (SfB) but with interoperability options to enable other video endpoints (non-sfb) to also join video conferences. KARL STORZ will deliver the product including IT services expertise to clients of KARL STORZ. Connectivity requirements to the different service components are described in Chapter 4 Connectivity requirements 3.1 Architecture for KARL STORZ OR1 FUSION Clients 4
4 Connectivity requirements Each video endpoint (with Skype for Business (any) client) must be allowed to access the public internet to connect to Microsoft s Office 365. Each video endpoint (with Skype for Business (any) client) must be allowed to access the public internet to connect to other video endpoints for direct video calls. Skype for Business selects and adjusts video codecs and therefore bandwidth utilization dynamically based on available bandwidth. However, it is recommended to have approximately 2.5Mbit/s for 720p / device stream available. The more devices the more bandwidth is available towards the public internet as well as on the LAN/ WAN (links). 2.5 Mbps is not a static/fixed value and the bandwidth required may vary. Quality of Service (QoS) is recommended Quality of Service (QoS) is only applicable on links / connections with defined service levels, e.g. LAN, WAN (MPLS-WAN). QoS is not applied on unmanaged connections, e.g. the public internet (https://technet.microsoft.com/en-us/library/gg425842.aspx). Please note that for cloud deployments Microsoft s Office 365 requirements must be met, e.g. the ones for connectivity. Office 365 / Skype for Business on the internet must be solvable via DNS. Note: Ensuring that connectivity is available to connect to the service is not KARL STORZ s responsibility as part of the proposed solution. Implementing QoS or any other changes of networking infrastructure is not KARL STORZ s responsibility as part of the proposed solution but can be requested if needed at an additional cost. 5
4.1 Connectivity background information Traffic on the Internet is considered to be best effort and all packets are treated the same with no prioritization. QoS settings on the corporate network do not carry over onto the Internet. Prioritization of Skype for Business media traffic is not possible for the entire path to Office 365 but can be prioritized right up to the point where it exits the network. Skype for Business uses Differentiated Services Code Point (DSCP) as the method of classifying types of traffic into priority groupings. These groupings are then used to prioritize packet transmission across the LAN. How DSCP works at a very high level is simply by marking each packet of data identified by source and/or destination port with a value. The DSCP marking is encapsulated into the network packet and transmitted over the LAN. Whilst the packet is in transit, switches and routers can read these values and determine how best to transport and deliver the packet to the destination. With Skype for Business two types of network traffic can be identified: SIP signaling and media traffic. Skype for Business media types are susceptible to packet loss and jitter as they are real-time communications for which QoS should be implemented by assigning DSCP values for: Audio Video Value Meaning Drop Probability Precedence Value Used For 0 Best Effort High Routine Non SfB Traffic 14 AF13 High Priority File Transfers 24 CS3 Medium Flash Application Sharing 34 AF1 Low Flash override Video 40 CS5 Almost None Critical SIP Signaling 46 EF None Critical Audio 6
4.2 Bandwidth requirements: Skype for Business audio Provision the network links to support throughput of 65 kilobits per second (Kbps) per audio stream, if they are enabled, during peak usage periods. A two-way audio uses two streams, so a simple audio/phone connection will require 130 Kbps to cover each stream. 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 while still maintaining acceptable quality. Do not assume that this adaptability will mask the problem when a network is under-provisioned. 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. For links that cannot be provisioned correctly in the short term (for example, a site that uses very poor WAN links), consider disabling video for certain users. Provision the network to guarantee a maximum end-to-end delay (latency) of 150 milliseconds (ms) under peak load. Latency is the one network impairment that Skype for Business Server media components can t reduce, and it is important to find and eliminate the weak points. For servers that are running antivirus software, include all servers that are running Skype for Business Server in the exception list to provide optimal performance and audio quality. https://technet.microsoft.com/en-us/library/gg425841.aspx https://gallery.technet.microsoft.com/office/configure-qos-for-skype-cdea2e67 4.3 Quality of Service for Skype for Business Quality of Service is a combination of networking technologies that enables companies to optimize the end-user experience for real time audio, video and application sharing communications. QoS is commonly used when network bandwidth is limited and when there is network congestion, in practice bandwidth limitation and network congestion are always there so we must have QoS configured correctly to optimize end-users experience. QoS can be configured as end to end, so it is more useful for your media traffic to traverse over a Wide Area Network because on a Local Area Network you might not have network congestion and bandwidth issues. When talking about WAN, most organizations use Multi-Protocol Label Switching (MPLS). An MPLS network is an L3 WAN built by a service provider to provision bandwidth to many customers which guarantees quality of service (QoS), although QoS is always required. 7
Basically, all port ranges provided to Skype for a Business/Lync client are via band provisioning. This means that once your Skype for Business/Lync client signs in, they will start using these locked down port ranges, which are configured on Skype for Business/Lync Server with these ports being pushed down to Skype for Business/Lync clients. This occurs when a client initiates the media traffic using applications like lync.exe, communicator.exe and attendeeconsole.exe. All applications that utilize Audio/video, application sharing, file transfer ports will get DSCP (Differentiated Services Code Point) markings stamped by the Operating System via GPO (Group Policy Object). Operating Systems like Windows Vista, Windows 7, Windows 8 and Windows 10 utilize the Policy based QoS. Policy based QoS has the benefit of being able to restrict the QoS at the application level. This means that all client applications that utilize audio/video application sharing, file transfer ports that we configure for audio/video, application sharing, file transfer will get DSCP markings stamped. Below are the client applications with their executable file names: Office Communicator 2007/R2 and Lync 2010 communicator.exe Lync 2010 and Lync Attendant Console attendantconsole.exe Lync 2013, Skype for Business 2015 and Skype for Business 2016 Lync.exe Below are the port ranges and DSCP values with their media type: Media Type Communication Port Range Port Count DSCP Values Audio Conferencing Server 49152-57500 8348 46 Audio Mediation Server 49152-57500 8348 Audio Client 50020-50059 40 46 Video Conferencing Server 57501-65535 8034 34 Video Clients 58000-58019 20 34 App Sharing Conferencing Server 40803-49151 8348 24 App Sharing Clients 42000-42019 20 24 File Transfer Clients 40783-40802 20 14 Signaling Clients and Server 5060-5061 2 46 8
All clients need to be able to directly connect to Skype for Business Online on the following destination ports: (the IP addresses and FQDNs can be found in the Office 365 URLs and IP address ranges) TCP 80, 443 UDP 3478, 3479, 3480, 3481 Optional: UDP/TCP 50,000-59,999 (if older SFB / Lync / OCS client / connection to VMR are used ) Note: All mobile clients, such as ios, Android, Windows, Skype for Business/Lync 2013 Mobility clients will not utilize this QoS capability as it is only applicable to Skype for Business Windows and Skype for Business for Mac clients and IP phone devices which are registered directly to an internal Skype for Business/Lync pool Server on managed networks; QoS is not applicable for traffic routed over the Internet. Microsoft recently released Skype for Business on Mac client, which can tag traffic, but the OS X does not support this feature. Microsoft is working with Apple to support tagged traffic. However as of now it is not working. Note: Office 365 reserves the right to update IP ranges and ports for Skype for Business Online. If a malfunction occurs after the successful commissioning, the following link and the firewall settings should be examined. https://techcommunity.microsoft.com/t5/skype-for-business-blog/simplified-portrequirements-for-skype-for-business-online/ba-p/77094 https://techcommunity.microsoft.com/t5/skype-for-business-blog/updated-ip-ranges-andports-for-skype-for-business-online/ba-p/47470 9
5 Abstract Technical Specifications 5.1 Unified Communication (UC) S4B cloud solution vs. backend server solution The KARL STORZ OR1 FUSION Unified Communication (UC) module consists of a customized UC client in KS design. Therefore, it requires a backend server, either located in the cloud or in the hospital network. 5.1.1 S4B cloud solution The provision of a cloud solution is part of the KARL STORZ offering. 5.1.2 S4B backend server solution A backend server solution, located in the hospital network, is not part of the KARL STORZ offering. Such a solution is the responsibility of the hospital / customer. Ideally this would be provided and supported by the hospital IT or a local IT supplier. If not, we can connect the hospital / customer to our partner. In this case the partner will take over responsibility and will cover all activities. 5.2 UC Video standard Video Standard: H.264 SVC Max. Video resolution: 720p/30 5.3 UC Network conditions Bandwidth: For 720p30 a minimum of 1000 kbps is required. We strongly suggest the provision of 2560 kbps (supports up to 1080p60) Jitter, Packet loss, Delays of video and audio: May vary depending on the infrastructure of the hospital network. Connectivity between a Skype for Business client and the hospital network to Skype for Business Online must meet these following network performance requirements and thresholds: Metric Latency (one way) Latency (RTT or Round-trip Time) Burst Packet loss Packet loss Packet inter-arrival Jitter Packet recorder Target < 50ms < 100ms < 10% during any 200ms interval < 1% during any 15s interval < 30ms during any 15s interval < 0.05% out-of-order packets 10
5.4 Virtual Meeting Room (VMR) connection to non-unified Communication solutions The connection to non-unified Communication solutions is possible via the KARL STORZ OR1 Virtual Meeting Room. 5.4.1 VMR Protocols SIP, H.323, WebRTC, Microsoft Lync, Microsoft Skype for Business, PSTN. 5.4.2 VMR Video standards H.261; H.263; H.263++; H.264; H.264 SVC; VP8. 5.4.3 VMR Audio standards G.711(a/μ); G.719; G.722; G.722.1; G.729; G.729A; G.729B; Siren7; Siren14; Opus; SILK; MPEG-4; AACLD; Speex; AACLC. 5.4.4 VMR Network conditions (See details on Unified Communication on previous page.) It is recommended to check the suitability of the product for the intended procedure prior to use. 11
KARL STORZ SE & Co. KG Dr.-Karl-Storz-Straße 34, 78532 Tuttlingen/Germany Postbox 230, 78503 Tuttlingen/Germany Phone: +49 (0)7461 708-0 Fax: +49 (0)7461 708-105 E-Mail: info@karlstorz.com www.karlstorz.com 96292001 OR1 32 1.0 11/2017/EW-E