GTm 5140 Installation and Admin Guide 20 November 2017

Transcription

1 GTm 5140 Installation and Admin Guide 20 November 2017

2 Contents About the GTm 5140 codec 3 The connectors 3 LEDs 4 Dimensions 4 About the touchscreen controller 5 Lync/Skype for Business/Exchange requirements for StarLeaf GTm Lync/Skype for Business requirements 6 Exchange requirements 6 How to install GTm Configuring the GTm Camera presets 11 Mounting the GTm 5140 unit 13 Mount Dimensions 14 Typical installation of GTm Appendix: LED behavior 17 Network port LED 17 Appendix: Ports and protocols 18 GTm system connectivity 18 Outbound 18 Inbound 18 Internal for GTm On-premise Skype for Business 2015 or Lync Outbound 19 GTm on external network 20 Skype for Business Online 21 Outbound 21 Inbound 22 Legal information 23 Third party software acknowledgments 23 Disclaimers and notices 23 GTm 5140, 20 November 2017 Page 2 of 23

3 About the GTm 5140 codec About the GTm 5140 codec The connectors The figure below shows the connectors on the rear of the GTm 5140 codec. Power Telepresence screen 1 Network Microphone Telepresence screen V USB 2.0 Camera (USB 3.0) The table below describes the connectors: Connector Power Screen 1 Network Microphone Screen 2 USB 2.0 Camera (USB 3.0) Description A DC +19V power connector. The codec automatically adjusts to the supply voltage. Use the supplied power cable to connect the codec to the power. Connect all other cables before connecting the power Mini display connectors. These connectors output video (1080p60 only) to screen one 10/100/1000 Mbit/s auto-sensing Ethernet port. Connect to the network USB connector. Connect a StarLeaf microphone Mini display connectors. These connectors output video (1080p60 only) to screen two USB 2.0 connectors. If you are using a static USB camera, connect it to one of these USB 2.0 connectors USB 3.0 connector. If you are using a PTZ USB camera, connect the camera cable to the USB 3.0 connector Note: Your telepresence screens can be connected to either of the mini display ports, regardless of whether you are using one or two screens. GTm 5140, 20 November 2017 Page 3 of 23

4 About the GTm 5140 codec LEDs There are Power and Status LEDs on the front of the codec. LED behavior is described in Appendix: LED behavior (p17). Dimensions The GTm 5140 is designed so that it doesn't need to be rack mounted. However, it can be wall mounted or mounted to the back of your telepresence screen. Dimension Metric American Width 150 mm 5.9 in Depth 152 mm 5.98 in Height 57 mm 2.24 in GTm 5140, 20 November 2017 Page 4 of 23

5 About the touchscreen controller About the touchscreen controller The GTm 5140 comes with a touchscreen controller: the StarLeaf Touch You use the touchscreen controller as the means for making and controlling video calls with GTm Through the touchscreen controller, you can access the directory and contacts, recent calls, and also the screen-share controls when in a video call. The StarLeaf Touch 2035 GTm 5140, 20 November 2017 Page 5 of 23

6 Lync/Skype for Business/Exchange requirements for StarLeaf GTm 5140 Lync/Skype for Business/Exchange requirements for StarLeaf GTm 5140 Lync/Skype for Business requirements The GTm supports: Lync 2010 Server, Lync 2013 Server, Skype for Business 2015 Server Note: If the deployment is not a Lync 2013 server, ensure that the Lync 2013 user interface is enabled. Skype for Business Online The GTm needs: A user or room system account with Lync/Skype for Business enabled For on-prem deployments: if the Lync/Skype for Business server certificates were issued by a private certificate authority, the GTm requires the certificate of the Root Certificate Authority and any intermediate certificates. Microsoft has documented how to export Root Certification Authority Certificates Exchange requirements The GTm supports: Exchange 2010 SP2 Server Exchange 2013 Server Exchange Online The GTm needs: A user account or room resource with Calendar enabled and linked to a Skype for Business enabled account. Auto-responding to invitations is not required but supported Note: Conference invite s to the GTm must remain intact with necessary attachments in order for conferencing facilities to function correctly. Be aware that stripping attachments from s causes the Join Now button to stop working. Autoresponding to invitations can cause attachments to be deleted and you must configure it not to do so. Note: If you are using a room resource and would like to show the meeting title correctly on the GTm, refer to this Microsoft article. GTm 5140, 20 November 2017 Page 6 of 23

7 How to install GTm 5140 How to install GTm 5140 Before installing the StarLeaf GTm 5140, read the safety information at GTm 5140 safety and compliance. Pre-requisites Before installing the GTm 5140, ensure you have the following: One or two telepresence screens that support a 1080p60 input format Supported video camera StarLeaf microphone StarLeaf touchscreen controller Note: Ensure that the televisions have audio-output capability. Unpack the GTm The package contents are: Codec Installation sheet Wall mounting kit Cables Power cable Ethernet cable HDMI to HDMI cables (two) (connects codec to screens) Mini DisplayPort to HDMI adaptor for the codec-to-screen cables Positioning the codec 1. Ensure you have chosen an appropriate installation site: The codec must be accessible with all cables easily connected You must provide ventilation for the codec; leave a space of at least 10cm (4 inches) behind, in front, and to the left and right of the codec Use a grounded AC power outlet for the codec 2. Wall mount the unit or place on a firm horizontal surface. The codec is 57 mm (2.24 in) high. If you intend to mount the unit, refer to Mounting the GTm 5140 unit (p13). Connecting cables and peripherals Connecting network cables to the codec Using an Ethernet cable, connect the Network port on the rear of the codec to an Ethernet switch in your network. The Ethernet port is a 10/100/1000 Mbit/s auto-sensing port and is set to auto by default. Note: In all cases, the speed and duplex settings at either end of the connection must be identical. Using non-matching settings causes severe packet loss. To configure the network speed and duplex settings of the codec s Network port: on the touchscreen controller, go to settings > networking > network port speed. GTm 5140, 20 November 2017 Page 7 of 23

8 How to install GTm 5140 Note: By default, the GTm 5140 uses DHCP to acquire an IP address. If necessary, you can configure the GTm 5140 with a static IP address, to do so: On the touchscreen controller, go to settings > networking, switch off DHCP and edit the IP address, netmask, gateway, and nameserver fields. Connecting the camera and microphone 1. Connect the camera to the GTm with the USB cable: If you have a PTZ USB camera, connect it to the the Camera USB connector. This is a blue USB 3.0 connector If you are using a static USB camera, connect it to one of the pair of USB 2.0 connectors at the bottom of the rear panel (refer to About the GTm 5140 codec (p3)) 2. Connect the microphone to the Microphone USB connector. Note: The Microphone port labeled in About the GTm 5140 codec (p3) isn't labeled as such on the unit but is the recommended port for microphone use. Connecting screens On the GTm 5140, the audio emits from the Mini DisplayPort connectors on the rear of the codec. Connect directly from the Mini DisplayPort to the screen using the supplied cable and adaptor. To do this: Connect a Mini DisplayPort connector on the codec to a screen using a a Mini DisplayPort-to-HDMI adaptor and an HDMI-to-HDMI cable. If this is a two-screen system: Connect the second screen in the same way to the other Mini DisplayPort. Prior to GTm software release 1.2, you must use a supplied audio injector to connect the screens to the codec. From GTm release 1.2 onwards, connect directly from the Mini DisplayPort to the screen using the supplied cables (without the need for an audio injector). Using the audio injector is described in the StarLeaf Knowledge Center. Note: Power the screens and switch them ON before you power the GTm, otherwise the screens do not detect the audio. Connecting power Using the supplied power cable, connect the DC +19V power connector on the rear of the codec to the mains power. Note: Power the screens and switch them ON before you power the GTm, otherwise the screens do not detect the audio. GTm 5140, 20 November 2017 Page 8 of 23

9 How to install GTm 5140 Connecting the controller Instead of connecting the StarLeaf Touch 2035 to the GTm 5140 codec, the controller connects directly to your network. Using an Ethernet cable, connect the PoE Network port on the rear of the controller to an Ethernet switch in your network. The Ethernet port is a 10/100/1000 Mbit/s auto-sensing port and is set to auto by default. The controller needs a switch/port that supplies PoE to function. Note: In all cases, the speed and duplex settings at either end of the connection must be identical. Using non-matching settings causes severe packet loss. The controller and the codec should be paired but if they are not and you need to do this manually, follow the instructions below. 1. When the controller is connected, double-press the Home button to go to settings. 2. Navigate to networking and, if enabled, turn off auto-discovery. 3. When auto-discovery is disabled, the configuration server field appears. Type in the MAC address from the bottom of the codec into the field. Mounting the camera StarLeaf recommends that when you mount the camera, you place it at the top of the screen, as opposed to the base. This makes it easier for you to see the participants on the screen while still appearing to make eye contact. If you have a dual-screen system, ensure that the camera is mounted on the screen that will display the view of the main video (telepresence screen 1). Creating a user account On your Lync/Skype for Business server, create a new user account for the GTm Make a note of the authentication details. (You can use an existing account if you prefer.) GTm 5140, 20 November 2017 Page 9 of 23

10 Configuring the GTm 5140 Configuring the GTm 5140 The following instructions are for setting up the GTm Initial configuration 1. On the GTm 5140 touchscreen controller, press the settings button to view settings and the IP address. 2. In a web browser, navigate to the IP address of the GTm Select a configuration. If you are using Maestro, choose Hosted or On-premise, or choose Demo/Unmanaged if you will not use Maestro to manage the GTm. If you choose Demo/Unmanaged, you configure the GTm using its web interface; the settings are available under Status. If you choose Maestro, you will manage the GTm using Maestro and you will only configure proxy settings, if required, through the web interface. 4. Proxy server: If there is a proxy server for your deployment, you need to configure the details of that for the GTm. Note that this is the same configuration as you would use for a PC running a Skype for Business/Lync client in the same location on your network. To configure the proxy server settings, go to Proxy: For more information about configuring the GTm through the Maestro management platform, start here: Introduction to Maestro. For more information about using GTm in demo/unmanaged mode, refer to Demo/Unmanaged GTm configuration. Near-end camera control for GTm 5140 If you have connected a PTZ camera to the GTm 5140, the Camera Control tab on the home screen allows you to control it. GTm 5140, 20 November 2017 Page 10 of 23

11 Configuring the GTm 5140 The near-end camera control allows you to pan, tilt, and zoom your camera. This control is available both in a call and before you make a call. Camera presets Camera presets are pre-defined camera positions. For example, a pre-defined position that points the camera at the whiteboard, or that changes the camera to a wide-angled view. Room users can select the position they require from the Camera Control tab on the touchscreen controller and they can swap between presets at any time. GTm room systems can have up to five camera presets. You will create the camera presets using Maestro. Refer to Maestro room management. Presets appear on the touch panel. Allowing users to connect a laptop to the GTm 5140 There are a few methods you can use to share content from a laptop. The first, and the easiest, is to use a sharing device. After you have paired the device with the GTm 5140, plug it into your laptop and follow the instructions given for the device. The other two methods are for sharing your screen with a room or a conference without a sharing device using Skype for Business. For more information and further instructions, refer to this article: GTm Family: Connecting a laptop. Standby mode GTm 5140, 20 November 2017 Page 11 of 23

12 Configuring the GTm 5140 When the GTm goes into standby mode, the screens darken, and the microphone and camera are disabled. The touchscreen controller does not dim unless it is during out-ofhours. Refer to the Knowledge Center for more information about out-of-hours functionality. The GTm does not go into this state if an active content source is connected. If you touch the controller or connect a content source, the GTm comes out of standby mode such that the screens will display the content. The camera and microphone will come out of standby mode if there is an active call. Standby mode can be disabled using Maestro. Refer to the Knowledge Center for more information about standby mode. GTm 5140, 20 November 2017 Page 12 of 23

13 Mounting the GTm 5140 unit Mounting the GTm 5140 unit The GTm 5140 is shipped with a wall mounting kit containing a VESA mount bracket, which can be used to mount the unit to either the back of a monitor or TV, or to a wall. To attach and use the VESA bracket with a monitor or TV: 1. Use the four small black screws that were included with the mount to attach the VESA bracket to the back of a monitor or a TV. 2. Attach the two slightly larger black screws to the bottom chassis cover of the GTm Slide the GTm 5140 onto the VESA mount bracket. GTm 5140, 20 November 2017 Page 13 of 23

14 Mounting the GTm 5140 unit Note: The small screws provided for mounting the bracket to the monitor or TV may not fit all models. If this is the case, you need to use screws that are the correct size for your model of monitor or TV. To attach and use the VESA bracket on a wall: 1. Use four screws and wall plugs of appropriate size and type to mount the bracket to a wall. 2. Attach the two slightly larger black screws provided to the bottom chassis cover of the GTm Slide the GTm 5140 onto the VESA mount bracket. Mount Dimensions The dimensions of the VESA mount bracket are as shown below: GTm 5140, 20 November 2017 Page 14 of 23

15 Mounting the GTm 5140 unit GTm 5140, 20 November 2017 Page 15 of 23

16 Typical installation of GTm 5140 This diagram shows a typical installation of a GTm 5140 system. Configuration To view settings and IP address, press settings on the touchscreen controller. To register the GTm and to configure display and other settings browse to the IP address of the GTm. Network Microphone Connecting the controller Connect the controller to the network using an Ethernet cable. The controller pairs with the codec using the codec s MAC address. The controller requires a Power over Ethernet network port, or a separate PoE injector for power. StarLeaf Touch Power 19V Telepresence screen 2 (optional) Static camera video-out PTZ camera video-out Telepresence screen 1 or Camera (either the supplied USB PTZ or static camera) Power supply for camera StarLeaf Group Telepresence Installation Guide Page 16 of 23

17 Appendix: LED behavior Appendix: LED behavior Network port LED LED Color State Link LED (On the left when looking at the port) Data Rate LED (On the right when looking at the port) Green Green/Yellow When off, the LAN link is not established. When on, the LAN link is established. When blinking, LAN activity is occurring When off, 10 Mb/s data rate is selected. When green, 100 Mb/s is selected. When yellow, 1000 Mb/s data rate is selected GTm 5140, 20 November 2017 Page 17 of 23

18 Appendix: Ports and protocols Appendix: Ports and protocols This is a list of ports and protocols used by the GTm. You will need this if your network has Network Access Control (NAC) enabled, which analyzes traffic from the unit for security purposes. GTm system connectivity Outbound Port Host Protocol Notes 53 DNS server as defined in the network configuration 67 Broadcast DHCP server 443 *.maestro.starleaf.com Local Maestro server TCP/UDP (DNS) UDP (DHCP) TCP (HTTPS) Used to resolve domain names or find services (for example, in autodiscovery on older configurations using SRV or A records) Requests to DHCP server Management server connection (either Cloud or on-premise) * currently denotes either config or fw. If you are using a proxy, the whitelist should be *.maestro.starleaf.com, and maestro.starleaf.com if the first rule doesn't cover this 5355 Windows machines TCP/UDP (LLMNR) Used to resolve names on the local network All source ports are ephemeral, that is, , unless otherwise specified. Inbound Port Host Protocol Notes 68 DHCP server UDP (DHCP) Responses from DHCP server 80 Any TCP (HTTP) Endpoint control API GTm 5140, 20 November 2017 Page 18 of 23

19 Appendix: Ports and protocols Port Host Protocol Notes 443 Any TCP (HTTPS) Web UI All source ports are ephemeral, that is, , unless otherwise specified. Internal for GTm 5140 Port Protocol Notes 69, 443, 5000, 5152, TCP (various application layer protocols) StarLeaf internal endpoint control Note: All connections from the touchscreen controller to the GTm 5140 codec use IPv6 and always originate from ephemeral ports. On-premise Skype for Business 2015 or Lync 2013 Outbound Port Host Protocol Notes 80 lyncdiscover.domain lyncdiscoverinternal.domain autodiscover.domain TCP (HTTP) Used in Lync and EWS autodiscovery 88 AD server TCP/UDP Kerberos authentication 443 Local webticket ADFS wsfed servers TCP (HTTPS) Various authentication modes need external servers (also EWS server) 3478 Edge server UDP (STUN/MSTURN) Used for external user access to A/V sessions and media (UDP) 5061 Front End server TCP (MTLS) Used for client-toserver SIP traffic for external user access GTm 5140, 20 November 2017 Page 19 of 23

20 Appendix: Ports and protocols Port Host Protocol Notes Front end server Other client Front end server Other client Front end server Other client UDP TCP TCP (PSOM) Audio, and video (minimum of 40 ports required) Audio, video, and application sharing Peer-to-peer file transfer (for conferencing file transfer, clients use PSOM) All source ports are ephemeral, that is, , unless otherwise specified. GTm on external network If the GTm is not located on the same local network as the Skype for Business deployment, that is, if it has to connect using the Edge server, the following ports and protocols also apply. Port Host Protocol Notes 443 Edge server TCP (TLS) Used for client-toserver SIP traffic for external user access 443 Edge server TCP (PSOM/TLS) 443 Edge server TCP (STUN/MSTURN) 3478 Edge server TCP (STUN/MSTURN) Used for external user access to web conferencing sessions Used for external user access to A/V sessions and media (TCP) Used for external user access to A/V sessions and media (UDP) Other client UDP Audio, and video Other client TCP Audio, video, and application sharing 50,000-59,999 Edge server UDP Audio, and video 50,000-59,999 Edge server TCP Audio, video, and application sharing GTm 5140, 20 November 2017 Page 20 of 23

21 Appendix: Ports and protocols All source ports are ephemeral, that is, , unless otherwise specified. Skype for Business Online Outbound Port Host Protocol Notes 443 Skype for Business Online servers t 443 Skype for Business Online servers t 443 Skype for Business Online servers t 443 Skype for Business Online servers t Skype for Business Online servers t 50,000-59,999 Skype for Business Online servers t Other client 50,000-59,999 Skype for Business Online servers t Other client 50,000-59,999 Skype for Business Online servers t Other client TCP (HTTPS) TCP (TLS) TCP (PSOM/TLS) TCP UDP TCP/UDP TCP/UDP TCP Webticket, wsfed authentication SIP signaling PSOM connections web conferencing Audio, video, and application sharing (source port depends on configuration) Audio, video, and application sharing (source port depends on configuration) Audio (source port 50,000-50,019) Video (source port 50,020-50,039) Application sharing (source port 50,040-50,059) All source ports are ephemeral, that is, , unless otherwise specified. The full range of Skype for Business Online IP addresses is available here GTm 5140, 20 November 2017 Page 21 of 23

22 Appendix: Ports and protocols Inbound Port Host Protocol Notes 50,000-50,019 Skype for Business Online servers Other client 50,020-50,039 Skype for Business Online servers Other client 50,040-50,059 Skype for Business Online servers Other client TCP/UDP TCP/UDP TCP Audio (source port 50,000-59,999) Audio (source port 50,000-59,999) Application sharing (source port 50,000-59,999) All source ports are ephemeral, i.e , unless otherwise specified. The full range of Skype for Business Online IP addresses is available here GTm 5140, 20 November 2017 Page 22 of 23

23 Legal information Legal information Third party software acknowledgments Acknowledgments of third-party software are available at: Disclaimers and notices Copyright StarLeaf All rights reserved. This guide may not be copied, photocopied, translated, reproduced, or converted into any electronic or machine-readable form in whole or in part without prior written approval of StarLeaf Limited. StarLeaf Limited reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of StarLeaf Limited to provide notification of such revision or change. StarLeaf Limited provides this documentation without warranty, term, or condition of any kind, either implied or expressed, including, but not limited to, the implied warranties, terms or conditions of merchantability, satisfactory quality, and fitness for a particular purpose. StarLeaf Limited may make improvements or changes to the product(s) and/or the program(s) described in this documentation at any time. All other product and company names herein may be trademarks of their respective owners. GTm 5140, 20 November 2017 Page 23 of 23