Bidders Library Interoperability Test and Evaluation - UCR 2013.pdf

i

DoD UCR 2013

Section 1 Changes Table

UCR 2013 Section 1, Introductions, Changes Table

VERSION

REQ-ID

CHANGE

EFFECTIVE

DATE

Errata 1 This section did not have any changes for Errata-1.

Change 1 The term “Enterprise and Network Management System” has been changed to “Element Management System”. This is done to reflect that the required capabilities are those of an EMS even if that may in some cases be performed by network management systems with broader scope.

Immediate

Change 1 The term “Information Assurance (IA)” has been changed to

“cybersecurity” throughout the UCR in Change 1 in accordance with

DoD Instruction (DoDI) 8500.01 (March 14, 2014).

Immediate

Change 1 The description of Section 6 has been reworded for clarity. Immediate

Change 1 A note has been added in Section 1.6 regarding how ANSI Standards are numbered and referenced.

Immediate

Change 1 A note has been added in Section 1.7 regarding Section 4 requirements.

Immediate

Change 2 Section 1.1 – updated pointers from Errata 1 to Change 1 Immediate

DoD UCR 2013 Change 2

Section 1 Table of Contents ii

TABLE OF CONTENTS

SECTION PAGE

Section 1 Introduction .................................................................................................................. 1-1

1.1 Purpose ....................................................................................................................... 1-1

1.2 Applicability ............................................................................................................... 1-1

1.3 UC Definition ............................................................................................................. 1-2

1.4 Scope of Document .................................................................................................... 1-2

1.5 UCR 2013 Document Suite ........................................................................................ 1-3

1.6 Applicable Standards.................................................................................................. 1-4

1.7 General Requirement Language ................................................................................. 1-4

1.7.1 Product Applicability .................................................................................... 1-5

1.8 Definitions .................................................................................................................. 1-5

Section 1 List of Figures iii

LIST OF FIGURES

FIGURE PAGE

Figure 1.5-1. UCR 2013 Document Suite ............................................................................. 1-4

Section 1

1-1

SECTION 1

INTRODUCTION

1.1 PURPOSE

The Department of Defense (DoD) Unified Capabilities Requirements (UCR) 2013 specifies the technical requirements for certification of approved commercial products to be used in DoD networks to provide end-to-end Unified Capabilities (UC), so that all components of the network are connected and working together.

This document supersedes UCR 2013 Change 1.

The UCR specifies the functional requirements, performance objectives, and technical specifications for DoD networks that support UC, and shall be used to support test, certification, acquisition, connection, and operation of these devices. It may also be used for UC product assessments and/or operational tests for emerging UC technology. The Defense Information

Systems Agency (DISA) translates DoD Component functional requirements into engineering specifications for inclusion into the UCR that identify the minimum requirements and features for UC applicable to the overall DoD community. The UCR also defines interoperability, cybersecurity, and interface requirements among products that provide UC. It provides a common language and reference for DoD Components’ implementation of UC technology, supports implementation of DoD Component solutions, and directs adherence to common standards and specifications to support the Department’s Joint Information Environment goal of establishing effective, secure, and common UC.

The UCR is based on commercial off-the-shelf (COTS) products’ features, standards listed in the

DoD Information Technology Standards Registry (DISR), and unique requirements needed to support DoD mission-critical needs.

1.2 APPLICABILITY

Per DoD Instruction (DoDI) 8100.04, the UCR applies to the following:

1. The Office of the Secretary of Defense (OSD), the Military Departments (MILDEPs), the

Office of the Chairman of the Joint Chiefs of Staff (CJCS) and the Joint Staff (JS), the

Combatant Commands (COCOMs), the Office of the Inspector General of the DoD, the

Defense Agencies, the DoD Field Activities, and all other organizational entities within the

DoD (hereafter referred to collectively as the “DoD Components”).

2. DoD Component planning, investment, development, acquisition, operations, and management of DoD networks to support UC, independent of the mix of technologies

(e.g., circuit-switched and/or Internet Protocol [IP]), and whether converged or non-converged, including all equipment or software (hereafter referred to as “UC products” or

1-2

“products”) and services that provide or support UC, during each phase of those products’ life cycles, from acquisition to operations.

3. Acquisition of services is described in DoD Directive (DoDD) 5000.01 and DoDI 5000.02.

1.3 UC DEFINITION

Unified Capabilities are the integration of voice, video, and/or data services delivered ubiquitously across a secure and highly available network infrastructure, independent of technology, to provide increased mission effectiveness to the warfighter and business communities.

1.4 SCOPE OF DOCUMENT

The UCR consists of the following 15 sections and three appendices:

Section 1, Introduction, addresses the purpose, applicability, and overview of the UCR.

Section 2, Session Control Products, addresses UC products that perform Session Control functions for Defense Information Systems Network (DISN) Voice over IP (VoIP) and Video over IP services.

Section 3, Auxiliary Services, addresses the required functionality, performance, capabilities, and associated technical parameters for Auxiliary Services and Systems.

Section 4, Cybersecurity, defines the interoperability focused cubersecurity requirements for UC products.

Section 5, IPv6, describes the IPv6 requirements for Sensitive but Unclassified (SBU) UC subsets provided by all products and technologies used to send and receive or to support voice, video, or data across DoD networks that provide UC services.

Section 6, Network Infrastructure End-to-End (E2E) Performance, focuses on the wide area network (WAN) performance characteristics for Layer 3 routers and switches used in the

E2E UC network infrastructure. It defines the Differentiated Services Code Point (DSCP)

Plan, Per-Hop Behavior (PHB) policy and priority as applied to packets based on the granular service class when traversing a DISN network hop, and traffic conditioning treatment requirements for packet queues to support network traffic shaping.

Section 7, Network Edge Infrastructure, defines technical requirements for the products used in configuring the network edge infrastructure.

Section 8, Multifunction Mobile Devices, addresses the requirements for an array of mobile devices and their associated supporting infrastructure elements. These devices provide network access through primarily wireless means, though wired connectivity may also be a feature of these products. A Multifunction Mobile Device (MMD) can assume any number of form factors including, but not limited to, a smartphone, Personal Digital Assistant (PDA), or small form factor wireless tablet.

1-3

Section 9,Video Distribution System, defines requirements for a complement of audio and video equipment designed for interfacing, switching/bridging, and distributing digital and/or analog audio and video signals sourced from multiple devices and destined to multiple devices.

Section 10, Network Infrastructure Products, defines requirements for products used in the

DISN backbone network infrastructure.

Section 11, Network Elements, defines requirements that must be met by DISN Fixed network element (F-NE) and Deployed network element (D-NE) devices.

Section 12, Generic Security Devices, defines high-level requirements for encryption products.

Section 13, Security Devices, defines requirements for security devices including firewalls, Intrusion Protection Systems (IPSs), Network Access Control, and Virtual Private Network

(VPN) devices.

Section 14, Online Storage Controller, defines requirements for Data Storage Controller

(DSC) systems.

Section 15, Element Management Systems, defines general requirements for element management systems and other network management systems performing EMS functionality.

Section 16, Core Session Controller, combines the role of Enterprise Session Controllers

(ESCs) and Soft Switches. Requirements for this category will be added in a future version of the UCR.

Appendix A, Unique Deployed (Tactical), contains requirements unique to tactical

(deployed) systems.

Appendix B, Unique Classified Unified Capability, contains requirements unique to

Classified systems.

Appendix C, Glossary of Abbreviations and Acronyms, contains the acronyms applicable to the UCR.

1.5 UCR 2013 DOCUMENT SUITE

This specification is one of several DoD documents that specify requirements for Assured

Services networks and requirements for products to achieve DoD UC Approved Products List

(APL) certification. The UC requirements documents that are included in the UCR scope are shown in Figure 1.5-1 and include the following.

UCR 2013: specifies the functional requirements, performance objectives and technical specifications.

Assured Services – Session Initiation Protocol (AS-SIP) 2013: contains the requirements for the IP-based UC Signaling system.

UC XMPP 2013: contains the requirements for multivendor interoperability as required to exploit the full potential of Instant Messaging (IM), Chat, and Presence across DoD.

1-4

UC Framework 2013: specifies the descriptive text and design associated with each of the

UCR 2013 sections.

The reference documents used are cited in UC Framework 2013, Appendix C, Definitions, Abbreviations and Acronyms, and References.

Figure 1.5-1. UCR 2013 Document Suite

1.6 APPLICABLE STANDARDS

The standards used in this section are provided in UC Framework 2013, Appendix C, Definitions, Abbreviations and Acronyms, and References. Note that the Alliance for

Telecommunications Industry Solutions (ATIS) has renumbered the Committee T1 family of documents. ATIS also updates the date on docments at reaffirmation, despite no change to the content. The UCR has not updated to the new number format and date. A new number, such as

ATIS-1000105, April 2015, will appear in its traditional format as T1.105-2001.

1.7 GENERAL REQUIREMENT LANGUAGE

The words “REQUIRED,” “MUST,” or “SHALL” mean that the definition is an absolute requirement of the product.

The word “CONDITIONAL” means a requirement is dependent on a condition. The text of a

CONDITIONAL requirement may use the “If <condition>, then <requirement>” format. An example of a CONDITIONAL requirement is “If the system provides authentication via the SIP digest method, then the SIP digest implementation shall be in accordance with RFC 3261.”

The phrases “MUST NOT” or “SHALL NOT” mean that the definition is an absolute prohibition of the item.

1-5

The word “RECOMMENDED” means that the reference is given as guidance and is not required to be tested. (This word is applicable to the AS-SIP and XMPP protocol requirements only.)

The word “OPTIONAL” means that the item or feature may or may not be used by a product when installed in the field. Optional requirements are features and capabilities that are not considered critical for DoD mission support based on DoD policies. Nevertheless, it is recognized that such features do have utility for some users or for specific operations. To ensure interoperability and consistency of the Assured Services across all platforms, these features and capabilities are specified with set parameters. If these features and capabilities are provided, then the UC product shall perform and meet the requirements as identified in the UCR.

The term “Information Assurance (IA)” has been changed to “cybersecurity” throughout the

UCR in Change 1 in accordance with DoD Instruction (DoDI) 8500.01 (March 14, 2014).

Requirements in Section 4 are cybersecurity requirements that should not be tested during interoperability testing. These requirements are the responsibility of cybersecurity assessment.

1.7.1 Product Applicability

This document identifies the minimum functional and performance requirements for products to be placed on the UC APL.

1.8 DEFINITIONS

Definitions are found in UC Framework 2013, Appendix C, Definitions, Abbreviations and

Acronyms, and References.

Section 2 Changes Table

UCR 2013 Section 2, Session Control Products, Changes Table

Errata 1 SCM-000190 Requirement deleted – redundant to SCM-000210. Immediate

Errata 1 SCM-

000990.a

In Section 2.6.1.1, corrected requirement identifier to SCM-

001180.a

Immediate

Errata 1 SCM-

00180.a

In Section 2.6.1.1, corrected requirement identifier to SCM-

001180.b

Immediate

Errata 1 SCM-001660 Changed “SC” in requirement text to “SS sending the

OPTIONS request.”

Immediate

Errata 1 SCM-001780 Removed PEI and AEI from requirement marking and added new requirement similar to SCM-001780 applicable to PEI and AEI to clarify that 1000-T Mbps Ethernet physical interfaces are not required for PEI and AEI.

Immediate

Errata 1 SCM-001781 New requirement. Please see Change entry for SCM-001780. Immediate

Errata 1 SCM-

001890, SCM-001900

Changed (10/100 Ethernet) to (10/100/1000 Ethernet). Immediate

Errata 1 SCM-

001940-

SCM-001970

Changed [Required: Voice EI] to [Required: PEI, AEI]. Immediate

Errata 1 SCM-001980 Requirement deleted – EI multiple line appearance requirements appear elsewhere in Section 2.1.9.7

Immediate

Errata 1 SCM-002040 Made changes to clarify required vs. optional announcements. Changes include revisions to Table 2.9-3, Required Announcements, a new Conditional requirement applicable to optional announcements, the addition of Table

2.9-4, Optional Announcements, and the deletion of requirement SCM-002050.

Immediate

Errata 1 SCM-002045 New requirement. Please see change entry for SCM-002040. Immediate

Errata 1 SCM-002050 Requirement deleted. See change entry for SCM-002040. Immediate

Errata 1 SCM-002560 Changed requirement for SC to support AS-SIP voice EI from Required to Optional. Changed [SC, SS] to [SC].

Immediate

Errata 1 SCM-002590 Requirement for SC to track and limit number of simultaneous calls at an AS-SIP voice EI deleted, to be consistent with AS-SIP 2013 requirements.

Immediate

Errata 1 SCM-002600 Requirement was deleted. Please see change entry for SCM-

002590.

Immediate

Errata 1 SCM-002610 Changed requirement for SC to support AS-SIP secure voice

EI from Required to Optional. Changed [SC, SS] to [SC].

ii

Errata 1 SCM-002750 Changed requirement for SC to support AS-SIP video EI from

Required to Optional. Changed [SC, SS] to [SC].

Immediate

Errata 1 SCM-002810 Requirement for SC to track and limit number of simultaneous calls at an AS-SIP video EI was deleted, in order to be consistent with AS-SIP 2013 requirements.

Immediate

Errata 1 SCM-003220 through SCM-

003290

Revisions made to introductory text in Section 2.9, End

Instruments, and Section 2.9.10, ROUTINE-Only EIs, to clarify that ROUTINE-only EIs can use either AS-SIP or proprietary signaling.

Immediate

Errata 1 SCM-003230 Requirement deleted. Explanatory note added to SCM-003220 to clarify that an SC that supports ROUTINE-only video EIs is not required to support video EIs that fully support precedence and preemption.

Immediate

Errata 1 SCM-003250 Requirement that a precedence call to a ROUTINE-only EI be immediately diverted by the SC to an attendant has been qualified to apply to calls to ROEIs that use proprietary signaling.

Immediate

Errata 1 SCM-003255 Optional SC requirement added to immediately divert precedence call to a ROUTINE-only EI that uses AS-SIP signaling.

Immediate

Errata 1 SCM-003300 Requirement deleted. Please see change entry for SCM-003220 through SCM-003290, above.

Immediate

Errata 1 SCM-003320 Requirement for SC to support AS-SIP modified to apply for signaling to Softswitches (SS) only.

Immediate

Errata 1 SCM-003325 Optional requirement was added for SC to support AS-SIP signaling to AS-SIP End Instruments.

Immediate

Errata 1 SCM-005320 ESC requirement to support capture of basic call information clarified to reference Section 2.19.2.3, Accounting Management.

Immediate

Errata 1 SCM-008460 In section 2.19.2.3.1, corrected the requirement identifier from

SCM-008460 to SCM-009325.

Immediate

Change 1 SCM-000010 Added AEI to applicability. Immediate

Change 1 SCM-000015 New Requirement to explicitly point out that sessions must remain active until expressly terminated and must not drop due to operational events.

Immediate

Change 1 SCM-000280 Relaxed requirement to allow the preemption tone to be played to

3-way call participants. Added clarify text regarding treatment of the remaining three-way call participants when one participant is preempted by a precedence call.

Immediate

Change 1 SCM-001100 Changed the term NE to product. The intended meaning of the term is equipment/node.

Immediate

Change 1 SCM-001780 Revised to require one or more of 4 Ethernet rates, instead of implying that 3 must be simultaneously supported.

Immediate

Change 1 SCM-001781 Requirement removed, in favor of combining it with SCM-

001780.

Immediate

Change 1 SCM-001782 New requirement [Optional] for auto-negotiation wherever configuration of the signal rate is supported.

Change 1 SCM-001784 Refactored requirement [Conditional] for mandatory auto-negotiation on 100/1000 BASE-T Ethernet interfaces. This is a breakout from previous SCM-001780 and not a new requirement.

Immediate

Change 1 SCM-001830 Broadened the allowed Ethernet rates and physical interfaces. Immediate

Change 1 SCM-002070 Removed MG (Media Gateway) from list of applicable products for this requirement. Requirements regarding MG codec support are found in other sections.

Immediate

Change 1 SCM-002080 Removed MG from list of applicable products for this requirement. Requirements regarding MG codec support are found in other sections.

Immediate

Change 1 SCM-002090 Removed MG from list of applicable products for this requirement. Requirements regarding MG codec support are found in other sections.

Immediate

Change 1 SCM-002100 Removed MG from list of applicable products for this requirement. Requirements regarding MG codec support are found in other sections.

Immediate

Change 1 SCM-

002180.f

Deleted Optional requirement for SC and SS support of analog modems connecting via analog TAs, IADs, and MG line cards.

Immediate

Change 1 SCM-002380 Corrected G.722 clock rate to "16000" samples per second. Immediate

Change 1 SCM-002390 Requirement for Video End Instrument support for H.263-2000 codec revised to say H.263 (i.e., any H.263 version).

Immediate

Change 1 SCM-002395 Created to carry the optional codecs that were part of SCM-

002390.

Immediate

Change 1 SCM-002420 Marked this requirement Conditional on supporting H.323. Immediate

Change 1 SCM-002440 Requirement regarding H.323 VTC and ISDN BRI deleted. Immediate

Change 1 SCM-002450 Requirement regarding VTC systems serial interfaces deleted. Immediate

Change 1 SCM-002460 Marked this requirement Conditional on supporting H.323. Immediate

Change 1 SCM-002462 New Requirement for H.323 Gatekeeper. Immediate

Change 1 SCM-002560 Requirement for SC to support AS-SIP voice EI remains Optional. Immediate

Change 1 SCM-002610 Requirement for SC to support AS-SIP secure voice EI remains

Optional.

Immediate

Change 1 SCM-002750 Requirement for SC to support AS-SIP video EI remains Optional. Immediate

Change 1 SCM-003180 Made optional for PEI and AEI. Immediate

Change 1 SCM-003250 Modified to allow an SC or ring an ROEI with a precedence call as long as it is diverted to an attendant after a preset interval.

Immediate

Change 1 SCM-003255 Removed. PEI and AEI treated the same no in SCM-003250 above.

Immediate

Change 1 SCM-003320 Requirement for SC to support AS-SIP signaling to AS-SIP End

Instruments remains Optional.

Immediate

Change 1 SCM-003325 Requirement for SC to support AS-SIP signaling to AS-SIP End

Instruments remains Optional.

Immediate

Change 1 SCM-004330 ESC Routing Database requirement removed. Immediate

Change 1 SCM-004340 ESC Routing Database requirement removed. Immediate

Change 1 SCM-004395 Added explicit optional requirement for an ESC to support ROEIs

IAW Section 2.9.10.

Change 1 SCM-004390 AEI support made Optional for ESC along with all SCs Immediate

Change 1 SCM-004630 Added G.729/G.729a to Optional audio codec list Immediate

Change 1 SCM-004640 G.722.1, G.723.1, G.728, and G.729/G.729A audio codecs, and

H.263v3 video codec, made optional for ESC video conference systems.

Immediate

Change 1 SCM-004645 New Optional requirement for ESC video conferencing codecs previously required by SCM-004640. G.729/G.729, H.261, H.263v3 and H.264 SVC have been added to this Optional list.

Immediate

Change 1 SCM-004820 Made optional. One of 4 implementation choices. Separated the interface to Outlook, since it is covered in the following requirements.

Immediate

Change 1 SCM-004840 This requirement has been divided into two requirements, SCM-

004840 and SCM-004842 and a third requirement, SCM-004844 has been added. ESCs must support one of the 3 options for conveying voicemail to email, so the last is marked [Required].

Immediate

Change 1 SCM-005020 Deleted “integration with DEE”. An ESC should support DoD directory services. Directory Services should support DEE integration. DEE Integration is not an ESC responsibility.

Immediate

Change 1 SCM-005100 Fixed typo: changed "speech-to-text" to "text-to-speech". Context makes the typo evident, no technical change to the requirement.

Immediate

Change 1 SCM-005120 Requirement for interoperability with Defense Connect Online

(DCO) has been removed now that DCO is discontinued.

Immediate

Change 1 SCM-005160

SCM-

005160.a

SCM-005420

Removed requirements for authentication of EDS Client to EDS

Gateway.

Immediate

Change 1 SCM-005200

SCM-005310

Removed. Immediate

Change 1 SCM-005230 to

SCM-005310

All of the EDS Gateway requirements for ESCs and Video

Conference Bridges were extended, so that they also apply to the standalone “UC EDS Gateway” product type.

Immediate

Change 1 SCM-005311 to

SCM-005318

EDS Gateway requirements for Scalability, Performance, and

Interoperability have been added.

Immediate

Change 1 SCM-007575 Added explicit requirement for MG support of G.711 A-law/μ-law conversion that previously appeared in explanatory text below SCM-002100 in Section 2.9.1.3, Audio Codecs, Voice

Instruments.

Immediate

Change 1 SCM-007580 Added note to clarify that MG support of G.722.1 codec is

Optional.

Immediate

Change 1 SCM-007890 Requirement deleted. Requirements regarding MG codec support are found in Sections 2.16.8.8, 2.16.8.9, 2.16.8.10, and 2.20.1.

Immediate

Change 1 SCM-007900 Requirement deleted. Requirements regarding MG codec support are found in Sections 2.16.8.8, 2.16.8.9, 2.16.8.10, and 2.20.1.

Immediate

Change 1 SCM-008430 Removed – converted to plain text Immediate

Change 1 SCM-008430-

SCM-008430

Explicitly added implied condition to these conditional requirements based on the old SCM-008430.

Change 1 SCM-008500 Corrected references to other sections that appear in this requirement.

Immediate

Change 1 SCM-009070 Explicitly added implied conditions to the conditional requirements a though f where missing.

Immediate

Change 1 SCM-009140 Restored missing text, “Extensible Markup Language (XML)” Immediate

Change 1 SCM-010024 New requirement that specifies a 20ms SPRT transmission interval for V.150.1 modem relay sessions on the trunk side of the MG.

Immediate

Change 1 SCM-010026 New requirement that specifies a 20ms SPRT transmission interval for V.150.1 modem relay sessions for Terminal Adapters (TA), Integrated Access Devices (IAD) and the line side of the MG. This requirement is Conditional on V.150.1 support by those products.

Immediate

Change 1 SCM-010945 New requirement that specifies a 20ms SPRT transmission interval for V.150.1 modem relay sessions for SCIP/V1.150.1 EI.

Immediate

Change 1 SCM-011420 through SCM-

011450

Explicitly added the condition implied by SCM-011410 to each of these conditional requirements.

Immediate

Change 1 SCM-012150

SCM-012160

Implementation of defensive network traffic controls (CANF, CANT) no longer required, but if implemented must still be IAW

GR 477-CORE and Flash/FO precedence attempts must be exempted.

Immediate

Change 1 SCM-012270 Changed to Optional Immediate

Change 1 SCM-013430 Removed obsolete internal reference Immediate

Change 1 The term “Information Assurance” has been changed to

“cybersecurity” in accordance with DoD Instruction 8500.01

(March 2014).

Immediate

Change 2 SCM-001070 Removed requirement as CCS7 is no longer needed/required Immediate

Change 2 SCM-001080 Added the word ‘shall’ to make the requirement more clear Immediate

Change 2 SCM-002390 Removed H.263 from the required codecs (see SCM-

002395)

Immediate

Change 2 SCM-002395 Added H.263 to the optional codecs Immediate

Change 2 SCM-002560 Requirement for SC to support AS-SIP voice EI reinstated to

Required.

Immediate

Change 2 SCM-002610 Requirement for SC to support AS-SIP secure voice EI reinstated to Required.

Immediate

Change 2 SCM-002750 Requirement for SC to support AS-SIP video EI reinstated to

Required.

Immediate

Change 2 SCM-003325 Requirement for SC to support AS-SIP signaling to AS-SIP

End Instruments reinstated to Required.

Immediate

Change 2 SCM-003820 Removed requirement. Requirement is already covered in

SBC section.

Immediate

Change 2 SCM-003850 Removed requirement. Requirement is already covered in

SBC section.

Immediate

Change 2 SCM-004150 Removed requirement. Requirement is already covered in

SBC section.

Immediate

Change 2 SCM-004190 Removed requirement. Requirement is already covered in

SBC section.

Change 2 SCM-004390 Requirement for ESC to support AS-SIP voice EI reinstated to Required.

Immediate

Change 2 SCM-004625 Removed G.722 codec from a required audio codec and moved it to Optional (see SCM-004630)

Immediate

Change 2 SCM-004625 Added G.722 audio codec as an optional requirement Immediate

Change 2 SCM-004640 Removed H.263 from required video codec (See SCM-

004645)

Immediate

Change 2 SCM-004645 Added H.263 as an optional video codec Immediate

Change 2 SCM-005900 Changed ETSI PRI from Required to Conditional. This is only needed if the product wants to be fielded in OCONUS

ETSI compliant countries

Immediate

Change 2 SCM-005910 Changed from Required to conditional (Same comment as

SCM-005900)

Immediate

Change 2 SCM-006010 Changed from Required to conditional (Same comment as

SCM-005900)

Immediate

Change 2 SCM-006230 Removed requirement as SCs should not be required to support proprietary EI. Added proprietary EIs to Optional in

SCM-006240.

Immediate

Change 2 SCM-006240.d Added Proprietary EIs as Optional Immediate

Change 2 SCM-006340 Changed from Required to conditional (Same comment as

SCM-005900)

Immediate

Change 2 SCM-006390 Changed from Required to conditional (Same comment as

SCM-005900)

Immediate

Change 2 SCM-007480 Removed North American 56 Kbps G.711 u-law PCM over digital trunks as this capability is no longer needed in the field

Immediate

Change 2 SCM-007500 Removed requirement as this capability is no longer needed in the field

Immediate

Change 2 SCM-007590 Changed to Optional Immediate

Change 2 SCM-007600 Changed to Optional Immediate

Change 2 SCM-007610 Changed to Optional Immediate

Change 2 SCM-008410 Added the words 'exit the MG' to make the requirement clearer

Immediate

Change 2 SCM-009120 Added verbiage to accommodate the use of Virtual

Machines.

Immediate

Change 2 SCM-009450 Removed requirement as this capability is no longer needed in the field

Immediate

Change 2 SCM-009460 Removed requirement as this capability is no longer needed in the field

Immediate

Change 2 SCM-009470 Removed requirement as this capability is no longer needed in the field

Immediate

Change 2 SCM-009480 Removed requirement as this capability is no longer needed in the field

Immediate

Change 2 SCM-009550.e Removed requirement as this capability is no longer needed in the field

Immediate

Change 2 SCM-012030 Changed requirement to Conditional Immediate

Change 2 SCM-012180 Removed requirement as this capability is no longer needed in the field

Immediate

Change 2 SCM-012190 Removed requirement as this capability is no longer needed in the field

Change 2 SCM-012210 Changed the requirement to only require Method 1 and not both methods for trunk route selection

Immediate

Change 2 SCM-012240 Changed this requirement to Conditional as only Method 1

(SCM-012210) is required)

Immediate

Change 2 SCM-012510 Changed this requirement to Conditional Immediate

Change 2 SCM-012260 Modified the requirement to only require the support for a domain of 000000

Immediate

Change 2 SCM-012530 Modified requirement to specify a default domain of 00 00

00.

Immediate

Change 2 SCM-012535 Created an optional requirement to support a setable domain in the range of 00 00 00 - FF FF FF.

Immediate

Change 2 SCM-012560 Changed to Conditional Immediate

Change 2 SCM-012680 Removed this requirement this capability is no longer needed in the field

Immediate

Change 2 SCM-012710 Changed requirement from Required to Optional Immediate

Change 2 SCM-012870 Changed requirement from Required to Conditional Immediate

Change 2 SCM-012880 Changed requirement from Required to Conditional Immediate

Change 2 SCM-012890 Changed requirement from Required to Conditional Immediate

Change 2 Section 2.27 Added requirements for AS-SIP – EI Interface Gateway Immediate

Change 2 SCM-001840 Removed Optional requirement Immediate

Change 2 Section 2.27.1

Deleted PON as a network management interface requirement from the AS-SIP EI Interface Gateway

Section 2 Table of Contents

TABLE OF CONTENTS

SECTION PAGE

Section 2 Session Control Products .............................................................................................. 2-1

2.1 Introduction ................................................................................................................ 2-1

2.2 Voice Features and Capabilities ................................................................................. 2-1

2.2.1 Call Forwarding ............................................................................................ 2-2

2.2.1.1 Call Forwarding Variable ............................................................. 2-4

2.2.1.2 Call Forwarding Busy Line .......................................................... 2-4

2.2.1.3 Call Forwarding – Don’t Answer – All Calls ............................... 2-5

2.2.1.4 Selective Call Forwarding ............................................................ 2-5

2.2.2 MLPP Interactions With Call Forwarding .................................................... 2-5

2.2.2.1 Call Forwarding at a Busy Station ............................................... 2-5

2.2.2.2 Call Forwarding – No Reply at Called Station ............................. 2-6

2.2.3 Precedence Call Waiting ............................................................................... 2-6

2.2.3.1 Busy With Higher Precedence Call .............................................. 2-6

2.2.3.2 Busy With Equal Precedence Call................................................ 2-6

2.2.3.3 Busy With Lower Precedence Call .............................................. 2-7

2.2.3.4 No Answer ................................................................................... 2-7

2.2.3.5 Line Active With a Lower Precedence Call ................................. 2-7

2.2.3.6 Call Waiting for Single Call Appearance VoIP Phones ............... 2-7

2.2.4 Call Transfer ................................................................................................. 2-7

2.2.4.1 Call Transfer Interaction at Different Precedence Levels ............ 2-7

2.2.4.2 Call Transfer Interaction at Same Precedence Levels .................. 2-8

2.2.5 Call Hold ...................................................................................................... 2-8

2.2.6 Three-Way Calling ....................................................................................... 2-9

2.2.6.1 Three-Way Calling for AEIs and PEIs ....................................... 2-10

2.2.7 Hotline Service ........................................................................................... 2-10

2.2.7.1 Protected Hotline Calling ........................................................... 2-11

2.2.7.2 Hotline Service Protection ......................................................... 2-11

2.2.7.3 Non-Pair Protected Hotline Calling ........................................... 2-13

2.2.7.4 Pair Protected Hotline Calling .................................................... 2-14

2.2.8 Calling Number Delivery ........................................................................... 2-14

2.2.8.1 Calling Name Delivery .............................................................. 2-14

2.2.8.2 Calling Party Organization and Location Delivery .................... 2-14

2.2.9 Call Pick-Up ............................................................................................... 2-14

2.2.10 Precedence Call Diversion .......................................................................... 2-15

2.2.11 Public Safety Voice Features ...................................................................... 2-16

2.2.11.1 Basic Emergency Service (911) ................................................. 2-16

2.2.11.2 Tracing of Terminating Calls ..................................................... 2-17

2.2.11.3 Outgoing Call Tracing ................................................................ 2-17

2.2.11.4 Tracing of a Call in Progress ...................................................... 2-18

2.2.11.5 Tandem Call Trace ..................................................................... 2-18

2.3 ASAC ....................................................................................................................... 2-18

2.3.1 ASAC Requirements Related to Voice ....................................................... 2-19

2.3.1.1 Voice Session Budget Unit ........................................................ 2-19

2.3.1.2 ASAC States .............................................................................. 2-19

2.3.1.3 Session Control Processing With No Directionalization ............ 2-20

2.3.1.4 SC Session Control Processing With Directionalization ............ 2-24

2.3.2 ASAC Requirements for the SS Related to Voice ...................................... 2-25

2.3.2.1 Voice Session Budget Unit ........................................................ 2-25

2.3.3 ASAC Requirements for the SC and the SS Related to Video Services ..... 2-26

2.4 Signaling Protocols .................................................................................................. 2-27

2.4.1 Signaling Performance Guidelines ............................................................. 2-28

2.5 Registration and Authentication ............................................................................... 2-28

2.6 SC and SS Failover and Recovery ........................................................................... 2-29

2.6.1 SC Failover: Alternative A: The SC-Generated OPTIONS Method .......... 2-29

2.6.1.1 SC-Generated OPTIONS ........................................................... 2-29

2.6.1.2 SC OPTIONS-based Failover .................................................... 2-30

2.6.1.3 SC-based Failback ...................................................................... 2-31

2.6.1.4 Failure Handling for Outbound Dialog-initiating INVITE ........ 2-32

2.6.2 SC Failover: Alternative B: The SBC-Generated OPTIONS Method ........ 2-33

2.6.2.1 SBC-Generated OPTIONS ......................................................... 2-33

2.6.2.2 SBC-based Failover ................................................................... 2-34

2.6.2.3 SBC-based Fail Back ................................................................. 2-35

2.6.2.4 Failure Handling for Outbound Dialog-initiating INVITE ........ 2-37

2.6.3 SS Failover ................................................................................................. 2-38

2.6.3.1 OPTIONS-based SS failover and failback of paired SS ............. 2-38

2.6.3.2 OPTIONS-based SS Failover and Failback of another SS

(that is NOT its paired SS) ......................................................... 2-39

2.6.3.3 Failure Handling for Dialog-initiating INVITEs ........................ 2-40

2.7 Product Interface ...................................................................................................... 2-40

2.7.1 Internal Interface ......................................................................................... 2-40

2.7.2 External Physical Interfaces Between Network Components ..................... 2-41

2.7.3 Interfaces to Other Networks ...................................................................... 2-41

2.7.3.1 Deployable Networks Interface .................................................. 2-42

2.7.3.2 DISN Teleport Site Interface ...................................................... 2-42

2.7.3.3 PSTN Interface ........................................................................... 2-42

2.7.3.4 Allied and Coalition Network Interface ..................................... 2-42

2.7.4 DISA VVoIP EMS Interface ...................................................................... 2-42

2.8 Product Physical, Quality, and Environmental Factors ............................................ 2-43

2.8.1 Physical Characteristics .............................................................................. 2-43

2.8.2 Product Quality Factors .............................................................................. 2-43

2.8.2.1 Product Availability ................................................................... 2-43

2.8.2.2 Maximum Downtimes ................................................................ 2-46

2.8.3 Environmental Conditions .......................................................................... 2-46

2.8.4 Voice Service Quality ................................................................................. 2-47

2.9 End Instruments ....................................................................................................... 2-47

2.9.1 IP Voice End Instruments ........................................................................... 2-47

2.9.1.1 Basic ........................................................................................... 2-47

2.9.1.2 Tones and Announcements ........................................................ 2-48

2.9.1.3 Audio Codecs, Voice Instruments .............................................. 2-52

2.9.1.4 VoIP PEI or AEI Telephone Audio Performance ...................... 2-52

2.9.1.5 Voice over IP Sampling Standard .............................................. 2-52

2.9.1.6 Softphones .................................................................................. 2-53

2.9.1.7 DSCP Packet Marking ............................................................... 2-53

2.9.2 Analog and ISDN BRI Telephone Support ................................................ 2-54

2.9.2.1 ISDN BRI Telephone Support ................................................... 2-55

2.9.3 Video End Instrument ................................................................................. 2-56

2.9.3.1 Basic ........................................................................................... 2-56

2.9.3.2 Display Messages, Tones, and Announcements ......................... 2-57

2.9.3.3 Video Codecs (Including Associated Audio Codecs) ................ 2-57

2.9.3.4 H.323 Video Teleconferencing .................................................. 2-58

2.9.4 Authentication to SC .................................................................................. 2-59

2.9.5 End Instrument to ASLAN Interface .......................................................... 2-59

2.9.6 Operational Framework for AEIs ............................................................... 2-59

2.9.6.1 Requirements for Supporting AS-SIP EIs .................................. 2-60

2.9.6.2 Requirements for AS-SIP Voice EIs .......................................... 2-61

2.9.6.3 Requirements for AS-SIP Secure Voice EIs .............................. 2-62

2.9.6.4 Requirements for AS-SIP Video EIs .......................................... 2-64

2.9.6.5 AS-SIP Video EI Features.......................................................... 2-66

2.9.7 Multiple Call Appearance Requirements for AS-SIP EIs ........................... 2-68

2.9.7.1 Multiple Call Appearance Scenarios .......................................... 2-68

2.9.7.2 Multiple Call Appearances – Specific Requirements ................. 2-69

2.9.7.3 Multiple Call Appearances – Interactions With Precedence

Calls ........................................................................................... 2-70

2.9.8 PEIs, AEIs, TAs, and IADs Using the V.150.1 Protocol ............................ 2-72

2.9.9 UC Products With Non-Assured Services Features .................................... 2-73

2.9.10 ROUTINE-Only EIs ................................................................................... 2-73

2.10 Session Controller .................................................................................................... 2-74

2.10.1 PBAS/ASAC .............................................................................................. 2-74

2.10.2 SC Signaling ............................................................................................... 2-74

2.10.3 Session Controller Location Service ........................................................... 2-75

2.10.4 SC Management Function .......................................................................... 2-75

2.10.5 SC-to-VVoIP EMS Interface ...................................................................... 2-75

2.10.6 SC Transport Interface Functions ............................................................... 2-75

2.10.7 Custom Line-Side Features Interference..................................................... 2-76

2.10.8 Loop Avoidance for SCs ............................................................................ 2-76

2.10.9 Local Session Controller Application ......................................................... 2-77

2.10.9.1 Service Requirements Under Total Loss of WAN Transport

Connectivity ............................................................................... 2-77

2.11 AS-SIP Gateways ..................................................................................................... 2-78

2.11.1 AS-SIP TDM Gateway ............................................................................... 2-78

2.11.1.1 AS-SIP TDM Gateway Signaling .............................................. 2-79

2.11.1.2 SIP URI and Mapping of Telephone Number ............................ 2-80

2.11.1.3 AS-SIP TDM Gateway Media ................................................... 2-80

2.11.1.4 Cybersecurity ............................................................................. 2-80

2.11.1.5 AS-SIP TDM Gateway Management Function .......................... 2-80

2.11.1.6 AS-SIP TDM Gateway-to-EMS Interface .................................. 2-81

2.11.2 AS-SIP IP Gateway .................................................................................... 2-81

2.11.2.1 AS-SIP IP Gateway Call Request Processing ............................ 2-82

2.11.2.2 SS Policing Requirements When Serving an AS-SIP IP

Gateway ..................................................................................... 2-82

2.11.2.3 AS-SIP IP Gateway SCS ............................................................ 2-84

2.11.2.4 AS-SIP IP Gateway Media Interworking ................................... 2-87

2.11.2.5 Cybersecurity ............................................................................. 2-87

2.11.2.6 AS-SIP IP Gateway Management Function ............................... 2-87

2.11.2.7 AS-SIP IP Gateway-to-EMS Interface ....................................... 2-88

2.11.3 AS-SIP – H.323 Gateway ........................................................................... 2-88

2.11.3.1 AS-SIP – H.323 Gateway Call Request Processing ................... 2-89

2.11.3.2 SS Policing Requirements When Serving an AS-SIP –

H.323 Gateway ........................................................................... 2-90

2.11.3.3 AS-SIP – H.323 Gateway SCS .................................................. 2-91

2.11.3.4 AS Precedence Capability Requirements and Resource

Priority Header ........................................................................... 2-92

2.11.3.5 SIP URI and Mapping of Telephone Number ............................ 2-93

2.11.3.6 Session Admission Control ........................................................ 2-93

2.11.3.7 AS-SIP – H.323 Gateway Media Interworking.......................... 2-94

2.11.3.8 Cybersecurity ............................................................................. 2-95

2.11.3.9 AS-SIP – H.323 Gateway Management Function ...................... 2-95

2.11.3.10 AS-SIP – H.323 Gateway-to-EMS Interface ............................. 2-95

2.11.3.11 Product Quality Factors .............................................................. 2-96

2.12 Enterprise UC Services ............................................................................................ 2-96

2.12.1 Introduction ................................................................................................ 2-96

2.12.2 Enterprise Session Controller (ESC) Core Infrastructure ........................... 2-96

2.12.2.1 Enterprise Session Controller (ESC) .......................................... 2-96

2.12.2.2 Centralized Enterprise Hosted UC Services ............................. 2-100

2.12.3 Edge Infrastructure ................................................................................... 2-113

2.12.3.1 End Instruments ....................................................................... 2-113

2.12.3.2 Media Gateway ........................................................................ 2-115

2.12.3.3 COOP ....................................................................................... 2-115

2.12.4 Session Border Controller (SBC) ............................................................. 2-118

2.12.4.1 General SBC Functionality ...................................................... 2-118

2.12.4.2 Enclave-Fronting SBC Functionality ....................................... 2-118

2.12.4.3 ESC-fronting SBC within the ESC Core Infrastructure ........... 2-120

2.13 Network-Level Softswitch ..................................................................................... 2-121

2.13.1 Softswitch Location Server ....................................................................... 2-122

2.13.2 SS Signaling Interfaces ............................................................................. 2-123

2.13.3 Network Management System Interface ................................................... 2-123

2.14 Call Connection Agent ........................................................................................... 2-123

2.14.1 Introduction .............................................................................................. 2-123

2.14.2 Functional ................................................................................................. 2-124

2.14.2.1 CCA IWF Component.............................................................. 2-124

2.14.2.2 CCA MGC Component ............................................................ 2-125

2.14.3 Role of the CCA in Network Appliances ................................................. 2-125

2.14.4 CCA-IWF Signaling Protocol Support ..................................................... 2-126

2.14.4.1 CCA-IWF Support for AS-SIP ................................................ 2-126

2.14.4.2 CCA-IWF Support for PRI, via MG ........................................ 2-126

2.14.4.3 CCA-IWF Support for CAS Trunks, via MG .......................... 2-129

2.14.4.4 CCA-IWF Support for PEI and AEI Signaling Protocols ........ 2-133

2.14.4.5 CCA-IWF Support for VoIP and TDM Protocol

Interworking ............................................................................. 2-134

2.15 CCA Interaction With Network Appliances and Functions ................................... 2-136

2.15.1 CCA Interactions With Transport Interface Functions ............................. 2-136

2.15.2 CCA Interactions With the SBC ............................................................... 2-137

2.15.3 CCA Support for Admission Control ....................................................... 2-138

2.15.4 CCA Support for User Features and Services........................................... 2-138

2.15.5 CCA Support for Cybersecurity ............................................................... 2-139

2.15.6 CCA Interactions With Session Controller Location Service ................... 2-140

2.15.7 CCA Interactions With Softswitch Location Service ............................... 2-140

2.15.8 CCA Interactions With End Instrument(s) ............................................... 2-140

2.15.9 CCA Support for Assured Services Voice and Video .............................. 2-141

2.15.10 CCA Interactions With Service Control Functions ................................... 2-142

2.16 Media Gateway ...................................................................................................... 2-143

2.16.1 MG Call Denial Treatments to Support CAC ........................................... 2-143

2.16.1.1 MG Call Preemption Treatments to Support ASAC ................ 2-144

2.16.1.2 MG and Cybersecurity Functions ............................................ 2-144

2.16.1.3 MG Interaction With Service Control Functions ..................... 2-145

2.16.1.4 Interactions With IP Transport Interface Functions ................. 2-146

2.16.1.5 MG–SBC Interaction ...........