DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 28 Aug 14

Transcription

1 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 28 Aug 14 MEMORANDUM FOR DISTRIBUTION Revision 1 SUBJECT: Joint Interoperability Certification of the Avaya Aura Communication Manager Release with Patch _Ver_1_0 References: (a) Department of Defense Instruction , "DoD Unified Capabilities (UC)," 9 December 2010 (b) DoD CIO, Memorandum, "Interim Guidance for Interoperability of Information Technology (IT) and National Security Systems (NSS)," 27 March 2012 (c) through (e), see Enclosure 1 1. Certification Authority. References (a) and (b) establish the Joint Interoperability Test Command (JITC) as the Joint Interoperability Certification Authority for the UC products. 2. Conditions of Certification. The Avaya Aura Communication Manager Release with Patch _Ver_1_0; hereinafter referred to as the System Under Test (SUT), meets the critical requirements of the Unified Capabilities Requirements (UCR), Reference (c), 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 three years from the date of the UC Approved Products List (APL) memorandum. None. None. Condition Table 1. Conditions UCR Waivers Conditions of Fielding Open Test Discrepancies Operational Impact Remarks The SUT G450 does not send the correct Preempt Not for Reuse signal over T1/E1 CAS. Minor See note 1. The SUT does not support RFC K Clear Channel over an IP network. When the invite has a Clear Mode/8000 audio attribute included in the SDP, the SUT sends the distant end a 488 (Not Acceptable Here) causing the call not to complete. Minor See note 1. The IP EI does not send the correct DSCP value on outbound AS-SIP trunk calls. Minor See note1. The SUT does not provide enough space to meet all of the required Domain Directory information. The SUT is limited to 26 characters. Minor See note 2. The SUT did not include video. Minor See note 2.

2 JITC Memo, JTE, Joint Interoperability Certification of the Avaya Aura Communication Manager Release with Patch _Ver_1_0 Table 1. Conditions (continued) NOTES: 1. DISA has accepted the vendor s POA&M and has adjudicated this discrepancy as minor. 2. DISA has accepted the vendor s POA&M and has adjudicated this discrepancy as minor. In the interim, if video service is required, it will be available as a DISA Enterprise Service. LEGEND: AS-SIP Assured Services Session Initiation Protocol IP Internet Protocol DISA Defense Information System Agency POA&M Plan of Action and Milestones DoD Department of Defense SDP Session Description Protocol DSCP Differentiated Services Code Point STIG Security Technical Implementation Guides E1 European Basic Multiplex Rate (2.048 Mbps) T1 Digital Transmission Link Level 1 (1.544 Mbps) EI End Instrument UCR Unified Capabilities 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. Interface Table 2. Interface Status Threshold CR/FR Requirements Status (See note 1.) Network Management Interfaces 10BaseT (R) 4, 6, 9, 13, 16, 21, 22 Met 100BaseT (R) 4, 6, 9, 13, 16, 21, 22 Met 1000BaseT (C) 4, 6, 9, 13, 16, 21, 22 Met 10BaseT (R) 100BaseT (R) 1000BaseT (R) 1, 5, 6, 7, 8, 10, 11, 13, 14, 15, 17, 18, 19, 20, 21, 22, 23 1, 5, 6, 7, 8, 10, 11, 13, 14, 15, 17, 18, 19, 20, 21, 22, 23 1, 5, 6, 7, 8, 10, 11, 13, 14, 15, 17, 18, 19, 20, 21, 22, 23 Network Interfaces (Line and Trunk) Met Met Met 2-wire analog (R) 1, 8, 15, 17, 19, 20, 21 Met ISDN BRI (C) 1, 8, 15, 17, 19, 20, 21 Met 10BaseT (C) 100BaseT (C) 1000BaseT (C) ISDN T1 PRI (ANSI T1.619a) (R) 2, 3, 5, 6, 7, 8, 11, 13, 18, 21, 22, 23 2, 3, 5, 6, 7, 8, 11, 13, 18, 21, 22, 23 2, 3, 5, 6, 7, 8, 11, 13, 18, 21, 22, 23 Legacy Interfaces (External) Met Met Met 3, 9, 12, 14, 20, 21 Met ISDN T1 PRI NI-2 (R) 3, 9, 12, 14, 20, 21 Met T1 CCS7 (ANSI T1.619a) (C) Remarks The SUT met the critical CRs and FRs for the IEEE 802.3i interface. 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 interface. The SUT met the critical CRs and FRs for the IEEE 802.3i interface with the SUT PEIs and softphones. The SUT met the critical CRs and FRs for the IEEE 802.3u interface with the SUT PEIs and softphones. The SUT met the critical CRs and FRs for the IEEE 802.3ab interface with the SUT PEIs and softphones. The SUT met the critical CRs and FRs for the 2-wire analog interface with the SUT 2-wire secure and non-secure analog instruments. The SUT met the critical CRs and FRs for the ISDN BRI interface. The SUT met the critical CRs/FRs for IEEE 802.3i for the AS- SIP trunk. The SUT met the critical CRs/FRs for IEEE 802.3u for the AS- SIP trunk. The SUT met the critical CRs/FRs for IEEE 802.3ab for the AS-SIP trunk. The met the critical CRs/FRs. This interface provides legacy DSN and TELEPORT connectivity. The SUT met the critical CRs/FRs. This interface provides PSTN connectivity. 3, 9, 12, 14, 20, 21 Not Tested The SUT does not support this conditional interface. 2

3 JITC Memo, JTE, Joint Interoperability Certification of the Avaya Aura Communication Manager Release with Patch _Ver_1_0 Interface Table 2. Interface Status Threshold CR/FR Requirements Status (See note 1.) Legacy Interfaces (External) (continued) T1 CAS (C) 3, 9, 12, 14, 20, 21 Partially Met E1 CAS (C) 3, 9, 12, 14, 20, 21 Partially Met Remarks The SUT met threshold CRs/FRs for DTMF and MFR1 with one minor exception. (See note 2.) The SUT met threshold CRs/FRs for DTMF and MFR1 with one minor exception. (See note 2.) E1 PRI (ITU-T Q.955.3) (C) 3, 9, 12, 14, 20, 21 Not Tested The SUT does not support this conditional interface. E1 PRI (ITU-T Q.931) (C) 3, 9, 12, 14, 20, 21 Not Tested The SUT does not support this conditional interface. NOTES: 1. The SUT high-level CR and FR ID numbers depicted in the Threshold CRs/FRs column can be cross-referenced in Table 3. These highlevel CR/FR requirements refer to a detailed list of requirements provided in Enclosure The SUT met the requirements with the exception noted in Table 1. DISA adjudicated this exception as minor. LEGEND: 10BaseT 10 Mbps Ethernet 100BaseT 100 Mbps Ethernet ISDN Integrated Services Digital Network 1000BaseT 1000 Mbps Ethernet ITU-T International Telecommunication Union - ANSI American National Standards Institute Telecommunication Standardization Sector AS-SIP Assured Services Session Initiation Protocol Mbps Megabits per second BRI Basic Rate Interface MFR1 Multi-Frequency Recommendation 1 C Conditional MLPP Multi-Level Precedence and Preemption CAS Channel Associated Signaling NI-2 National ISDN Standard 2 CCS7 Common Channel Signaling Number 7 OCONUS Outside the Continental United States CR Capability Requirement PEI Proprietary End Instrument DSN Defense Switched Network PRI Primary Rate Interface DTMF Dual Tone Multi-Frequency PSTN Public Switched Telephone Network E1 European Basic Multiplex Rate (2.048 Mbps) Q.931 Signaling Standard for ISDN ESC Enterprise Session Controller Q ISDN Signaling Standard for E1 MLPP ETSI European Telecommunications Standards Institute R Required FR Functional Requirement SS7 Signaling System 7 ID Identification T1 Digital Transmission Link Level 1 (1.544 Mbps) IEEE Institute of Electrical and Electronics Engineers T1.619a SS7 and ISDN MLPP Signaling Standard for T1 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 Partially Met (See note 2.) 3 Signaling Protocols (R) 2.4 Met 4 Registration and Authentication (R) 2.5 Met (See note 3.) 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 AS-SIP Gateways (C) 2.11 Met 11 Call Connection Agent (R) 2.14 Met 12 CCA Interaction with Network Appliances and Functions (R) 2.15 Partially Met (See note 2.) 13 Media Gateway (R) 2.16 Partially Met (See note 2.) 14 Worldwide Numbering & Dialing Plan (R) 2.18 Partially Met (See note 2.) 15 Management of Network Devices (R) 2.19 Met 3

4 JITC Memo, JTE, Joint Interoperability Certification of the Avaya Aura Communication Manager Release with Patch _Ver_1_0 CR/FR ID Table 3. SUT Capability Requirements and Functional Requirements Status UCR Requirement (High-Level) (See note 1.) UCR 2013 Reference Status 16 V Modem Relay Secure Phone Support (R) 2.20 Partially Met (See note 4.) 17 Requirements for Supporting AS-SIP Based Ethernet Devices for Voic Systems (C) 2.21 Not Tested 18 Local Attendant Console Features (O) 2.22 Met 19 MSC and SSC (O) 2.23 Not Tested 20 MSC, SSC, and Dynamic ASAC Requirements in Support of Bandwidth-constrained links (O) 2.24 Not Tested 21 Other UC Voice (R) 2.25 Met 22 Information Assurance Requirements (R) 4 Met (See note 3.) 23 IPv6 Requirements (R) 5 Partially Met (See note 4.) 24 Assured-Services (AS) Session Initiation Protocol (SIP) (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 Enclosure The SUT met the requirements with the exceptions noted in Table 1. DISA adjudicated these exceptions as minor. 3. Security is tested by DISA-led Information Assurance test teams and the results published in a separate report, Reference (e). 4. The G450 met all requirements and is approved as a standalone Gateway. 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, if the G650 is deployed, it must be deployed with a G450. LEGEND: ASAC Assured Services Admission Control MSC Master Session Controller AS-SIP Assured Services Session Initiation Protocol O Optional C Conditional R Required CCA Call Connection Agent SC Session Controller CR Capability Requirement SS Softswitch DISA Defense Information System Agency SSC Subtended Session Controller FR Functional Requirement SUT System Under Test ID Identification UC Unified Capabilities IPv6 Internet Protocol version 6 UCR Unified Capabilities Requirements Table 4. UC APL Product Summary Product Identification Product Name Software Release UC Product Type(s) Product Description Avaya Aura Communication Manager with Patch _Ver_1_0 Local Session Controller (LSC) Local Session Controller Product Components (See note 1.) Component Name (See note 2.) Version Remarks Communications Core Server HP DL360 PG8 (x2), Dell R620 (x2), HP DL360G7, See note Dell R610, Avaya S Voic messaging Communication Manager Messaging (CMM) See note 3. ACD Contact Center CC Elite See note 4. Enterprise Survivable Core server HP DL360 PG8 (x2), Dell R620 (x2), HP DL360G7, See note Dell R Media Gateway G450 (X2), G650 G /1, See note G650 Version Not Applicable 5. IP h.323 IPv4/v6 9621G, 9641G S9621_41HALBR6_5_0_0P _V474 IP h.323 IPv4/v6 9608, 9611G S9608_11HALBR6_5_0_0P _V474 IP h.323 IPv4 9610, 9620, 9620L, 9620C, 9630, 9640, 9650 ha96xxua3_0_21r02st.bin 4

5 JITC Memo, JTE, Joint Interoperability Certification of the Avaya Aura Communication Manager Release with Patch _Ver_1_0 Table 4. UC APL Product Summary Product Components (See note 1.) Component Name (See note 2.) Version Remarks DCP Hard client 2410, 9408, 6416D+M NA Legacy DCP endpoints 6402D, 2420, 6408D, 6402, 8410D NA Any analog endpoint used by DoD Any analog endpoint used by DoD NA Legacy BRI Endpoint 8510T NA Attendant Console Attendant Console 302C NA Softclient (site-provided PC) OneX Communicator Microsoft Windows 7 SP1 OneXC 6.2 SP2 Administration/management Microsoft Windows 7 SP1 Avaya Site Administration workstation (site-provided PC) ASA SP9 NOTES: 1. The detailed component and subcomponent list is provided in 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. Avaya CM6.3.6/CMM run on VMware servers designed for high availability failover configuration. CM and CMM run as virtual machines on the Core server. For both CM and CMM-Federal Market (FM) the HPDL360-G7 and the Dell R610 server supports the SUT version of CM with both VMware and System Platform. The Avaya S8800 server supports CM/CMM-FM only on System Platform. The vendor does not provide the server or VMWare. The SUT CM and CMM are Open Virtual Applications (OVAs) on a site-provided, high availability VMware platform. 4. The CCElite ACD is not on a separate server. The CCElite ACD feature is included in the Core Server; however, it requires a license to use this feature. 5. The G450 met all requirements and is approved as a standalone Gateway. 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, if the G650 is deployed, it must be deployed with a G450. LEGEND: ACD Automatic Call Distribution HP Hewlett Packard APL Approved Products List IP Internet Protocol ASA Avaya Site Administrator IPv4 Internet Protocol version 4 BRI Basic Rate Interface IPv6 Internet Protocol version 6 CM Communication Manager JITC Joint Interoperability Test Command CMM Communication Manager Messaging NA Not Applicable DCP Digital Communications Protocol PC Personal Computer DoD Department of Defense SP1 Service Pack 1 FM Federal Market UC Unified Capabilities 4. Test Details. This certification is based on interoperability testing, review of the vendor s Letters of Compliance (LoC), 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 2 through 27 June 2014 using test procedures derived from Reference (d). Patches were applied and regression testing was conducted on 14 July Review of the vendor s LoC was completed on 26 June DISA adjudication of outstanding TDRs was completed on 14 August Information Assurance testing was conducted by DISA-led Information Assurance test teams and the results are published in a separate report, Reference (e). Enclosure 2 documents the test results and describes the tested network and system configurations. Enclosure 3 provides a detailed list of the interface, capability, and functional requirements. 5. Additional Information. JITC distributes interoperability information via the JITC Electronic Report Distribution (ERD) system, which uses Sensitive but Unclassified IP Data (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 5

6 JITC Memo, JTE, Joint Interoperability Certification of the Avaya Aura Communication Manager Release with Patch _Ver_1_0 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 Capt. Soamva Duong, commercial telephone (520) , DSN telephone , FAX DSN ; address mailing address Joint Interoperability Test Command, ATTN: JTE (Capt. Soamva Duong) P.O. Box 12798, Fort Huachuca, AZ The UCCO tracking number for the SUT is FOR THE COMMANDER: 3 Enclosures a/s for RIC HARRISON Chief Networks/Communications and UC Portfolio 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 6

7 ADDITIONAL REFERENCES (c) Office of the Department of Defense Chief Information Officer, Department of Defense Unified Capabilities Requirements 2013, Errata 1, 1 July 2013 (d) Joint Interoperability Test Command, Session Controller (SC) Test Procedures Version 1.0 for Unified Capabilities Requirements (UCR) 2013 Errata 1, Draft (e) Joint Interoperability Test Command, Information Assurance (IA) Assessment Report for Avaya Aura Communication Manager (CM) Release (Rel.) (Tracking Number ), Draft Enclosure 1

8 CERTIFICATION SUMMARY 1. SYSTEM AND REQUIREMENTS IDENTIFICATION. The Avaya Aura Communication Manager Release with Patch _Ver_1_0 is hereinafter referred to as the System Under Test (SUT). Table 2-1 depicts the SUT identifying information and requirements source. Table 2-1. System and Requirements Identification System Identification Sponsor United States Navy Sponsor Point of Contact Jennifer Park, Phone: Vendor Point of Contact William Stehling, Phone: System Name Avaya Aura Communication Manager Increment and/or Version with Patch _Ver_1_0 Product Category Local Session Controller (LSC) System Background Previous certifications None. Tracking UCCO ID System Tracking Program ID 4948 Requirements Source Unified Capabilities Requirements Unified Capabilities Requirements 2013, Errata 1 Remarks Test Organization(s) Joint Interoperability Test Command, Fort Huachuca, Arizona LEGEND: ID Identification UCCO Unified Capabilities Connection Office 2. SYSTEM DESCRIPTION. The Session Controller (SC) is a software-based call processing product that provides voice and video services to Internet Protocol (IP) telephones and media processing devices within a service domain. An SC extends signaling and session (call) control services to allow sessions to be established with users outside a given service domain via an IPbased long-haul network or via gateways to non-ip networks. The SC software and functions may be distributed physically among several high-availability server platforms with redundant call management modules and subscriber tables to provide robustness. Different types of SCs can be deployed, depending upon the service environment. These types are Local, Enterprise, and Master and Subtended. Local SCs (LSCs) are physically located at the Base/Post/Camp/Station (B/P/C/S) where the EIs they serve are located. The SUT organizes and routes voice, data, image, and video transmissions. It can connect to private and public telephone networks, Ethernet Local Area Networks (LAN), Asynchronous Transfer Mode networks, and the Internet. The SUT is an open, scalable, and secure telephony application, which provides user and system management functionality, call routing, application integration and extensibility, and enterprise communications networking. It is installed on a high availability Virtual Machine (VM)ware platform and optionally on XEN Hypervisor system platform with the Cent Operating System (OS) on the various commercially available server pairs. The CM solution supports dual stack Internet Protocol (IP) version 4(IPv4)/IP version 6 (IPv6). Enclosure 2

9 The system consists of CM6.3.6 and Communication Manager Messaging (CMM) as Open Virtual Applications (OVAs) on a high availability VMware platform residing on site-provided Hewlett Packard (HP)-DL360 PG8 (or similar) duplicated servers, management workstation (site-provided), 96x1 H.323 IPv6/IPv4 dual stack sets, 96xx H.323 IPv4, gateway (G)450 gateways, OneX Communicator soft client (resident on a site-provided workstation), 85xxT Basic Rate Interface (BRI)/Secure Telephone Equipment (STE), Analog, and Digital Communications Protocol (DCP) 24xx/64xx/84xx,94xx. HP-DL360 PG8 Core Servers (x2 for High Availability). Avaya CM6.3.6/CMM run on VMware servers designed for high availability failover configuration. CM and CMM run as virtual machines on the server. The vendor does not provide the server or VMWare. The SUT CM and CMM are OVAs on a site-provided, high availability VMware platform. IPv4/IPv6 dual stack is supported. For both CM and CMM-Federal Market (FM) the HPDL360-G7 and the Dell R610 server also supports the SUT version of CM with both VMware and System Platform. The Avaya S8800 server supports CM/CMM-FM only on System Platform. HP-DL360 PG8 Survivable Servers (x2 for High Availability). The Enterprise Survivable Core servers provide survivability by allowing backup servers to be placed in various locations in the customer s network. The backup servers supply service to port networks and gateways in the case where the main server pair fails or connectivity to the main server or server pair is lost. IPv4/IPv6 dual stack is supported. The vendor does not provide the server or VMWare. The SUT CM and CMM are OVAs on a site-provided, high availability VMware platform. Management Workstation (site-provided). The system is managed using a site-provided, STIG-compliant, Common Access Card (CAC)-enabled workstation with the Windows 7 Service Pack (SP)1 Operating System (OS) and Avaya Site Administrator (ASA) installed. The System Access Terminal (SAT) is available through the ASA package and uses a command line interface for telephony administration. Avaya 96x1 H.323 IPv6/IPv4 dual stack sets. The Avaya 96x1 Series use IP technology with Ethernet interfaces. These telephones use Dynamic Host Configuration Protocol (DHCP) to obtain dynamic IP Addresses and HTTP or HTTPS to download new software versions or customized settings for the telephones. The Avaya 96x1 Sets support dual stack IPv4/IPv6 implementations. Avaya 96xx H.323 IPv4. The Avaya 96xx series use IP technology with Ethernet interfaces. These telephones use DHCP to obtain dynamic IP Addresses and HTTP or HTTPS to download new software versions or customized settings for the telephones. The 96xx sets only support IPv4 for current legacy installations. G450 Gateway. The G450 gateways provide a scalable platform for delivery of Avaya CMbased IP telephony applications, including support for dual stack IPv4/IPv6 with expandable capabilities by deploying between 1 and 250 gateways; two are included in this assessment. Standard Local Survivability provides a local G450 Gateway with a limited subset of CM functionality when there is no IP-routed Wide Area Network (WAN) link available to the main 2-2

10 server or when the main server is unavailable. The gateways vary in terms of features based on the following Media Modules (MM): Media Modules for G450 gateway MM710 Transmission Carrier 1 (T1)/European Interface Standard 1 (E1). The MM710 T1/E1 terminates a digital T1 or E1 connection to either private enterprise network trunks or to trunks to the public network and has a built-in Channel Service Unit (CSU). MM711 Analog. The MM711 provides eight (8) ports of features and functionality for analog trunks and telephones. MM712 DCP. The MM712 DCP connects up to eight (8) 2-wire DCP voice terminals. MM716 Analog. The MM716 provides 24 analog ports supporting telephones, modem, and facsimiles. These ports can also be configured as Direct Inward Dialing (DID) trunks with either wink-start or immediate-start. The 24 ports are provided through a 25- pair Registered Jack (RJ)-21X Amphenol connector, which can be connected by an Amphenol cable to a breakout box or punch down block. MM717 DCP. The Avaya MM717 DCP provides 24 DCP ports connected through an RJ-21X Amphenol connector. The MM717 supports simultaneous operation of all 24 ports. Each port can be connected to a 2-wire DCP telephone. The MM717 does not support 4-wire DCP telephones. MM720/721 BRI. The MM720/721 BRI module provides eight ports supporting telephone and data transmission. For BRI trunking, the module supports up to eight BRI interfaces to the central office at the Integrated Services Digital Network (ISDN) S/T reference point. For BRI endpoints, each of the eight ports supports integrated voice and data endpoints for up to two BRI stations or data modules or both. The module supports 4-wire S/T ISDN BRI on each interface. OneX Soft Client. The client uses a site-provided workstation installed with OneX Communicator software and Microsoft Windows 7 SP1. The UC softphone provides enterprise users with access to all their communications tools. It also provides business users with a consistent interface for Avaya Aura CM through H.323 protocol. 85xxT (BRI/STE). The Avaya 8510T model is a voice/data terminal used with the ISDN communication system through a 4-wire T -interface. Analog Telephone. A simple telephone used to make Public Switched Telephone Network calls. DCP 24xx/64xx/84xx/94xx. The Avaya DCP sets use digital communications protocol, providing multi-line functionality (and displays in some sets) when connected to either DCP TN cards or DCP medial modules. 3. OPERATIONAL ARCHITECTURE. The UC architecture is a two-level network hierarchy consisting of Defense Information Systems Network (DISN) backbone switches and Service/Agency installation switches. The Department of Defense (DoD) Chief Information Officer (CIO) and Joint Staff policy and subscriber mission requirements determine which type of switch can be used at a particular location. The UC architecture, therefore, consists of several 2-3

11 categories of switches. Figure 2-1 depicts the notional operational UC architecture in which the SUT may be used and Figure 2-2 the LSC functional model. 4. TEST CONFIGURATION. The test team tested the SUT at JITC, Fort Huachuca, Arizona in a manner and configuration similar to that of a notional operational environment. Testing of the system s required functions and features was conducted using the test configuration depicted in Figure 2-3. Information Assurance testing used the same configuration. 5. METHODOLOGY. Testing was conducted using LSC requirements derived from the Unified Capabilities Requirements (UCR) 2013, Errata 1, Reference (c), and Session Controller test procedures, Reference (d). Any discrepancies noted were documented in Test Discrepancy Reports (TDRs). The vendor submitted Plan of Action and Milestones (POA&M) as required. The TDRs were adjudicated by DISA as minor. Any new discrepancy noted in the operational environment will be evaluated for impact on the existing certification. These discrepancies will be adjudicated to the satisfaction of DISA via a vendor POA&M, which will address all new critical TDRs within 120 days of identification. 2-4

12 LEGEND: DCO Defense Connection Online DISA Defense Information Systems Agency DISN Defense Information Systems Network DoD Department of Defense EI End Instrument IAP Internet Access Point IM Instant Messaging IP Internet Protocol ISP Internet Service Provider LAN Local Area Network MCEP Multi Carrier Entry Point NETOPS PKI PSTN QoS SBC SC SS STEP UC VVoIP XMPP Network Operations Public Key Infrastructure Public Switched Telephone Network Quality of Service Session Border Controller Session Controller Softswitch Standardized Tactical Entry Point Unified Capabilities Voice and Video over IP Extensible Messaging and Presence Protocol Figure 2-1. Notional UC Network Architecture 2-5

13 LEGEND: AEI AS-SIP End Instrument ASAC Assured Services Admission Control ASLAN Assured Services Local Area Network AS-SIP Assured Services Session Initiation Protocol B2BUA Back-to-Back User Agent CAS Channel Associated Signaling CCA Call Connection Agent CCS7 Common Channel Signaling 7 DoD Department of Defense EO End Office ISDN Integrated Services Digital Network IWF Interworking Function LSC Local Session Controller MFSS Multifunction Softswitch MG Media Gateway MGC PBX PEI PRI PSTN SBC SC SG SIP SMEO SS TDM UC WAN Media Gateway Controller Private Branch Exchange Proprietary End Instrument Primary Rate Interface Public Switched Telephone Network Session Border Controller Session Controller Signaling Gateway Session Initiation Protocol Small End Office Softswitch Time Division Multiplexing Unified Capabilities Wide Area Network Figure 2-2. LSC Functional Reference Model 2-6

14 LEGEND: ASLAN Assured Services Local Area Network BRI Basic Rate Interface CAS Channel Associated Signaling CMM Communications Manager Messaging DCP Data Communications Protocol DSN Defense Switched Network E1 European Basic Multiplex Rate G Gateway IP Internet Protocol IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 HP Hewitt Packard LSC Local Session Controller Mbps Megabits per second PRI Primary Rate Interface PSTN Public Switched Telephone Network SBC Session Border Controller STE Secure Terminal Equipment SUT System Under Test T1 Digital Transmission Link Level 1 UC Unified Capabilities WAN Wide Area Network Figure 2-3. SUT Test Configuration 2-7

15 6. INTEROPERABILITY REQUIREMENTS, RESULTS, AND ANALYSIS. The interface, Capability Requirements (CR) and Functional Requirements (FR), Information Assurance (IA), and other requirements for LSCs are established by UCR 2013, Errata 1, sections 2, 4, and 5. a. The UCR 2013, Errata 1, section 2.2, states that it is expected that all Assured Services products, such as SCs and SSs, will support vendor-proprietary VVoIP features and capabilities. The product s support for these vendor-proprietary VVoIP features and capabilities shall not adversely affect the required operation of the MLPP or ASAC features on that product. In addition, the SC shall meet the requirements in the subparagraphs below. (1) The UCR 2013, Errata 1, section 2.2.1, includes four types of call forwarding features considered for UC: Call Forwarding Variable (CFV), Call Forwarding Busy Line (CFBL), Call Forwarding - Don t Answer - All Calls (CFDA), and Selective Call Forwarding (SCF). Call forwarding interaction with MLPP and a reminder ring for call forwarding features are optional. The SUT met this requirement with testing and the vendor s LoC. (2) The UCR 2013, Errata 1, section 2.2.2, includes the requirements for MLPP Interactions with Call Forwarding. If a call is forwarded by a CF feature that supports MLPP, the precedence level of the call shall be preserved during the forwarding process. This section includes the following features: Call Forwarding at a Busy Station and Call Forwarding - No Reply at Called Station. The SUT met this requirement with testing. (3) The UCR 2013, Errata 1, section 2.2.3, includes the requirements for Precedence Call Waiting. The following treatments apply to precedence levels of PRIORITY and above: Busy With Higher Precedence Call, Busy With Equal Precedence Call, No Answer, Line Active With a Lower Precedence Call, and Call Waiting for Single Call Appearance VoIP Phones. The SUT met this requirement with testing. (4) The UCR 2013, Errata 1, section 2.2.4, includes the requirements for Call Transfer. The two types of call transfers are normal and explicit. A normal call transfer is a transfer of an incoming call to another party. An explicit call transfer happens when both calls are originated by the same subscriber. This section includes the following features: Call Transfer Interaction at Different Precedence Levels and Call Transfer Interaction at Same Precedence Levels. The SUT met this requirement with testing. (5) The UCR 2013, Errata 1, section 2.2.5, Call Hold, states that the calls on hold shall retain the precedence of the originating call. The SUT met this requirement with testing. (6) The UCR 2013, Errata 1, section 2.2.6, includes the requirements for Three-Way Calling (TWC). The SUT met this requirement with testing. (7) The UCR 2013, Errata 1, section 2.2.7, includes the requirements for Hotline Service. The SUT met this requirement with testing. 2-8

16 (8) The UCR 2013, Errata 1, section 2.2.8, includes the requirements for Calling Number Delivery. The SUT met this requirement with testing and the vendor s LoC. (9) The UCR 2013, Errata 1, section 2.2.9, includes the requirements for Call Pick-Up. The SUT met this requirement with testing and the vendor s LoC. (10) The UCR 2013, Errata 1, section , includes the requirements for Precedence Call Diversion. The SUT met this requirement with testing. (11) The UCR 2013, Errata 1, section , includes the requirements for Public Safety Voice Features. This section includes the following features: Basic Emergency Service (911), Tracing of Terminating Calls, Outgoing Call Tracing, Tracing of a Call in Progress, and Tandem Call Trace. The SUT met this requirement with testing and the vendor s LoC. b. The UCR 2013, Errata 1, section 2.3, includes the requirements for ASAC in the subparagraphs below. (1) The UCR 2013, Errata 1, section 2.3.1, includes the requirements for ASAC requirements related to voice. This section includes the following requirements: Voice Session Budget Unit, ASAC States, Session Control Processing with No Directionalization, and SC Session Control Processing with Directionalization. The SUT met this requirement with testing. (2) The UCR 2013, Errata 1, section 2.3.3, includes the requirements for ASAC Requirements for the SC and the SS Related to Video Services. The SUT did not include video. DISA has accepted the vendor s POA&M and has adjudicated this discrepancy as minor. In the interim, if this service is required, it should be provided on an Enterprise Service basis. c. The UCR 2013, Errata 1, section 2.4, includes the requirements for Signaling Protocols. This section also includes the Signaling Performance Guidelines, which include call setup and call tear-down times as well as guidelines for intra-enclave, inter-enclave and worldwide calls. The SUT met this requirement with testing. d. The UCR 2013, Errata 1, section 2.5, includes the requirements for Registration and Authentication. Registration and authentication between Network Elements (NEs) shall follow the requirements set forth in Section 4, Information Assurance. Security is tested by the Information Assurance Test Team and the results published in a separate report, Reference (e). This section includes additional Network Time Protocol (NTP) requirements. The SUT met this requirement with testing and the vendor s LoC. e. The UCR 2013, Errata 1, section 2.6, includes the requirements for SC and SS Failover and Recovery. An SC may be provisioned with direct links to any number of other SCs (i.e. direct tertiary routes) and provisioned with the set of addresses or record served by each SC with which it has a direct tertiary route. Each SC and SBC pairing shall support OPTIONS-based failover by at least one of the following methods under UCR 2013, Errata 1, sections or

17 (1) Section 2.6.1, SC Failover: Alternative A: The SC-Generated OPTIONS Method. This section covers SC-Generated OPTIONS, SC OPTIONS-based Failover, SC-based Failback and Failure Handling for Outbound Dialog-initiating INVITE. The SUT met this requirement with testing. (2) Section 2.6.2, SC Failover: Alternative B: The SBC-Generated OPTIONS Method. This section covers SBC-Generated OPTIONS, SBC-based Failover, SBC-based Failback and Failure Handling for Outbound Dialog-initiating INVITE. The SUT does not support this optional requirement. f. The UCR 2013, Errata 1, section 2.7, includes the requirements for Product Interfaces. This includes requirements for internal and external physical interfaces, interfaces to other networks, and DISA VVoIP EMS Interface. (1) The UCR 2013, Errata 1, section 2.7.1, states that internal interfaces are functions that operate internal to a System Under Test (SUT) or UC-approved product (e.g., SC, SS). The interfaces between SC/SS functions within an SC and Signaling Gateway (SG) are considered internal to the SC regardless of the physical packaging. These interfaces are vendor-proprietary and unique, especially the protocol used over the interface. Whenever the physical interfaces use Institute of Electrical and Electronics Engineers, Inc. (IEEE) Ethernet standards, they shall support auto-negotiation even when the IEEE standard has it as optional. This applies to 10/100/1000-T Ethernet standards; i.e., IEEE, Ethernet Standard 802.3, 1993; or IEEE, Fast Ethernet Standard 802.3u, 1995; and IEEE, Gigabit Ethernet Standard 802.3ab, The SUT met this requirement with testing. (2) The UCR 2013, Errata 1, section 2.7.2, states External Physical Interfaces Between Network Components are functions that cross the demarcation point between SUT and other external network components. Whenever the physical interfaces use IEEE Ethernet standards, they shall support auto-negotiation even when the IEEE standard has it as optional. This applies to 10/100/1000-T Ethernet standards; i.e., IEEE, Ethernet Standard 802.3, 1993; or IEEE, Fast Ethernet Standard 802.3u, 1995; and IEEE, Gigabit Ethernet Standard 802.3ab, This requirement does not preclude the use of other types of physical interfaces. The SUT met this requirement with testing and the vendor s LoC. (a) The SC (and its appliances), SS, and SBC shall support 10/100/1000-T Mbps Ethernet physical interfaces to ASLAN switches and routers. The SUT met this requirement with testing and the vendor s LoC. (b) In addition, PEI and AEI shall support 10/100-T Mbps Ethernet physical interfaces to ASLAN switches and routers. The SUT met this requirement with testing and the vendor s LoC. (3) The UCR 2013, Errata 1, section 2.7.3, states that interfaces to other networks, are interfaces where traffic flows from one network (e.g., UC) to another network (e.g., PSTN). The SUT met this requirement with testing and the vendor s LoC. The SUT was not tested for connectivity to DISN Teleport; therefore, this is not covered under this certification. 2-10

18 (a) The Deployable interface requirements are specified in Appendix A, Unique Deployed (Tactical), and Section 6, Network Infrastructure End-to-End Performance. These requirements are unique optional requirements for a deployed SC and were not tested. (b) The Assured Services subsystem shall interface the Teleport sites on both a TDM basis and an IP basis. An ANSI T1.619a MG with PRI signaling will be used for T1 trunks to the Teleport sites. If the Teleport site contains an SC, then the interface will be via the DISN WAN for both the media and signaling, with the signaling being AS-SIP (AS-SIP 2013) between the Teleport SC and the UC SS. The SUT met this requirement with testing. (c) The Assured Services subsystem shall interface with the PSTN and host-nation PTTs via the MG interfaces as specified in Section 2.16, Media Gateway. The SUT met this requirement with testing. (d) Voice and video interfaces with allied and coalition networks have not been defined. Therefore, the interface will remain TDM as specified in UCR 2013, Figure , DSN Design and Components. (4) The UCR 2013, Errata 1, section 2.7.4, states that SCs shall support a 10/100-Mbps Ethernet physical interface to the DISA VVoIP EMS. The interface will work in either of the two following modes using auto-negotiation: IEEE, Ethernet Standard 802.3, 1993; or IEEE, Fast Ethernet Standard 802.3u, The SUT met this requirement with testing. g. The UCR 2013, Errata 1, section 2.8, includes the requirements for the Product Physical, Quality and Environmental Factors. (1) The UCR 2013, Errata 1, section , includes the Product Availability requirements. This includes requirements for the following three availability options: High Availability, Medium Availability, and Medium Availability for non-command and Control (C2) users. The SUT met the requirement with the vendor s LoC. For High Availability, the SUT requires two communications core servers and enterprise survivable core servers. (a) High Availability. The Assured Services appliance shall have a hardware or software availability of (a nonavailability state of no more than 5 minutes per year). The vendor shall provide an availability model for the appliance showing all calculations and showing how the overall availability will be met. The subsystem(s) shall have no single point of failure that can cause an outage of more than 96 voice and/or video subscribers. To meet the availability requirements, all subsystem(s) platforms that offer service to more than 96 voice and/or video subscribers shall have a modular chassis that provides, at a minimum, the following: Dual Power Supplies, Dual Processors/Swappable Sparing (Control Supervisors), Termination Sparing, Redundancy Protocol, No Single Failure Point, Switch Fabric or Backplane Redundancy for Active Backplanes, Software Upgrades and Patches, Backup Power UPS Requirements, No Loss of Active Sessions. In addition, when an appliance component fails and the backup component takes over, each media stream for each active call shall remain active 2-11

19 during the failover, until either 1) timer expirations or lack of state information cause that call to terminate or 2) the EI subscribers on that call, naturally terminate the call. (b) Medium Availability. The Medium Availability SC shall have a hardware or software availability of (a non-availability state of no more than 53 minutes per year). The vendor shall provide an availability model for the appliance showing all calculations and showing how the overall availability will be met. In support of the availability requirements, all subsystem(s) platforms that offer service to more than 96 voice and/or video subscribers shall have a modular design and chassis that provides, at a minimum, the following: Dual Power Supplies, Software Upgrades and Patches, No Loss of Active Sessions. In addition, when an Appliance component fails and the backup component takes over, each media stream for each active call shall remain active during the failover, until either 1) timer expirations or lack of state information cause that call to terminate or 2) the EI subscribers on that call naturally terminate the call. (c) Medium Availability not for Special C2 users. The Medium Availability SC shall have a modular design and chassis that provides, at a minimum, the following: Dual Processors/Swappable Sparing (Control Supervisors), Termination Sparing, Redundancy Protocol, No Single Failure Point, Switch Fabric or Backplane Redundancy for Active Backplanes, and Backup Power UPS Requirements. (2) The UCR 2013, Errata 1, section , includes the Maximum Downtime requirements. This includes requirements for the following products: High Availability and Medium Availability. The SUT met this requirement with the vendor s LoC. For High Availability, the SUT requires two communications core servers and enterprise survivable core servers. (a) High Availability. The performance parameters associated with the ASLAN, SS, and High Availability SC, when combined, shall meet the following maximum downtime requirements: IP (10/100/1000 Ethernet) network links - 35 minutes per year and IP subscriber - 12 minutes per year. (b) Medium Availability. The performance parameters associated with the ASLAN, SS, and Medium Availability SC, when combined, shall meet the following maximum downtime requirements: IP (10/100/1000 Ethernet) network links - 82 minutes per year and IP subscriber 60 minutes per year. (3) The UCR 2013, Errata 1, section 2.8.4, states that, for the VoIP devices, the voice quality shall have a Mean Opinion Score (MOS) of 4.0 (R-Factor equals 80) or better, as measured IAW the E-Model. Additionally, these devices shall not lose two or more consecutive packets in a minute and shall not lose more than seven voice packets (excluding signaling packets) in a 5-minute period. This applies only to devices that generate media and have a Network Interface Card (NIC). The SUT met this requirement with testing. h. The UCR 2013, Errata 1, section 2.9, includes the requirements for End Instruments (EIs) in the subparagraphs below. 2-12

20 (1) The UCR 2013, Errata 1, section 2.9.1, includes the requirements for IP Voice End Instruments. This section includes the basic requirements, tones and announcements, audio codecs for voice instruments, VoIP telephone audio performance, VoIP sampling standard, softphones, and DSCP packet marking. The SUT met this requirement with testing with the following minor exception. The SUT IP EI does not send the correct DSCP value on outbound AS-SIP trunk calls. The SUT meets the requirement for intra-enclave calls; however, it does not support the requirement for calls placed via the AS-SIP trunk into the WAN. The administrative terminal/gui has a field to assign a unique DSCP value for each precedence level; however, these assigned values do not translate to the assigned DSCP value. Instead, the SUT assigns the DSCP value of 46, which is changeable. DISA has accepted the vendor s POA&M and adjudicated this discrepancy as minor. (2) The UCR 2013, Errata 1, section 2.9.2, includes the requirements for analog and ISDN BRI Telephone Support. The SUT met this requirement with testing and the vendor s LoC. (3) The UCR 2013, Errata 1, section 2.9.3, includes the requirements for Video End Instruments. Video EIs are considered associated with the SC and must have been designed in conjunction with the SC design. This section includes the basic requirements; display messages, tones, and announcements; video codecs including associated audio codecs; and H.323 video teleconferencing. The SUT did not include video. DISA has accepted the vendor s POA&M and has adjudicated this discrepancy as minor. In the interim, if this service is required, it should be provided on an Enterprise Service basis. (4) The UCR 2013, Errata 1, section 2.9.4, states that the PEI and AEI shall each be capable of authenticating itself to its associated SC and vice versa IAW Section 4, Information Assurance. The SUT met this requirement with testing. In addition, security is tested by the Information Assurance Test Team and the results published in a separate report, Reference (e). (5) The UCR 2013, Errata 1, section 2.9.5, states that the EI interface to the ASLAN shall be IAW Ethernet (IEEE 802.3) Local Area Network (LAN) technology. The 10-Mbps and 100-Mbps Fast Ethernet (IEEE 802.3u) shall be supported. The SUT met the requirements with testing. In addition, the SUT also met the requirements for the 1000 Mbps (IEEE 802.3ab) interface. (6) The UCR 2013, Errata 1, section 2.9.6, includes the requirements for Operational Framework for AEIs. This section contains SC and AS-SIP EI requirements to support a generic, multivendor-interoperable interface between a VVoIP SC and an AS-SIP VVoIP EI, which can be a voice EI, a secure voice EI, or a video EI. This generic, multivendorinteroperable interface uses AS-SIP protocol instead of the various vendor-proprietary SC-to-EI protocols. This section includes the following requirements: Requirements for Supporting AS- SIP EIs, Requirements for AS-SIP voice EIs, Requirements for AS-SIP Secure voice EIs, Requirements for AS-SIP video EIs, and AS-SIP video EI features. The vendor does not support AS-SIP EIs, which is an optional requirement. 2-13

21 (7) The UCR 2013, Errata 1, section 2.9.7, includes the requirements for Multiple Call Appearance Requirements for AS-SIP EIs. This section includes the following requirements: Multiple Call Appearance Scenarios, Multiple Call Appearances - Specific Requirements, and Multiple Call Appearances - Interactions With Precedence Calls. The SUT does not support AS- SIP EIs, which is an optional requirement. (8) The UCR 2013, Errata 1, section includes the requirements for PEIs, AEIs, TAs, and IADs using the ITU-T Recommendation V protocol. The SUT met this requirement with testing. The G650 gateway included in this certification by similarity to the G450 gateway does not support the ITU-T V protocol. The SUT does not support AEI, which is an optional requirement. (9) The UCR 2013, Errata 1, section includes the requirements for UC Products with Non-Assured Service Features. The SUT met this requirement with testing. (10) The UCR 2013, Errata 1, section includes the requirements for ROUTINE- Only EIs (ROEIs). SC support for ROEIs is optional; however, if they are supported the requirements in this section apply. The SUT met this requirement with testing and vendor s LoC. i. The UCR 2013, Errata 1, section 2.10 includes the requirements for Session Controllers. (1) The UCR 2013, Errata 1, section , states the SC shall meet all the requirements for Precedence-Based Assured Services (PBAS) and ASAC, as appropriate for VoIP and Video over IP services, as specified in Section , Multilevel Precedence and Preemption and Section 2.3, ASAC. The SUT met this requirement with testing. (2) The UCR 2013, Errata 1, section states the SC shall support AS-SIP over IP for signaling to SSs. The SC shall optionally support AS-SIP over IP signaling to AEIs. The SC shall optionally support proprietary VVoIP signaling to interface with PEI. The SUT met this requirement with testing and vendor s LoC with the following minor exception. The SUT did not include video. DISA has accepted the vendor s POA&M and has adjudicated this discrepancy as minor. In the interim, if this service is required, it should be provided on an Enterprise Service basis. The SUT does not support AEI, which is an optional requirement. (3) The UCR 2013, Errata 1, section , states that the SC shall support a Session Controller Location Service (SCLS) functionality that provides information on call routing and called address translation. The SUT met this requirement with testing. (4) The UCR 2013, Errata 1, section , states that the SC shall support the applicable Fault, Configuration, Accounting, Performance, and Security (FCAPS) Management and Audit Log requirements specified in Section 2.19, Management of Network Appliances. The SUT met this requirement with testing and the vendor s LoC. (5) The UCR 2013, Errata 1, section , states that the SC shall provide an interface to the DISA VVoIP Element Management System (EMS). The interface consists of a 10/