Avaya Port Matrix: Avaya Aura Conferencing 8.0

Transcription

1 Avaya Matrix: Avaya Aura Conferencing 8.0 Issue 1.2 April 12, 2016 Avaya Matrix: Avaya Aura Conferencing 8.0. April 2016

2 2013, 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. Avaya or Avaya Channel Partner (as applicable) for more information. Hosted Service THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE, UNDER Documentation disclaimer Documentation means information published in varying mediums which may include product information, operating instructions and performance specifications that are generally made available to users of products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of Documentation unless such modifications, additions, or deletions were performed by or on the express behalf of Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or Documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on Avaya hardware and software. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product while under warranty is available to Avaya customers and other parties through the Avaya Support website: getgenericdetails?detailid=c under the link Warranty & Product Lifecycle or such successor site as designated by Avaya. Please note that if You acquired the product(s) from an authorized Avaya Channel Partner outside of the United s 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 2 Avaya Matrix: Avaya Aura Conferencing 8.0 THE LINK Avaya Terms of Use for Hosted Services OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THE TERMS OF USE. IF YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED SERVICE. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, UNDER THE LINK AVAYA SOFTWARE LICENSE TERMS (Avaya Products) OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Avaya grants You a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type,

3 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 types 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. Named User License (NU). You may: (i) install and use each copy or Instance of the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use each copy or Instance of the Software on a Server so long as only authorized Named Users access and use the Software. Named User, means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya s sole discretion, a Named User may be, without limitation, designated by name, corporate account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Heritage Nortel Software Heritage Nortel Software means the software that was acquired by Avaya as part of its purchase of the Nortel Enterprise Solutions Business in December The Heritage Nortel Software is the software contained within the list of Heritage Nortel Products located at under the link Heritage Nortel Products or such successor site as designated by Avaya. For Heritage Nortel Software, Avaya grants Customer a license to use Heritage Nortel Software provided hereunder solely to the extent of the authorized activation or authorized usage level, solely for the purpose specified in the Documentation, and solely as embedded in, for execution on, or for communication with Avaya equipment. Charges for Heritage Nortel Software may be based on extent of activation or use authorized as specified in an order or invoice. 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: 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, Copyright L.L.C. SEE Avaya Matrix: Avaya Aura Conferencing 8.0 April

4 Service Provider THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER S HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER S HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER S EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER. WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729 CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE THE H.264 (AVC) CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ( AVC VIDEO ) AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE Compliance with Laws You acknowledge and agree that it is Your responsibility for complying with any applicable laws and regulations, including, but not limited to laws and regulations related to call recording, data privacy, intellectual property, trade secret, fraud, and music performance rights, in the country or territory where the Avaya product is used. If You suspect that You are being victimized by Toll Fraud and You need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United s and Canada. For additional support telephone numbers, see the Avaya Support website: or such successor site as designated by Avaya. Security Vulnerabilities Information about Avaya s security support policies can be found in the Security Policies and Support section of support.avaya.com/security. Suspected Avaya product security vulnerabilities are handled per the Avaya Product Security Support Flow ( support.avaya.com/css/p8/documents/ ). Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support. Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, its licensors, its suppliers, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. 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 4 Avaya Matrix: Avaya Aura Conferencing 8.0

5 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. Java is a registered trademark of Oracle and/or its affiliates. Avaya Matrix: Avaya Aura Conferencing 8.0 April

6 1 Conferencing Components The Avaya Aura Conferencing server platform supports the configuration of a single bonded network interface. Each bonded interface consists of two physical Ethernet network interfaces operating in active/standby mode. The server attaches to only one subnet and uses only one server IP address for the bond0 interface. The Avaya Aura Conferencing server platform supports the configuration of multiple IPv4 addresses in one subnet. Depending on the deployment model selected for deployment, one or more components may share the same server, along with the server IP address. Please refer to Deploying Avaya Aura Conferencing 8.0 for supported configurations. Component Description Database The Database is the component that stores configuration data for the Avaya Aura Conferencing Network Elements. Element Manager (EM) The Element Manager is the component that manages all the Avaya Aura Conferencing Network Elements. Accounting Manager The Accounting Manager is the component that manages all the billing (AM) and account details. Provisioning Manager The Provisioning Manager is the component that manages configuration procedures via a web interface for configuring system wide conferencing details and templates, and managing user configuration specific to conferencing. Collaboration Agent (CA) The Collaboration Agent Manager is the component that hosts the Manager Collaboration Agent which is a web interface for users to see their conference status, perform actions on the conference, and share a web collaboration session. Server (AS) The Server is the component that manages conferencing signaling. Media Server (MS) The Media Server is the component that host conferencing, relay media, and optionally records and stores recorded content for playback retrieval when configured in a Recording Media Server Cluster. When used in the co-resident deployment model, the Media Server requires an additional IPv4 network address on the bond0 interface for media due to the number of ports used by media flows. Web Conferencing Management Server (WCMS) Web Conferencing Server (WCS) Document Conversion Server (DCS) Flash Media Gateway (FMG) Flash Media Management Server Audio/Video in Collaboration Management al Client Avaya Aura Session Manager The Web Conferencing Management Server is the component that manages Web Conferencing Servers and relays documents to the Document Conversion Server when document conversion is requested. The Web Conferencing Server is the component that handles user actions and media during web collaboration. The Document Conversion Server it the component that converts Office documents into the format required for document sharing during a web conference session. The FMG component converts sessions between the Flash-domain (RTMP signaling and media) and the Multimedia-domain (SIP signaling and RTP/RTCP media). The Flash Media Management Server component provides OAM&P functions for configuration, administration, and management of Audio/Video in Collaboration Agent. This is a Flash-based client that connects to the Flash Media Management Server and provides access to OAM&P functions for configuration, administration, and management of Audio/Video in Collaboration systems. The Avaya Aura Session Manager is the SIP routing and core component of the Avaya Aura solution. 6 Avaya Matrix: Avaya Aura Conferencing 8.0

7 Component Avaya Aura System Manager Avaya Session Border Controller (SBC) Description The Avaya Aura System Manager is the central management system component of the Avaya Aura solution. The Avaya Session Border Controller is a secure interface for SIP trunking and remote worker connectivity. Avaya Matrix: Avaya Aura Conferencing 8.0 April

8 2 Usage Tables 2.1 Usage Table Heading Definitions Ingress Connections (In): This indicates connection requests that are initiated from external devices to open ports on this product. From the point of view of the product, the connection request is coming In. (Note that in most cases, traffic will flow in both directions.) Egress Connections (Out): This indicates connection requests that are initiated from this product to known ports on a remote device. From the point of view of the product, the connection requests is going Out. (Note that in most cases, traffic will flow in both directions.) Intra-Device Connections: This indicates connection requests that both originate and terminate on this product. Normally these would be handled on the loopback interface, but there may be some exceptions where modules within this product must communicate on ports open on one of the physical Ethernet interfaces. These ports would not need to be configured on an external firewall, but may show up on a port scan of the product. Destination : This is the default layer-4 port number to which the connection request is sent. Valid values include: A (C) next to the port number means that the port number is configurable. Refer to the Notes section after each table for specifics on valid port ranges. Network/ : This is the name associated with the layer-4 protocol and layers-5-7 application. Disabled: This field indicates whether customers can enable or disable a layer-4 port changing its default port setting. Valid values include: Yes or No No means the default port state cannot be changed (e.g. enabled or disabled). Yes means the default port state can be changed and that the port can either be enabled or disabled. : A port is either open, closed, filtered or N/A. Open ports will respond to queries. Closed ports may or may not respond to queries and are only listed when they can be optionally enabled. Filtered ports can be open or closed. Filtered UDP ports will not respond to queries. Filtered TCP will respond to queries, but will not allow connectivity. N/A is used for the egress default port state since these are not listening ports on the product. External Device: This is the remote device that is initiating a connection request (Ingress Connections) or receiving a connection request (Egress Connections). 8 Avaya Matrix: Avaya Aura Conferencing 8.0

9 2.2 Tables Below are the tables which document the port usage for this product. Each component is represented by a separate table. For components that use more than one IP Address, that component has a table for each address separating the ingress/egress traffic per IP Address. Most components share a server IP Address with other components therefore there will be some duplication of ports, for example each server IP address will have the SSH TCP 22 open. For communication between components, egress traffic will be ingress traffic for the other component. In addition, unless otherwise noted, the source port of the data flows is the ephemeral port range ( ) as suggested by the IANA Firewall Boundary Legend Notes If communication may cross an optional firewall boundary, it is noted in the note column for that table using the following symbols: δ Used to note communication crossing Firewall boundary between a DMZ and the Core Data Center Network. δ Used to note communication crossing Firewall boundary between a DMZ and the Core Data Center that exists due to initial installation having the WCMS in the DMZ and has not been moved to the Core Data Center Network. ε Used to note communication crossing DMZ Firewall boundary from the Internet. ρ Used to note communication crossing Firewall boundary between the Core Data Center Network and a Remote Hosting Location Network. Figure 1 below shows a high level diagram where these firewall boundaries may exist and the corresponding symbol use to correlate using the notes column in the respective tables that follow. ε δ ρ Internet DMZ Enterprise Network Remote Location Figure 1: Firewall Boundaries Avaya Matrix: Avaya Aura Conferencing 8.0 April

10 2.2.2 Conferencing Database Servers No. Destination Table 1 s for Database (DB) Server IP Addresses TCP/SSH No Open Admin Terminal, SAL Gateway System Management requiring shell access TCP/TLS No Open EM Server NED TCP/TLS No Open EM Server Database SQL TCP/TLS No Open AM Server Database SQL TCP/TLS No Open Provisioning Manager Server Database SQL TCP/TLS No Open CA Manager Server Database SQL δ TCP/TLS No Open AS Server Database SQL TCP/TLS No Open MS Server Database SQL ρ TCP/TLS No Open WCMS Server Database SQL δ TCP/TLS No Open WCS Server Database SQL δ TCP/TLS No Open DCS Server Database SQL TCP/TLS No Open Redundant Database server Database synchronization UDP No N/A NTP Source NTP UDP Yes N/A Syslog server Remote Syslog Server TCP/TLS No N/A All Network Element servers NED FTP pull passive mode (control) TCP/TLS No N/A All Network Element servers NED FTP pull passive mode (data) TCP/TLS No N/A Redundant Database server Database synchronization INTRA-DEVICE CONNECTIONS NONE Notes: 1. Source port Uses SSL FTP (RFC 4217) 10 Avaya Matrix: Avaya Aura Conferencing 8.0 April 2016

11 2.2.3 Element Manager No. Destination Table 2: s for EM Server IP Address TCP/SSH No Open Admin Terminal, SAL Gateway System Management requiring shell access UDP No Open NTP Source NTP UDP No Open All Network Element servers SMNP (GET) δ,δ,ρ TCP/TLS No Open All Network Element servers NED FTP pull passive mode (control) δ,δ,ρ, TCP/TLS No Open All Network Element servers NED FTP pull passive mode (data) δ,δ,ρ, TCP/TLS No Open All Network Element servers NED δ,δ,ρ TCP/TLS No Open EM Service Config. Mtce (perfect channel) UDP No Open EM Service Config. Mtce (perfect channel) and associated heartbeat to the TCP Perfect Channel TCP No Open EM Service Logs (perfect channel) UDP No Open EM Service Logs (perfect channel), Associated Heartbeat to TCP Perfect Channel TCP No Open EM Service OMs (perfect channel) UDP No Open EM Service OMs (perfect channel), Associated Heartbeat to TCP Perfect Channel UDP No Open Redundant EM Server FT heartbeat 6, TCP No Open Redundant EM Server FT Sync Channel UDP No Open Redundant EM Server FT Sync Channel UDP No Open EM Service Alarms (sync channel) UDP/TCP Yes N/A DNS Servers DNS UDP No N/A NTP Source NTP UDP No N/A Media Server SNMP (GET) TCP/HTTPS No N/A Avaya Aura System Manager Trust Management UDP Yes N/A Syslog Server Remote Syslog Server TCP/TLS No N/A EM Server NED FTP pull passive mode (control) TCP/TLS No N/A EM Server NED FTP pull passive mode (data) TCP/TLS No N/A DB Server Database SQL TCP No N/A Avaya Aura System Manager SNMP (TRAP) , TCP No N/A External SNMP Manager SNMP (TRAP) UDP No N/A EM Service Logs (perfect channel) UDP No N/A EM Service OMs (perfect channel) 10 Avaya Matrix: Avaya Aura Conferencing 8.0 April

12 No. Destination TCP/TLS No N/A EM Service Alarm Sync UDP No N/A Redundant EM Server FT heartbeat 6, TCP No N/A Redundant EM Server FT Sync Channel UDP No N/A Redundant EM Server FT Sync Channel UDP No N/A EM Service Alarm Sync 11 INTRA-DEVICE CONNECTIONS NONE Notes: 1. Source port Uses SSL FTP (RFC 4217) 3. Source port is 12101, Source port is 12112, Source port is 12114, Sync between active and standby instance 7. Source Source Source port Source port Source port Source port Trap port value must be either 162 or between 1024 and No default source port value. Trap port value must be either 162 or between 1024 and Avaya Matrix: Avaya Aura Conferencing 8.0 April 2016

13 No. Destination Table 3: s for EM Service IP Address TCP/TLS No Open Network Element Servers Config. Mtce (perfect channel) δ,δ,ρ UDP No Open Network Element Servers Config. Mtce (perfect channel) δ,δ,ρ, UDP No Open Redundant ADR EM Service ADR Inter-system Heartbeat ρ TCP/TLS No Open Network Element Servers Logs (perfect channel) δ,δ,ρ UDP No Open Network Element Servers Logs (perfect channel) δ,δ,ρ, TCP/TLS No Open Network Element Servers OMs (perfect channel) δ,δ,ρ UDP No Open Network Element Servers OMs (perfect channel) δ,δ,ρ, TCP Yes Open EM Console TCP/TLS No Open EM Console EM Console connection to the EM Service Address. EM Console secure connection to the EM Service Address TCP/TLS No Open Network Element Servers Alarms (sync channel) δ,δ,ρ, TCP/TLS No Open EM Console EM Console Log Browser Stream UDP No Open Network Element Servers Alarms Sync δ,δ,ρ, UDP No N/A Redundant ADR EM Service ADR Inter-system Heartbeat ρ TCP/TLS No N/A AM Server Config. Mtce (Perfect Channel) UDP No N/A AM Server Config. Mtce (Perfect Channel) and associated heartbeat to TCP Perfect Channel TCP/TLS No N/A AM Server Logs (Perfect Channel) UDP No N/A AM Server Logs (Perfect Channel) and associated heartbeat to TCP Perfect Channel TCP/TLS No N/A AM Server OMs (Perfect Channel) UDP No N/A AM Server OMs (Perfect Channel) and associated heartbeat to TCP Perfect Channel TCP/TLS No N/A AS Server Config. Mtce (Perfect Channel) Config. Mtce (Perfect Channel) and UDP No N/A AS Server associated heartbeat to TCP Perfect Channel TCP/TLS No N/A AS Server Logs (Perfect Channel) UDP No N/A AS Server Logs (Perfect Channel) and associated heartbeat to TCP Perfect Channel TCP/TLS No N/A AS Server OMs (perfect channel) UDP No N/A AS Server OMs (perfect channel), Associated Heartbeat to TCP Perfect Channel TCP/TLS No N/A WCMS Server Config. Mtce (Perfect Channel) δ Avaya Matrix: Avaya Aura Conferencing 8.0 April

14 No. Destination UDP No N/A WCMS Server Config. Mtce (Perfect Channel) and associated heartbeat to TCP Perfect Channel TCP/TLS No N/A WCMS Server Logs (Perfect Channel) δ UDP No N/A WCMS Server Logs (Perfect Channel) and associated heartbeat to TCP Perfect Channel δ, TCP/TLS No N/A WCMS Server OMs (perfect channel) δ UDP No N/A WCMS Server OMs (Perfect Channel) and associated heartbeat to TCP Perfect Channel δ, TCP/TLS No N/A UDP No N/A Provisioning or CA Manager Server Provisioning or CA Manager Server Config. Mtce (Perfect Channel) Config. Mtce (Perfect Channel) and associated heartbeat to TCP Perfect Channel TCP/TLS No N/A Provisioning or CA Manager Server Logs (Perfect Channel) UDP No N/A Provisioning or CA Manager Logs (Perfect Channel) and associated Server heartbeat to TCP Perfect Channel TCP/TLS No N/A Provisioning or CA Manager Server OMs (perfect channel) UDP No N/A Provisioning or CA Manager OMs (perfect channel), Associated Server Heartbeat to TCP Perfect Channel TCP/TLS No N/A DCS Config. Mtce (Perfect Channel) Config Mtce (Perfect Channel) and UDP No N/A DCS associated heartbeat to TCP Perfect Channel TCP/TLS No N/A DCS Logs (Perfect Channel) UDP No N/A DCS Logs (Perfect Channel) and associated heartbeat to TCP Perfect Channel TCP/TLS No N/A DCS OMs (perfect channel) UDP No N/A DCS OMs (perfect channel) and associated heartbeat to TCP Perfect Channel TCP/TLS No N/A WCS Server Config. Mtce (Perfect Channel) δ UDP No N/A WCS Server Config. Mtce (Perfect Channel) and associated heartbeat to TCP Perfect Channel TCP/TLS No N/A WCS Server Logs (Perfect Channel) δ UDP No N/A WCS Server Logs (Perfect Channel) and associated heartbeat to TCP Perfect Channel δ, TCP/TLS No N/A WCS Server OMs (perfect channel) δ 14 Avaya Matrix: Avaya Aura Conferencing 8.0 April 2016 δ,5 δ δ,5 δ δ,6 δ δ,7 5 δ,5

15 No. Destination UDP No N/A WCS Server OMs (Perfect Channel) and associated heartbeat to TCP Perfect Channel δ, TCP/TLS No N/A MS Server Config. Mtce (Perfect Channel) ρ UDP No N/A MS Server Config. Mtce (Perfect Channel) and associated heartbeat to TCP Perfect Channel ρ, TCP/TLS No N/A MS Server Logs (Perfect Channel) ρ UDP No N/A MS Server Logs (Perfect Channel) and associated heartbeat to TCP Perfect Channel ρ, TCP/TLS No N/A MS Server OMs (perfect channel) ρ UDP No N/A MS Server OMs (Perfect Channel) and associated heartbeat to TCP Perfect Channel ρ,7 INTRA-DEVICE CONNECTIONS UDP No Open N/A EM Service to local syslog 8 Notes: 1. Source port is External Device Network Element Base + NE Config. Maintenance Perfect Channel Offset. Refer to Table 28, Table Source port is External Device Network Element Base + Log Offset. Refer to Table 28, Table Source port is External Device Network Element Base + OM Offset. Refer to Table 28, Table Source port is External Device Network Element Base + Alarm Offset. Refer to Table 28, Table Source port is 12101, Source port is 12112, Source port is 12114, Source port is Avaya Matrix: Avaya Aura Conferencing 8.0 April

16 2.2.4 Accounting Manager No. Destination Table 4: s for Accounting Manager (AM) Server IP Address TCP/SSH No Open Admin terminal, SAL Gateway System Management requiring shell access UDP No Open EM Server SNMP (GET) TCP/TLS No Open EM Server NED TCP/TLS No Open EM Service Config. Mtce (perfect channel) UDP No Open EM Service Config. Mtce (perfect channel) and associated heartbeat to the TCP Perfect Channel TCP No Open EM Service Logs (perfect channel) UDP No Open EM Service Logs (perfect channel), Associated Heartbeat to TCP Perfect Channel TCP No Open EM Service OMs (perfect channel) UDP No Open EM Service OMs (perfect channel), Associated Heartbeat to TCP Perfect Channel UDP No Open Redundant AM Server FT heartbeat 4, TCP No Open Redundant AM Server FT Sync Channel UDP No Open Redundant AM Server FT Sync Channel UDP/TCP Yes N/A DNS Servers DNS UDP No N/A NTP source NTP UDP Yes N/A Syslog Server Remote Syslog Server TCP/TLS No N/A EM Server NED FTP pull passive mode (control) TCP/TLS No N/A EM Server NED FTP pull passive mode (data) TCP/TLS No N/A DB Server Database SQL UDP No N/A EM Service Logs (perfect channel) UDP No N/A EM Service OMs (perfect channel) TCP/TLS No N/A EM Service Alarm Sync UDP No N/A Redundant AM Server FT Heartbeat 4, TCP No N/A Redundant AM Server FT Sync Channel UDP No N/A Redundant AM Server FT Sync Channel >1023 TCP Yes N/A Back office billing processing system Billing Stream UDP No N/A EM Service Alarm Sync 7 INTRA-DEVICE CONNECTIONS 16 Avaya Matrix: Avaya Aura Conferencing 8.0 April

17 Destination No NONE Notes: 1. Source port is 12101, Source port is 12112, Source port is 12114, Sync between active and standby 5. Source port is Uses SSL FTP (RFC 4217) 7. Source port is Avaya Matrix: Avaya Aura Conferencing 8.0 April

18 No. Destination Table 5: s for Accounting Manager (AM) Service IP Address TCP/TLS No Open AS Server Billing Stream (perfect channel) UDP No Open AS Server Billing Stream (perfect channel) TCP/TLS No N/A AS Server Billing Stream (perfect channel) UDP No N/A AS Server Billing Stream (perfect channel) 2 INTRA-DEVICE CONNECTIONS NONE Notes: 1. Source port is Source port is Avaya Matrix: Avaya Aura Conferencing 8.0 April 2016

19 2.2.5 Provisioning Manager Table 6: s for Provisioning Manager Server IP Address No. Destination TCP/SSH No Open Admin terminal, SAL Gateway System Management requiring shell access UDP No Open EM Server SNMP (GET) TCP/HTTPS No Open Intranet Web Client Client access to the Collaboration Agent 1, TCP/TLS No Open EM Server NED TCP/HTTPS No Open WCMS Server SIP Bridge δ, TCP/HTTPS No Open Admin subnet, Avaya Aura Administrative access for System System Manager Provisioning TCP/TLS No Open EM Service Config. Mtce (perfect channel) UDP No Open EM Service Config. Mtce (perfect channel), Associated Heartbeat to TCP Perfect Channel TCP/TLS No Open EM Service Logs (perfect channel) UDP No Open EM Service Logs (perfect channel), Associated Heartbeat to TCP Perfect Channel TCP/TLS No Open EM Service OMs (perfect channel) UDP No Open EM Service OMs (perfect channel), Associated Heartbeat to TCP Perfect Channel TCP/SIP Yes Closed AS Service AS SIP connection to the Provisioning or Personal Agent Manager Server TCP/TLS/SIP(S) Yes Open AS Service AS SIP connection to the Provisioning or Personal Agent Manager Server UDP/TCP Yes N/A DNS Servers DNS UDP No N/A NTP source NTP TCP/LDAP Yes N/A LDAP Servers Used to sync/authenticate with a Directory Server UDP Yes N/A Syslog server Remote Syslog Server TCP/TLS/LDAPS Yes N/A LDAPS Servers Used to sync/authenticate with a Directory Server over TLS TCP/TLS No N/A EM Server NED FTP pull passive mode (control) TCP/TLS No N/A EM Server NED FTP pull passive mode (data) TCP/SIP Yes N/A AS Service SIP to AS Service TCP/TLS/SIP(S) Yes N/A AS Service SIP(S)/TLS to AS Service TCP/TLS No N/A DB Server Database SQL UDP No N/A EM Service Logs (perfect channel) UDP No N/A EM Service OMs (perfect channel) 10 Avaya Matrix: Avaya Aura Conferencing 8.0 April

20 No. Destination TCP/TLS No N/A EM Service Alarm Sync UDP No N/A EM Service Alarm Sync 12 INTRA-DEVICE CONNECTIONS NONE Notes: 1. Server redirects to port The Provisioning Manager also includes the Collaboration Agent (CA). 3. SIP Bridge between the Web Conferencing Management Server and either the Provisioning Manager or CA Manager that is configured to be the Meeting Event Processor. 4. Source port is 12101, Source port is 12112, Source port is 12114, Source port Uses SSL FTP (RFC 4217) 9. Source port is Source port is Source port is Avaya Matrix: Avaya Aura Conferencing 8.0 April 2016

21 2.2.6 Collaboration Agent Manager No. Destination Table 7: s for Collaboration Agent (CA) Manager Server IP Address TCP/SSH No Open Admin terminal, SAL Gateway System Management requiring shell access δ UDP No Open EM Server SNMP (GET) δ TCP/HTTPS No Open Internet/Intranet Web Client Client access to the Collaboration Agent ε, TCP/TLS No Open EM Server NED δ TCP/HTTPS No Open WCMS Server SIP Bridge δ, TCP/TLS No Open EM Service Config. Mtce (perfect channel) δ UDP No Open EM Service Config. Mtce (perfect channel), Associated Heartbeat to TCP Perfect Channel δ, TCP/TLS No Open EM Service Logs (perfect channel) δ UDP No Open EM Service Logs (perfect channel), Associated Heartbeat to TCP Perfect Channel δ, TCP/TLS No Open EM Service OMs (perfect channel) δ UDP No Open EM Service OMs (perfect channel), Associated Heartbeat to TCP Perfect Channel δ, TCP/SIP Yes Closed AS Service AS SIP connection to the Provisioning or Personal Agent Manager Server δ, TCP/TLS/SIP(S) Yes Open AS Service AS SIP/TLS connection to the Provisioning or Personal Agent Manager Server δ, TCP/SIP Yes Closed SBC Avaya SBC SIP connection to the Provisioning or Collaboration Agent Manager Server for the Mobile App. δ,6, TCP/TLS/SIP(S) Yes Open SBC Avaya SBC SIP/TLS connection to the Provisioning or Collaboration Agent Manager Server for the Mobile App UDP/TCP Yes N/A DNS Servers DNS δ, ε, UDP No N/A NTP source NTP δ, TCP/LDAP Yes N/A LDAP Servers Used to authenticate with a Directory Server δ UDP Yes N/A Syslog server Remote Syslog Server δ TCP/TLS/LDAPS Yes N/A LDAPS Servers Used to authenticate with a Directory Server over TLS δ TCP/TLS No N/A EM Server NED FTP pull passive mode (control) δ, TCP/TLS No N/A EM Server NED FTP pull passive mode (data) δ, 9 Avaya Matrix: Avaya Aura Conferencing 8.0 April δ,6,13

22 No. Destination TCP/SIP Yes N/A AS Service SIP to AS Service δ TCP/SIP Yes N/A SBC SIP to SBC δ TCP/TLS/SIP(S) Yes N/A AS Service SIP(S)/TLS to AS Service δ TCP/TLS/SIP(S) Yes N/A SBC SIP(S)/TLS to SBC δ TCP/TLS No N/A DB Server Database SQL δ TCP/TLS No N/A EM Service Log (perfect channel) δ UDP No N/A EM Service Logs (perfect channel) δ, TCP/TLS No N/A EM Service OMs (perfect channel) δ UDP No N/A EM Service OMs (perfect channel) δ, TCP/TLS No N/A EM Service Alarm Sync δ, UDP No N/A EM Service Alarm Sync δ INTRA-DEVICE CONNECTIONS NONE 1. Server redirects to port SIP Bridge between the Web Conferencing Management Server and either the Provisioning Manager or CA Manager that is configured to be the Meeting Event Processor. 3. Source port is 12101, Source port is 12112, Source port is 12114, The use of SIP and SIP/TLS is mutually exclusive. 7. Depending on if Split-Horizon DNS is used will dictate if a firewall rule to the Enterprise DNS is required. If not using Split-Horizon DNS it is recommended that /etc/hosts is used instead on any servers in the DMZ such that external access to internal DNS is restricted. 8. Source port Uses SSL FTP (RFC 4217) 10. Source port is Source port is Source port is For the Enhanced Audio/Video in Collaboration Agent feature, make sure that SIP trunk traffic flows between the SBC and Avaya Session Manager is configured in both directions. They are either SIP TLS 5061 or SIP TCP 5060 in both directions. 22 Avaya Matrix: Avaya Aura Conferencing 8.0 April 2016

23 Avaya Matrix: Avaya Aura Conferencing 8.0 April

24 2.2.7 Server No. Destination Table 8: s for Server (AS) Server IP Address TCP/SSH No Open Admin terminal, SAL Gateway System Management requiring shell access UDP No Open EM Server SNMP (GET) TCP/TLS No Open EM Server NED TCP/TLS No Open EM Service Config. Mtce (perfect channel) UDP No Open EM Service Config. Mtce (perfect channel) and associated heartbeat to TCP Perfect Channel TCP/TLS No Open EM Service Logs (perfect channel) UDP No Open EM Service Logs (perfect channel) and associated heartbeat to TCP Perfect Channel TCP/TLS No Open EM Service OMs (perfect channel) UDP No Open EM Service OMs (perfect channel) and associated heartbeat to TCP Perfect Channel TCP/TLS No Open AM Service Billing Stream (perfect channel) UDP No Open AM Service Billing Stream (perfect channel) TCP No Open Redundant AS Server FT heartbeat 5, TCP Yes Open Redundant AS Server FT Sync Channel UDP No Open Redundant AS Server FT Sync Channel TCP/TLS No Open Redundant AS Server FT Secure Sync Channel UDP/TCP Yes N/A DNS Servers DNS UDP No N/A NTP source NTP TCP/LDAP Yes N/A LDAP Server Used to authenticate with a Directory Server TCP/HTTPS No N/A Avaya Aura System Manager WebLM Licensing TCP/HTTPS No N/A WCS Service Server REST service call to control start/stop of recordings UDP No N/A Syslog Server Remote Syslog Server TCP/LDAPS Yes N/A LDAPS Server Used to authenticate with a Directory Server over TLS TCP/TLS No N/A EM Server NED FTP pull passive mode (control) TCP/TLS No N/A EM Server NED FTP pull passive mode (data) TCP/TLS No N/A DB Server Database SQL 1 δ 24 Avaya Matrix: Avaya Aura Conferencing 8.0 April 2016

25 No. Destination TCP/TLS No N/A WCMS Server Server ping of the SIP Bridge through the WCMS δ TCP/TLS No N/A EM Service Logs (perfect channel) UDP No N/A EM Service Logs (perfect channel) TCP/TLS No N/A EM Service OMs (perfect channel) UDP No N/A EM Service OMs (perfect channel) TCP/TLS No N/A EM Service Alarm Sync UDP No N/A Redundant AS Server FT heartbeat 5, TCP Yes N/A Redundant AS Server FT Sync Channel UDP No N/A Redundant AS Server FT Sync Channel UDP No N/A EM Service Alarm Sync TCP/TLS No N/A Redundant AS Server FT Secure Sync Channel 12 INTRA-DEVICE CONNECTIONS NONE Notes: 1. Source port is 12101, Source port is 12112, Source port is 12114, Source port is Sync between active and standby, may be disabled after upgrade to AAC 8.0 SP2 6. Source port is Source port is Uses SSL FTP (RFC 4217) 9. Source port is Source port is Source port is As of AAC 8.0 SP2 Avaya Matrix: Avaya Aura Conferencing 8.0 April

26 Table 9: s for Server (AS) Service IP Address Destination No TCP/SIP Yes Closed MS Server SIP ρ, TCP/SIP Yes Closed Avaya Aura Session Manager (SM100) SIP TCP/SIP Yes Closed Provisioning or CA Manager Server SIP δ, TCP/SIP Yes Closed AAC Mobile App Client (ios and Android) SIP within Enterprise from Client 2, TCP/SIP Yes Closed SBC SIP trunk from SBC δ, TCP/TLS/SIP(S) Yes Open MS Server SIP or SIPS over TLS ρ, TCP/TLS/SIP(S) Yes Open Provisioning or CA Manager Server SIP or SIPS over TLS δ, TCP/TLS/SIP(S) Yes Open Avaya Aura Session Manager (SM100) SIP or SIPS over TLS TCP/TLS/SIP(S) Yes Open AAC Mobile App Client (ios SIP or SIPS over TLS within Enterprise from and Android) Client 2, TCP/TLS/SIP(S) Yes Open SBC SIP or SIPS trunk from SBC over TLS δ, TCP/SIP Yes N/A MS Server SIP ρ, TCP/SIP Yes N/A Avaya Aura Session Manager (SM100) SIP TCP/SIP Yes N/A SBC SIP Trunk to SBC δ, TCP/TLS/SIP(S) Yes N/A MS Server SIP or SIPS over TLS ρ, TCP/TLS/SIP(S) Yes N/A Avaya Aura Session Manager (SM100) SIP or SIPS over TLS TCP/TLS/SIP(S) Yes N/A SBC SIP or SIPS Trunk to SBC over TLS δ, TCP/SIP Yes N/A Co-Res MS Server SIP TCP/TLS/SIP(S) Yes N/A Co-Res MS Server SIP or SIPS over TLS TCP/SIP Yes N/A TCP/TLS/SIP(S) Yes N/A INTRA-DEVICE CONNECTIONS NONE Provisioning or CA Manager Server Provisioning or CA Manager Server Server SIP connection to the Provisioning or CA Manager Server SIP(S)/TLS connection to the Provisioning or CA Manager δ,1,3 δ,1,3 26 Avaya Matrix: Avaya Aura Conferencing 8.0 April 2016

27 Notes: 1. Dependent on Meeting Event Processor configuration. 2. Client supports Connection Reuse such that additional outbound connection is not required. 3. The use of SIP and SIP/TLS is mutually exclusive. Avaya Matrix: Avaya Aura Conferencing 8.0 April

28 2.2.8 Media Server No. Destination Table 10: s for Media Server (MS) Server IP Address TCP/SSH No Open Admin terminal, SAL Gateway System management requiring shell access ρ UDP No Open EM Server SNMP(GET) ρ TCP/TLS No Open MS Servers in the same cluster Media Server Configuration DB TCP No Open Provisioning Manager External Session API (ESA) UComm service only. ρ TCP/TLS No Open EM Server NED ρ TCP/SIP Yes Closed AS Service Server SIP connection to the Media Server ρ TCP/TLS/SIP(S) Yes Open AS Service Server SIP(S)/TLS connection to the Media Server ρ TCP/SIP Yes Closed AS Service Server SIP connection to the Co- Res Media Server TCP/TLS/SIP(S) No Open AS Service Server SIP(S)/TLS connection to the Co-Res Media Server TCP No Open MS Servers in the same cluster Cluster AMS Management TCP/HTTP Yes Closed Admin subnet Also used for KPI Monitoring via Administrator Web Client access TCP/HTTP Yes Closed WCS Server, WCMS Server TCP/HTTPS Yes Open Admin subnet TCP/HTTPS Yes Open WCS Server, WCMS Server Web Conferencing Server and Web Conferencing Management Server signaling to the Media Server for recording media storage/retrieval. Web Conferencing Server and Web Conferencing Management Server signaling to the Media Server for recording media storage/retrieval. Also used for KPI Monitoring via Administrator Web Client access Web Conferencing Server and Web Conferencing Management Server signaling to the Media Server for recording media storage/retrieval TCP/HTTP/S No Open EM KPI/SDR Browser Client SOAP request from Admin client, defaults to over TLS TCP No Open MS Servers in the same cluster Cluster Inter-SC Communication 28 Avaya Matrix: Avaya Aura Conferencing 8.0 April δ, ρ,1,12 2 δ, ρ, 2,12 ρ