User Guide for Avaya Scopia® PathFinder Client

User Guide for Avaya Scopia® PathFinderClient

Release 8.3.3For Solution 8.3

March 2016

© 2015-2016, Avaya, Inc.All Rights Reserved.

NoticeWhile reasonable efforts have been made to ensure that theinformation in this document is complete and accurate at the time ofprinting, Avaya assumes no liability for any errors. Avaya reservesthe right to make changes and corrections to the information in thisdocument without the obligation to notify any person or organizationof such changes.

Documentation disclaimer“Documentation” means information published by Avaya in varyingmediums which may include product information, operatinginstructions and performance specifications that Avaya may generallymake available to users of its products and Hosted Services.Documentation does not include marketing materials. Avaya shall notbe responsible for any modifications, additions, or deletions to theoriginal published version of documentation unless suchmodifications, additions, or deletions were performed by Avaya. EndUser agrees to indemnify and hold harmless Avaya, Avaya's agents,servants and employees against all claims, lawsuits, demands andjudgments arising out of, or in connection with, subsequentmodifications, additions or deletions to this documentation, to theextent made by End User.

Link disclaimerAvaya is not responsible for the contents or reliability of any linkedwebsites referenced within this site or documentation provided byAvaya. Avaya is not responsible for the accuracy of any information,statement or content provided on these sites and does notnecessarily endorse the products, services, or information describedor offered within them. Avaya does not guarantee that these links willwork all the time and has no control over the availability of the linkedpages.

WarrantyAvaya provides a limited warranty on Avaya hardware and software.Refer to your sales agreement to establish the terms of the limitedwarranty. In addition, Avaya’s standard warranty language, as well asinformation regarding support for this product while under warranty isavailable to Avaya customers and other parties through the AvayaSupport website: https://support.avaya.com/helpcenter/getGenericDetails?detailId=C20091120112456651010 under the link“Warranty & Product Lifecycle” or such successor site as designatedby Avaya. Please note that if You acquired the product(s) from anauthorized Avaya Channel Partner outside of the United States andCanada, the warranty is provided to You by said Avaya ChannelPartner and not by Avaya.

“Hosted Service” means a hosted service subscription that Youacquire from either Avaya or an authorized Avaya Channel Partner(as applicable) and which is described further in Hosted SAS or otherservice description documentation regarding the applicable hostedservice. If You purchase a Hosted Service subscription, the foregoinglimited warranty may not apply but You may be entitled to supportservices in connection with the Hosted Service as described furtherin your service description documents for the applicable HostedService. Contact Avaya or Avaya Channel Partner (as applicable) formore information.

Hosted ServiceTHE FOLLOWING APPLIES IF YOU PURCHASE A HOSTEDSERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYACHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USEFOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYAWEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFOUNDER THE LINK “Avaya Terms of Use for Hosted Services” ORSUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND AREAPPLICABLE TO ANYONE WHO ACCESSES OR USES THEHOSTED SERVICE. BY ACCESSING OR USING THE HOSTEDSERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ONBEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU AREDOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLYAS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IFYOU ARE ACCEPTING THE TERMS OF USE ON BEHALF ACOMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THATYOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE

TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, ORIF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOUMUST NOT ACCESS OR USE THE HOSTED SERVICE ORAUTHORIZE ANYONE TO ACCESS OR USE THE HOSTEDSERVICE. YOUR USE OF THE HOSTED SERVICE SHALL BELIMITED BY THE NUMBER AND TYPE OF LICENSESPURCHASED UNDER YOUR CONTRACT FOR THE HOSTEDSERVICE, PROVIDED, HOWEVER, THAT FOR CERTAIN HOSTEDSERVICES IF APPLICABLE, YOU MAY HAVE THE OPPORTUNITYTO USE FLEX LICENSES, WHICH WILL BE INVOICEDACCORDING TO ACTUAL USAGE ABOVE THE CONTRACTLICENSE LEVEL. CONTACT AVAYA OR AVAYA’S CHANNELPARTNER FOR MORE INFORMATION ABOUT THE LICENSESFOR THE APPLICABLE HOSTED SERVICE, THE AVAILABILITYOF ANY FLEX LICENSES (IF APPLICABLE), PRICING ANDBILLING INFORMATION, AND OTHER IMPORTANTINFORMATION REGARDING THE HOSTED SERVICE.

LicensesTHE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYAWEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (AvayaProducts)” OR SUCH SUCCESSOR SITE AS DESIGNATED BYAVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASEDFROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYACHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIALAGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWAREWAS OBTAINED FROM ANYONE OTHER THAN AVAYA, ANAVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYARESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOUAND ANYONE ELSE USING OR SELLING THE SOFTWAREWITHOUT A LICENSE. BY INSTALLING, DOWNLOADING ORUSING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOMYOU ARE INSTALLING, DOWNLOADING OR USING THESOFTWARE (HEREINAFTER REFERRED TOINTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TOTHESE TERMS AND CONDITIONS AND CREATE A BINDINGCONTRACT BETWEEN YOU AND AVAYA INC. OR THEAPPLICABLE AVAYA AFFILIATE (“AVAYA”).

Avaya grants You a license within the scope of the license typesdescribed below, with the exception of Heritage Nortel Software, forwhich the scope of the license is detailed below. Where the orderdocumentation does not expressly identify a license type, theapplicable license will be a Designated System License. Theapplicable number of licenses and units of capacity for which thelicense is granted will be one (1), unless a different number oflicenses or units of capacity is specified in the documentation or othermaterials available to You. “Software” means computer programs inobject 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 versionsthereto. “Designated Processor” means a single stand-alonecomputing device. “Server” means a Designated Processor thathosts a software application to be accessed by multiple users.“Instance” means a single copy of the Software executing at aparticular time: (i) on one physical machine; or (ii) on one deployedsoftware virtual machine (“VM”) or similar deployment.

License typesDesignated System(s) License (DS). End User may install and useeach copy or an Instance of the Software only on a number ofDesignated Processors up to the number indicated in the order.Avaya may require the Designated Processor(s) to be identified inthe order by type, serial number, feature key, Instance, location orother specific designation, or to be provided by End User to Avayathrough electronic means established by Avaya specifically for thispurpose.

Concurrent User License (CU). End User may install and use theSoftware on multiple Designated Processors or one or more Servers,so long as only the licensed number of Units are accessing and usingthe Software at any given time. A “Unit” means the unit on whichAvaya, at its sole discretion, bases the pricing of its licenses and canbe, without limitation, an agent, port or user, an e-mail or voice mail

https://support.avaya.com/helpcenter/getGenericDetails?detailId=C20091120112456651010

https://support.avaya.com/helpcenter/getGenericDetails?detailId=C20091120112456651010

https://support.avaya.com/LicenseInfo

https://support.avaya.com/LicenseInfo

account in the name of a person or corporate function (e.g.,webmaster or helpdesk), or a directory entry in the administrativedatabase utilized by the Software that permits one user to interfacewith the Software. Units may be linked to a specific, identified Serveror an Instance of the Software.

Database License (DL). End User may install and use each copy oran Instance of the Software on one Server or on multiple Serversprovided that each of the Servers on which the Software is installedcommunicates with no more than one Instance of the samedatabase.

CPU License (CP). End User may install and use each copy orInstance of the Software on a number of Servers up to the numberindicated in the order provided that the performance capacity of theServer(s) does not exceed the performance capacity specified for theSoftware. End User may not re-install or operate the Software onServer(s) with a larger performance capacity without Avaya’s priorconsent and payment of an upgrade fee.

Named User License (NU). You may: (i) install and use each copy orInstance of the Software on a single Designated Processor or Serverper authorized Named User (defined below); or (ii) install and useeach copy or Instance of the Software on a Server so long as onlyauthorized Named Users access and use the Software. “NamedUser”, means a user or device that has been expressly authorized byAvaya 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 e-mail or voicemail account in the name of a person or corporate function, or adirectory entry in the administrative database utilized by the Softwarethat permits one user to interface with the Software.

Shrinkwrap License (SR). You may install and use the Software inaccordance with the terms and conditions of the applicable licenseagreements, such as “shrinkwrap” or “clickthrough” licenseaccompanying or applicable to the Software (“Shrinkwrap License”).

CopyrightExcept where expressly stated otherwise, no use should be made ofmaterials on this site, the Documentation, Software, Hosted Service,or hardware provided by Avaya. All content on this site, thedocumentation, Hosted Service, and the product provided by Avayaincluding the selection, arrangement and design of the content isowned either by Avaya or its licensors and is protected by copyrightand other intellectual property laws including the sui generis rightsrelating to the protection of databases. You may not modify, copy,reproduce, republish, upload, post, transmit or distribute in any wayany content, in whole or in part, including any code and softwareunless expressly authorized by Avaya. Unauthorized reproduction,transmission, dissemination, storage, and or use without the expresswritten consent of Avaya can be a criminal, as well as a civil offenseunder the applicable law.

VirtualizationThe following applies if the product is deployed on a virtual machine.Each product has its own ordering code and license types. Note thateach Instance of a product must be separately licensed and ordered.For example, if the end user customer or Avaya Channel Partnerwould like to install two Instances of the same type of products, thentwo products of that type must be ordered.

Third Party Components“Third Party Components” mean certain software programs orportions thereof included in the Software or Hosted Service maycontain software (including open source software) distributed underthird party agreements (“Third Party Components”), which containterms regarding the rights to use certain portions of the Software(“Third Party Terms”). As required, information regarding distributedLinux OS source code (for those products that have distributed LinuxOS source code) and identifying the copyright holders of the ThirdParty Components and the Third Party Terms that apply is availablein the products, Documentation or on Avaya’s website at: https://support.avaya.com/Copyright or such successor site as designatedby Avaya. The open source software license terms provided as ThirdParty Terms are consistent with the license rights granted in theseSoftware License Terms, and may contain additional rights benefitingYou, such as modification and distribution of the open sourcesoftware. The Third Party Terms shall take precedence over theseSoftware License Terms, solely with respect to the applicable Third

Party Components to the extent that these Software License Termsimpose greater restrictions on You than the applicable Third PartyTerms.

The following applies if the H.264 (AVC) codec is distributed with theproduct. THIS PRODUCT IS LICENSED UNDER THE AVC PATENTPORTFOLIO LICENSE FOR THE PERSONAL USE OF ACONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVEREMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITHTHE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVCVIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN APERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEOPROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE ISGRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEGLA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.

Service ProviderTHE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’SHOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCTOR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTSSUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICEPROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLYFROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNELPARTNER’S HOSTING OF AVAYA PRODUCTS MUST BEAUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTEDPRODUCTS USE OR EMBED CERTAIN THIRD PARTYSOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFTSOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER ISREQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLELICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’SEXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTYSUPPLIER.

Preventing Toll Fraud“Toll Fraud” is the unauthorized use of your telecommunicationssystem by an unauthorized party (for example, a person who is not acorporate employee, agent, subcontractor, or is not working on yourcompany's behalf). Be aware that there can be a risk of Toll Fraudassociated with your system and that, if Toll Fraud occurs, it canresult in substantial additional charges for your telecommunicationsservices.

Avaya Toll Fraud interventionIf You suspect that You are being victimized by Toll Fraud and Youneed technical assistance or support, call Technical Service CenterToll Fraud Intervention Hotline at +1-800-643-2353 for the UnitedStates and Canada. For additional support telephone numbers, seethe Avaya Support website: https://support.avaya.com or suchsuccessor site as designated by Avaya.

Downloading DocumentationFor the most current versions of Documentation, see the AvayaSupport website: https://support.avaya.com, or such successor siteas designated by Avaya.

Contact Avaya SupportSee the Avaya Support website: https://support.avaya.com forproduct or Hosted Service notices and articles, or to report a problemwith your Avaya product or Hosted Service. For a list of supporttelephone numbers and contact addresses, go to the Avaya Supportwebsite: https://support.avaya.com (or such successor site asdesignated by Avaya), scroll to the bottom of the page, and selectContact Avaya Support.

TrademarksThe trademarks, logos and service marks (“Marks”) displayed in thissite, the Documentation, Hosted Service(s), and product(s) providedby Avaya are the registered or unregistered Marks of Avaya, itsaffiliates, or other third parties. Users are not permitted to use suchMarks without prior written consent from Avaya or such third partywhich may own the Mark. Nothing contained in this site, theDocumentation, Hosted Service(s) and product(s) should beconstrued as granting, by implication, estoppel, or otherwise, anylicense or right in and to the Marks without the express writtenpermission of Avaya or the applicable third party.

Avaya is a registered trademark of Avaya Inc.

https://support.avaya.com/Copyright

https://support.avaya.com/Copyright

HTTP://WWW.MPEGLA.COM

https://support.avaya.com




All non-Avaya trademarks are the property of their respective owners.Linux® is the registered trademark of Linus Torvalds in the U.S. andother countries.

Contents

Chapter 1: About This Manual................................................................................................. 6Related Documentation........................................................................................................... 6Feedback............................................................................................................................... 6

Chapter 2: Introducing PathFinder.......................................................................................... 7About the Avaya Scopia® PathFinder Solution........................................................................... 7Scopia® PathFinder Components............................................................................................. 8Configuring Your Firewall to Work with Scopia® PathFinder........................................................ 8Enterprise Deployment............................................................................................................ 9Service Provider Deployment................................................................................................. 10Role of the PathFinder server................................................................................................. 10Role of the Scopia® PathFinder client..................................................................................... 11About Direct Media Connections............................................................................................. 12

Direct Media Connection Within an Enterprise Branch........................................................ 12Direct Media Connection Between Enterprise Branches..................................................... 13

Key Benefits of the Scopia® PathFinder Solution..................................................................... 14Features of the Scopia® PathFinder Solution........................................................................... 15

Chapter 3: System Requirements......................................................................................... 18Software Environment Options............................................................................................... 18

Chapter 4: Installing the PathFinder Client.......................................................................... 19Installing the Scopia® PathFinder client On a Windows Platform............................................... 19Installing the Scopia® PathFinder client On a Linux Platform..................................................... 20Launching the Scopia® PathFinder client Configuration Tool..................................................... 20Upgrading Scopia® PathFinder client...................................................................................... 21

Chapter 5: Configuring the PathFinder Client...................................................................... 22Configuring a Connection to a PathFinder server..................................................................... 22Configuring a Scopia® PathFinder client Deployed On a WAN.................................................. 24Configuring a Scopia® PathFinder client Deployed On a LAN................................................... 24Configuring Additional PathFinder servers............................................................................... 24Configuring Gateway and MCU Details................................................................................... 25Defining Access Permission to the PathFinder server............................................................... 25

Authorizing Communication with the PathFinder server Via the Scopia® PathFinder client.... 26Blocking Communication with the PathFinder server Via the Scopia® PathFinder client........ 27

Configuring Startup Preferences............................................................................................. 28Enabling Guest Users to Access a Conference........................................................................ 28Enabling the Enterprise Gatekeeper to Route IP Calls.............................................................. 30Viewing Scopia® PathFinder Version Information..................................................................... 32

March 2016 User Guide for Avaya Scopia® PathFinder Client 5Comments on this document? [email protected]

mailto:[email protected]?subject=User Guide for Avaya Scopia® PathFinder Client

Chapter 1: About This Manual

The Scopia® PathFinder client User Guide describes how to install, configure and use the Scopia®

PathFinder client.

Related linksRelated Documentation on page 6Feedback on page 6

Related DocumentationThe PathFinder documentation set is available on the Avaya Utilities and Documentation CD-ROMsupplied 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 AcrobatReader free of charge from www.adobe.com.

Related linksAbout This Manual on page 6

FeedbackThe team at Avaya constantly endeavors to provide accurate and informative documentation. If youhave comments or suggestions regarding improvements to future publications, we would value yourfeedback.

Please send your comments to [email protected]. We thank you for your contribution.

Related linksAbout This Manual on page 6


mailto:%[email protected]


Chapter 2: Introducing PathFinder

About the Avaya Scopia® PathFinder SolutionEnterprises and Service Providers that want to secure network data and devices while takingadvantage of H.323 communications across LANs, WANs and the public Internet must inevitablyaddress the issue of firewall and Network Address Translation (NAT) device traversal.

Firewalls block unsolicited incoming communications from outside the local network. Most firewallsare not designed to allow video conferencing scenarios where everyone is allowed to connect toeveryone.

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. ANAT 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 deviceson 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 endpointswhich support the ITU H.460.18 and H.460.19 standards to enable traversal of firewalls. TheScopia® 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.460.18/H.460.19. 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 notsupport the H.460 standard, or in cases where the H.460 traversal does not work.

H.460.18 and H.460.19 are ITU standards which define protocols for the firewall traversal ofsignaling and media, respectively.

Note:

Only H.460 traversal-enabled endpoints can register with a PathFinder server. All other endpointsmust use the Scopia® PathFinder client for registration requests.



Scopia® PathFinder ComponentsScopia® 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 andmedia processing for communications among private enterprise networks served by Scopia®

PathFinder clients. When a Scopia® PathFinder client establishes an initial outboundconnection with the PathFinder server through a specific port of the firewall (the default port is3089), the PathFinder server can communicate with the Scopia® PathFinder client through thatparticular 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 Windowsoperating system. Scopia® PathFinder client supports non-H460 compliant endpoints. If all thedeployed endpoints support the H.460 standard, there is no need for the Scopia® PathFinderclient.

Configuring Your Firewall to Work with Scopia®PathFinder

Table 1: Firewall Port Configuration on page 8 describes the port configuration required to enableyour firewall to work with Scopia® PathFinder. For details, see the Reference Guide on Port Securityfor Avaya Scopia® Solution.

Table 1: Firewall Port Configuration

Port Type Use1719 UDP H.460.18 RAS1720 TCP IP Call Signaling/DPA Mode (Direct Public Access)2776 TCP H.460.18 Call Signaling2776 UDP H.460.19 Media (RTP)2777 TCP H.460.18 and H.460.19 Call Control2777 UDP H.460.19 Media Control (RTCP)3089 TCP/UDP Tunneling4000–5000 TCP/UDP H.323 Call Signaling/DPA Mode

Introducing PathFinder



Enterprise DeploymentFigure 1: Scopia® PathFinder Enterprise Deployment on page 9 shows how all cross-enterprisecalls pass between a Scopia® PathFinder client and the PathFinder server. Firewalls allowconnections between the PathFinder server and each Scopia® PathFinder client while still offeringuncompromised 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 enterpriseendpoints to register to a Scopia® PathFinder client by setting the Scopia® PathFinder client IPaddress as the endpoint gatekeeper. For more information on endpoint registration, consult yourendpoint model documentation.

Figure 1: Scopia® PathFinder Enterprise Deployment

Enterprise Deployment



Service Provider DeploymentFigure 2: Scopia® PathFinder Service Provider Deployment on page 10 shows how eachenterprise 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 firewallconfiguration. When an enterprise utilizes a gatekeeper, there is no need to open ports for incomingtraffic.

Figure 2: Scopia® PathFinder Service Provider DeploymentFor information on configuring your firewall, see Configuring Your Firewall to Work with Scopia®PathFinder on page 8.

Role of the PathFinder serverThe PathFinder server provides signaling and media processing for communications among privateenterprise networks served by Scopia® PathFinder clients. When a Scopia® PathFinder clientestablishes 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.

The PathFinder server has in-depth knowledge of the communication protocols used by the systemand is able to modify protocols and substitute the initiator’s address with its own address, so that itacts as the call initiator to the receiving end. This eliminates the need to publish internal nativeenterprise IP addresses.

Role of the Scopia® PathFinder clientThe Scopia® PathFinder client acts as the sole proxy through which internal devices behind anenterprise firewall communicate with external devices.

Figure 3: Scopia® PathFinder client Remote Site Deployment on page 11 shows a deployment ofthe Scopia® PathFinder client at a remote enterprise site behind the corporate firewall.

Figure 3: Scopia® PathFinder client Remote Site Deployment

Role of the Scopia® PathFinder client



About Direct Media ConnectionsDirect media connection enables a direct media flow between endpoints without passing thePathFinder server located at the main site.

Direct media connection is supported both within an enterprise branch and between enterprisebranches.

Related linksDirect Media Connection Within an Enterprise Branch on page 12Direct Media Connection Between Enterprise Branches on page 13

Direct Media Connection Within an Enterprise BranchIn this scenario, several Scopia® PathFinder clients are deployed at the same enterprise branch. Incalls between endpoints located at the same branch (but registered to different Scopia® PathFinderclients), the media goes directly between the endpoints without passing through the PathFinderserver located at the main site.




Figure 4: Direct Media Connection Within an Enterprise Branch

In Figure 4: Direct Media Connection Within an Enterprise Branch on page 13, Scopia® PathFinderclients 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 thePathFinder server at the main site. Support for this scenario is automatic and requires no specialsettings on the PathFinder server.

Related linksAbout Direct Media Connections on page 12

Direct Media Connection Between Enterprise BranchesIn this scenario, Scopia® PathFinder clients are deployed at different branch sites. The sites arelinked via a direct Multi Protocol Label Switching (MPLS) connection. When there is a call betweenthe sites, the media is routed directly between the sites without passing through the PathFinderserver located at the main site.

About Direct Media Connections



Figure 5: Direct Media Connection Between Enterprises

In Figure 5: Direct Media Connection Between Enterprises on page 14, there is an MPLSconnection 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 endpointswithout going through the PathFinder server at the main site.

To use this scenario, you need to configure a topology island on the PathFinder server. Forinformation on configuring topology islands, contact Customer Support.

Related linksAbout Direct Media Connections on page 12

Key Benefits of the Scopia® PathFinder SolutionThe key benefits of the Scopia® PathFinder solution include:

• Handles firewall and NAT problems without device upgrades or security compromises.




• Tunnels and transparently traverses firewalls and NAT devices, preserving securityadvantages.

• 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 SolutionThe 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-timemonitoring, 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 Windows2008 Server.

• Linux support.

• H.235 support (encryption only).

• Traffic separation — The ability to separate Management and Media IP traffic, and to complywith the strict security requirements of Service Providers.

• Status Check — Scopia® PathFinder client checks the status of the connection to thePathFinder 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.

Features of the Scopia® PathFinder Solution



• Avaya Scopia® ECS Gatekeeper Integration — The Scopia® PathFinder client can be installedon the same machine as the ECS.

• Local Gatekeeper — Enterprise gatekeeper support allows deploying a local gatekeeper at theremote site.

• Interoperability — Based on the H.323 standard, Scopia® PathFinder provides a high degree ofinteroperability with other H.323-compliant gateways, gatekeepers, terminals and MCUproducts. Interoperability with the ECS supports calling external endpoints by dialing to an IPaddress 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 viewedand modified from a remote location using a standard web browser.

• T.120 Data Collaboration — Scopia® PathFinder supports data transfers in calls, for legacyendpoints which are registered through the Scopia® PathFinder client, using the T.120standard. There is no support for H.460 endpoints.

• H.239 Support — Scopia® PathFinder supports H.239.

• H.460.18 and H.460.19 Support — Standard firewall/NAT traversal support.

• Quality Of Service (QoS) — Configurable coding of media packets to achieve QoS routingpriority on the IP network. The TOS bits of the IP datagram header can be configured forpriority level.

• Dial Plan — Scopia® PathFinder provides full dial plan support.

• Direct Media Connection — Ensures that media is routed directly between clients whenpossible.

• Access Control — Access to the Scopia® PathFinder user interface is password controlled.

• Authentication — The PathFinder server runs on a hardened Linux Operating System (Avayacustomized kernel). The Scopia® PathFinder client must be authenticated to connect theserver.

• Security Solution — The Scopia® PathFinder client contains an access control list (ACL) for theadministrator to define which devices are accessible via the client.

• Role Based User Management — Enables the allocation of suggested roles and default rightsprofiles.

• AES Encryption — Scopia® PathFinder supports encryption for all client-server traffic for callprivacy. This includes signaling and media encryption.

• Scalable Solution — With one client serving many endpoints, Scopia® PathFinder servers canbe neighbored. Clients hunt backup servers if a primary server is unavailable.

• Neighboring Server — The PathFinder server can be neighbored, thereby supporting largeenterprises or firewall/NAT traversal between organizations.

• URI Dialing — Enables endpoints registered with different gatekeepers or PathFinder serversto easily call each other. Without URI dialing, all systems must be neighbored to each other.




• Failover mechanism (Client Redundancy) — Activated upon system failures (Windows).

Features of the Scopia® PathFinder Solution



Chapter 3: System Requirements

Software Environment Options• Microsoft Windows 2000 Professional

• Microsoft Windows 2000 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 anapplication and cannot be installed as a service.

• Trustix 3.0

• Linux RedHat 9.0 desktop version

• Linux Redhat Enterprise ES release 4



Chapter 4: Installing the PathFinder Client

Installing the Scopia® PathFinder client On a WindowsPlatform

About this taskYou install the Scopia® PathFinder client by running the Scopia® PathFinder client installationwizard.

Procedure1. 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 notsupport, 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 pagedisplays. Select Support Clustering to support Scopia® PathFinder client redundancy on aWindows server cluster setup.



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 theinformation 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 LinuxPlatform

About this taskAvaya recommends using Red Hat 9.0 for installation on a Linux platform.

Procedure1. 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 configurationfile name appear.

Note:

Configuration files contain detailed descriptions for all items. You can refer to thesedescriptions for Linux client configuration. You can configure the Linux client only bymanually editing these files.

Launching the Scopia® PathFinder client ConfigurationTool

About this taskFor information about configuring the Scopia® PathFinder client, see Configuring a Connection to aPathFinder server on page 22.

ProcedureClick Start > All Programs > Scopia® PathFinder client > PathFinder Client.

Installing the PathFinder Client



The Scopia® PathFinder client Configuration Tool starts and the Connection tab displays.

Upgrading Scopia® PathFinder clientYou upgrade a Scopia® PathFinder client by installing the new version. During Scopia® PathFinderclient upgrade, you can install the newer version of the client only at the same location where theprevious version was installed.

If the old client is running during the upgrade, the Scopia® PathFinder client installation wizardprompts you to reboot.

Upgrading Scopia® PathFinder client



Chapter 5: Configuring the PathFinderClient

Configuring a Connection to a PathFinder serverAbout this taskYou can configure a connection to a PathFinder server, to configure additional Scopia® PathFinderServers 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 followingcases:

• 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 guestusers or endpoints which are not part of the enterprise to connect to your video conferencingnetwork.

Before you beginEnsure you have the PathFinder server password provided by the PathFinder server administrator.

Procedure1. 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 24.

5. Enter the PathFinder server password for connecting the Scopia® PathFinder client to thePathFinder server.

6. Enter a unique name to identify your Scopia® PathFinder client. By default, this field includesthe name of the computer on which the Scopia® PathFinder client is installed.



Note:

The values in the Server Password and Client Name fields must match the values inthe Password and Login ID fields defined for the corresponding Client User in theUsers tab of the PathFinder server. If no Client User role is defined on the PathFinderserver, the value in the Client Name field can be any string which is unique on thePathFinder server’s connected clients list. In this case, the Server Password field mustbe empty.

7. Select the This client is located on private network check box if the Scopia® PathFinderclient is located in the enterprise LAN. Figure 6: Scopia® PathFinder client Corporate LANDeployment on page 23 displays a Scopia® PathFinder client installed in the mainenterprise 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.

Configuring a Connection to a PathFinder server



Configuring a Scopia® PathFinder client Deployed On aWAN


2. Clear the This client is located on private network check box.

The Enable extension dialing using this client’s public IP address and Defaultextension options are available on the Advanced tab.

Configuring a Scopia® PathFinder client Deployed On aLAN


2. Select the This client is located on private network check box for clients which have toserve 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 IPcalls proxy port options are selected.

The IP calls proxy port option has a range of 1-65534; the default port is 1720.

Configuring Additional PathFinder serversAbout this taskThe Standby Servers option in the Connection tab enables you to configure up to three additionalPathFinder 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 aconnection is established with one of them.


2. Select Standby Servers.

The Standby Servers dialog box opens.

3. Configure additional servers, as follows:

a. Select the relevant check box.

Configuring the PathFinder Client



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 DetailsAbout this taskThis procedure describes how to configure a new Gateway or MCU for the Scopia® PathFinderclient.

Procedure1. 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.


Defining Access Permission to the PathFinder serverYou can add another level of security to a conferencing system by specifying which IP addressesare and are not authorized to communicate with the PathFinder server via the Scopia® PathFinderclient.

Related linksAuthorizing Communication with the PathFinder server Via the Scopia® PathFinder client onpage 26Blocking Communication with the PathFinder server Via the Scopia® PathFinder client on page 27

Configuring Gateway and MCU Details



Authorizing Communication with the PathFinder server Via theScopia® PathFinder client

Before you beginBefore you define the IP addresses authorized to communicate with the PathFinder server via theScopia® PathFinder client, note the following:

• Select All registered devices to allow all network devices listed in the Devices tab and allother H.323 endpoints which use this Scopia® PathFinder client as their gatekeeper tocommunicate with the PathFinder server via the Scopia® PathFinder client. For moreinformation 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, whilethe Scopia® PathFinder client is used for out-of-zone calls (incoming or outgoing calls) only, asshown 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 tothe Allow list. If you do not, the media to the endpoints registered to the enterprise gatekeeperis discarded by the Scopia® PathFinder client and it may not be possible to establish calls fromthe PathFinder server to the enterprise gatekeeper.

• When the MCU works with a media processing card (such as the MVP), you must add the IPaddress of the media processing card to the Allow list.




Procedure1. 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.


Related linksDefining Access Permission to the PathFinder server on page 25

Blocking Communication with the PathFinder server Via theScopia® PathFinder client

About this taskYou can specify IP addresses which are not authorized to communicate with the PathFinder servervia the Scopia® PathFinder client.

Procedure1. 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.

Defining Access Permission to the PathFinder server



5. Select OK.

The defined IP addresses are displayed in the Deny area of the Security tab.


Related linksDefining Access Permission to the PathFinder server on page 25

Configuring Startup PreferencesAbout this taskThe 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 firsttime 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 asan application or as a Support Clustering service.

• Connect to server on startup — The Scopia® PathFinder client connects to its PathFinderserver automatically at startup. If the client is installed as Support Clustering and is running onthe 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 trayonce it connects to its PathFinder server.

• Language — Scopia® PathFinder changes its user interface to the specified language afterrestart.

Procedure1. Select the Preferences tab.

2. Select the check boxes to configure options as required.

3. Select the language from the list.


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 ConferenceA guest user is a user with a terminal which is not registered to the organization gatekeeper. Youcan configure the Scopia® PathFinder client so that when a guest user dials in, there is a default




extension to which they are routed when no extension is specified. This option is available onlywhen the Scopia® PathFinder client is located on a public network.

Procedure1. On the PathFinder Client Configuration page, ensure that the Connection tab is selected.

2. Clear the This client is located on private network checkbox.

Figure 8: PathFinder Client Configuration — Connection Tab

3. On the Advanced 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 arerouted when dialing into a conference. The default extension is typically set to theScopia® Management VIVR.

Enabling Guest Users to Access a Conference



Figure 9: PathFinder Client Configuration Advanced Tab

Scopia® PathFinder redirects the call to the default extension when the user dials the IPaddress 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 itsgatekeeper.

Note:

By default, the public Scopia® PathFinder client denies all incoming calls. To accept allincoming calls by default, add an 0.0.0.0 entry to the Allow list in the Security tab. Fordetails, see Defining Access Permission to the PathFinder server on page 25.

Enabling the Enterprise Gatekeeper to Route IP CallsYou can invoke the Scopia® PathFinder solution to ensure firewall and NAT traversal when using anenterprise gatekeeper. This option is available only when the client is located on the private network.

Procedure1. On the PathFinder Client Configuration page, ensure that the Connection tab is selected.

2. Select the This client is located on private network checkbox.




Figure 10: PathFinder Client Configuration Connection Tab

3. On the Advanced tab:

a. Select the Enable Enterprise Gatekeeper using this client to route IP callscheckbox.

b. In the IP calls proxy port field, enter the value of the Route IP Calls to field on theECS that is used as the Enterprise Gatekeeper for this client.

Figure 11: PathFinder Client Configuration Advanced TabWhen dialing an external IP address from Enterprise Gatekeeper-registered endpoints, youmust configure the relevant entities which can make calls via Scopia® PathFinder. Select the

Enabling the Enterprise Gatekeeper to Route IP Calls



Security tab and in the Allow section, click Add to add the permitted IP addresses, or selectthe 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 serverVia the Scopia® PathFinder client on page 26.

Viewing Scopia® PathFinder Version InformationThe About tab displays information about the version of the Scopia® PathFinder client currently inuse.




Date post:	30-Nov-2021
Category:	Documents
Upload:	others
View:	13 times
Download:	0 times

User Guide for Avaya Scopia® PathFinder Client

Documents