Scopia Video Gateway for Microsoft Lync Lync Deployment Guide

Transcription

1 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide Release 9.0 Issue 1 January 2017

2 , Avaya, Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published in varying mediums which may include product information, operating instructions and performance specifications that are generally made available to users of products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of Documentation unless such modifications, additions, or deletions were performed by or on the express behalf of Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or Documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on Avaya hardware and software. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product while under warranty is available to Avaya customers and other parties through the Avaya Support website: getgenericdetails?detailid=c under the link Warranty & Product Lifecycle or such successor site as designated by Avaya. Please note that if You acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to You by said Avaya Channel Partner and not by Avaya. Hosted Service means an Avaya hosted service subscription that You acquire from either Avaya or an authorized Avaya Channel Partner (as applicable) and which is described further in Hosted SAS or other service description documentation regarding the applicable hosted service. If You purchase a Hosted Service subscription, the foregoing limited warranty may not apply but You may be entitled to support services in connection with the Hosted Service as described further in your service description documents for the applicable Hosted Service. Contact Avaya or Avaya Channel Partner (as applicable) for more information. Hosted Service THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE, UNDER THE LINK Avaya Terms of Use for Hosted Services OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THE TERMS OF USE. IF YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED SERVICE. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, UNDER THE LINK AVAYA SOFTWARE LICENSE TERMS (Avaya Products) OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Avaya grants You a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other materials available to You. Software means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-installed on hardware products, and any upgrades, updates, patches, bug fixes, or modified versions thereto. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Instance means a single copy of the Software executing at a particular time: (i) on one physical machine; or (ii) on one deployed software virtual machine ( VM ) or similar deployment. License type(s) Designated System(s) License (DS). End User may install and use each copy or an Instance of the Software only on a number of Designated Processors up to the number indicated in the order. Avaya may require the Designated Processor(s) to be identified in the order by type, serial number, feature key, Instance, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Shrinkwrap License (SR). You may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickthrough license accompanying or applicable to the Software ( Shrinkwrap License ). Heritage Nortel Software Heritage Nortel Software means the software that was acquired by Avaya as part of its purchase of the Nortel Enterprise Solutions Business in December The Heritage Nortel Software is the software contained within the list of Heritage Nortel Products located at under the link Heritage Nortel Products or such successor site as designated by Avaya. For Heritage Nortel Software, Avaya grants Customer a license to use Heritage Nortel Software provided hereunder solely to the extent of the authorized activation or authorized usage level, solely for the purpose specified in the Documentation, and solely as embedded in, for execution on, or for communication with Avaya equipment. Charges for Heritage Nortel Software may be based on extent of activation or use authorized as specified in an order or invoice.

3 Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, and the product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Virtualization The following applies if the product is deployed on a virtual machine. Each product has its own ordering code and license types. Note that each Instance of a product must be separately licensed and ordered. For example, if the end user customer or Avaya Channel Partner would like to install two Instances of the same type of products, then two products of that type must be ordered. Third Party Components Third Party Components mean certain software programs or portions thereof included in the Software or Hosted Service may contain software (including open source software) distributed under third party agreements ( Third Party Components ), which contain terms regarding the rights to use certain portions of the Software ( Third Party Terms ). As required, information regarding distributed Linux OS source code (for those products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the products, Documentation or on Avaya s website at: support.avaya.com/copyright or such successor site as designated by Avaya. The open source software license terms provided as Third Party Terms are consistent with the license rights granted in these Software License Terms, and may contain additional rights benefiting You, such as modification and distribution of the open source software. The Third Party Terms shall take precedence over these Software License Terms, solely with respect to the applicable Third Party Components to the extent that these Software License Terms impose greater restrictions on You than the applicable Third Party Terms. The following applies only if the H.264 (AVC) codec is distributed with the product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ( AVC VIDEO ) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE Service Provider THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER S HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER S HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER S EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER. WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729 CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE THE H.264 (AVC) CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ( AVC VIDEO ) AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE Compliance with Laws You acknowledge and agree that it is Your responsibility for complying with any applicable laws and regulations, including, but not limited to laws and regulations related to call recording, data privacy, intellectual property, trade secret, fraud, and music performance rights, in the country or territory where the Avaya product is used. Preventing Toll Fraud Toll Fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Toll Fraud intervention If You suspect that You are being victimized by Toll Fraud and You need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: or such successor site as designated by Avaya. Security Vulnerabilities Information about Avaya s security support policies can be found in the Security Policies and Support section of support.avaya.com/security. Suspected Avaya product security vulnerabilities are handled per the Avaya Product Security Support Flow ( support.avaya.com/css/p8/documents/ ). Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support. Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, its licensors, its suppliers, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc.

4 All non-avaya trademarks are the property of their respective owners. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

5 Contents Chapter 1: About Scopia Video Gateway... 7 Main Features of the Scopia Video Gateway... 8 New Features of the Scopia Video Gateway... 8 Technical Specifications Chapter 2: Preparing the Setup Planning the Deployment Topology of your Scopia Video Gateway in the Enterprise Planning the Deployment Topology of your Hosted Scopia Video Gateway Deploying your Hosted Scopia Video Gateway with Enterprise-installed Lync Services Deploying your Hosted Scopia Video Gateway with Hosted Enterprise Lync Services Deploying your Hosted Scopia Video Gateway with Lync Server 2010 Hosting Pack Deciding on the Scopia Video Gateway's Location Prerequisites of your Current Video Network Ports to Open on the Scopia Video Gateway Checking Site Suitability Unpacking the Device Inspecting for Damage Chapter 3: Setting up the Device Choosing the Type of Rack Preparing the Rack and Rails for Mounting the Scopia Video Gateway Connecting Cables to the Device Configuring the IP addresses Verifying the Scopia Video Gateway Installation Chapter 4: Configuring Your Scopia Video Gateway Deployment Creating User Groups and Users in the Microsoft Active Directory Creating New User Groups in the Active Directory Creating New Users Representing Room Systems in the Active Directory Creating New Users Representing Personal Endpoints in the Active Directory Creating New Users Representing Virtual Rooms in the Active Directory Creating a User Representing the Auto-Attendant in the Active Directory Creating a User Representing My Virtual Room in the Active Directory Creating Users Groups and Users for the Lync Server 2010 Hosting Pack Deployment Configuring the Microsoft Lync Server Configuring the Lync Server without TLS (for TCP Environment) Enabling New Active Directory Users on the Lync Server Enabling Support for Non-encrypted Calls and HD on the Lync Server Configuring the Lync Server for TLS Environment Configuring Ports on the Scopia Video Gateway Limiting TCP Port Range for H.245 on the Scopia Video Gateway Configuring RTP/RTCP/SRTP Ports on the Scopia Video Gateway January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 5

6 Contents Configuring UDP Port for RAS on the Scopia Video Gateway Configuring TCP Port for Q.931 on the Scopia Video Gateway Configuring a Scopia Video Gateway in Equinox Management Adding a gateway in Equinox Management Configuring the Scopia Video Gateway in Equinox Management Dedicating the Scopia Video Gateway to an Organization Making Custom Pictures Visible to External Users Connecting Equinox Management to Microsoft Components of Your Video Network Adding a Lync, Skype for Business, in Equinox Management Defining Service Provider Organizations Connecting Equinox Management with the LDAP Server Downloading Users from the LDAP Server Importing H.323 Endpoints from an External LDAP Server Downloading Virtual Rooms from the LDAP Server Enabling Auto-Attendant Support Adding Access to Lync in Invitations Configuring a Third Party Deployment Adding a Neighbor Gatekeeper Defining a Third-Party MCU in Avaya Equinox Management Securing Your Video Network Using TLS Planning the Required Certificates for TLS Generating and Uploading Certificates for the Scopia Video Gateway Enabling Encryption on Scopia Video Gateway Chapter 5: Performing Maintenance Procedures Upgrading the Software File of a Video Device Restoring the Previous Software Version of a Network Device Downgrading your Scopia Video Gateway Changing the IP Address of your Gateway Chapter 6: Troubleshooting Your Scopia Video Gateway Deployment All Endpoints Appear Offline Resolving Room System Availability Resolving Lync Client Connectivity in TCP Environment Resolving Lync Client Connectivity in TLS Environment Retrieving Scopia Video Gateway Logs Resolving a TCP Connectivity Issue with Lync Server 2010 Hosting Pack Resolving a Copy and Paste Issue in Avaya Equinox Management Renewing an Expired Certificate in the Scopia Video Gateway January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 6

7 Chapter 1: About Scopia Video Gateway Scopia Video Gateway serves as a bridge between a video network based on endpoints and room systems using H.323 protocol and a video network based on Microsoft Lync platform. With a Scopia Video Gateway deployed into your existing solution, you can use these two separate video networks as one, making video calls from H.323 endpoints to Lync clients and vice versa. This bridge functionality characterizes the Scopia Video Gateway whether it is located in an enterprise or hosted in the service provider s network. Figure 1: Scopia Video Gateway functionality on page 7 depicts the Scopia Video Gateway functionality. Figure 1: Scopia Video Gateway functionality You can use the Scopia Video Gateway both in Equinox Solution deployments and in third party video deployments. The Scopia Video Gateway was the first gateway officially certified for Microsoft OCS-R2 and Lync video deployments. The certification process required rigorous and extensive testing to ensure the highest quality and compatibility. It is also fully interoperable with Lync Main Features of the Scopia Video Gateway on page 8 New Features of the Scopia Video Gateway on page 8 Technical Specifications on page 10 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 7

8 About Scopia Video Gateway Main Features of the Scopia Video Gateway The Scopia Video Gateway includes many powerful features including: Presence reflection All H.323 devices appear on the Lync Contact List. Their presence is updated dynamically according to their real-time status. Presence is updated for H.323 room systems, Equinox Media Server, Scopia Elite MCU virtual rooms and the video auto-attendant. HD video transcoding Scopia Video Gateway transcodes Microsoft's RTVideo codec to H.264 video codec and vice versa, from RTVideo to H.264. This enables end-to-end HD video quality for every call, assuming HD is supported by both sides. Point-to-point calls A Microsoft Lync client can easily initiate a point-to-point call with any of the H.323 endpoints or room systems that are part of the Contact List. Calling an H.323 endpoint is just like when calling any other Lync client. Users can also call from an H.323 endpoint to a Lync client. Multipoint calls Several users can participate in the same meeting. This includes Lync clients and H.323 room systems and endpoints. Multipoint calls may be hosted on the Equinox Media Server, Scopia Elite MCU or the Lync internal A/V MCU. Using Equinox Media Server or Scopia Elite MCU upgrades the user experience by providing continuous presence, Telepresence interoperability and full moderation capabilities. Joining a call on Equinox Media Server or on Scopia Elite MCU is done by directly accessing one of the virtual rooms or using the video auto-attendant. Note that virtual rooms and auto-attendant are features of Equinox Media Server and Scopia Elite MCU. About Scopia Video Gateway on page 7 New Features of the Scopia Video Gateway The Scopia Video Gateway includes these new features: Support for the Equinox Solution The Equinox Solution supports the Scopia Video Gateway, allowing complete connectivity to the service provider network as well as complete integration with a Microsoft Lync deployment installed locally in the enterprise (tenant). Support for Microsoft Lync deployments hosted in the service provider network The Avaya videoconferencing services support the Scopia Video Gateway and integrate with Microsoft Lync deployments installed in the service provider s network. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 8

9 New Features of the Scopia Video Gateway Avaya videoconferencing services are deployed in service provider networks that offer Lync services to their tenants via the Microsoft Lync Server 2010 Hosting Pack or through Lync Servers hosted for tenants in the cloud instead of locally in the enterprise. Support of multiple Microsoft edge servers The Scopia Video Gateway works seamlessly with multiple edge servers located within the same domain or in a multi-tenant deployment where the gateway s resources are shared among multiple tenants. The Scopia Video Gateway always negotiates the call with the edge server located in its vicinity, thus attaining immediate call efficiency. End-to-end call encryption The Scopia Video Gateway supports the H.235 encryption standard when connecting to H. 323 devices. There is now a fully secured media path when connecting a call between a Microsoft Lync client and an H.323 device. All media lines (audio, video, data) are encrypted. Connecting to your personal virtual room from the Lync client You can now easily join your own virtual room by selecting the My Virtual Room contact. No login is required as your room is associated with your corporate user name and password. In your own virtual room, you can change your room properties, set up your meetings with people inside and outside your organization. Dialing an H.323 endpoint that has a public address A Lync client can dial the public IP address of an H.323 endpoint to set up the video call, even if the called H.323 endpoint does not belong to the organization (enterprise and/or partner) and as such is not listed in the Active Directory. Up-to-date presence information for an endpoint registered to a third-party gatekeeper Presence information in the Lync Contact List is available for non-avaya components in the H. 323-based video network where you have deployed the Scopia Video Gateway. For example, all H.323 endpoints and third-party MCUs registered to the Cisco Video Communication Server (VCS) appear on the Lync Contact List and their presence is updated dynamically according to their real-time status. Seeing content shared by an H.323 endpoint When an H.323 endpoint shares content in a video call or in a videoconference, the Scopia Video Gateway automatically switches to the presentation channel and starts sending the presentation to the Lync client. The presentation is supported in H.264 format with a maximum resolution of 720p at 30fps; the minimum supported resolution is VGA at 30fps. Video Scaling The Scopia Video Gateway is capable of upscaling and downscaling the actual video resolution. The video resolution matching is required for Microsoft Lync native resolutions, such as VGA, to avoid image cropping. Customized user pictures in the Contact List of the MS Lync client Contacts have custom profile image for meeting rooms, virtual meeting rooms (including their personal virtual room), and auto attendant, allowing to identify the listed videoconference equipment at a glance. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 9

10 About Scopia Video Gateway About Scopia Video Gateway on page 7 Technical Specifications This section lists important information about the device you purchased. Refer to this information when preparing system setup and afterwards to verify that the environment still complies with these requirements. System power requirements: VAC input, 50/60Hz auto-switched Power consumption: - 946W (230V/4.3A or 115V/8.6A) Environmental requirements: - Operating temperature: 10 C to 35 C (50 F to 95 F) - Humidity: 90% non-condensing at 35 - Storage and transit temperature: -40 C to 70 C (-40 F to 158 F), ambient Physical dimensions: - Size: 430mm (16.9 ) width x 43mm (1.7 ) height x 690mm (27.2 ) depth - Weight: ~15kg (~34lbs) - 19-inch rack-mountable with flanges Ethernet connection requirement: - 1Gbps Communications: - H IPv4 - Bit rate: up to 1.5Mbps per call Audio support: - Codecs: G.711. G.722, G DTMF Translation: - In-band to out-of-band translation Video support: - Codecs: Microsoft RTVideo, H.264, H Video resolutions for Microsoft Lync: CIF, VGA, 720p@30fps January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 10

11 Technical Specifications - Microsoft RTVideo HD transcoding Content sharing - H.323 to Lync, up to 720p resolution support Call capacity Table 1: Call capacity on page 11 lists, for each Scopia Video Gateway license, the number of ports used for transcoding the video resolutions. Table 1: Call capacity Transcoding Scopia Video Gateway Entry Level Scopia Video Gateway X2 Capacity* HD 720p 5 ports 10 ports VGA 10 ports 20 ports CIF 20 ports 40 ports * Capacity is doubled using a license key that should be purchased separately. Note: Sending content presentation to Lync clients in VGA resolution requires the Scopia Video Gateway to upgrade the call to HD 720p for the content to be readable on the Lync screen. Therefore the Scopia Video Gateway capacity is limited to 10 concurrent calls for calls with content presentation. Sending content presentation to Lync clients in CIF resolution is not allowed by the Scopia Video Gateway. Scalability - Unlimited scalability with multiple Gateways - The ratio depends on the number of room systems and on the overall video usage in the company. The recommended ratio is: High video usage demands one gateway port per one room system Medium video usage demands one gateway port per three room systems Low video usage demands one gateway port per five room systems Firewall traversal - Microsoft A/V Edge integration using Microsoft ICE2 and Microsoft TURN. - H , H (through Avaya Equinox H.323 Edge) Security - Microsoft SRTP support - Microsoft Transport Layer Security (TLS) - H.235 AES encryption January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 11

12 About Scopia Video Gateway Interfaces - RJ-45, dual gigabit Ethernet - RJ-45 serial port connector About Scopia Video Gateway on page 7 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 12

13 Chapter 2: Preparing the Setup Perform procedures in this section to prepare the site and device for installation. Planning the Deployment Topology of your Scopia Video Gateway in the Enterprise on page 13 Planning the Deployment Topology of your Hosted Scopia Video Gateway on page 15 Deciding on the Scopia Video Gateway's Location on page 17 Prerequisites of your Current Video Network on page 21 Ports to Open on the Scopia Video Gateway on page 22 Checking Site Suitability on page 25 Unpacking the Device on page 25 Inspecting for Damage on page 26 Planning the Deployment Topology of your Scopia Video Gateway in the Enterprise Important: This section provides general guidelines that are common for both the Equinox Solution deployments and third party deployments. Follow these guidelines to locate the Scopia Video Gateway and Equinox Management in your video network, when the Scopia Video Gateway is deployed in the enterprise. The guidelines describe a typical entreprise deployment of Lync Server 2010 and includes one Lync Server or multiple Lync Servers: In a local deployment with one Lync Server, always place the Scopia Video Gateway and Equinox Management at the location of the Lync Server (Figure 2: Example of a local deployment with one Lync Server on page 14). Typically, there is no firewall between the Equinox Management and the Lync Server and between the Equinox Management and the Scopia Video Gateway. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 13

14 Preparing the Setup Figure 2: Example of a local deployment with one Lync Server However, if there is a firewall between these components, for example, if the Equinox Management is located in the DMZ in the Complete Centralized Solution, you need to open several ports on the firewall to allow connection. For more information, see Ports to Open on the Scopia Video Gateway on page 22. In a local deployment with more than one Lync Server, place your Scopia Video Gateway and Equinox Management in the same location as the main Lync Server (Figure 3: Example of a local deployment with multiple Lync Servers on page 14). It is recommended that you locate the Equinox Management within a close physical proximity to the main Lync Server. If you need to locate more than one Scopia Video Gateway in such a deployment, place them together with the other Lync Servers. Preparing the Setup on page 13 Figure 3: Example of a local deployment with multiple Lync Servers January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 14

15 Planning the Deployment Topology of your Hosted Scopia Video Gateway Planning the Deployment Topology of your Hosted Scopia Video Gateway Important: This section provides general guidelines that are common for both the Equinox Solution deployments and third party deployments. If your Equinox Solution is deployed as the Avaya Video Platform for Cloud Services hosted in the service provider s network, the service provider shares these videoconference services between its customers. Preparing the Setup on page 13 Deploying your Hosted Scopia Video Gateway with Enterprise-installed Lync Services on page 15 Deploying your Hosted Scopia Video Gateway with Hosted Enterprise Lync Services on page 16 Deploying your Hosted Scopia Video Gateway with Lync Server 2010 Hosting Pack on page 16 Deploying your Hosted Scopia Video Gateway with Enterpriseinstalled Lync Services When Lync Servers are deployed locally, place your Scopia Video Gateway and Equinox Management in the service provider s network (see (Figure 4: Example of deployment with local Lync Servers in each enterprise on page 15). The videoconference services use the Avaya Equinox Management Multi-tenant Edition. Each enterprise has its own Microsoft Lync Server 2010 Standard Enterprise Edition. Figure 4: Example of deployment with local Lync Servers in each enterprise January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 15

16 Preparing the Setup Planning the Deployment Topology of your Hosted Scopia Video Gateway on page 15 Deploying your Hosted Scopia Video Gateway with Hosted Enterprise Lync Services This type of deployment serves customers who want to retain dedicated Lync Servers while having them hosted by the service provider. Each enterprise installs endpoints locally and receives Lync services from the virtual Lync Server hosted and managed in the service provider s large physical server. The customer is viewed as a single tenant in this type of deployment. The videoconferencing services that comprise Scopia Video Gateway and Equinox Management are also hosted in the service provider s network for use by that particular customer. See Figure 5: Example of deployment with hosted enterprise Lync Servers on page 16. Figure 5: Example of deployment with hosted enterprise Lync Servers Planning the Deployment Topology of your Hosted Scopia Video Gateway on page 15 Deploying your Hosted Scopia Video Gateway with Lync Server 2010 Hosting Pack This type of deployment enables hosting service providers to share video resources between different organizations while offering Lync services. The service provider uses the Microsoft Lync Server 2010 Hosting pack to provide Lync services to its tenants and hosts videoconferencing services that comprise the Scopia Video Gateway and Equinox Management Multi-tenant Edition. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 16

17 Deciding on the Scopia Video Gateway's Location Tenants install endpoints locally to interface with these services. See Figure 6: Example of deployment with Lync Server 2010 Hosting Pack on page 17. Figure 6: Example of deployment with Lync Server 2010 Hosting Pack Planning the Deployment Topology of your Hosted Scopia Video Gateway on page 15 Deciding on the Scopia Video Gateway's Location After you have chosen the topology of your deployment, you must decide how many Scopia Video Gateways you need to deploy, and where to deploy these gateways in your deployment. Planning your Scopia Video Gateway deployment can make the process significantly more efficient. The deployment process may be different depending on your current video network and the features you want to enable. Deploying the Scopia Video Gateway requires configuring the unit itself as well as several other components. Therefore, it is very important to plan how many Scopia Video Gateways, meeting rooms, endpoints and public virtual rooms you want to add to your deployment. Depending on the selected deployment, the setup is composed of these mandatory components: Scopia Video Gateway Avaya Equinox Management Standalone H.323 Gatekeeper for providing the address resolution functionality in H.323 networks. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 17

18 Preparing the Setup Lync Server and Clients (and associated components). All clients are assumed to have video and audio support. H.323 endpoints. Other optional components typically include: Equinox Media Server or Scopia Elite MCU for hosting videoconferences from multiple endpoints, both H.323 and SIP. Personal endpoints. These are specifically defined endpoints which are associated with a Lync account. When the account is dialed, both the personal endpoint and the Lync Client ring simultaneously. Avaya Equinox H.323 Edge server. This component allows H.323 calls to traverse firewalls. Scopia Desktop Server, Scopia Desktop Client s, Scopia Mobiles, and Avaya Equinox Meetings for Web. Scopia Desktop Server acts as a gateway from Scopia Desktop Clients to Equinox Media Server or Scopia Elite MCU and handles all media connections. Scopia Desktop Client is a simple web conferencing client for interactive conferencing using high definition or standard definition broadcasting. Scopia Mobile enables users to easily connect to a videoconference and fully participate in the meeting on ios devices like the Apple iphone, ipod touch and ipad. Avaya Equinox Meetings for Web is a WebRTC client. Figure 7: Deploying the Scopia Video Gateway and the Lync Server in the enterprise on page 18 describes a typical deployment of the Scopia Video Gateway in an enterprise that uses a locally installed Lync Server. Figure 7: Deploying the Scopia Video Gateway and the Lync Server in the enterprise January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 18

19 Deciding on the Scopia Video Gateway's Location Figure 8: Deploying hosted Scopia Video Gateway and enterprise-dedicated Lync Servers on page 19 illustrates a typical deployment where the Scopia Video Gateway is hosted in the service provider network that also hosts dedicated Lync Servers belonging to enterprises. Figure 8: Deploying hosted Scopia Video Gateway and enterprise-dedicated Lync Servers Figure 9: Deploying a hosted Scopia Video Gateway with enterprise-installed Lync Servers on page 19 illustrates a typical deployment in which the Scopia Video Gateway is hosted in the service provider s network and connects with Lync services locally installed in enterprises. Figure 9: Deploying a hosted Scopia Video Gateway with enterprise-installed Lync Servers Figure 10: Deploying hosted Scopia Video Gateway and Lync Servers on page 20 illustrates a typical deployment where the Scopia Video Gateway connects to the Microsoft Lync Server 2010 Hosting Pack, both hosted in the service provider network. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 19

20 Preparing the Setup Figure 10: Deploying hosted Scopia Video Gateway and Lync Servers Plan your deployment by answering the questions below and checking Technical Specifications on page 10. Where are you planning to locate the Scopia Video Gateways? In the Avaya Video Platform for Cloud Services the Scopia Video Gateway, Avaya Equinox Management and other videoconferencing components are deployed in the service provider s network. The service provider shares the video platform between organizations that hired the videoconferencing services. Decide how many Scopia Video Gateways you need to deploy: - How many simultaneous Microsoft Lync or Microsoft Office Communications participants will be in your Scopia Video Gateway deployment? - What video quality will be used in your deployment: high definition (HD) or standard definition (SD)? - In service provider deployments is the Scopia Video Gateway shared among multiple tenants? - In service provider deployments is one Scopia Video Gateway dedicated to one tenant in particular? - How many Microsoft Edge Servers will the Scopia Video Gateway support? How many H.323 room systems do you want to add to your Scopia Video Gateway deployment? Where are these H.323 room systems physically located? If you have Equinox Media Server or Scopia Elite MCU deployed in your network, do you want to enable public virtual rooms? How many public virtual rooms do you want to enable? If you have Equinox Media Server or Scopia Elite MCU deployed in your network, do you want to enable the video auto-attendant feature? January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 20

21 Prerequisites of your Current Video Network Which type of security (TLS/TCP) do you want to ensure in your deployment? If TLS is required, make sure to generate the Avaya Equinox Management and Scopia Video Gateway certificates. Which naming convention do you want to use for your meeting rooms and virtual meeting rooms? It is important to use these names consistently during configuration of different network components. We highly recommend that you use self-explanatory names based on a location or a user name. For example, use London Main Meeting Room for a meeting room situated in London. Preparing the Setup on page 13 Prerequisites of your Current Video Network Verify that your current video network complies with the following requirements: Your video network employs a Microsoft Lync Server 2010 Standard Edition, Enterprise Edition, or Microsoft Lync Server 2010 Hosting Pack Your video network uses H.323 endpoints and Equinox Media Server or MCU The Equinox Management containing the H.323 Gatekeeper should be installed and configured. For information about installing Equinox Management, refer to the Installation Guide for Equinox Management release 7.7. Important: This document assumes that H.323 Gatekeeper (the gatekeeper module which is part of Equinox Management) is used for H.323 signal management. When using the standalone ECS gatekeeper, perform the same actions on the standalone ECS instead of the H.323 Gatekeeper. If you want to support high definition (HD) video calls, Microsoft Lync Clients must be installed on computers capable of supporting HD video calls according to system requirements defined by Microsoft. In addition to these requirements, ensure that you have administrator s rights on the Microsoft Lync Server as well as the Microsoft Active Directory. You need to be able to change configuration settings on these servers. Preparing the Setup on page 13 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 21

22 Preparing the Setup Ports to Open on the Scopia Video Gateway The Scopia Video Gatewayis typically deployed in the enterprise network. When opening ports on the device, use the following as a reference: If you are opening ports that are both in and out of the gateway, see Table 2: Bidirectional Ports to Open on the Scopia Video Gateway on page 22. If you are opening ports outbound from the gateway, see Table 3: Outbound Ports to Open from the Scopia Video Gateway on page 24. If you are opening ports inbound to the gateway, see Table 4: Inbound Ports to Open to the Scopia Video Gateway on page 24. Important: Choosing the specific firewalls where ports need to be opened depends on where your gateway and your other Equinox Solution products are deployed. Table 2: Bidirectional Ports to Open on the Scopia Video Gateway Port Range Protocol Destination Functionality Result of Blocking Port 443 STUN (TCP) H.245 (TCP) Microsoft STUN Server Enables remote SIP ICE connectivity. Any H.323 device Enables H.245 signaling 1719 RAS (UDP) H.323 gatekeeper Enables RAS signaling 1720 Q.931 (TCP) Any H.323 device Enables Q.931 signaling Cannot connect remote endpoints Cannot connect H.323 calls Cannot communicate with H.323 gatekeeper Cannot connect H.323 calls Required Mandatory Mandatory To limit range, see Limiting TCP Port Range for H.245 on the Scopia Video Gateway on page 71 Mandatory To configure, see Configuring UDP Port for RAS on the Scopia Video Gateway on page 74 Mandatory To configure, see Configuring TCP Port for Q.931 on the Scopia Video Gateway on page 74 Table continues January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 22

23 Ports to Open on the Scopia Video Gateway Port Range Protocol Destination Functionality Result of Blocking Port 3336 XML (TCP) Equinox Management 3338 XML (TCP) Equinox Management, or any third-party configuration applications 3346 XML (TLS) Equinox Management 3348 XML (TLS) Equinox Management, or any third-party configuration applications 3478 STUN (UDP) 5060 SIP (TCP/ UDP) STUN Server Any SIP device Enables you to manage this gateway via the XML API Enables you to configure the gateway via the XML API Enables you to manage Scopia Video Gateway via the XML API Enables you to configure Scopia Video Gateway via the XML API Enables remote endpoint to connect Enables SIP signaling 5061 SIP (TLS) Any SIP device Enables secure SIP signaling RTP/ RTCP / SRTP(UDP ) RTP/ RTCP / SRTP (UDP) RTP/ RTCP / SRTP (TCP) UDP for any H.323 or SIP media connection UDP for any H.323 or SIP media connection TCP for H.323 or SIP media connection. Video: Enables real-time delivery of video media Audio: Enables real-time delivery of audio media Audio: Enables real-time delivery of audio media in TCP. Cannot use the XML API to manage the gateway Cannot use the XML API to configure the gateway Cannot use the XML API to manage Scopia Video Gateway Cannot use the XML API to configure Scopia Video Gateway Cannot connect remote endpoints Cannot connect SIP calls Cannot connect SIP calls via TLS Cannot transmit/ receive video media streams Cannot transmit/ receive audio media streams Cannot transmit/ receive audio media streams Required Mandatory Mandatory Mandatory if using TLS Mandatory if using TLS Mandatory Mandatory Mandatory if using TLS Mandatory To configure, see Configuring RTP/ RTCP/SRTP Ports on the Scopia Video Gateway on page 73 Mandatory To configure, see Configuring RTP/ RTCP/SRTP Ports on the Scopia Video Gateway on page 73 Mandatory To configure, see Configuring RTP/ Table continues January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 23

24 Preparing the Setup Port Range Protocol Destination Functionality Result of Blocking Port Microsoft Lync uses both UDP and TCP to ensure the widest compatibility RTP/ RTCP / SRTP (TCP) TCP for H.323 or SIP media connection. Microsoft Lync uses both UDP and TCP to ensure the widest compatibility. Video: Enables real-time delivery of video media in TCP. Cannot transmit/ receive audio media streams Required RTCP/SRTP Ports on the Scopia Video Gateway on page 73 Mandatory To configure, see Configuring RTP/ RTCP/SRTP Ports on the Scopia Video Gateway on page 73 Table 3: Outbound Ports to Open from the Scopia Video Gateway Port Range Protocol Destination Functionality Result of Blocking Port 162 SNMP (UDP) Equinox Management, Equinox Management, or any SNMP manager station Enables sending SNMP Trap events Cannot send Traps via a Network Manager Required Recommende d Table 4: Inbound Ports to Open to the Scopia Video Gateway Port Range Protocol Destination Functionality Result of Blocking Port Required 21 FTP (TCP) FTP Server Enables audio stream recording 22 SSH (TCP) SSH Client Enables you to view logs for the gateway in realtime 80 HTTP (TCP) Web client Enables you to upgrade the gateway and download customer support information Preparing the Setup on page 13 Cannot record audio streams Cannot view logs in real- time (logs are collected on local storage device) Cannot upgrade the gateway or download customer support information Optional Optional Mandatory January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 24

25 Checking Site Suitability Checking Site Suitability Prior to setting up your device, you need to verify your site suitability for: System power requirements System environmental requirements The device physical dimensions. For more information, see to learn about these requirements. Ensure the site conforms to the listed requirements. Preparing the Setup on page 13 Unpacking the Device About this task We strongly recommend that you follow safety guidelines described in this section during unpacking. Procedure 1. Inspect the shipping box to verify that it is not seriously damaged during shipping. 2. Place the shipping box on a horizontal surface paying attention to the This Side Up symbol on the shipping box (Figure 11: This Side Up symbol on page 25). Caution: Figure 11: This Side Up symbol The accessories kit is situated on top of the device inside the shipping box and can be damaged if the box is placed upside down. Pay attention to the This Side Up symbol on the shipping box to handle the box correctly at all times. Caution: To prevent injury and equipment damage, follow the lifting guidelines described in the Safety Guide when lifting or moving the shipping box. 3. Cut the plastic straps. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 25

26 Preparing the Setup Caution: The plastic straps are tightly stretched and can hit you when you cut them. To avoid this, make sure you do not face the side of the box secured by the straps before you cut the straps. 4. Cut the strapping tape. 5. Open the shipping box. 6. Take the accessories kit out of the shipping box. 7. Take the device out of the shipping box. 8. Carefully open the additional boxes, remove the packing material, and remove the drives and other contents. Important: We recommend keeping the packaging materials in case you need to repack the device. 9. Remove the cellophane wrapping from the server case. 10. After opening the shipping box, check the shipment is complete. Compare the contents of the shipment with the packing list included in the box. Preparing the Setup on page 13 Inspecting for Damage After you verify that all of the equipment is included, carefully examine the, power supplies and cables for any damage resulting from shipping. If you suspect any damage from shipping, contact your local freight carrier for procedures on damage claims. If you observe any physical defects in the items you ordered, contact Technical Support for Return Material Authorization (RMA) form. Important: Before proceeding with the installation, verify that all of the ordered parts are present and in good condition. Keep a record of the parts and serial numbers. If any parts are missing or damaged, contact your sales representative. Preparing the Setup on page 13 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 26

27 Chapter 3: Setting up the Device These sections describe how to set up the device: Choosing the Type of Rack on page 27 Preparing the Rack and Rails for Mounting the Scopia Video Gateway on page 28 Connecting Cables to the Device on page 30 Configuring the IP addresses on page 30 Verifying the Scopia Video Gateway Installation on page 33 Choosing the Type of Rack There are many types of racks on the market. The installation instructions in this guide are intended for a 19 rack. Verify that the 19 rack meets the EIA-310 standards. This standard includes precise definitions of the shape of the holes, their size, the depth of the rack and other features. For more information on the EIA-310 standard, see We recommend choosing an open rack. If installing in an enclosed rack, ensure that the rack has adequate ventilation. Ensure the device has enough space on the rack to prevent overheating by following these guidelines: Do not place the device in an overly congested rack or directly next to another equipment rack. Find a space on the rack which is at least 7 empty square holes in height on the rack posts. The device takes up 3 holes (1U) on the posts. You need at least 2 additional holes to slide the device into the rack. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 27

28 Setting up the Device Figure 12: Ensuring enough space for the device Maintain a minimum clearance of 3 inches (7.62 cm) on the left and right of the device. If there are few devices mounted in the rack, find the lowest possible location to mount the device, to ensure the rack remains stable. To mount the device between two rack posts, the width between the inner sides of the two posts must be at least 17.7 inches (45 cm). Setting up the Device on page 27 Preparing the Rack and Rails for Mounting the Scopia Video Gateway When checking for an empty space to set up the device, be aware of its physical dimensions. Verify that you have a 19 rack that meets the EIA-310 standards. This standard includes precise definitions of the shape of the holes, their size, the depth of the rack and other features. The rack should be sturdy enough to support the device when you slide it in and out. We recommend choosing an open rack. If installing in an enclosed rack, ensure that the rack has adequate ventilation. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 28

29 Preparing the Rack and Rails for Mounting the Scopia Video Gateway Ensure that the environment is suitable for the rack, considering factors such as the ambient temperature of the room. Read the safety instructions that came with your rack for details. Make sure you have the following items, which were shipped with the device and are used to mount the rails to the rack: - Two long outer rails - Two short outer rails - Two flat-head long screws (Phillips cross recessed flat-head machine screws M5x12mm 90 ) - Two brackets (finishing washers M5) Figure 13: Preparing the parts required to mount the rails Use the guidelines listed below to decide where on the rack to mount the device. Proper placement prevents the device from overheating and ensures that the rack is stable. - Do not place the device in an overly congested rack or directly adjacent to another equipment rack. - Find a space on the rack which is 3 empty square holes in height (1U) on the rack posts. - If there are few devices mounted in the rack, find the lowest possible location to mount the device, to ensure the rack remains stable. Setting up the Device on page 27 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 29

30 Setting up the Device Connecting Cables to the Device About this task Follow this procedure to connect the power and serial cable supplied with the accessories kit. Important: The serial connection is used only for configuring the IP address of the device. Caution: During this procedure, follow the safety guidelines described in the Safety Guide. Procedure 1. On the rear panel, connect the power cable to the AC power connector (Figure 14: Rear panel of the device on page 30). Figure 14: Rear panel of the device 2. Connect the other end of the power cable to the AC power. 3. Use a serial cable to connect a PC to the device's serial port. This connection is required for local configuration and maintenance. Important: Do not connect a screen or a keyboard to the device directly. Define the device's basic settings via the serial connection only. Setting up the Device on page 27 Configuring the IP addresses About this task January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 30

31 Configuring the IP addresses Before you begin Make sure you have these items: Dedicated IP address for the device Dedicated subnet mask for the device IP address of the default router which the device uses to communicate over the network A PC with an available serial port. It should have a terminal emulator software installed like SecureCRT or PuTTY. Power, network, and serial cables supplied with the device accessories kit. Use the serial port on the back panel of the device to connect it directly to a PC to assign an IP address. You must assign the IP address before you connect the device to the network. Procedure 1. Connect the power cable, but do not switch on the device. 2. Connect the device serial port to a PC with the terminal emulator software installed. 3. Start the terminal emulation application on the PC. 4. Set the communication settings in the terminal emulation application on the PC as follows (Table 5: Configuring the communication settings on page 31): Table 5: Configuring the communication settings Field Name Value Baud Rate 9600 Data bits 8 Parity Stop bits 1 Flow Control None None 5. Power the device (see Figure 15: Device front panel on page 32). Verify the power LED is lit green (Figure 15: Device front panel on page 32). January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 31

32 Setting up the Device Figure 15: Device front panel A log of the auto-boot events is displayed in the terminal emulator. 6. When the message Press any key to start configuration appears on the screen, press a key and wait for the following message: Main menu Main Menu N: Configure network port values R: Restore factory defaults Q: Quit Select: If you do not see this output, contact customer support. 7. Enter N at the prompt to configure network port values. The terminal displays the following message: Configure network port values 1: Show current network configuration 2: Change network configuration 0: Return to main menu Select: 8. Enter 2 to change the network configuration. 9. Enter the new settings at each prompt (Table 6: Configuring network settings on page 32). Table 6: Configuring network settings Field IP Address Subnet mask Description IP address of the device IP address of the subnet mask to which the device belongs. If you are not using a subnet mask, press Enter. Table continues January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 32

33 Verifying the Scopia Video Gateway Installation Field Default router Description IP address of the default router the device uses to communicate over the network Important: 10. Allow the device to complete the reboot process. A new emulator session begins. 11. Close the terminal emulator session. 12. Connect the network cable to the ethernet connector on the rear panel of the device. Setting up the Device on page 27 Verifying the Scopia Video Gateway Installation About this task After you installed the device and performed its initial configuration, you need to verify that it is installed and configured correctly. Procedure 1. On the front panel, verify that the power LED is lit green. 2. Verify that the status LED is lit green. Figure 16: Locating the front panel LEDs 3. Check the network connection by verifying that the Ethernet activity LED is lit green. Setting up the Device on page 27 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 33

34 Chapter 4: Configuring Your Scopia Video Gateway Deployment To configure your video network using Scopia Video Gateway, you need to configure the following deployment components: Scopia Video Gateway, Equinox Management, Microsoft Active Directory, and Microsoft Lync Server. You also need to configure non-radvision gatekeepers if they are used in your video network. Important: Deploying the Scopia Video Gateway with Microsoft Lync Server 2010 editions for the enterprise and the Hosting Pack is very similar. Special settings for each edition are indicated in the procedures required to set up the deployment. Only the personnel that installed the Lync services and the customer's network administrator can modify the Lync configuration. Most of the Scopia Video Gateway features need to be configured on more than one component. For example, to add H.323 meeting rooms to your Microsoft Lync deployment, you first need to add users that represent H.323 meeting rooms to the Active Directory, and then you download these users as H.323 meeting rooms from the Active Directory into the Equinox Management. To make the configuration process orderly we recommend that you configure all necessary features on each component in the correct order. Important: For a first-time installation of the Scopia Video Gateway, we strongly recommend to configure the Microsoft Lync Server to the TCP protocol. Once the Scopia Video Gateway has all its functionality, reconfigure your Lync Server for the TLS environment. This chapter guides you through the recommended configuration process which consists of these stages: Creating User Groups and Users in the Microsoft Active Directory on page 35 Configuring the Microsoft Lync Server on page 54 Configuring Ports on the Scopia Video Gateway on page 71 Configuring a Scopia Video Gateway in Equinox Management on page 75 Connecting Equinox Management to Microsoft Components of Your Video Network on page 82 Configuring a Third Party Deployment on page 106 Securing Your Video Network Using TLS on page 109 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 34

35 Creating User Groups and Users in the Microsoft Active Directory Creating User Groups and Users in the Microsoft Active Directory As the first step of your Scopia Video Gateway deployment, you need to add user groups and users dedicated to room systems and personal endpoints to your Active Directory. If your deployment has Equinox Media Server or Scopia Elite MCU, you can also add a user group and users for public virtual rooms and auto-attendant. At a later stage the users you created are downloaded into the Equinox Management as meeting rooms, personal endpoints, public virtual rooms, and auto-attendant. You create new user groups for different kinds of users. After the user groups are ready, you create users and assign users to user groups. For example, in order to create a user dedicated to an H.323 room system, you need to first create a user group for H.323 room systems, and then create a user and assign this user to the H.323 user group. We highly recommend that you plan your Scopia Video Gateway deployment before performing this procedure. Important: This procedure is identical for all types of Lync deployment, but we recommend reading the section Creating Users Groups and Users for the Lync Server 2010 Hosting Pack Deployment on page 53 before configuring user groups and users for a deployment with the Lync Server 2010 Hosting Pack. Configuring Your Scopia Video Gateway Deployment on page 34 Configuring the Microsoft Lync Server on page 54 Creating New User Groups in the Active Directory on page 35 Creating New Users Representing Room Systems in the Active Directory on page 37 Creating New Users Representing Personal Endpoints in the Active Directory on page 41 Creating New Users Representing Virtual Rooms in the Active Directory on page 44 Creating a User Representing the Auto-Attendant in the Active Directory on page 47 Creating a User Representing My Virtual Room in the Active Directory on page 50 Creating Users Groups and Users for the Lync Server 2010 Hosting Pack Deployment on page 53 Creating New User Groups in the Active Directory About this task You need to create these user groups for these types of users: H.323 room systems registered to a H.323 Gatekeeper personal endpoints registered to a H.323 Gatekeeper or a third-party gatekeeper public virtual rooms January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 35

36 Configuring Your Scopia Video Gateway Deployment H.323 room systems registered by a third-party gatekeeper (only in deployments using a thirdparty gatekeeper) Before you begin Decide on names you want to use for user groups before starting the procedure. We highly recommend that you use these names: Meeting Rooms for H.323 rooms systems Personal Rooms for personal endpoints Public Virtual Rooms for public virtual rooms Procedure 1. Access the Active Directory. 2. Navigate to the relevant folder in the left pane. 3. Create a user group for H.323 room systems: a. Right-click Users and select New > Group in the left pane. Figure 17: Creating a new user group in Active Directory b. Enter the name for your new user group. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 36

37 Creating User Groups and Users in the Microsoft Active Directory Figure 18: Entering details for a new user group c. Select a relevant option in the Group scope section. d. Select Security in the Group type section. e. Select OK. 4. Repeat step 3 on page 36 to create other user groups necessary for your deployment: Personal endpoints Public virtual rooms Creating User Groups and Users in the Microsoft Active Directory on page 35 Creating New Users Representing Room Systems in the Active Directory About this task During this procedure you create Active Directory users for all room systems you want to enable in your video network. H.323 users can be represented by Active Directory users either of the room system type or the personal endpoint type. If a room system functions as someone s personal endpoint, you should assign the personal endpoint type to this room system. At the end of this procedure you assign these new users to the Meeting Rooms user group. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 37

38 Configuring Your Scopia Video Gateway Deployment Before you begin Verify that there is a user group representing room systems in Active Directory. For information about creating user groups, see Creating New User Groups in the Active Directory on page 35. Procedure 1. Access the Active Directory. 2. Create a new user for a specific room system: a. Right-click Users and select New > User in the left pane. b. Enter the name for this meeting room in the First name and Full name fields. We recommend that you use a self explanatory name like London_Meeting_Room. Important: You cannot use spaces in names. Figure 19: Entering details for the new user c. Enter the user login name. d. Select Next. e. Enter your password when prompted. f. Select Finish. The new user is added to your Active Directory. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 38

39 Creating User Groups and Users in the Microsoft Active Directory 3. Define the user you created: a. Right-click the user you added and select Properties. The General tab is displayed. b. Enter the telephone number for the H.323 room system. c. Enter the address for the H.323 room system. For example, in Figure 20: Entering a phone number and an for the new user on page 39 we created a new user representing a room system in London with the telephone number 1111 and the address London_Meeting_Room@support2008.com. Figure 20: Entering a phone number and an for the new user d. Enable users on Lync Server as described in Enabling New Active Directory Users on the Lync Server on page 63. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 39

40 Configuring Your Scopia Video Gateway Deployment 4. Assign the user you created to a relevant user group: a. Select the Member Of tab. b. Select Add. c. Select Advanced. d. Select Find Now. e. Select Meeting Room from the list. f. Select OK. g. Select OK. Figure 21: Assigning the new user to a user group Creating User Groups and Users in the Microsoft Active Directory on page 35 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 40

41 Creating User Groups and Users in the Microsoft Active Directory Creating New Users Representing Personal Endpoints in the Active Directory About this task Perform this procedure to create users for all personal H.323 endpoints that you want to enable in your video network. Before you begin Verify that there is a user group representing personal endpoints in Active Directory. For information about creating user groups, see Creating New User Groups in the Active Directory on page 35. Procedure 1. Access the Active Directory. 2. Double-click the Active Directory user to whom you want to assign a personal endpoint. The Properties dialog box opens. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 41

42 Configuring Your Scopia Video Gateway Deployment Figure 22: The Properties Dialog box 3. Verify that the telephone number configured in the Active Directory is the number of this user s personal endpoint. Figure 22: The Properties Dialog box on page 42 shows details of an existing user with the personal endpoint number Assign the user you created to the Personal Endpoints group. a. Select the Member Of tab. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 42

43 Creating User Groups and Users in the Microsoft Active Directory b. Select Add. c. Select Advanced. d. Select Find Now. Figure 23: Assigning the new user to the Personal Endpoints group e. Select Personal Endpoints from the list. f. Select OK. g. Select OK. Creating User Groups and Users in the Microsoft Active Directory on page 35 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 43

44 Configuring Your Scopia Video Gateway Deployment Creating New Users Representing Virtual Rooms in the Active Directory About this task You need to create users for public virtual rooms only if your video network includes Equinox Media Server or Scopia Elite MCU. During this procedure you define the virtual room ID that is used by H.323 room systems for accessing this virtual room. Procedure 1. Access the Active Directory. 2. Create a new user for a specific virtual room: a. Right-click Users and select New > User in the left pane. b. Enter the name for this virtual room in the First name field. We recommend that you use a self explanatory name like Virtual_Room_1. Important: You cannot use spaces in user names. c. Enter the user login name. Figure 24: Entering details for the new user January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 44

45 Creating User Groups and Users in the Microsoft Active Directory d. Select Next. The new user is added to your Active Directory. 3. Define the user you created: a. Right-click the user you added and select Properties. The General tab is displayed. b. Enter the virtual room ID number in the Telephone Number field. c. Enter the address for this virtual room. For example, in Figure 25: Entering a phone number for the new user on page 45 we created a new user representing a virtual room with the ID and the Virtual_Room_1@support2008.com. The address cannot be longer than 25 characters. Figure 25: Entering a phone number for the new user January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 45

46 Configuring Your Scopia Video Gateway Deployment d. Enable users on Lync Server as described in Enabling New Active Directory Users on the Lync Server on page Assign the user you created to a relevant user group: a. Select the Member Of tab. Figure 26: Assigning the new user to a user group b. Select Add. c. Select Advanced. d. Select Find Now. e. Select Public Virtual Room from the list. f. Select OK. g. Select OK. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 46

47 Creating User Groups and Users in the Microsoft Active Directory Creating User Groups and Users in the Microsoft Active Directory on page 35 Creating a User Representing the Auto-Attendant in the Active Directory About this task You need to create a user that represents the auto-attendant if you want to enable this functionality in your video network. This functionality is available only in deployments using a AvayaMCU. Procedure 1. Access the Active Directory. 2. Create a new user for a specific room system: a. Right-click Users and select New > User in the left pane. b. Enter the name for this user in the First name field. We recommend that you use a self explanatory name like AutoAtten. Important: Do not use spaces in names. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 47

48 Configuring Your Scopia Video Gateway Deployment c. Enter the user login name. d. Select Next. e. Select Finish. Figure 27: Entering details for the new user The new user is added to your Active Directory. 3. Define the user you created: a. Right-click the user you added and select Properties. The General tab is displayed. b. Enter the address for this user. The address cannot be longer than 25 characters. For example, in Figure 28: Entering an address for the new user on page 49 we created a new user representing the auto-attendant with the address AutoAtten@support2008.com. Important: This Active Directory user does not need to be part of a user group. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 48

49 Creating User Groups and Users in the Microsoft Active Directory Important: Figure 28: Entering an address for the new user The LDAP Configurations tab includes the checkbox Do not update users without an address from the LDAP server to Avaya iview Suite. If the checkbox is selected, you need to configure the auto-attendant with an address for receiving future updates. c. Enable users on Lync Server as described in Enabling New Active Directory Users on the Lync Server on page 63. Creating User Groups and Users in the Microsoft Active Directory on page 35 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 49

50 Configuring Your Scopia Video Gateway Deployment Creating a User Representing My Virtual Room in the Active Directory About this task You need to create a user that represents the user s personal virtual room if you want to enable this functionality in your video network. This functionality is available only in deployments using a AvayaMCU. Procedure 1. Access the Active Directory. 2. Create a new user for a specific room system: a. Right-click Users and select New > User in the left pane. b. Enter the name for this user in the First name field. We recommend using a self-explanatory name like My_Virtual_Room. Important: Do not use spaces in names. c. Enter the user login name. Figure 29: Entering details for the new user January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 50

51 Creating User Groups and Users in the Microsoft Active Directory d. Select Next. e. Select Finish. The new user is added to your Active Directory. 3. Define the user you created: a. Right-click the user you added and select Properties. The General tab is displayed. b. Enter the address for this user. The address cannot be longer than 25 characters. For example, Figure 30: Entering an address for the new user on page 52 creates a new user representing My Virtual Room with the address MyVRoom@support2008.com. Important: This Active Directory user does not need to be part of a user group. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 51

52 Configuring Your Scopia Video Gateway Deployment Important: Figure 30: Entering an address for the new user The LDAP Configurations tab includes the checkbox Do not update users without an address from the LDAP server to Avaya iview Suite. If the checkbox is selected, you need to configure the user with an address for receiving future updates. c. Enable users on Lync Server as described in Enabling New Active Directory Users on the Lync Server on page 63. Creating User Groups and Users in the Microsoft Active Directory on page 35 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 52

53 Creating User Groups and Users in the Microsoft Active Directory Creating Users Groups and Users for the Lync Server 2010 Hosting Pack Deployment About this task The Active Directory contains these multi-tenancy provisions for the Lync Server 2010 Hosting Pack deployment: Each tenant has its own sub-directory under the OCS Tenants directory. Each tenant should configure its own set of user groups and users. Figure 31: Example of the OCS Tenants directory in the Active Directory on page 53 shows the setup of tenants under the OCS Tenants directory. Four tenants are defined in this example: Tenant1 through Tenant4. Tenant1 has two users ( room11t1, room12t1 ) which are members of the group RoomSystems1. Tenant1 has also four additional users that are not members of any group and three additional users that are members of the VirtualRooms1 group. Tip: Figure 31: Example of the OCS Tenants directory in the Active Directory We recommend to use group names that convey to which tenant the group belongs as well as its function. This simplifies the configuration when connecting Avaya Equinox Management with the LDAP Server. For example, the Terminals group of Tenant1 could be TerminalsT1 or T1Terminals. Creating User Groups and Users in the Microsoft Active Directory on page 35 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 53

54 Configuring Your Scopia Video Gateway Deployment Configuring the Microsoft Lync Server After your Microsoft Active Directory is configured, you need to configure your Microsoft Lync Server. Important: For a first-time installation of the Scopia Video Gateway, we strongly recommend to configure the Microsoft Lync Server to the TCP protocol. The TCP configuration procedure is detailed in Configuring the Lync Server without TLS (for TCP Environment) on page 54. Once the Scopia Video Gateway has all its functionality, reconfigure your Lync Server for TLS environment as described in Configuring the Lync Server for TLS Environment on page 66. This section describes the following procedures: Configuring Your Scopia Video Gateway Deployment on page 34 Creating User Groups and Users in the Microsoft Active Directory on page 35 Configuring Ports on the Scopia Video Gateway on page 71 Configuring the Lync Server without TLS (for TCP Environment) on page 54 Enabling New Active Directory Users on the Lync Server on page 63 Enabling Support for Non-encrypted Calls and HD on the Lync Server on page 64 Configuring the Lync Server for TLS Environment on page 66 Configuring the Lync Server without TLS (for TCP Environment) By default the Lync Server is configured to use TLS for security. If you do not want to secure your video network using TLS, you need to configure your Lync Server to work in a regular TCP environment. Important: For a first-time installation of the Scopia Video Gateway, we strongly recommend to configure the Microsoft Lync Server to the TCP protocol. Once the Scopia Video Gateway has all its functionality, reconfigure your Lync Server for the TLS environment as described in Configuring the Lync Server for TLS Environment on page 66. Configuring the Microsoft Lync Server on page 54 Enabling the TCP Connection on the Lync Server on page 55 Configuring the Lync Server to Trust Equinox Management in TCP Environment on page 56 Configuring the Lync Static Route without TLS (TCP Mode) on page 60 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 54

55 Configuring the Microsoft Lync Server Enabling the TCP Connection on the Lync Server About this task By default the Microsoft Lync Server is configured to work with TLS. You need to enable the Lync Server to use the TCP protocol if your video network uses TCP. Important: If you have a simple enterprise Lync deployment, the Front End Pool server is in fact the Lync Server. Procedure 1. On the Lync Server, select the Start button. 2. Select Microsoft Lync Server 2010 > Lync Server Management Shell > Run as administrator. The Lync Server Management Shell window opens. 3. Set the encryption mode to support both encrypted and non-encrypted calls as detailed in Enabling Support for Non-encrypted Calls and HD on the Lync Server on page Open port 5060 for TCP communication by entering this command: Set-CsRegistrar -Identity "registrar: <FQDN of your Front End Pool > " -SipServerTcpPort 5060 Where <FQDN of your Front End Pool > is the name of the computer of the Front End Pool, for example, Set-CsRegistrar "registrar: RVCN-IVIEW-W14.LYNC2010.COM" - SipServerTcpPort Check that the number of the TCP port changed to You can view the port number by entering this command: Get-CsService -Registrar The Lync Server settings are displayed. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 55

56 Configuring Your Scopia Video Gateway Deployment Figure 32: Checking the Lync Server settings Configuring the Lync Server without TLS (for TCP Environment) on page 54 Configuring the Lync Server to Trust Equinox Management in TCP Environment About this task Ensure that the Microsoft Lync Server and the Scopia Video Gateway can work together in the same deployment by configuring the Lync Server to trust the Equinox Management. Important: If you have a simple enterprise Lync deployment, the Front End Pool server is in fact the Lync Server. Procedure 1. On the Lync Server, select the Start button. 2. Select Microsoft Lync Server 2010 > Lync Server Management Shell > Run as administrator. 3. Create a new pool for your Equinox Management by entering this command: New-CsTrustedApplicationPool -Identity iviewpool. <your organization domain name > -Registrar: <FQDN of your Front End Pool > -Site 1 - ComputerFqdn <FQDN of your Equinox Management > - January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 56

57 Configuring the Microsoft Lync Server TreatAsAuthenticated $true -ThrottleAsServer $true -OutboundOnly $false Where <your organization domain name>, <FQDN of your Front End Pool>, and <FQDN of your Equinox Management > are variables that you need to change to relevant values. For example, New-CsTrustedApplicationPool -Identity iviewpool.lync2010.com- Registrar: RVCN-IVIEW-W14.LYNC2010.COM-Site 1 -ComputerFqdn iview.lync2010.com-treatasauthenticated $true -ThrottleAsServer $true -OutboundOnly $false Important: If the Application Pool is already added, skip this command. 4. Add the pool you created to the list of trusted servers of the Lync Server by entering this command: New-CsTrustedApplication -ApplicationId TrustedServer - TrustedApplicationPoolFqdn iviewpool. <your organization domain name > -Port EnableTcp Where <your organization domain name > is a variable that you need to modify. For example, New-CsTrustedApplication -ApplicationId TrustedServer - TrustedApplicationPoolFqdn iviewpool.lync2010.com -Port EnableTcp 5. Publish the topology on the Lync Server by entering this command: Enable-CsTopology 6. Enter Get-CsService -Registrar to verify that the new pool is registered and appears as a trusted application as in Figure 33: The new pool appears as a trusted application on page 58. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 57

58 Configuring Your Scopia Video Gateway Deployment Figure 33: The new pool appears as a trusted application 7. On the Lync Server, select the Start button. 8. Select Microsoft Lync Server 2010 > Lync Server Topology Builder > Run as administrator. The Topology Builder window opens. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 58

59 Configuring the Microsoft Lync Server 9. Select Download Topology from existing deployment and select OK. The Save Topology As dialog box opens. 10. Enter the topology file name and select Save. 11. Navigate to the Trusted applications servers folder in the left pane. 12. Open the Trusted applications servers folder and navigate to the new Equinox Management pool you created in 3 on page Right-click the new Equinox Management pool and select Edit Properties. The Edit Properties dialog box opens. 14. Select Limit service usage to selected IP addresses and enter the IP address of your Equinox Management. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 59

60 Configuring Your Scopia Video Gateway Deployment Caution: 15. Select OK. The default Lync configuration is to reject traffic from all IPs. Failing to correctly set the IP address results in authentication errors. 16. Right-click the Equinox Management pool in the left pane and select Topology > Publish. The Publish Topology window opens. 17. Select Next. If the confirmation message is displayed, select Yes to All. 18. Select Finish. Configuring the Lync Server without TLS (for TCP Environment) on page 54 Configuring the Lync Static Route without TLS (TCP Mode) About this task Setting up a static route is an optional configuration allowing a Lync client to dial an H.323 endpoint without having it as a registered Lync contact. Once set up, the static route defines the call paths so that they are redirected from the Lync network to the Equinox Management. The Equinox Management, in turn, redirects calls to the Scopia Video Gateway. For example, if a static route is defined for the domain "test.com", all Lync calls to that domain are forwarded according to the static route configuration. Thus, dialing to "1234@test.com" results in a call to "1234" that is sent directly to the configured FQDN. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 60

61 Configuring the Microsoft Lync Server Procedure 1. Select Start > Microsoft Lync Server 2010 > Lync Server Management Shell > Run as administrator. The Lync Server Management Shell window opens. 2. Create a new static routing by entering this command: $x=new-csstaticroute -TCPRoute -Destination <IP address of the Equinox Management> -Port MatchUri <Lync Server domain> For example, $x=new-csstaticroute -TCPRoute -Destination Port MatchUri lync2010.com 3. Add the new static route to a collection of routing configuration settings by entering this command: New-CsStaticRoutingConfiguration -Identity "service: Registrar: <FQDN of your Front End Pool > " -Route $x For example, New-CsStaticRoutingConfiguration -Identity "service:registrar:rvcn- IVIEW-W14.lync2010.com" -Route $x Important: If you have a simple enterprise Lync deployment, the Front End Pool server is in fact the Lync Server. 4. To create an additional static route, enter this command: Set-CsStaticRoutingConfiguration -Identity "service:registrar: <FQDN of your Front End Pool > " For example, Set-CsStaticRoutingConfiguration -Identity "service:registrar:rvcn- IVIEW-W14.lync2010.com" 5. Verify that the static routing is configured correctly: a. Enter this command: Get-CsStaticRoutingConfiguration b. Verify that the Identity value is set to the FQDN of your Front End Pool as in Figure 34: Checking the Identity value on page 62. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 61

62 Configuring Your Scopia Video Gateway Deployment Important: Figure 34: Checking the Identity value If there are additional Front End Pools deployed in your network, you should create this type of static route for each Front End Pool. The commands to create the extra static routes are the same as 1 on page 61 to 5 on page 61. If you have a simple enterprise Lync deployment, continue with 6 on page 62 to create additional static routes for additional Lync Servers. 6. All calls routed to the Equinox Management must come from the main Lync Server. If there are additional Lync Servers deployed in your network, you must create a static route from the front end of each Lync Server to the main Lync Server. The commands to create the extra static routes are the same as the previous steps in this procedure: a. On each of the remaining Lync Servers, select Start > Microsoft Lync Server 2010 > Lync Server Management Shell > Run as administrator. The Lync Server Management Shell window opens. b. Create a new static route to the main Lync Server using the same command as earlier, but insert the address of the main Lync Server: $x=new-csstaticroute -TCPRoute -Destination "<FQDN of the main Lync Server>" -Port MatchUri "<Matching rule >" c. Add the new static route to a collection of routing configuration settings by entering the same command as above: New-CsStaticRoutingConfiguration -Identity "service:registrar: <FQDN of the Front End of this Lync Server>" -Route $x d. To create an additional static route, enter the same command as above: Set-CsStaticRoutingConfiguration -Identity "service:registrar: <FQDN of the Front End of this Lync Server > " Configuring the Lync Server without TLS (for TCP Environment) on page 54 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 62

63 Configuring the Microsoft Lync Server Enabling New Active Directory Users on the Lync Server About this task You need to manually enable Active Directory users representing room systems, virtual rooms, and the auto-attendant feature you added in Creating User Groups and Users in the Microsoft Active Directory on page 35. Procedure 1. From a PC connect remotely to the Lync Server. 2. Open the Lync Server Control Panel. 3. Select Users in the left pane. 4. Select Enable users. 5. Select Add. 6. Select Find. 7. Select meeting rooms and virtual rooms that you want to enable. Press and hold the Ctrl key to select multiple users. 8. Select OK. 9. Select Use user s address. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 63

64 Configuring Your Scopia Video Gateway Deployment 10. Select Enable. Figure 35: Configuring Active Directory settings on the Lync Server The changes to the Active Directory users are added to the Lync Server after synchronization, typically after 10 minutes. Configuring the Microsoft Lync Server on page 54 Enabling Support for Non-encrypted Calls and HD on the Lync Server About this task Typically, video endpoints support HD resolution, while the Microsoft Lync Server supports standard definition resolution by default. You need to enable support for HD resolution on the Lync Server to enable end-to-end HD resolution calls. You also need to configure the encryption setting so that both encrypted and non-encrypted calls are supported on the Lync Server. Important: If the Lync Server is not connected when the configuration changes are applied, Equinox Management implements a keep-alive mechanism within a few minutes after the changes January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 64

65 Configuring the Microsoft Lync Server occur. After the connection with the Lynnc Server is re-established, Equinox Management retrieves the new Lync configuration. For detailed information on the commands listed in this procedure, see Microsoft s online documentation on Media Configuration Cmdlets athttp://technet.microsoft.com/en-us/library/ gg aspx Procedure 1. On the Lync Server, select the Start button. 2. Select Microsoft Lync Server 2010 > Lync Server Management Shell > Run as administrator. The Lync Server Management Shell window opens. 3. Configure encryption: a. Enter this command to change the setting: Set-CsMediaConfiguration -EncryptionLevel SupportEncryption b. Enter this command: Get-CsMediaConfiguration c. Verify that the EncryptionLevel value is SupportEncryption. See Figure 36: Checking the encryption and HD resolution values on page 65. Figure 36: Checking the encryption and HD resolution values 4. Configure HD resolution support: a. Enter this command to change the HD setting: PS C:\Users\Administrator.OCS2010>Set-CsMediaConfiguration - MaxVideoRateAllowed Hd720p15M b. Enter this command: PS C:\Users\Administrator.OCS2010>Get-CsMediaConfiguration c. Verify that the MaxVideoRateAllowed value is Hd720p15M. See Figure 36: Checking the encryption and HD resolution values on page 65. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 65

66 Configuring Your Scopia Video Gateway Deployment 5. Close the Lync Server Management Shell window. Configuring the Microsoft Lync Server on page 54 Configuring the Lync Server for TLS Environment By default the Microsoft Lync Server is configured to use the TLS protocol for security; however, if your Lync Server configuration was changed to allow it to work in the TCP environment, you may need to perform procedures in this section to reconfigure it for the TLS environment. Important: For a first-time installation of the Scopia Video Gateway, we strongly recommend to configure the Microsoft Lync Server to the TCP protocol. The TCP configuration procedure is detailed in Configuring the Lync Server without TLS (for TCP Environment) on page 54. Once the Scopia Video Gateway has all its functionality, reconfigure your Lync Server for TLS environment. Configuring the Microsoft Lync Server on page 54 Enabling the TLS Connection in Equinox Management on page 66 Configuring the Lync Server to Trust Equinox Management in TLS Environment on page 67 Configuring the Lync Static Route in TLS Environment on page 69 Enabling the TLS Connection in Equinox Management About this task You can configure your Equinox Management to use the TLS connection by modifying the configuration of the B2BUA component of the Equinox Management. Perform this procedure only if you want to secure your video network using TLS. Important: Using encryption is subject to local regulation. In some countries it is restricted or limited for usage. For more information, consult your local reseller. Procedure 1. Navigate to <install_dir>\sipserver\conf. 2. Open the UpdatedSIPConfig.xml file in a text editor. 3. Configure the DNS of the B2BUA component by setting values in the entire<dnsserverlist>element as shown in Figure 37: Adding the <DNSServerList> element on page 67: January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 66

67 Configuring the Microsoft Lync Server 4. Save and close the file. Figure 37: Adding the <DNSServerList> element 5. Restart the Equinox Management service and the Equinox Management SIP service. Configuring the Lync Server for TLS Environment on page 66 Configuring the Lync Server to Trust Equinox Management in TLS Environment About this task Ensure that the Microsoft Lync Server and the Scopia Video Gateway can work together in the same secure deployment by configuring the Lync Server to trust Equinox Management. Procedure 1. On the Lync Server, select the Start button. 2. Select Microsoft Lync Server 2010 > Lync Server Management Shell > Run as Administrator. The Lync Server Management Shell window opens. 3. Create a new Equinox Management pool for the TLS deployment by entering these comands: New-CsTrustedApplicationPool -Identity iviewpool.<your organization domain name> -Registrar:<FQDN of your Lync Server> -Site 1 - ComputerFqdn <FQDN of your iview Management Suite> - TreatAsAuthenticated $true -ThrottleAsServer $true -OutboundOnly $false Important: If the Application Pool is already added, skip this command. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 67

68 Configuring Your Scopia Video Gateway Deployment Add a new application with TLS: New-CsTrustedApplication -ApplicationId <new application name > - TrustedApplicationPoolFqdn iviewpool. <your organization domain > - Port 5061 Where <new application name> should be a unique string in this pool. For example, New-CsTrustedApplication -ApplicationId 201TLStrust - TrustedApplicationPoolFqdn iviewpool.lync2010.com -Port Publish the topology on the Lync Server by entering this command: Enable-CsTopology Important: It is recommended to publish the topology from the topology builder by opening the Topology Builder tool, selecting a location, and selecting Publish Topology in the Actions section. 5. Verify that the protocol is set to TLS: a. Enter this command: Get-CsTrustedApplication b. Check that the Protocol parameter value is Mtls. Figure 38: Checking the Protocol value 6. Close the Lync Server Management Shell window. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 68

69 Configuring the Microsoft Lync Server 7. Configure the trusted server IP address in the Topology Builder as explained in Configuring the Lync Server to Trust Equinox Management in TCP Environment on page 56, 7 on page 58 to 18 on page 60. Configuring the Lync Server for TLS Environment on page 66 Configuring the Lync Static Route in TLS Environment About this task Setting up a static route is an optional configuration allowing a Lync client to dial an H.323 endpoint without having it as a registered Lync contact. Once set up, the static route defines the call paths so that they are redirected from the Lync network to the Equinox Management. The Equinox Management, in turn, redirects calls to the Scopia Video Gateway. For example, if a static route is defined for the domain "test.com", all Lync calls to that domain are forwarded according to the static route configuration. Thus, dialing to "1234@test.com" results in a call to "1234" that is sent directly to the configured FQDN. Procedure 1. Select Start > Microsoft Lync Server 2010 > Lync Server Management Shell > Run as administrator. The Lync Server Management Shell window opens. 2. Create a new static routing by entering this command: $x=new-csstaticroute -TLSRoute -Destination "<FQDN of your iview Management Suite>" -Port MatchUri "<Matching rule >" - UseDefaultCertificate $True For example, $x = New-CsStaticRoute -TLSRoute -Destination "iview.lync2010.com" - Port MatchUri "lync2010.com" -UseDefaultCertificate $True 3. Add the new static route to a collection of routing configuration settings by entering this command: New-CsStaticRoutingConfiguration -Identity "service: Registrar: <FQDN of your Front End Pool > " -Route $x For example, New-CsStaticRoutingConfiguration -Identity "service:registrar:rvcn- IVIEW-W14.lync2010.com" -Route $x Important: If you have a simple enterprise Lync deployment, the Front End Pool server is in fact the Lync Server. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 69

70 Configuring Your Scopia Video Gateway Deployment 4. To create an additional static route, enter this command: Set-CsStaticRoutingConfiguration -Identity "service:registrar: <FQDN of your Front End Pool > " For example, Set-CsStaticRoutingConfiguration -Identity "service:registrar:rvcn- IVIEW-W14.lync2010.com" 5. Verify that the additional static route is created correctly. a. Enter this command: Get-CsStaticRoutingConfiguration b. Verify that the Identity value is set to the FQDN of your Front End Pool as in Figure 39: Checking the Identity value on page 70. Important: Figure 39: Checking the Identity value If there are additional Front End Pools deployed in your network, you should create this type of static route for each Front End Pool. The commands to create the extra static routes are the same as 1 on page 69 to 5 on page 70. If you have a simple enterprise Lync deployment, continue with 6 on page 70 to create additional static routes for additional Lync Servers. 6. All calls routed to the Equinox Management must come from the main Lync Server. If there are additional Lync Servers deployed in your network, you must create a static route from the front end of each Lync Server to the main Lync Server. The commands to create the extra static routes are the same as the previous steps in this procedure: a. On each of the remaining Lync Servers, select Start > Microsoft Lync Server 2010 > Lync Server Management Shell > Run as administrator. The Lync Server Management Shell window opens. b. Create a new static route to the main Lync Server using the same command as earlier, but insert the address of the main Lync Server: $x=new-csstaticroute -TLSRoute -Destination "<FQDN of the main Lync Server>" -Port MatchUri "<Matching rule >" - UseDefaultCertificate $True January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 70

71 Configuring Ports on the Scopia Video Gateway c. Add the new static route to a collection of routing configuration settings by entering the same command as above: New-CsStaticRoutingConfiguration -Identity "service:registrar: <FQDN of the Front End of this Lync Server>" -Route $x d. To create an additional static route, enter the same command above: Set-CsStaticRoutingConfiguration -Identity "service:registrar: <FQDN of the Front End of this Lync Server > " Configuring the Lync Server for TLS Environment on page 66 Configuring Ports on the Scopia Video Gateway This section provides instructions of how to configure the following ports and port ranges on the Scopia Video Gateway. Configuring Your Scopia Video Gateway Deployment on page 34 Configuring the Microsoft Lync Server on page 54 Configuring a Scopia Video Gateway in Equinox Management on page 75 Limiting TCP Port Range for H.245 on the Scopia Video Gateway on page 71 Configuring RTP/RTCP/SRTP Ports on the Scopia Video Gateway on page 73 Configuring UDP Port for RAS on the Scopia Video Gateway on page 74 Configuring TCP Port for Q.931 on the Scopia Video Gateway on page 74 Limiting TCP Port Range for H.245 on the Scopia Video Gateway About this task The Scopia Video Gateway designates ports for H.245 (signaling). H.245 is a control protocol used for multimedia communications that enables transferring information about the device capabilities, as well as opening/closing the logical channels that carry media streams. To provide additional security for your firewall, you can limit this range. Procedure 1. Log in to the Equinox Management administrator portal. 2. Select Devices > Devices by Type > Gateways. 3. Select the relevant gateway from the Gateways list. 4. Select the Configure tab (see Figure 40: Configuring a gateway from Equinox Management on page 72). January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 71

72 Configuring Your Scopia Video Gateway Deployment Figure 40: Configuring a gateway from Equinox Management 5. Select Advanced Parameters. The Advanced Parameters dialog box appears (see Figure 40: Configuring a gateway from Equinox Management on page 72). 6. To set the base port for the H.245 control channel protocol, do the following: a. Clear the values before proceeding to the next step. b. Enter h245baseport in the Command ID field. c. Enter the port value in the Value field. d. Select Save. e. Select Close 7. To set the port range for H.245, do the following: a. Clear the values before proceeding to the next step. b. Enter h245portrange in the Command ID field. c. Enter the port value in the Value field. d. Select Save. e. Select Close Configuring Ports on the Scopia Video Gateway on page 71 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 72

73 Configuring Ports on the Scopia Video Gateway Configuring RTP/RTCP/SRTP Ports on the Scopia Video Gateway About this task The Scopia Video Gateway designates ports for UDP audio media, and for UDP video media. In addition, the Scopia Video Gateway uses ports for TCP audio and for TCP video. Procedure 1. Log in to the Equinox Management administrator portal. 2. Select Devices. 3. Select Gateways in the sidebar menu. 4. Select the relevant gateway from the Gateways list. 5. Select the Configure tab (see Figure 40: Configuring a gateway from Equinox Management on page 72). 6. Select Advanced Parameters Settings. The Advanced Parameters dialog box appears (see Figure 40: Configuring a gateway from Equinox Management on page 72). 7. Set the UDP video base port by doing the following: a. Enter the advcmdmpcsetval command in the Command field. b. Enter the mf.baseport parameter in the Parameter field to set the UDP video base port. Important: To set the TCP video base port, enter mf.mvptcpbaseport in the Parameter field. c. Enter the port value in the Value field. d. Select Save. 8. Set the UDP audio base port by doing the following: a. Enter the setmprtpbaseport command in the Command field. b. Modify the port value in the Value field. c. Select Save. 9. Set the TCP audio base port by doing the following: a. Enter the setmptcpbaseport command in the Command field. b. Modify the port value in the Value field. c. Select Save. 10. Select Close. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 73

74 Configuring Your Scopia Video Gateway Deployment Configuring Ports on the Scopia Video Gateway on page 71 Configuring UDP Port for RAS on the Scopia Video Gateway About this task The Scopia Video Gateway designates port 1719 for RAS, the protocol for signaling messages. You can configure a different port for RAS (if, for example, port 1719 is busy). Procedure 1. Log in to the Equinox Management administrator portal. 2. Select Devices. 3. Select Gateways in the sidebar menu. 4. Select the relevant gateway from the Gateways list. 5. Select the Configure tab (see Figure 40: Configuring a gateway from Equinox Management on page 72). 6. Select Advanced Parameters Settings. The Advanced Parameters dialog box appears (see Figure 40: Configuring a gateway from Equinox Management on page 72). a. Select h323rasport from the Command ID list. b. Enter the port value in the Value field. c. Select Save. d. Select Close. Configuring Ports on the Scopia Video Gateway on page 71 Configuring TCP Port for Q.931 on the Scopia Video Gateway About this task The Scopia Video Gateway designates port 1720 for Q.931. Q.931 is a telephony protocol used for establishing and terminating the connections in H.323 calls. You can configure a different port for Q. 931 (if, for example, port 1720 is busy). Procedure 1. Log in to the Equinox Management administrator portal. 2. Select Devices. 3. Select Gateways in the sidebar menu. 4. Select the relevant gateway from the Gateways list. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 74

75 Configuring a Scopia Video Gateway in Equinox Management 5. Select the Configure tab (see Figure 40: Configuring a gateway from Equinox Management on page 72). 6. Select Advanced Parameters Settings. The Advanced Parameters dialog box appears (see Figure 40: Configuring a gateway from Equinox Management on page 72). a. Select h323sigport from the Command ID list. b. Enter the port value in the Value field. c. Select Save. d. Select Close. Configuring Ports on the Scopia Video Gateway on page 71 Configuring a Scopia Video Gateway in Equinox Management After your Microsoft Lync Server is configured, you need to configure your Scopia Video Gateway. This section describes the following procedures: Configuring Your Scopia Video Gateway Deployment on page 34 Configuring Ports on the Scopia Video Gateway on page 71 Connecting Equinox Management to Microsoft Components of Your Video Network on page 82 Adding a gateway in Equinox Management on page 75 Configuring the Scopia Video Gateway in Equinox Management on page 77 Dedicating the Scopia Video Gateway to an Organization on page 80 Making Custom Pictures Visible to External Users on page 81 Adding a gateway in Equinox Management About this task This section describes how to add or modify a gateway to your video network in Equinox Management. If you are configuring Equinox Management redundancy, deploy the primary server first, referring to component FQDNs rather than IP addresses (for example, smgmt.company.com). This reduces maintenance when servers switch to their backups. After you add a device, Equinox Management connects to it and retrieves additional information. You can then configure additional settings for your device, such as managing your bandwidth by using distributed Equinox Media Servers or Scopia Elite MCUs for a single videoconference. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 75

76 Configuring Your Scopia Video Gateway Deployment Before you begin Verify that your network connections are working and you performed the initial installation procedures for the devices (such as setting up the management IP address), as described in their Installation Guide. Add devices in the order listed in Administrator Guide for Avaya Equinox Management. If you have multiple locations in your network, make sure you have all the locations defined in Equinox Management before adding devices to the network. See Administrator Guide for Avaya Equinox Management. For Scopia Video Gateway deployments, ensure your Microsoft Lync Servers are fully configured before adding the gateway to Equinox Management. Procedure 1. Access the Equinox Management administrator portal. 2. Select the Devices tab. Figure 41: Devices Tab 3. Select the type of device you are adding or modifying, such as, Conferencing SIP Gateway, Equinox TIP Gateway or Scopia Video Gateway from the list in the sidebar. 4. Do one of the following: To add the device, select Add. To modify the basic attributes of the device, select the link of the device in the Name column, and select the Configure tab if present. 5. Enter or modify the basic settings for your device, as described in Table 7: Configuring your device's basic settings on page 77. Equinox Management then connects to the devices and retrieves additional information, such as the version number. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 76

77 Configuring a Scopia Video Gateway in Equinox Management Figure 42: Adding a new gateway Table 7: Configuring your device's basic settings Field Name Name IP Address Location Model Required GK Description Enter the name used to identify the device. This name will be displayed in the list of devices. Enter the device's management IP address, as configured during device installation. This is relevant only for service providers or deployments with multiple locations. Select the device s location. This field is necessary only when adding gatekeepers and gateways: If adding a gatekeeper profile, select the gatekeeper's vendor and model from the list. If adding a gateway profile, select the gateway type from the list. (For Equinox Media Servers, Scopia Elite MCUs, and Gateways only) Select the gatekeeper to which the device is registered to from the list. If you select None, the device can be added to Equinox Management but will not be connected until you register the device with the gatekeeper, and select the gatekeeper here. Configuring a Scopia Video Gateway in Equinox Management on page 75 Configuring the Scopia Video Gateway in Equinox Management About this task This section explains how to configure the,, Avaya Recording Gateway, Scopia Video Gateway settings in Equinox Management. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 77

78 Configuring Your Scopia Video Gateway Deployment Since the Gateway does not have its own web interface, its configuration is performed in Equinox Management. Equinox Management and gateways communicate in XML over TCP for control and configuration commands. You can secure the connection by configuring it to the TLS protocol. Make sure to generate the Avaya Equinox Management and Gateway certificates before configuring the connection to TLS (see Avaya Scopia Management Administrator Guide). Important: If your deployment consists of multiple Equinox Management servers, configure both Equinox Management servers before configuring the TLS connection for Scopia Video Gateway. Scopia Video Gateway is configured by default to switch to the presentation channel whenever an H.323 endpoint shares content during a video call by sending the shared content to the Lync client. If this feature does not suit the needs of the video call, you can disable it in Equinox Management. Before you begin 1. In Microsoft deployments, perform this procedure after your Microsoft Lync Server is configured. For more information on adding a Lync Server profile to Equinox Management, see Adding a Lync, Skype for Business, in Equinox Management on page Add the Gateway to Equinox Management by entering its basic settings, as described in Adding a gateway in Equinox Management on page 75. Procedure 1. Access the Equinox Management administrator portal. 2. Select Devices > Devices by Type > Gateways. 3. Select the gateway you are configuring. 4. Select the Configuration tab. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 78

79 Configuring a Scopia Video Gateway in Equinox Management Figure 43: Configuring the Gateway 5. Configure the gateway settings, as described in Table 8: Configuring settings for the gateway on page 79. Table 8: Configuring settings for the gateway Field Names Name In Maintenance Secure Connection Meeting Type Prefix Required Gatekeeper Current Gatekeeper Description You can modify the name that identifies the Gateway in Equinox Management. Select to indicate that the gateway is not online and is therefore not available. You typically select this option while upgrading the gateway The location of the gateway. The numeric dial prefix used by the gateway to identify this meeting type. The gatekeeper to which you want to register the gateway This (read-only) field displays the management IP address of the gatekeeper that this gateway is currently registered to. In most cases, this is the same gatekeeper selected in the Required Gatekeeper field. Table continues January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 79

80 Configuring Your Scopia Video Gateway Deployment Field Names Location SIP Proxy Server Transport Type Default SIP Domain NTP Server Time Zone MTU Size DNS Server 1, 2 Quality of Service QoS Priority Description If the current gatekeeper is not the same as the gatekeeper configured in the Required Gatekeeper field, an alarm is issued by Equinox Management. Relevant only for service providers or deployments with multiple locations. You can modify the gateway s location. The IP address of the SIP Proxy Server The enable transport type The default domain of the DIP Proxy Server The IP address of the NTP server The time zone of the NTP server The size of the maximum transmission unit, measured in bytes The IP address(es) of the organization s DNS server(s) Select the quality of service for the gateway 6. Select Apply. 7. Allow Equinox Management to access the Gateway: a. Select the Access tab. b. Enter the login name and password of the Gateway. The default username is admin and the default password is password. c. Select Apply. Configuring a Scopia Video Gateway in Equinox Management on page 75 Dedicating the Scopia Video Gateway to an Organization About this task In a service provider deployment, the Scopia Video Gateway can be dedicated as a resource to one of the organizations. This configuration can be implemented in conjunction with the limitation of concurrent calls per organization, as described in Defining Service Provider Organizations on page 87. Procedure 1. In the Equinox Management server, stop the Equinox Management services and the Equinox Management SIP service. 2. Navigate to <install_dir>\icm\tomcat\config. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 80

81 Configuring a Scopia Video Gateway in Equinox Management 3. Open the vcs-core.properties file in a text editor. 4. Verify that the parameter com.visionnex.vcms.core.ucgw.schedule.rejectcallwhennobestucgw is set to true. 5. Save and close the file. 6. Restart the Equinox Management and Equinox Management SIP services. Configuring a Scopia Video Gateway in Equinox Management on page 75 Making Custom Pictures Visible to External Users About this task Custom pictures are meant to replace the default Microsoft Lync picture next to the names of meeting rooms, virtual rooms, and auto attendants in the Contact List. The custom pictures help the user to quickly identify the videoconferencing equipment among the numerous contacts in the list. The custom pictures are part of Equinox Management and displayed in the Contact List once the users have installed them. External users are those people who are outside your organization firewall (for example, employees working from home, partners, or potential customers). They can also see the custom pictures if they are capable of accessing Equinox Management from the public network. Procedure 1. In the Equinox Management server, stop the Equinox Management services and the Equinox Management SIP service. 2. Navigate to <install_dir>\icm\tomcat\config. 3. Open the vcs-config.xml file in a text editor. 4. In the <host-url> tag, enter the FQDN of Equinox Management followed by port number Verify that your DNS server is capable of resolving the URL. 6. Save and close the file. 7. Restart the Equinox Management and Equinox Management SIP services. Configuring a Scopia Video Gateway in Equinox Management on page 75 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 81

82 Configuring Your Scopia Video Gateway Deployment Connecting Equinox Management to Microsoft Components of Your Video Network You must connect the Equinox Management to the Microsoft Active Directory and the Microsoft Lync Server. This procedure is performed after your Scopia Video Gateway is configured, including port configuration. Connection to the Lync Server is established by adding the Lync Server profile to the Equinox Management. Connection to the Active Directory is performed by configuring settings of the Active Directory on the Equinox Management. After the Active Directory is connected, you can download endpoints and virtual rooms from the Active Directory into the Equinox Management, and enable the Auto- Attendant feature if necessary. For any questions and/or assistance on Microsoft components, see the Microsoft documentation and/or Microsoft Support Services. The Auto-Attendant feature is available only in video networks where a AvayaMCU is deployed. Figure 44: Connecting Equinox Management to Microsoft components We recommend that you perform the following procedures in this order. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 82

83 Connecting Equinox Management to Microsoft Components of Your Video Network Important: For a first-time installation of the Scopia Video Gateway, we strongly recommend to configure the Microsoft Lync Server to the TCP protocol first. The TCP configuration procedure is detailed in Configuring the Lync Server without TLS (for TCP Environment) on page 54. Once the Scopia Video Gateway has all its functionality, reconfigure your Lync Server for TLS environment as described in Configuring the Lync Server for TLS Environment on page 66. Configuring Your Scopia Video Gateway Deployment on page 34 Configuring a Scopia Video Gateway in Equinox Management on page 75 Configuring a Third Party Deployment on page 106 Adding a Lync, Skype for Business, in Equinox Management on page 83 Defining Service Provider Organizations on page 87 Connecting Equinox Management with the LDAP Server on page 91 Downloading Users from the LDAP Server on page 94 Importing H.323 Endpoints from an External LDAP Server on page 96 Downloading Virtual Rooms from the LDAP Server on page 99 Enabling Auto-Attendant Support on page 101 Adding Access to Lync in Invitations on page 106 Adding a Lync, Skype for Business, in Equinox Management About this task To enable Equinox Management to operate with SIP endpoints, configure Equinox Management with an external SIP server to which the SIP endpoints are registered. For Scopia Video Gateway deployments, your Lync server is your SIP server. Add your Lync Server to Equinox Management so that it can use them as a SIP proxy/registrar. Microsoft s Lync Server is a SIP device. Equinox Management can communicate with SIP network devices when they are managed by Equinox Management. You can view the connection status between Equinox Management and your Lync Server by navigating to Devices > SIP Servers. This is the first step in configuring your Microsoft components, as described in Connecting Equinox Management to Microsoft Components of Your Video Network on page 82. Equinox Management is interoperable with these Microsoft environments/ : Microsoft Lync Server 2010 Microsoft Office Communications Server 2007 R2 Microsoft Lync Server 2010 Hosting Pack Broadsoft IPCentrix Cisco Unified Communications Manager (CUCM) January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 83

84 Configuring Your Scopia Video Gateway Deployment Procedure 1. Access the Equinox Management administrator portal. 2. Select the Devices tab. 3. Select SIP Servers in the sidebar. 4. Select Add. The Add SIP Server page appears. Figure 45: Adding a SIP server 5. Configure the SIP server settings in the Basic Settings section, as described in Table 9: Configuring SIP server settings on page 84. Important: In the fields below, the SIP server is the Microsoft Lync server. Table 9: Configuring SIP server settings Field Name Name IP Address/ FQDN Port Description Enter a name to identify your SIP server. This name is displayed in the list of SIP servers. Enter either the network name (FQDN) of the computer that you are using for SIP (specify all domain levels), or the computer's IP address. Important: For Scopia Video Gateway deployments, you must enter the FQDN. Enter the port used for SIP connections. The default port is 5060 for TCP/ UDP, and 5061 for TLS. Table continues January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 84

85 Connecting Equinox Management to Microsoft Components of Your Video Network Field Name Transport Type Model Location SIP Domain Use Outbound Proxy Description Select the transport protocol used for connecting to the SIP server, according to the selected port number. If the default port is 5060, select TCP/UDP; if it is 5061, select TLS. Select the type of SIP server you are using from the list. Select the location of the SIP server. This field is only relevant for distributed or service provider deployments. Enter the domain name of the SIP server's network. For example, if the FQDN is <SIP server name>.companyname, the SIP domain is 'companyname'. Select to forward SIP connections to a proxy SIP server. Otherwise, Equinox Management handles the SIP connection directly. Important: For Scopia Video Gateway deployments, this is mandatory and therefore selected by default. 6. If required by your SIP server, configure the registrar settings in the Registrar section, as described in Table 10: Configuring Registrar settings on page 85. A SIP Registrar is used to register IP addresses of SIP endpoints in the network with their SIP URIs. Table 10: Configuring Registrar settings Figure 46: Defining the SIP registrar Field Name Use Registrar Description Select to register Equinox Management to the SIP server. Important: For Scopia Video Gateway deployments, this is mandatory and therefore cannot be modified. Table continues January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 85

86 Configuring Your Scopia Video Gateway Deployment Field Name Registration User Name Use the "Auto Attendant" number as the registration name Refresh Rate (Seconds) Use Authentication Username Password Description Enter a name or number to use for registering Equinox Management to the SIP server, used to forward calls from SIP endpoints to Equinox Management. Important: For Scopia Video Gateway deployments, this value is the username of the Auto-Attendant, and cannot be modified. Select if you are using the Auto Attendant. The Auto-Attendant feature provides quick access to meetings hosted on Equinox Media Servers or Scopia Elite MCUs, allowing meeting participants to access a video menu and select menu options using DTMF. To enable the Auto Attendant, see the Enabling Auto-Attendant Support on page 101. The Auto-Attendant number is used for registering Equinox Management to the SIP server that forwards calls from SIP endpoints to Equinox Management. Important: For Scopia Video Gateway deployments, this is automatically selected and cannot be modified. Select the frequency with which Equinox Management sends updated user information to the SIP server, in seconds. This is not relevant for Lync or Skype for Business servers. If required by your SIP server, select this option to authorize Equinox Management to register to the SIP server. To enable Equinox Management to automatically register to the SIP server, enter the username and password required to access the SIP server. 7. Select OK to save your changes. You can modify these settings at any time by selecting the device name link in the SIP Servers list. 8. To support Microsoft's Director Server: a. Stop the Equinox Management service and the Equinox Management SIP service. b. Navigate to <install_dir>\icm\tomcat\config. c. Open the vcs-core.properties file in a text editor. d. Ensure the parameter vnex.vcms.core.ucgw.check.viaheaders; is set to true. e. Save and close the file. f. Restart the Equinox Management service and the Equinox Management SIP service. 9. To identify your organization's domain when calling external SIP endpoints, define the default network domain: a. Select > Advanced Parameters. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 86

87 Connecting Equinox Management to Microsoft Components of Your Video Network b. Find the vnex.vcms.core.conference.defaultdomain property and select the Edit icon. c. Enter the network's domain name in the Property Value field. For example, if the FQDN is <SIP server name>.companyname, the domain name is 'companyname'. d. Select Apply. 10. For Scopia Video Gateway deployments only: Configure your LDAP server in Equinox Management, as required by your deployment (see Connecting Equinox Management with the LDAP Server on page 91 for more details). Connecting Equinox Management to Microsoft Components of Your Video Network on page 82 Defining Service Provider Organizations on page 87 Defining Service Provider Organizations About this task This procedure is relevant for service provider (multi-tenant) deployments only. Add organizations by defining the following: Basic information about the organization, such as the name and address. The organization's system administrator. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 87

88 Configuring Your Scopia Video Gateway Deployment This administrator can then define additional administrators and other users within that organization (for details, see Administrator Guide for Equinox Management). Customized settings for this organization, such as number of licenses. Service providers can also price their services to organizations based on increasing the number of simultaneous participants on an Equinox Media Server or Scopia Elite MCU available in videoconferences. They can also regulate the number of participants using different protocols by limiting participants entering via gateways. These charges can be associated with a billing code unique to that organization, so it can be easily handled by a separate billing system. Procedure 1. Access the Equinox Management administrator portal. 2. Select Settings > Multiple-tenant > Organizations > Add. The Organization page appears. Figure 47: Adding an organization 3. Enter the organization's details, as described in Table 11: Entering the organization's basic details on page 89. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 88

89 Connecting Equinox Management to Microsoft Components of Your Video Network Table 11: Entering the organization's basic details Field Name Organization Name Alias Address 1 Description The organization's name. This name is used to identify this organization in Equinox Management. The alias of the organization, as defined in the organization profile. Aliases cannot contain spaces or any of the following punctuation characters: " ~! # $ % ^ & * ( ) = + [ ] { } ; < >,? /. The organization's address. Address 2 City State/Province Country Postal Code Telephone Fax The organization's telephone number. The organization's fax number. 4. Define the administrator for this organization by entering the information described in Table 12: Defining the organization's administrator on page 89. Table 12: Defining the organization's administrator Field Name Login ID Password Description Define the administrator's username and password, to be used when accessing Equinox Management. Enter the system administrator's address that is used by the organization. 5. (Optional) Customize settings and permissions for this organization, such as restricting Equinox Media Server or Scopia Elite MCU capacity and allowing customers to display their own logo on the Equinox Management interface, as described in Table 13: Customizing settings for organizations on page 89. Table 13: Customizing settings for organizations Field Name Allow Product Branding Allow Recording Description Select to allow organizations to display their own logo on the Equinox Management interface. Select to allow organizations to record meetings. This field appears only if a streaming and recording server has been added. Table continues January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 89

90 Configuring Your Scopia Video Gateway Deployment Field Name Allow Broadcast Limit Equinox Media Server Use to Limit Gateway Use to Limit AvayaVideo Gateway Use to Description Select to allow organizations to broadcast meetings. This field appears only if a streaming and recording server has been added. To limit the number of calls an Equinox Media Server can host at the same time, select and enter the number of calls. You can define the system behavior when this limit is reached by selecting Reject if over the limit. If left unchecked, some calls may need to be downgraded to audio-only if there is unusually high call volume. To limit the number of calls a Gateway can host at the same time, select and enter the number of calls. You can define the system behavior when this limit is reached by selecting Reject if over the limit. If left unchecked, some calls may need to be downgraded to audio-only if there is unusually high call volume. To limit the number of calls an AvayaVideo Gateway can host at the same time, select and enter the number of calls. You can define the system behavior when this limit is reached by selecting Reject if over the limit. If left unchecked, some calls may need to be downgraded to audio-only if there is unusually high call volume. 6. Define a unique Billing Code for this organization. This is used to associate charges to the organization, so it can be easily handled by a separate billing system. 7. To limit the meeting types that are available for this organization, select Edit and choose the meeting types. For more information about meeting types, see Administrator Guide for Equinox Management. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 90

91 Connecting Equinox Management to Microsoft Components of Your Video Network Figure 48: Selecting the meeting types 8. In the Receive Calls From section, select from whom the tenant can receive calls: Everyone Within organization only Any organization in the deployment 9. Select OK. Connecting Equinox Management to Microsoft Components of Your Video Network on page 82 Adding a Lync, Skype for Business, in Equinox Management on page 83 Connecting Equinox Management with the LDAP Server on page 91 Connecting Equinox Management with the LDAP Server About this task To allow user provisioning and synchronization of user profiles using an LDAP server, you have to configure the connection between Equinox Management and the LDAP server. Before you begin Depending on your organization's policies and the LDAP server you are using, decide whether to secure its connection with Equinox Management, as described in Avaya Scopia Management Administrator Guide. Procedure 1. Access the Equinox Management administrator portal. 2. Select Settings > Servers > LDAP Servers. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 91

92 Configuring Your Scopia Video Gateway Deployment 3. Select Add to add a new LDAP server, or select the required LDAP server entry to modify an existing LDAP server connection. 4. Select the type of LDAP server in the Directory Server Type field. If the Scopia Video Gateway is part of your deployment, select Active Directory Server. Figure 49: Basic LDAP server settings 5. Enter the directory server domain or directory server URL in the URL/Domain field, using the Idap:// prefix. For a secured connection between the Equinox Management and the LDAP server, do one of the following: Secure the connection with SSL certificates using the Idaps:// prefix (with an 's'). You need to also set up SSL on the LDAP server itself, as described in its documentation. Secure the credentials with MD5 (Microsoft Active Directory only): Enter the FQDN here (not the IP address). You then secure the credentials at a later stage, as part of Downloading Users from the LDAP Server on page 94. If securing user credentials, you cannot also secure the connection with the LDAP server. 6. Enter the directory server login ID and password in the relevant fields. Important: The user account needs to have read access to all user accounts that you want to synchronize to Equinox Management. This user account does not have to be part of the search base. 7. Select Configure to configure the LDAP Search Base field. The LDAP Tree window appears, showing all OUs (Organization Units) defined on the directory server. Figure 50: Tree structure in an enterprise deployment on page 93 illustrates the tree structure for an enterprise deployment. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 92

93 Connecting Equinox Management to Microsoft Components of Your Video Network Figure 50: Tree structure in an enterprise deployment 8. Select the OUs whose users you want to download. 9. Select Apply. The selected OUs are displayed in the LDAP Search Base field. 10. Select Apply. 11. After your Equinox Management is connected to the LDAP server, you can download users, as well as endpoints and virtual rooms: To download users from the LDAP server, see Downloading Users from the LDAP Server on page 94. To download endpoints, see Importing H.323 Endpoints from an External LDAP Server on page 96. To download virtual rooms, see Downloading Virtual Rooms from the LDAP Server on page 99. Connecting Equinox Management to Microsoft Components of Your Video Network on page 82 Defining Service Provider Organizations on page 87 Downloading Users from the LDAP Server on page 94 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 93

94 Configuring Your Scopia Video Gateway Deployment Downloading Users from the LDAP Server About this task This procedure describes how to download users from the LDAP server. Users are then displayed in the User tab and you can modify settings, such as the user profile of a group, and synchronize the database with Equinox Management. See Administrator Guide for Equinox Management for details. This procedure is part of the configuration described in Connecting Equinox Management to Microsoft Components of Your Video Network on page 82. Before you begin Make sure your Equinox Management is connected to the LDAP server as described in Connecting Equinox Management with the LDAP Server on page 91. You can assign a Equinox Management user profile to users and user groups defined in the LDAP server. This way, when users are downloaded from the LDAP server to Equinox Management, roles and permissions are automatically assigned. If user profiles are not defined, a default user profile is assigned to all users. For more information about user profiles, see Administrator Guide for Equinox Management. Procedure 1. Access the Equinox Management administrator portal. 2. Select the Settings > Servers > LDAP Servers. 3. Select the LDAP server from which you want to download users. Figure 51: LDAP Server Settings page 4. Click Select next to each user profile to assign LDAP user groups to a specific Equinox Management user profile. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 94

95 Connecting Equinox Management to Microsoft Components of Your Video Network Figure 52: Advanced section of LDAP Server Settings page You can assign multiple LDAP user groups to each Equinox Management user profile. By default, all users are assigned the Meeting Organizer profile. When configuring users in a service provider deployment, only select user groups belonging to the organization that you are currently configuring. 5. In the Default User Profile field, select a user profile you want to assign to all users for whom you did not specify a user profile, or set the Default User Profile field to Don t download to instruct Equinox Management not to download users that are not assigned to any Equinox Management user type. 6. If necessary, assign virtual rooms to the users, as described in Downloading Virtual Rooms from the LDAP Server on page To download only LDAP users with an address to Equinox Management, select Download only users with an address defined in the LDAP server. 8. Define how often users and meeting rooms are synchronized with the LDAP server by selecting a value from the Update Frequency list. 9. (Optional) If using Microsoft Active Directory, you can encrypt the user's LDAP credentials with MD5 by selecting Secure User credentials. Important: To use this feature, you must also: Define the LDAP server using its FQDN (not its IP address), as described in Connecting Equinox Management with the LDAP Server on page 91. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 95

96 Configuring Your Scopia Video Gateway Deployment In Microsoft Active Directory, enable the Store password using reversible encryption option. Do not secure user credentials if you secured the connection between the LDAP server and Equinox Management. 10. Select Apply. Connecting Equinox Management to Microsoft Components of Your Video Network on page 82 Connecting Equinox Management with the LDAP Server on page 91 Importing H.323 Endpoints from an External LDAP Server on page 96 Importing H.323 Endpoints from an External LDAP Server About this task This procedure describes how to import H.323 endpoints from your external LDAP server. Endpoints are predefined in the LDAP server and can be imported to Equinox Management as room systems and personal endpoints. Follow the procedure described below when: Your endpoints are defined in your LDAP server and your LDAP server is not configured with an H.350 search base. If your LDAP server is configured with an H.350 search base, follow the procedure described in Administrator Guide for Equinox Management. You are importing endpoints from the LDAP server for the first time. After this initial import, you can add endpoints by just synchronizing Equinox Management with the LDAP server. You want to synchronize only endpoints, and not users, in your LDAP directory with Equinox Management. To synchronize both users and endpoints in your LDAP server, see Administrator Guide for Equinox Management. You are modifying the endpoints' import settings, such as the E.164 dialing number. During this procedure you can define a prefix for endpoints you import (this is optional). The prefix is like an area code which is added to the start of a phone number. In this case, the prefix helps to route a call to a specific endpoint. The following is relevant for Scopia Video Gateway deployments: The LDAP Server is your Active Directory Server. When an endpoint is registered to an H.323 Gatekeeper, Avaya Equinox H.323 Gatekeeper, or Tandberg VCS, the status of the endpoint is visible in Lync clients. If imported endpoints are registered to any other gatekeeper, their status is not displayed on Lync clients. Before you begin 1. Define your LDAP server in Equinox Management, as described in Connecting Equinox Management with the LDAP Server on page Synchronize your LDAP server with Equinox Management. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 96

97 Connecting Equinox Management to Microsoft Components of Your Video Network Procedure Otherwise, personal endpoints belonging to users recently added to the LDAP but not listed in Equinox Management, are not imported to Equinox Management. 1. Access the Equinox Management administrator portal. 2. Select the Endpoints tab. 3. Select Add > Import from LDAP, and select the LDAP server's IP address from the list. 4. Select the type of endpoint you are importing, as follows: Room system: Select this option if you are importing room system endpoints. Personal endpoint: Select this option if you are importing personal endpoints. 5. Select Next. Figure 53: Selecting the endpoint type 6. Select the user group to which you want to assign personal endpoints or import room systems. 7. Select Next. The Import from LDAP Directory window opens. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 97

98 Configuring Your Scopia Video Gateway Deployment Figure 54: Configuring import settings for these endpoints 8. Configure the endpoints or room systems, as described in Table 14: Configuring import settings for these endpoints on page 98. Table 14: Configuring import settings for these endpoints Field Name Prefix Field Those endpoints are registered to Description If required by your dialing plan, enter a number to use for a prefix for these endpoints, according to the following guidelines: Must contain less than 11 digits Cannot already be used as a prefix for the auto-attendant, autorouting, or for other deployment components. Personal endpoints cannot have the same prefix as personal virtual rooms, when configuring the same LDAP attribute (such as telephonenumber). Select the LDAP attribute you want to use to retrieve the endpoint's information from the LDAP server, depending on your organization's dialing plan. The most commonly used attribute is telephonenumber. Important: Do not select non-numerical attributes, such as streetaddress or OU. Select the gatekeeper the endpoints are registered to. Important: If you select Other, these endpoints would not support Lync presence information. 9. Select Next > Finish. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 98

99 Connecting Equinox Management to Microsoft Components of Your Video Network The endpoints are added to Equinox Management. 10. Verify that endpoints were downloaded correctly: a. Select Endpoints > Imported Endpoints > From Active Directory. b. Verify that all endpoints defined in the LDAP server were downloaded and appear in the Endpoints tab. Connecting Equinox Management to Microsoft Components of Your Video Network on page 82 Downloading Users from the LDAP Server on page 94 Downloading Virtual Rooms from the LDAP Server on page 99 Downloading Virtual Rooms from the LDAP Server About this task Virtual rooms are literally virtual rooms that serve as a meeting place for your video network users. Virtual meeting rooms can be public (available for any user), or personal (assigned to a specific user, who is the only one allowed to schedule meetings in this room). Virtual meeting rooms appear in the Contact List of Lync Video Chat Clients, unlike personal endpoints which are not shown. To download virtual rooms from the LDAP server, the following conditions must be met: The value of the LDAP field mapped to the virtual room must be numeric. The virtual room number is not editable in the virtual room profile window. If the same virtual room number is defined for two users in the LDAP server, the virtual room is created and downloaded to Equinox Management for only one of the users. Virtual rooms are available only if an Equinox Media Server or Scopia Elite MCU is deployed. In deployments using Microsoft Lync, you can add a contact named My Virtual Room. This is a personal meeting place where the user can host meetings. When My Virtual Room is enabled in the system, it shows its availability in the contact list (while the user s personal virtual room indicates an unknown presence). Before you begin Check the prefixes used for the auto-attendant and for other components within your network, such as Equinox Media Servers or Scopia Elite MCUs, and Gateway. You cannot assign the prefixes already used in the system, because the prefixes assigned to virtual rooms must be unique. Decide on SIP URIs for the users to whom virtual rooms are assigned (for example, bfmyvr@lync2010.com). For Microsoft Lync and OCS deployments, users can add a contact called My Virtual Room to Lync or OCS clients. To enable this setting, verify your Equinox Management is set for Lync integration. Navigate to Settings > Unified Communications > Microsoft Lync/OCS, and select Enable Microsoft Lync Integration. Procedure 1. Access the Equinox Management portal. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 99

100 Configuring Your Scopia Video Gateway Deployment 2. Select Settings > Servers > LDAP Servers. 3. Select the LDAP server to which organization users were added. 4. Configure personal and public virtual rooms, as described in Table 15: Configuring settings for downloading virtual meeting rooms on page 100. Figure 55: Defining virtual rooms Table 15: Configuring settings for downloading virtual meeting rooms Field Select Virtual Room Number Description Select the LDAP user group to which you assigned the public virtual rooms on the LDAP server. A public virtual room is not associated with any user, and therefore can be assigned to a group of users, like users of the Microsoft Lync client. This is visible only when Microsoft OCS/Lync integration is enabled in Equinox Management. This is relevant for both personal and public virtual rooms. Define the virtual room number as follows: a. Enter a number that you want to use for a prefix. Use any number that is shorter than 11 digits and is not used as a prefix for the auto attendant or for other deployment components. b. Select the LDAP attribute to use when generating the number of the virtual rooms, according to your dialing plan. Typically, the telephonenumber attribute is used. 5. Define how often users and meeting rooms are synchronized with the LDAP server by selecting a value from the Update Frequency list. 6. Select Apply. 7. Select Synchronize All on the LDAP Server Settings page. Users from the LDAP server downloaded into Equinox Management as virtual meeting rooms. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 100

101 Connecting Equinox Management to Microsoft Components of Your Video Network 8. Verify that the virtual meeting rooms were downloaded correctly: a. Select Users > Active Directory > All. b. Verify that the virtual meeting rooms defined in the LDAP server were downloaded and appear on the Users tab. 9. If necessary, enable additional personal virtual rooms (My Virtual Rooms): a. Select Settings > Unified Communications > Microsoft Lync/OCS. b. Select Enable "My Virtual Room" Contact. Figure 56: Enabling Microsoft Lync/OCS integration c. Enter the SIP URI of My Virtual Room as configured in the Active Directory user, in the Microsoft Lync Account field. d. Select Apply. Connecting Equinox Management to Microsoft Components of Your Video Network on page 82 Importing H.323 Endpoints from an External LDAP Server on page 96 Enabling Auto-Attendant Support on page 101 Enabling Auto-Attendant Support About this task The Auto-Attendant feature provides quick access to meetings hosted on Equinox Media Servers or Scopia Elite MCUs, allowing meeting participants to access a video menu and select menu options using DTMF. This procedure describes how to enable the Auto-Attendant feature in Equinox Management. You must designate one meeting type for the Auto-Attendant. For more information about meeting types, including configuring its bandwidth and resolution, see Administrator Guide for Equinox Management. To enable the Auto-Attendant feature, you first configure a meeting type with Auto-Attendant support, and then configure the Auto-Attendant settings. In service provider (multi-tenant) January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 101

102 Configuring Your Scopia Video Gateway Deployment deployments, the service provider administrator configures the meeting type, and the organization administrator configures the Auto-Attendant settings. Before you begin 1. When integrating Equinox Solution with the Avaya Aura Conferencing server, use the same number for both the Avaya and Avaya Auto-Attendant. You must also enable integration, as described in Administrator Guide for Equinox Management. 2. Choose a number you want to assign to the Auto-Attendant feature. Important: In service provider deployments, service provider administrators should allocate a range of numbers each organization can use, according to the rules listed below. Organization administrators should select a number from this range for the Auto-Attendant. The Auto-Attendant number must be different from the following numbers: All E.164 numbers of your organization's endpoints. In service provider deployments, this number must be different from endpoints of all organizations. Equinox Media Server or Scopia Elite MCU meeting type Gateway service H.323 Gatekeeper zone prefix Auto-Route number 3. Synchronize the Equinox Media Server s or Scopia Elite MCU's meeting types with Equinox Management, as described in Administrator Guide for Equinox Management. 4. If your deployment uses a third-party gatekeeper, ensure that the gatekeeper has a prefix configured to direct calls to the Auto-Attendant. 5. For Scopia Video Gateway deployments only: Create an Active Directory user dedicated to the Auto-Attendant, to be displayed as a contact on Lync clients. Use the Auto-Attendant's URI when configuring the Auto-Attendant's settings in Equinox Management. Procedure 1. Access the Equinox Management administrator portal. 2. Select the Settings tab. 3. Configure the meeting type for Auto-Attendant support, as follows: Important: In service provider deployments, this step is performed by the service provider administrator. a. Select Settings > Meetings > Meeting Types. b. Select the meeting type for which you want to configure Auto-Attendant support, from the Name column. The Meeting Type Details page appears (Figure 57: Configuring Auto-Attendant support for a meeting type on page 103). January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 102

103 Connecting Equinox Management to Microsoft Components of Your Video Network Figure 57: Configuring Auto-Attendant support for a meeting type c. Select Auto-Attendant Support. d. Select Apply. 4. Configure settings for the Auto-Attendant, as follows: Important: In service provider deployments, this is done by each organization's administrator. a. Select Settings > Meetings > Auto-Attendant. b. Select Enable Auto Attendant. Figure 58: Enabling Auto-Attendant c. Configure the Auto-Attendant settings, as described in Table 16: Configuring Auto- Attendant settings on page 104. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 103

104 Configuring Your Scopia Video Gateway Deployment Table 16: Configuring Auto-Attendant settings Field Name Specify the Auto-Attendant Number Allow creating meetings Prompt for a meeting PIN while creating new meetings Display all current meetings on Auto-Attendant Automatically route incoming calls according to schedule. Specify the Auto Route number Description Assign an Auto-Attendant number to the meeting type you configured with Auto-Attendant support. For details on choosing a number for the Auto-Attendant, see the prerequisites above. Select to allow guests to create meetings by dialing the Auto-Attendant. Select to prompt regular users to enter a meeting PIN when creating new meetings. Select to display all ongoing meetings on the Auto- Attendant. Select to route all meetings hosted by the Equinox Media Server or Scopia Elite MCU to the Auto-Attendant, and assign a unique auto-route number, which is used by the gatekeeper to route calls to the Equinox Media Server or Scopia Elite MCU. This number cannot be the same as any of the following: Auto-Attendant number Equinox Media Server or Scopia Elite MCU meeting type Virtual room prefix Gateway service H.323 Gatekeeper zone prefix d. Select Apply. 5. For Scopia Video Gateway deployments only, enable the Auto-Attendant contact to be displayed as a contact on your Lync client: Important: In service provider deployments, the service provider's administrator first enables Microsoft Lync integration, and then each organization defines the Auto-Attendant contact. a. Select Settings > Unified Communications > Microsoft Lync/OCS. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 104

105 Connecting Equinox Management to Microsoft Components of Your Video Network Figure 59: Adding an Auto-Attendant user to Lync clients b. Select Enable Microsoft Lync Integration. c. Select Enable "Auto Attendant" Contact. d. Enter the URI of the user you created for the Auto-Attendant in Active Directory, in the Microsoft Lync Account field. The user's URI depends on the attributes configured in your LDAP directory. An example URI could be The Auto-Attendant user is displayed as a contact on Lync clients. When dialing the Auto-Attendant from your Lync, the Auto-Attendant welcome screen appears. e. Select Apply. Connecting Equinox Management to Microsoft Components of Your Video Network on page 82 Downloading Virtual Rooms from the LDAP Server on page 99 Adding Access to Lync in Invitations on page 106 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 105

106 Configuring Your Scopia Video Gateway Deployment Adding Access to Lync in Invitations About this task As an administrator, you decide on the default text which accompanies videoconference invitations via . The invitation text is compartmentalized into sections which relate to the different implementations your organization supports. This section details how to activate the link for joining a videoconference using the Lync client. For more information regarding the Avaya Equinox Add-in for Microsoft Outlook configuration, see the User Guide foravaya Equinox Add-in for Microsoft Outlook. Procedure 1. Log in to Avaya Equinox Management. 2. Select Settings > Meetings > Invitations. 3. Select Add LYNC/OCSR2 client access information. Figure 60: Adding a Lync link for joining the videoconference from 4. Select Apply to save the change. Connecting Equinox Management to Microsoft Components of Your Video Network on page 82 Enabling Auto-Attendant Support on page 101 Configuring a Third Party Deployment About this task If your H.323-based video network is not a Equinox Solution, the Scopia Video Gateway and Equinox Management will fully integrate into your video network allowing you to make calls from an H.323 endpoint to a Lync client and vice versa. However, please notice that there are several features whose behavior is different in the third party deployments: Presence information for H.323 endpoints is unavailable. The presence status for these endpoints is always shown as online in the Lync Client Contact list. You may still call each one of these endpoints, but the result of the call is unpredictable. Third party MCUs do not appear in the Lync Client Contact list: users need to dial the sip address of a video conference to join. Figure 61: Dialing a third-party MCU from the Lync Client contact list on page 107 depicts such type of dialing. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 106

107 Configuring a Third Party Deployment Figure 61: Dialing a third-party MCU from the Lync Client contact list For Equinox Management to interoperate with third party gatekeepers, they need to be configured as neighbors to the Avaya Equinox Management s internal gatekeeper. For details on adding a third party gatekeeper in Equinox Management, see Adding a gateway in Equinox Management on page 75. To import endpoints registered to third party gatekeepers, see Importing H.323 Endpoints from an External LDAP Server on page 96. Configuring Your Scopia Video Gateway Deployment on page 34 Connecting Equinox Management to Microsoft Components of Your Video Network on page 82 Securing Your Video Network Using TLS on page 109 Adding a Neighbor Gatekeeper on page 107 Defining a Third-Party MCU in Avaya Equinox Management on page 108 Adding a Neighbor Gatekeeper About this task Perform this procedure to add your third party gatekeeper as a neighbor to the H.323 Gatekeeper. Neighbor gatekeepers are stored in a Neighbor Table in the H.323 Gatekeeper database. The H. 323 Gatekeeper uses this table for resolving destination IP addresses when the source endpoint is not in the same zone as the destination endpoint. The list of Neighbor gatekeepers and their IP addresses allows a gatekeeper to search for and communicate directly with the gatekeeper of the destination endpoint. As a result, there is no need for a gatekeeper to multicast a Location Request message (LRQ) to the entire network in order to resolve addresses from other zones. This makes call routing to the other zones more efficient and reliable. To define Neighbor gatekeepers, you specify the IP address and port number of the Neighbor Gatekeeper. You can also specify a zone prefix. Each Neighbor gatekeeper should have a unique prefix. If you specify a zone prefix, the H.323 Gatekeeper routes LRQ messages and calls only to the Neighbor gatekeeper that starts with the zone prefix in the destination address. Procedure 1. Select the Hierarchy tab. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 107

108 Configuring Your Scopia Video Gateway Deployment 2. Select the Neighbors tab. 3. Select Add. The Add Neighbor dialog box opens. Figure 62: Adding a neighbor gatekeeper 4. Enter the zone prefix for the neighbor gatekeeper. 5. Enter a free text description for the neighbor gatekeeper. 6. Enter the IP address for the neighbor gatekeeper. 7. Enter the neighbor gatekeeper port. 8. Verify that Use Cisco proxy is unchecked. 9. Select Upload. Configuring a Third Party Deployment on page 106 Defining a Third-Party MCU in Avaya Equinox Management About this task Integrating a third-party party MCU enables users to dial in to MCU meeting rooms as if they were endpoints. You can view the presence of these meeting rooms in your Lync client. Important: The virtual room icon only appears for AvayaMCU s. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 108

109 Securing Your Video Network Using TLS Procedure 1. Register the third-party MCU to your gatekeeper, as follows: If your deployment includes a SCOPIA ECS Gatekeeper, Avaya Equinox H.323 Gatekeeper, or Tandberg VCS, register the MCU directly to the gatekeeper. If your deployment includes a third-party gatekeeper, register the MCU after H.323 Gatekeeper your third-party gatekeeper to Avaya Equinox H.323 Gatekeeper. 2. Access your Active Directory and create a user group for all the MCU rooms you want to add. 3. Add a user for each MCU room to the group, with the telephone number of the MCU room. 4. Enable these users in Lync, as described in Enabling New Active Directory Users on the Lync Server on page Import the endpoints registered to the third party gatekeeper as described in Importing H.323 Endpoints from an External LDAP Server on page Add the rooms to your Lync client Contact List. Presence is indicated for each of the rooms. You can call them and reach the third-party MCU. Configuring a Third Party Deployment on page 106 Securing Your Video Network Using TLS This section describes how to secure the connection between Scopia Video Gateway and Equinox Management. Important: Using encryption is subject to local regulation. In some countries it is restricted or limited for usage. For more information, consult your local reseller. TLS enables network devices to communicate securely using certificates, to provide authentication of the devices and encryption of the communication between them. To create a TLS certificate, you need to generate a certificate signing request (CSR) and send it to the certification authority (CA) for signing. A CA has its own certificate, known as the CA root certificate. When the CA signed certificate is ready, you upload it into the component for which it was created, together with the CA root certificate. Once this is done, the component can authenticate itself and is ready for TLS connection. In some cases, when the CA signing the certificate is not a known trusted source, you must obtain an additional certificate vouching for the trustworthiness of the CA. These certificates are known as intermediary certificates, and must be signed by a trusted CA. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 109

110 Configuring Your Scopia Video Gateway Deployment Some third-party components of your deployment may have pre-installed certificates. For example, you do not need to generate certificates for the Microsoft Lync Server and the Microsoft Office Communications Server. Each time a video network device starts the TLS communication session, it sends its own signed certificate together with the CA root certificate and requests the same certificates from the other devices to which it wants to connect. After both devices verify each other's identity, a secure TLS connection can be established. Exchanging certificates between devices is part of the TLS protocol; it happens in the background and is transparent to a user. Figure 63: Establishing TLS connection The following set of procedures secure the connection between Equinox Management and the gateway. Perform these tasks in the order listed below: 1. Decide which certificates products deployed in your video network need, as described in Planning the Required Certificates for TLS on page Generate and upload the Equinox Management's certificate for videoconferencing components as described in the Administrator Guide for Equinox Management. 3. Perform the procedure in Generating and Uploading Certificates for the Scopia Video Gateway on page If the CA used to identify the Scopia Video Gateway is different from the CA which identifies Equinox Management, upload the gateway's CA root and intermediate certificates into Equinox Management as described in the Administrator Guide for Equinox Management. 5. Perform the procedure in Enabling Encryption on Scopia Video Gateway on page 123. Configuring Your Scopia Video Gateway Deployment on page 34 Configuring a Third Party Deployment on page 106 Planning the Required Certificates for TLS on page 111 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 110

111 Securing Your Video Network Using TLS Generating and Uploading Certificates for the Scopia Video Gateway on page 118 Enabling Encryption on Scopia Video Gateway on page 123 Planning the Required Certificates for TLS When a device establishes a secure TLS connection with another component, it requests a signed certificate verifying the other component's identity. The signature on the certificate must be from a known (trusted) certification authority (CA). Important: Figure 64: Certificate Request Using encryption is subject to local regulation. In some countries it is restricted or limited for usage. For more information, consult your local reseller. There are several types of TLS connections: Standard TLS, where all certificates are signed by the same CA. Unique CAs, where each certificate is signed by a different CA. Unknown gateway CA, where the gateway s certificate is signed by an unknown (untrusted) CA. Unknown Equinox Management CA, where Equinox Management's certificate is signed by an unknown (untrusted) CA. Mutually unknown CAs, where both components carry certificates signed by CAs that are unknown to each other. Each situation requires a different set of certificates to be uploaded to each of the components. Typically, the certificates are all signed by the same CA. Some unique deployments, such as service provider deployments, may use multiple CAs. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 111

112 Configuring Your Scopia Video Gateway Deployment A CA s signature is always verified by its root certificate, which identifies the CA and is self-signed by that CA. When a device receives a certificate as part of TLS negotiations, it must verify that the CA signing the certificate is trusted, so it must have the CA s root certificate uploaded. Standard TLS These connections use the same CA for signing all certificates on both sides. In this case, you need to upload two certificates to Equinox Management and two for the gateway (Figure 65: Standard TLS: Component Certificates and a CA Root Certificate on page 112). Figure 65: Standard TLS: Component Certificates and a CA Root Certificate Upload the following certificates to the Equinox Management: - A certificate identifying Equinox Management, signed by the CA. This is sent to the gateway as part of the TLS negotiation. - A root certificate verifying the CA s identity, self-signed by that CA. This is used by Equinox Management to verify the certificate sent by the gateway. On the gateway side, upload the following certificates (Figure 65: Standard TLS: Component Certificates and a CA Root Certificate on page 112): - A certificate identifying the gateway, signed by the same CA. This is sent to Equinox Management as part of the TLS negotiation. - A copy of the root certificate verifying the CA s identity, self-signed by the CA. This is used by the gateway to verify the certificate sent by Equinox Management. Unique CAs When certificates are signed by different CAs, each CA requires its own root certificate to be uploaded for authentication. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 112

113 Securing Your Video Network Using TLS For example, in Figure 66: TLS connection using certificates signed by different CAs on page 113, the certificate identifying Equinox Management is signed by CA1, while the the gateway's certificate is signed by CA2. This requires three certificates to be uploaded to Equinox Management and two for the gateway (Figure 66: TLS connection using certificates signed by different CAs on page 113). Figure 66: TLS connection using certificates signed by different CAs When each certificate is signed by a different CA (Figure 66: TLS connection using certificates signed by different CAs on page 113), upload the following certificates to the Equinox Management: - A certificate identifying Equinox Management, signed by trusted CA1. This is sent to the gateway as part of the TLS negotiation. - A root certificate from the trusted CA1 verifying CA1 s identity, self-signed by CA1. This is used by Equinox Management to authenticate its certificate. - A root certificate from the trusted CA2 verifying CA2 s identity, self-signed by CA2. This is used by Equinox Management to authenticate the certificate sent by the gateway, which is signed by CA2. On the gateway side, upload the following certificates (Figure 66: TLS connection using certificates signed by different CAs on page 113): - A certificate identifying the gateway, signed by trusted CA2. This is sent to Equinox Management as part of the TLS negotiation. - A root certificate verifying CA1 s identity, self-signed by trusted CA1. This is used by the gateway to verify the certificate sent by Equinox Management, which is signed by CA1. Unknown gateway CA January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 113

114 Configuring Your Scopia Video Gateway Deployment If the CA of the gateway s certificate is unknown, it cannot be trusted unless it comes with an intermediate certificate, which vouches for the trustworthiness of the unknown CA. Intermediate certificates must be signed by a trusted CA. For example, in Figure 67: Signature of Gateway Certificate from Unknown CA on page 114, the certificate identifying the gateway is signed by CA3, which may be known and trusted by those who installed the gateway, but in this scenario CA3 is not trusted by Equinox Management. Meanwhile Equinox Management s certificate is signed by CA1, a trusted CA. This scenario requires four certificates to be uploaded to Equinox Management and two for the gateway (Figure 67: Signature of Gateway Certificate from Unknown CA on page 114). Figure 67: Signature of Gateway Certificate from Unknown CA When CA3 is untrusted (Figure 67: Signature of Gateway Certificate from Unknown CA on page 114), the certificates to upload to the Equinox Management are: - A certificate identifying Equinox Management, signed by trusted CA1. This is sent to the gateway as part of the TLS negotiation. - A root certificate from CA1 verifying CA1 s identity, self-signed by trusted CA1. This is used by Equinox Management to authenticate its certificate. - An intermediate certificate vouching for the trustworthiness of CA3, signed by trusted CA2. This is used to trust the certificate sent by the gateway, which is signed by CA3. - A root certificate from CA2 verifying CA2 s identity, self-signed by trusted CA2. This is used by Equinox Management to authenticate the intermediate certificate, which is signed by CA2. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 114

115 Securing Your Video Network Using TLS On the gateway side, the certificates to be uploaded are (Figure 67: Signature of Gateway Certificate from Unknown CA on page 114): - A certificate identifying the gateway, signed by CA3, an unknown CA. This certificate is sent to Equinox Management as part of the TLS negotiation. - A root certificate from CA1 verifying CA1 s identity, self-signed by trusted CA1. This is used by the gateway to verify the certificate sent by Equinox Management, which is signed by CA1. Unknown Equinox Management CA When Equinox Management s certificate is signed by a CA unknown to the gateway, you must upload an intermediate certificate for the untrusted CA signed by a trusted CA to vouch for its authenticity. In the example of Figure 68: Signature of Equinox Management Certificate from Unknown CA on page 115, Equinox Management s certificate is signed by CA3, an unknown CA, while the gateway s certificate is signed by CA2, a trusted CA. This requires four certificates to be uploaded to Equinox Management and three for the gateway (Figure 68: Signature of Equinox Management Certificate from Unknown CA on page 115). Figure 68: Signature of Equinox Management Certificate from Unknown CA When CA3 is untrusted by the gateway (Figure 68: Signature of Equinox Management Certificate from Unknown CA on page 115), the certificates to upload to the Equinox Management are: - A certificate identifying Equinox Management, signed by CA3, a CA unknown to the gateway. This is sent to the gateway as part of the TLS negotiation. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 115

116 Configuring Your Scopia Video Gateway Deployment - An intermediate certificate vouching for the trustworthiness of CA3, signed by trusted CA1. This is used to trust Equinox Management s identity certificate, which is signed by CA3. - A root certificate from CA1 verifying CA1 s identity, self-signed by trusted CA1. This is used by Equinox Management to authenticate the intermediate certificate, which was signed by CA1. - A root certificate from CA2 verifying CA2 s identity, self-signed by trusted CA2. This is used by Equinox Management to authenticate the gateway s certificate, which is signed by CA2. On the gateway side, the certificates to be uploaded are (Figure 68: Signature of Equinox Management Certificate from Unknown CA on page 115): - A certificate identifying the gateway, signed by trusted CA2. This certificate is sent to Equinox Management as part of the TLS negotiation. - An intermediate certificate vouching for the trustworthiness of CA3, signed by trusted CA1. This is used to trust Equinox Management s identity certificate, which is signed by CA3. - A root certificate from CA1 verifying CA1 s identity, self-signed by trusted CA1. This is used by the gateway to verify the intermediate certificate, which is signed by CA1. Mutually unknown CAs In the final scenario, both components use certificates signed by CA s which are not recognized by each other. In this case, there needs to be two intermediate certificates, one for each of the untrusted CAs, to vouch for their authenticity. For example, in Figure 69: Signature of Both Certificates are from Untrusted CAs on page 117, the certificate identifying the gateway is signed by CA4, an unknown CA, while Equinox Management s certificate is signed by CA3, also untrusted. This would require five certificates to be uploaded to Equinox Management and three for the gateway (Figure 69: Signature of Both Certificates are from Untrusted CAs on page 117). January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 116

117 Securing Your Video Network Using TLS Figure 69: Signature of Both Certificates are from Untrusted CAs When CA3 is untrusted by the gateway and CA4 is untrusted by Equinox Management (Figure 68: Signature of Equinox Management Certificate from Unknown CA on page 115), the certificates to upload to the Equinox Management are: - A certificate identifying Equinox Management, signed by CA3, a CA unknown to the gateway. This is sent to the gateway as part of the TLS negotiation. - An intermediate certificate vouching for the trustworthiness of CA3, signed by trusted CA1. This is used to trust Equinox Management s identity certificate, which is signed by CA3. - A root certificate from CA1 verifying CA1 s identity, self-signed by trusted CA1. This is used by Equinox Management to authenticate CA3 s intermediate certificate, which was signed by CA1. - A root certificate from CA2 verifying CA2 s identity, self-signed by trusted CA2. This is used by Equinox Management to authenticate CA4 s intermediate certificate, which is signed by CA2. - An intermediate certificate vouching for the trustworthiness of CA4, signed by trusted CA2. This is used to trust the gateway s identity certificate, which is signed by CA4. On the gateway side, the certificates to be uploaded are (Figure 68: Signature of Equinox Management Certificate from Unknown CA on page 115): - A certificate identifying the gateway, signed by CA4, a CA unknown to Equinox Management. This is sent to Equinox Management as part of the TLS negotiation. - An intermediate certificate vouching for the trustworthiness of CA3, signed by trusted CA1. This is used to trust Equinox Management s identity certificate, which is signed by CA3. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 117

118 Configuring Your Scopia Video Gateway Deployment - A root certificate from CA1 verifying CA1 s identity, self-signed by trusted CA1. This is used by the gateway to verify the intermediate certificate, which is signed by CA1. For more information on uploading certificates to the gateway and to Equinox Management, see Administrator Guide for Equinox Management. If you have the Equinox Management redundant solution, it is important to configure redundancy before proceeding with TLS configuration. See Administrator Guide for Equinox Management for details. Securing Your Video Network Using TLS on page 109 Generating and Uploading Certificates for the Scopia Video Gateway About this task This procedure describes how to generate and upload a TLS certificate, that is used for encrypting communications between Scopia Video Gateway and other components of your video deployment. Important: Using encryption is subject to local regulation. In some countries it is restricted or limited for usage. For more information, consult your local reseller. To create a TLS certificate, you need to generate a certificate signing request (CSR) and send it to the certification authority (CA) for signing. A CA has its own certificate, known as the CA root certificate. When the CA signed certificate is ready, you upload it into the component for which it was created, together with the CA root certificate. Once this is done, the component can authenticate itself and is ready for TLS connection. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 118

119 Securing Your Video Network Using TLS Figure 70: Typical TLS communication with a gateway In some cases, when different CAs are used for signing certificates in your deployment, you must obtain an additional certificate vouching for the trustworthiness of these CAs. These certificates are known as intermediary certificates, and must be signed by a trusted CA. For more information, see Planning the Required Certificates for TLS on page 111. Before you begin Upload all certificates for Avaya Equinox Management, including certificates signed by the CA to identify Equinox Management, and root and intermediate certificates (if necessary) to identify the CA. See the Administrator Guide for Equinox Management for details. Procedure 1. Access the Equinox Management administrator portal. 2. Select Devices > Devices by Type > Gateways and navigate to the gateway to create its CSR. 3. Select the Certificate tab. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 119

120 Configuring Your Scopia Video Gateway Deployment 4. Select Create a new CSR. Figure 71: Creating a CSR for the gateway The Save Certificate Request window opens displaying the certificate request. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 120

121 Securing Your Video Network Using TLS Figure 72: The Save Certificate Request 5. Copy the certificate request into a separate text file and save it with the.csr extension. 6. Select Close. 7. Send the text file containing the certificate for signing as a certificate compatible with Base-64 ASCII code. Select Web Server as the certificate template when submitting a certificate request. Important: We recommend using a common CA for the Equinox Management and the gateway certificates for a more efficient implementation. 8. After receiving the signed certificate together with the CA's root certificate, save the CA root certificate as the gateway s root certificate file. 9. Access the Equinox Management administrator portal again. 10. Select Devices > Devices by Type > Gateways and navigate to the gateway to upload its certificates. 11. Select the Certificate tab. 12. Select Upload a Certificate to upload the certificate for the gateway which has been signed by the CA. The Upload Certificate window opens. 13. Paste the content of the gateway certificate signed by the CA and select OK. The CA signed certificate is uploaded. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 121

122 Configuring Your Scopia Video Gateway Deployment Figure 73: Uploading a signed certificate 14. Select Upload under the CA root section of the window to upload the CA s root certificate. The upload certificate window opens. 15. Paste the content of the CA root certificate and select OK. The CA root certificate is uploaded. 16. In cases where the CA root certificate is signed by another CA, you also need to upload the root of the second CA to verify it is trusted. Select Upload under the CA intermediate section of the window to upload the intermediate s root certificate. 17. Paste the content of the intermediate CA s root certificate and select OK. The intermediate CA s root certificate is uploaded. 18. Restart the gateway. 19. If the gateway certificate is signed by a different CA than Equinox Management s certificate, upload the root and intermediate certificates of the CA that signed the gateway's certificate into Equinox Management as described in the Administrator Guide for Equinox Management. 20. If the device certificates are signed by the same CA as Equinox Management s certificate, enable TLS encryption on Equinox Management as described in the Administrator Guide for Equinox Management. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 122

123 Securing Your Video Network Using TLS Securing Your Video Network Using TLS on page 109 Enabling Encryption on Scopia Video Gateway About this task Encrypting communications in the gateway is done at each leg of the gateway.broken xref. See XML comment in source file. Important: Using encryption is subject to local regulation. In some countries it is restricted or limited for usage. For more information, consult your local reseller. Figure 74: Encryption in Equinox Management For the leg communicating with the Lync/OCS network, the gateway provides media encryption using the S-RTP standard. For the leg communicating with the H.323 network, the gateway provides media encryption using the H.235 standard. For the leg communicating with Equinox Management, the gateway can provides TLS for secure XML over TCP communications. Important: Encrypting communications between the gateway and Equinox Management is typically less common since they are usually both located behind the firewall inside an enterprise. This section details how to encrypt communications between the Gateway and the video network. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 123

124 Configuring Your Scopia Video Gateway Deployment To encrypt control and management communications between Equinox Management and the SIP and H.323 networks, see Enabling the TLS Connection in Equinox Management on page 66 Before you begin Make sure that certificates authenticating the gateway are installed on it as described in Generating and Uploading Certificates for the Scopia Video Gateway on page 118. If the CA that signed the gateway's certificates is different from the CA that signed the certificate for Equinox Management, upload the gateway's CA root and intermediate certificate onto the Equinox Management as described in the Administrator Guide for Equinox Management. Procedure 1. Access the Equinox Management administrator portal. 2. Select Devices > Devices by Type > Gateways. 3. Select the gateway you require. 4. Select the Configuration tab. Figure 75: Enabling encryption on the gateway 5. For encrypting communications between the gateway and the H.323 network, especially the MCU, proceed as follows: a. Select Advanced Parameter. The Advanced Parameters dialog box appears (seebroken xref. See XML comment in source file.). January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 124

125 Securing Your Video Network Using TLS Figure 76: Enabling H.235 call support b. Type h235callssupport in the Command ID field. c. Clean the Value field. d. Select Get. Equinox Management automatically sets the port's value to 1 in the Value field. e. Select Save. f. Select Close 6. To encrypt communications with Equinox Management: a. Select Secure XML connection using TLS. b. Make sure that TLS encryption is enabled on Equinox Management as described in Administrator Guide for Equinox Management Securing Your Video Network Using TLS on page 109 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 125

126 Chapter 5: Performing Maintenance Procedures This section details to the ongoing administrator tasks required to maintain your video network: Upgrading the Software File of a Video Device on page 126 Restoring the Previous Software Version of a Network Device on page 129 Downgrading your Scopia Video Gateway on page 130 Changing the IP Address of your Gateway on page 131 Upgrading the Software File of a Video Device About this task You can quickly and easily perform remote software upgrades of video devices from Avaya Equinox Management by uploading an upgrade file and applying it to the device. Important: Perform the upgrade remotely using the Equinox Management. You cannot upgrade the firmware of the gateway directly on the device. Depending on your support contract, you can upgrade to: The next major version. Upgrading a major version requires a new license. This kind of upgrade changes one of the first two digits in a version number. For example, upgrading from version 8.0 to version 8.1 requires a new license. An incremental version. Upgrading an incremental version does not require a new license. This kind of upgrade changes the third, fourth and fifth digits in the version number. For example, upgrading from to or to does not require a new license. Upgrades may require first applying the major upgrade and then the incremental upgrade within that major version. For example, to upgrade from to , first apply the major upgrade to , and then the incremental upgrade to January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 126

127 Upgrading the Software File of a Video Device Before you begin Before upgrading your video network devices, including endpoints, do the following: Before upgrading a video device software, back up its configuration by retrieving its configuration file. For more information on remote backups, see Administrator Guide for Equinox Management. Go to to apply for and download your upgrade package. If you upgrade to a major version, ensure you have a new license key. The upgrade procedure is different when upgrading to a major new version compared with smaller incremental upgrades. See Administrator Guide for Equinox Management for details. Navigate to the device and select the Access tab. Enter a name and password for automatic login to the video device during the upgrade process. We recommend using the same name across the deployment. Procedure 1. Access the Avaya Equinox Management administrator portal. 2. Select the tab. 3. Locate the video device as explained in the Administrator Guide for Equinox Management. 4. Select the check box of the device to be upgraded. 5. Select Manage > Upgrade Software. Figure 77: Upgrading the software file of a device 6. At the prompt, select OK to shut down the video device for a few minutes. This disconnects all active calls, and the first page of the Upgrade Software Wizard appears. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 127

128 Performing Maintenance Procedures Figure 78: Upgrade Software Wizard Page 1 7. Either select one of the current upgrade files to upgrade, or select I want to upload a new upgrade file and select the Next button. The second page of the wizard appears. Figure 79: Upgrade Software Wizard Page 2 8. Select the search icon to search for the package you want to upload. The package displays in the File Name field. 9. In the Save As field, enter a name by which you want to save the package, and optionally, add a description in the Description field. 10. Select Next to save the upgrade file and its information in Equinox Management. 11. If required, enter license keys. 12. Select Apply. The system notifies that the video device shuts down for several minutes, causing all the active calls to be disconnected. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 128

129 Restoring the Previous Software Version of a Network Device If using Application Server P/N , make sure to remove upgrade packages on a regular basis to ensure that there is enough disk space. Performing Maintenance Procedures on page 126 Restoring the Previous Software Version of a Network Device About this task This section explains how to restore a previous software version after you upgrade your network device. You can restore the same software version only once. The following network devices can be restored: Scopia Elite 6000 MCU Conferencing SIP Gateway Scopia Video Gateway Only the most recent version of the device s software can be restored. During this procedure, the network device shuts down for a few minutes, causing all active calls to be disconnected. The following parameters are not backed up and cannot be restored: IP address Scopia Video Gateway IP mask Default router IP address MTU size - the size of the packets received from the gateway DNS suffix DNS primary address DNS secondary address Procedure 1. Access the Equinox Management administrator portal. 2. Search for an online network device. 3. Select Devices > Devices by Type > Gateways. 4. Select the network device whose software version you want to restore. 5. Select Manage > Restore Previous Version. The system informs you that all active calls on the device will be disconnected when you begin the process. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 129

130 Performing Maintenance Procedures 6. Select Yes in the confirmation message. Figure 80: Restore Previous Version Warning Message The Update Log window opens, showing the task progress (Figure 81: Progress of restoring a software package on page 130). Performing Maintenance Procedures on page 126 Figure 81: Progress of restoring a software package Downgrading your Scopia Video Gateway If necessary, you can downgrade your network device in one of the following ways: To downgrade one version back after you upgraded your network device, perform the procedure in Restoring the Previous Software Version of a Network Device on page 129. To downgrade to a version earlier than the previous version, see Upgrading the Software File of a Video Device on page 126. Performing Maintenance Procedures on page 126 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 130

131 Changing the IP Address of your Gateway Changing the IP Address of your Gateway About this task You may need to change the IP address of your gateway when it is transferred to a different subnet of your network. Perform the procedure described in Configuring the IP addresses on page 30. Performing Maintenance Procedures on page 126 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 131

132 Chapter 6: Troubleshooting Your Scopia Video Gateway Deployment This section covers troubleshooting problems that may occur when setting up and operating the Scopia Video Gateway. All Endpoints Appear Offline on page 132 Resolving Room System Availability on page 134 Resolving Lync Client Connectivity in TCP Environment on page 135 Resolving Lync Client Connectivity in TLS Environment on page 136 Retrieving Scopia Video Gateway Logs on page 137 Resolving a TCP Connectivity Issue with Lync Server 2010 Hosting Pack on page 138 Resolving a Copy and Paste Issue in Avaya Equinox Management on page 139 Renewing an Expired Certificate in the Scopia Video Gateway on page 140 All Endpoints Appear Offline Problem All H.323 endpoints appear offline in the Lync Video Chat Client. Offline All Scopia Video Gateways used in your deployment are offline. Solution 1. Access the Equinox Management administrator portal. 2. Select Devices > Gateways. 3. Check that the status of all Scopia Video Gateways is Online. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 132

133 All Endpoints Appear Offline Figure 82: Online status of gateways LDAP server not synchronized The LDAP server containing endpoint information is not synchronized with Equinox Management. Solution 1. Access the Equinox Management administrator portal. 2. Select Settings > LDAP Servers. 3. Select Synchronize All. Equinox Management synchronizes with the Microsoft Active Directory. As a result, the endpoint statuses are updated. Figure 83: Synchronizing LDAP servers 4. Also check the endpoint status of each offline endpoint in the Lync Client. No Equinox Management service The Equinox Management service fails or is unavailable. Solution 1. On the Equinox Management Server, select Start > Administrative Tools > Services. 2. Verify the Avaya Equinox Management service is active. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 133

134 Troubleshooting Your Scopia Video Gateway Deployment Cause The status of the AvayaEquinox Management watchdog service is not important. 3. Verify the Avaya H.323 Gatekeeper services are active. 4. If the problem persists, restart the Equinox Management Server. The endpoint is defined but did not register successfully in the H.323 Gatekeeper. Troubleshooting Your Scopia Video Gateway Deployment on page 132 Resolving Room System Availability Problem In Equinox Management, a room system that is online appears to be unavailable or offline. Room system not in endpoint list The room system does not appear in the filtered endpoint list of Equinox Management. 1. Access the Equinox Management administrator portal. 2. Navigate to Settings > LDAP Servers. 3. Edit the Users Search Base by selecting Configure. Figure 84: Editing the Users Search Base Equinox Management 4. In the Ldap Tree list select the checkbox of the areas to ensure they include the missing endpoint. Equinox Management only lists endpoints from the selected search base. Room system not registered The room system is not registered with H.323 Gatekeeper. January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 134

135 Resolving Lync Client Connectivity in TCP Environment Solution To resolve, check the following: Check that the room system is registered with H.323 Gatekeeper. Alter the search criteria of the endpoints listed in the endpoint list in Equinox Management to include the missing endpoint. Troubleshooting Your Scopia Video Gateway Deployment on page 132 Resolving Lync Client Connectivity in TCP Environment Problem Call from Lync clients do not connect to H.323 room systems in TCP environment. Cause The Lync Server is set to use the TLS protocol while the rest of the environment is configured to use the TCP protocol. Solution Verify the Lync protocol setting and, if required, change the Lync Server settings so that it supports both the TCP and TLS connection. 1. Hold down the Ctrl key on your computer keyboard and right click on the Lync icon. 2. Select Configuration Information in the dropdown menu. If the PC to PC AV Encryption field is set to AV Encryption Supported, continue with 3 on page On the Lync Server, select the Start button. 4. Select Microsoft Lync Server 2010 > Lync Server Management Shell > Run as administrator. The Lync Server Management Shell window opens. 5. Enter this command: Get-CsMediaConfiguration 6. Check that the EncryptionLevel parameter is not set to EncryptionRequired. 7. If it is set to EncryptionRequired, change it by entering this command: Set-CsMediaConfiguration -EncryptionLevel SupportEncryption Troubleshooting Your Scopia Video Gateway Deployment on page 132 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 135

136 Troubleshooting Your Scopia Video Gateway Deployment Resolving Lync Client Connectivity in TLS Environment Problem Calls from Lync clients do not connect to H.323 room systems in a TLS environment. FQDN not configured as domain The Lync server FQDN must be configured to a domain name, not an IP address. Solution Verify that the Lync Server FQDN name is configured to a domain name. For more information, see Adding a Lync, Skype for Business, in Equinox Management on page 83 Unstable connection The connection between a Lync client and the H.323 Gatekeeper has become unstable. Solution Make an H.323 point-to-point call between the Lync client and the H.323 Gatekeeper to verify H.323 Gatekeeper functioning. If this fails, troubleshoot the H.323 Gatekeeper. TLS problem The TLS environment was not successfully deployed. Solution 1. Access the Equinox Management administrator portal. 2. Select Logs & Events > Events > All. 3. The following error messages indicate an issue in TLS negotiation: ERROR - TLS - RvTLSSessionClientHandshake: session (0x8c35c58) general eerror ERROR - TLS - RvTLSSessionServerHandshake: session (0x8c35098) general error - SSL alert... [...B2BAPP] Proxy core obj=0x0e39f5f0, appobj=0x0e39f698 was created ERROR - TLS - RvTLSSessionClientHandshake: session (0x8c35c58) general eerror ERROR - TRANSPORT - TlsContinueHandshake - Connection 0x : Call to handshake failed side=1 closing connection, (rv=-512) 4. Troubleshoot by verifying that the certificates are properly applied at both the Scopia Video Gateway and Avaya Equinox Management. Troubleshooting Your Scopia Video Gateway Deployment on page 132 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 136

137 Retrieving Scopia Video Gateway Logs Retrieving Scopia Video Gateway Logs About this task When reporting a problem to customer support, you may be asked to retrieve and send logs of Scopia Video Gateway. Procedure 1. Access the Equinox Management administrator portal. 2. Select Devices > Gateways. 3. Select the check box of the Scopia Video Gateway. 4. Select Manage > Retrieve Customer Support Package. The logs are retrieved in form of a zip file. Figure 85: Retrieving support package 5. Send the zip file containing logs to the Avaya customer support. You can contact Avaya customer support from this web page: Troubleshooting Your Scopia Video Gateway Deployment on page 132 January 2017 Scopia Video Gateway for Microsoft Lync Lync Deployment Guide 137