Deployment Guide for Avaya Equinox H.323 Edge

Deployment Guide for Avaya Equinox
H.323 Edge
Release 9.1
Issue 1
December 2017
© 2014-2017, Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves
the right to make changes and corrections to the information in this
document without the obligation to notify any person or organization
of such changes.
Documentation disclaimer
“Documentation” means information published in varying mediums
which may include product information, operating instructions and
performance specifications that are generally made available to users
of products. Documentation does not include marketing materials.
Avaya shall not be responsible for any modifications, additions, or
deletions to the original published version of Documentation unless
such modifications, additions, or deletions were performed by or on
the express behalf of Avaya. End User agrees to indemnify and hold
harmless Avaya, Avaya's agents, servants and employees against all
claims, lawsuits, demands and judgments arising out of, or in
connection with, subsequent modifications, additions or deletions to
this documentation, to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked
websites referenced within this site or Documentation provided by
Avaya. Avaya is not responsible for the accuracy of any information,
statement or content provided on these sites and does not
necessarily endorse the products, services, or information described
or offered within them. Avaya does not guarantee that these links will
work all the time and has no control over the availability of the linked
pages.
Warranty
Avaya provides a limited warranty on Avaya hardware and software.
Refer to your sales agreement to establish the terms of the limited
warranty. In addition, Avaya’s standard warranty language, as well as
information regarding support for this product while under warranty is
available to Avaya customers and other parties through the Avaya
Support website: https://support.avaya.com/helpcenter/
getGenericDetails?detailId=C20091120112456651010 under the link
“Warranty & Product Lifecycle” or such successor site as designated
by Avaya. Please note that if You acquired the product(s) from an
authorized Avaya Channel Partner outside of the United States and
Canada, the warranty is provided to You by said Avaya Channel
Partner and not by Avaya.
“Hosted Service” means an Avaya hosted service subscription that
You acquire from either Avaya or an authorized Avaya Channel
Partner (as applicable) and which is described further in Hosted SAS
or other service description documentation regarding the applicable
hosted service. If You purchase a Hosted Service subscription, the
foregoing limited warranty may not apply but You may be entitled to
support services in connection with the Hosted Service as described
further in your service description documents for the applicable
Hosted Service. Contact Avaya or Avaya Channel Partner (as
applicable) for more information.
Hosted Service
THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA
HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER
THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH
SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF
YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
MUST NOT ACCESS OR USE THE HOSTED SERVICE OR
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
SERVICE.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,
UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya
Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY
AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,
USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED
FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA
CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.
UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,
AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE
WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA
AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA
RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
AND ANYONE ELSE USING OR SELLING THE SOFTWARE
WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
YOU ARE INSTALLING, DOWNLOADING OR USING THE
SOFTWARE (HEREINAFTER REFERRED TO
INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
THESE TERMS AND CONDITIONS AND CREATE A BINDING
CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).
Avaya grants You a license within the scope of the license types
described below, with the exception of Heritage Nortel Software, for
which the scope of the license is detailed below. Where the order
documentation does not expressly identify a license type, the
applicable license will be a Designated System License as set forth
below in the Designated System(s) License (DS) section as
applicable. The applicable number of licenses and units of capacity
for which the license is granted will be one (1), unless a different
number of licenses or units of capacity is specified in the
documentation or other materials available to You. “Software” means
computer programs in object code, provided by Avaya or an Avaya
Channel Partner, whether as stand-alone products, pre-installed on
hardware products, and any upgrades, updates, patches, bug fixes,
or modified versions thereto. “Designated Processor” means a single
stand-alone computing device. “Server” means a set of Designated
Processors that hosts (physically or virtually) a software application
to be accessed by multiple users. “Instance” means a single copy of
the Software executing at a particular time: (i) on one physical
machine; or (ii) on one deployed software virtual machine (“VM”) or
similar deployment.
License type(s)
Designated System(s) License (DS). End User may install and use
each copy or an Instance of the Software only: 1) on a number of
Designated Processors up to the number indicated in the order; or 2)
up to the number of Instances of the Software as indicated in the
order, Documentation, or as authorized by Avaya in writing. Avaya
may require the Designated Processor(s) to be identified in the order
by type, serial number, feature key, Instance, location or other
specific designation, or to be provided by End User to Avaya through
electronic means established by Avaya specifically for this purpose.
Heritage Nortel Software
“Heritage Nortel Software” means the software that was acquired by
Avaya as part of its purchase of the Nortel Enterprise Solutions
Business in December 2009. The Heritage Nortel Software is the
software contained within the list of Heritage Nortel Products located
at https://support.avaya.com/LicenseInfo under the link “Heritage
Nortel Products” or such successor site as designated by Avaya. For
Heritage Nortel Software, Avaya grants Customer a license to use
Heritage Nortel Software provided hereunder solely to the extent of
the authorized activation or authorized usage level, solely for the
purpose specified in the Documentation, and solely as embedded in,
for execution on, or for communication with Avaya equipment.
Charges for Heritage Nortel Software may be based on extent of
activation or use authorized as specified in an order or invoice.
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, Hosted Service,
or hardware provided by Avaya. All content on this site, the
documentation, Hosted Service, and the product provided by Avaya
including the selection, arrangement and design of the content is
owned either by Avaya or its licensors and is protected by copyright
and other intellectual property laws including the sui generis rights
relating to the protection of databases. You may not modify, copy,
reproduce, republish, upload, post, transmit or distribute in any way
any content, in whole or in part, including any code and software
unless expressly authorized by Avaya. Unauthorized reproduction,
transmission, dissemination, storage, and or use without the express
written consent of Avaya can be a criminal, as well as a civil offense
under the applicable law.
Virtualization
The following applies if the product is deployed on a virtual machine.
Each product has its own ordering code and license types. Note,
unless otherwise stated, that each Instance of a product must be
separately licensed and ordered. For example, if the end user
customer or Avaya Channel Partner would like to install two
Instances of the same type of products, then two products of that
type must be ordered.
Third Party Components
“Third Party Components” mean certain software programs or
portions thereof included in the Software or Hosted Service may
contain software (including open source software) distributed under
third party agreements (“Third Party Components”), which contain
terms regarding the rights to use certain portions of the Software
(“Third Party Terms”). As required, information regarding distributed
Linux OS source code (for those products that have distributed Linux
OS source code) and identifying the copyright holders of the Third
Party Components and the Third Party Terms that apply is available
in the products, Documentation or on Avaya’s website at: https://
support.avaya.com/Copyright or such successor site as designated
by Avaya. The open source software license terms provided as Third
Party Terms are consistent with the license rights granted in these
Software License Terms, and may contain additional rights benefiting
You, such as modification and distribution of the open source
software. The Third Party Terms shall take precedence over these
Software License Terms, solely with respect to the applicable Third
Party Components to the extent that these Software License Terms
impose greater restrictions on You than the applicable Third Party
Terms.
The following applies only if the H.264 (AVC) codec is distributed with
the product. THIS PRODUCT IS LICENSED UNDER THE AVC
PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE
REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH
THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC
VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS
GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA,
L.L.C. SEE HTTP://WWW.MPEGLA.COM.
Service Provider
THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S
HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT
OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS
SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE
PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM
THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER’S
HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN
WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE
OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING
BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS,
THE AVAYA CHANNEL PARTNER IS REQUIRED TO
INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE
AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE,
DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER.
WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL
PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED
THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE
AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES
THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY
AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729
CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE
WWW.SIPRO.COM/CONTACT.HTML. THE H.264 (AVC) CODEC IS
LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR
THE PERSONAL USE OF A CONSUMER OR OTHER USES IN
WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE
VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC
VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED
BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR
WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO
PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION
FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE
OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://
WWW.MPEGLA.COM.
Compliance with Laws
You acknowledge and agree that it is Your responsibility for
complying with any applicable laws and regulations, including, but not
limited to laws and regulations related to call recording, data privacy,
intellectual property, trade secret, fraud, and music performance
rights, in the country or territory where the Avaya product is used.
Preventing Toll Fraud
“Toll Fraud” is the unauthorized use of your telecommunications
system by an unauthorized party (for example, a person who is not a
corporate employee, agent, subcontractor, or is not working on your
company's behalf). Be aware that there can be a risk of Toll Fraud
associated with your system and that, if Toll Fraud occurs, it can
result in substantial additional charges for your telecommunications
services.
Avaya Toll Fraud intervention
If You suspect that You are being victimized by Toll Fraud and You
need technical assistance or support, call Technical Service Center
Toll Fraud Intervention Hotline at +1-800-643-2353 for the United
States and Canada. For additional support telephone numbers, see
the Avaya Support website: https://support.avaya.com or such
successor site as designated by Avaya.
Security Vulnerabilities
Information about Avaya’s security support policies can be found in
the Security Policies and Support section of 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
Chapter 1: Introduction............................................................................................................ 8
Purpose.................................................................................................................................. 8
Prerequisites........................................................................................................................... 8
New in this release.................................................................................................................. 9
Chapter 2: Equinox H.323 Edge overview............................................................................ 10
Main features........................................................................................................................ 11
Technical specifications of Equinox H.323 Edge....................................................................... 12
Minimum requirements of the Equinox H.323 Edge virtual appliance OVA.................................. 13
Chapter 3: Preparing the Equinox H.323 Edge server Setup.............................................. 15
Planning the topology............................................................................................................ 15
Ports configuration................................................................................................................ 16
Chapter 4: Deploying the Equinox H.323 Edge virtual server............................................ 21
Equinox H.323 Edge virtual server deployment checklist.......................................................... 21
Downloading software from PLDS.......................................................................................... 21
Deploying the Equinox H.323 Edge virtual server..................................................................... 22
Starting the Equinox H.323 Edge virtual server........................................................................ 23
Configuring the virtual machine automatic startup settings........................................................ 24
Chapter 5: Initial administration of Equinox H.323 Edge.................................................... 25
Equinox H.323 Edge initial configuration checklist.................................................................... 25
Adding networks to Equinox H.323 Edge................................................................................. 26
Adding Equinox H.323 Edge in Equinox Management.............................................................. 27
Configuring IP separation in Equinox Management.................................................................. 28
Configuring Ports on the Equinox H.323 Edge server............................................................... 29
Configuring the TCP/UDP port range for H.323 Direct Public Access calls........................... 29
Configuring the TCP/UDP port range on the internal interface............................................. 30
Integrating the Equinox H.323 Edge server with Other Equinox Solution Components................ 31
Integrating Equinox H.323 Edge with H.323 Gatekeeper..................................................... 31
Integrating Equinox H.323 Edge with NAT......................................................................... 32
Configuring the NTP server.............................................................................................. 32
Enabling Internal Endpoints to Call External Endpoints............................................................. 33
Configuring access for calls to H.323 video endpoints........................................................ 33
URI-based dialing............................................................................................................ 34
Configuring URI-based dialing to external endpoints.......................................................... 35
Configuration field descriptions......................................................................................... 37
Add Neighbors field descriptions....................................................................................... 37
Configuring IP address-based dialing to external endpoints................................................ 38
Add IP Calls field descriptions.......................................................................................... 40
Secure connection with Equinox Management......................................................................... 41
Creating security certificates............................................................................................. 41
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
5
Contents
Generate CSR field descriptions....................................................................................... 42
Uploading security certificates.......................................................................................... 42
Securing the connection with Equinox Management using TLS........................................... 43
Getting the system ID to activate Equinox H.323 Edge............................................................. 44
Adding and updating licenses................................................................................................. 44
Configuring remote access..................................................................................................... 45
Access field descriptions........................................................................................................ 45
Configuring QoS for audio and video....................................................................................... 46
Creating an Equinox H.323 Edge server Cluster...................................................................... 47
Chapter 6: Equinox H.323 Edge Client configuration.......................................................... 50
Equinox H.323 Edge Client configuration checklist................................................................... 50
Installing the Avaya Equinox H.323 Edge Client On a Windows Platform................................... 51
Adding Equinox H.323 Edge Client user accounts to Equinox H.323 Edge................................. 52
Adding enterprise gatekeepers to Equinox H.323 Edge............................................................ 53
Authorizing Communication with the Equinox H.323 Edge server Via the Avaya Equinox H.323
Edge Client........................................................................................................................... 54
Configuring a Connection to an Equinox H.323 Edge server..................................................... 55
Getting the RAS port number to relay messages of enterprise gatekeepers............................... 58
Configuring an enterprise gatekeeper as a neighbor of the internal gatekeeper of Equinox
Management......................................................................................................................... 59
Configuring an enterprise gatekeeper as a neighbor of H.323 Gatekeeper................................. 60
Add Neighbors field descriptions............................................................................................. 61
Chapter 7: Optimization and scalability................................................................................ 62
Optimization and scalability with server clusters....................................................................... 62
Creating an Equinox H.323 Edge server Cluster................................................................ 62
Deleting an Equinox H.323 Edge server Cluster................................................................. 64
Optimization and scalability with hardware load balancers........................................................ 65
Workflow to Configure Equinox H.323 Edge for Redundancy.............................................. 67
Configuring the Radware AppDirector load balancer for Equinox H.323 Edge...................... 68
Configuring the F5 BIG-IP LTM load balancer for Equinox H.323 Edge................................ 70
Configuring settings for load balancers.............................................................................. 73
Chapter 8: Performing Maintenance Procedures................................................................ 75
Updating, Backing Up and Restoring the Equinox H.323 Edge server........................................ 75
Backing up the Equinox H.323 Edge server....................................................................... 76
Restoring the Equinox H.323 Edge server......................................................................... 76
Creating an automatic backup schedule for the Equinox H.323 Edge server ........................ 77
Filtering and Monitoring Events in Equinox H.323 Edge............................................................ 78
Managing Logs..................................................................................................................... 79
Configuring the log recording level.................................................................................... 79
Downloading Customer Support Package......................................................................... 80
Chapter 9: Resources............................................................................................................. 81
Documentation...................................................................................................................... 81
Finding documents on the Avaya Support website............................................................. 84
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
6
Contents
Training................................................................................................................................ 84
Support................................................................................................................................ 85
Using the Avaya InSite Knowledge Base........................................................................... 85
Glossary................................................................................................................................... 87
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
7
Chapter 1: Introduction
Purpose
This document contains Avaya Equinox H.323 Edge installation, configuration, initial
administration, and basic maintenance checklist and procedures.
This document is intended for people who install and configure a verified Equinox H.323 Edge
reference configuration at a customer site.
Prerequisites
Before deploying Equinox H.323 Edge, ensure that you have the following knowledge, skills, and
tools.
Knowledge
Basic knowledge of:
• Equinox H.323 Edge
• Avaya Equinox solution
• Avaya Equinox Management
• Video networks and components
• Firewalls
Skills
Skills about how to:
• Deploy video networking components using Equinox Management
• Configure and administer video networks
Tools
An administration computer with:
• Equinox Management
• vSphere Client
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
8
New in this release
New in this release
This Equinox H.323 Edge Release 9.1 includes the following enhancements:
• Change of the OS to Linux Red Hat Release 7.3
• Porting of the Equinox H.323 Edge application to Linux Red Hat Release 7.3
• Support for high availability and scalability using Equinox H.323 Edge server clusters without
third-party load balancers.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
9
Chapter 2: Equinox H.323 Edge overview
Avaya Equinox H.323 Edge provides a complete firewall and NAT traversal solution and support for
secure connectivity between enterprise networks and remote locations.
Note:
Equinox H.323 Edge is an optional component. Equinox H.323 Edge is required when you need
to connect remote H.323–based video conferencing endpoints to an Avaya Equinox solution
conference through firewalls.
Equinox H.323 Edge is part of the Avaya Equinox solution. Components of Avaya Equinox can be
combined to fit the existing network topology and video conferencing requirements of the enterprise.
Equinox H.323 Edge is an optional Avaya Equinox solution component which is deployed in Over
The Top and Team Engagement deployments. Equinox H.323 Edge is deployed in network DMZs
when enterprises need H.323–based calls to traverse the network firewall.
Equinox H.323 Edge maintains the security and advantages of firewall and NAT over heterogeneous
video networks and supports seamless integration with existing video endpoints and infrastructure
components.
Equinox H.323 Edge uses the H.460 protocol. H.460 enhances the standard H.323 protocol to
manage firewall and NAT traversal using ITU-T standards.
H.460–compliant endpoints can directly communicate with Equinox H.323 Edge. The endpoints act
as H.460 clients and Equinox H.323 Edge acts as an H.460 server.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
10
Main features
Endpoints in private networks can communicate with the endpoints in public networks through
Equinox H.323 Edge. Endpoints in public networks can join conferences hosted in private networks
through Equinox H.323 Edge if there is an open connection through the firewall. H.323 Gatekeeper
provides standalone address resolution functionality in H.323–based networks.
Equinox H.323 Edge supports static addresses for external endpoints for conferences hosted on the
enterprise network. Users located outside the enterprise firewall can join conferences using
addresses such as 1234@h323edge.company.com , while users with endpoints logged in to
Equinox H.323 Edge can directly dial numbers such as 1234 to join conferences.
Main features
Equinox H.323 Edge enables firewall and NAT traversal for secure connectivity between
enterprise networks and remote sites. Equinox H.323 Edge has many powerful features including:
• Works with any firewall, endpoint and gatekeeper
Equinox H.323 Edge solves near-end and far-end firewall issues by allowing you to maintain
existing security measures with no changes to existing firewalls. All H.323 standards-based
endpoints and gatekeepers are supported. Equinox H.323 Edge is also fully compatible with
Avaya Equinox Management features, such as enhanced dial plan, hierarchy, conference
hunting, CDR records and API for integration.
• Highly secured
Equinox H.323 Edge uses a hardened version of the Linux operating system which has a
proven track record in secured system access.
Equinox H.323 Edge also provides uncompromised security by separating and restricting IP
traffic between the external and internal network cards (NICs). The external NIC accepts
access only from a very specific range of ports and media types, which significantly limits
intrusive attempts on the system.
Customers can restrict access of all management interfaces to a single NIC which resides
either in the DMZ or in the secured zone.
Equinox H.323 Edge works as an application layer firewall for H.323 calls and inspects the
contents of the traffic, blocking specific content, such as invalid H.323/RTP/RTCP packets.
Equinox H.323 Edge routes only validated H.323 based packets or RTCP/RTP based
packets from the external NIC to the internal NIC.
• Scalable and distributed
You can now deploy multiple Equinox H.323 Edge instances for improved availability for dial
in and dial out from your organization. As a result, enterprises can improve reliability or
accommodate more external endpoints joining videoconferences by adding more Equinox H.
323 Edge instances to their deployments.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
11
Equinox H.323 Edge overview
Equinox H.323 Edge supports server clusters to provide scalability and solid redundancy for
large deployments. Equinox H.323 Edge also supports external load balancers for high
availability.
• Guest user dial-in
Equinox H.323 Edge supports Direct Public Access (DPA). Any public H.323 endpoint can
directly call through Equinox H.323 Edge without the need to deploy an additional Avaya
Equinox H.323 Edge Client. Public H.323 endpoints which do not support the H.460 standard
can directly call Equinox H.323 Edge and easily and securely participate in any call or
conference call inside the organization.
• URI Dialing
With support for URI dialing Equinox H.323 Edge 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
Equinox Management fully supports Equinox H.323 Edge with comprehensive maintenance
tools such as:
- Platform settings, including network settings, static route settings, and setting permitted
networks and hosts.
- Configuration and user management.
- Security certificate and license management.
- Logging of traps and alarms and real-time monitoring.
• Integrated web-based event log in Equinox Management for quick and effective
troubleshooting.
Technical specifications of Equinox H.323 Edge
Requirement
Specification
Communications
• H.323
• IPv4
• Bit rate: up to 4Mbps per call
Table continues…
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
12
Minimum requirements of the Equinox H.323 Edge virtual appliance OVA
Requirement
Specification
Call capacity
• Up to 120 concurrent calls
• Up to 720 registered devices
Hardware load balancers for clusters
• Radware AppDirector 208
Load-balancers are optional. Load balancers are
needed only when you cannot configure dual NIC
virtual machines to use the built-in virtual machine
clustering mechanism.
• Radware AppDirector 1000
Firewall traversal
• H.460.18, H.460.19 including support for
multiplexed media
• F5 BIG-IP Load Traffic Manager 1600 Series
• 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 has Equinox H.323 Edge
Client, you can send the communications data
securely through the firewall by establishing a
route for the data through Equinox H.323 Edge
Client
Security
H.235 for call privacy in all traversal modes, such as
H.460, tunneling, and DPA
Minimum requirements of the Equinox H.323 Edge virtual
appliance OVA
Component
Specification
Server
Intel Xeon @ 2.0GHz, 4 physical cores
Server RAM
8GB
Virtual machine minimum vCPUs
2
Virtual machine CPU reservation
3000MHz
Virtual Machine RAM reservation
2GB
Server disk space reservation
60GB
Number of NICs
1 shared
Deploy a dual-NIC configuration of Equinox H.323
Edge with dedicated NICs for the internal and
external networks for more security and robustness.
A dual-NIC configuration also supports the built-in
virtual machine clustering mechanism. Single-NIC
Table continues…
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
13
Equinox H.323 Edge overview
Component
Specification
configurations need external hardware load
balancers for clustering.
Software
VMware ESXi Release 5.5 or 6.0 for customerprovided servers
Avaya Virtualization Platform Release 7.0 for
Avaya- provided servers
Capacity
December 2017
Maximum 120 calls and 720 registered users
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
14
Chapter 3: Preparing the Equinox H.323
Edge server Setup
Perform procedures in this section to prepare the site and device for installation.
Related links
Planning the topology on page 15
Ports configuration on page 16
Planning the topology
Communication in the deployment comprises management, external communication traffic
(unsecured), and internal communication traffic (secured). Equinox H.323 Edge supports these
communication protocols used by the system:
Table 1: Protocols supported by Equinox H.323 Edge
Type of Network Traffic
Protocols supported by Equinox H.323 Edge
Management
External management (TCP-XML based)
External communication (insecure)
H.460, proprietary client-server tunneling, DNS
Internal communication (secure)
H.323
To create a secure deployment, administrators in organizations need to separate the various types
of network traffic in the deployment.
Equinox H.323 Edge must be configured with two NICs to support enhanced 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 and management traffic.
Equinox H.323 Edge is located in the DMZ behind the firewalls. The DMZ is divided into two
subnets. The external NIC is connected to the outer DMZ and the internal NIC is connected to the
inner DMZ. The subnets do not communicate between them.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
15
Preparing the Equinox H.323 Edge server Setup
Figure 1: Deploying a high-security Dual-NIC Equinox H.323 Edge
Deploying Equinox H.323 Edge requires configuring the unit itself as well as several other
components. For information on components that are part of Equinox Solution, see Deploying
Avaya Equinox Solution.
The dual-NIC configuration of Equinox H.323 Edge supports a build-in virtual machine clustering
mechanism, which does not need third-party load balancers. The single-NIC configuration of
Equinox H.323 Edge does not support the built-in clustering mechanism and you need third-party
hardware load-balancers for scalability and redundancy.
Important:
Small and medium-size enterprises that set up video conferences within their enterprise can
choose to deploy Equinox H.323 Edge with a single NIC. Contact Customer Support for
information on that type of deployment.
Related links
Preparing the Equinox H.323 Edge server Setup on page 15
Ports configuration
Equinox H.323 Edge is Equinox Solution’s answer to firewall traversal. Equinox H.323 Edge is an
H.460 server, typically deployed in the DMZ, while Equinox H.323 Edge Client is a tunneling client,
typically deployed outside the enterprise firewall alongside the remote H.323 endpoint (see Figure
2: H.323 connections to Equinox H.323 Edge on page 17).
Many recent H.323 endpoints have built-in H.460 functionality (which enables secure
communication), thereby avoiding the need for Equinox H.323 Edge Client. If an H.323 endpoint
located in a partner company does not have H.460 capabilities, it must communicate via Equinox
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
16
Ports configuration
H.323 Edge Client to access Equinox H.323 Edge in the DMZ (see Figure 2: H.323 connections to
Equinox H.323 Edge on page 17).
Important:
There must be no firewall between the H.323 endpoint (device) and Equinox H.323 Edge
Client.
An H.323 endpoint in the public network can also directly dial Equinox H.323 Edge using direct
port access (ports 4000-5000).
Figure 2: H.323 connections to Equinox H.323 Edge
When opening ports to and from Equinox H.323 Edge, use the following as a reference:
• If opening ports that are both to and from Equinox H.323 Edge, see Table 2: Bidirectional
Ports to Open Equinox H.323 Edge on page 18.
• If opening ports that are both to and from Equinox H.323 Edge Client, see Table 3:
Bidirectional Ports to Open on the Equinox H.323 Edge Client on page 19.
Important:
In order for an H.323 endpoint (or other H.323 device) within the enterprise to successfully
connect to Equinox H.323 Edge in the DMZ via the enterprise firewall (see Figure 3:
Contacting Equinox H.323 Edge from within the enterprise on page 18), you must do the
following:
• Install Equinox H.323 Edge Client within the enterprise or use H.460-enabled endpoints.
• Open the internal firewall to Equinox H.323 Edge (12000 to 15000, bidirectional).
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
17
Preparing the Equinox H.323 Edge server Setup
Figure 3: Contacting Equinox H.323 Edge from within the enterprise
Important:
The specific firewalls to open ports depends on where Equinox H.323 Edge Client and other
Avaya Equinox Solution components are deployed.
Table 2: Bidirectional Ports to Open Equinox H.323 Edge
Port Range
Protocol
Source
Functionality
Result of
Blocking Port
Required
53
DNS (UDP)
DNS server
Enables querying
the DNS for
domains per call
Cannot support
domain name calls
and dialing by URI
Mandatory if
using URI dialing
1719
UDP
H.460.18–based Enables registration
endpoint or H.
of H.460–based
460.18–based
endpoints
client gatekeeper
H.460.18–based
endpoints cannot
register through
Equinox H.323
Edge
Mandatory for H.
460–based
endpoints
1720
TCP
Any H.323
device using Q.
931 signaling in
DPA mode
Enables IP call
signaling
No signaling
capabilities: guest
users cannot dial
into internal
endpoints
Mandatory if in
DPA mode
2776
TCP, UDP
H.460.18
endpoint/ H.
460.18 client
gatekeeper
Enables H.460.18
Call Signaling, H.
460.19 Multiplex
Media Channel
Firewall traversal
function based on
H.460.18 and H.
460.19 cannot
function.
Mandatory for H.
460 endpoints
2777
TCP, UDP
H.460.18
endpoint/ H.
Enables H.460.18
and H.460.19 Call
Control, H.460.19
H.460.18
endpoints cannot
set up Call Control
Mandatory for H.
460 endpoints
Table continues…
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
18
Ports configuration
Port Range
Protocol
Source
Functionality
460.18 client
gatekeeper
Multiplex Media
Control Channel
Result of
Blocking Port
channels or logical
channels. Firewall
traversal function
based on H.460.18
and H.460.19
cannot function.
Required
3089
TCP, UDP
Equinox H.323
Edge Client
Enables signaling
and media traversal
If the TCP port is
Mandatory if
blocked, Equinox
using Equinox H.
H.323 Edge Client 323 Edge Client
cannot connect to
Equinox H.323
Edge. Legacy H.
323 endpoints
behind the Equinox
H.323 Edge Client
cannot call external
endpoints. If the
UDP port is
blocked, Equinox
H.323 Edge Client
can only traverse
media via TCP.
4000-5000
TCP, UDP
Any H.323
device using Q.
931 signaling in
DPA mode
Enables Direct
Public Access
(DPA) for H.323 call
signaling, control
and media traversal
Cannot setup/
Mandatory if in
connect DPA mode DPA mode
calls
To limit range,
see Configuring
the TCP/UDP
port range for H.
323 Direct Public
Access calls on
page 29
8089
XML (TCP)
XML API Client
Enables managing
Equinox H.323
Edge via XML API
The External
Management
System cannot get
Equinox H.323
Edge status or
receive traps from
Equinox H.323
Edge
Optional
Table 3: Bidirectional Ports to Open on the Equinox H.323 Edge Client
Port Range
Protocol
Source
Functionality
3478
STUN (UDP)
STUN server
Enables an endpoint Equinox H.323
located in the
Edge Client
remote network to
cannot
December 2017
Result of
Blocking Port
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
Required
Recommended
19
Preparing the Equinox H.323 Edge server Setup
Port Range
Protocol
Source
Functionality
send a STUN
Binding Request
when connecting to
another endpoint in
the same network
Result of
Blocking Port
determine its
public IP
address. Smart
Direct Media
Connect cannot
function.
Required
Important:
If there is a firewall between the H.323 client and the Equinox H.323 Edge Client, all high
ports must be opened in both directions (1024-65535). We therefore recommend no firewall
between the endpoint and the Equinox H.323 Edge Client.
Related links
Preparing the Equinox H.323 Edge server Setup on page 15
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
20
Chapter 4: Deploying the Equinox H.323
Edge virtual server
Equinox H.323 Edge virtual server deployment checklist
#
Action
Link/Notes
1
Download the Equinox H.323 Edge
software from PLDS
See Downloading software from
PLDS on page 21
2
Deploy the Equinox H.323 Edge virtual
server
See Deploying the Equinox H.323 Edge
virtual server on page 22
3
Start the Equinox H.323 Edge virtual
server
See Starting the Equinox H.323 Edge
virtual server on page 23
4
Configure the Equinox H.323 Edge virtual See Configuring the virtual machine
server automatic startup settings
automatic startup settings on page 24
Downloading software from PLDS
When you place an order for an Avaya PLDS-licensed software product, PLDS creates the license
entitlements of the order and sends an email notification to you. The email includes a license
activation code (LAC) and instructions for accessing and logging into PLDS. Use the LAC to locate
and download the purchased license entitlements.
In addition to PLDS, you can download the product software from http://support.avaya.com using
the Downloads and Documents tab at the top of the page.
Note:
Only the latest service pack for each release is posted on the support site. Previous service
packs are available only through PLDS.
Procedure
1. Enter http://plds.avaya.com in your Web browser to access the Avaya PLDS website.
2. Enter your login ID and password.
3. On the PLDS home page, select Assets.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
21
Deploying the Equinox H.323 Edge virtual server
4. Click View Downloads.
5. Click on the search icon (magnifying glass) for Company Name.
6. In the %Name field, enter Avaya or the Partner company name.
7. Click Search Companies.
8. Locate the correct entry and click the Select link.
9. Enter the Download Pub ID.
10. Click Search Downloads.
11. Scroll down to the entry for the download file and click the Download link.
12. In the Download Manager box, click the appropriate download link.
Note:
The first link, Click to download your file now, uses the Download Manager to
download the file. The Download Manager provides features to manage the download
(stop, resume, auto checksum). The click here link uses your standard browser
download and does not provide the download integrity features.
13. If you use Internet Explorer and get an error message, click the install ActiveX message
at the top of the page and continue with the download.
14. Select a location where you want to save the file and click Save.
15. If you used the Download Manager, click Details to view the download progress.
Deploying the Equinox H.323 Edge virtual server
About this task
The Equinox H.323 Edge virtual server software for VMware is available in the .OVA package
format. You can install the OVA file using vSphere Client. The virtual server configuration file and
virtual disk files are stored on a data store. The data store can be local to the host or a mounted
shared storage, such as NFS or SAN.
If multiple virtual machine networks are configured on the host ESXi server, the wizard prompts
you to associate networks specified in the OVA with networks available on the host.
Procedure
1. Log in to vSphere Client.
2. Select the host ESXi server to deploy the Equinox H.323 Edge virtual server.
If you do not choose a host before deploying the OVA, vSphere Client prompts you for the
host or cluster name to deploy the virtual server.
3. Click File > Deploy OVF Template.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
22
Starting the Equinox H.323 Edge virtual server
4. Do one of the following:
• Click Browse and provide the Equinox H.323 Edge OVA file location.
• In the Deploy from a file or URL field, enter the full URL of the HTTP server where the
Equinox H.323 Edge OVA file is located.
5. Click Next to display the OVF Template Details window.
6. Verify the details of the OVA template, and click Next.
7. Read the license agreement, and click Accept.
8. Click Next.
9. In the Name field, enter the name of the new virtual server.
10. Click Next to display the Disk Format window.
11. Select Thick Provision.
12. Click Next to display the Ready to Complete window.
13. Verify the deployment settings.
If you need to modify any of the settings, use the Back option.
14. Click Finish.
Result
1. vSphere Client starts the Equinox H.323 Edge virtual server deployment.
2. After completing the deployment, in the Recent Tasks window, vSphere Client updates the
status of the Deploy OVT Template task to Completed.
Starting the Equinox H.323 Edge virtual server
Before you begin
Deploy the Equinox H.323 Edge virtual server.
Procedure
1. Log in to vSphere Client.
2. Click Inventory.
3. Click Virtual Machine > Power > Power On.
The Equinox H.323 Edge virtual server starts.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
23
Deploying the Equinox H.323 Edge virtual server
Configuring the virtual machine automatic startup settings
About this task
When a vSphere ESXi host restarts after a power failure, the virtual machines that are deployed
on the host do not start automatically. You must configure the virtual machines to start
automatically.
In high availability (HA) clusters, the VMware HA software ignores the startup selections.
Before you begin
Verify with the system administrator that you have the proper level of permissions to configure the
automatic startup settings.
Procedure
1. In the vSphere Client inventory, select the host where the virtual machine is located.
2. Click the Configuration tab.
3. In the Software section, click Virtual Machine Startup/Shutdown.
4. Click Properties in the upper-right corner of the screen.
5. In the System Settings section, select Allow virtual machines to start and stop
automatically with the system.
6. In the Manual Startup section, select the virtual machine.
7. Use the Move up button to move the virtual machine to the Automatic Startup section.
8. Click OK.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
24
Chapter 5: Initial administration of Equinox
H.323 Edge
Equinox H.323 Edge initial configuration checklist
No.
Task
Link/Notes
1
(Optional) Add more networks to the
Equinox H.323 Edge.
Adding networks to Equinox H.323
Edge on page 26
2
Add Equinox H.323 Edge as a device in
Equinox Management
Adding Equinox H.323 Edge in Equinox
Management on page 27
3
(Optional) Configure IP separation of the
Configuring IP separation in Equinox
internal and external network traffic on the Management on page 28
Equinox H.323 Edge virtual server.
4
Configure the ports on Equinox H.323
Edge.
Configuring Ports on Equinox H.323
Edge on page 29
5
Configure the gatekeeper .
Integrating with the gatekeeper on
page 31
6
Configure NAT.
Integrating with NAT on page 32
7
Configure the NTP server.
Configuring the NTP server on page 32
8
Configure access to calls to H.323 legacy
endpoints.
Configuring access for calls to H.323
legacy endpoints on page 33
9
Configure URI-based dialing.
URI Dialing Functionality on page 34
10
Configure IP address-based dialing.
Configuring IP address-based dialing to
external endpoints on page 38
11
Secure the connection with Equinox
Management.
Securing the connection with Equinox
Management using TLS on page 43
12
Update the Equinox H.323 Edge license
Adding or updating licenses on page 44
13
Configure remote access to administer
Equinox H.323 Edge from Equinox
Management.
Configuring remote access on page 45
14
Configure QoS.
Configuring QoS for audio and video on
page 46
Table continues…
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
25
Initial administration of Equinox H.323 Edge
No.
Task
Link/Notes
15
(Optional) Create Equinox H.323 Edge
server clusters to optimize the server use
without load balancers.
Creating an Equinox H.323 Edge server
Cluster on page 47
Adding networks to Equinox H.323 Edge
About this task
Add more networks to Equinox H.323 Edge to configure IP separation for the external and internal
networks. You can also use this procedure to configure separate subnets for different networks.
This procedure is relevant only if you have a dual NIC deployment of Equinox H.323 Edge.
Before you begin
Connect a network cable to the second NIC of the host server.
Procedure
1. Log in to vSphere Client.
2. In the vSphere Client inventory, select the host where you deployed Equinox H.323 Edge.
3. Click the Configuration tab.
4. In the Hardware section, click Networking .
5. Click Add Networking....
VSphere Client displays the Add Networking Wizard window.
6. In Connection Type, select Virtual Machine, and click Next.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
26
Adding Equinox H.323 Edge in Equinox Management
7. In Network Access, select the vSwitch corresponding to the second NIC of the host
server, and click Next.
8. In Connection Settings, configure the following fields:
• Network Label
• VLAN ID (Optional): If you do not have a VLAN ID, select None.
9. Click Next.
10. In Summary, verify the configuration, and click Finish.
Result
vSphere Client adds another network to the host server.
Next steps
1. Add the Equinox H.323 Edge instance in Equinox Management for the eth0 interface.
2. Configure IP separation in Equinox Management.
Adding Equinox H.323 Edge in Equinox Management
About this task
Manage Equinox H.323 Edge using Equinox Management.
Before you begin
Get the IP address of the Equinox H.323 Edge eth0 interface.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
27
Initial administration of Equinox H.323 Edge
Procedure
1. Log in to Equinox Management.
2. Click Devices.
3. Click H.323 Edge Servers in the left pane.
Equinox Management displays the Equinox H.323 Edge server window.
4. Click Add.
Equinox Management displays the Add Equinox H.323 Edge server window.
5. Configure the following fields:
• Name
• IP Address
6. Click OK.
Result
Equinox Management adds the Equinox H.323 Edge instance as a device.
Configuring IP separation in Equinox Management
About this task
Configure a different IP address and subnet for the second virtual NIC of Equinox H.323 Edge to
process the external traffic.
Before you begin
Configure vSwitches in vSphere Client.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
Equinox Management opens the Equinox H.323 Edge instance window.
3. Click the Configuration tab.
4. In the Network Settings section, click NIC Settings.
Equinox Management displays the NIC Settings window.
5. Configure the following:
Internal NIC:
• IP Address: The IP address of the eth0 interface.
• Subnet Mask
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
28
Configuring Ports on the Equinox H.323 Edge server
• Gateway
• Local FQDN
External NIC:
• External NIC: Select to enable dual NIC.
• IP Address: The IP address of the eth1 interface.
• Subnet Mask
• Gateway
Result
Equinox Management configures dedicated NICs for the external and internal network traffic.
Next steps
In a dual NIC configuration, the internal NIC can connect only to its subnet. You must configure
static routes between the internal NIC and other subnets.
Configuring Ports on the Equinox H.323 Edge server
This section provides instructions of how to configure the following ports and port ranges on the
Avaya Equinox H.323 Edge server:
Configuring the TCP/UDP port range for H.323 Direct Public
Access calls
About this task
Equinox H.323 Edge has a port range of 4000 to 5000 ports designated for H.323 Direct Public
Access. Using H.323 Direct Public Access, non-H.460 public endpoints can call internal endpoints
without being registered to Equinox H.323 Edge. To add more security to your firewall, you can
limit the port range for H.323 Direct Public Access.
To calculate the number of ports Equinox H.323 Edge uses, multiply the number of simultaneous
Direct Public Access 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.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
3. Click Configuration.
4. In Direct Public Access, select Enabled.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
29
Initial administration of Equinox H.323 Edge
5. Type the values in the following fields:
• Default Extension
• Port Range Minimum Port
• Port Range Maximum Port
6. Click Apply.
Equinox Management displays a confirmation message.
7. Click Yes.
Configuring the TCP/UDP port range on the internal interface
About this task
Equinox H.323 Edge has a port range of 12000 to 15000 ports designated for H.323–based calls
to the internal interface. To add more security to your firewall, you can limit the port range for H.
323 calls.
To calculate the number of ports Equinox H.323 Edge 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 Equinox H.323 Edge after you modify the port range.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
3. Click Configuration.
4. In Internal Communication, change the port range in the following fields:
• Internal Port Range Minimum Port
• Internal Port Range Maximum Port
Select a port range between 12000 to 15000. The maximum port range is from 9000 to
65535. The port range requires a minimum range of 300 ports.
5. Click Apply.
Equinox Management displays a confirmation message.
6. Click Yes.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
30
Integrating the Equinox H.323 Edge server with Other Equinox Solution Components
Next steps
Restart Equinox H.323 Edge
Integrating the Equinox H.323 Edge server with Other
Equinox Solution Components
Your Avaya Equinox H.323 Edge server is part of the Equinox Solution and must be integrated
with other components:
Integrating Equinox H.323 Edge with H.323 Gatekeeper
About this task
The integration of Equinox H.323 Edge and H.323 Gatekeeper supports the communication
between endpoints from external networks and endpoints in the internal network. You need to
configure the IP address of H.323 Gatekeeper in Equinox H.323 Edge.
The external endpoints can be endpoints that are compliant with H.323 and H.460. Conference
participants dial in to call using IP addresses, URI, or the E.164 number.
For example, dialing in to conferences using URI involves the gatekeeper resolving the host
name, such as name@company.com or number@company.com, with the IP address of the
endpoint being used. When the URI address contains a destination to an external network,
Equinox H.323 Edge and H.323 Gatekeeper work together to resolve the URI address.
Note:
In the settings of the gatekeeper, add the IP address of Equinox H.323 Edge at port 1719 as
the gatekeeper's neighbor, as described in Configuring URI-based dialing to external
endpoints on page 35.
Before you begin
Get the IP address of the H.323 Gatekeeper.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select Equinox H.323 Edge instance.
3. Click the Configuration tab.
4. In the Gatekeeper Settings section, enter gatekeeper address and port in the following
fields:
• Gatekeeper Address
• Gatekeeper Port
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
31
Initial administration of Equinox H.323 Edge
Related links
Configuring URI-based dialing to external endpoints on page 35
Configuring access for calls to H.323 video endpoints on page 33
Integrating Equinox H.323 Edge with NAT
About this task
If the external NIC of Equinox H.323 Edge uses a private IP address to communicate with
endpoints in external networks, enable NAT traversal.
Do not enable NAT traversal if the external NIC communicates with the Internet by using a public
IP address.
Before you begin
Get the NAT traversal IP address.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
Equinox Management opens the Equinox H.323 Edge instance window.
3. Click the Configuration tab.
4. Click Basic Settings.
5. In the NAT Support section, do the following:
a. Select Enabled.
b. Enter the IP address in Public IP Address.
Next steps
In the firewall or NAT device, verify that the NAT address is mapped to the private IP address of
the external NIC of Equinox H.323 Edge.
Configuring the NTP server
Before you begin
Get the IP address of the NTP server.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
Equinox Management opens the Equinox H.323 Edge instance window.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
32
Enabling Internal Endpoints to Call External Endpoints
3. Click the Configuration tab.
4. Click Network Settings.
5. In NTP Settings section, do the following:
a. NTP Server Address: Type the IP address of the NTP server.
b. Time Zone: Select the time zone.
6. Click Apply.
Enabling Internal Endpoints to Call External Endpoints
Endpoints in the organization call external endpoints using their IP address (including dialing the
device, then # or ##, then the meeting ID) or URI. If the external endpoint is registered to the H.
323 Gatekeeper, it can also dial the endpoint's E.164 number. Since external endpoints are
typically not registered to the gatekeeper, this requires the gatekeeper to work with the Avaya
Equinox H.323 Edge server to complete the call.
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. The H.323 Gatekeeper
provides address resolution functionality in H.323 networks and also manages video traffic over IP
networks. When the destination address is located in another network, the gatekeeper forwards
the request to the Equinox H.323 Edge server to complete the call and resolve the destination.
You must configure both the Equinox H.323 Edge server and the H.323 Gatekeeper to support IP
and URI dialing, as described in the following topics:
Configuring access for calls to H.323 video endpoints
About this task
Direct Public Access supports a direct connection to Equinox H.323 Edge for calls to external
endpoints. To set up this connection, you need to configure:
• Equinox H.323 Edge to process H.323 calls.
• H.323 Gatekeeper to Equinox H.323 Edge instances to process the routing of the calls.
For more information about configuring H.323 Gatekeeper, see Reference Guide for H.323
Gatekeeper.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
3. Click the Configuration tab.
4. In the Direct Public Access section, select Enabled.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
33
Initial administration of Equinox H.323 Edge
5. Enter the direct line extension number and the port range in the following fields:
• Default Extension
• Port Range Minimum Port
• Port Range Maximum Port
Field
Description
Port Range
Define the range of ports used for direct H.323 calls in the
field.
Important:
If the external NIC of the Equinox H.323 Edge 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). Equinox H.323 Edge
redirects a call to the default extension when the endpoint
dials only the server's IP address without any extension.
6. Click Apply.
Equinox Management displays a confirmation message.
7. Click Yes.
Related links
Configuring URI-based dialing to external endpoints on page 35
Integrating Equinox H.323 Edge with H.323 Gatekeeper on page 31
Configuring IP address-based dialing to external endpoints on page 38
URI-based dialing
The Avaya Equinox solution supports URI-based dialing, which is a dialing format to call and
receive calls from external endpoints.
URI is an address format 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, such as <endpoint
name>@<server_domain_name>. For example, 5000@198.51.100.51.
All Avaya Equinox solution endpoints work transparently with URI-based dialing, including the
Avaya Scopia® XT Series. You can also perform URI-based dialing from the conference control
feature of Equinox Management.
Equinox H.323 Edge supports URI-based dialing for H.323–based endpoints. Outgoing calls to
external endpoints traverse through the enterprise firewall of the caller using Equinox H.323 Edge
to the Internet and connect to the external endpoint through the firewall traversal solution of the
external endpoint’s enterprise.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
34
Enabling Internal Endpoints to Call External Endpoints
DNS configuration to allow inbound DNS-based URI calls
Configure DNS to ensure that calls to your enterprise can be dialed using the shortest possible
name. Use SRV records under the host name record to configure services under the same
domain as the host. You can also map the SRV records to sub-domains.
You must create the following two new resource records and map them with the same domain to
allow inbound DNS-based URI calls to your enterprise:
• A resource record called the Host (A or AAAA) record for the enterprise host address.
• A service record called Service (SRV) record for the TCP/IP service.
The following screenshots of the DNS Manager windows show the mapping of the Host record
and the SRV record:
Configuring URI-based dialing to external endpoints
About this task
Callers can establish calls to endpoints using the IP address, URI, or the E.164 number of
endpoints. Configure Equinox H.323 Edge to accept H.323–based calls and forward them. You
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
35
Initial administration of Equinox H.323 Edge
also need to configure internal gatekeeper of Equinox Management to define one or more
instances of Equinox H.323 Edge as the neighbor of the internal gatekeeper to establish routes for
the H.323–based calls.
The internal gatekeeper of Equinox Management forwards URI-based calls from internal
endpoints to external endpoints in another enterprise through Equinox H.323 Edge. The internal
gatekeeper must also forward the URI-based calls from external endpoints through Equinox H.323
Edge because external endpoints are not registered to the internal gatekeeper. The external
endpoints can be H.323–based and H.460–based.
If the enterprise deployment has multiple Equinox H.323 Edge instances, which includes several
servers deployed as one server behind a load balancer, perform this procedure for each Equinox
H.323 Edge instance.
Before you begin
• Configure Direct Public Access on Equinox H.323 Edge for calls to H.323–based endpoints.
Using Direct Public Access, internal endpoints can call external H.323–based endpoints that
do not support H.460.
If you are configuring multiple Avaya Equinox H.323 Edges, with or without a load balancer,
do this for each Avaya Equinox H.323 Edge.
• Integrate Equinox H.323 Edge with the H.323 gatekeeper to enable external endpoints to
communicate with internal endpoints.
• Get the IP address of the Equinox H.323 Edge internal NIC.
If you are configuring multiple Avaya Equinox H.323 Edges, with or without a load balancer,
do this for each Avaya Equinox H.323 Edge.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
Equinox Management opens the Equinox H.323 Edge instance window.
3. On the Info tab, note the IP address and port number in Public Access Proxy Address.
4. Click the Configuration tab.
5. Configure the following fields in the URI Dialing Settings section:
• Local Domain Name
• Strip Domain Name
6. Click Settings.
7. On the left pane, under System Preferences, click Local Services.
Equinox Management displays the Local Services page.
8. Click H.323 Gatekeeper.
Equinox Management displays the internal H.323 gatekeeper page.
9. Click Neighbors > Add.
Equinox Management displays the Add Neighbors window.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
36
Enabling Internal Endpoints to Call External Endpoints
10. Configure the following fields:
• Prefix: Keep this field empty.
• Description
• IP Address: The IP address of the internal NIC of Equinox H.323 Edge
• Port: 1719
11. Click OK.
12. Click Apply.
Result
Equinox Management adds Equinox H.323 Edge as a neighbor of the internal gatekeeper.
Related links
Configuring access for calls to H.323 video endpoints on page 33
Integrating Equinox H.323 Edge with H.323 Gatekeeper on page 31
Configuration field descriptions
Name
Description
Local Domain Name
The domain name of the enterprise where Equinox
H.323 Edge is physically located.
Strip Domain Name
The option to strip the domain name and IP address
from the dialed string before transferring the
signaling message to the main gatekeeper.
This setting optimizes the processing of call
transfers. Do not select this option if the enterprise
has a policy of transferring messages by using the
complete dial string of endpoints. For example,
1234@5.6.7.8, instead of the 1234 alias.
Add Neighbors field descriptions
Name
Description
Prefix
The local zone prefix of the gatekeeper.
Do not configure this field. URI-based dialing does
not establish call routes to zones using dial prefixes.
URI-based dialing establishes call routes using the
domain name in the URI string, which is resolved to
all zone worldwide.
Description
The name of Equinox H.323 Edge.
Table continues…
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
37
Initial administration of Equinox H.323 Edge
Name
Description
IP Address
The IP address of the Equinox H.323 Edge internal
NIC, which is connected to the internal network.
Port
The port for URI-based calls.
The default 1719 port is mandatory for URI-based
dialing.
Configuring IP address-based dialing to external endpoints
About this task
Callers can establish calls to endpoints using the IP address, URI, or the E.164 number of
endpoints. Configure the internal gatekeeper of Equinox Management to forward IP addressbased calls from internal endpoints to external endpoints through Equinox H.323 Edge. The
internal gatekeeper must forward the IP address-based calls from external endpoints through
Equinox H.323 Edge because external endpoints are not registered to the internal gatekeeper.
If the enterprise deployment has multiple Equinox H.323 Edge instances, which includes several
servers deployed as one server behind a load balancer, perform this procedure for each Equinox
H.323 Edge instance.
Before you begin
• Get the IP address of the Equinox H.323 Edge internal NIC.
If you are configuring multiple Avaya Equinox H.323 Edges, with or without a load balancer,
do this for each Avaya Equinox H.323 Edge.
• Get the Direct Public Access address of Equinox H.323 Edge.
If you are configuring multiple Avaya Equinox H.323 Edges, with or without a load balancer,
do this for each Avaya Equinox H.323 Edge.
• Configure Direct Public Access on Equinox H.323 Edge for calls to external endpoints. Using
Direct Public Access, internal endpoints can call external endpoints that do not support H.
460.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
38
Enabling Internal Endpoints to Call External Endpoints
If you are configuring multiple Avaya Equinox H.323 Edges, with or without a load balancer,
do this for each Avaya Equinox H.323 Edge.
• If the enterprise deployment has multiple Equinox H.323 Edge instances, verify that the
correct redundancy policy is configured between the internal gatekeeper of Equinox
Management and each Equinox H.323 Edge instance.
The internal gatekeeper of Equinox Management has its own load balancing method to work
with multiple Equinox H.323 Edge instances for outgoing calls from internal endpoints to
external endpoints. By default, the internal gatekeeper is configured to the Scalability policy,
which enables the internal gatekeeper to send requests to each Equinox H.323 Edge
instance using the round robin method.
You can set also configure the internal gatekeeper of Equinox Management to work with the
Priority policy where the internal gatekeeper can establish the route of the call to the first
Equinox H.323 Edge instance in the list and send the call to the next Equinox H.323 Edge
instance if the first Equinox H.323 Edge instance fails. Contact Customer Support to
configure the Equinox H.323 Edge redundancy policy.
Note:
The Equinox H.323 Edge redundancy policy configuration is different from the
redundancy policy for the load balancer, which instructs it how to direct incoming traffic
from the external network to the internal network.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
Equinox Management opens the Equinox H.323 Edge instance window.
3. On the Info tab, note the IP address and port number in Public Access Proxy Address.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
39
Initial administration of Equinox H.323 Edge
4. Click Settings.
5. On the left pane, under System Preferences, click Local Services.
Equinox Management displays the Local Services page.
6. Click H.323 Gatekeeper.
Equinox Management displays the internal H.323 gatekeeper page.
7. Click Route IP calls, and select Route IP calls to H.323 Edge Server.
8. Click Add.
Equinox Management displays the Add IP Calls window.
9. Configure the following fields:
• IP Address
• Port
The value of these fields must match the IP address and port number in Public Access
Proxy Address on the Info tab of the Equinox H.323 Edge instance window.
10. Click OK.
Result
The internal gatekeeper of Equinox Management forwards all IP address-based calls from
external endpoints through Equinox H.323 Edge.
Related links
Configuring access for calls to H.323 video endpoints on page 33
Add IP Calls field descriptions
Name
Description
IP Address
The IP address in the Public Access Proxy
Address field on the Info tab of the Equinox H.323
Edge instance.
Equinox H.323 Edge automatically creates the IP
address when you enable Direct Public Address.
Port
December 2017
The port number in the Public Access Proxy
Address field on the Info tab of the Equinox H.323
Edge instance.
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
40
Secure connection with Equinox Management
Secure connection with Equinox Management
Creating security certificates
About this task
TLS certificates, issued by a trusted certification authority, contain the public encryption keys of
Equinox H.323 Edge that are used over the network to ensure authentication and encryption of the
network connection.
Important:
Using encryption is subject to local regulation. In some countries it is restricted or limited for
usage. For more information, consult your local reseller.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and click the name of the Equinox H.323 Edge instance.
Equinox Management displays the Equinox H.323 Edge instance window.
3. Click the Certificate tab.
4. Click Create.
Equinox Management displays the Generate CSR window.
5. Configure the following fields:
• Common name
• Organizational Unit
• Organization
• City
• State
• Country Code
• Encryption Strategy
• Signature Algorithm
6. Click Generate CSR.
7. Click Save to view the certificate.
Equinox Management displays the certificate in the Download window.
8. Save the certificate.
Equinox Management saves the certificate as a CSR file that is compatible with the
Base-64 ASCII code.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
41
Initial administration of Equinox H.323 Edge
9. Send the CSR file containing the certificate to the certification authority for signing.
Select Web Server as the certificate template when you submit the certificate request.
Result
The certification authority will send back a signed certificate.
Next steps
Upload the certificates.
Generate CSR field descriptions
Name
Description
Common Name
The Equinox H.323 Edge FQDN.
For a redundant deployment, the common name
must be the public virtual FQDN.
Country Code
The standard country code that consists of two
characters.
For example, uk for United Kingdom or jp for Japan.
This field is not case-sensitive.
Encryption Strategy
The code for the encryption strategy. The options
are:
• 1024
• 2048
• 4096
Signature Algorithm
The algorithm to use when generating the signature
on the certificate.
This algorithm is a combination of the private keys
of both the CA and the device. The options are:
• SHA1withRSA
• SHA256withRSA
Uploading security certificates
About this task
TLS certificates from the certification authority must be uploaded to Equinox H.323 Edge to ensure
authentication and encryption of the network connection.
If Equinox Management is configured as the certificate authority, Equinox Management
automatically generates a self-signed certificate to upload to Equinox H.323 Edge when the
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
42
Secure connection with Equinox Management
connection between Equinox Management and Equinox H.323 Edge establishes. You can replace
the Equinox Management self-signed certificate.
Important:
Using encryption is subject to local regulation. In some countries it is restricted or limited for
usage. For more information, consult your local reseller.
Before you begin
Generate the certificates.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and click the name of the Equinox H.323 Edge instance.
Equinox Management displays the Equinox H.323 Edge instance window.
3. Click the Certificate tab.
4. Click Upload.
Equinox Management displays the Upload certificates window.
5. Click Add, and browse to the certificates.
Repeat this step for all certificates.
Equinox Management displays a confirmation message after each certificate is uploaded.
6. Click Apply All.
Result
Equinox Management uploads the security certificate to Equinox H.323 Edge.
Next steps
1. Restart Equinox H.323 Edge.
2. Enable the secure connection between Equinox H.323 Edge and Equinox Management.
Securing the connection with Equinox Management using TLS
Before you begin
Upload the security certificates.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and click the name of the Equinox H.323 Edge instance.
Equinox Management displays the Equinox H.323 Edge instance window.
3. Click the Configuration tab.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
43
Initial administration of Equinox H.323 Edge
4. Click Network Settings.
5. Select Secure Connection,
Result
The connection between Equinox H.323 Edge and Equinox Management is secured using TLS.
Getting the system ID to activate Equinox H.323 Edge
About this task
You need the system ID of Equinox H.323 Edge to activate the server.
If you deploy the hardware server, see the customer letter for the system ID.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
3. On the Info tab, note UUID.
Next steps
Add the Equinox H.323 Edge license to activate the server.
Adding and updating licenses
About this task
Update licenses when you increase the Equinox H.323 Edge capacity or increase the number of
ports with a flexible license.
If you upgrade Equinox H.323 Edge to a major version, you must have a new license.
Before you begin
• Download the Equinox H.323 Edge upgrade package at https://plds.avaya.com/.
• Get the Equinox H.323 Edge System ID.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
Equinox Management displays the Equinox H.323 Edge instance page.
3. Click the Licensing tab.
4. In Update License Key, type the license key.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
44
Configuring remote access
5. Click Apply.
Result
Equinox Management activates the new Equinox H.323 Edge license.
Related links
Getting the system ID to activate Equinox H.323 Edge on page 44
Configuring remote access
About this task
Configure remote access to Equinox H.323 Edge. You can use these remote access logins to
administer Equinox H.323 Edge using Equinox Management.
Before you begin
To enable a secure connection between Equinox H.323 Edge and Equinox Management,
configure the security certificates in the Certificate tab.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
Equinox Management displays the Equinox H.323 Edge instance page.
3. Click the Access tab.
4. Configure the following settings:
• Username: The user name of the administrator.
• Password: The password of the administrator.
5. Click Apply.
Access field descriptions
Name
Description
Username
The user name of the administrator.
You can change the user name.
Password
The password of the administrator.
The password must match the password configured
for the administrator in Equinox H.323 Edge. You
can change the password.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
45
Initial administration of Equinox H.323 Edge
Configuring QoS for audio and video
About this task
Quality of Service helps solve network performance issues by assigning relative priorities to the
following packets:
• Audio, which is one of the media sent during a call. For example, by assigning high priority to
audio under poor network conditions with high packet loss, you determine that audio is the
most important element of the videoconference to be maintained at the expense of better
video quality. Audio is transmitted via the RTP and RTCP protocols in H.323 calls.
Video, which includes shared data stream like a presentation, also known as dual video. Far
end camera control (FECC) is another example of information carried on the data stream.
Video is transmitted via the RTP and RTCP protocols in H.323 calls.
Control, which includes signaling and media control.
- 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. Signaling occurs before
the control aspect of call setup.
- 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. Control occurs within the
framework of an established call, after signaling.
During low-bandwidth conditions, Equinox Management uses these priority settings to adjust the
quality of the meeting. Follow this procedure to determine the relative priorities for audio, video,
and control transmitted via Equinox H.323 Edge.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and click the Equinox H.323 Edge instance.
Equinox Management displays the Equinox H.323 Edge instance page.
3. Click Configuration > Advanced Parameters.
Equinox Management displays the Advanced Parameters window.
4. Select Options of QoS Settings, and set the value to one of the following settings:
Field
Description
None
Select this setting when the network has sufficient bandwidth for each
stream (audio, video, and media control) and does not require any
prioritization of the different streams.
Table continues…
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
46
Creating an Equinox H.323 Edge server Cluster
Field
Description
Default
Select this setting to use the following default priority values for each
stream:
• 48 for the media Control stream. This highest priority ensures that calls
are set up properly even if it means that other calls ongoing may reduce
their video or audio during a call setup. All TCP connections use the
QoS value set in this field.
• 46 for the Audio stream. This priority ensures that audio is always
given precedence over video. This audio applies to multiple video
channels (e.g., sound stream for endpoint microphones and
presentations).
• 34 for the Video stream. The lowest default priority is given to video
image quality. It applies to endpoint camera images and also covers
data streams like far end camera control.
Customized
The QoS options to configure the relative priority of the audio, video, and
control channels.
Use the following advanced parameters to set the priority of the audio,
video, and control channels. The valid value range is from 0 to 255:
• QoS value for Audio Channel
• QoS value for Video Channel
• QoS value for Control Channel
Creating an Equinox H.323 Edge server Cluster
About this task
You can create a cluster of Equinox H.323 Edge servers. H.323 Edge server clusters enable you
to increase your call volume. Equinox Management treats a cluster as if it is a single server, so if
you have three servers in a cluster, the cluster can handle three times as many calls as a single H.
323 Edge server.
Note:
The built-in virtual machine clustering mechanism relies on a multicast MAC address to
distribute the network traffic to all the virtual machines. Typically, network routers and firewalls
deny multicast MAC addressing. You might need to update the router and firewall policy for
the clustering mechanism to work.
Before you begin
Ensure that you have more than one H.323 Edge server configured in your deployment.
Procedure
1. Access the Equinox Management administrator portal.
2. Select Devices > Devices by Type > Media & Signaling > H.323 Edge Servers.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
47
Initial administration of Equinox H.323 Edge
The H.323 Edge Servers page appears.
Figure 4: H.323 Edge Servers Page
3. Select Create a Cluster.
The Create a Cluster dialog box appears:
Figure 5: Create a Cluster Dialog Box
4. Configure a Cluster Name and Public IP Address in the relevant fields, and select the
check boxes of the servers you want to add to the cluster.
5. Select Apply.
The cluster appears in the list on the H.323 Edge Servers page.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
48
Creating an Equinox H.323 Edge server Cluster
Figure 6: H.323 Edge Server Cluster
A cluster has one of the following statuses:
• Green: Normal
• Yellow: Alarm
Note:
If the cluster is deployed inside a private address DMZ, the cluster’s public IP address
must be mapped to an actual global IP address. The global IP address must be must
be configured to the public IP address in the NAT support section of the cluster’s H.323
Edge server.
If the cluster is deployed in the public network, the cluster’s IP address does not need
to be mapped and therefore can be set to the public IP address in the NAT support
section of the cluster’s H.323 Edge server.
6.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
49
Chapter 6: Equinox H.323 Edge Client
configuration
Equinox H.323 Edge Client configuration checklist
No.
Task
Link/Notes
1
Install Equinox H.323 Edge Client.
See Installing Equinox H.323 Edge
Client On a Windows Platform on
page 51
2
Add Equinox H.323 Edge Client user
accounts to Equinox H.323 Edge.
See Adding Equinox H.323 Edge Client
user accounts to Equinox H.323
Edge on page 52
3
Add the enterprise gatekeeper to
Equinox H.323 Edge and specify the
Equinox H.323 Edge Client instance that
the gatekeeper serves.
See Adding enterprise gatekeepers to
Equinox H.323 Edge on page 53
4
Configure Equinox H.323 Edge Client as
a neighbor of the enterprise gatekeeper.
Configure Equinox H.323 Edge Client as
a neighbor in the UI of the enterprise
gatekeeper. Before you begin the
configuration, get the following
information:
• The local zone prefix of the main
Equinox H.323 Edge gatekeeper.
• The Equinox H.323 Edge Client IP
address.
• The Equinox H.323 Edge Client RAS
port number. The default port number
is 1719.
• The Equinox H.323 Edge Client name.
5
Configure the communications between
enterprise gatekeepers and endpoints
and Equinox H.323 Edge to be
transmitted through Equinox H.323 Edge
Client.
See Authorizing Communication with
the Equinox H.323 Edge server Via the
Avaya Equinox H.323 Edge Client on
page 54
Table continues…
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
50
Installing the Avaya Equinox H.323 Edge Client On a Windows Platform
No.
Task
Link/Notes
6
Configure a connection between Equinox See Configuring a Connection to an
H.323 Edge Client and Equinox H.323
Equinox H.332 Edge server on
Edge.
page 55
7
Get the RAS port number that Equinox
H.323 Edge uses to relay messages of
enterprise gatekeepers.
See Getting the RAS port number to
relay messages of enterprise
gatekeepers on page 58
8
Configure an enterprise gatekeeper as
the neighbor of:
See Configuring an enterprise
gatekeeper as a neighbor of the internal
gatekeeper of Equinox Management on
page 59 or Configuring an enterprise
gatekeeper as a neighbor of H.323
Gatekeeper on page 60
• The internal gatekeeper of Equinox
Management.
• H.323 Gatekeeper, if you use H.323
Gatekeeper as the gatekeeper of
Equinox Management.
Installing the Avaya Equinox H.323 Edge Client On a
Windows Platform
About this task
You install the Avaya Equinox H.323 Edge Client by running the Avaya Equinox H.323 Edge Client
installation wizard.
Procedure
1. Locate and double click the H323Edge_Client_9_x_y_z.exe file (where 9_x_y_z
represents the version number).
The Introduction page displays.
Note:
If you try to install the Avaya Equinox H.323 Edge Client on an operating system it
does not support, an error message displays.
2. Select Next.
The License Agreement displays.
3. Select I accept the terms of the license agreement.
4. Select Next.
The Choose Install Folder page displays.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
51
Equinox H.323 Edge Client configuration
5. Select the location where you want to install an instance of the Avaya Equinox H.323 Edge
Client:
• To keep the default setting, select Next.
• To assign a different location, select Choose to browse for a location, then select Next.
The Install Equinox H.323 Edge Client as a Windows Service page displays.
6. Select Install Equinox H.323 Edge Client as a Windows Service to automatically run the
Avaya Equinox H.323 Edge Client on Windows startup.
7. Select Next.
If you perform installation on Windows 2003 operating system, the Windows Clustering
page displays. Select Support Clustering to support Avaya Equinox H.323 Edge Client
redundancy on a Windows server cluster setup.
8. Select Next.
The Pre-Installation Summary page displays.
9. Review the information and confirm disk space availability. If you wish to change any of the
information displayed, select Previous to return to the required installation page.
Otherwise, select Install to start the installation process.
When installation is complete, the Install Complete page displays.
10. Select Done to exit the installation wizard.
Adding Equinox H.323 Edge Client user accounts to
Equinox H.323 Edge
Procedure
1. Log in to Equinox Management.
2. Click Devices.
3. On the left pane, click H.323 Edge Servers, and click the name of the Equinox H.323
Edge instance.
Equinox Management displays the page of the Equinox H.323 Edge instance.
4. Click the Configuration tab.
5. Click Advanced Parameters.
Equinox Management displays the Advanced Parameters window.
6. Select H.323 Edge Client Accounts from the list of advanced commands.
Equinox Management displays the parameters of the advanced command.
7. In Value, enter the login name and password of the user account in the following format:
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
52
Adding enterprise gatekeepers to Equinox H.323 Edge
<Equinox H.323 Edge Client login>=<Password>
8. Click Apply.
9. Click Close.
Result
Equinox Management adds the Equinox H.323 Edge Client user account to Equinox H.323 Edge.
Adding enterprise gatekeepers to Equinox H.323 Edge
About this task
The AddEntGK command to add enterprise gatekeepers is a hidden command in the Advanced
Parameters configuration of Equinox Management
Before you begin
Get the IP address and the port number of the enterprise gatekeeper.
Procedure
1. Log in to Equinox Management.
2. Click Devices.
3. On the left pane, click H.323 Edge Servers, and click the name of the Equinox H.323
Edge instance.
Equinox Management displays the Equinox H.323 Edge instance page.
4. Click the Configuration tab.
5. Click Advanced Parameters.
Equinox Management displays the Advanced Parameters window.
6. Select Enterprise Gatekeepers from the list of advanced commands.
Equinox Management displays the parameters of the advanced command.
7. Click Cancel to enable ID.
8. Do the following:
a. In ID, type AddEntGK.
b. In Value, enter the details of the gatekeeper in the following format:
<Equinox H.323 Edge Client name>{<enterprise gatekeeper IP
address>:<enterprise gatekeeper port number>}
9. Click Apply.
10. Click Close.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
53
Equinox H.323 Edge Client configuration
Result
Equinox Management adds the enterprise gatekeeper to the list of gatekeepers.
Authorizing Communication with the Equinox H.323 Edge
server Via the Avaya Equinox H.323 Edge Client
Before you begin
Before you define the IP addresses authorized to communicate with the Equinox H.323 Edge
server via the Avaya Equinox H.323 Edge Client, note the following:
• Select All registered devices to allow all network devices listed in the Devices tab and all
other H.323 endpoints which use this Avaya Equinox H.323 Edge Client as their gatekeeper
to communicate with the Equinox H.323 Edge server via the Avaya Equinox H.323 Edge
Client.
• There are scenarios in which a local gatekeeper is required at a remote branch. In such
cases, the gatekeeper deployed at the remote site manages the endpoints at the remote site,
while the Avaya Equinox H.323 Edge Client is used for out-of-zone calls (incoming or
outgoing calls) only, as shown in Figure 7: Local Gatekeeper at a Remote Branch on
page 54.
Figure 7: Local Gatekeeper at a Remote Branch
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
54
Configuring a Connection to an Equinox H.323 Edge server
In these cases, you must add the IP address of the enterprise gatekeeper and all endpoints
to the Allow list. If you do not, the media to the endpoints registered to the enterprise
gatekeeper is discarded by the Avaya Equinox H.323 Edge Client and it may not be possible
to establish calls from the Equinox H.323 Edge server to the enterprise gatekeeper.
• When the MCU works with a media processing card (such as the MVP), you must add the IP
address of the media processing card to the Allow list.
Procedure
1. Select the Security tab.
2. Select Add in the Allow area.
The Security Group dialog box opens.
3. To define a single device:
a. Select Single IP.
b. Enter the IP address of the device.
4. To define a range of IP addresses:
a. Select From.
b. Enter the IP address which opens the range.
c. Enter the IP address which closes the range.
5. Select OK.
The defined IP addresses are displayed in the Allow area of the Security tab.
6. Select Start Client to connect the Avaya Equinox H.323 Edge Client to the Equinox H.323
Edge server.
Configuring a Connection to an Equinox H.323 Edge
server
About this task
You can configure a connection to an Equinox H.323 Edge server, to configure additional Avaya
Equinox H.323 Edge servers and to define the name and location of the Avaya Equinox H.323
Edge Client.
During configuration, you can define this client to be located in a private network in the following
cases:
• If the Avaya Equinox H.323 Edge Client is located at an enterprise remote branch
Or
• If the enterprise video conferencing services are supplied by a service provider who owns the
Equinox H.323 Edge server.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
55
Equinox H.323 Edge Client configuration
In some cases, the Avaya Equinox H.323 Edge Client can be located on the public internet to
allow guest users or endpoints which are not part of the enterprise to connect to your video
conferencing network.
Before you begin
Ensure you have the Equinox H.323 Edge server password provided by the Equinox H.323 Edge
server administrator.
Procedure
1. Select the Connection tab.
2. Enter the IP address of the default Equinox H.323 Edge server.
The Avaya Equinox H.323 Edge Client connects to the server’s address you enter in this
field.
3. Enter the port of the default Equinox H.323 Edge server.
4. Select Standby Servers to configure additional Avaya Equinox H.323 Edge servers.
5. Enter the Equinox H.323 Edge server password for connecting the Avaya Equinox H.323
Edge Client to the Equinox H.323 Edge server.
6. Enter a unique name to identify your Avaya Equinox H.323 Edge Client. By default, this
field includes the name of the computer on which the Avaya Equinox H.323 Edge Client is
installed.
Note:
The values in the Server Password and Client Name fields must match the values in
the Password and Name fields defined for the corresponding Client Account in the
Advanced Parameters of the H.323 Edge server managed in Equinox Management. If
no Client Account role is defined on the Equinox H.323 Edge server, the value in the
Client Name field can be any string which is unique on the Equinox H.323 Edge
server’s connected clients list. In this case, the Server Password field must be empty.
7. Select the This client is located on private network check box if the Avaya Equinox H.
323 Edge Client is located in the enterprise LAN. Figure 8: Avaya Equinox H.323 Edge
Client Corporate LAN Deployment on page 57 displays an Avaya Equinox H.323 Edge
Client installed in the main enterprise LAN.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
56
Configuring a Connection to an Equinox H.323 Edge server
Figure 8: Avaya Equinox H.323 Edge Client Corporate LAN Deployment
8. Select Start Client to save all modified configuration data and to connect the Avaya
Equinox H.323 Edge Client to the Equinox H.323 Edge server.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
57
Equinox H.323 Edge Client configuration
Getting the RAS port number to relay messages of
enterprise gatekeepers
About this task
Equinox H.323 Edge uses RAS ports to relay messages of enterprise gatekeepers. You need the
RAS port number that Equinox H.323 Edge uses to configure the enterprise gatekeeper as the
neighbor of H.323 Gatekeeper.
Procedure
1. Log in to Equinox Management.
2. Click Devices.
3. On the left pane, click H.323 Edge Servers, and click the name of the Equinox H.323
Edge instance.
Equinox Management displays the Equinox H.323 Edge instance page.
4. Click the Configuration tab.
5. Click Advanced Parameters.
Equinox Management displays the Advanced Parameters window.
6. Select Enterprise Gatekeepers from the list of advance commands.
Equinox Management displays the parameters of the advance command.
7. Check Value for the RAS port number.
Equinox Management displays the value of the field in the following format:
<Equinox H.323 Edge Client name>{<enterprise gatekeeper IP
address>:<enterprise gatekeeper port number>:<port number@Equinox
H.323 Edge>}
The port number in <port number@Equinox H.323 Edge> is the RAS port number that
Equinox H.323 Edge uses to relay messages of enterprise gatekeepers
Example
The following string is an example of the value that Equinox Management displays in Value where
33079 is the RAS port number:
ex323ec1{10.134.92.3::33079}
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
58
Configuring an enterprise gatekeeper as a neighbor of the internal gatekeeper of Equinox Management
Configuring an enterprise gatekeeper as a neighbor of the
internal gatekeeper of Equinox Management
About this task
Configure the enterprise gatekeeper as a neighbor of the main gatekeeper of Equinox H.323
Edge. This procedure is relevant only if the internal gatekeeper of Equinox Management is
deployed as the main gatekeeper of Equinox H.323 Edge.
Before you begin
Ensure that the internal gatekeeper of Equinox Management is deployed as the main gatekeeper
of Equinox H.323 Edge.
Get the following details:
• The local zone prefix of the enterprise gatekeeper
• The IP address of the internal interface of Equinox H.323 Edge
• The RAS relay port number that Equinox H.323 Edge uses to relay messages of the
enterprise gatekeeper
• The name of the enterprise gatekeeper
Procedure
1. Log in to Equinox Management.
2. Click Settings.
3. On the left pane, under System Preferences, click Local Services.
Equinox Management displays the Local Services page.
4. Click H.323 Gatekeeper.
Equinox Management displays the internal H.323 gatekeeper page.
5. Click Neighbors > Add.
Equinox Management displays the Add Neighbors window.
6. Configure the following fields:
• Prefix
• IP Address
• Port
• Description
7. Click OK.
8. Click Apply.
Result
Equinox Management configures the enterprise gatekeeper as a neighbor of the internal
gatekeeper.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
59
Equinox H.323 Edge Client configuration
Configuring an enterprise gatekeeper as a neighbor of H.
323 Gatekeeper
About this task
Configure the enterprise gatekeeper as a neighbor of the main gatekeeper of Equinox H.323
Edge. This procedure is relevant only if H.323 Gatekeeper is deployed as the main gatekeeper of
Equinox H.323 Edge.
If you configure a third-party gatekeeper as the gatekeeper of Equinox Management, configure the
enterprise gatekeeper as a neighbor in the user interface of the third-party gatekeeper.
Before you begin
Ensure that H.323 Gatekeeper is deployed as the main gatekeeper of Equinox H.323 Edge.
Get the following details:
• The local zone prefix of the enterprise gatekeeper
• The IP address of the internal interface of Equinox H.323 Edge
• The RAS relay port number that Equinox H.323 Edge uses to relay messages of the
enterprise gatekeeper
• The name of the enterprise gatekeeper
Procedure
1. Log in to Equinox Management.
2. Click Devices.
Equinox Management displays the list of all devices.
3. On the left pane, click H.323 Gatekeepers, and click the name of the H.323 Gatekeeper
instance.
Determine the H.323 Gatekeeper instance deployed as the Equinox H.323 Edge
gatekeeper by matching the IP address of the H.323 Gatekeeper instance with the IP
address of the gatekeeper in the Configuration tab of the Equinox H.323 Edge page.
Equinox Management displays the H.323 Gatekeeper instance page.
4. Click the Advanced Configuration tab.
5. Click Neighbors > Add.
Equinox Management displays the Add Neighbors window.
6. Configure the following fields:
• Prefix
• IP Address
• Port
• Description
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
60
Add Neighbors field descriptions
7. Click OK.
8. Click Apply.
Result
Equinox Management configures the enterprise gatekeeper as a neighbor of H.323 Gatekeeper.
Add Neighbors field descriptions
Name
Description
Prefix
The local zone prefix of the enterprise gatekeeper.
IP Address
The IP address of the internal interface of Equinox
H.323 Edge.
Get the IP address from the Info tab of the Equinox
H.323 Edge page.
Port
The RAS relay port number that Equinox H.323
Edge uses to relay messages of the enterprise
gatekeeper.
Description
The name of the enterprise gatekeeper.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
61
Chapter 7: Optimization and scalability
Optimization and scalability with server clusters
Equinox H.323 Edge supports configuring server clusters in Equinox Management for large
deployments. The Equinox H.323 Edge virtual machine clustering mechanism provides high
availability and scalability without external load balancers. The virtual machine clustering
mechanism supports only dual-NIC deployments of Equinox H.323 Edge.
The ideal Equinox H.323 Edge server clusters have maximum 20 servers. Administrators can
create clusters of servers that have:
• Dual NIC enabled.
• Configured with the same subnet and connected to the same VMware vSwitch.
• Configured with the same application settings for gatekeeper, direct publication, NAT, and
license capacity.
Creating an Equinox H.323 Edge server Cluster
About this task
You can create a cluster of Equinox H.323 Edge servers. H.323 Edge server clusters enable you
to increase your call volume. Equinox Management treats a cluster as if it is a single server, so if
you have three servers in a cluster, the cluster can handle three times as many calls as a single H.
323 Edge server.
Note:
The built-in virtual machine clustering mechanism relies on a multicast MAC address to
distribute the network traffic to all the virtual machines. Typically, network routers and firewalls
deny multicast MAC addressing. You might need to update the router and firewall policy for
the clustering mechanism to work.
Before you begin
Ensure that you have more than one H.323 Edge server configured in your deployment.
Procedure
1. Access the Equinox Management administrator portal.
2. Select Devices > Devices by Type > Media & Signaling > H.323 Edge Servers.
The H.323 Edge Servers page appears.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
62
Optimization and scalability with server clusters
Figure 9: H.323 Edge Servers Page
3. Select Create a Cluster.
The Create a Cluster dialog box appears:
Figure 10: Create a Cluster Dialog Box
4. Configure a Cluster Name and Public IP Address in the relevant fields, and select the
check boxes of the servers you want to add to the cluster.
5. Select Apply.
The cluster appears in the list on the H.323 Edge Servers page.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
63
Optimization and scalability
Figure 11: H.323 Edge Server Cluster
A cluster has one of the following statuses:
• Green: Normal
• Yellow: Alarm
Note:
If the cluster is deployed inside a private address DMZ, the cluster’s public IP address
must be mapped to an actual global IP address. The global IP address must be must
be configured to the public IP address in the NAT support section of the cluster’s H.323
Edge server.
If the cluster is deployed in the public network, the cluster’s IP address does not need
to be mapped and therefore can be set to the public IP address in the NAT support
section of the cluster’s H.323 Edge server.
6.
Deleting an Equinox H.323 Edge server Cluster
About this task
You can delete an H.323 Edge server cluster in Equinox Management. You must ensure that all of
the cluster’s servers are online before deleting the cluster. When deleting a cluster, the servers in
the cluster remain in the system, but they no longer exist as a cluster.
Servers that exist in a cluster cannot be deleted from the server list on the H.323 Edge Servers
page.
Before you begin
Ensure that you have created an H.323 Edge server cluster, as described in Creating an Equinox
H.323 Edge server Cluster on page 47.
Procedure
1. Access the Equinox Management administrator portal.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
64
Optimization and scalability with hardware load balancers
2. Select Devices > Devices by Type > Media & Signaling > H.323 Edge Servers.
The H.323 Edge Servers page appears.
Figure 12: H.323 Edge Servers Page
3. In the Action column, select the delete icon
for the cluster you want to delete.
4. Select Yes in the confirmation dialog box to delete the cluster.
Optimization and scalability with hardware load balancers
You can provide both scalability and high availability for your Equinox H.323 Edge servers by
deploying multiple Equinox H.323 Edge 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 Equinox H.323 Edge 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
Equinox H.323 Edge server has too many incoming calls at a given time, for example, another
Equinox H.323 Edge 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 13: Load balancing Equinox H.323 Edge server in the enterprise’s DMZ on page 66
illustrates a typical deployment of multiple Equinox H.323 Edge servers with a load balancer.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
65
Optimization and scalability
Figure 13: Load balancing Equinox H.323 Edge server in the enterprise’s DMZ
Load balancing multiple Equinox H.323 Edge 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 13: Load balancing Equinox H.323 Edge server
in the enterprise’s DMZ on page 66.
In each case, the deployment requires the following components:
• Equinox H.323 Edge 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
Equinox H.323 Edge server:
- The first NIC connects to a DMZ switch along with the load balancer
- The second NIC connects to the company’s internal network
Equinox H.323 Edge 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).
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
66
Optimization and scalability with hardware load balancers
The following load balancers are certified for the current version of Avaya Equinox H.323
Edge:
- Radware AppDirector
- F5 BIG-IP Load Traffic Manager (LTM)
Avaya Equinox H.323 Edge 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. Equinox Management includes a built-in Avaya Equinox H.
323 Gatekeeper, while H.323 Gatekeeper 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 Equinox
H.323 Edge server do so via the cluster’s virtual IP address or register to the Avaya Equinox
H.323 Edge Client if they are not H.460-compliant. The Avaya Equinox H.323 Edge Client
registers to the Equinox H.323 Edge server via the cluster’s virtual IP address.
For information on the components that are part of the Equinox Solution, see the Equinox Solution
Guide.
Workflow to Configure Equinox H.323 Edge for Redundancy
About this task
To configure the main components required for Equinox H.323 Edge redundancy, perform the
tasks as they are listed in the workflow below. All Equinox H.323 Edge servers in the cluster must
be configured identically.
The following load balancers are certified for the current version of Avaya Equinox H.323 Edge:
• Radware AppDirector
• F5 BIG-IP Load Traffic Manager (LTM)
Avaya Equinox H.323 Edge redundancy can also be managed using other third-party load
balancers.
Procedure
1. Install and configure one of the Equinox H.323 Edge.
2. Test the deployment’s operability to verify that the Equinox Solution functions with a single
Equinox H.323 Edge instance.
You can now deploy multiple servers behind a load balancer by going through the tasks
listed below.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
67
Optimization and scalability
3. Configure your load balancer to work with Equinox H.323 Edge, as follows:
• If configuring the Radware AppDirector, see Configuring the Radware AppDirector load
balancer for Equinox H.323 Edge on page 68.
• If configuring the F5 BIG-IP LTM, see Configuring the F5 BIG-IP LTM for Equinox H.323
Edge on page 70.
4. Configure Equinox H.323 Edge to work with the load balancer, as described in Configuring
settings for load balancers on page 73.
5. For each Equinox H.323 Edge in the cluster, perform the necessary configurations
described in Equinox H.323 Edge initial configuration checklist on page 25.
Configuring the Radware AppDirector load balancer for Equinox
H.323 Edge
About this task
The procedure in this topic describes the initial settings required for the Radware AppDirector to
function with Equinox H.323 Edge. For the detailed configuration of the load balancer, see
Radware’s AppDirector documentation.
Radware AppDirector is one of the load balancers that was certified for this release of the Equinox
H.323 Edge deployment.
See Optimization and scalability with hardware load balancers on page 65 for an overview of
scalability and load balancing with Equinox H.323 Edge.
Before you begin
Important:
This procedure should only be performed by certified Radware implementation specialists.
This section focuses only on the settings which may be different from a standard Radware
implementation. For more information on standard Radware deployments, see the Radware
documentation.
Verify that you have all the IP addresses of Equinox H.323 Edge, required to configure the load
balancer.
Procedure
1. Log in to the AppDirector user interface.
2. Create a server farm for Equinox H.323 Edge servers in the load balancer, as described in
the AppDirector documentation. A farm is the term used by AppDirector to refer to a cluster
of servers.
The settings described below are specific to Equinox H.323 Edge server and may differ
from a typical AppDirector deployment:
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
68
Optimization and scalability with hardware load balancers
Table 4: Virtual farm settings specific to Equinox H.323 Edge server
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 Avaya
Equinox H.323 Edge Client, depending on whether the
endpoint is connecting directly or via the Avaya Equinox H.323
Edge 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 Equinox H.323 Edge instance, in turn.
• Least Amount of Traffic: Directs endpoint service requests
to the Equinox H.323 Edge 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 Equinox H.
323 Edge 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
Equinox H.323 Edge 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 request’s 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 Equinox H.323 Edge 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 Equinox H.323 Edge instance to the farm as described in the AppDirector
documentation.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
69
Optimization and scalability
The settings described below are specific to Equinox H.323 Edge 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 Equinox H.323 Edge, add the farm's virtual IP
address and service port to the organization's firewalls.
7. Continue with Configuring settings for load balancers on page 73 to configure Equinox H.
323 Edge to function with a load balancer.
Configuring the F5 BIG-IP LTM load balancer for Equinox H.323
Edge
About this task
The procedure in this topic describes the settings required for the F5 BIG-IP Load Traffic Manager
(LTM) to function with Equinox H.323 Edge. For the detailed configuration of the load balancer,
see the F5’s documentation.
The F5 BIG-IP LTM is one of the load balancers that was certified for this release of the Equinox
H.323 Edge deployment.
Before you begin
Important:
This procedure should only be performed by certified F5 BIG-IP LTM implementation
specialists. This section focuses only on the settings which may be different from a standard
implementation, and does not elaborate on specific F5 terminology necessary to understand
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 Equinox H.323 Edge 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 Equinox H.323 Edge 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.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
70
Optimization and scalability with hardware load balancers
4. Add a Node for each Equinox H.323 Edge instance 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 Equinox H.323 Edge instances 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 Equinox H.323 Edge pool settings, as described in the F5 documentation.
The settings described below are specific to Equinox H.323 Edge and may differ from a
typical F5 deployment:
Table 5: Pool settings specific to Equinox H.323 Edge server
Field
Description
Configuration
From the list, select Advanced.
Name
Enter a name to identify this as the Equinox H.323 Edge cluster,
such as Avaya Equinox H.323 Edge_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 Equinox H.323 Edge server, in turn.
Node List
Select this option. A list of the Equinox H.323 Edge servers you
added as nodes appears.
Service Port
Enter 0 to indicate that this field should not be used. The Equinox
H.323 Edge server's service port is configured on the firewall.
New Members
Add each Equinox H.323 Edge 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 Equinox H.323 Edge and may differ from a
typical F5 deployment:
Table 6: Gateway pool settings specific to Equinox H.323 Edge
Field
Description
Configuration
From the list, select Advanced.
Name
Enter a name to identify this as the gateway cluster, such as
Gateway_Pool.
Table continues…
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
71
Optimization and scalability
Field
Description
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 Equinox
H.323 Edge 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 Equinox H.323 Edge pool, as described in
the F5 documentation.
9. Add a virtual server, which includes all Equinox H.323 Edge instances 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 Equinox H.323 Edge and may differ from a
typical F5 deployment:
Table 7: Virtual server settings specific to Equinox H.323 Edge server
Field
Description
Default Pool
From the list, select the Equinox H.323 Edge 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 Equinox H.323 Edge server.
11. Configure static network address translation (SNAT) to translate the source IP from an
actual Equinox H.323 Edge 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 Equinox H.323 Edge and may differ from a
typical F5 deployment:
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
72
Optimization and scalability with hardware load balancers
Table 8: SNAT settings specific to Equinox H.323 Edge
Field
Description
Name
Enter a name to identify this as the NAT for the Equinox H.
323 Edge cluster, such as Avaya Equinox H.323
Edge_SNAT.
Translation
Select IP address from the list and enter the IP address of
the Avaya Equinox H.323 Edge virtual server you just
created.
Origin
Select Address List from the list.
Type
Select Host.
Address
Add the IP addresses of the Equinox H.323 Edge servers in
the pool.
12. To ensure communication is possible with Equinox H.323 Edges, add the IP address and
service port of the Equinox H.323 Edge virtual server to the organization's firewalls.
13. Continue with Configuring settings for load balancers on page 73 to configure Equinox H.
323 Edge to function with a load balancer.
Configuring settings for load balancers
About this task
This procedure describes how to configure Equinox H.323 Edge instances in the cluster to
function with the load balancer. All Equinox H.323 Edge servers in the cluster must be configured
identically.
The following load balancers are certified for the current version of Avaya Equinox H.323 Edge:
• Radware AppDirector
• F5 BIG-IP Load Traffic Manager (LTM)
Avaya Equinox H.323 Edge redundancy can also be managed using other third-party load
balancers.
For more information, see:
• Optimization and scalability with hardware load balancers on page 65 for an overview of
scalability and load balancing with Equinox H.323 Edge instances.
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 Equinox H.323
Edge.
• The load balancer's documentation.
Before you begin
Verify the default gateway of each Equinox H.323 Edge is set to the native IP address of the load
balancer.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
73
Optimization and scalability
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
Equinox Management displays the Equinox H.323 Edge instance page.
3. Click the Configuration tab.
4. In the NAT Support section, select Enabled.
5. Enter the IP address in Public IP Address.
Configure NAT support for each Equinox H.323 Edge in the cluster, as follows:
Table 9: Configuring 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 Equinox H.323 Edge.
This is mandatory when deploying Equinox H.323 Edge
with a load balancer.
Address
Enter the VIP of the Equinox H.323 Edge 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 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 Equinox
H.323 Edge cluster's external NIC.
Port
If required, change the Avaya Equinox H.323 Edge Client
port number which is set to 3089 by default.
6. Click Apply.
Equinox Management displays a confirmation message.
7. Click Yes.
Next steps
For each Equinox H.323 Edge in the cluster, perform the necessary configurations described in
Equinox H.323 Edge initial configuration checklist on page 25.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
74
Chapter 8: Performing Maintenance
Procedures
This section details to the ongoing administrator tasks required to maintain your video network:
Related links
Updating, Backing Up and Restoring the Equinox H.323 Edge server on page 75
Managing Logs on page 79
Updating, Backing Up and Restoring the Equinox H.323
Edge server
You should back up your application and system configuration files on a regular basis. It is general
practice to back up the latest configuration before performing maintenance procedures such as an
upgrade.
Depending on your support contract, you can update the Avaya Equinox H.323 Edge server
application to:
• The next major version.
Updating a major version requires a new license.
This kind of update changes one of the first two digits in a version number. For example,
updating from version 7.7 to version 8.2 requires a new license.
• An incremental version.
Updating an incremental version does not require a new license.
This kind of update changes the third, fourth and fifth digits in the version number. For
example, updating from 8.2.0.0.29 to 8.2.0.0.34 does not require a new license.
The update procedure may vary depending on the release number and the size of the jump from
the current installation to the new release.
For details about updating, backing up, restoring the Equinox H.323 Edge server application and
its operating system, see the following topics:
Related links
Performing Maintenance Procedures on page 75
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
75
Performing Maintenance Procedures
Backing up the Equinox H.323 Edge server on page 76
Restoring the Equinox H.323 Edge server on page 76
Backing up the Equinox H.323 Edge server
About this task
Back up the Equinox H.323 Edge configuration to a single file. You can use the saved
configuration file to restore the settings to the current Equinox H.323 Edge or to configure a similar
Equinox H.323 Edge.
The backup process is different from generating Customer Support Package. You can restore the
system configuration only from the backup file. You cannot restore the server configuration of
Release 9.1 with backup files of earlier releases. Similarly, you cannot restore the server
configuration of earlier releases with the Release 9.1 backup file.
Procedure
1. Log in to Equinox Management.
2. Click Devices.
3. In the left pane, select H.323 Edge Servers.
Equinox Management displays the list of Equinox H.323 Edge instances.
4. Select an Equinox H.323 Edge instance.
5. Click Manage > Retrieve Configuration File.
Equinox Management displays the Retrieve Configuration window.
6. Click OK.
Result
Equinox Management saves the configuration.
Related links
Updating, Backing Up and Restoring the Equinox H.323 Edge server on page 75
Restoring the Equinox H.323 Edge server
About this task
You cannot restore the server configuration from Customer Support Package. You can restore the
configuration only from a backup file.
You cannot restore the server configuration of Release 9.1 with backup files of earlier releases.
Similarly, you cannot restore the server configuration of earlier releases with the Release 9.1
backup file.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
76
Updating, Backing Up and Restoring the Equinox H.323 Edge server
Procedure
1. Log in to Equinox Management.
2. Click Devices.
3. In the left pane, select H.323 Edge Servers.
Equinox Management displays the list of Equinox H.323 Edge instances.
4. Select an Equinox H.323 Edge instance.
5. Click Manage > Update Configuration File.
Equinox Management displays the Update Configuration window.
6. Select the configuration file.
7. Click Apply.
The restore procedure permanently deletes the current configuration and disconnects all
active conferences.
Result
Equinox Management restores the configuration and restarts Equinox H.323 Edge.
Related links
Updating, Backing Up and Restoring the Equinox H.323 Edge server on page 75
Creating an automatic backup schedule for the Equinox H.323
Edge server
Procedure
1. Log in to Equinox Management.
2. Click Settings.
3. On the left pane, click Maintenance > Backup.
Equinox Management displays the Backup window.
4. Select Enable Auto Backup.
5. Click H.323 Edge Server’s Configuration Files.
6. Set the following automatic backup options:
• Frequency
• Start
• Destination
• Maximum storage size allocated to the backup data disk (MB): When the backup
files use up the allocated size, Equinox Management overwrites the oldest backup files
with the new files.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
77
Performing Maintenance Procedures
Filtering and Monitoring Events in Equinox H.323 Edge
About this task
You can view the Equinox H.323 Edge events and alerts in Equinox Management. You can add
filters to the log that Equinox H.323 Edge generates to customize the list to display certain types of
events or alerts. An event can be:
• An information notice about the Equinox H.323 Edge behavior or status. For example, the
time and date when Equinox H.323 Edge started or when users log in to Equinox H.323
Edge.
• A warning or error indicating a problem that affects the Equinox H.323 Edge operation and
needs the administrator's intervention.
Equinox H.323 Edge clears a warning or error automatically when the problem is resolved and
informs Equinox Management that the alarm is no longer relevant.
Note:
You can manage Equinox H.323 Edge from only one management system. If you want to
manage Equinox H.323 Edge from a third-party management system, you must disconnect
Equinox Management.
For more information about:
• Equinox Management, see Administrator Guide for Avaya Equinox Management.
• Third-party event or managing servers, contact Avaya at https://support.avaya.com.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and click the name of the Equinox H.323 Edge instance.
Equinox Management displays the Equinox H.323 Edge instance window.
3. Click the Events tab.
4. (Optional) To filter the list of events by the severity, click the severity drop-down list, and
select one of the following options:
• All
• Information
• Warning
• Critical
5. (Optional) To filter the list of events by the duration, click the duration drop-down list, and
select one of the following options:
• 1 Week
• 1 Day
• 1 Hour
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
78
Managing Logs
6. (Optional) To hide repeated events, click Hide repeated events.
Managing Logs
Logs are important for troubleshooting. This section describes the log managing provided in the
Avaya Equinox H.323 Edge server:
Related links
Performing Maintenance Procedures on page 75
Configuring the log recording level on page 79
Downloading Customer Support Package on page 80
Configuring the log recording level
About this task
Log files contain important information for troubleshooting the system. You can set the level of logs
in Equinox H.323 Edge. You can also define the size and number of log files kept on the hard disk
of Equinox H.323 Edge for further troubleshooting.
Procedure
1. Log in to Equinox Management.
2. Click Devices, and select the Equinox H.323 Edge instance.
Equinox Management displays the Equinox H.323 Edge instance page.
3. Click Configuration.
4. In Logging, select one of the following log levels in Logging Level.
Field Name
Description
Detail
Saves call details, warnings, and critical system errors to the log file.
Warning
Saves warnings issued by the system and critical system errors to the
log file.
Error
Saves critical system errors only to the log file.
Disabled
Disables the Equinox H.323 Edge logging.
5. Click Apply.
6. Click Advanced Parameters
Equinox Management displays the Advanced Parameters window.
7. Configure the following parameters:
• Log File Size: The size of an individual log file is configured to 500KB by default. The
maximum size of an individual log file is 10000KB.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
79
Performing Maintenance Procedures
• Log File Number: The maximum number of log files that are kept on Equinox H.323
Edge 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 79
Downloading Customer Support Package
About this task
Customer support might ask you to send logs of Equinox H.323 Edge to diagnose issues.
Customer Support Package contains logs and server configuration, which include the following:
• Application and operating system configuration
• Application and operating system logs
• Operating system run time information, such as CPU usage, memory usage, and networking
status
• Application run time information, such as memory status and other details.
Note:
You cannot restore the server configuration from Customer Support Package. You can restore
the configuration only from a backup file.
Procedure
1. Log in to Equinox Management.
2. Click Devices.
3. On the left pane, click H.323 Edge Servers.
4. Select the check box next to the Equinox H.323 Edge instance.
5. Click Manage > Retrieve Customer Support Package.
6. Select one of the following options, and configure the values:
• Capture last: Enter the total minutes.
• Capture from: Enter the date range.
7. Click Generate.
Related links
Managing Logs on page 79
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
80
Chapter 9: Resources
Documentation
See the following related documents at http://support.avaya.com.
Title
Use this document to:
Audience
Deploying Avaya Equinox Solution
Plan for and deploy Avaya Equinox
Solution
Partners, Services,
and Support
personnel
Deployment Guide for Avaya
Equinox H.323 Edge
Plan for and deploy Avaya Equinox H.323
Edge
Partners, Services,
and Support
personnel
Deployment Guide for Avaya
Scopia® XT Series
Plan for and deploy Avaya Scopia® XT
Series
Partners, Services,
and Support
personnel
Deployment Guide for XT
Telepresence
Plan for and deploy XT Telepresence
Partners, Services,
and Support
personnel
Deployment Guide for Avaya Video
Collaboration Solution for IP Office
Plan for and deploy Avaya Video
Collaboration Solution for IP Office
Partners, Services,
and Support
personnel
Deployment Guide for Avaya
Equinox Add-in for IBM Lotus Notes
Plan for and deploy Avaya Equinox Add-in
for IBM Lotus Notes
Partners, Services,
and Support
personnel
Avaya Equinox Solution Guide for
Small to Medium (SMB) Enterprises
Plan for and deploy Avaya Equinox
Solution for small and medium enterprises
Partners, Services,
and Support
personnel
Avaya Equinox Solution Guide for
Medium to Large Enterprises
Plan for and deploy Avaya Equinox
Solution for medium and large enterprises
Partners, Services,
and Support
personnel
Avaya Equinox Solution Guide for
Large Enterprises and Service
Providers
Plan for and deploy Avaya Equinox
Solution for large enterprises and service
providers
Partners, Services,
and Support
personnel
Implementing
Table continues…
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
81
Resources
Title
Use this document to:
Audience
Installation Notes — Discovering the
IP address of the XT Server
Install XT Server
Partners, Services,
and Support
personnel
Rack Mounting Guide for Avaya
Scopia® Elite 6000 MCU
Install the Avaya Scopia® Elite 6000 MCU
hardware
Partners, Services,
and Support
personnel
Administrator Guide for Avaya
Scopia® Elite 6000 MCU
Perform administration tasks for Avaya
Scopia® Elite 6000 MCU
System
administrators
Administrator Guide for Avaya
Scopia® Elite 6000 MCU for Avaya
Aura® Power Suite
Perform administration tasks for Avaya
Scopia® Elite 6000 MCU for Avaya Aura®
Power Suite
System
administrators
Administering Avaya Equinox Media
Server
Perform administration tasks for Avaya
Equinox Media Server
System
administrators
Administrator Guide for Avaya
Equinox Management
Perform administration tasks for Avaya
Equinox Management
System
administrators
Administrator Guide for Avaya
Equinox Streaming and Recording
Server
Perform administration tasks for Avaya
Equinox Streaming and Recording Server
System
administrators
Quick Setup Guide for Avaya
Scopia® XT5000 Codec Only
Perform administration tasks for the Avaya
Scopia® XT5000 codec
System
administrators
Avaya Scopia® XT5000 Codec Only
Perform administration tasks for the Avaya
Scopia® XT5000 codec
System
administrators
Avaya Scopia® XT Executive 240
Perform administration tasks for Avaya
Scopia® XT Executive 240
System
administrators
Avaya Scopia® XT5000 Server for
IP Office
Perform administration tasks for Avaya
Scopia® XT5000 Server for IP Office
System
administrators
Avaya Scopia® XT Premium 3–way
Microphone Pod
Perform administration tasks for Avaya
Scopia® XT Premium 3–way Microphone
Pod
System
administrators
Avaya Scopia® XT4300
Perform administration tasks for Avaya
Scopia® XT4300
System
administrators
Avaya Scopia® XT4300 Codec Only
Perform administration tasks for the Avaya
Scopia® XT4300 codec
System
administrators
Avaya Scopia® XT7100 Codec Only
Perform administration tasks for the Avaya
Scopia® XT7100 codec
System
administrators
Avaya Scopia® XT Deluxe Camera
Perform administration tasks for Avaya
Scopia® XT Deluxe Camera
System
administrators
Avaya Scopia® XT Flex Camera
Perform administration tasks for Avaya
Scopia® XT Flex Camera
System
administrators
Quick Tips for Avaya Scopia® XT
Series
Perform administration tasks for Avaya
Scopia® XT Series
System
administrators
Administering
Table continues…
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
82
Documentation
Title
Use this document to:
Audience
Reference Guide for Avaya Equinox
Management XML API
Understand how to perform administration
tasks on Avaya Equinox Management
System
administrators,
Customers, Partners,
Services, and
Support personnel
SAMPLE Reference Guide for
Avaya Equinox Management XML
API
Understand how to perform administration
tasks on Avaya Equinox Management
System
administrators,
Customers, Partners,
Services, and
Support personnel
Reference Guide for Avaya Equinox
Management SNMP Traps
Understand how to configure Avaya
Equinox Management to send information
to a remote SNMP management client of its
operational status
System
administrators,
Customers, Partners,
Services, and
Support personnel
Reference Guide for Avaya Equinox
Management CDR Files
Understand how to perform administration
tasks on Avaya Equinox Management
System
administrators,
Customers, Partners,
Services, and
Support personnel
Reference Guide for Port Security
for Avaya Equinox Solution
Understand how to perform the
administration tasks on Avaya Equinox
Solution
System
administrators,
Customers, Partners,
Services, and
Support personnel
Purchasing Guide for AvayaLive™
Video
Understand how to purchase AvayaLive™
Video
System
administrators,
Customers, Partners,
Services, and
Support personnel
Using Avaya Equinox Unified Portal
Understand the features of and use Avaya
Equinox Unified Portal
Customers
User Guide for Avaya Equinox H.
323 Edge Client
Understand the features of and use Avaya
Equinox H.323 Edge Client
Customers
User Guide for Avaya Scopia® XT
Series
Understand the features of and use Avaya
Scopia® XT Series
Customers
User Guide for Avaya Equinox
Management
Understand the features of and use Avaya
Equinox Management
Customers
User Guide for Avaya Equinox Addin for IBM Lotus Notes
Understand the features of and use Avaya
Equinox Add-in for IBM Lotus Notes
Customers
Supporting
Using
Table continues…
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
83
Resources
Title
Use this document to:
Audience
User Guide for Avaya Equinox Addin for Microsoft Outlook
Understand the features of and use Avaya
Equinox Add-in for Microsoft Outlook
Customers
User Guide for Avaya Equinox Addin for Microsoft Outlook for Avaya
Aura® Power Suite
Understand the features of and use Avaya
Equinox Add-in for Microsoft Outlook for
Avaya Aura® Power Suite
Customers
User Guide for Avaya Scopia®
Control
Understand the features of and use Avaya
Scopia® Control
Customers
Finding documents on the Avaya Support website
Procedure
1. Navigate to http://support.avaya.com/.
2. At the top of the screen, type your username and password and click Login.
3. Click Support by Product > Documents.
4. In Enter your Product Here, type the product name and then select the product from the
list.
5. In Choose Release, select an appropriate release number.
6. In the Content Type filter, click a document type, or click Select All to see a list of all
available documents.
For example, for user guides, click User Guides in the Content Type filter. The list
displays the documents only from the selected category.
7. Click Enter.
Training
The following courses are available on the Avaya Learning website at http://www.avayalearning.com. After logging in to the website, enter the course code or the course title in the
Search field and press Enter or click > to search for the course.
Course code
Course title
Avaya Equinox administration training course
2038W
Avaya Equinox Administration
Avaya Equinox Team Engagement solution courses
3140W
Avaya Equinox Solutions Overview
3170W
Avaya Equinox Solutions Customer Field Study
Table continues…
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
84
Support
Course code
Course title
3171T
APDS Avaya Enterprise Team Engagement Solutions Online Test
Avaya Equinox Over The Top solution courses
3281W
Avaya Video Conferencing Solutions Overview
3283W
Avaya Video Conferencing Solutions Customer Field Study
3271T
APDS Avaya Video Conferencing Solutions Online Test
Avaya Equinox Sales course
3140WD02
Designing Avaya Equinox Clients & Breeze Client SDK Sales Readiness Quiz
3140WD03
Avaya Equinox Sales Readiness — Design Delta Training
Support
Go to the Avaya Support website at http://support.avaya.com for the most up-to-date
documentation, product notices, and knowledge articles. You can also search for release notes,
downloads, and resolutions to issues. Use the online service request system to create a service
request. Chat with live agents to get answers to questions, or request an agent to connect you to a
support team if an issue requires additional expertise.
Using the Avaya InSite Knowledge Base
The Avaya InSite Knowledge Base is a web-based search engine that provides:
• Up-to-date troubleshooting procedures and technical tips
• Information about service packs
• Access to customer and technical documentation
• Information about training and certification programs
• Links to other pertinent information
If you are an authorized Avaya Partner or a current Avaya customer with a support contract, you
can access the Knowledge Base without extra cost. You must have a login account and a valid
Sold-To number.
Use the Avaya InSite Knowledge Base for any potential solutions to problems.
1. Go to http://www.avaya.com/support.
2. Log on to the Avaya website with a valid Avaya user ID and password.
The system displays the Avaya Support page.
3. Click Support by Product > Product Specific Support.
4. In Enter Product Name, enter the product, and press Enter.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
85
Resources
5. Select the product from the list, and select a release.
6. Click the Technical Solutions tab to see articles.
7. Select relevant articles.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
86
Glossary
1080p
See Full HD on page 90.
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.
720p
See HD on page 92.
AAC
AAC is an audio codec which compresses sound but with better results
than MP3.
AGC (Automatic Gain
Control)
Automatic Gain Control (AGC) smooths audio signals through
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.
Alias
An alias in H.323 represents the unique name of an endpoint. Instead of
dialing an IP address to reach an endpoint, you can dial an alias, and the
gatekeeper resolves it to an IP address.
Auto-Attendant
Auto-Attendant is a video-based IVR which provides quick access to
meetings through a set of visual menus. Participants can select the DTMF
tone-based menu options using the standard numeric keypads of
endpoints. Auto-Attendant works with H.323 and SIP endpoints.
Avaya Scopia
Content Slider
See Content Slider on page 88.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
87
Glossary
Balanced
Microphone
A balanced microphone uses a cable that is built to reduce noise and
interference even when the cable is long. This reduces audio disruptions
resulting from surrounding electromagnetic interference.
BFCP (Binary Floor
Control Protocol)
BFCP is a protocol which coordinates shared videoconference features in
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. Bitrate is often measured in
kilobits per second (kbps).
Call Control
See Signaling on page 98.
Cascaded
Videoconference
A cascaded videoconference is a meeting distributed over more than one
physical Scopia Elite MCU and/or Equinox Media Server, where a master
MCU/Media Server connects to one or more slave MCUs/Media Servers
to create a single videoconference. It increases the meeting capacity by
combining the resources of several MCUs/Media Servers. This can be
especially useful for distributed deployments across several locations,
reducing bandwidth usage.
CIF
CIF, or Common Intermediate Format, describes a video resolution of 352
× 288 pixels (PAL) or 352 x 240 (NTSC). This is sometimes referred to as
Standard Definition (SD).
Content Slider
The Avaya Scopia Content Slider stores the data already presented in the
videoconference and makes it available for participants to view during the
meeting.
Continuous
Presence
Continuous presence enables viewing multiple participants of a
videoconference at the same time, including the active speaker. This
graphics-intensive work requires scaling and mixing the images together
into one of the predefined video layouts. The range of video layouts
depends on the type of media processing supported, typically located in
the MCU/Media Server.
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
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
88
CP
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.
CP
See Continuous Presence on page 88.
Dedicated Endpoint
A dedicated endpoint is a hardware endpoint for videoconferencing
assigned to a single user. It is often referred to as a personal or executive
endpoint, and serves as the main means of video communications for this
user. For example, XT Executive. It is listed in the organization's LDAP
directory as associated exclusively with this user.
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.
Distributed
Deployment
A distributed deployment describes a deployment where the solution
components are geographically distributed in more than one network
location.
DNS Server
A DNS server is responsible for resolving domain names in your network
by translating them into IP addresses.
DTMF
DTMF, or touch-tone, is the method of dialing on touch-tone phones,
where each number is translated and transmitted as an audio tone.
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
Layout
The dynamic video layout is a meeting layout that switches dynamically to
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 and/or
Equinox Media Server). The largest image always shows the active
speaker.
E.164
E.164 is an address format for dialing an endpoint with a standard
telephone numeric keypad, which only has numbers 0 - 9 and the
symbols: * and #.
Endpoint
An endpoint is a tool through which people can participate in a
videoconference. Its display enables you to see and hear others in the
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
89
Glossary
meeting, while its microphone and camera enable you to be seen and
heard by others. Endpoints include dedicated endpoints, like XT
Executive, software endpoints, mobile device endpoints, room systems
like XT Series, and telepresence systems like XT Telepresence.
Endpoint Alias
See Alias on page 87.
FEC
Forward Error Correction (FEC) is a proactive method of sending
redundant information in the video stream to preempt quality degradation.
FEC identifies the key frames in the video stream that should be
protected by FEC. There are several variants of the FEC algorithm. The
Reed-Solomon algorithm (FEC-RS) sends redundant packets per block of
information, enabling the sender (like the Scopia Elite MCU and/or
Equinox Media Server) to manage up to ten percent packet loss in the
video stream with minimal impact on the smoothness and quality of the
video.
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.
Forward Error
Correction
See FEC on page 90.
FPS
See Frames Per Second on page 90.
Frame Rate
See Frames Per Second on page 90.
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.
FTP
The File Transfer Protocol (FTP) is a standard network protocol used to
transfer computer files from one host to another host over a TCP-based
network, such as the Internet. FTP is built on a client-server architecture
and uses separate control and data connections between the client and
the server. FTP users may authenticate themselves using a clear-text
sign-in protocol, normally in the form of a username and password, but
can connect anonymously if the server is configured to allow it.
Full HD
Full HD, or Full High Definition, also known as 1080p, describes a video
resolution of 1920 x 1080 pixels.
Full screen Video
Layout
The full screen view shows one video image. Typically, it displays the
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
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
90
Gateway
initial connection of calls. Gatekeepers also implement the dial plan of an
organization by routing H.323 calls depending on their dial prefixes.
Equinox Management includes a built-in Avaya Equinox H.323
Gatekeeper, while H.323 Gatekeeper is a standalone gatekeeper.
Gateway
A gateway is a component in a video solution which routes information
between two subnets or acts as a translator between different protocols.
For example, a gateway can route data between the headquarters and a
partner site, or between two protocols like the Equinox TIP Gateway, or
the 100 Gateway.
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.263
H.263 is an older a protocol used to compress video. It is an
enhancement to the H.261 protocol.
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 Baseline
Profile
See H.264 on page 91.
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
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
91
Glossary
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 Equinox
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.320
H.320 is a protocol for defining videoconferencing over ISDN networks.
H.323
H.323 is a widespread set of protocols governing the communication
between endpoints in videoconferences and point-to-point calls. It defines
the call signaling, control, media flow, and bandwidth regulation.
H.323 Alias
See Alias on page 87.
H.350
H.350 is the protocol used to enhance LDAP user databases to add video
endpoint information for users and groups.
H.460
H.460 enhances the standard H.323 protocol to manage firewall and NAT
traversal using ITU-T standards. H.460–compliant endpoints can directly
communicate with Equinox H.323 Edge. The endpoints act as H.460
clients and Equinox H.323 Edge acts as an H.460 server.
HD
A HD ready device describes its high definition resolution capabilities of
720p, a video resolution of 1280 x 720 pixels.
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.
High Definition
See HD on page 92.
High Profile
See H.264 High Profile on page 91.
HTTP
The Hypertext Transfer Protocol (HTTP) is an application protocol for
distributed, collaborative, hypermedia information systems. HTTP is the
foundation of data communication for the World Wide Web.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
92
HTTPS
Hypertext is structured text that uses logical links (hyperlinks) between
nodes containing text. HTTP is the protocol to exchange or transfer
hypertext.
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 Equinox
Solution products.
Image Resolution
See Resolution on page 97.
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).
LDAP
LDAP is a widespread standard database format which stores network
users. The format is hierarchical, where nodes are often represented
asbranch location > department > sub-department, orexecutives >
managers > staff members. The database standard is employed by most
user directories including Microsoft Active Directory. H.350 is an
extension to the LDAP standard for the videoconferencing industry.
Lecture Mode
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.
Legacy endpoints
Legacy endpoints are H.323–based endpoints that do not support H.460.
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).
Location
A location is a physical space (building) or a network (subnet) where
video devices can share a single set of addresses. A distributed
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
93
Glossary
deployment places these components in different locations, often
connected via a VPN.
Management
Management refers to the administration messages sent between
components of the Equinox Solution as they manage and synchronize
data between them. Management also includes front-end browser
interfaces configuring server settings on the server. Management
messages are usually transmitted via protocols like HTTP, SNMP, FTP or
XML. For example, Equinox Management uses management messages
to monitor the activities of an MCU/Media Server, or when it authorizes
the MCU/Media Server to allow a call to proceed.
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.
MCU
An MCU, or Multipoint Control Unit, connects several endpoints to a
single videoconference. It manages the audio mixing and creates the
video layouts, adjusting the output to suit each endpoint's capabilities.
MCU service
See Meeting Type on page 94.
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.
Media Control
See Control on page 88.
Meeting Type
Meeting types (also known as MCU/Media Server 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 Avaya Equinox Media Server, with additional properties in
Equinox Management.
Moderator
A moderator has special rights in a videoconference, including blocking
the sound and video of other participants, inviting new participants,
disconnecting others, determining video layouts, and closing meetings.
An owner of a virtual room is the moderator when the room is protected
by a PIN. Without this protection, any participant can assume moderator
rights.
MTU
The MTU, or Maximum Transmission Unit, is the maximum size of data
packets sent around your network. This value must remain consistent for
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
94
Multi-Point
all network components, including servers like the MCU and/or Equinox
Media Server and endpoints like XT Series and other network devices like
network routers.
Multi-Point
A multi-point conference has more than two participants.
Multi-tenant
Service provider, or multi-tenant, deployments enable one installation to
manage multiple organizations. All the organizations can reside as
tenants within a single service provider deployment. For example,
Equinox Management can manage a separate set of users for each
organization, separate local administrators, separate bandwidth policies
etc. all within a single multi-tenant installation.
Multicast Streaming
Multicast streaming sends a videoconference to multiple viewers across a
range of addresses, reducing network traffic significantly. Avaya Equinox®
multicasts to a single IP address, and streaming clients must tune in to
this IP address to view the meeting. Multicasts require that routers,
switches and other equipment know how to forward multicast traffic.
NAT
A NAT, or Network Address Translation device, translates external IP
addresses to internal addresses housed in a private network. This
enables a collection of devices like endpoints in a private network, each
with their own internal IP address, can be represented publicly by a
single, unique IP address. The NAT translates between public and private
addresses, enabling users toplace calls between public network users
and private network users.
NetSense
NetSense is a proprietary Equinox Solution technology which optimizes
the video quality according to the available bandwidth to minimize packet
loss. As the available bandwidth of a connection varies depending on
data traffic, NetSense's sophisticated algorithm dynamically scans the
video stream, and then reduces or improves the video resolution to
maximize quality with the available bandwidth.
OVA
Open Virtualization Appliance. An OVA contains the virtual machine
description, disk images, and a manifest zipped into a single file. The
OVA follows the Distributed Management Task Force (DMTF)
specification.
Over The Top
deployments
Over The Top deployments of Avaya Equinox Solution are independent of
Avaya Aura®. The deployments use port-based licensing.
Over The Top deployments are also called standalone deployments.
Packet Loss
December 2017
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.
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
95
Glossary
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/Media Server 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.
Prefix
See Dial Prefix on page 89.
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
(QoS)
Quality of Service (QoS) determines the priorities of different types of
network traffic (audio, video and control/signaling), so in poor network
conditions, prioritized traffic is still fully transmitted.
Recordings
A recording of a videoconference can be played back at any time.
Recordings include audio, video and shared data (if presented). Users
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
96
Redundancy
can access recordings from the web portal or using a web link to the
recording on the portal.
Redundancy
Redundancy is a way to deploy a network component, in which you
deploy extra units as 'spares', to be used as backups in case one of the
components fails.
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.
Resolution
Resolution, or image/video resolution, is the number of pixels which make
up an image frame in the video, measured as the number of horizontal
pixels x the number of vertical pixels. Increasing resolution improves
video quality but typically requires higher bandwidth and more computing
power. Techniques like SVC, H.264 High Profile and FEC reduce
bandwidth usage by compressing the data to a smaller footprint and
compensating for packet loss.
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.
Room System
A room system is a hardware videoconferencing endpoint installed in a
physical conference room. Essential features include its camera's ability
to PTZ (pan, tilt, zoom) to allow maximum flexibility of camera angles
enabling participants to see all those in the meeting room or just one part
of the room.
RTCP
Real-time Control Transport Protocol, used alongside RTP for sending
statistical information about the media sent over RTP.
RTP
RTP or Real-time Transport Protocol is a network protocol which supports
video and voice transmission over IP. It underpins most
videoconferencing protocols today, including H.323, SIP and the
streaming control protocol known as RTSP. The secured version of RTP
is SRTP.
RTSP
RTSP or Real-Time Streaming Protocol controls the delivery of streamed
live or playback video over IP, with functions like pause, fast forward and
reverse. While the media itself is sent via RTP, these control functions are
managed by RTSP
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
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
97
Glossary
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.
SD
Standard Definition (SD), is a term used to refer to video resolutions
which are lower than HD. There is no consensus defining one video
resolution for SD.
Service
Also known as MCU/Media Server 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
Session Initiation Protocol (SIP) is a signaling protocol for starting,
managing and ending voice and video sessions over TCP, TLS or UDP.
Videoconferencing endpoints typically are compatible with SIP or H.323,
and in some cases (like Avaya Scopia® XT Series), an endpoint can be
compatible with both protocols. As a protocol, it uses fewer resources
than H.323.
SIP Registrar
See Registrar on page 97.
SIP Server
A SIP server is a network device communicating via the SIP protocol.
SIP URI
See URI on page 101.
Slider
See Content Slider on page 88.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
98
SNMP
SNMP
Simple Network Management Protocol (SNMP) is a protocol used to
monitor network devices by sending messages and alerts to their
registered SNMP server.
Software endpoint
A software endpoint turns a computer or portable device into a
videoconferencing endpoint via a software application only. It uses the
system's camera and microphone to send image and sound to the other
participants, and displays their images on the screen.
SQCIF
SQCIF defines a video resolution of 128 x 96 pixels.
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.
SSO
See Single Sign On on page 98.
Standard Definition
See SD on page 98.
Streaming
Streaming is a method to send live or recorded videoconferences in one
direction to viewers. Recipients can only view the content; they cannot
participate with a microphone or camera to communicate back to the
meeting. There are two types of streaming supported in Equinox Solution:
unicast which sends a separate stream to each viewer, and multicast
which sends one stream to a range of viewers.
STUN
A STUN server enables you to directly dial an endpoint behind a NAT or
firewall by giving that computer’s 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.
SVGA
SVGA defines a video resolution of 800 x 600 pixels.
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
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
99
Glossary
switching increases the port capacity of the Scopia Elite MCU and/or
Equinox Media Server 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.
SXGA
SXGA defines a video resolution of 1280 x 1024 pixels.
Team Engagement
deployments
Team Engagement deployments of Avaya Equinox Solution are integrated
with Avaya Aura®. The deployments use user-based licensing for the
main components.
Telepresence
A telepresence system combines two or more endpoints together to
create a wider image, simulating the experience of participants being
present in the same room. Telepresence systems always designate one
of the endpoints as the primary monitor/camera/codec unit, while the
remainder are defined as auxiliary or secondary endpoints. This ensures
that you can issue commands via a remote control to a single codec base
which leads and controls the others to work together as a single
telepresence endpoint.
Telepresence - Dual
row telepresence
room
Dual row telepresence rooms are large telepresence rooms with two rows
of tables that can host up to 18 participants.
TLS
TLS enables network devices to communicate securely using certificates,
to provide authentication of the devices and encryption of the
communication between them.
Transcoding
Transcoding is the process of converting video into different sizes,
resolutions or formats. This enables multiple video streams to be
combined into one view, enabling continuous presence, as in a typical
videoconferencing window.
UC (Unified
Communications)
UC, or unified communications deployments offer solutions covering a
wide range of communication channels. These include audio (voice),
video, text (IM or chat), data sharing (presentations), whiteboard sharing
(interactive annotations on shared data).
Unbalanced
Microphone
An unbalanced microphone uses a cable that is not especially built to
reduce interference when the cable is long. As a result, these unbalanced
line devices must have shorter cables to avoid audio disruptions.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
100
Unicast Streaming
Unicast Streaming
Unicast streaming sends a separate stream of a videoconference to each
viewer. This is the default method of streaming. To save bandwidth,
consider multicast streaming.
Unified Portal
Unified Portal is a graphic user interface (GUI) for Avaya Equinox Solution
users. Using this GUI, users can schedule and attend meetings. They can
also access their recordings and broadcasts. It is the typical way that
users interact with and access Avaya Equinox Streaming and Recording .
There is a user guide for Unified Portal available on https://
support.avaya.com/. Avaya recommends distributing this guide to all
users.
URI
URI is an address format 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, such as <endpoint
name>@<server_domain_name>. For example, 5000@198.51.100.51.
URI Dialing
Accessing a device via its URI on page 101.
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 functionality, and allowed bandwidth for calls.
VFU
See Video Fast Update (VFU) on page 101.
VGA
VGA defines a video resolution of 640 x 480 pixels.
Video Fast Update
(VFU)
Video Fast Update (VFU) is a request for a refreshed video frame, sent
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.
Video Resolution
See Resolution on page 97.
Video Switching
See Switched video on page 99.
Videoconference
A videoconference is a meeting of more than two participants with audio
and video using endpoints. Professional videoconferencing systems can
handle many participants in single meetings, and multiple simultaneous
meetings, with a wide interoperability score to enable a wide variety of
endpoints to join the same videoconference. Typically you can also share
PC content, like presentations, to other participants.
Viewer Portal
The Avaya Equinox Streaming and Recording Viewer Portal is embedded
in the Unified Portal. To access the Viewer Portal, you can select
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
101
Glossary
Recordings and Events on the main page of the Unified Portal. From
the Viewer Portal, you can watch recordings and navigate through the
categories.
Virtual Room
A virtual room 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 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 user’s
virtual room number is often based on that person’s phone extension
number. You can personalize your virtual room with PIN numbers, custom
welcome slides and so on. External participants can use a zero-download
web application 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.
Webcast
A webcast is a streamed live broadcast of a videoconference over the
internet. Enable webcasts by enabling the streaming feature. To invite
users to the webcast, send an email or instant message containing the
webcast link or a link to the Unified Portal and the meeting ID.
WUXGA
WUXGA defines a video resolution of 1920 x 1200 pixels.
XGA
XGA defines a Video resolution of 1024 x 768 pixels.
Zone
Gatekeepers like H.323 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.
December 2017
Deployment Guide for Avaya Equinox H.323 Edge
Comments on this document? infodev@avaya.com
102