DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 26 Sep 16

Transcription

1 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 26 Sep 16 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of the Joint Interoperability Certification of the Avaya Aura References: (a) Department of Defense Instruction , "DoD Unified Capabilities (UC)," 9 December 2010 (b) Office of the Department of Defense Chief Information Officer, Department of Defense Unified Capabilities Requirements 2013 (UCR 2013) Change 1, June 2015 (c) through (g), see Enclosure 1. Certification Authority. Reference (a) establishes the Joint Interoperability Test Command (JITC) as the Joint Interoperability Certification Authority for UC products, Reference (b). 2. Conditions of Certification. The Avaya Aura CM Release 7.0.1; hereinafter referred to as the System Under Test (SUT), meets the critical requirements of the Unified Capabilities Requirements (UCR), Reference (b), and is certified for joint use as a Local Session Controller (LSC) with the conditions described in Table 1. This certification expires upon changes that affect interoperability, but no later than the expiration date of the UC Approved Products List (APL) memorandum. This extension is for Desktop Review (DTR) 1, which requested the addition of the S8300D and S8300E communications core servers as part of the SUT as well as the G430 media gateway. See Paragraph 4 for the test details. Table 1. Conditions None Condition UCR Waivers Conditions of Fielding Although the SUT supports an E1 Q.931 PSTN interface, they do not support a Q DSN interface. As a result, the SUT is certified in the United States, including the CONUS, Alaska, Hawaii, and U.S. Caribbean and Pacific Territories. This discrepancy was adjudicated by DISA as minor with vendor POA&M and the following condition of fielding: The SUT is not certified for joint use outside CONUS in ETSI-compliant countries. Operational Impact Minor

2 Table 1. Conditions (continued) Condition Conditions of Fielding (continued) The SUT AS5300 Aura soft client did not decode video when an H.264 video call was placed to the Acano UCCS and packetization mode 1 is negotiated in the SIP session. If the SUT AS5300 Aura soft client initiated a video call at high (524 Kbps) or very high (768 Kbps) bandwidth the video call was negotiated with packetization mode 2 and video was decoded by the SUT AS5300 Aura soft client. DISA has accepted the vendor s POA&M and has adjudicated this discrepancy as minor with the following condition of fielding; The Deployment Guide must state The soft client establishing a video with Acano, the user needs to select high or very high bandwidth (524k or 768k). The SUT AS5300 Aura soft client is not able to establish a two-way video call with Vidyo using H.263 protocol. DISA has adjudicated this discrepancy as minor with the condition of fielding to be configured for H.264 protocol. The SUT must be configured with two separate AS-SIP trunks to the DISN WAN. One for voice ASAC to support the CM voice endpoints and another to support the AS5300 voice and video soft clients. Open Test Discrepancies Operational Impact Minor Minor Minor The SUT does not support ETSI ISDN PRI E1 with ITU-T Q Minor See note 1. The SUTs media gateway is not able to establish a 64K data clear channel call. Minor See note 2. The SUT does not support ASAC or Video EIs. Minor See note 2. Traffic entering and exiting the SUT via a TDM MG Trunk exceeds maximum latency. Minor See note 2. The SUT does not provide enough memory to meet Domain Directory Information Minor See note 2. Per the vendor s LoC, the SUT AS5300 does not support all DHCPv6 client messages and options. Minor See note 2. Per the vendor s LoC, the SUT AS5300 does not log all reconfigure events. Minor See note 3. Per the vendor s LoC, the SUT AS5300 SIP Core/AMS does not allow for DAD to be disabled. Minor See note 3. Per the vendor s LoC, the SUT AS5300 does not support domain directory IAW the reference. Minor See note 2. The SUT AS5300 is not capable of supporting IPv6 signaling. The SUT supports IPv4 signaling only, with dual stack IPv4/IPv6 media. Minor See note 2. The SUT does not provide enough memory to meet Domain Directory Information. Minor See note 2. NOTES: 1. Although the SUT supports an E1 Q.931 PSTN interface, they do not support a Q DSN interface. As a result, the SUT is certified in the United States, including the CONUS, Alaska, Hawaii, U.S. Caribbean, and Pacific Territories. This discrepancy was adjudicated by DISA as minor with POA&M and the following condition of fielding: The SUT is not certified for joint use outside CONUS in ETSIcompliant countries. 2. DISA has accepted the vendor s POA&M and adjudicated this discrepancy as minor. 3. DISA has adjudicated this discrepancy as minor with the intent to change the UCR requirement. 2

3 Table 1. Conditions (continued) LEGEND: AMS Avaya Media Server AS Application Server ASAC Assured Services Admission Control AS-SIP Assured Services Session Initiation Protocol CM Communications Manager CONUS Continental U.S. DAD Duplicate Address Detection DHCPv6 Dynamic Host Configuration Protocol for IPv6 DISA Defense Information Systems Agency DISN Defense Information Systems Network DSN Defense Switched Network E1 European Basic Multiplex Rate (2.048 Mbps) EI End Instrument ETSI European Telecommunications Standards Institute IAW In Accordance With IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 ISDN Integrated Services Digital Network ITU-T International Telecommunication Union - Telecommunication Standardization Sector K Kilobits Kbps Kilobits per second LoC Letters of Compliance Mbps Megabits per second MG Media Gateway POA&M Plan of Action and Milestones PRI Primary Rate Interface PSTN Public Switched Telephone Network SIP Session Initiation Protocol SUT System Under Test TDM Time Division Multiplexing U.S. United States UCCS Unified Capabilities Conference System UCR Unified Capabilities Requirements WAN Wide Area Network 3. Interoperability Status. Table 2 provides the SUT interface interoperability status and Table 3 provides the Capability Requirements (CR) and Functional Requirements (FR) status. Table 4 provides the UC APL product summary. Table 2. Interface Status Interface Applicability (See note 1.) Status Network Management Interfaces (See note 2.) 10BaseT Conditional Met The SUT met the critical CRs and FRs for the IEEE 802.3i interface. 100BaseT Conditional Met The SUT met the critical CRs and FRs for the IEEE 802.3u interface. The SUT met the critical CRs and FRs for the IEEE 802.3ab 1000BaseT Conditional Met interface. Network Interfaces (Trunk) (See note 2.) The SUT met the critical CRs and FRs for the IEEE 802.3i interface 10BaseT Conditional Met with the SUT AEIs and softphones. The SUT met the critical CRs and FRs for the IEEE 802.3u interface 100BaseT Conditional Met with the SUT voice PEIs and AS-SIP Trunking. 1000BaseT Conditional Met The SUT met the critical CRs and FRs for the IEEE 802.3ab interface 10 Gbps Conditional Not Tested with the SUT voice PEIs and AS-SIP Trunking. The SUT does not offer the conditional CRs and FRs for the IEEE 802.3ae interface with the SUT voice PEIs and AS-SIP Trunking. Line Interfaces The SUT met the critical CRs and FRs for the IEEE 802.3i interface 10BaseT (See note 2.) Conditional Met with the SUT AEIs and softphones. The SUT met the critical CRs and FRs for the IEEE 802.3u interface 100BaseT (See note 2.) Conditional Met with the SUT voice PEIs and AS-SIP Trunking. The SUT met the critical CRs and FRs for the IEEE 802.3ab interface 1000BaseT (See note 2.) Conditional Met with the SUT voice PEIs and AS-SIP Trunking. The SUT does not offer the conditional CRs and FRs for the IEEE 10 Gbps (See note 2.) Conditional Not Tested 802.3ae interface with the SUT voice PEIs and AS-SIP Trunking. The SUT met the critical CRs and FRs for the 2-wire analog interface 2-wire analog Required Met with the SUT 2-wire secure and non-secure analog instruments. ISDN BRI Conditional Met The SUT met the critical CRs and FRs for the ISDN BRI interface. 3

4 Interface Table 2. Interface Status (continued) Applicability (See note 1.) Status Legacy Interfaces (External) ISDN T1 PRI (ANSI T1.619a) Required Met The SUT met the critical CRs/FRs. This interface provides legacy DSN and TELEPORT connectivity. ISDN T1 PRI NI-2 Required Met The SUT met the critical CRs/FRs. This interface provides PSTN connectivity. T1 CCS7 (ANSI T1.619a) Conditional Not Tested The SUT does not support this conditional interface. T1 CAS Conditional Met The SUT met threshold CRs/FRs for DTMF and MFR1. (See note 3.) E1 PRI (ITU-T Q.955.3) Required Not Met The SUT does not support this required interface. (See note 4.) E1 PRI (ITU-T Q.931) Required Met The SUT met the critical CRs/FRs. This interface provides OCONUS connectivity in ETSI-compliant countries. E1 CAS Conditional Met The SUT met threshold CRs/FRs for DTMF and MFR1. (See note 3.) NOTES: 1. The SUT high-level requirements are depicted in Table 3. These high-level requirements refer to a more detailed list of requirements provided in Reference (c), Enclosure The SC (and its appliances), SS, SBC, AEI, and PEI shall support one or more of the following Ethernet physical interfaces (compliant to IEEE Ethernet standards) to ASLAN switches and routers. 3. T1 and E1 CAS interfaces with DTMF and MFR1 signaling protocols were met without testing, based on JITC analysis because there has been no effective change in the SUT Trunk-Side Media Gateways, with T1 CAS interfaces since these gateways were tested and certified as part of the Avaya Aura Communication Manager Release certification as depicted in Reference (e). 4. Although the SUT supports an E1 Q.931 PSTN interface, they do not support a Q DSN interface. As a result, the SUT is certified in the United States, including the CONUS, Alaska, Hawaii, and U.S. Caribbean and Pacific Territories. This discrepancy was adjudicated by DISA as minor with vendor POA&M and the following condition of fielding: The SUT is not certified for joint use outside CONUS in ETSIcompliant countries. LEGEND: 10BaseT 10 Mbps Ethernet 100BaseT 100 Mbps Ethernet 1000BaseT 1000 Mbps Ethernet AEI AS-SIP End Instrument ANSI American National Standards Institute ASLAN Assured Services Local Area Network AS-SIP Assured Services Session Initiation Protocol BRI Basic Rate Interface CAS Channel Associated Signaling CCS7 Common Channel Signaling Number 7 CONUS Continental United States CR Capability Requirements DISA Defense Information Systems Agency DSN Defense Switched Network DTMF Dual Tone Multi-Frequency E1 European Basic Multiplex Rate (2.048 Mbps) ETSI European Telecommunications Standards Institute FR Functional Requirements Gbps Gigabits per second IEEE Institute of Electrical and Electronics Engineers ISDN Integrated Services Digital Network ITU-T International Telecommunication Union- Telecommunication Standardization Sector JITC Joint Interoperability Test Command Mbps Megabits per second MFR1 Multi-Frequency Recommendation 1 MLPP Multi-Level Precedence and Preemption NI-2 National ISDN Standard 2 OCONUS Outside the Continental United States PEI Proprietary End Instrument POA&M Plan of Action and Milestones PRI Primary Rate Interface PSTN Public Switched Telephone Network Q.931 Signaling Standard for ISDN Q ISDN Signaling Standard for E1 MLPP SBC Session Border Controller SC Session Controller SS Softswitch SS7 Signaling System 7 SUT System Under Test T1 Digital Transmission Link Level 1 (1.544 Mbps) T1.619A SS7 and ISDN MLPP Signaling Standard for T1 U.S. United States CR/FR ID Table 3. SUT Capability Requirements and Functional Requirements Status UCR Requirement (High-Level) (See note 1.) UCR 2013 Reference Status 1 Voice Features and Capabilities (R) 2.2 Met 2 Assured Services Admission Control (R) 2.3 Met 3 Signaling Protocols (R) 2.4 Met 4 Registration and Authentication (R) 2.5 Met 4

5 Table 3. SUT Capability Requirements and Functional Requirements Status (continued) CR/FR ID UCR Requirement (High-Level) (See note 1.) UCR 2013 Reference Status 5 SC and SS Failover and Recovery (R) 2.6 Met 6 Product Interface (R) 2.7 Met 7 Product Physical, Quality, and Environmental Factors (R) 2.8 Met 8 End Instruments (including tones and announcements) (R) 2.9 Partially Met (See note 2.) 9 Session Controller (R) 2.10 Met 10 Call Connection Agent (R) 2.14 Partially Met (See note 3.) 11 CCA Interaction with Network Appliances and Functions (R) 2.15 Met (See note 4.) 12 Media Gateway (R) 2.16 Partially Met (See note 2.) 13 Worldwide Numbering & Dialing Plan (R) 2.18 Partially Met (See note 2.) 14 Management of Network Devices (R) 2.19 Met (See note 6.) 15 V Modem Relay Secure Phone Support (R) 2.20 Partially Met (See note 7.) 16 Requirements for Supporting AS-SIP Based Ethernet Devices for Voic Systems (C) 2.21 Not Tested (See note 8.) 17 Local Attendant Console Features (O) 2.22 Met 18 MSC and SSC (O) 2.23 Not Tested (See note 9.) 19 MSC, SSC, and Dynamic ASAC Requirements in Support of Bandwidthconstrained links (O) 2.24 Not Tested (See note 9.) 20 Other UC Voice (R) 2.25 Met (See note 10.) 21 Information Assurance Requirements (R) 4 Met (See note 4.) 22 IPv6 Requirements (R) 5 Partially Met (See notes 2 and 7.) 23 AS-SIP 2013 (R) AS-SIP Met NOTES: 1. The annotation of required refers to a high-level requirement category. The applicability of each sub-requirement is provided in Reference (c), Enclosure The SUT met the requirements with the exceptions noted in Table 1. DISA adjudicated these exceptions as minor. 3. Although the SUT supports an E1 Q.931 PSTN interface, they do not support a Q DSN interface. As a result, the SUT is certified in the United States, including the CONUS, Alaska, Hawaii, and U.S. Caribbean and Pacific Territories. This discrepancy was adjudicated by DISA as minor with vendor POA&M and the following condition of fielding: The SUT is not certified for joint use outside CONUS in ETSIcompliant countries. 4. Cybersecurity testing was conducted by DISA-led Cybersecurity test teams and the results are published in a separate report, Reference. (e). In addition to the Cybersecurity testing conducted by these test teams, the SUT met the requirements in section 4 with the vendor s LoC. 6. General Management of network devices is supported, however requirements for FCAPS Management was not tested, but was determined to be compliant based on vendor submitted LoC. 7. The SUT partially met this requirement with testing. The G650 gateway is certified by similarity to the G450 gateway, but cannot be deployed as a standalone Gateway, due to the fact that it does not support IPv6 or V Therefore, the G650 must be deployed with a G450 in order to meet IPv6 and V requirements. In addition the following SUT AS5300 IPv6 LoC requirements were not met, but DISA accepted the vendors POA&M and they were adjudicated as minor: SUT AS5300 does not support all DHCPv6 client messages and options. The SUT AS5300 does not log all reconfigure events. The SUT AS5300 SIP Core/AMS does not allow for DAD to be disabled. The SUT AS5300 is not capable of supporting IPv6 signaling. The SUT supports IPv4 signaling only, with dual stack IPv4/IPv6 media. 8. The SUT does not support AS-SIP based voic optional requirement. 9. This optional requirement applies specifically to a Local Session Controller. The optional requirements for Master Session Controller and Subtended Session Controller were not tested and are not covered under this certification. 10. Following the risk avoidance guidance in Telcordia Technologies GR-513-CORE, the backup power design shall minimize the probability of a complete loss of UC appliance system power. This is a non-testable requirement. The SUT must be installed following this guidance. 5

6 Table 3. SUT Capability Requirements and Functional Requirements Status (continued) LEGEND: AMS Avaya Media Server AS Application Server ASAC Assured Services Admission Control AS-SIP Assured Services Session Initiation Protocol C Conditional CCA Call Connection Agent CM Communication Manager CONUS Continental U.S. CR Capability Requirement DAD Duplicate Address Detection DHCPv6 Dynamic Host Configuration Protocol for IPv6 DISA Defense Information System Agency DSN Defense Switched Network E1 European Basic Multiplex Rate (2.048 Mbps) ETSI European Telecommunications Standards Institute FCAPS Fault, Configuration, Accounting, Performance, and Security FR Functional Requirement ID Identification IPv4 Internet Protocol version 6 IPv6 Internet Protocol version 6 LoC Letters of Compliance Mbps Megabits per second MLPP Multi-Level Precedence and Preemption MSC Master Session Controller O Optional POA&M Plan of Action and Milestones Q.931 Signaling Standard for ISDN Q ISDN Signaling Standard for E1 MLPP R Required SC Session Controller SIP Session Initiation Protocol SS Softswitch SSC Subtended Session Controller SUT System Under Test U.S. United States UC Unified Capabilities UCR Unified Capabilities Requirements VVoIP Voice/Video over Internet Protocol Table 4. UC APL Product Summary Product Identification Product Name Software Release UC Product Type(s) Product Description Product Components (See note 1.) Active Duplex Communication Manager (AVP) (x2) Standby Duplex Communication Manager (x2) Administrative Workstation (site-provided) Administrative Workstation (site-provided) Avaya Aura Communication Manager Local Session Controller (LSC) Local Session Controller Component Name (See note 2.) HP DL360 G9 Dell R630 HP DL360PG7/G8 & DellR610/620 S8300D, S8300E HP DL360 G9 Dell R630 HP DL360PG7/G8 & DellR610/620 NA NA Version AVP ESXi Kernel e16.AV2 CM RedHat Linux 6.5 OpenSSH 5.3p1 OpenSSL 1.0.1e-fips 11 Feb 2013 McAfee VirusScan CL for Linux v Apache AVP ESXi Kernel e16.AV2 CM RedHat Linux 6.5 OpenSSH 5.3p1 OpenSSL 1.0.1e-fips 11 Feb 2013 McAfee VirusScan CL for Linux v Apache Windows 7 SP1, or Windows 10 Enterprise Axway Desktop Validator ActivClient CAC x64 McAfee VirusScan Enterprise 8.8 Communications Core Server (See notes 3 and 4.) Enterprise Survivable Core server (See note 3.) 6

7 Table 4. UC APL Product Summary (continued) Product Components (See note 1.) Communication Manager Messaging Component Name (See note 2.) Version NA CC Elite Release NA MM710 (x12) 1 port T1/E1 Media Module MM711 8 port Analog Media Module MM712 8 port DCP Media G450 and G430 Media Gateways (for HA x3) Module MM716 (x2) 24 port Analog Media Module MM port DCP Media Module MM721, MM720 8 port BRI Media Module TN2224CP 24 port DCP board TN2312BP IPSI board TN2198BP 24 port BRI board G650 Media Gateway (x2 for TN2501AP VLAN board HA) TN2602AP MP320 board TN464HP T1/E1 board TN793DP 24 port Analog TN799DP CLAN Interface Attendant Console 302C NA NA OneX Soft Client Workstation (site-provided) Routine Only EI NA VxWorks VxWorks 6.8 Windows 7 SP1, or Windows 10 Enterprise Avaya OneX Communicator OneXC-OneXC6053-Integration-124 Axway Desktop Validator ActivClient CAC x64 Voic messaging (See note 5.) ACD Contact Center (See note 5.) (See notes 6 and 7.) (See note 8.) IP End Instruments McAfee VirusScan Enterprise G, 9641G, 9611G,9608 (dual-stack) (See note 9.) 96x0 (single-stack) Digital 8410D, 24XX, 64XX, 9408 DCPA94xxR12.BIN Analog Generic NA BRI Legacy endpoint 8510T Feature Pack 3.2 PostgreSQL patch 3 SIP Core OAM&P IBM 3550 HP DL-360p G7 and G8 HP DL360 G9 mcp_core_linux_ple MCP_ _ rsit-server ESXi 5.5 VMware SIP Core SESM x2 (Master/Slave) Avaya Media Server (AMS) x2 IBM 3550 HP DL-360p G7 and G8 HP DL360 G9 IBM 3550 HP DL-360p G7 and G8 HP DL360 G9 PostgreSQL mcp_core_linux_ple MCP_ _ ESXi 5.5 VMware MCP_MediaServer_ _ _29 AMS apps mcp_core_linux_ple rsit-server MySQL Enterprise Server - Advanced ESXi 5.5 VMware (See note 10.) (See note 10.) (See note 10.) 7

8 Table 4. UC APL Product Summary (continued) Product Components (See note 1.) Component Name (See note 2.) Version Customer-provided, STIG-compliant PC with Microsoft Windows 7 SP1 or Windows 10 Soft Client Aura AS5300 UC Client (See note 10.) (hardened, CAC disabled by default) (hardened, CAC enabled by default) NOTES: 1. The detailed component and subcomponent list is provided in Reference (c), Enclosure Components bolded and underlined were tested by JITC. The other components in the family series were not tested but are also certified for joint use. JITC certifies those additional components because they utilize the same software and similar hardware and JITC analysis determined them to be functionally identical for interoperability certification purposes. 3. For both CM and CMM-FM the HP DL360-G7 and the Dell R610 server supports the SUT version of CM with both VMware and System Platform. Two servers are required for the High Availability configuration. The SUT CM and CMM are OVAs on a site-provided, high availability VMware platform. 4. The S8300D and S8300E communications core servers were included with DTR 1. The S8300D/E, which runs on the same software as the SUT, is a blade server that plugs into the G450 media gateway and can be used to replace the pair of external HP DL360 G9 servers that were integrated with the G450 media gateway as the hardware for the SUT. The S8300D/E utilizes the same trunk, line, and IP interfaces cards as were originally tested with the SUT. Based upon JITC analysis, the Avaya G450 media gateway with the S8300D blade server has less memory, less processing capability, and limited redundancy when compared to the pair of HP DL360 G9 servers with G450. Therefore, the SUT only meets the UCR requirements for a medium availability LSC when configured with the S8300D/E communications core servers. 5. The CMM and the CC Elite are OVA applications on the Core Server activated by a license. 6. The MM720 is certified for use based on similarity of its hardware and software to the MM721, which was tested and certified. 7. The G430 media gateway was included with DTR 1. The G430 media gateway is certified by similarity to the G450 media gateway, but has a smaller scale chassis and does not have redundancy. Therefore the SUT when configured with the G.430 only meets the UCR requirements for a medium availability. The G.430 cannot be configured with the EM200 expansion unit, which would enable the G430 media gateway to support more than 96 telephony users which is the maximum number of users that can be supported with a single point of failure. 8. The G650 media gateway is certified by similarity to the G450 media gateway, but cannot be deployed as a standalone Gateway, due to the fact that it does not support IPv6 or V Therefore, the G650 media gateway must be deployed with a G450 media gateway in order to meet IPv6 and V requirements. 9. The SUT IP 96XX use proprietary H.323 signaling and support assured services with Multi-level Precedence and Preemption. 10. These SUT AS5300 components provide voice and video soft client capability with Multi-level Precedence and Preemption. LEGEND: ACD Automatic Call Distribution AMS Avaya Media Server APL Approved Products List AS Application Server AVP Appliance Virtualization Platform BRI Basic Rate Interface CAC Common Access Card CC Call Center CL Command Line CLAN Control Local Area Network CM Communication Manager CMM Communication Manager Messaging CP Communications Protocol DL Digital Line DCP Digital Communications Protocol E1 European Basic Multiplex Rate EI End Instrument FM Federal Market G Generation HA High Availability HP Hewlett Packard IBM International Business Machines IP Internet Protocol IPSI Internet Protocol Server Interface IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 JITC Joint Interoperability Test Command LSC Local Session Controller Mbps Megabits per second MCP Multimedia Communication Platform MP Media Pack MM Media Modules NA Not Applicable OAM&P Operations, Administration, Maintenance, and Provisioning OVA Open Virtual Applications PC Personal Computer SESM Session Manager SP Service Pack SIP Session Initiation Protocol SSH Secure Shell SSL Secure Socket Layer STIG Security Technical Implementation Guide SUT System Under Test TN Tracking Number T1 Digital Transmission Link Level 1 (1.544 Mbps) UC Unified Capabilities VLAN Virtual Local Area Network 8

9 4. Test Details. The extension of this certification is based upon DTR 1. The original certification, documented in Reference (c), is based on interoperability testing, review of the vendor s Letters of Compliance (LoC), Defense Information Systems Agency (DISA) adjudication of open test discrepancy reports (TDRs), and DISA Certifying Authority (CA) Recommendation for inclusion on the UC APL. Testing was conducted at JITC s Global Information Grid Network Test Facility at Fort Huachuca, Arizona, from 13 June through 24 June 2016 using test procedures derived from Reference (d). Review of the vendor s LoC was completed on 13 June DISA s adjudication of outstanding TDRs was completed on 12 July Cybersecurity testing was conducted by JITC-led Cybersecurity test teams and the results are published in a separate report, Reference (e). The Joint Interoperability Certification of the Avaya Aura Communication Manager (CM) Release is listed in Reference (f). The Joint Interoperability Certification of the Avaya Aura Application Server (AS) 5300 with Software Release 3.0 Service Pack (SP) 7 Enterprise Session Controller (ESC) and LSC is listed in Reference (g). This DTR 1 requested the addition of the S8300D and S8300E communications core servers as part of the SUT as well as the G430 media gateway. The S8300D/E, which runs on the same software as the SUT, is a blade server that plugs into the G450 media gateway and can be used to replace the pair of external Hewlett-Packard (HP) DL360 Generation (G) 9 servers that were integrated with the G450 media gateway as the hardware for the SUT. The S8300D/E utilizes the same trunk, line, and Internet Protocol (IP) interfaces cards as were originally tested with the SUT. Based upon JITC analysis, the Avaya G450 with the S8300D/E blade servers has less memory, less processing capability, and limited redundancy when compared to the pair of HP DL360 G9 servers with G450 media gateway; therefore, the SUT only meets the UCR requirements for a medium availability LSC when configured with the S8300D/E communications core servers. Additionally, the S8300D/E communications core servers were previously certified with the Avaya CM listed in Reference (f). The G430 media gateway utilizes the same software and modules as the G450 media gateway, but is a smaller scale chassis and does not have redundancy. Based upon the similarities between the G430 and G450 media gateways, JITC added the G430 media gateway to the certification letter with the restriction that it not be configured with the EM200 expansion unit, which would enable the G430 media gateway to support more than 96 telephony users; the maximum number of users that can be supported with a single point of failure. Additionally, the G430 media gateway was previously certified with the Avaya CM listed in Reference (f). JITC analysis determined the addition of the servers and the media gateway has no impact on the interoperability certified features and functions of the SUT; therefore, no interoperability testing was required. DISA UC Certification Office concurred that no additional IA testing was required because the addition of the servers and the media gateway does not alter the security posture of the solution. Therefore, the original DISA IA accreditation applies to this DTR and JITC approves this DTR without any additional testing. 5. Additional Information. JITC distributes interoperability information via the JITC Electronic Report Distribution (ERD) system, which uses Sensitive but Unclassified IP Data 9

10 (formerly known as NIPRNet) . Interoperability status information is available via the JITC System Tracking Program (STP). STP is accessible by.mil/.gov users at Test reports, lessons learned, and related testing documents and references are on the JITC Joint Interoperability Tool (JIT) at Due to the sensitivity of the information, the Information Assurance Accreditation Package (IAAP) that contains the approved configuration and deployment guide must be requested directly from the Unified Capabilities Certification Office (UCCO), All associated information is available on the DISA UCCO website located at 6. Point of Contact (POC). The JITC point of contact is Sibylle Gonzales, commercial telephone (520) , DSN telephone , FAX DSN ; address mailing address Joint Interoperability Test Command, ATTN: JTE (Sibylle Gonzales) P.O. Box 12798, Fort Huachuca, AZ The UCCO tracking number for the SUT is FOR THE COMMANDER: Enclosure a/s RIC HARRISON Chief Networks/Communications and UC Division Distribution (electronic mail): DoD CIO Joint Staff J-6, JCS USD(AT&L) ISG Secretariat, DISA, JTA U.S. Strategic Command, J665 US Navy, OPNAV N2/N6FP12 US Army, DA-OSA, CIO/G-6 ASA(ALT), SAIS-IOQ US Air Force, A3CNN/A6CNN US Marine Corps, MARCORSYSCOM, SIAT, A&CE Division US Coast Guard, CG-64 DISA/TEMC DIA, Office of the Acquisition Executive NSG Interoperability Assessment Team DOT&E, Netcentric Systems and Naval Warfare Medical Health Systems, JMIS IV&V HQUSAISEC, AMSEL-IE-IS UCCO 10

11 ADDITIONAL REFERENCES (c) Joint Interoperability Test Command, Memo, JTE, Joint Interoperability Certification of the Avaya Aura, 22 August 2016 (d) Joint Interoperability Test Command, Session Controller (SC) Test Procedures Version 1.0 for Unified Capabilities Requirements (UCR) 2013 Change 1, 15 March 2016 (e) Joint Interoperability Test Command, Cybersecurity Assessment Report for Avaya Aura Communication Manager (CM) Release (Rel.) (Tracking Number ), 20 July 2016 (f) Joint Interoperability Certification of the Avaya Aura Communication Manager (CM) Release with Patch _Ver_1_0 Revision 1 (Tracking Number ), August 2014 (g) Joint Interoperability Certification of the Avaya Aura Application Server (AS) 5300 with Software Release 3.0 Service Pack (SP) 7 Enterprise Session Controller (ESC) and Local Session Controller (LSC) (Tracking Number ), 28 May 2014 Enclosure