JITC is short for Joint Interoperability Test Command, which is the Department of Defense's joint interoperability compliance test agency for information technology. The JITC process uses risk-based Test Evaluation & Certification services, tools, and environments to ensure Joint Warfighting IT capabilities are interoperable and support mission needs. Where it deems appropriate, JITC issues certifications and recommends the inclusion of products, services and tools on the Approved Products List (APL). Products, services and tools on the APL, when deployed according to JITC evaluation criteria, help ensure that all capabilities are interoperable to support mission needs.Download Case Study
Ribbon's JITC Compliance Products - Local Session Controller and Enterprise Session Controller
In 2016, the Ribbon Application Server 11.2 (EXPERiUS) was successfully tested as a Local Session Controller (LSC) and added to Approved Products List (APL) by the US Department of Defense Joint Interoperability Test Command (JITC). ). In 2017, the Ribbon Application Server 11.2 was additionally tested and granted inclusion on the APL as an Enterprise Session Controller (ESC).
The Ribbon Application Server 11.2 shares it’s heritage with the Nortel AS 5300 and as such has a unique capability to offer a highly scalable, standards-based, upgrade option for AS 5300 R1.0, R2.0 and R3.0 systems deployed by US Department of Defense’s Command and Control operations.
The Ribbon solution is deployed with standards-based SIP and ASSIP endpoints, so there is no proprietary endpoint lock-in. It easily scales to hundreds of thousands of endpoints per node (max of 2 million), making it ideally suited for graphically redundant, private clouds.
The Session Controller (SC) is a software-based call processing product that provides voice and video services to 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 IP-based long-haul network or via gateways to non-IP networks. DoD UCR 2013 Section 2 2-73 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. – Source: Unified Capabilities Requirements 2013 (UCR 2013)