Professional Documents
Culture Documents
Release 8.3
For Solution 8.3 (Intel servers only)
Issue 3
April 2016
2014-2016, Avaya, Inc. IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
All Rights Reserved. MUST NOT ACCESS OR USE THE HOSTED SERVICE OR
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
Notice SERVICE.
While reasonable efforts have been made to ensure that the Licenses
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
the right to make changes and corrections to the information in this WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,
document without the obligation to notify any person or organization UNDER THE LINK AVAYA SOFTWARE LICENSE TERMS (Avaya
of such changes. Products) OR SUCH SUCCESSOR SITE AS DESIGNATED BY
AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,
Documentation disclaimer USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED
Documentation means information published in varying mediums FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA
which may include product information, operating instructions and CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
performance specifications that are generally made available to users AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.
of products. Documentation does not include marketing materials. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,
Avaya shall not be responsible for any modifications, additions, or AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE
deletions to the original published version of Documentation unless WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN
such modifications, additions, or deletions were performed by or on AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA
the express behalf of Avaya. End User agrees to indemnify and hold RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
harmless Avaya, Avaya's agents, servants and employees against all AND ANYONE ELSE USING OR SELLING THE SOFTWARE
claims, lawsuits, demands and judgments arising out of, or in WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
connection with, subsequent modifications, additions or deletions to USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
this documentation, to the extent made by End User. YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
YOU ARE INSTALLING, DOWNLOADING OR USING THE
Link disclaimer SOFTWARE (HEREINAFTER REFERRED TO
Avaya is not responsible for the contents or reliability of any linked INTERCHANGEABLY AS YOU AND END USER), AGREE TO
websites referenced within this site or Documentation provided by THESE TERMS AND CONDITIONS AND CREATE A BINDING
Avaya. Avaya is not responsible for the accuracy of any information, CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
statement or content provided on these sites and does not APPLICABLE AVAYA AFFILIATE (AVAYA).
necessarily endorse the products, services, or information described Avaya grants You a license within the scope of the license types
or offered within them. Avaya does not guarantee that these links will described below, with the exception of Heritage Nortel Software, for
work all the time and has no control over the availability of the linked which the scope of the license is detailed below. Where the order
pages. documentation does not expressly identify a license type, the
Warranty applicable license will be a Designated System License. The
applicable number of licenses and units of capacity for which the
Avaya provides a limited warranty on Avaya hardware and software. license is granted will be one (1), unless a different number of
Refer to your sales agreement to establish the terms of the limited licenses or units of capacity is specified in the documentation or other
warranty. In addition, Avayas standard warranty language, as well as materials available to You. Software means computer programs in
information regarding support for this product while under warranty is object code, provided by Avaya or an Avaya Channel Partner,
available to Avaya customers and other parties through the Avaya whether as stand-alone products, pre-installed on hardware products,
Support website: https://support.avaya.com/helpcenter/ and any upgrades, updates, patches, bug fixes, or modified versions
getGenericDetails?detailId=C20091120112456651010 under the link thereto. Designated Processor means a single stand-alone
Warranty & Product Lifecycle or such successor site as designated computing device. Server means a Designated Processor that
by Avaya. Please note that if You acquired the product(s) from an hosts a software application to be accessed by multiple users.
authorized Avaya Channel Partner outside of the United States and Instance means a single copy of the Software executing at a
Canada, the warranty is provided to You by said Avaya Channel particular time: (i) on one physical machine; or (ii) on one deployed
Partner and not by Avaya. software virtual machine (VM) or similar deployment.
Hosted Service means an Avaya hosted service subscription that License type(s)
You acquire from either Avaya or an authorized Avaya Channel
Partner (as applicable) and which is described further in Hosted SAS Designated System(s) License (DS). End User may install and use
or other service description documentation regarding the applicable each copy or an Instance of the Software only on a number of
hosted service. If You purchase a Hosted Service subscription, the Designated Processors up to the number indicated in the order.
foregoing limited warranty may not apply but You may be entitled to Avaya may require the Designated Processor(s) to be identified in
support services in connection with the Hosted Service as described the order by type, serial number, feature key, Instance, location or
further in your service description documents for the applicable other specific designation, or to be provided by End User to Avaya
Hosted Service. Contact Avaya or Avaya Channel Partner (as through electronic means established by Avaya specifically for this
applicable) for more information. purpose.
Hosted Service Concurrent User License (CU). End User may install and use the
Software on multiple Designated Processors or one or more Servers,
THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA so long as only the licensed number of Units are accessing and using
HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA the Software at any given time. A Unit means the unit on which
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE Avaya, at its sole discretion, bases the pricing of its licenses and can
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA be, without limitation, an agent, port or user, an e-mail or voice mail
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO account in the name of a person or corporate function (e.g.,
UNDER THE LINK Avaya Terms of Use for Hosted Services OR webmaster or helpdesk), or a directory entry in the administrative
SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE database utilized by the Software that permits one user to interface
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE with the Software. Units may be linked to a specific, identified Server
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED or an Instance of the Software.
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE Database License (DL). End User may install and use each copy or
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY an Instance of the Software on one Server or on multiple Servers
AS YOU AND END USER), AGREE TO THE TERMS OF USE. IF provided that each of the Servers on which the Software is installed
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A communicates with no more than one Instance of the same
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT database.
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE CPU License (CP). End User may install and use each copy or
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, 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 software. The Third Party Terms shall take precedence over these
Server(s) does not exceed the performance capacity specified for the Software License Terms, solely with respect to the applicable Third
Software. End User may not re-install or operate the Software on Party Components to the extent that these Software License Terms
Server(s) with a larger performance capacity without Avayas prior impose greater restrictions on You than the applicable Third Party
consent and payment of an upgrade fee. Terms.
Named User License (NU). You may: (i) install and use each copy or The following applies only if the H.264 (AVC) codec is distributed with
Instance of the Software on a single Designated Processor or Server the product. THIS PRODUCT IS LICENSED UNDER THE AVC
per authorized Named User (defined below); or (ii) install and use PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
each copy or Instance of the Software on a Server so long as only CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE
authorized Named Users access and use the Software. Named REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH
User, means a user or device that has been expressly authorized by THE AVC STANDARD (AVC VIDEO) AND/OR (ii) DECODE AVC
Avaya to access and use the Software. At Avayas sole discretion, a VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
Named User may be, without limitation, designated by name, PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
corporate function (e.g., webmaster or helpdesk), an e-mail or voice PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS
mail account in the name of a person or corporate function, or a GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
directory entry in the administrative database utilized by the Software ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG
that permits one user to interface with the Software. LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.
Shrinkwrap License (SR). You may install and use the Software in Service Provider
accordance with the terms and conditions of the applicable license
agreements, such as shrinkwrap or clickthrough license THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNERS
accompanying or applicable to the Software (Shrinkwrap License). HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT
OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS
Heritage Nortel Software SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE
PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY
Heritage Nortel Software means the software that was acquired by FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL
Avaya as part of its purchase of the Nortel Enterprise Solutions PARTNERS HOSTING OF AVAYA PRODUCTS MUST BE
Business in December 2009. The Heritage Nortel Software is the AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED
software contained within the list of Heritage Nortel Products located PRODUCTS USE OR EMBED CERTAIN THIRD PARTY
at https://support.avaya.com/LicenseInfo under the link Heritage SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT
Nortel Products or such successor site as designated by Avaya. For SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS
Heritage Nortel Software, Avaya grants Customer a license to use REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE
Heritage Nortel Software provided hereunder solely to the extent of LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNERS
the authorized activation or authorized usage level, solely for the EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY
purpose specified in the Documentation, and solely as embedded in, SUPPLIER.
for execution on, or for communication with Avaya equipment.
Charges for Heritage Nortel Software may be based on extent of WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL
activation or use authorized as specified in an order or invoice. PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED
THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE
Copyright AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES
Except where expressly stated otherwise, no use should be made of THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY
materials on this site, the Documentation, Software, Hosted Service, AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729
or hardware provided by Avaya. All content on this site, the CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE
documentation, Hosted Service, and the product provided by Avaya WWW.SIPRO.COM/CONTACT.HTML. THE H.264 (AVC) CODEC IS
including the selection, arrangement and design of the content is LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR
owned either by Avaya or its licensors and is protected by copyright THE PERSONAL USE OF A CONSUMER OR OTHER USES IN
and other intellectual property laws including the sui generis rights WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I)
relating to the protection of databases. You may not modify, copy, ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD
reproduce, republish, upload, post, transmit or distribute in any way (AVC VIDEO) AND/OR (II) DECODE AVC VIDEO THAT WAS
any content, in whole or in part, including any code and software ENCODED BY A CONSUMER ENGAGED IN A PERSONAL
unless expressly authorized by Avaya. Unauthorized reproduction, ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER
transmission, dissemination, storage, and or use without the express LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED
written consent of Avaya can be a criminal, as well as a civil offense OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL
under the applicable law. INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS
MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://
Virtualization WWW.MPEGLA.COM.
The following applies if the product is deployed on a virtual machine. Compliance with Laws
Each product has its own ordering code and license types. Note that
each Instance of a product must be separately licensed and ordered. You acknowledge and agree that it is Your responsibility for
For example, if the end user customer or Avaya Channel Partner complying with any applicable laws and regulations, including, but not
would like to install two Instances of the same type of products, then limited to laws and regulations related to call recording, data privacy,
two products of that type must be ordered. intellectual property, trade secret, fraud, and music performance
rights, in the country or territory where the Avaya product is used.
Third Party Components
Preventing Toll Fraud
Third Party Components mean certain software programs or
portions thereof included in the Software or Hosted Service may Toll Fraud is the unauthorized use of your telecommunications
contain software (including open source software) distributed under system by an unauthorized party (for example, a person who is not a
third party agreements (Third Party Components), which contain corporate employee, agent, subcontractor, or is not working on your
terms regarding the rights to use certain portions of the Software company's behalf). Be aware that there can be a risk of Toll Fraud
(Third Party Terms). As required, information regarding distributed associated with your system and that, if Toll Fraud occurs, it can
Linux OS source code (for those products that have distributed Linux result in substantial additional charges for your telecommunications
OS source code) and identifying the copyright holders of the Third services.
Party Components and the Third Party Terms that apply is available Avaya Toll Fraud intervention
in the products, Documentation or on Avayas website at: https://
support.avaya.com/Copyright or such successor site as designated If You suspect that You are being victimized by Toll Fraud and You
by Avaya. The open source software license terms provided as Third need technical assistance or support, call Technical Service Center
Party Terms are consistent with the license rights granted in these Toll Fraud Intervention Hotline at +1-800-643-2353 for the United
Software License Terms, and may contain additional rights benefiting States and Canada. For additional support telephone numbers, see
You, such as modification and distribution of the open source
the Avaya Support website: https://support.avaya.com or such
successor site as designated by Avaya.
Security Vulnerabilities
Information about Avayas security support policies can be found in
the Security Policies and Support section of https://
support.avaya.com/security.
Suspected Avaya product security vulnerabilities are handled per the
Avaya Product Security Support Flow (https://
support.avaya.com/css/P8/documents/100161515).
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support website: https://support.avaya.com, or such successor site
as designated by Avaya.
Contact Avaya Support
See the Avaya Support website: https://support.avaya.com 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: https://support.avaya.com (or such successor site as
designated by Avaya), scroll to the bottom of the page, and select
Contact Avaya Support.
Trademarks
The trademarks, logos and service marks (Marks) displayed in this
site, the Documentation, Hosted Service(s), and product(s) provided
by Avaya are the registered or unregistered Marks of Avaya, its
affiliates, its licensors, its suppliers, or other third parties. Users are
not permitted to use such Marks without prior written consent from
Avaya or such third party which may own the Mark. Nothing
contained in this site, the Documentation, Hosted Service(s) and
product(s) should be construed as granting, by implication, estoppel,
or otherwise, any license or right in and to the Marks without the
express written permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
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.
Contents
Avaya Scopia PathFinder provides a complete firewall and NAT traversal solution for H.323
deployments, enabling secure connectivity between enterprise networks and remote sites.
Avaya Scopia PathFinder is part of the Scopia Solution the components of which can be
combined to fit the existing network topology and videoconferencing requirements of the
organization.
PathFinder maintains the security and advantages of firewall and NAT over heterogeneous video
networks and allows seamless integration with existing video endpoints and infrastructure
components.
Figure 1: PathFinder Functionality on page 8 illustrates the functionality of PathFinder.
PathFinder uses the H.460 protocol. H.460 enhances the standard H.323 protocol to manage
firewall/NAT traversal, employing ITU-T standards.
Endpoints which are already H.460 compliant can communicate directly with the PathFinder server,
where the endpoint acts as an H.460 client to the PathFinder server which acts as an H.460 server.
The endpoints in a private network can communicate with the endpoints located in the public
network via the PathFinder server. Endpoints in the public network can join a conference hosted in
the private network via the PathFinder server if there is an open connection through the firewall. The
ECS provides standalone address resolution functionality in H.323 networks.
The PathFinder server offers external endpoints a static address when joining conferences hosted in
your organization. You can dial1234@pathfinder.company.com to access from outside the firewall,
or you can dial 1234 directly if you are an H.460 client logged in to the PathFinder server.
Related links
Main Features of PathFinder on page 9
Technical Specifications on page 10
The PathFinder server supports Direct Public Access (DPA). Any public H.323 endpoint can
directly call through the PathFinder server without the need to deploy an additional Scopia
PathFinder client. Public H.323 endpoints which do not support the H.460 standard can directly
call the PathFinder server and easily and securely participate in any call or conference call
inside the organization.
URI Dialing
With support for URI dialing PathFinder enables seamless and intuitive connectivity between
enterprises, with customers and home workers. The following dialing methods are supported
for both outgoing public calls and incoming public calls:
- <Number>@<Domain> e.g. 5640@company.com
- <Number>@<IP Address> e.g. 5640@216.2.12.310
- <Name>@<Domain> e.g. Paul@company.com
- <Name>@<IP Address> e.g. Paul@216.2.12.310
Enhanced management capabilities
Avaya Scopia Management fully supports the PathFinder server providing comprehensive
maintenance tools such as user management, real-time monitoring, traps and alarms,
automated log collection, and direct web access.
Integrated web-based event log
Use the event log for quick and effective troubleshooting
Related links
About PathFinder on page 8
Technical Specifications
This section lists important information about the device you purchased. Refer to this information
when preparing system setup and afterwards to verify that the environment still complies with these
requirements.
This information lists the technical specifications of the Avaya Scopia PathFinder server.
System power requirements:
- 600W, 100-240VAC input, 50/60Hz auto-switched
Environmental requirements:
- Operating temperature: 5C to 35C (41F to 95F)
- Humidity: 8% to 90% non-condensing
- Storage and transit temperature: -40C to 60C (-40F to 140F)
Physical dimensions:
- Size: 437mm (17.2) width x 43mm (1.7) height x 650mm (25.6) depth
- Weight: ~16.3kg (~36lbs)
External interfaces:
- Dual Gigabit NICs
- 1 x DB9 serial port connector
- 2 x USB 2.0 connectors
Communications:
- H.323
- IPv4
- Bit rate: up to 4Mbps per call
Call capacity:
- Up to 100 concurrent calls
- Up to 600 registered devices
Scalability:
- Radware AppDirector 208
- Radware AppDirector 1000
- F5 BIG-IP Load Traffic Manager 1600 Series
Firewall traversal:
- H.460.18, H.460.19 including support for multiplexed media
- Direct Public Access (DPA) solution for direct communication between internal endpoints in
the internal network and external ones in the public network.
- If the remote system includes an installation of the Scopia PathFinder client, you can tunnel
communication through the firewall securely by routing traffic via the Scopia PathFinder
client.
Security:
- H.235 for call privacy in all traversal modes (H.460, tunneling, DPA)
Related links
About PathFinder on page 8
Change history
Perform procedures in this section to prepare the site and device for installation.
Related links
Planning Your Topology for PathFinder on page 13
Ports to Open on PathFinder on page 15
Checking Site Suitability on page 20
Unpacking the Device on page 20
Inspecting for Damage on page 21
To create a secure deployment, administrators in organizations need to separate the various types
of network traffic in the deployment.
The PathFinder server houses two NIC cards. The PathFinder server provides uncompromised
security by using the two NICs for separating and restricting IP traffic in the deployment. The
external NIC accepts access only from a very specific range of ports and media types, which
significantly limits intrusive attempts on the system. The internal NIC is dedicated to the local traffic.
We recommend configuring the second NIC to also support management traffic.
There are two recommended ways of deploying the dual-NIC PathFinder server:
Bypassing the enterprise firewall
The external NIC is connected to the external network while the internal NIC resides in the
enterprise LAN. The external endpoints have access to the external NIC through the firewall
and the NAT. The internal NIC communicates with the components of the internal network and
bypasses the firewall to the enterprise LAN. Figure 2: Deploying a Dual-NIC PathFinder server
bypassing the enterprise firewall on page 14 illustrates this type of deployment.
Deploying the PathFinder server requires configuring the unit itself as well as several other
components. For information on components that are part of the Scopia Solution, see the Scopia
Solution guide.
SCOPIA PathFinder Servers can also be clustered behind a load balancing system for scalability
and high availability. See Scalability, High Availability and Load Balancing with PathFinder on
page 59.
Important:
Small and medium-size enterprises that set up videoconferences within their enterprise can
choose to deploy PathFinder server with a single NIC. Contact Customer Support for
information on that type of deployment.
Related links
Preparing the PathFinder server Setup on page 13
When opening ports to and from PathFinder server, use the following as a reference:
If opening ports that are both to and from the PathFinder server, see Table 2: Bidirectional
Ports to Open the PathFinder server on page 17.
If opening ports that are both to and from the Scopia PathFinder client, see Table 3:
Bidirectional Ports to Open on the Scopia PathFinder client on page 19.
Important:
In order for an H.323 endpoint (or other H.323 device) within the enterprise to successfully
connect to the PathFinder server in the DMZ via the enterprise firewall (see Figure 5: Contacting
PathFinder server from within the enterprise on page 17), you must do one of the following:
Install a Scopia PathFinder client within the enterprise
Use H.460-enabled endpoints
Open the internal firewall to the PathFinder server (1024-65535, bidirectional)
Important:
The specific firewalls you need to open ports on depends on where your PathFinder server,
Scopia PathFinder client, and other Scopia Solution products are deployed.
Important:
If there is a firewall between the H.323 client and the Scopia PathFinder client, all high ports
must be opened in both directions (1024-65535). We therefore recommend no firewall between
the endpoint and the Scopia PathFinder client.
Related links
Preparing the PathFinder server Setup on page 13
Caution:
The accessories kit is situated on top of the device inside the shipping box and can be
damaged if the box is placed upside down. Pay attention to the This Side Up symbol on
the shipping box to handle the box correctly at all times.
Caution:
To prevent injury and equipment damage, follow the lifting guidelines described in the
Safety Guide when lifting or moving the shipping box.
3. Cut the plastic straps.
Caution:
The plastic straps are tightly stretched and can hit you when you cut them. To avoid this,
make sure you do not face the side of the box secured by the straps before you cut the
straps.
4. Cut the strapping tape.
5. Open the shipping box.
6. Take the accessories kit out of the shipping box.
7. Take the device out of the shipping box.
8. Carefully open the additional boxes, remove the packing material, and remove the drives
and other contents.
Important:
We recommend keeping the packaging materials in case you need to repack the device.
9. Remove the cellophane wrapping from the server case.
10. After opening the shipping box, check the shipment is complete. Compare the contents of
the shipment with the packing list included in the box.
Related links
Preparing the PathFinder server Setup on page 13
We recommend choosing a rack without doors. If installing in an enclosed rack, ensure that
the rack has adequate ventilation.
2. Ensure that the environment is suitable and set up the rack, considering factors such as the
ambient temperature of the room. Read the safety instructions that came with your rack for
details.
Important:
Maintain a minimum clearance of 30 inches (76.2 cm) in the rear of the rack to allow
adequate airflow.
Ensure the rack is stable. The leveling jacks at the bottom of the rack should be fully
extended.
3. Decide where on the rack to place the device, using the guidelines listed below. Mark this
location on the rack, ensuring that the height is the same on each rack post.
Proper placement prevents the device from overheating and ensures that the rack is stable.
Find a space on the rack which is 3 empty square holes in height (1U), as shown in Figure
7: One rack unit of space on the rack on page 23.
Note that the holes on the rack posts are not spaced equally. They form a repeating
pattern of two holes close together, then one hole separate, then two holes close together
and so on.
The top of the device should start on the lower of the two holes which are close together.
4. Make sure you have the following items, which were shipped with the device and are used to
mount the rails to the rack (Figure 8: Preparing the parts required to mount the rails on
page 24):
Two long outer rails and two short outer rails, to be attached to the rack itself (as
described in Mounting the Outer Rails on to the Rack on page 25)
Two inner rail extensions, used to attach the device to the outer rails on the rack (as
described in Mounting the Device on to the Outer Rails on page 28)
Eight flat-head long screws (Phillips cross recessed flat-head machine screws M5x12mm).
You need only four to mount the device.
Eight brackets (finishing washers M5). You need only four to mount the device.
Two flat-head short screws (Phillips cross recessed flat-head machine screws 6-32
UNCx3/16")
Procedure
1. Connect the long and short outer rails to each other by sliding the knob on the short rail
through the rounded end of the slot on the long rail (Figure 10: Connecting the two outer
rails on page 26).
Figure 11: Attaching the short rail to the rear of the rack
b. Slide the long rail towards the front of the rack, adjusting the length according to the
depth of the rack. Attach it to the front of the rack as you did to the rear of the rack.
Important:
To unfasten the rail pins from the rack, push the safety latch to release:
The outer rail is now attached to the rack, as shown in Figure 14: Side view of rack with
the outer rail attached on page 28.
Figure 14: Side view of rack with the outer rail attached
3. Repeat all steps to mount the outer rails to the other side of the rack.
4. Continue with Mounting the Device on to the Outer Rails on page 28.
Related links
Mounting the Device on to the Rack on page 22
Make sure you have the following items, which were shipped with the device and are used to
mount the rails to the rack (Figure 15: Preparing the parts required to mount the device onto
the rails on page 29):
- Two inner rail extensions
- Two flat-head short screws (Phillips cross recessed flat-head machine screws 6-32
UNCx3/16")
- Two flat-head long screws (Phillips cross recessed flat-head machine screws M5x12mm)
- Two brackets (finishing washers M5)
Figure 15: Preparing the parts required to mount the device onto the rails
Procedure
1. Attach the inner rail extension to the rear of the device:
a. Slide the rear inner rail extension towards the front of the device (see Figure 16:
Attaching inner rail extensions to the device on page 29).
The hooks on the side of the device fasten the inner rail in place.
Important:
To pull out the device, you need to slide the long part of the latch on each side
simultaneously to release the safety lock. Slide the right latch up and slide the left latch
down (Figure 19: Removing the device from the rails on page 31).
Figure 20: Securing the front panel of the device to the front post
Related links
Mounting the Device on to the Rack on page 22
Procedure
1. On the rear panel, connect the power cable to the AC power connector (Figure 21: Rear
panel of the device on page 33).
Related links
Setting up the Device on page 22
After connecting the cables and switching on the Avaya Scopia PathFinder server, perform the
initial configuration as described in these sections:
Related links
Configuring the IP Addresses of the PathFinder server on page 35
Configuring Ports on the PathFinder server on page 40
Integrating the PathFinder server with Other Scopia Solution Components on page 45
Enabling Internal Endpoints to Call External Endpoints on page 47
Configuring Priority of Audio or Video on page 57
The system automatically disables the external role of eth1. The window displays the
NIC configuration as illustrated in Figure 25: The network interface configuration
screen on page 38.
Settings > General (Figure 26: The page displaying the NIC IP addresses in the
Settings tab on page 39).
Figure 26: The page displaying the NIC IP addresses in the Settings tab
3. Configure the DNS server as your enterprise DNS server.
a. In the Network administration menu enter 3 to access the DNS configuration menu.
b. Enter A to add a DNS server.
c. Enter the IP address of the new server.
4. Configure the new FQDN.
a. In the Network administration menu, enter 4 to access the FQDN configuration menu.
b. Enter the FQDN of the PathFinder server. The system displays the host name and
domain name, as well as the new FQDN of the PathFinder server.
5. Add a static route to define call paths so that they are redirected from the PathFinder server
to ECS and internal endpoints on other subnets.
A static route is required if the internal network has many subnets. For example:
If the internal NIC is in network 168.168.1.10, and all internal endpoints and the ECS are
also located in network 192.168.1.0, there is no need for a static route.
If the internal network has many subnets (such as 168.168.2.0, 172.16.0.0), you need to
configure the static route so that the PathFinder server can communicate with devices
inside subnets other than 168.168.1.0.
a. In the Network administration menu enter 6 to access the static route configuration
menu.
b. Enter A to add a new static route.
c. Enter the routing rule as: <host_ip|network_ip/prefix> via <gateway>>
6. Close the SSH session.
Related links
Performing the Initial Configuration of the PathFinder server on page 35
Limiting the TCP/UDP Port Range for H.323 Direct Access Calls
on the PathFinder server
About this task
The Avaya Scopia PathFinder server has designated ports 4000-5000 for H.323 Direct Public
Access (DPA), which allows non-H.460 public endpoints to call internal endpoints without being
registered to the PathFinder server. To provide additional security for your firewall, you can limit this
range.
To calculate approximately how many ports the PathFinder server uses, multiply the number of
simultaneous DPA calls by 10. The multiplication factor is lower for audio-only calls and higher for
calls with dual video. We recommend using 10 as an approximation.
Procedure
1. Access the PathFinder server Administrator web interface.
2. Select Settings > General.
3. Enable H.323 Direct Access by selecting the checkbox next to H.323 Direct Access (Figure
28: H.323 Direct Access Settings on page 41).
To calculate the number of ports PathFinder uses, add the two figures that you get by the following
methods:
Multiply the number of simultaneous H.323 calls by 10.
The multiplication factor is lower for audio-only calls and higher for calls with dual video. Use
10 as an approximate multiplication factor.
Count one port for each endpoint registration.
For example, if you have 100 endpoints, count 100 ports.
You must restart PathFinder after you modify the port range.
Procedure
1. Access the PathFinder server Administrator web interface.
2. Click Settings > General.
3. In the Internal interface section, set the port range to 12000 up to 15000.
The maximum port range is from 9000 to 65535. The port range setting requires a minimum
range of 300 ports.
4. Click Save.
Next steps
Restart PathFinder
Related links
Configuring Ports on the PathFinder server on page 40
If an external H.460 endpoint in the public internet can dial the E.164 number of an endpoint within
the enterprise, the ports used are:
1. The H.460 endpoint requests registration (RRQ) to the PathFinder server via port 1719.
2. The PathFinder server confirms RRQ.
3. The endpoint sends a call request in the form of two connections to the PathFinder server:
Port 2776 for call setup with H.225. H.225 is part of the set of H.323 protocols. It defines
the messages and procedures used by gatekeepers to set up calls.
Port 2777 for signaling with H.245
Signaling, also known as call control, sets up, manages and ends a connection or call.
These messages include the authorization to make the call, checking bandwidth, resolving
endpoint addresses, and routing the call through different servers. Signaling is transmitted
via the H.225.0/Q.931 and H.225.0/RAS protocols in H.323 calls, or by the SIP headers in
SIP calls. Signaling occurs before the control aspect of call setup.
The PathFinder server in turn routes these requests to the ECS.
For more information on the firewall's port configuration see Ports to Open on PathFinder on
page 15. The PathFinder server ports are configured by default to support these calls. Follow this
procedure to change the default configuration.
Procedure
1. Access the PathFinder server Administrator web interface.
2. Select Settings > H.460. The window displays the default port values for H.460 endpoint
port access.
Field Description
Ras Port RAS (Registration, Admission, Status) is required for
communication between the remote endpoint and the PathFinder
server. It allows the endpoint to request admission of the call.
Important:
Avoid changing the default value of the RAS public port. This
change requires changing the port value for all endpoints in
your deployment.
Call Signal Port Used for call setup, call proceeding, alerts, connection, call
release upon completion.
Call Control Port Provides control service to the multimedia session that has been
established.
RTCP Port Real-time Transmission Control Protocol provides statistics on the
quality of the multimedia session in place.
RTP Port Real-Time Transport Protocol port carries the media flow.
Multiplex When enabled, reduces the number of required ports by sending
media and control communications over RTP/RTCP via UDP
ports 2776 and 2777. The Multiplex option is automatically
enabled when you enable NAT support (see Integrating the
PathFinder server with NAT on page 46).
Related links
Configuring Ports on the PathFinder server on page 40
Field Description
NAT Support Enable NAT Support if the external NIC of the PathFinder server
uses a private IP address to communicate with endpoints outside
the organization.
If deploying the PathFinder with a load balancer, you must enable
NAT Support. For more information, see Configuring PathFinder
servers for the Load Balancer on page 67.
Address Enter the public IP address of the NAT device in the Address field.
Table continues
Field Description
Important:
In the firewall/NAT device, verify that the NAT address is
mapped to the private IP address of the PathFinder server's
external NIC.
Port If required, change the Scopia PathFinder client port number which
is set to 3089 by default.
Related links
Integrating the PathFinder server with Other Scopia Solution Components on page 45
To set up this connection, you need to configure the PathFinder server to accept H.323 calls and
forward them. You also need to configure the Avaya Scopia ECS Gatekeeper to one or more
PathFinder servers to facilitate the routing of these calls. For more information on configuring the
ECS, see the Reference Guide for Avaya Scopia ECS Gatekeeper.
Procedure
1. Access the PathFinder server Administrator web interface.
2. Select Settings > General.
3. Configure the following settings for Direct Public Access:
Field Description
H.323 Direct Access Enable H.323 Direct Access to open a direct dial line to the
PathFinder server for H.323 endpoints that do not support the
secure H.460 protocol.
Port Range Define the range of ports used for direct H.323 calls in the
field.
Important:
If the external NIC of the PathFinder server is located
behind a firewall, this range of port must also be opened
in the firewall, as well as port 1720 for H.323 signaling.
Default Extension Enter the default extension that you usually configure to the
MCU IVR (Interactive Voice Response). PathFinder server
redirects a call to the default extension when the endpoint
dials only the server's IP address without any extension.
4. Select Save.
Related links
Enabling Internal Endpoints to Call External Endpoints on page 47
To access an endpoint in the other company, the URIs domain name is the second companys
firewall traversal system, like the name of their PathFinder server, or the organization's domain
name. For example, in Figure 34: URI dialing between two enterprises using PathFinder on
page 49, dialing to the partner company requires knowing the following:
The name or number of the endpoint, in this example xt1
The domain name of the PathFinder server of that company, public.partner.com in this
example, or the organization's domain name, partner.com.
Important:
As with regular web domain names, the name of the PathFinder server resolves to an IP
address via standard DNS lookup if it has been allocated a global DNS name. If the servers IP
address does not have a DNS name, the URI dial should directly specify the servers IP address
instead. For example, the URI xt1@123.456.789.1 specifies the alias followed by the servers IP
address.
To set up this connection, you need to configure the PathFinder server to accept H.323 calls and
forward them. You also need to configure the ECS to define one or more PathFinder servers as
ECSs neighbor, to facilitate the routing of these calls.
Related links
Enabling Internal Endpoints to Call External Endpoints on page 47
Field Description
Local Domain Name Enter the domain name of the organization in which the PathFinder
server is physically located. This configuration enables the server to
optimize the handling of calls when used with Resolve on Server
First, described below.
Resolve on Server First Select to strip the domain name/IP address from the dialed string
before transferring the relevant message to its destination.
Important:
We recommend enabling this setting to optimize the handling
of call transfer.
Do not select this option if your organization has a policy of
transferring a message to its destination by using the complete
endpoint's dial string (for example, 1234@5.6.7.8) instead of
its alias (1234 in this example).
Figure 37: Configuring a Neighboring PathFinder server for outgoing URI calls
6. Configure the PathFinder server as a neighboring server to the ECS to facilitate outgoing
URI dialing, as described below.
This is required since the external endpoint is not registered to the gatekeeper, and therefore
it cannot resolve the address of the external endpoint. When an internal endpoint calls an
external endpoint using its URI address, the gatekeeper sends the request to all devices
configured as its neighbor, which may include other gatekeepers and PathFinder servers, to
check which one can resolve the address.
Field Description
Add Select to add the PathFinder server.
Prefix Leave this field empty since URI dialing does not route calls
to zones using dial prefixes. URI dialing routes calls using
the domain name in the URI string, which is resolved to any
zone worldwide.
Description Enter the name of your PathFinder server.
IP Address Enter the IP address of your PathFinder server. This is the
IP address of the internal NIC connected to the internal
network.
Port The default port value, 1719, is mandatory for URI dialing.
7. Select Upload.
8. If your deployment includes multiple PathFinder servers, including several servers acting as
one server behind a load balancer, repeat the steps above for each PathFinder server.
Related links
Enabling Internal Endpoints to Call External Endpoints on page 47
You can also configure the gatekeeper to forward URI calls to the PathFinder server, as described
in Enabling Internal Endpoints to Call External Endpoints on page 47. For deployments with multiple
PathFinder servers, including several servers acting as one server behind a load balancer, perform
this procedure for each server. For more information about configuring multiple PathFinder servers
behind a load balancer, see Scalability, High Availability and Load Balancing with PathFinder on
page 59.
Before you begin
Verify you have the IP address of the Avaya Scopia PathFinder server NIC connected to the
internal network.
If you are configuring multiple PathFinder servers, with or without a load balancer, do this for
each PathFinder server.
Enable Direct Public access on the PathFinder server, as described in Configuring Access for
H.323 Legacy Endpoints on page 47. This allows internal endpoints to call external legacy H.
323 endpoints that do not support H.460.
If you are configuring multiple PathFinder servers, with or without a load balancer, do this for
each PathFinder server.
Verify you have the Direct Public Access address of the PathFinder server:
If you are configuring multiple PathFinder servers, with or without a load balancer, do this for
each PathFinder server.
1. From the PathFinder server web interface, select Client Status > Client Name that has
the format paProxy@<IP address>. The PathFinder server automatically created this
proxy address when you enabled Direct Public Access.
2. Note the address (IP address and port) under Q.931 Address > Registration
Information(see Figure 39: Registration information required for configuring the ECS on
page 55).
You need this registration information to configure IP dialing.
Field Description
Route IP calls to Select this option to enable routing IP calls to the PathFinder server.
Add Select to add the PathFinder server to the list of servers. The
gatekeeper routes IP calls to the PathFinder server(s) in the list.
IP Address Enter the IP address and port of the PathFinder server that it
Port automatically created when you enabled H.323 Direct Access. For
more information, see Configuring Access for H.323 Legacy
Endpoints on page 47.
You need to add the PathFinder server's IP address to instruct the
gatekeeper where to forward all IP calls when the destination IP
address is not registered to the gatekeeper.
4. Select OK.
5. Select Upload.
6. If your deployment includes multiple PathFinder servers, including several servers acting as
one server behind a load balancer:
a. Repeat the steps above for each PathFinder server.
b. Verify you have the correct redundancy policy set up between the gatekeeper and each
PathFinder server.
The ECS has its own load balancing method to work with multiple PathFinder servers
for outgoing calls from internal endpoints to external endpoints (Figure 41: Forwarding
traffic to the PathFinder server on page 57). By default, it is configured to the
Scalability policy, enabling it to send requests to each PathFinder server in the cluster,
in a round robin manner.
Alternatively, you can set the ECS to work with the Priority policy, where the ECS can
route the call to the first PathFinder server in the list and continue to the next one only if
a failure occurred. Contact Customer Support to configure this setting.
Important:
This is separate from the redundancy policy you configured for the load balancer,
which instructs it how to direct incoming traffic from the external network to the
internal network (Figure 41: Forwarding traffic to the PathFinder server on
page 57). For more information about setting up the load balancer, see
Scalability, High Availability and Load Balancing with PathFinder on page 59.
video and audio codecs, and other parameters like resolution, bitrate and frame rate. Control
is communicated via H.245 in H.323 endpoints. Control occurs within the framework of an
established call, after signaling.
Follow this procedure to determine the relative priorities for audio, video, and control transmitted via
the PathFinder server.
Procedure
1. Access the PathFinder server Administrator web interface.
2. Select the Settings > General > QoS tab.
3. In the General tab navigate to QoS.
Related links
Performing the Initial Configuration of the PathFinder server on page 35
Enabling Internal Endpoints to Call External Endpoints on page 47
Avaya Scopia PathFinder servers provide firewall traversal and NAT solution services to both H.
460-compliant and non-H.460 endpoints. You can provide both scalability and high availability for
your PathFinder servers by deploying multiple PathFinder servers behind a load balancer. High
availability is a state where you ensure better service and less downtime by deploying additional
servers. Scalability describes the ability to increase the capacity of a network device by adding
another identical device (one or more) to your existing deployment.
A load balanced group of PathFinder servers, also known as a cluster, act as a single virtual server.
A load balancer can distribute traffic among the servers in the cluster, so that if one PathFinder
server has too many incoming calls at a given time, for example, another PathFinder server can
take up the load of managing incoming calls in a round-robin manner. Other load balancing methods
can be configured for the load balancer, according to your deployment's requirements. Likewise, if
one server fails, the remaining servers can continue working, providing high availability of the
deployment.
Figure 43: Load balancing PathFinder server in the enterprises DMZ on page 60 illustrates a
typical deployment of multiple PathFinder servers with a load balancer.
Load balancing multiple PathFinder servers is also often required for service provider deployments,
where the large capacity can serve multiple enterprises within one deployment. This topology is
similar to the one illustrated in Figure 43: Load balancing PathFinder server in the enterprises
DMZ on page 60.
In each case, the deployment requires the following components:
PathFinder servers
The servers are configured as a cluster that has a virtual IP address for routing calls inbound to
the local network. We recommend connecting both network interface cards (NIC) of each
PathFinder server:
- The first NIC connects to a DMZ switch along with the load balancer
- The second NIC connects to the companys internal network
For more information about a dual NIC configuration, see Configuring the IP Addresses of the
PathFinder server on page 35. PathFinder server s with one NIC can also be part of the
cluster.
A load balancer
A load balancer groups together a set (or cluster) of servers to give them a single IP address,
known as a virtual IP address. It distributes client service requests amongst a group of servers.
It distributes loads according to different criteria such as bandwidth, CPU usage, or cyclic
(round robin). Load balancers are also known as application delivery controllers (ADC).
The following load balancers are certified for the current version of PathFinder server:
- Radware AppDirector
- F5 BIG-IP Load Traffic Manager (LTM)
PathFinder server redundancy can also be managed using other third-party load balancers.
A gatekeeper
A gatekeeper routes audio and video H.323 calls by resolving dial strings (H.323 alias or URI)
into the IP address of an endpoint, and handles the initial connection of calls. Gatekeepers also
implement the dial plan of an organization by routing H.323 calls depending on their dial
prefixes. Scopia Management includes a built-in Avaya Scopia Gatekeeper, while ECS is a
standalone gatekeeper.
H.323 endpoints
Your deployment can include H.323 endpoints that are H.460 compliant or H.323 (legacy)
endpoints which do not support H.460. Both types of endpoints can reside either in the
enterprise (secured network) or in the Internet. Endpoints that want to register to the
PathFinder server do so via the clusters virtual IP address or register to the Scopia
PathFinder client if they are not H.460-compliant. The Scopia PathFinder client registers to
the PathFinder server via the clusters virtual IP address.
For information on the components that are part of the Scopia Solution, see the Scopia Solution
Guide.
Related links
Workflow to Configure PathFinder server for Redundancy on page 61
Configuring Radware Load Balancer for PathFinder servers on page 62
Configuring the F5 BIG-IP LTM for PathFinder servers on page 64
Configuring PathFinder servers for the Load Balancer on page 67
Field Description
Farm Name Enter the name of the server farm.
Aging Time Indicates the number of seconds before the connection between
a source IP to the server is timed out (disconnected). The source
IP refers to either the endpoint or the Scopia PathFinder client,
depending on whether the endpoint is connecting directly or via
the Scopia PathFinder client.
Set the aging time to a high value (for example, 90000). Within
that period of time, AppDirector routes the reconnecting client to
that specific server.
Dispatch Method Select the method the load balancer uses for distributing traffic
between servers in this farm. We recommend one of the
following:
Round Robin: Directs each endpoint service request to
another PathFinder server, in turn.
Least Amount of Traffic: Directs endpoint service requests to
the PathFinder server with the least amount of traffic.
Sessions Mode Select EntryPerSession to ensure the load balancer continues
to route packets from the same client to the same PathFinder
server throughout the duration of the videoconference.
3. Configure a virtual IP address for the farm, as described in the AppDirector documentation.
This is the address the load balancer uses to forward endpoint service requests to the
PathFinder servers grouped in the farm.
4. Configure the Layer 4 rules (or policies) the load balancer uses to manage traffic, as
described in the AppDirector documentation.
AppDirector uses the Layer 4 protocol and the requests destination port to select the
required farm. TCP (Transmission Control protocol) and UDP (User Datagram Protocol) are
part of the Layer 4 protocol. AppDirector manages the virtual IP addresses using Layer 4
policies.
The settings described below are specific to PathFinder server and may differ from a typical
AppDirector deployment:
Use the same farm name as above
Set L4 Protocol to Any. This ensures the farm supports any IP protocol, including TCP
and UDP.
5. Add each PathFinder server to the farm as described in the AppDirector documentation.
The settings described below are specific to PathFinder server and may differ from a typical
AppDirector deployment:
Enter the server's details, such as the IP address
Verify that Client NAT is set to Disabled.
6. To ensure communication is possible with the PathFinders, add the farm's virtual IP address
and service port to the organization's firewalls.
7. Continue with Configuring PathFinder servers for the Load Balancer on page 67 to
configure the PathFinder servers to function with a load balancer.
Related links
Scalability, High Availability and Load Balancing with PathFinder on page 59
when deploying the load balancer. For more information on standard F5 BIG-IP LTM
deployments, see the F5 documentation.
Verify that you have all the IP addresses of the PathFinder servers and the F5 (including its default
gateway, also known as its router). This is required to configure the load balancer.
Procedure
1. Access the F5 web interface.
2. Set up a virtual LAN (VLAN) for all PathFinder servers, as described in the F5
documentation.
A VLAN is similar to a physical LAN, but is used to group devices based on specific
attributes rather than a common location. Any data packets passing in and out of the VLAN
must be done via the F5's router (also known as the default gateway).
3. Add a Self IP for the VLAN you created, as described in the F5 documentation.
This IP address represents the range of IP addresses of the servers in the cluster. The load
balancer uses this IP address to determine which VLAN to forward the request.
4. Add a Node for each PathFinder server and the default gateway, as described in the F5
documentation.
The VLAN consists of nodes, where each node is a physical server.
5. Add a pool that contains all PathFinder servers in your deployment, as described in the F5
documentation. A pool is the term used by F5 to refer to a cluster of servers.
Configure the PathFinder server pool settings, as described in the F5 documentation.
The settings described below are specific to PathFinder server and may differ from a typical
F5 deployment:
Field Description
Configuration From the list, select Advanced.
Name Enter a name to identify this as the PathFinder server cluster, such
as PathFinder_Pool.
Health Monitors Select the gateway_icmp health monitor.
gateway_icmp is a pre-configured health monitor available by
default on the F5. Health monitors check devices to verify that they
are running, at specified intervals. For more information, see the F5
documentation.
Load Balancing Method From the list, select the method the load balancer uses for
distributing traffic between servers in this pool. The default method
is Round Robin, which directs each endpoint service request to
another PathFinder server, in turn.
Table continues
Field Description
Node List Select this option. A list of the PathFinder servers you added as
nodes appears.
Service Port Enter 0 to indicate that this field should not be used. The PathFinder
server's service port is configured on the firewall.
New Members Add each PathFinder server.
6. Add a pool that contains the default gateway, as described in the F5 documentation.
The pool may include more than one gateway, depending on your network setup.
The settings described below are specific to PathFinder server and may differ from a typical
F5 deployment:
Field Description
Configuration From the list, select Advanced.
Name Enter a name to identify this as the gateway cluster, such as
Gateway_Pool.
Health Monitors Select the gateway_icmp health monitor.
gateway_icmp is a pre-configured health monitor available by
default on the F5. Health monitors check devices to verify that they
are running, at specified intervals. For more information, see the F5
documentation.
New Address Select this option and enter the IP address of the F5's default
gateway (router).
Service Port Enter 0 to indicate that this field should not be used. The PathFinder
server's service port is configured on the firewall.
New Members Add the F5's default gateway as a member to this pool.
7. (Optional) After configuring the pools, we recommend verifying that the servers are running
by checking the list of members in each pool, as described in the F5 documentation.
8. Set up the default gateway as the router for the PathFinder server pool, as described in the
F5 documentation.
9. Add a virtual server, which includes all PathFinder servers in your deployment, as described
in the F5 documentation.
10. Configure the virtual server, as described in the F5 documentation.
The settings described below are specific to PathFinder server and may differ from a typical
F5 deployment:
Field Description
Default Pool From the list, select the PathFinder server pool you
created.
Default Persistence Profile From the list, select source_address. This instructs the
load balancer to send all session requests from the same
source IP to the same PathFinder server.
11. Configure static network address translation (SNAT) to translate the source IP from an actual
PathFinder server to a virtual public IP, as described in the F5 documentation. This is used
to convert a request to the virtual cluster IP into the real IP of one of the servers in the
cluster.
The settings described below are specific to PathFinder server and may differ from a typical
F5 deployment:
Field Description
Name Enter a name to identify this as the NAT for the PathFinder
server cluster, such as PathFinder_SNAT.
Translation Select IP address from the list and enter the IP address of the
PathFinder virtual server you just created.
Origin Select Address List from the list.
Type Select Host.
Address Add the IP addresses of the PathFinder servers in the pool.
12. To ensure communication is possible with the PathFinders, add the IP address and service
port of the PathFinder virtual server to the organization's firewalls.
13. Continue with Configuring PathFinder servers for the Load Balancer on page 67 to
configure the PathFinder servers to function with a load balancer.
Related links
Scalability, High Availability and Load Balancing with PathFinder on page 59
The following load balancers are certified for the current version of PathFinder server:
Radware AppDirector
F5 BIG-IP Load Traffic Manager (LTM)
PathFinder server redundancy can also be managed using other third-party load balancers.
For more information, see:
Scalability, High Availability and Load Balancing with PathFinder on page 59 for an overview of
scalability and load balancing with PathFinder servers.
Important:
The load balancer maps the traffic based on the source IP address. All endpoint requests
that originate from the same IP address are always mapped to the same PathFinder
server.
The load balancer's documentation.
Before you begin
Verify the default gateway of each PathFinder server is set to the native IP address of the load
balancer. For more information on setting the device's default gateway, see Configuring the IP
Addresses of the PathFinder server on page 35.
Procedure
1. Access the PathFinder server Administrator web interface.
2. Select Settings > General > NAT Support.
Field Description
NAT Support Enable NAT Support to use the virtual IP address (VIP) of
the cluster when communicating with external endpoints,
instead of the IP address of this PathFinder server.
This is mandatory when deploying PathFinder server with a
load balancer.
Address Enter the VIP of the PathFinder server's cluster, as follows:
If you have a single NIC configuration, or a dual NIC
configuration with the external NIC secured behind a
firewall, enter the public IP address with NAT translation to
the cluster's VIP.
If you have a dual NIC configuration with the external NIC
directly in the public network, set the NAT address to the
Table continues
Field Description
VIP of the cluster and deploy your load balancer in the
public network.
Important:
In the firewall/NAT device, verify that the NAT address
is mapped to the private VIP address of the PathFinder
server cluster's external NIC.
Port If required, change the Scopia PathFinder client port
number which is set to 3089 by default.
4. Select Save.
5. For each PathFinder server in the cluster, perform the necessary configurations described in
Performing the Initial Configuration of the PathFinder server on page 35.
Important:
All PathFinder servers in the cluster must be configured identically, apart from their
native IP addresses. For more information about configuring the IP address, see
Configuring the IP Addresses of the PathFinder server on page 35.
Related links
Scalability, High Availability and Load Balancing with PathFinder on page 59
This section details to the ongoing administrator tasks required to maintain your video network:
Related links
Updating, Backing Up and Restoring the PathFinder server on page 70
Filtering and Monitoring Events in PathFinder server on page 76
Managing Logs on page 80
Capturing Network Traces for Troubleshooting on page 83
Viewing PathFinder Hardware and License Information on page 85
Important:
You can restore the operating system of the PathFinder server to any version of the server as
long as you use the Intel server's backup packages.
For details about updating, backing up, restoring the PathFinder server application and its operating
system, see the following topics:
Related links
Performing Maintenance Procedures on page 70
Upgrading the PathFinder server on page 71
Backing Up the Configuration Settings on page 73
Restoring the Configuration Settings on page 75
Procedure
1. Run WinSCP to transfer the file.
2. Configure the connection to your PathFinder server in the WinSCP Login dialog box, as
follows:
Field Description
Host name Enter the IP address of the PathFinder server.
User name Enter the username to access PathFinder server. This is always
uadmin.
Password Enter the password. The default is admin. If you modified the
default password, enter the new value here.
File protocol Select SFTP to enable the SSH File Transfer Protocol capability.
3. Select Login.
4. Drag the new .pkg update file to the /updates folder in the PathFinder server and select
Copy when prompted (Figure 45: Screen showing the application upgrade file in the
PathFinder server on page 72).
Figure 45: Screen showing the application upgrade file in the PathFinder server
5. Run PuTTY to connect to the PathFinder server.
6. Configure the connection to the PathFinder server in the Session tab of the PuTTY
Configuration dialog box, as follows:
Field Description
Host Name (or IP address) Enter the IP address of the PathFinder server.
SSH Verify the Secure Shell protocol is enabled.
Figure 47: Screen showing the installation of the PathFinder server application update
d. If this is a major update of the PathFinder server application, enter the license key
(Figure 47: Screen showing the installation of the PathFinder server application
update on page 73). Otherwise, press Enter to use the current license key.
The PathFinder server reboots automatically after each installation procedure.
Related links
Updating, Backing Up and Restoring the PathFinder server on page 70
Procedure
1. Run PuTTY to connect to the PathFinder server.
2. Configure the connection to the PathFinder server in the Session tab of the PuTTY
Configuration dialog box, as follows:
Field Description
Host Name (or IP address) Enter the IP address of the PathFinder server.
SSH Verify the Secure Shell protocol is enabled.
Depending on the backup you selected, the configuration is saved to a file that has the
format <sysconfig_yyyy-mm-dd-hh-mm-ss.tgz> or <pfsconfig_yyyy-mm-dd-hh-mm-
ss.tgz> (Figure 49: Screen showing the backing up the PathFinder server application
configuration on page 74). The file is located in the server folder /updates/bckp.
Figure 49: Screen showing the backing up the PathFinder server application
configuration
c. Press Enter to return to the Main menu.
d. Enter Q to exit the session.
Related links
Updating, Backing Up and Restoring the PathFinder server on page 70
Field Description
Host Name (or IP address) Enter the IP address of the PathFinder server.
SSH Verify the Secure Shell protocol is enabled.
c. Enter the item number corresponding to the configuration restore (Figure 51: Screen
showing how to restore the PathFinder server application configuration on page 76).
Figure 51: Screen showing how to restore the PathFinder server application configuration
d. Press Enter. After the configuration is restored, the display returns to the Backup/
Restore menu.
Related links
Updating, Backing Up and Restoring the PathFinder server on page 70
Procedure
1. Access the PathFinder server Administrator web interface.
2. To pass events and messages to a management server, enable the Third Party
Management API field in the General tab.
The management server uses the dedicated username whose role is Collaborator,
displayed in the Users tab. The default username is Collab with password balloC.
Field Description
Power Up The PathFinder server went online after an automatic or manual restart of
the software. PathFinder caches this message until the management
server is properly connected and then sends it.
Power Down The PathFinder server went offline. Possible causes include: an orderly
shutdown followed by an automatic restart, or a configuration change
prompting you to select Restart in the General tab.
Endpoint Registered The specified remote endpoint successfully registered in the PathFinder
server so it can route calls from and to this endpoint. The event includes
the endpoint's name, IP address, date and time.
Endpoint An endpoint is no longer registered in the PathFinder server.
Unregistered
GK Changed The PathFinder server has registered to a new gatekeeper.
This is a critical event, therefore we recommend not removing this from
the list of displayed events. An administrator must always manually
change a gatekeeper. If the PathFinder server starts routing calls
incorrectly, look for this event as a possible cause.
High Level CPU Meter The PathFinder server has reached the maximum CPU usage, set in the
Threshold field in the same row (Figure 54: Event types on page 78).
Client Connected A Scopia PathFinder client established a connection to the PathFinder
server. The event includes the client's name, IP address, date and time.
Client Disconnected A Scopia PathFinder client has disconnected from the PathFinder server.
Table continues
Field Description
Port Utilization The PathFinder server has reached the maximum percentage of
simultaneous calls, set in the Threshold field in the same row.
The default license supports 10 concurrent calls. You need to purchase a
license to increase the threshold. Depending on the license you purchase,
you can reach a maximum capacity of 100 concurrent calls.
If you see this event when the threshold is at maximum, consider raising
capacity by purchasing additional PathFinder servers and deploying them
with a load balancer.
Registration The PathFinder server has reached the maximum percentage of
Utilization registration capacity, set in the Threshold field in the same row.
The default license supports 60 registered endpoints. You need to
purchase a license to increase the threshold. Depending on the license
you purchase, you can reach a maximum capacity of 600 registered
endpoints.
User logged in A user (for example, an administrator) successfully logged into the
PathFinder server web interface.
User logged out A user successfully logged out from the PathFinder server web interface.
Authentication A user failed to log into the PathFinder server web interface.
Failure
License Update Displays details of the PathFinder server new license (for example,
number of concurrent calls and number of registered endpoints).
Link Down PathFinder's external NIC cannot see the network. Possible causes
include a bad cable, disabled network port, or network failure.
5. Where available, set the Threshold value from the dropdown list. For example, when the
server's CPU load exceeds the 85% you configured in High Level CPU Meter, the alert
remains active until the usage decreases below the configured value.
The server sends clearing messages to Scopia Management for the High Level CPU
Meter, Port Utilization, or Registration Utilization events.
6. Select Save.
7. Access the PathFinder server web interface and monitor the trap messages in the Event
Logs tab (Figure 55: Trap messages in PathFinder server on page 79).
Managing Logs
Logs are important for troubleshooting. This section describes the log managing provided in the
Avaya Scopia PathFinder server:
Related links
Performing Maintenance Procedures on page 70
Configuring the Alert Level and Size of Logs on page 80
Retrieving Application and Operating System Logs on page 81
5. Select the log file size in the Size Limit field. The size of an individual log file is configured to
500KB by default. The maximum size of an individual log file is 10000KB.
6. Define how many log files are created in the Number of Log Files field. By default the
maximum number of log files that are kept on the PathFinder server is 300. The maximum
number of log files is 1000. When the maximum number is reached and a new log file is
created, it replaces the oldest log file.
Related links
Managing Logs on page 80
Figure 57: Accessing the screen for generating the Customer Support Package
3. To collect today's log, select Capture last day.
Field Description
Host name Enter the IP address of the PathFinder server.
User name Enter the username to access PathFinder server. This is always
uadmin.
Password Enter the password. The default is admin. If you modified the
default password, enter the new value here.
File protocol Select SFTP to enable the SSH File Transfer Protocol capability.
9. Select Login.
10. Drag the log file from the /updates/logs folder to the relevant folder on your computer The
PathFinder server names logs as pfcspkg_<selected_dates>.zip by default.
11. Close WinSCP and confirm ending the session to save the changes.
Related links
Managing Logs on page 80
You can retrieve the network captures as files and use them to troubleshoot problems.
Before you begin
Verify you have the IP address of the PathFinder server.
You need software tools to perform this procedure. We recommend using these freeware
applications:
- PuTTY, an SSH client, to connect to the PathFinder server administration console to perform
the procedure in this section. You can download this application from http://
www.chiark.greenend.org.uk/~sgtatham/putty/
- WinSCP, a Secure FTP client, to save the file(s) to the desired location. You can download
this application from http://winscp.net/eng/download.php
Procedure
1. Run PuTTY to connect to the PathFinder server.
2. Configure the connection to the PathFinder server in the Session tab of the PuTTY
Configuration dialog box, as follows:
Field Description
Host Name (or IP address) Enter the IP address of the PathFinder server.
SSH Verify the Secure Shell protocol is enabled.
generates a .tgz file which compresses all these .pcap files to a single package (Figure
63: Downloading the network capture files to your computer on page 85). As each file
is dated and time stamped, you can download and review only the files which captured
issues you are interested in troubleshooting.
d. Press Enter to return to the Main Menu.
e. Press Q to exit the session.
4. Run WinSCP to transfer the file.
5. Configure the connection to your PathFinder server in the WinSCP Login dialog box, as
follows:
Field Description
Host name Enter the IP address of the PathFinder server.
User name Enter the username to access PathFinder server. This is always
uadmin.
Password Enter the password. The default is admin. If you modified the
default password, enter the new value here.
File protocol Select SFTP to enable the SSH File Transfer Protocol capability.
6. Select Login.
7. Drag the relevant network capture file from the /updates/nw_traces folder to the relevant
folder on your computer (Figure 63: Downloading the network capture files to your
computer on page 85).
Procedure
1. Access the PathFinder server Administrator web interface.
2. Select the About tab. The screen displays system information.
Related links
Performing Maintenance Procedures on page 70
2CIF 2CIF describes a video resolution of 704 x 288 pixels (PAL) or 704 x 240
(NTSC). It is double the width of CIF, and is often found in CCTV products.
2SIF 2SIF describes a video resolution of 704 x 240 pixels (NTSC) or 704 x 288
(PAL). This is often adopted in IP security cameras.
4CIF 4CIF describes a video resolution of 704 x 576 pixels (PAL) or 704 x 480
(NTSC). It is four times the resolution of CIF and is most widespread as the
standard analog TV resolution.
4SIF 4SIF describes a video resolution of 704 x 480 pixels (NTSC) or 704 x 576
(PAL). This is often adopted in IP security cameras.
AAC AAC is an audio codec which compresses sound but with better results
than MP3.
AGC (Automatic Gain Automatic Gain Control (AGC) smooths audio signals through
Control) normalization, by lowering sounds which are too strong and strengthening
sounds which are too weak. This is relevant with microphones situated at
some distance from the speaker, like room systems. The result is a more
consistent audio signal within the required range of volume.
Auto-Attendant Auto-Attendant, also known as video IVR, offers quick access to meetings
hosted on MCUs, via a set of visual menus. Participants can select menu
options using standard DTMF tones (numeric keypad). Auto-Attendant
works with both H.323 and SIP endpoints.
Balanced A balanced microphone uses a cable that is built to reduce noise and
Microphone interference even when the cable is long. This reduces audio disruptions
resulting from surrounding electromagnetic interference.
BFCP (Binary Floor BFCP is a protocol which coordinates shared videoconference features in
Control Protocol) SIP calls, often used by one participant at a time. For example, when
sharing content to others in the meeting, one participant is designated as
the presenter, and is granted the floor for presenting. All endpoints must be
aware that the floor was granted to that participant and react appropriately.
Bitrate Bitrate is the speed of data flow. Higher video resolutions require higher
bitrates to ensure the video is constantly updated, thereby maintaining
smooth motion. If you lower the bitrate, you lower the quality of the video. In
some cases, you can select a lower bitrate without noticing a significant
drop in video quality; for example during a presentation or when a lecturer
is speaking and there is very little motion. In video recordings, the bitrate
determines the file size for each minute of recording. Bitrate is often
measured in kilobits per second (kbps).
Content Slider The Scopia Content Slider stores the data already presented in the
videoconference and makes it available for participants to view during the
meeting.
Control Control, or media control, sets up and manages the media of a call (its
audio, video and data). Control messages include checking compatibility
between endpoints, negotiating video and audio codecs, and other
parameters like resolution, bitrate and frame rate. Control is communicated
via H.245 in H.323 endpoints, or by SDP in SIP endpoints. Control occurs
within the framework of an established call, after signaling.
Dial Plan A dial plan defines a way to route a call and to determine its characteristics.
In traditional telephone networks, prefixes often denote geographic
locations. In videoconferencing deployments, prefixes are also used to
define the type and quality of a call. For example, dial 8 before a number for
a lower bandwidth call, or 6 for an audio-only call, or 5 to route the call to a
different branch.
Dial Prefix A dial prefix is a number added at the beginning of a dial string to route it to
the correct destination, or to determine the type of call. Dial prefixes are
defined in the organization's dial plan. For example, dial 9 for an outside
line, or dial 6 for an audio only call.
DNS Server A DNS server is responsible for resolving domain names in your network by
translating them into IP addresses.
Dual Video Dual video is the transmitting of two video streams during a
videoconference, one with the live video while the other is a shared data
stream, like a presentation.
Dynamic Video The dynamic video layout is a meeting layout that switches dynamically to
Layout include the maximum number of participants it can display on the screen
(up to 9 on the XT Series, or up to 28 on Scopia Elite MCU). The largest
image always shows the active speaker.
FECC Far End Camera Control (FECC) is a feature of endpoint cameras, where
the camera can be controlled remotely by another endpoint in the call.
Frames Per Second Frames Per Second (fps), also known as the frame rate, is a key measure
in video quality, describing the number of image updates per second. The
average human eye can register up to 50 frames per second. The higher
the frame rate, the smoother the video.
Full HD Full HD, or Full High Definition, also known as 1080p, describes a video
resolution of 1920 x 1080 pixels.
Full screen Video The full screen view shows one video image. Typically, it displays the
Layout remote presentation, or, if there is no presentation, it displays the other
meeting participant(s).
Gatekeeper A gatekeeper routes audio and video H.323 calls by resolving dial strings
(H.323 alias or URI) into the IP address of an endpoint, and handles the
initial connection of calls. Gatekeepers also implement the dial plan of an
organization by routing H.323 calls depending on their dial prefixes.
Scopia Management includes a built-in Avaya Scopia Gatekeeper, while
ECS is a standalone gatekeeper.
GLAN GLAN, or gigabit LAN, is the name of the network port on the XT Series. It
is used on the XT Series to identify a 10/100/1000MBit ethernet port.
H.225 H.225 is part of the set of H.323 protocols. It defines the messages and
procedures used by gatekeepers to set up calls.
H.235 H.235 is the protocol used to authenticate trusted H.323 endpoints and
encrypt the media stream during meetings.
H.239 H.239 is a widespread protocol used with H.323 endpoints, to define the
additional media channel for data sharing (like presentations) alongside the
videoconference, and ensures only one presenter at a time.
H.243 H.243 is the protocol used with H.323 endpoints enabling them to remotely
manage a videoconference.
H.245 H.245 is the protocol used to negotiate call parameters between endpoints,
and can control a remote endpoint from your local endpoint. It is part of the
H.323 set of protocols.
H.261 H.261 is an older protocol used to compress CIF and QCIF video
resolutions. This protocol is not supported by the XT Series.
H.264 H.264 is a widespread protocol used with SIP and H.323 endpoints, which
defines video compression. Compression algorithms include 4x4 transforms
and a basic motion comparison algorithm called P-slices. There are several
profiles within H.264. The default profile is the H.264 Baseline Profile, but
H.264 High Profile uses more sophisticated compression techniques.
H.264 High Profile H.264 High Profile is a standard for compressing video by up to 25% over
the H.264 Baseline Profile, enabling high definition calls to be held over
lower call speeds. It requires both sides of the transmission (sending and
receiving endpoints) to support this protocol. H.264 High Profile uses
compression algorithms like:
CABAC compression (Context-Based Adaptive Binary Arithmetic
Coding)
8x8 transforms which more effectively compress images containing
areas of high correlation
These compression algorithms demand higher computation requirements,
which are offered with the dedicated hardware available in Scopia
Solution components. Using H.264 High Profile in videoconferencing
requires that both the sender and receiver's endpoints support it. This is
different from SVC which is an adaptive technology working to improve
quality even when only one side supports the standard.
H.350 H.350 is the protocol used to enhance LDAP user databases to add video
endpoint information for users and groups.
High Availability High availability is a state where you ensure better service and less
downtime by deploying additional servers. There are several strategies for
achieving high availability, including deployment of redundant servers
managed by load balancing systems.
HTTPS HTTPS is the secured version of the standard web browser protocol HTTP.
It secures communication between a web browser and a web server
through authentication of the web site and encrypting communication
between them. For example, you can use HTTPS to secure web browser
access to the web interface of many Scopia Solution products.
KBps Kilobytes per second (KBps) measures the bitrate in kilobytes per second,
not kilobits, by dividing the number of kilobits by eight. Bitrate is normally
quoted as kilobits per second (kbps) and then converted to kilobytes per
second (KBps). Bitrate measures the throughput of data communication
between two devices.
kbps Kilobits per second (kbps) is the standard unit to measure bitrate,
measuring the throughput of data communication between two devices.
Since this counts the number of individual bits (ones or zeros), you must
divide by eight to calculate the number of kilobytes per second (KBps).
Lecture Mode Scopia Desktop's lecture mode allows the participant defined as the
lecturer to see all the participants, while they see only the lecturer. All
participants are muted except the lecturer, unless a participant asks
permission to speak and is unmuted by the lecturer. This mode is tailored
for distance learning, but you can also use it for other purposes like when
an executive addresses employees during company-wide gatherings.
Load balancer A load balancer groups together a set (or cluster) of servers to give them a
single IP address, known as a virtual IP address. It distributes client service
requests amongst a group of servers. It distributes loads according to
different criteria such as bandwidth, CPU usage, or cyclic (round robin).
Load balancers are also known as application delivery controllers (ADC).
MBps Megabytes per second (MBps) is a unit of measure for the bitrate. The
bitrate is normally quoted as kilobits per second (kbps) and then converted
by dividing it by eight to reach the number of kilobytes per second (KBps)
and then by a further 1000 to calculate the MBps.
Media Media refers to the live audio, video and shared data streams sent during a
call. Presentation and Far end camera control (FECC) are examples of
information carried on the data stream. Media is transmitted via the RTP
and RTCP protocols in both SIP and H.323 calls. The parallel data stream
of both live video and presentation, is known as dual video.
Meeting Type Meeting types (also known as MCU services) are meeting templates which
determine the core characteristics of a meeting. For example, they
determine if the meeting is audio only or audio and video, they determine
the default video layout, the type of encryption, PIN protection and many
other features. You can invoke a meeting type by dialing its prefix in front of
the meeting ID. Meeting types are created and stored in the MCU, with
additional properties in Scopia Management.
MTU The MTU, or Maximum Transmission Unit, is the maximum size of data
packets sent around your network. This value must remain consistent for all
network components, including servers like the MCU and Scopia Desktop
server, endpoints like XT Series and other network devices like LDAP
servers and network routers.
Packet Loss Packet loss occurs when some of the data transmitted from one endpoint is
not received by the other endpoint. This can be caused by narrow
bandwidth connections or unreliable signal reception on wireless networks.
PaP Video Layout The PaP (Picture and Picture) view shows up to three images of the same
size.
Phantom Power Microphones which use phantom power draw their electrical power from the
same cable as the audio signal. For example, if your microphone is
powered by a single cable, it serves both to power the microphone and
transmit the audio data. Microphones which have two cables, one for sound
and a separate power cable, do not use phantom power.
PiP Video Layout The PiP (Picture In Picture) view shows a video image in the main screen,
with an additional smaller image overlapping in the corner. Typically, a
remote presentation is displayed in the main part of the screen, and the
remote video is in the small image. If the remote endpoint does not show
any content, the display shows the remote video in the main part of the
screen, and the local presentation in the small image.
Point-to-Point Point-to-point is a feature where only two endpoints communicate with each
other without using MCU resources.
PoP Video Layout The PoP (Picture out Picture) view shows up to three images of different
size, presented side by side, where the image on the left is larger than the
two smaller images on the right.
PTZ Camera A PTZ camera can pan to swivel horizontally, tilt to move vertically, and
optically zoom to devote all the camera's pixels to one area of the image.
For example, the XT Standard Camera is a PTZ camera with its own power
supply and remote control, and uses powerful lenses to achieve superb
visual quality. In contrast, fixed cameras like webcams only offer digital
PTZ, where the zoom crops the camera image, displaying only a portion of
the original, resulting in fewer pixels of the zoomed image, which effectively
lowers the resolution. Fixed cameras also offer digital pan and tilt only after
zooming, where you can pan up to the width or length of the original
camera image.
Q.931 Q.931 is a telephony protocol used to start and end the connection in H.323
calls.
QCIF QCIF, or Quarter CIF, defines a video resolution of 176 144 pixels (PAL)
or 176 x 120 (NTSC). It is often used in older mobile handsets (3G-324M)
limited by screen resolution and processing power.
Quality of Service Quality of Service (QoS) determines the priorities of different types of
(QoS) network traffic (audio, video and control/signaling), so in poor network
conditions, prioritized traffic is still fully transmitted.
Registrar A SIP Registrar manages the SIP domain by requiring that all SIP devices
register their IP addresses with it. For example, once a SIP endpoint
registers its IP address with the Registrar, it can place or receive calls with
other registered endpoints.
Restricted Mode Restricted mode is used for ISDN endpoints only, when the PBX and line
uses a restricted form of communication, reserving the top 8k of each
packet for control data only. If enabled, the bandwidth values on these lines
are in multiples of 56kbps, instead of multiples of 64kbps.
RTCP Real-time Control Transport Protocol, used alongside RTP for sending
statistical information about the media sent over RTP.
protocols today, including H.323, SIP and the streaming control protocol
known as RTSP. The secured version of RTP is SRTP.
Sampling Rate The sampling rate is a measure of the accuracy of the audio when it is
digitized. To convert analog audio to digital, it must collect or sample the
audio at specific intervals. As the rate of sampling increases, it raises audio
quality.
SBC A Session Border Controller (SBC) is a relay device between two different
networks. It can be used in firewall/NAT traversal, protocol translations and
load balancing.
Scalability Scalability describes the ability to increase the capacity of a network device
by adding another identical device (one or more) to your existing
deployment. In contrast, a non-scalable solution would require replacing
existing components to increase capacity.
Service Also known as MCU service. See Meeting Type on page 94.
SIF SIF defines a video resolution of 352 x 240 pixels (NTSC) or 352 x 288
(PAL). This is often used in security cameras.
Signaling Signaling, also known as call control, sets up, manages and ends a
connection or call. These messages include the authorization to make the
call, checking bandwidth, resolving endpoint addresses, and routing the call
through different servers. Signaling is transmitted via the H.225.0/Q.931
and H.225.0/RAS protocols in H.323 calls, or by the SIP headers in SIP
calls. Signaling occurs before the control aspect of call setup.
Single Sign On Single Sign On (SSO) automatically uses your network login and password
to access different enterprise systems. Using SSO, you do not need to
separately login to each system or service in your organization.
SIP Server A SIP server is a network device communicating via the SIP protocol.
SRTP Secure Real-time Transport Protocol (SRTP) adds security to the standard
RTP protocol, which is used to send media (video and audio) between
devices in SIP calls. It offers security with encryption, authentication and
message integrity. The encryption uses a symmetric key generated at the
start of the call, and being symmetric, the same key locks and unlocks the
data. So to secure transmission of the symmetric key, it is sent safely
during call setup using TLS.
STUN A STUN server enables you to directly dial an endpoint behind a NAT or
firewall by giving that computers public internet address.
SVC SVC extends the H.264 codec standard to dramatically increase error
resiliency and video quality without the need for higher bandwidth. It is
especially effective over networks with high packet loss (like wireless
networks) which deliver low quality video. It splits the video stream into
layers, comprising a small base layer and then additional layers on top
which enhance resolution, frame rate and quality. Each additional layer is
only transmitted when bandwidth permits. This allows for a steady video
transmission when available bandwidth varies, providing better quality
when the bandwidth is high, and adequate quality when available
bandwidth is poor.
Switched video Switching is the process of redirecting video as-is without transcoding, so
you see only one endpoint's image at a time, usually the active speaker,
without any video layouts or continuous presence (CP). Using video
switching increases the port capacity of the Scopia Elite MCU only by four
times.
Important:
Use switched video only when all endpoints participating in the
videoconference support the same resolution. If a network experiences
high packet loss, switched video might not be displayed properly for all
endpoints in the videoconference.
Telepresence - Dual Dual row telepresence rooms are large telepresence rooms with two rows
row telepresence of tables that can host up to 18 participants.
room
URI URI is an address format used to locate a device on a network, where the
address consists of the endpoint's name or number, followed by the domain
name of the server to which the endpoint is registered. For
example,<endpoint name>@<server_domain_name>. When dialing URI
between organizations, the server might often be the Avaya Scopia
PathFinder server of the organization.
User profile A user profile is a set of capabilities or parameter values which can be
assigned to a user. This includes available meeting types (services),
access to Scopia Desktop and Scopia Mobile functionality, and allowed
bandwidth for calls.
Video Fast Update Video Fast Update (VFU) is a request for a refreshed video frame, sent
(VFU) when the received video is corrupted by packet loss. In response to a VFU
request, the broadcasting endpoint sends a new intra-frame to serve as the
baseline for the ongoing video stream.
Video Layout A video layout is the arrangement of participant images as they appear on
the monitor in a videoconference. If the meeting includes a presentation, a
layout can also refer to the arrangement of the presentation image together
with the meeting participants.
Virtual Room A virtual room in Scopia Desktop and Scopia Mobile offers a virtual
meeting place for instant or scheduled videoconferences. An administrator
can assign a virtual room to each member of the organization. Users can
April 2016 Avaya Scopia PathFinder Firewall Traversal Deployment Guide 100
Comments on this document? infodev@avaya.com
VISCA Cable
send invitations to each other via a web link which brings you directly into
their virtual room. Virtual meeting rooms are also dialed like phone
extension numbers, where a users virtual room number is often based on
that persons phone extension number. You can personalize your virtual
room with PIN numbers, custom welcome slides and so on. External
participants can download Scopia Desktop or Scopia Mobile free to
access a registered user's virtual room and participate in a
videoconference.
VISCA Cable A crossed VISCA cable connects two PTZ cameras to enable you to use
the same remote control on both.
Waiting Room A waiting room is a holding place for participants waiting for the host or
moderator to join the meeting. While waiting, participants see a static image
with the name of the owner's virtual room, with an optional audio message
periodically saying the meeting will start when the host arrives.
Zone Gatekeepers like Avaya Scopia ECS Gatekeeper split endpoints into
zones, where a group of endpoints in a zone are registered to a
gatekeeper. Often a zone is assigned a dial prefix, and usually corresponds
to a physical location like an organization's department or branch.
April 2016 Avaya Scopia PathFinder Firewall Traversal Deployment Guide 101
Comments on this document? infodev@avaya.com