DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND Joint Interoperability Test Command (JTE) 19 October 2017

Transcription

1 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 19 October 2017 MEMORANDUM FOR DISTRIBUTION Revision 1 (Enclosure 4) SUBJECT: Joint Interoperability Certification of the Forum Communications Consortium III, Release 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, Change 1, June 2015 (c) through (d), see Enclosure 1 1. Certification Authority. Reference (a) establishes the Joint Interoperability Test Command (JITC) as the Joint Interoperability Certification Authority (CA) for Department of Defense Information Network (DoDIN) products, Reference (b). 2. Conditions of Certification. Forum Communications Consortium III, with Software Release , is hereinafter referred to as the System Under Test (SUT). The SUT meets the critical requirements of the Unified Capabilities Requirements (UCR), Reference (b), and is certified for joint use, with the optional capability of Multi-Level Precedence & Preemption (MLPP), on the Defense Information Systems Network (DISN) as an audio only (AO) Unified Capabilities Conferencing System (UCCS) with no waivers, conditions, or open discrepancies (See Table 1). The SUT was tested and certified for use in three different configurations: With the SUT registered as an integrated Assured Services (AS) Session Initiation Protocol (SIP) component of the following session controllers (SCs): REDCOM High Density Exchange (HDX) and SLICE, Unify Inc. OpenScape Voice, Genband_EXPERiUS, Avaya Aura Enterprise Session Controller (ESC), the Avaya AS5300 and the NEC Univerge 3C Session Controller (SC). The Consortium III was not tested with a direct connection to the NEC Univerge 3C SC; however, the prior version, Consortium II, was successfully tested with a direct connection to the NEC Univerge 3C SC. Therefore, by analysis the NEC Univerge 3C is certified for a direct connection to the Consortium III because there was no signaling change in the upgrade from the Consortium II. With the SUT as a standalone AS-SIP appliance, fronted by an SBC, and registered to any of the LSCs listed on the DoDIN Approved Products List (APL) via the Avaya AS5300 soft switch (SS). With the SUT connected to any time division, multiplexing (TDM) circuit switch currently, or previously, listed on the APL with a certified Integrated Services Digital Network (ISDN) Primary Rate Interface (PRI) T1 interface. The testing of this interface

2 was combined with the testing of the SUT as a standalone appliance and an integrated AS-SIP component of the above listed SCs. This certification expires upon changes that affect interoperability, but no later than the expiration date specified in the DoDIN APL memorandum. Table 1. Conditions Condition Operational Impact Remarks Not applicable; the Forum Communications Consortium III, with Software Release , meets all of the critical joint interoperability requirements in accordance with the Unified Capabilities Requirements (UCR), Reference (b). 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 a DoDIN APL product summary. Table 2. SUT Interface Status Interface Applicability (R), (O), (C) (See note 1.) Status Network Management Interface Remarks Ethernet 1/100 Mbps (SNMPv3) R Met See notes 3 and 4. Access (User) Interfaces (See note 2.) Ethernet 10 Mbps (AS-SIP) R Met See notes 3, and 4. Ethernet 100 Mbps (AS-SIP) R Met See notes 3, and 4. Ethernet 1000 Mbps (AS-SIP) R Met See notes 3 and 4. Ethernet Mbps (AS-SIP) R Not Met See note 3. Ethernet 10 Mbps (H.323) O Not Tested See note 5. Ethernet 100 Mbps (H.323) O Not Tested See note 5. Ethernet 1000 Mbps (H.323) O Not Tested See note 5. Ethernet Mbps (H.323) O Not Tested See note 5. T1 ISDN PRI (H.320) O Met E1 ISDN PRI (H.320) O Not Tested T1 CAS O Not Tested Serial O Not Tested End Instrument Interface ISDN (H.320) O Not Tested See note 5. Ethernet (H.323) O Not Tested See note 5. NOTE(S): 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 Enclosure The SUT must provide a minimum of one of the listed interfaces. 3. The UCR does not specify a particular IEEE 802.x standard interface for a UCCP 4. The SUT met the critical CRs and FRs for the IEEE 802.3i and IEEE 802.3u interfaces. 5. The SUT is an AO device. Video Only and Audio/Video requirements do not apply. 2

3 LEGEND: AO Audio Only ANSI American National Standards Institute AS-SIP Assured Services Session Initiation Protocol C Conditional CAS Channel Associated Signaling CR Capability Requirements DSN Defense Switched Network E1 European Basic Multiplex Rate (2.048 Mbps) FR Functional Requirements H.320 ITU Standard for narrowband VTC H.323 Standard for multi-media communications on packet-based networks IEEE Institute of Electrical and Electronics Engineers ISDN Integrated Services Digital Network Mbps Megabits per second O Optional PRI Primary Rate Interface R Required SUT System under Test T1 Digital Transmission Link Level 1 (1.544 Mbps) CR/FR ID Table 3. SUT Capability Requirements and Functional Requirements Status UCR Requirement (See note 1.) UCR 2013 Change 1 Reference Status 1 System Description See notes 2 and 3. 2 Service Met 3 Service Performance Met 4 Service Management See notes 2 and 3. NOTE(S): 1. The annotation of required refers to a high-level requirement category. The applicability of each sub-requirement is provided in Enclosure JITC-led Cybersecurity test team performed Cybersecurity testing and published the results in a separate report, Reference (d). 3. The SUT met the requirements for an AO Unified Capabilities Conferencing System (UCCS). LEGEND: AO Audio Only CR Capability Requirement FR Functional Requirement ID Identification JITC UC UCR SUT Joint Interoperability Test Command Unified Capabilities Unified Capabilities Requirements System Under Test Table 4. DoDIN APL Product Summary (UCCS Audio Only) Product Identification Product Name Forum Communications Consortium III Software Release UC Product Type(s) Unified Capabilities Conference System (UCCS) (Audio Only) Product Description The Consortium III Unified Capabilities Conferencing System (UCCS) provides real-time audio conferencing capabilities for the DoD. The system is audio-only; video conferencing is not supported. UC Certified Function Component/Sub-component Name (See note.) Version Remarks Audio Conferencing Server Consortium III Chassis CentOS Linux 6.9 Apache Web 2.2 Management Management Workstation Microsoft Windows 10 Site provided workstation/laptop NOTE(S): The detailed component and subcomponent list is provided in Enclosure 3, Table 3-3. LEGEND: APL Approved Product List DoDIN Department of Defense Information Network JITC Joint Interoperability Test Command SUT UC UCCS System Under Test Unified Capabilities Unified Capabilities Conference System 3

4 4. Test Details. This certification is based on interoperability testing, review of the vendor s Letters of Compliance (LoC), and DISA Certifying Authority Recommendation for inclusion on the DoDIN APL. JITC conducted testing at the Global Information Grid Network Test Facility at Fort Huachuca, Arizona, from 18 September through 22 September 2017 using test procedures derived from Reference (c). Reviewed the vendor s LoC on 18 September JITC-led Cybersecurity (CS) test teams conducted CS testing and published the results in a separate report, Reference (d). 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 sensitivity of the information, the CS Assessment Package (CAP) that contains the approved configuration and deployment guide must be requested directly from the Approved Products Certification Office (APCO), disa.meade.ie.list.approved-products-certificationoffice@mail.mil. All associated information is available on the DISA APCO website located at 6. Point of Contact (POC). JITC POC: Kathleen Kendall; commercial telephone (520) ; DSN telephone ; FAX DSN ; address: kathleen.a.kendall2.civ@mail.mil; mailing address: Joint Interoperability Test Command, ATTN: JTE (Kathleen Kendall), P.O. Box 12798, Fort Huachuca, AZ The APCO tracking number for the SUT is FOR THE COMMANDER: 4 Enclosures a/s for RIC HARRISON Chief Networks/Communications and UC Division 4

5 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-ISE-ME APCO 5

6 ADDITIONAL REFERENCES (c) Joint Interoperability Test Command, Unified Capabilities Conference System (UCCS) Test Procedures Version 1.0 for Unified Capabilities Requirements (UCR) 2013 Change 1, November 2015 (d) Joint Interoperability Test Command, Cybersecurity Assessment Report (CAR) of Forum Communications Consortium III Software Release (Tracking Number ), September 2017 Enclosure 1

7 CERTIFICATION SUMMARY 1. SYSTEM AND REQUIREMENTS IDENTIFICATION. Forum Communications Consortium III with Software Release , 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 Air Force Sponsor Point of Contact Thomas Jefferson, Building 730, Room 170, E. Crested Butte Ave, Buckley AFB, CO , Vendor Point of Contact Bob Hartwig, Address: 355 Ridge Ave., Crystal Lake, IL 60014, System Name Forum Communications Consortium III UCCS Increment and/or Version Product Category Audio Only (AO) Unified Capabilities Conference System (UCCS) System Background Tracking Previous certifications Forum Communications Consortium II with Software Release 9.1 TN# APCO ID System Tracking Program ID 6265 Requirements Source Unified Capabilities Requirements Unified Capabilities Requirements 2013, Change 1, Section 3.4 Remarks Test Organization(s) LEGEND: AFB Air Force Base AO Audio Only APCO Approved Products Certification Office ID Identification Joint Interoperability Test Command, Fort Huachuca, Arizona JITC STP UCCS Joint Interoperability Test Command System Tracking Program Unified Capabilities Conference System 2. SYSTEM DESCRIPTION. The Unified Capabilities Conference System (UCCS) category comprises three types of conference systems: Audio Only (AO), Video Only (VO), and Audio/Video (A/V). The AO conference system includes systems that support AO end instruments (EI). The VO conference system includes systems that support video only end instruments (i.e., video teleconferencing [VTC] systems). The Audio/Video (A/V) conference system includes systems that support dedicated AO and VO. An A/V conference system can be implemented as an integrated audio and video product, or as a combination of an audio conference system and a video conference system. The Consortium III Unified Capabilities Conferencing System (UCCS) provides real-time audio conferencing capabilities, the SUT is an audio-only conferencing system; video conferencing is not supported. The SUT can support 2,000 concurrent Session Initiation Protocol (SIP) calls or 1,920 Time Division Multiplexing (TDM) ports over multiple conference types including Meet Me, Preset, and Blast Dial Conferences. The conference system connects to the Defense Information System Network via the Wide Area Network (WAN), a soft switch (SS), Multifunction Switch, or a Local Session Controller on the Assured Services LAN using Assured Enclosure 2

8 Services (AS)-SIP with Encrypted Signaling using Transport Layer Security (TLS) and media using the Security Remote Transport Protocol. A site-provided, STIG-compliant, Common Access Card (CAC)-enabled workstation running Microsoft (MS) Windows 10 Operating System (OS) is used to manage the SUT. The server is a CentOS Linux platform installed on general-purpose server hardware and accessed via a standard web-browser. Apache 2.2 web server and the Consortium III v11.0 web application software are installed on the server. The Consortium III application includes WebView, an Application Programming Interface-based browser user interface which provides remote system administration and user feature access to schedule, create, modify, and monitor conferences and participants. Server-Client authentication is accomplished via CAC credentials and end user authenticated is accomplished via username and password credentials. Component 1. Consortium III Server The Consortium III is an audio conferencing server designed to support enterprise or government conferencing requirements. The server can support 2,000 concurrent SIP calls or 1,920 time division multiplexing (TDM) ports over multiple conference types including MeetMe, Preset, and Blast Dial conferences. The following interface boards are interchangeable within the server and provide T1\Primary Rate Interface (PRI) connectivity: Dual; 2 PRI spans Quad; 4 PRI spans Octal; 8 PRI spans Component 2. Management Workstation (site-provided) - STIG-compliant, CAC-enabled workstation used for both administrators and end-users to access the web-based (WebView) server user interface. 3. OPERATIONAL ARCHITECTURE. The DoDIN Capabilities (DC) architecture is a twolevel 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 DC architecture, therefore, consists of several categories of switches. Figure 2-1 depicts the notional operational DC architecture in which the SUT may be used. 4. TEST CONFIGURATION. The test team tested the SUT at the Joint Interoperability Test Command (JITC), Fort Huachuca, Arizona in a manner and configuration similar to that of a notional operational environment depicted in Figure 2-1. The test team verified the SUT s required functions and features using the test configuration depicted in Figure 2-2. The test team conducted interoperability testing of the AO UCCS components by testing the SUT with different vendor DoDIN Capabilities (DC) APL certified products as illustrated in Figure 2-3. The Cybersecurity (CS) testers used the same configuration. 5. METHODOLOGY. JITC conducted testing of the AO UCCS components using LAN requirements derived from the UCR 2013, Change 1, Reference (b), and the test procedures, 2-2

9 Reference (c). In addition to testing, JITC analyzed the vendor s Letters of Compliance (LoC) and verified the SUT met letter R requirements. 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 Soft-switch Standardized Tactical Entry Point Unified Capabilities Voice and Video over IP Extensible Messaging and Presence Protocol Figure 2-1. Notional DC Network Architecture 2-3

10 LEGEND: AEI AS-SIP End Instrument AS-SIP Assured Services Session Initiation Protocol A/V Audio/Video EI End Instrument H.320 ITU-T Standard for narrowband VTC H.323 ITU-T Standard for multi-media communications on packet-based networks ITA Information Technology Assessment ITU-T International Telecommunication Union - Telecommunication Standardization Sector PEI RTP SBC SC SRTP UCCS VTC WAN Proprietary End Instrument Real-Time Transport Protocol Session Border Controller Session Controller Secure Real-Time Transport Protocol Unified Capabilities Conference System Video Teleconference Wide Area Network Figure 2-2. UCCS Conference System Framework 2-4

11 LEGEND: LAN Local Area Network LSC Local Session Controller Mbps Megabits Per Second PRI Primary Rate Interface PSTN Public Switched Telephone Network SUT System Under Test T1 Transmission Carrier 1 WAN Wide Area Network Figure 2-3. SUT Interoperability Test Configuration for Standalone Operation 2-5

12 LEGEND: LAN Local Area Network LSC Local Session Controller Mbps Megabits Per Second PRI Primary Rate Interface PSTN Public Switched Telephone Network SUT System Under Test T1 Transmission Carrier 1 WAN Wide Area Network Figure 2-4. SUT Interoperability Test Configuration for Direct Connection to Session Controllers 6. INTEROPERABILITY REQUIREMENTS, RESULTS, AND ANALYSIS. The interface, Capability Requirements (CR) and Functional Requirements (FR), CS, and other UCCS requirements are defined by UCR 2013, Change 1, Section 3.4. Table 3-1 provides the SUT interface interoperability status and Table 3-2 provides the Capability Requirements (CR) and Functional Requirements (FR) status. The following sub-paragraphs provide testing details and results. a. The UCR 2013, Change 1, section includes the General System Description. (1) Overall System Description. The UCR 2013, section includes the UCCS System Description. The UCCS is intended to provide global real-time audio and video conferencing service capabilities for the DoD. Services include non-secure audio add on, video recording, archive and retrieval, bandwidth management, and seamless connectivity of users and resources. Furthermore, the conference system shall provide reservation and reservationless based scheduling conferencing management capabilities. The System Description requirements are listed in the subparagraphs below. 2-6

13 (2) System Architecture. The conference system shall provide, as a minimum, an Ethernet-based interface to the network. The SUT met this requirement with the vendor s LoC. (3) Cybersecurity. The conference system shall meet the CS requirements of all applicable DISA Security Technical Implementation Guides (STIGS). JITC-led CS test teams performed CS testing and published the results in a separate report, Reference (d). b. The UCR 2013, Change 1, Section includes the Service Description and Requirements for the Conferencing System. (1) Overall Service Description. This section describes the service requirements of the conference system. (a) Registration. All subscriber EIs and devices directly utilizing the conferencing system shall be required to register with the controller for call connection services. This registration requirement is not meant to exclude non-registered EIs and external parties from participating in a conference to which they have been invited by the registered subscriber that scheduled the conference. Section , Registration System, contains additional conference services registration system requirements. The SUT met this requirement with testing. (b) Point-to-Point Conferencing. The point-to-point consists of two participants with fully audio and/or video capabilities. 1. The conference system shall provide IP-based point-to-point conferencing. The SUT met this requirement with testing. 2. The conference system shall support EIs that are registered with the system to initiate point-to-point, fully interactive audio communications. The SUT met this requirement with testing. 3. Point-to-point conferencing shall be supported through conferencing services that enable the resolution of resource conflicts by calendaring and scheduling system application programming interfaces (APIs) with enterprise scheduling systems. The SUT did not meet this optional requirement. 4. The conference system shall provide real-time conferencing status capability; e.g., busy, online, offline. The SUT met this requirement with testing and the vendor s LoC. 5. The conference system shall support IP-based solutions using AS-SIP and T1.619A PRI supported endpoint support. The SUT met this requirement with testing and the vendor s LoC. 6. The conference system shall support interactive conferences using IP and [Optional] ISDN transport. These conferences shall consist of Proprietary and AS-SIP EIs only, [Optional] H.323 EIs only, [Optional] H.320 EIs only, or [Optional] a combination of H.323 EIs, 2-7

14 Proprietary and AS-SIP EIs, and H.320 EIs. ISDN transport applies only to conferences involving non-ip EIs. The SUT met this requirement with testing and the vendor s LoC. (c) Multipoint Conferencing. The multipoint conferencing requirements are listed in the subparagraphs below. 1. The conference system shall provide multipoint conferencing. A multipoint conference consists of three or more EIs in a conference call and shall include the following functions and features. The SUT met this requirement with testing and the vendor s LoC. 2. The conference system shall distribute fully interactive audio streams among multiple participants according to the channel bandwidth of each participant. The SUT met this requirement for audio streams with testing and the vendor s LOC. 3. The conference system shall accommodate users on the same conference at different video rates, resolutions, and frame rates according to EI capability and not at the lowest common denominator level. This requirement does not apply to the SUT, which is an AO UCCS. 4. The conference system shall provide interactive, multipoint conferences using IP transport. These conferences shall consist of Proprietary and AS-SIP EIs only, [Optional] H.323 EIs only, [Optional] H.320 EIs only, or [Optional] a combination of H.323 EIs Proprietary and AS-SIP EIs, and H.320 EIs. The SUT met the minimum requirement with native AS-SIP. In addition the SUT also meets the optional requirement for ISDN transport. The SUT met the requirements with a PRI T1 ANSI T1.619a or NI2 (ANSI T1.619a or ANSI T1.607) interface. ISDN transport applies only to conferences involving non-ip EIs. The SUT met this requirement with testing and the vendor s LoC. (d) Video Performance. This section describes the criteria and metrics required to ensure audio/video quality during multi-party conferences as well as point-to-to calls. 1. The conference system shall operate with IP network bit error rates of up to The SUT met this requirement with the vendor s LoC. 2. The conference system shall operate with an IP network packet loss of up to 1 percent and may use of packet loss concealment. The 1 percent packet loss design guideline is also supported by industry standard document Telecommunications Industry Alliance (TIA/Electronic Industries Alliance (EIA) TSB116. The SUT met this requirement with the vendor s LoC. 2-8

15 3. The conference system shall operate with IP network latency that meets recommendations of the International Telecommunications Union Telecommunication (ITU-T) Recommendation G.114. The SUT met this requirement with the vendor s LOC. The end-to-end one-way delay guideline is as follows: Less than 150 milliseconds for international connections. Less than 100 milliseconds for domestic connections. 4. The conference system shall incorporate jitter buffers that temporarily store arriving packets to minimize delay variation. The SUT met this requirement with the vendor s LoC. (e) In-Conference Control. The In-conference control requirements are listed in the subparagraphs below. 1. The conference system shall provide in-conference control. In-conference control shall include the following functions and features. The SUT met this requirement with testing. 2. The conference system shall provide a banner that indicates the classification of the content for each conference. This requirement does not apply to the SUT, which is an AO UCCS. 3. The conference system shall provide notification of participants joining and leaving a conference, and provide an end-of-conference warning to all participants. The SUT met this requirement with testing. 4. If the conference system supports time limits or scheduled end times for conferences, it shall provide an end-of-conference warning to all participants. The SUT met this requirement with testing. 5. If the conference system supports time limits or scheduled end times for conferences, it shall provide the ability to extend conferences, without disruption, to conferences in progress. The SUT met this requirement with testing. 6. The conference system shall support presentation capability for different screen layouts locally, manageable by each individual host. This requirement does not apply to the SUT, which is an AO UCCS. functionality: 7. The conference system shall provide the following conferencing chair control Voice activated switching. This requirement does not apply to the SUT, which is an AO UCCS. Broadcast mode. The SUT met this requirement with the vendor s LOC. Lecture Mode. The SUT met this requirement with the vendor s LOC. 2-9

16 If the conference system supports H.320, it shall provide video switching using H.243 control. This requirement does not apply to the SUT, which is an AO UCCS. Continuous presence. This requirement does not apply to the SUT, which is an AO UCCS. Add/Delete, Accept/Reject, Connect/Disconnect, Mute/Unmute, audio/video. The SUT met this requirement with testing and the vendor s LoC. (f) Transcoding. Transcoding converts audio and video media streams, allowing conference participants to communicate with each other even though their EIs are equipped with different encoding/decoding capabilities. The transcoding requirements are in the subparagraphs below. 1. The conference system shall provide transcoding availability regardless of the data speeds; the number of concurrent video calls; and the number of concurrent conferences, video sizes, frame rates, and conference modes (voice switching or continuous presence) without downgrading the conference to a lowest common denominator protocol. This requirement does not apply to the SUT, which is an AO UCCS. 2. The conference system shall provide automatic video transcoding without downgrading the conference to a lowest common denominator protocol. This requirement does not apply to the SUT, which is an AO UCCS. 3. The conference system shall provide automatic audio transcoding without downgrading the conference to a lowest common denominator protocol. The SUT met this requirement with testing and the vendor s LoC. (g) Variable Data Rates. The conference system shall provide support for variable data rates, the rate at which data (bits) is transmitted, usually expressed in bits per second (bps) per Conferencing Terminal Unit (CTU). The system shall support data rates of at least 64 kilobits per second (kbps) per CTU. The system shall provide speed matching and down speeding to facilitate adjustable data rates. This requirement does not apply to the SUT, which is an AO UCCS. (h) Audio Add-On. The conference system shall provide audio add-on features for audio-only participants in video conferences and support an external VoIP audio conference connecting to the video conference session. This requirement does not apply to the SUT, which is an AO UCCS. (i) Interactive Graphics Exchange. The interactive graphics exchange requirements are provided in the subparagraphs below. 1. The UCCS shall provide content sharing capability for participants to interact during video teleconferencing (VTC) sessions that allow participants to view and display the same presentation material at the same time. The system shall provide a dedicated live video 2-10

17 stream and a presentation video stream and still-frame graphics as specified in Section , Compression Algorithms and Audio/Video Protocols. This requirement does not apply to the SUT, which is an AO UCCS. 2. The conference system shall provide a means to allow participants to interactively view images from external sources with all or any of the participants in the conference. This requirement does not apply to the SUT, which is an AO UCCS. 3. The conference system shall provide realtime participation of any combination of EIs. The system shall provide still image exchange as specified in Section , Compression Algorithms and Audio/Video Protocols. This requirement does not apply to the SUT, which is an AO UCCS. 4. Interactive graphics exchanges capabilities shall be functional during the following conditions: This requirement does not apply to the SUT, which is an AO UCCS. Point-to-point and multipoint conferencing services. This requirement does not apply to the SUT, which is an AO UCCS Interoperability with different vendor EIs and variable graphic resolutions. This requirement does not apply to the SUT, which is an AO UCCS. Connections among participants using any video EIs, connection types, and at any rates. This requirement does not apply to the SUT, which is an AO UCCS. (j) Audio Conferencing. The conference system shall be able to support audio conferencing and provide the following functions and features. 1. The system shall be capable of accepting audio-only participants into a conference call for both scheduled and ad hoc video conferences. This requirement does not apply to the SUT, which is an AO UCCS. 2. The system shall have the capability to dial out to an external audio conferencing system to allow cascading between a multi-point VTC call with a multi-point audio call. This requirement does not apply to the SUT, which is an AO UCCS. 3. The system shall provide internal conferencing capabilities for the support of audio-only participants. The SUT met this requirement with testing and the vendor s LoC. (2) Integrated Services. This subsection describes services that are to be integrated in a means that provides the customer a user-friendly presentation, request, and access. (a) Web Access to Conference System. The SUT met this requirement with testing and the vendor s LoC. The conference system shall provide a Web-based portal for customer access to the UC conferencing services, features, and capabilities. As the conferencing services 2-11

18 change, the Web-based portal shall reflect those changes. Additionally, the conferencing services Web portal shall provide the following: 1. An enterprise-wide service for the identification and other pertinent information about users, conferencing services, and resources, and makes it accessible from any place at any time. The SUT met this requirement with the vendor s LoC. 2. Awareness of relevant, accurate information about the conferencing service to users at all levels (strategic, operational, and Tactical). The SUT met this requirement with the vendor s LoC. 3. An integrated scheduling system that provides users the ability to schedule one or a combination of video and audio conference services in one Web Interface. The SUT met this requirement for audio with testing and the vendor s LoC. (b) Recorded Content Retrieval and Management. The following subsections describe the Video Conferencing Recorded Content Retrieval and Management services to be provided by the system IAW the following requirements. This requirement does not apply to the SUT, which is an AO UCCS 1. The conference system shall provide a video conferencing recorded content request and retrieval system in accordance with (IAW) the following requirements. This requirement does not apply to the SUT, which is an AO UCCS. 2. The system shall provide the user the ability to view and listen to the recorded video conferences using a Web browser to retrieve streaming video. This requirement does not apply to the SUT, which is an AO UCCS. 3. The system shall provide a Web-based system for the meeting moderator to access the recorded video conference call. This requirement does not apply to the SUT, which is an AO UCCS. 4. The system shall inform the meeting moderator of the recorded video conference access information immediately after the completion of the video conference. This requirement does not apply to the SUT, which is an AO UCCS. 5. The system shall provide Web-based interfaces for users to search recorded content based on the combination of the following information: meeting topic, meeting date/time, keywords provided by meeting moderators, meeting leader name, meeting language, and meeting leader organization. This requirement does not apply to the SUT, which is an AO UCCS. 6. The Web interface shall provide a link to the content retrieval launch page. This requirement does not apply to the SUT, which is an AO UCCS. 2-12

19 7. The content retrieval launch page shall authenticate the users using PKI and prompt users to enter passwords defined by the meeting moderators during the meeting scheduling phase. This requirement does not apply to the SUT, which is an AO UCCS. 8. The content retrieval launch page shall maintain a record of every content request. The record of each request shall include the name, address, and E.164 number or IP address of the requester; the identification of the recording; and the date and time of the request. This requirement does not apply to the SUT, which is an AO UCCS. 9. The content retrieval launch page shall allow users to choose which format of the supported streaming media formats to use when playing back the retrieved content. This requirement does not apply to the SUT, which is an AO UCCS. 10. The system shall provide the end user controls during streaming to pause/resume and select segments to play. This requirement does not apply to the SUT, which is an AO UCCS. 11. The content retrieval launch page shall allow users to download the stored content of a conference meeting, if this option is permitted by the meeting's moderator. This requirement does not apply to the SUT, which is an AO UCCS. 12. The streaming shall comply with the Streaming Service Protocol Requirements described in Section , Compression Algorithms and Audio/Video Protocols. This requirement does not apply to the SUT, which is an AO UCCS. 13. The system shall ensure the compatibility of stored content with the latest versions of media player clients. This requirement does not apply to the SUT, which is an AO UCCS. (c) Audio Conferencing Recorded Content Management. The conference system shall provide a content management system IAW the following requirements. 1. The content management system shall comply with DoD R with clear marking and labeling. The SUT met this requirement with the vendor s LoC. 2. The content management system shall maintain recorded audio conferencing content ready for users to retrieve anytime for a period of 30 days after the completion of the conferences. The SUT met this requirement with the vendor s LoC. 3. The content management system shall archive recorded audio conferencing content into permanent storage after 30 days. The SUT met this requirement with the vendor s LoC. 4. The content management system shall allow users to request stored content from archive. The wait time to retrieve archived material shall be less than one working day. The SUT met this requirement with the vendor s LoC. 2-13

20 5. The archive material shall be kept at the same fidelity levels of the original recordings. Compression techniques that cause a loss of fidelity are not acceptable encoding schemes for archive material. The SUT met this requirement with the vendor s LoC. (3) Interoperability. The Interoperability requirements are listed in the subparagraphs below. This subsection describes the system s interoperability requirements. The system shall maximize the use of standards-based interfaces. The system shall use functions, protocols, and formats that are publicly available. The SUT met this requirement with the vendor s LoC. For video equipment, the conference system shall adhere to Federal Telecommunications Recommendation 1080B-2002 (FTR-1080B). This requirement does not apply to the SUT, which is an AO UCCS. (a) Compression Algorithms and Audio/Video Protocols. The Interoperability requirements are listed in the subparagraphs below. 1. The conference system shall support the following audio and video standards for video conferencing: (1) Audio Protocols (G.711, G.722). (2) Video Protocols (H.263, H.264). This requirement does not apply to the SUT, which is an AO UCCS. 2. The conference system shall support the following audio and video standards for video conferencing: (1) Audio Protocols (G.722.1, G.723.1, G.728, G.729/G.729A). (2) Video Protocols (H.261, H , H.264 (SVC). This requirement does not apply to the SUT, which is an AO UCCS. 3. The conference system shall support the following audio standards for audioonly conferencing: (1) Audio Protocols (G.711, G722.1, G.729/G.729A). The SUT met this requirement with testing and the vendor s LoC. 4. The conference system shall support the following audio standards for audioonly conferencing: (1) Audio Protocols (G722.1, G.723.1, G.728). The SUT met this optional requirement for G722.1 with testing and the vendor s LoC. 5. The conference system shall provide interoperability for all endpoint devices that support AS-SIP during call setup. The SUT met this requirement with testing and the vendor s LoC. 6. The conference system shall provide interoperability for all endpoint devices that support H.320 during call setup. This SUT does not meet this optional requirement. 7. The conference system shall provide interoperability for all end point devices that support H.323 during call setup. This SUT does not meet this optional requirement. 2-14

21 8. The conference system, including any proprietary Video EIs, shall support the following: This requirement does not apply to the SUT, which is an AO UCCS. Sub-Quarter Common Intermediate Format (SQCIF). This requirement does not apply to the SUT, which is an AO UCCS Quarter Common Intermediate Format (QCIF). This requirement does not apply to the SUT, which is an AO UCCS. Common Intermediate Format (FCIF, also called CIF). This requirement does not apply to the SUT, which is an AO UCCS. 4 Full Common Intermediate Format (4FCIF, also called 4CIF). This requirement does not apply to the SUT, which is an AO UCCS. 16 Full Common Intermediate Format (16FCIF), also called 16 Common Intermediate Format (16CIF). This requirement does not apply to the SUT, which is an AO UCCS. SD and HD video resolution formats for H.261, H.263, and H.264 codecs. The following are the Video Format Standards Video and Video Resolution: SQCIF-128x96, QCIF -176x144, SIF(525)-352x240,CIF/SIF(625)-352x288, 4SIF(525)-704x480, 4CIF/ASIF(625)-704x526, 16CIF-1408x1152,DCIF-528x384,SD-720x480,HD(720p)- 1280x720,HD(1080p)-1920x1080. This requirement does not apply to the SUT, which is an AO UCCS. 9. If H.320 or H.323 is supported, the conference system shall ensure that the freeze-frame image feature is compliant with ITU-T H.239. This requirement does not apply to the SUT, which is an AO UCCS. 10. If the conference system supports H.261, it shall ensure that the freeze-frame image feature is compliant with H.261 Annex D. This requirement does not apply to the SUT, which is an AO UCCS. 11. The system's freeze-frame image size shall support 4FCIF (4CIF), VGA, SVGA, XGA, and WSXGA+ when using H.239. This requirement does not apply to the SUT, which is an AO UCCS. 12. The system's freeze-frame image size shall support HD (720p) and HD (1080p) when using H.239. This requirement does not apply to the SUT, which is an AO UCCS. (b) H.320 and H.323 Protocols. A conference system that supports H.323/H.320 (03/2004) shall meet the following requirements for protocols being implemented: 1. ISDN/PRI on ISDN interfaces (including Alcatel-Lucent 5ESS PRI, GENBAND DMS PRI, and National ISDN PRI. This requirement does not apply to the SUT, which is an AO UCCS. 2. European E1 ISDN standards. This requirement does not apply to the SUT, which is an AO UCCS. 2-15

22 3. ISDN bonding up to 1.5 Mbps on T1 and 2 Mbps on E1 per International Organization for Standardization (ISO) This requirement does not apply to the SUT, which is an AO UCCS. 4. H.323 (2000) Version 4, H.320 (03/2004). This requirement does not apply to the SUT, which is an AO UCCS. 5. Far end camera control (FECC) H.281 and H.323 Annex Q. This requirement does not apply to the SUT, which is an AO UCCS. 6. Resource Availability Indicator (RAI)/Resource Availability Confirmation (RAC) for load balancing. This requirement does not apply to the SUT, which is an AO UCCS. 7. Chair control messages per H.245, H.242/H.243. This requirement does not apply to the SUT, which is an AO UCCS. 8. Direct, H.225 routed, and H.225-H.245 routed modes of H.323 gatekeeper operations. This requirement does not apply to the SUT, which is an AO UCCS. 9. Quality of Service (QoS) support using DSCP marking of IP packets. This requirement does not apply to the SUT, which is an AO UCCS. 10. Automatic down speed to available ISDN/IP bandwidth. This requirement does not apply to the SUT, which is an AO UCCS. 11. Automatic rate detection to match incoming video calls. This requirement does not apply to the SUT, which is an AO UCCS. 12. V.35/RS-449/EIA-530 Data Terminating Equipment (DTE) and Data Circuit- Terminating Equipment (DCE) interfaces (The implementation shall use EIA-530 interfaces, and the use of 13.V.35 and RS-449 interfaces shall be phased out where multiple interfaces are supported in equipment. RS-366 interfaces shall also be supported for dial signaling bypass devices). This requirement does not apply to the SUT, which is an AO UCCS. 13. H.239 for additional video channels or still images. This requirement does not apply to the SUT, which is an AO UCCS. (c) AS-SIP. The system shall ensure that all conferencing equipment meets the following protocol requirements: 1. The AS-SIP audio and video signaling conferencing requirements are specified in AS-SIP Section 10, Audio and Video Conference Services. The SUT met this requirement with the vendor s LoC. 2. FECC H.281 and H.323 Annex Q. This requirement does not apply to the SUT, which is an AO UCCS. 2-16

23 3. Chair control messages per H.245, H.242/H.243. This requirement does not apply to the SUT, which is an AO UCCS. 4. QoS support using DSCP marking of IP packets. The SUT met this requirement with testing and the vendor s LoC. 5. Automatic downspeed to available IP bandwidth. This requirement does not apply to the SUT, which is an AO UCCS. 6. Automatic rate detection to match incoming video calls. This requirement does not apply to the SUT, which is an AO UCCS. requirement. 7. Support T.140 for text messages. The SUT does not meet this optional (d) Video Mixing Modes. The conference system shall ensure that all video mixing modes meet the following standards: 1. Video Switching Mode. The system shall ensure that the system supports video switching according to H.243 and H.323. The design shall minimize the time to switch and the disruption of video when switching from one video source to another. This requirement does not apply to the SUT, which is an AO UCCS. 2. Video. Mixing (Picture Composition or Continuous Presence Mode). The system shall ensure that the system supports video mixing functions according to H.243 and H.323. The system shall support enhanced continuous presence multiple video mixing to include the 7 plus 1 format. This requirement does not apply to the SUT, which is an AO UCCS. (e) In-Conference Chair Control. The conference system shall ensure that the system supports chair control standards as defined in H.230, H.246, H.242, H.243 and H.245, including standards supporting Broadcast and Lecture mode capabilities. The following shall be supported: 1. H.320 chair control messages and procedures as defined in H.230, H.242, H.243, and H.245. This requirement does not apply to the SUT, which is an AO UCCS. 2. H.323 multipoint conferencing units (MCUs) shall support chair control messages and procedures as defined in H.323 and as carried forward to H.323 from H.243. This requirement does not apply to the SUT, which is an AO UCCS. 3. H.323 H.320 gateways shall follow the H.246 message translation tables related to chair control functions. This requirement does not apply to the SUT, which is an AO UCCS. (f) Audio Conferencing. Audio systems shall support in-dial and out-dial IAW the DISN World Wide Numbering Plan and the PSTN North American dialing plans. The SUT met this requirement with the vendor s LoC. 2-17

24 1. Audio Conferencing for TDM-specific requirements are in listed the subparagraphs below: 2. The audio system's PSTN interfaces shall support T1/E1 (AT&T TR62411 or Telcordia TR-NWT ). The SUT met this requirement with testing and the vendor s LOC. 3. The audio system's CAS interfaces shall support Alcatel-Lucent 5ESS and GENBAND DMS switches. The SUT does not meet this optional requirement. 4. The audio system's T1 PRI interfaces shall support Non-Facility Associated Signaling (NFAS) and D-channel backup, if the audio system supports more than two PRIs. The SUT does not meet this optional requirement. 5. The audio system's T1 interface shall support extended super frame (ESF) framing and with bipolar with eight-zero substitution (B8ZS)/ Alternate Mark Inversion (AMI) coding. The SUT met this requirement with the vendor s LoC. 6. The audio system's PSTN signaling module shall support ISDN PRI (5ESS, DMS, and National ISDN), and the PRI flavors of foreign countries such as Germany, Japan, and Korea. The SUT met this requirement with the vendor s LoC. 7. The audio system shall support the Dialed Number Identification Service (DNIS) feature where the original dialed numbers are presented as generic address parameters (GAPs). The SUT met this requirement with the vendor s LoC. 8. The audio system shall support the automatic number identification (ANI) feature and use it to identify a calling party, if applicable. The SUT met this requirement with the vendor s LoC. 9. Audio Conferencing for VoIP-specific requirements are in listed the subparagraphs below: 10. The audio system IP interfaces shall support static assignment of the IP address, mask, default router, and Domain Name Service (DNS) entries. The SUT met this requirement with the vendor s LoC. 11. The audio system shall support multiple DNS entries. If the primary DNS server does not respond to a DNS request, then a secondary DNS server shall be queried. The SUT met this requirement with the vendor s LoC. 12. The audio system shall support configurable transmission control protocol (TCP) ports for AS-SIP messaging. The SUT met this requirement with the vendor s LoC. 13. The audio system shall be able to set the IPv4/IPv6 Precedence Field bits of the Type of Service (TOS) byte and DSCP bits for media streams and signaling streams. The SUT met this requirement with testing and the vendor s LoC. 2-18

25 14. The audio system shall support Network Time Protocol (NTP), version 3 [RFC 1305]. The SUT met this requirement with the vendor s LoC. 15. The audio system shall support SNMPv3 [RFC 3414]. The SUT met this requirement with the vendor s LoC. 16. The audio system shall support Secure Real-Time Transport Protocol (SRTP) and Secure Real-Time Transport Control Protocol (SRTCP) [RFC 3711]. The SUT met this requirement with the vendor s LoC. 17. The audio system shall support SRTCP and accurately report jitter, delay, and packet loss information to the far end using Real-Time Transport Protocol (RTP) Control Protocol Extended Reports (RTCP XR) [RFC 3611]. The SUT met this requirement with the vendor s LoC. 18. The audio system's AS-SIP signaling module shall support RFC 3261 including loose route. The SUT met this requirement with the vendor s LoC. 19. The audio system's AS-SIP signaling module shall allow AS-SIP URLs for both incoming and outgoing calls. This includes all alphanumeric characters allowed in legal SIP URLs. The SUT met this requirement with the vendor s LoC. 20. The audio system's AS-SIP signaling module shall support Session Description Protocol (SDP) as defined in RFC The SUT met this requirement with the vendor s LoC. 21. The audio system's AS-SIP signaling module shall implement user "hold" feature by using a=inactive or a=sendonly, or by sending a mid-call INVITE that includes a session description that is the same as in the original request, but the "c" destination addresses for the media streams to be put on hold are set to zero:c=in IP The SUT met this requirement with the vendor s LoC. 22. The AS-SIP signaling module shall support AS-SIP Digest Authentication [RFCs 3261 and 3310]. The SUT met this requirement with the vendor s LoC. 23. The AS-SIP signaling module shall be able to reject incoming INVITE messages when the message does not come from pre-provisioned proxies. The SUT met this requirement with the vendor s LoC. 24. The AS-SIP signaling module shall support call transfer as specified in AS-SIP Section 9.6, Call Transfer. The SUT met this requirement with the vendor s LoC. 25. Audio systems shall support electronic numbering (ENUM) service registration for SIP (AS-SIP) Addresses-of-Record [RFC 3764]. The SUT met this requirement with the vendor s LoC. 2-19