User Guide for Avaya Scopia PathFinder Client

Transcription

1 User Guide for Avaya Scopia PathFinder Client Release For Solution 8.3 March 2016

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 by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya may generally make available to users of its products and Hosted Services. 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 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 a 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 IF YOU PURCHASE A 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. YOUR USE OF THE HOSTED SERVICE SHALL BE LIMITED BY THE NUMBER AND TYPE OF LICENSES PURCHASED UNDER YOUR CONTRACT FOR THE HOSTED SERVICE, PROVIDED, HOWEVER, THAT FOR CERTAIN HOSTED SERVICES IF APPLICABLE, YOU MAY HAVE THE OPPORTUNITY TO USE FLEX LICENSES, WHICH WILL BE INVOICED ACCORDING TO ACTUAL USAGE ABOVE THE CONTRACT LICENSE LEVEL. CONTACT AVAYA OR AVAYA S CHANNEL PARTNER FOR MORE INFORMATION ABOUT THE LICENSES FOR THE APPLICABLE HOSTED SERVICE, THE AVAILABILITY OF ANY FLEX LICENSES (IF APPLICABLE), PRICING AND BILLING INFORMATION, AND OTHER IMPORTANT INFORMATION REGARDING 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 types 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. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail

3 account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server or an Instance of the Software. Database License (DL). End User may install and use each copy or an Instance of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicates with no more than one Instance of the same database. CPU License (CP). End User may install and use each copy or Instance of the Software on a number of Servers up to the number indicated in the order provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya s prior consent and payment of an upgrade fee. Named User License (NU). You may: (i) install and use each copy or Instance of the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use each copy or Instance of the Software on a Server so long as only authorized Named Users access and use the Software. Named User, means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya s sole discretion, a Named User may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. 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 ). 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 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. 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. 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, 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 This Manual... 6 Related Documentation... 6 Feedback... 6 Chapter 2: Introducing PathFinder... 7 About the Avaya Scopia PathFinder Solution... 7 Scopia PathFinder Components... 8 Configuring Your Firewall to Work with Scopia PathFinder... 8 Enterprise Deployment... 9 Service Provider Deployment Role of the PathFinder server Role of the Scopia PathFinder client About Direct Media Connections Direct Media Connection Within an Enterprise Branch Direct Media Connection Between Enterprise Branches Key Benefits of the Scopia PathFinder Solution Features of the Scopia PathFinder Solution Chapter 3: System Requirements Software Environment Options Chapter 4: Installing the PathFinder Client Installing the Scopia PathFinder client On a Windows Platform Installing the Scopia PathFinder client On a Linux Platform Launching the Scopia PathFinder client Configuration Tool Upgrading Scopia PathFinder client Chapter 5: Configuring the PathFinder Client Configuring a Connection to a PathFinder server Configuring a Scopia PathFinder client Deployed On a WAN Configuring a Scopia PathFinder client Deployed On a LAN Configuring Additional PathFinder servers Configuring Gateway and MCU Details Defining Access Permission to the PathFinder server Authorizing Communication with the PathFinder server Via the Scopia PathFinder client Blocking Communication with the PathFinder server Via the Scopia PathFinder client Configuring Startup Preferences Enabling Guest Users to Access a Conference Enabling the Enterprise Gatekeeper to Route IP Calls Viewing Scopia PathFinder Version Information March 2016 User Guide for Avaya Scopia PathFinder Client 5

6 Chapter 1: About This Manual The Scopia PathFinder client User Guide describes how to install, configure and use the Scopia PathFinder client. Related links Related Documentation on page 6 Feedback on page 6 Related Documentation The PathFinder documentation set is available on the Avaya Utilities and Documentation CD-ROM supplied with the product and includes manuals and online helps. The manuals are in PDF format. Note: You require Adobe Reader version 6.0 or later to open the PDF files. You can download Acrobat Reader free of charge from Related links About This Manual on page 6 Feedback The team at Avaya constantly endeavors to provide accurate and informative documentation. If you have comments or suggestions regarding improvements to future publications, we would value your feedback. Please send your comments to infodev@avaya.com. We thank you for your contribution. Related links About This Manual on page 6 March 2016 User Guide for Avaya Scopia PathFinder Client 6

7 Chapter 2: Introducing PathFinder About the Avaya Scopia PathFinder Solution Enterprises and Service Providers that want to secure network data and devices while taking advantage of H.323 communications across LANs, WANs and the public Internet must inevitably address the issue of firewall and Network Address Translation (NAT) device traversal. Firewalls block unsolicited incoming communications from outside the local network. Most firewalls are not designed to allow video conferencing scenarios where everyone is allowed to connect to everyone. Network Address Translation (NAT) is an Internet standard that enables a local-area network (LAN) to use one set of IP addresses for internal traffic and a second set of addresses for external traffic. A NAT box located where the LAN meets the Internet makes all necessary IP address translations. The NAT hides the internal native IP address and thus prevents incoming video calls to the devices on the private network. The Avaya Scopia PathFinder solution maintains the security and advantages of firewall and NAT, requires no costly upgrade to the firewall or NAT for protocol awareness, handles both near-end (local) and far-end (remote destination) firewall traversal and is easy to implement and deploy. The Scopia PathFinder solution works with the Scopia PathFinder client and H.323 endpoints which support the ITU H and H standards to enable traversal of firewalls. The Scopia PathFinder client is necessary for the support of non-h.460 compliant endpoints. For firewall traversal, Scopia PathFinder supports a proprietary Avaya protocol and H /H The proprietary Avaya protocol has been supported since the first release of Scopia PathFinder and is used in conjunction with the Scopia PathFinder client for endpoints which do not support the H.460 standard, or in cases where the H.460 traversal does not work. H and H are ITU standards which define protocols for the firewall traversal of signaling and media, respectively. Note: Only H.460 traversal-enabled endpoints can register with a PathFinder server. All other endpoints must use the Scopia PathFinder client for registration requests. March 2016 User Guide for Avaya Scopia PathFinder Client 7

8 Introducing PathFinder Scopia PathFinder Components Scopia PathFinder contains two components PathFinder server and Scopia PathFinder client. Scopia PathFinder Server The core intelligent component of the solution. The Scopia PathFinder provides signaling and media processing for communications among private enterprise networks served by Scopia PathFinder clients. When a Scopia PathFinder client establishes an initial outbound connection with the PathFinder server through a specific port of the firewall (the default port is 3089), the PathFinder server can communicate with the Scopia PathFinder client through that particular port. Scopia PathFinder Client A light client application that is deployed at the different sites inside the protected network. Scopia PathFinder client can be installed on any standalone computer with a Windows operating system. Scopia PathFinder client supports non-h460 compliant endpoints. If all the deployed endpoints support the H.460 standard, there is no need for the Scopia PathFinder client. Configuring Your Firewall to Work with Scopia PathFinder Table 1: Firewall Port Configuration on page 8 describes the port configuration required to enable your firewall to work with Scopia PathFinder. For details, see the Reference Guide on Port Security for Avaya Scopia Solution. Table 1: Firewall Port Configuration Port Type Use 1719 UDP H RAS 1720 TCP IP Call Signaling/DPA Mode (Direct Public Access) 2776 TCP H Call Signaling 2776 UDP H Media (RTP) 2777 TCP H and H Call Control 2777 UDP H Media Control (RTCP) 3089 TCP/UDP Tunneling TCP/UDP H.323 Call Signaling/DPA Mode March 2016 User Guide for Avaya Scopia PathFinder Client 8

9 Enterprise Deployment Enterprise Deployment Figure 1: Scopia PathFinder Enterprise Deployment on page 9 shows how all cross-enterprise calls pass between a Scopia PathFinder client and the PathFinder server. Firewalls allow connections between the PathFinder server and each Scopia PathFinder client while still offering uncompromised network security. For information on configuring your firewall, see Configuring Your Firewall to Work with Scopia PathFinder on page 8. An H.460-compliant endpoint should register with the PathFinder server directly. If the H.460- compliant endpoint registers to a Scopia PathFinder client or the main site gatekeeper, endpoint H. 460 functionality is not used. Once the Scopia PathFinder system is running and operational, you can configure enterprise endpoints to register to a Scopia PathFinder client by setting the Scopia PathFinder client IP address as the endpoint gatekeeper. For more information on endpoint registration, consult your endpoint model documentation. Figure 1: Scopia PathFinder Enterprise Deployment March 2016 User Guide for Avaya Scopia PathFinder Client 9

10 Introducing PathFinder Service Provider Deployment Figure 2: Scopia PathFinder Service Provider Deployment on page 10 shows how each enterprise can use its own gatekeeper or use the Service Provider gatekeeper. When working with an enterprise, you do not need to make any changes to your firewall configuration. When an enterprise utilizes a gatekeeper, there is no need to open ports for incoming traffic. Figure 2: Scopia PathFinder Service Provider Deployment For information on configuring your firewall, see Configuring Your Firewall to Work with Scopia PathFinder on page 8. Role of the PathFinder server The PathFinder server provides signaling and media processing for communications among private enterprise networks served by Scopia PathFinder clients. When a Scopia PathFinder client establishes an initial outbound connection with the PathFinder server through a specific port of the March 2016 User Guide for Avaya Scopia PathFinder Client 10

11 Role of the Scopia PathFinder client firewall (the default port is 3089), the PathFinder server can communicate with the Scopia PathFinder client through that particular port. The PathFinder server has in-depth knowledge of the communication protocols used by the system and is able to modify protocols and substitute the initiator s address with its own address, so that it acts as the call initiator to the receiving end. This eliminates the need to publish internal native enterprise IP addresses. Role of the Scopia PathFinder client The Scopia PathFinder client acts as the sole proxy through which internal devices behind an enterprise firewall communicate with external devices. Figure 3: Scopia PathFinder client Remote Site Deployment on page 11 shows a deployment of the Scopia PathFinder client at a remote enterprise site behind the corporate firewall. Figure 3: Scopia PathFinder client Remote Site Deployment March 2016 User Guide for Avaya Scopia PathFinder Client 11

12 Introducing PathFinder About Direct Media Connections Direct media connection enables a direct media flow between endpoints without passing the PathFinder server located at the main site. Direct media connection is supported both within an enterprise branch and between enterprise branches. Related links Direct Media Connection Within an Enterprise Branch on page 12 Direct Media Connection Between Enterprise Branches on page 13 Direct Media Connection Within an Enterprise Branch In this scenario, several Scopia PathFinder clients are deployed at the same enterprise branch. In calls between endpoints located at the same branch (but registered to different Scopia PathFinder clients), the media goes directly between the endpoints without passing through the PathFinder server located at the main site. March 2016 User Guide for Avaya Scopia PathFinder Client 12

13 About Direct Media Connections Figure 4: Direct Media Connection Within an Enterprise Branch In Figure 4: Direct Media Connection Within an Enterprise Branch on page 13, Scopia PathFinder clients A and B are deployed at the remote branch. In a call between the H.323 endpoints (registered to each client), the media goes directly between the endpoints without going through the PathFinder server at the main site. Support for this scenario is automatic and requires no special settings on the PathFinder server. Related links About Direct Media Connections on page 12 Direct Media Connection Between Enterprise Branches In this scenario, Scopia PathFinder clients are deployed at different branch sites. The sites are linked via a direct Multi Protocol Label Switching (MPLS) connection. When there is a call between the sites, the media is routed directly between the sites without passing through the PathFinder server located at the main site. March 2016 User Guide for Avaya Scopia PathFinder Client 13

14 Introducing PathFinder Figure 5: Direct Media Connection Between Enterprises In Figure 5: Direct Media Connection Between Enterprises on page 14, there is an MPLS connection between the London and New York branch offices. In a call between H.323 endpoints (registered to each client at the respective office), the media goes directly between the endpoints without going through the PathFinder server at the main site. To use this scenario, you need to configure a topology island on the PathFinder server. For information on configuring topology islands, contact Customer Support. Related links About Direct Media Connections on page 12 Key Benefits of the Scopia PathFinder Solution The key benefits of the Scopia PathFinder solution include: Handles firewall and NAT problems without device upgrades or security compromises. March 2016 User Guide for Avaya Scopia PathFinder Client 14

15 Features of the Scopia PathFinder Solution Tunnels and transparently traverses firewalls and NAT devices, preserving security advantages. No costly upgrade to firewalls or NAT devices for protocol awareness. No publishing of enterprise IP addresses. Both near-end (local) and far-end (remote destination) firewall traversal. Thin Scopia PathFinder client requires no knowledge of underlying communication protocols. Scopia PathFinder client requires no upgrade to support additional protocols. Scopia PathFinder client uses only one TCP or UDP port to connect to the PathFinder server. Suitable for service providers and enterprises. Simplified Enterprise Gatekeeper configuration. Easy to implement and deploy. Features of the Scopia PathFinder Solution The key features of the Scopia PathFinder solution include: Enhanced Management capabilities Avaya Scopia Management fully supports Scopia PathFinder, providing comprehensive maintenance tools such as user management, real-time monitoring, traps & alarms, automated log collection, and direct web access. Integrated web-based event log for quick and effective troubleshooting. Native Windows 2008 Server support Scopia PathFinder client installer supports Windows 2008 Server. Linux support. H.235 support (encryption only). Traffic separation The ability to separate Management and Media IP traffic, and to comply with the strict security requirements of Service Providers. Status Check Scopia PathFinder client checks the status of the connection to the PathFinder server. Endpoint Calling Support for calling endpoints far away from the Scopia PathFinder client. Default extension for guest endpoint dialing into a private network. Scopia PathFinder client can run on Microsoft Windows Vista Business (Service Pack 1), Microsoft Windows Vista Ultimate (Service Pack 1), and Windows 2008 Server. Concurrent Calls Up to 100 2M concurrent calls. Registered Devices Up to 600 registered devices. TCP or UDP For media traversal. Web Server Timeout Configurable web server timeout. March 2016 User Guide for Avaya Scopia PathFinder Client 15

16 Introducing PathFinder Avaya Scopia ECS Gatekeeper Integration The Scopia PathFinder client can be installed on the same machine as the ECS. Local Gatekeeper Enterprise gatekeeper support allows deploying a local gatekeeper at the remote site. Interoperability Based on the H.323 standard, Scopia PathFinder provides a high degree of interoperability with other H.323-compliant gateways, gatekeepers, terminals and MCU products. Interoperability with the ECS supports calling external endpoints by dialing to an IP address from Enterprise Gatekeeper-registered endpoints. Aliases H.460 endpoint aliases are displayed as Client Name under Client Status > Connected Clients. Web-based Management All aspects of the PathFinder server configuration can be viewed and modified from a remote location using a standard web browser. T.120 Data Collaboration Scopia PathFinder supports data transfers in calls, for legacy endpoints which are registered through the Scopia PathFinder client, using the T.120 standard. There is no support for H.460 endpoints. H.239 Support Scopia PathFinder supports H.239. H and H Support Standard firewall/nat traversal support. Quality Of Service (QoS) Configurable coding of media packets to achieve QoS routing priority on the IP network. The TOS bits of the IP datagram header can be configured for priority level. Dial Plan Scopia PathFinder provides full dial plan support. Direct Media Connection Ensures that media is routed directly between clients when possible. Access Control Access to the Scopia PathFinder user interface is password controlled. Authentication The PathFinder server runs on a hardened Linux Operating System (Avaya customized kernel). The Scopia PathFinder client must be authenticated to connect the server. Security Solution The Scopia PathFinder client contains an access control list (ACL) for the administrator to define which devices are accessible via the client. Role Based User Management Enables the allocation of suggested roles and default rights profiles. AES Encryption Scopia PathFinder supports encryption for all client-server traffic for call privacy. This includes signaling and media encryption. Scalable Solution With one client serving many endpoints, Scopia PathFinder servers can be neighbored. Clients hunt backup servers if a primary server is unavailable. Neighboring Server The PathFinder server can be neighbored, thereby supporting large enterprises or firewall/nat traversal between organizations. URI Dialing Enables endpoints registered with different gatekeepers or PathFinder servers to easily call each other. Without URI dialing, all systems must be neighbored to each other. March 2016 User Guide for Avaya Scopia PathFinder Client 16

17 Features of the Scopia PathFinder Solution Failover mechanism (Client Redundancy) Activated upon system failures (Windows). March 2016 User Guide for Avaya Scopia PathFinder Client 17

18 Chapter 3: System Requirements Software Environment Options Microsoft Windows 2000 Professional Microsoft Windows 2000 Server Microsoft Windows 2003 Server Microsoft Windows 2008 Server Microsoft Windows XP Microsoft Windows Vista Business (Service Pack 1) Microsoft Windows Vista Ultimate (Service Pack 1) Microsoft Windows 7 Note: On some Windows 7 64-bit systems, the Scopia PathFinder client must be installed as an application and cannot be installed as a service. Trustix 3.0 Linux RedHat 9.0 desktop version Linux Redhat Enterprise ES release 4 March 2016 User Guide for Avaya Scopia PathFinder Client 18

19 Chapter 4: Installing the PathFinder Client Installing the Scopia PathFinder client On a Windows Platform About this task You install the Scopia PathFinder client by running the Scopia PathFinder client installation wizard. Procedure 1. Locate and double click the PathFinder_Client_8_w_x_y_z.exe file (where 8_w_x_y_z represents the version number). The Introduction page displays. Note: If you try to install the Scopia PathFinder client on an operating system it does not support, an error message displays. 2. Select Next. The License Agreement displays. 3. Select I accept the terms of the license agreement. 4. Select Next. The Choose Install Folder page displays. 5. Select the location where you want to install an instance of the Scopia PathFinder client: To keep the default setting, select Next. To assign a different location, select Choose to browse for a location, then select Next. The Install PathFinder Client as a Windows Service page displays. 6. Select Install PathFinder Client as a Windows Service to automatically run the Scopia PathFinder client on Windows startup. 7. Select Next. If you perform installation on Windows 2003 operating system, the Windows Clustering page displays. Select Support Clustering to support Scopia PathFinder client redundancy on a Windows server cluster setup. March 2016 User Guide for Avaya Scopia PathFinder Client 19

20 Installing the PathFinder Client 8. Select Next. The Pre-Installation Summary page displays. 9. Review the information and confirm disk space availability. If you wish to change any of the information displayed, select Previous to return to the required installation page. Otherwise, select Install to start the installation process. When installation is complete, the Install Complete page displays. 10. Select Done to exit the installation wizard. Installing the Scopia PathFinder client On a Linux Platform About this task Avaya recommends using Red Hat 9.0 for installation on a Linux platform. Procedure 1. Copy the Linux PathFinder client pfc-8.0.w.x.y.z-rv.i586.rpm installer file from the Avaya Utilities and Documentation CD-ROM supplied with the product to a folder on your computer. 2. Log in as the root user of the Linux computer. 3. Execute rpm -i pfc-8.0.w.x.y.z.-rv.i586.rpm in the folder from which you copied the installer. The client installs. Instructions of where and how to configure the client and the configuration file name appear. Note: Configuration files contain detailed descriptions for all items. You can refer to these descriptions for Linux client configuration. You can configure the Linux client only by manually editing these files. Launching the Scopia PathFinder client Configuration Tool About this task For information about configuring the Scopia PathFinder client, see Configuring a Connection to a PathFinder server on page 22. Procedure Click Start > All Programs > Scopia PathFinder client > PathFinder Client. March 2016 User Guide for Avaya Scopia PathFinder Client 20

21 Upgrading Scopia PathFinder client The Scopia PathFinder client Configuration Tool starts and the Connection tab displays. Upgrading Scopia PathFinder client You upgrade a Scopia PathFinder client by installing the new version. During Scopia PathFinder client upgrade, you can install the newer version of the client only at the same location where the previous version was installed. If the old client is running during the upgrade, the Scopia PathFinder client installation wizard prompts you to reboot. March 2016 User Guide for Avaya Scopia PathFinder Client 21

22 Chapter 5: Configuring the PathFinder Client Configuring a Connection to a PathFinder server About this task You can configure a connection to a PathFinder server, to configure additional Scopia PathFinder Servers and to define the name and location of the Scopia PathFinder client. During configuration, you can define this client to be located in a private network in the following cases: If the Scopia PathFinder client is located at an enterprise remote branch Or If the enterprise video conferencing services are supplied by a service provider who owns the PathFinder server. In some cases, the Scopia PathFinder client can be located on the public internet to allow guest users or endpoints which are not part of the enterprise to connect to your video conferencing network. Before you begin Ensure you have the PathFinder server password provided by the PathFinder server administrator. Procedure 1. Select the Connection tab. 2. Enter the IP address of the default PathFinder server. The Scopia PathFinder client connects to the server s address you enter in this field. 3. Enter the port of the default PathFinder server. 4. Select Standby Servers to configure additional Scopia PathFinder servers. See Configuring Additional PathFinder Servers on page Enter the PathFinder server password for connecting the Scopia PathFinder client to the PathFinder server. 6. Enter a unique name to identify your Scopia PathFinder client. By default, this field includes the name of the computer on which the Scopia PathFinder client is installed. March 2016 User Guide for Avaya Scopia PathFinder Client 22

23 Configuring a Connection to a PathFinder server Note: The values in the Server Password and Client Name fields must match the values in the Password and Login ID fields defined for the corresponding Client User in the Users tab of the PathFinder server. If no Client User role is defined on the PathFinder server, the value in the Client Name field can be any string which is unique on the PathFinder server s connected clients list. In this case, the Server Password field must be empty. 7. Select the This client is located on private network check box if the Scopia PathFinder client is located in the enterprise LAN. Figure 6: Scopia PathFinder client Corporate LAN Deployment on page 23 displays a Scopia PathFinder client installed in the main enterprise LAN. Figure 6: Scopia PathFinder client Corporate LAN Deployment 8. Select Start Client to save all modified configuration data and to connect the Scopia PathFinder client to the PathFinder server. March 2016 User Guide for Avaya Scopia PathFinder Client 23

24 Configuring the PathFinder Client Configuring a Scopia PathFinder client Deployed On a WAN Procedure 1. Select the Connection tab. 2. Clear the This client is located on private network check box. The Enable extension dialing using this client s public IP address and Default extension options are available on the Advanced tab. Configuring a Scopia PathFinder client Deployed On a LAN Procedure 1. Select the Connection tab. 2. Select the This client is located on private network check box for clients which have to serve an Enterprise Gatekeeper on their site for dialing to external IP addresses. 3. Select the Advanced tab. 4. Verify that the Enable Enterprise Gatekeeper using this client to route IP calls and IP calls proxy port options are selected. The IP calls proxy port option has a range of ; the default port is Configuring Additional PathFinder servers About this task The Standby Servers option in the Connection tab enables you to configure up to three additional PathFinder servers on your network. If the default PathFinder server is unreachable, the Scopia PathFinder client attempts to connect to each of the PathFinder servers configured here until a connection is established with one of them. Procedure 1. Select the Connection tab. 2. Select Standby Servers. The Standby Servers dialog box opens. 3. Configure additional servers, as follows: a. Select the relevant check box. March 2016 User Guide for Avaya Scopia PathFinder Client 24

25 Configuring Gateway and MCU Details b. Enter the server IP address. c. Enter the server port number. d. Select OK. 4. Select Start Client to connect the Scopia PathFinder client to the PathFinder server. Configuring Gateway and MCU Details About this task This procedure describes how to configure a new Gateway or MCU for the Scopia PathFinder client. Procedure 1. Select the Devices tab. 2. Select Add. The Rich Media Device dialog box opens. 3. Enter the IP address of the Gateway or MCU. 4. Enter a description of the device. 5. Select OK. The new network device displays in the Devices tab. 6. Select Start Client to connect the Scopia PathFinder client to the PathFinder server. Defining Access Permission to the PathFinder server You can add another level of security to a conferencing system by specifying which IP addresses are and are not authorized to communicate with the PathFinder server via the Scopia PathFinder client. Related links Authorizing Communication with the PathFinder server Via the Scopia PathFinder client on page 26 Blocking Communication with the PathFinder server Via the Scopia PathFinder client on page 27 March 2016 User Guide for Avaya Scopia PathFinder Client 25

26 Configuring the PathFinder Client Authorizing Communication with the PathFinder server Via the Scopia PathFinder client Before you begin Before you define the IP addresses authorized to communicate with the PathFinder server via the Scopia PathFinder client, note the following: Select All registered devices to allow all network devices listed in the Devices tab and all other H.323 endpoints which use this Scopia PathFinder client as their gatekeeper to communicate with the PathFinder server via the Scopia PathFinder client. For more information about the Devices tab, see Configuring Gateway and MCU Details on page 25. There are scenarios in which a local gatekeeper is required at a remote branch. In such cases, the gatekeeper deployed at the remote site manages the endpoints at the remote site, while the Scopia PathFinder client is used for out-of-zone calls (incoming or outgoing calls) only, as shown in Figure 7: Local Gatekeeper at a Remote Branch on page 26. Figure 7: Local Gatekeeper at a Remote Branch In these cases, you must add the IP address of the enterprise gatekeeper and all endpoints to the Allow list. If you do not, the media to the endpoints registered to the enterprise gatekeeper is discarded by the Scopia PathFinder client and it may not be possible to establish calls from the PathFinder server to the enterprise gatekeeper. When the MCU works with a media processing card (such as the MVP), you must add the IP address of the media processing card to the Allow list. March 2016 User Guide for Avaya Scopia PathFinder Client 26

27 Defining Access Permission to the PathFinder server Procedure 1. Select the Security tab. 2. Select Add in the Allow area. The Security Group dialog box opens. 3. To define a single device: a. Select Single IP. b. Enter the IP address of the device. 4. To define a range of IP addresses: a. Select From. b. Enter the IP address which opens the range. c. Enter the IP address which closes the range. 5. Select OK. The defined IP addresses are displayed in the Allow area of the Security tab. 6. Select Start Client to connect the Scopia PathFinder client to the PathFinder server. Related links Defining Access Permission to the PathFinder server on page 25 Blocking Communication with the PathFinder server Via the Scopia PathFinder client About this task You can specify IP addresses which are not authorized to communicate with the PathFinder server via the Scopia PathFinder client. Procedure 1. Select the Security tab. 2. Select Add in the Deny area. The Security Group dialog box opens. 3. To define a single device: a. Select Single IP. b. Enter the IP address of the device. 4. To define a range of IP addresses: a. Select From. b. Enter the IP address which opens the range. c. Enter the IP address which closes the range. March 2016 User Guide for Avaya Scopia PathFinder Client 27

28 Configuring the PathFinder Client 5. Select OK. The defined IP addresses are displayed in the Deny area of the Security tab. 6. Select Start Client to connect the Scopia PathFinder client to the PathFinder server. Related links Defining Access Permission to the PathFinder server on page 25 Configuring Startup Preferences About this task The procedure in this section describes how to configure the basic behavior of the Scopia PathFinder client after startup or reboot. You can configure the following options: Auto start on Windows logon The Scopia PathFinder client starts automatically the first time a user logs on to Windows after system reboot. This option is disabled when the Scopia PathFinder client is installed as a Windows service; it is enabled when the Client is installed as an application or as a Support Clustering service. Connect to server on startup The Scopia PathFinder client connects to its PathFinder server automatically at startup. If the client is installed as Support Clustering and is running on the inactive host of the Cluster, the Windows Cluster disables this option automatically. Minimize after connecting to server The Scopia PathFinder client runs in the system tray once it connects to its PathFinder server. Language Scopia PathFinder changes its user interface to the specified language after restart. Procedure 1. Select the Preferences tab. 2. Select the check boxes to configure options as required. 3. Select the language from the list. 4. Select Start Client to connect the Scopia PathFinder client to the PathFinder server. Note: When the client is installed as Support Clustering, the Start Client button is disabled. The service should be started only by Windows Cluster. Enabling Guest Users to Access a Conference A guest user is a user with a terminal which is not registered to the organization gatekeeper. You can configure the Scopia PathFinder client so that when a guest user dials in, there is a default March 2016 User Guide for Avaya Scopia PathFinder Client 28

29 Enabling Guest Users to Access a Conference extension to which they are routed when no extension is specified. This option is available only when the Scopia PathFinder client is located on a public network. Procedure 1. On the PathFinder Client Configuration page, ensure that the Connection tab is selected. 2. Clear the This client is located on private network checkbox. 3. On the Advanced tab: Figure 8: PathFinder Client Configuration Connection Tab a. Select the Enable extension dialing using this client's public IP address checkbox. b. In the Default Extension field, specify the default extension to which guest users are routed when dialing into a conference. The default extension is typically set to the Scopia Management VIVR. March 2016 User Guide for Avaya Scopia PathFinder Client 29

30 Configuring the PathFinder Client Figure 9: PathFinder Client Configuration Advanced Tab Scopia PathFinder redirects the call to the default extension when the user dials the IP address of the public Scopia PathFinder client without an extension. The endpoint does not need to have its own gatekeeper, or to use this client as its gatekeeper. Note: By default, the public Scopia PathFinder client denies all incoming calls. To accept all incoming calls by default, add an entry to the Allow list in the Security tab. For details, see Defining Access Permission to the PathFinder server on page 25. Enabling the Enterprise Gatekeeper to Route IP Calls You can invoke the Scopia PathFinder solution to ensure firewall and NAT traversal when using an enterprise gatekeeper. This option is available only when the client is located on the private network. Procedure 1. On the PathFinder Client Configuration page, ensure that the Connection tab is selected. 2. Select the This client is located on private network checkbox. March 2016 User Guide for Avaya Scopia PathFinder Client 30

31 Enabling the Enterprise Gatekeeper to Route IP Calls 3. On the Advanced tab: Figure 10: PathFinder Client Configuration Connection Tab a. Select the Enable Enterprise Gatekeeper using this client to route IP calls checkbox. b. In the IP calls proxy port field, enter the value of the Route IP Calls to field on the ECS that is used as the Enterprise Gatekeeper for this client. Figure 11: PathFinder Client Configuration Advanced Tab When dialing an external IP address from Enterprise Gatekeeper-registered endpoints, you must configure the relevant entities which can make calls via Scopia PathFinder. Select the March 2016 User Guide for Avaya Scopia PathFinder Client 31

32 Configuring the PathFinder Client Security tab and in the Allow section, click Add to add the permitted IP addresses, or select the All registered devices checkbox to enable all registered devices. Figure 12: PathFinder Client Configuration Security Tab For details on the Security tab, see Authorizing Communication with the PathFinder server Via the Scopia PathFinder client on page 26. Viewing Scopia PathFinder Version Information The About tab displays information about the version of the Scopia PathFinder client currently in use. March 2016 User Guide for Avaya Scopia PathFinder Client 32