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

Transcription

1 DEFENSE INFORMATION SYSTEMS AGENCY P. O. BOX 549 FORT MEADE, MARYLAND IN REPLY REFER TO: Joint Interoperability Test Command (JTE) 5 January 2017 MEMORANDUM FOR DISTRIBUTION SUBJECT: Extension of the Joint Interoperability Certification of the TEO Technologies 78XX, 4104 and 4101 with Software Release xx References: (a) Department of Defense Instruction , "DoD Unified Capabilities (UC)," 9 December 2010 (b) Office of the Department of Defense Chief Information Officer, Department of Defense Unified Capabilities Requirements 2013 (UCR 2013) Change 1, June 2015 (c) through (f), see Enclosure 1. Certification Authority. Reference (a) establishes the Joint Interoperability Test Command (JITC) as the Joint Interoperability Certification Authority (CA) for UC products, Reference (b). 2. Conditions of Certification. The TEO Technologies 78XX, 4104, and 4101 with Software Release xx.04.23, hereinafter referred to as the (), is certified for joint use as a voice only, non-secure Assured Services Session Initiation Protocol (AS-SIP) End Instrument (EI) (AEI). The meets the critical requirements of the Unified Capabilities Requirements (UCR), Reference (b), and is certified for joint use as a voice only, non-secure AEI with the conditions described in Table 1. The was tested and is certified for use specifically with REDCOM High Density Exchange (HDX) and REDCOM SLICE 2100 Releases 4.0AR3PD, REDCOM Sigma Core Release 1.2, the NEC UNIVERGE 3C Release , Avaya Aura Application Server (AS)5300 Release 3.0 Service Pack (SP)12, Genband Inc. EXPERiUS 11.2, and the Unify OpenScape Voice (OSV) version (V) 9R0 Local Session Controllers (LSCs), along with the Avaya Aura AS5300 Release 3.0 SP12 Enterprise Session Controller (ESC). In addition, the is also certified with subsequent certified versions of the LSCs and ESCs listed above and on the UC APL. This certification expires upon changes that affect interoperability, but no later than the expiration date specified in the UC Approved Products List (APL) memorandum. The extension of this certification is for Desktop Review (DTR) 8, which was a request to update the Software Release from xx to xx and add the Unify OSV to the above list of LSCs that are certified with the. See Paragraph 4 for test details.

2 Table 1. Conditions.. Condition UCR Waivers Conditions of Fielding Open Test Discrepancies Per the vendor s LoC, the did not support DHCPv6. This discrepancy was resolved and successfully tested with DTR 2, which included Release xx During testing for DTR 1, the did not support Layer 2 internal CoS (p-bit) for signaling prioritization. This discrepancy was resolved and successfully tested with DTR 2, which included Release xx During testing for DTR 4, the did not class mark an unattended transfer at the highest precedence of the two call legs. This discrepancy was resolved and successfully tested with DTR 8, which included Release xx During testing for DTR 5, the did not did not send a ROUTINE RPH when first leg was dialed without a"9x" in an explicit attended call transfer. This discrepancy was resolved and successfully tested with DTR 8, which included Release xx LEGEND CoS Class of Service DHCPv6 Dynamic Host Control Protocol version 6 DTR Desktop Review LoC Letters of Compliance RPH UCR Operational Impact Resource Priority Header Unified Capabilities Requirements Remarks 3. Interoperability Status. Table 2 provides the interface interoperability status and Table 3 provides the Capability Requirements (CR) and Functional Requirements (FR) status. Table 4 provides a UC APL product summary. Table 2. End Instrument Interface Status Interface (See note.) Applicability Status Remarks Voice EIs 10Base-X Required The met the CRs and FRs for the IEEE 802.3i interface. 100Base-X Required The met the CRs and FRs for the IEEE 802.3u interface. 1000Base-X Conditional The does not support this conditional interface. 10GBase-X Conditional The does not support this conditional interface. Video EIs 10Base-X Required Not applicable. The is a voice only AEI. 100Base-X Required Not applicable. The is a voice only AEI. 1000Base-X Conditional The does not support this conditional interface. 10GBase-X Conditional The does not support this conditional interface. NOTE: The high-level requirements are depicted in Table 3. These high-level requirements refer to a more detailed list of requirements provided in Reference (c), Enclosure 3. LEGEND: 10Base-X 100Base-X 1000Base-X 10GBase-X AEI AS-SIP 10 Mbps (Baseband Operation, Twisted Pair) Ethernet 100 Mbps (Baseband Operation, Twisted Pair) Ethernet 1000 Mbps (Baseband Operation, Twisted Pair) Ethernet 10 Gigabit Ethernet over Fiber or Copper AS-SIP End Instrument Assured Services Session Initiation Protocol CR EI FR G IEEE Capability Requirement End Instrument Functional Requirement Gigabits Institute of Electrical and Electronics Engineers 2

3 Table 3. EI Capability Requirements and Functional Requirements Status CR/FR ID UCR Requirement (High-Level) (See note 1.) UCR 2013 Reference 1 IP Voice End Instruments EI Applicability 2 Analog and ISDN BRI Telephone Support EI (R) 3 Video EI Authentication to SC EI to ASLAN Interface AS-SIP Voice EI (R) 6 Operational Framework for AEIs and Video EIs AS-SIP Secure Voice EI (R) AS-SIP Video EI (R) AS-SIP Voice EI (R) 7 Multiple Call Appearance Requirements for AS-SIP EIs AS-SIP Secure Voice EI (R) AEI (O) 8 PEIs, AEIs, TAs, and IADs Using the V Protocol Secure PEI (O) ROEI (R) 9 ROEIs non-roei (R) Status (See note 2.) (See note 3.) (See note 3.) (See note 4.) 10 IPv6 Section 5 All IP EI (R) (See note 5.) 11 Cybersecurity Section 4 All EI (R) (See note 2.) 12 CoS Markings d. IP EI with shared access (R) (See note 6.) 13 Call Transfer PEI, AEI, SC, SS (R) (See note 7.) NOTES: 1. The annotation of required refers to a high-level requirement category. The applicability of each sub-requirement is provided in Reference (c), Enclosure Cybersecurity requirements in UCR 2013, Change 1, Section 4, are met by the vendor s LoC. In addition, cybersecurity testing is accomplished by JITC-led cybersecurity test teams and the results published in a separate report, Reference (e). 3. The is a voice only AEI. Therefore, the video, secure voice, and ROEI requirements do not apply. 4. Non-secure AEI phones do not use V V is used exclusively with TAs, IADs, and secure AEI phones. This requirement was changed to Optional for AEIs/PEIs with UCR 2013 Change 1, and the does not support this Optional requirement. 5. During the original test, the did not support DHCPv6. This discrepancy was resolved and successfully tested with Release xx via DTR During testing for DTR 1, the did not support Layer 2 internal CoS (p-bit) for signaling prioritization. This discrepancy was resolved and successfully tested with Release xx via DTR During testing for DTR 4, the EI did not class mark an unattended transfer at the highest precedence of the two call legs and during testing for DTR 5, the EI did not send a ROUTINE RPH when first leg was dialed without a"9x" in an explicit attended call transfer. These discrepancies were resolved and successfully tested with Release xx via DTR 8. LEGEND: AEI AS-SIP End Instrument AS-SIP Assured Services Session Initiation Protocol ASLAN Assured Services Local Area Network BRI Basic Rate Interface CoS Class of Service CR Capability Requirement DHCPv6 Dynamic Host Control Protocol version 6 DTR Desktop Review EI End Instrument FR Functional Requirement IAD Integrated Access Device ID Identification IP Internet Protocol IPv6 Internet Protocol version 6 ISDN JITC LoC O PEI R ROEI RPH SC SS TA UCR Integrated Services Defense Network Joint Interoperability Test Command Letters of Compliance Optional Proprietary End Instrument Required ROUTINE Only End Instrument Resource Priority Header Session Controller Softswitch Terminal Adapter Unified Capabilities Requirements 3

4 Table 4. UC APL Product Summary Product Identification Product Name TEO Software Release xx (See notes 1, 2, and 3.) UC Product Type(s) AEI Product Description The is a voice only, non-secure AEI. Product Components (See note 4.) Component Name (See note 5.) Version Remarks AEI (See note 1.) AEI 7810-TSG (See note 1.) AEI 7810-PoE-TSGA (See note 1.) AEI 7810-PoE-TSGB (See note 1.) AEI (See note 2.) AEI (See note 3.) This model is certified with or without the optional 8030x 30-button expander. NOTES: 1. The TEO 7810 Software Release was updated as follows: From to with DTR 1. From to with DTR 2. From to with DTR 3. From to with DTR 4. From to with DTR The TEO 4101 Software Release was updated as follows: From to with DTR 1. From to with DTR 2. From to with DTR 3. From to with DTR 4. From to with DTR The TEO 4104 Software Release was updated as follows: From to with DTR 1. From to with DTR 2. From to with DTR 3. From to with DTR 4. From to with DTR The detailed component and subcomponent list is provided in Reference (c), Enclosure Components bolded and underlined were tested by JITC. The other components in the family series were not tested but are also certified for joint use. JITC certifies those additional components because they utilize the same software and similar hardware and JITC analysis determined that they are functionally identical for interoperability certification purposes. LEGEND: AEI AS-SIP End Instrument APL Approved Products List AS-SIP Assured Services Session Initiation Protocol DTR Desktop Review JITC Joint Interoperability Test Command PoE TSG UC Power over Ethernet Telephone Security Group Unified Capabilities 4. Test Details. The extension of this certification is based upon DTR 8. The original certification, documented in Reference (c), was based on interoperability (IO) testing, review of the vendor s Letters of Compliance (LoC), Defense Information System Agency (DISA) adjudication of open Test Discrepancy Reports (TDRs), and DISA CA Recommendation for inclusion on the UC APL. IO testing was conducted at JITC s Global Information Grid Network Test Facility at Fort Huachuca, Arizona, from 2 through 12 April 2013 with the REDCOM HDX LSC and from 22 July through 13 September 2013 with the NEC UNIVERGE LSC using test procedures derived from Reference (d). Review of the vendor s LoC was completed on 21 October DISA adjudication of outstanding TDRs was completed on 1 November

5 The DISA CA provided a positive Recommendation based on the cybersecurity testing completed by JITC-led cybersecurity test teams and the results published in a separate report, Reference (e). DTR 8 was a request to update the Software Release from xx to xx and to add the Unify OSV to the list (see paragraph 2) of LSCs that are certified with the. JITC reviewed the DTR request and vendor release notes and determined that IO Verification and Validation (V&V) testing was required for this software update. No additional cybersecurity testing was required for this DTR because the DISA UC Certification Office concurred that there was no change in the cybersecurity posture of the with this software update; therefore, the original cybersecurity approval applies to this DTR. Test personnel conducted IO V&V testing at JITC s Global Information Grid Network Test Facility, Fort Huachuca, Arizona, from 28 November to 2 December Test results demonstrated that the successfully meets the referenced AEI requirements in table 2 when operated with any of the LSCs listed in paragraph 2 of this memorandum, including the Unify OSV, with no new test discrepancies. Additionally, two previous test discrepancies were closed during this V&V as denoted in Table 1. Therefore, JITC approves this DTR. 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 Information Assurance Accreditation Package (IAAP) that contains the approved configuration and deployment guide must be requested directly from the Unified Capabilities Certification Office (UCCO), disa.meade.ie.list.unified-capabilities-certification-office@mail.mil. All associated information is available on the DISA UCCO website located at Services/UCCO. 5

6 6. Point of Contact (POC). JITC POC: Ms. Kathleen Kendall; commercial telephone (520) DSN telephone FAX DSN ; address mailing address Joint Interoperability Test Command, ATTN: JTE (Ms. Kathleen Kendall), P.O. Box 12798, Fort Huachuca, AZ The UCCO tracking number for the is FOR THE COMMANDER: Enclosure a/s for RIC HARRISON Chief Networks/Communications and UC Division Distribution (electronic mail): DoD CIO Joint Staff J-6, JCS USD (AT&L) ISG Secretariat, DISA, JTA U.S. Strategic Command, J665 US Navy, OPNAV N2/N6FP12 US Army, DA-OSA, CIO/G-6 ASA (ALT), SAIS-IOQ US Air Force, A3CNN/A6CNN US Marine Corps, MARCORSYSCOM, SIAT, A&CE Division US Coast Guard, CG-64 DISA/TEMC DIA, Office of the Acquisition Executive NSG Interoperability Assessment Team DOT&E, Netcentric Systems and Naval Warfare Medical Health Systems, JMIS IV&V HQUSAISEC, AMSEL-IE-IS UCCO 6

7 ADDITIONAL REFERENCES (c) Joint Interoperability Test Command, Memo, JTE, Joint Interoperability Certification of the TEO Technologies 78XX, 4104, and 4101 with Software Release xx.04.13, 7 November 2013 (d) Joint Interoperability Test Command, Session Controller (SC) Test Procedures for Unified Capabilities Requirements (UCR) 2013, Draft (e) Joint Interoperability Test Command, Cybersecurity Assessment Report (CAR) For TEO Internet Protocol (IP) Telephones 78xx, 4104, 4101, Release xx (Tracking Number ), November 2016 (f) Office of the Department of Defense Chief Information Officer, Department of Defense Unified Capabilities Requirements 2013, Errata 1, 1 July 2013 Enclosure