M6785423R4907_Attch 7_NCI Regional UC Voice Svcs Arch CONOPS_17MAY2021.pdf

UNCLASSIFIED

DRAFT: D400.12663.04.RUC_VS – May 2021 i

UNCLASSIFIED

Regional Unified Capabilities (R-UC)

Voice Services Solution

Architecture and Concept of Operations

USMC Release:

D400.12663.04.MCEN_RUC-VS

Version 1.1

17 May 2021

Marine Corps Systems Command

Network Communications Infrastructure

United States Marine Corps Portfolio Manager

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense (DoD) and U.S.

20 August 2020. Other requests shall be referred to Portfolio Manager, Network and Infrastructure, Marine Corps

Systems Command (MCSC), 2200 Lester Street, Quantico, VA 22134-6050.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act

(Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive (DoDD) 5230.25.

DESTRUCTION NOTICE: For Unclassified destroy by any method that will prevent disclosure of contents or reconstruction of the document.

ISTC Unified Capabilities Architecture and CONOPS

DRAFT: N65236-USMC-BTI-SEP-0001 V4.00 – 24 June 2019 ii

Unclassified / For Official Use Only

Program Executive Office Digital & Enterprise Services (PEO Digital)

Infrastructure Services, Transport and Communications (ISTC)

Marine Corps

Regional Unified Capabilities, Voice Services Solution –

Architecture and Concept of Operations (CONOPS)

Approved By:

Andrew Mittura

USMC APM-E

Infrastructure Services, Transport & Communications

PEO Digital Enterprise Services

Regional UC – Voice Services Solution Architecture and CONOPS

DRAFT: D400.12663.04.RUC_VS – May 2021 ii

Change History

The Change History identifies all changes incorporated into the updated version of this document after initial approval. The Regional Unified Capabilities (UC) – Voice Services (VS) Solution

Architecture and Concept of Operations (CONOPS) document is a configuration item and will be managed in accordance with the Network Communications Infrastructure (NCI)

Configuration Management Plan (CMP). Updates to this document that are related to any significant changes in the project will go through the Configuration Management (CM) process for approval.

The following table contains a record of changes made to this document. The NCI Lead Systems

Engineer (LSE) and supporting personnel are responsible for providing additional updates between versions to include risk status updates, new reviews accomplished, schedule updates, and any other activities as they are completed. The approval process is the same for all version updates.

Change History Log

Date

Published /

Revised

Version

No.

Author

Section / Description of Change

20 Aug 2020 1.0 Andy Mittura Initial Release

17 May 2021 1.1 Andy Mittura Updated per the EPR feedback

Refer questions concerning this Regional Unified Capabilities (UC) – VS Solution Architecture and CONOPS document to Andy Mittura, NCI Engineering Lead, 170.4 NCI, Marine Corps

System Command, 2200 Lester Street, Quantico, VA 22134-6050, commercial 703-784-4935, andrew.mittura@usmc.mil

Document Properties

Responsible Organization: Marine Corps Systems Command (MCSC) Solution Architect: Various (Site Contractors)

Cyber Lead: Jeffrey Miller, PEO-D, MCSES

Engineering Lead: Andy Mittura, PEO-D, MCSES

Operational Engineering Lead: Michael Caruso, MCCOG

Project Number: N/A (various site projects) mailto:andrew.mittura@usmc.mil

DRAFT: D400.12663.04.RUC_VS – May 2021 iii

Contents

1 Introduction

1.1 Purpose and Solution Overview

1.2 Background

1.3 Audience

1.4 Solution Goals and Objectives

1.5 Threats

1.5.1 Human Unintentional Threats

1.5.2 Human Intentional Threats

2 Capabilities and Requirements

2.1 Key Performance Parameters (KPP)

2.1.1 Regional Unified Capabilities

2.2 Key System Attributes

2.3 Major Functional Requirements

3 Architecture Context

3.1 Regional Construct

3.2 Relationship to Other Program Documentation

3.3 Operational Context

3.3.1 Business Voice

3.3.2 Voice Conferencing

3.3.3 Commercial Voice Access

3.3.4 Voice Mail

3.3.5 Unified Messaging

3.4 Exclusions

4 Solution Description

4.1 Solution Context

4.1.1 Tier A – Regional Hub Site

4.1.2 Tier B – Regional ISN Site

4.1.3 Tier C – Regional GSU Site

4.2 Voice Network

4.3 Components

4.4 Use Cases / Modes of Operation

4.4.1 Local On-Base Call

4.4.2 Base-to-Base Call

4.4.3 Commercial Call

4.4.4 E911 Calls

4.5 Adherence to Industry Standards and Best Practices

4.6 Architecture Implementation

4.7 Architecture Guidance

4.8 Continuing Governance

5 Solution Support

5.1 Roles and Responsibilities

DRAFT: D400.12663.04.RUC_VS – May 2021 iv

5.2 Training Requirements

5.3 Personnel Requirements

5.4 Non-Labor Resource Requirements

Appendix A: Acronyms and Abbreviations

Figures Figure 1. (FOUO) Site Capabilities

Figure 2. (FOUO) UC Regions and Associated Sites

Figure 3. (FOUO) Defined Regions and Installation Capabilities

Figure 4. (FOUO) Voice Data Flow

Figure 5. (FOUO) Reference Architecture – Tier A Site

Figure 6. (FOUO) Reference Architecture – Tier B Site

Figure 7. (FOUO) Reference Architecture – Tier C Site

Tables Table 1(FOUO) Traffic Conditioning Specification

Table 2 (FOUO) UC Architecture Components

Table 3 (FOUO) Roles and Responsibilities

Table 4 (FOUO) UC Architecture Training Requirements

Table 5 (FOUO) Appendix A: Acronyms and Abbreviations

DRAFT: D400.12663.04.RUC_VS – May 2021 1

1 Introduction

This document describes the architecture of the Regional Unified Capabilities (UC) of Voice

Services (VS) in the Marine Corps Network Communications Infrastructure (NCI) program.

1.1 Purpose and Solution Overview

(FOUO) The objective of this document is to define requirements and architecture for the provision of voice services at the regional enterprise. The Marine Corps NCI voice services are a regional design that aligns to the Wide Area Network (WAN) Transport Implementation Plan.

Voice Services include:

Business Voice

Voice Conferencing

Commercial Voice Access

Voicemail

Unified Messaging

Precedence-Based Voice.

The UC solution includes:

Session Border Controllers (SBCs)

Local Session Controllers (LSCs)

Media Gateways

Teleconferencing bridges

Voice mail

Telecommunications Management System (TMS).

1.2 Background

(FOUO) This architecture will replace existing non-Internet Protocol (IP) Private Branch

Exchanges (PBXs) used to provide telephone service at Base/Post/Camp/Stations (B/P/C/S).

Existing non-IP PBXs are beyond End-of-Life (EoL) and are nearing (or in some cases beyond)

End-of-Support (EoS). Additionally, it will replace/upgrade existing LSCs that have been installed in a stand-alone manner.

1.3 Audience

This document is intended as an architecture document for network architects and engineers.

It also has value for non-technical administrators and other senior staff.

DRAFT: D400.12663.04.RUC_VS – May 2021 2

1.4 Solution Goals and Objectives

(FOUO) This solution architecture is constructed to achieve the following goals with supporting objectives:

Enhance operational effectiveness

Enable continuity of operations, high availability and failover

Fully leverage enterprise services for telephony

Empower individual users to schedule and execute voice and video conferences directly, and give them the tools to effectively manage conferences in progress.

Reduce total cost of ownership of garrison communications systems

Consolidate disparate telephone, data, and video networks

Consolidate maintenance staffs and supply chains

Makes use of the voice Internet Services Provider (ISP) service provided by the

Defense Information Systems Agency (DISA)

Reduce work load on existing installations

Eliminates need for installation billing

Eliminates need for costly Integrated Services Digital Network (ISDN) circuits.

Remove EoS vulnerability of existing PBXs.

1.5 Threats

(FOUO) The solution is affected by threats in relation to its location on the network. These threats include denial of service both intentional and unintentional and unauthorized remote access attack.

1.5.1 Human Unintentional Threats

(FOUO) Human unintentional threats tend to be the result of accidents, lack of configuration management, failure to adhere to policy and/or procedural failures. Human unintentional threats for the UC segment include:

Misconfiguration: (FOUO) Improper configuration can cause systems to operate incorrectly or incompletely, or failure. This can in turn lead to communications failure, leading to mission / operations failure.

Lack of Configuration Management (CM): (FOUO) Lack of proper configuration management can lead to misconfiguration with the results described above. It can also lead to creating vulnerabilities that can be exploited by bad actors.

DRAFT: D400.12663.04.RUC_VS – May 2021 3

1.5.2 Human Intentional Threats

(FOUO) Specific human intentional threats for the UC architecture include:

Willful misconfiguration to create “taps” on data flows or to cause theft of services.

Willful extraction of configuration data and transmission to unauthorized users.

Malicious attacks to create Distributed Denial of Service (DDoS), data manipulation, data destruction and Malware.

DRAFT: D400.12663.04.RUC_VS – May 2021 4

2 Capabilities and Requirements

(FOUO) Increasingly, UC systems have evolved into powerful and comprehensive platforms to provide UC services for voice, video, instant messaging, collaboration, etc. They provide communications capabilities for enterprise users virtually anywhere, anytime, and on any platform.

(FOUO) At a high level, the United States Marine Corps (USMC) UC system must support robust UC capabilities and meet relevant requirements of the Department of Defense (DoD)

Unified Capabilities Requirements 2013 (UCR 2013, Change 2). 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.

2.1 Key Performance Parameters (KPP)

(FOUO) This section defines the Key Performance Parameters (KPPs) required to achieve the required UC capabilities delivered by the regional UC system. KPPs are the most essential benchmarks for the UC system to provide robust UC services within USMC installations, and reflect the USMC’s mission and operational requirements that must be met. All KPPs include

Threshold (T) and Objective (O) values that must be able to be validated through testing and/or analysis.

The regional UC system shall meet the following KPPs:

NGEN CPD (Version 1.5.7): Net-Ready KPP (Section 6.1.3)

DoD UCR-2013 (Change 2): Product Availability (Section 2.8.2.1)

2.1.1 Regional Unified Capabilities

(FOUO) A regional UC system shall consist of several installations connected in a cluster. One of the installations, normally the Component Enterprise Data Center (CEDC) or Tier A site, will serve as the main node and host the enterprise equipment. The regional UC system shall provide voice services to each user on each installation within the region. Each installation shall have a

SBC and a LSC to provide self-sustaining capabilities should it become separated from the region. The system shall have a TMS, along with a Voice Mail and Voice Conferencing system that supports the Region. The management, maintenance and operations of the UC system will be primarily performed from the regional site with each site responsible for Moves, Adds, Changes (MAC), and day-to-day operations.

DRAFT: D400.12663.04.RUC_VS – May 2021 5

Figure 1 depicts each Tier’s Site capabilities.

Figure 1. (FOUO) Site Capabilities

2.2 Key System Attributes

(FOUO) This section defines the Key System Attributes (KSAs) required to achieve the required

UC capabilities delivered by the UC system. They are considered essential to achieve a balanced solution/approach for the UC system, but not critical enough to be designated as KPPs.

All KSAs include Threshold and Objective values that must be able to be validated through testing and/or analysis. The regional UC system shall meet the following KSAs:

DoD UCR-2013 (Change 2): Service Class Performance Objective (Section 6.3.1)

The system shall be listed on the UC Approved Product List (APL.)

The system shall be capable of being installed in an incremental fashion one campus at a time.

The system shall provide Business voice, voice conferencing, commercial voice access, voice mail, and unified messaging as defined in the Functional Requirements

Document for Defense Enterprise Office Solutions.

Calls between Marine-to-Marine users shall be made without using the DISA soft switch backbone.

DISA Voice Internet Service Provider (VISP) shall be used as the primary interface for commercial voice access.

Transmitting and receiving (i.e., Direct Inward Dial) of point-to-point voice sessions from commercial voice networks via the VISP shall be provided to each installation.

DRAFT: D400.12663.04.RUC_VS – May 2021 6

Support the Differentiated Services Code Points (DSCP) markings to implement

Quality of Service (QoS)/ Class of Service (CoS).

Provide native audio Mean Opinion Score (MOS) of 3.8, at a minimum.

In accordance with (IAW) the Telecommunications Industry Association (TIA)

Telecommunications – IP Telephony Equipment – Voice Quality Recommendations for IP Telephony (TSB-116-A).

2.3 Major Functional Requirements

(FOUO) A regional UC system shall:

Consist of a LSC at each designated B/P/C/S.

Each LSC shall integrate with the other LSCs in its region in a coordinated cluster that provides full failover capability to other installations.

Each LSC shall provide a media gateway to accommodate the necessary analog services on the installation.

The regional UC shall provide the assignment of both a Defense Switched

Network (DSN) and commercial phone number to each end instrument.

Each LSC shall provide local survivability in the event it is severed from the Defense

Information Systems Network (DISN).

Support local session management when in a disconnected state.

Support local Enhanced 911 (E911) routing to the Public Safety Answering

Point (PSAP) or Emergency Response Center (ERC).

Remote users can utilize softphones through secure Virtual Private Networks (VPNs) from any location.

Automatic Call Distribution (ACD) shall be provided at the region.

Customer Service Support Applications (CSSAs) shall be provided at the region.

CSSAs shall provide call routing via Interactive Voice Recognition (IVR) for management, administration features.

CSSA shall support 400 agents.

CSSAs shall have a built in “heat map” to allow scheduling during peak usage vice time of day.

DRAFT: D400.12663.04.RUC_VS – May 2021 7

3 Architecture Context

(FOUO) The Marine Corps is implementing a network that has the ability to integrate voice, video, and data services delivered ubiquitously across an interoperable, secure, and highly available network infrastructure in accordance with the Joint Information Environment (JIE).

This environment calls for designated B/P/C/S to host core services in a regional construct and subordinate installations to reach into the designated sites for services.

The Unified Communications capabilities shall be designed as a regional enterprise solution.

There are six (6) regions: East, West, Pacific (PAC), Middle Pacific (MID PAC), National

Capital Region (NCR), and Enterprise. Figure 3 shows the sites in each region.

Figure 2. (FOUO) UC Regions and Associated Sites

DRAFT: D400.12663.04.RUC_VS – May 2021 8

Figure 3 displays the defined regions and installation capabilities.

Figure 3. (FOUO) Defined Regions and Installation Capabilities

3.1 Regional Construct

The regional construct applies a regional enterprise in order to minimize equipment and workload. It provides continuity of operations within the region by providing each Tier A and

Tier B installation with an SBC and a LSC to provide individual installations with dial tone and phone service. It consolidates at the Tier A location enterprise services including telecommunication management systems and voice mail.

Emergency call capability is maintained with PSAPs on designated installations and connection to Emergency services where applicable. Analog services are supported to support emergency phones, internal communications systems, alarms, monitoring stations and others.

Figure 4 shows the data flow for the different types of communications. Standard commercial communications and DSN communications utilize the SBC and DISA Voice over Internet

Protocol (VoIP) Virtual Routing and Forwarding (VRF). Additionally, the installation can have a second Local Exchange Carrier (LEC) ordered through Defense Information Technology

Contracting Organization (DITCO) and routed via the SBC. Marine-to-Marine calls between

DRAFT: D400.12663.04.RUC_VS – May 2021 9 installations are router without the SBC and over the closed Layer 3 Virtual Private

Network (L3VPN). Communications to and from a Geographically Separated Units (GSUs) are routed via a L3VPN to its host site.

ESINET

TMS

Server

Voicemail Server

Primary

LSC

Secondary

LSC

CEDC

ISN

GSU

DISA

SBC

DISA

SBC

Remote Survivable

LSC

Voice Conferencing Server

Voice Conferencing Server

Primary

LSC

Secondary

LSC

Marine

Marine to

NG 911

IPSEC

Tunnel

Closed USMC Transport

L3VPN

Closed USMC Traffic L3VPN

Commercial

Exchange

Carriers

VISP

SBC

LEC SIP Trunk

LEC SIP

Trunk

Voice Conferencing

Server

Voice Conferencing

Server

, DSN VISP

Commerical

DISA

USMC-VOIP-VRF

Figure 4. (FOUO) Voice Data Flow

3.2 Relationship to Other Program Documentation

(FOUO) This specification document is the first step in engineering level requirements and provides clarification and specificity to the requirements document. It provides the Concept of

Operations (CONOPS) for the system as it will be deployed or used in production. UC services ride on the transport system for the installations as defined in the Base Area Network (BAN)

DEV 400. The SBC architecture is further defined in the SBC DEV 400.

3.3 Operational Context

(FOUO) The UC solution will be used by installation users to obtain voice services, including voicemail and voice conferencing. Voice services include:

Business voice

Voice Conferencing

Commercial voice access

Voice mail

Unified messaging.

DRAFT: D400.12663.04.RUC_VS – May 2021 10

3.3.1 Business Voice

(FOUO) Non-Command and Control (C2) users who require voice (single-line and multi-line), access to E911, local, and long-distance dialing.

3.3.2 Voice Conferencing

(FOUO) The ability to link together multiple voice sessions in a multi-party conference, using a voice conference bridge or started from a telephony End Instrument (EI). Conferences can be ad hoc or pre-scheduled using persistent phone numbers and unique access codes. Individual point-to-point calls within a voice conference can have C2 features.

3.3.3 Commercial Voice Access

(FOUO) External voice connections for Sensitive but Unclassified (SBU) calls via a centralized, enterprise wide subscription based access point to the public telephone network.

Locally provided Internet Protocol (IP) circuits are by exception only and must comply with applicable DoD policies.

3.3.4 Voice Mail

(FOUO) An electronic communication system in which spoken messages are recorded or digitized and stored for later playback to the intended recipient.

3.3.5 Unified Messaging

(FOUO) The ability to retrieve voice, fax, and email messages that a user can access either with an email client or by telephone. Voice messages can be transcribed into email, and emails can be digitized into voicemail.

3.4 Exclusions

Not applicable.

DRAFT: D400.12663.04.RUC_VS – May 2021 11

4 Solution Description

(FOUO) The UC architecture provides session management for session-based information exchanges. It also provides firewall protection for voice traffic, and interfaces to non-IP transmission systems as required for voice traffic.

4.1 Solution Context

(FOUO) Not every B/P/C/S receives a full suite of hardware. Tier A sites host voicemail, voice conferencing, and a centralized TMS. Tier A and Tier B sites receive SBCs and LSCs.

Since they have direct access to the Joint Base Provider Edge (JB-PE) device, they will have direct DSN access. Tier C sites or GSUs will have a remote survivable unit, which will only provide local communications in the event of a loss of connection to the host installation.

Figures 5, 6, and 7 provide the individual capabilities at each B/P/C/S depending on the designated tier level.

4.1.1 Tier A – Regional Hub Site

(FOUO) UC Regional Hubs (Tier A sites) shall contain the basic system capabilities including but not limited to SBCs, a Session Manager, and Voice Conferencing. This type of site shall host consolidated equipment to support the region by providing a Telecommunications

Management System, Voice Mail, license management, and a subscriber database. Tier A Sites shall provide patch management for region as well as provide regional operations support to

Tier B and C sites. Dual Points of Presence (PoPs) shall provide high availability for all external communications. DSN and Commercial carriers shall be accessible via DISA. There shall be a separate LEC interface for local commercial connections. Emergency Services IP

Network (ESInet) shall interface to support local PSAP for Next Generation 911 (NG911).

Marine-to-Marine communications shall traverse over the L3VPN, which saves on Session

Initiation Protocol (SIP) trunking.

DRAFT: D400.12663.04.RUC_VS – May 2021 12

Figure 5 depicts a UC Architecture for a Regional Hub Site.

MCEN-N

Core

Router

(B)

QFP

DISA

SBC

VoIP

EUDs

MCEN-N

Core

Router

(A)

QFP

MCEN

CORE

SWITCH

(A)

UC Architecture Tier A Site

BAN Core

Router (B)BAN Core

Router (A)

MCEN

CORE

SWITCH

(B)AS-LAN

Primary

SBC

V

TMS

Server

Voicemail Server

Primary

LSC

Secondary

LSC

Voice Conferencing

Server

Voice

Switches

Voice Conferencing

Server

DISA

SBC

ESINET

DISA

JB PE

QFP QFP

DISA

JB PE

BCF

V

Closed USMC Transport

L3VPN

LEC SIP Trunk

SIP

SIP

Commercial

Exchange

Carriers

VISP

SBC DISA

USMC-VoIP-VRF

Figure 5. (FOUO) Reference Architecture – Tier A Site

4.1.2 Tier B – Regional ISN Site

(FOUO) UC Regional ISN (Tier B sites) shall contain the basic system capabilities, including, but not limited to, SBCs, a Session Manager, and Voice Conferencing. This type of site shall maintain access to consolidated equipment to provide the installation support (Moves, Adds, Changes). In addition, Tier B sites shall provide failover capability to Tier A sites. Dual PoPs shall provide high availability for all external communications. DSN and Commercial carriers shall be accessible via DISA. There shall be a separate LEC interface for local commercial connections. ESInet shall interface to support local PSAP for NG911. Marine-to-Marine communications shall traverse over the L3VPN, which saves on SIP trunking. The Tier B sites

DRAFT: D400.12663.04.RUC_VS – May 2021 13 shall leverage enterprise services, including, but not limited to, TMSs and Voice Mail from a regional hub.

Figure 6 depicts a UC Architecture for a Regional ISN Site.

MCEN-N

Core

Router

(B)

QFP

DISA

SBC

VoIP

EUDs

Commercial

Exchange

Carriers

MCEN-N

Core

Router

(A)

QFP

MCEN

CORE

SWITCH

(A)

UC Architecture Tier B Site

BAN Core

Router (B)BAN Core

Router (A)

MCEN

CORE

SWITCH

(B)AS-LAN

Primary

SBC

V

Primary

LSC

Secondary

LSC

Voice Conferencing

Server

Voice

Switches

Centralized Telecom Mgmt

System

DISA

SBC

ESINET

LEC SIP Trunk

SBC

BCF

V

SIP

Commercial

Exchange

Carriers

VISP

SBC

DISA

Figure 6. (FOUO) Reference Architecture – Tier B Site

DRAFT: D400.12663.04.RUC_VS – May 2021 14

4.1.3 Tier C – Regional GSU Site

(FOUO) UC Regional GSUs (Tier C sites) contain local survivable capability to support the enclave in the event it is severed from its host. A Tier 3 site shall have a survivable session controller to provide enclave communications in the event it becomes disconnected. This site shall utilize a L3VPN connection to a Tier A or B site for voice service.

Figure 7. (FOUO) Reference Architecture – Tier C Site

TIER A

Core

Router

QFP

VOIP

EUDs

Commercial

Exchange

Carriers

MCEN-N

Core

Router QFP

MCEN CORE

SWITCH

UC Architecture Tier C Site

Boundary

Router

AS-LAN

V

Remote Survivable

LSC

Voice

Switches

DISA

JB-PE

DISA

JB-PE

V

QFP

QFP QFP

Commercial

DITCO

Lease

IPSEC Tunnel

JIE

JB-CE

Tier A Site

Closed USMC Transport

L3VPN

DRAFT: D400.12663.04.RUC_VS – May 2021 15

4.2 Voice Network

(FOUO) The voice network consists of an Assured Services-Local Area Network (AS-LAN) and the user distribution. The AS-LAN consists of the Local Session Controller, Telecommunications Management System (TMS). The AS-LAN is protected and interfaced to the BAN via a pair of Layer 3 switches executing ACLs. These ACLs allow the LSC and TMS to take advantage of enterprise services to include PKI, AAA, DNS, DHCP, HBSS, NTP and syslog.

(FOUO) The Marine Corps has implemented a private IP scheme for the voice traffic. An allocation of the 10.X.X.X network has been defined for each B/P/C/S. Each region and each installation in that region has been allocated a block of private IPs.

(FOUO) Separate Virtual Local Area Networks (VLANs) are used to segregate voice traffic. In conjunction with the BAN architecture scheme, voice will utilize extended VLANS and indicate zones on each installation associated with the distribution nodes. The tens digit in the extended

VLAN Identification (ID) will indicate the zone.

(FOUO) Extended VLANs in the range of 1200-1399 are reserved for IP Phones.

Voice VLANs 1210-1219 are in Zone 1.

Voice VLANs 1220-1229 are in Zone 2.

Voice VLANs 1370-1379 are in zone 17.

VLANs 1380 – 1397 are reserved for voice servers.

VLANs 1398 and 1399 are reserved for maintenance.

DRAFT: D400.12663.04.RUC_VS – May 2021 16

The USMC VoIP VPN shall implement QoS. The DSCP plan to be used is described in Table 1.

Table 1(FOUO) Traffic Conditioning Specification

AGGREGATED

SERVICE CLASS

GRANULAR SERVICE CLASS

PRIORITY/

PRECEDENCE

DSCP

BASE10

DSCP

BINARY

DSCP

BASE8

Network Control Network Signaling (OSPF, BGP, etc.) N/A 48 110 000 60

User Signaling (AS-SIP or SIP) N/A 40 101 000 50

Short Message FO 32 100 000 40

FO 41 101 001 51

F 43 101 011 53

I 45 101 101 55

P 47 101 111 57

R 49 110 001 61

SIP Voice ** N/A 46 101 110 56

Assured Multimedia FO 33 100 001 41

F 35 100 011 43

I 37 100 101 45

P 39 100 111 47

Broadcast Video N/A 24 011 000 30

FO 25 011 001 31

F 27 011 011 33

I 29 011 101 35

P 31 011 111 37

R 26 011 010 32

FO 17 010 001 21

F 19 010 011 23

I 21 010 101 25

P 23 010 111 27

R 18 [20,22]*** 010 010 22

FO 9 001 001 11

F 11 001 011 13

I 13 001 101 15

P 15 001 111 17

R 10 [12,14]*** 001 010 12

OA&M N/A 16 010 000 20

Best Effort N/A 0 000 000 0

Elastic Low Priority Data N/A 8 001 000 10

** For a definition, see UC Framework 2013, Appendix C, Definitions, Abbreviations and Acronyms, and References.

*** Code points in brackets are reserved for nonconformance marking.

AS-SIP Voice * (Includes SRTCP)Inelastic Real-Time

Conferencing (voice, video, and data)

(code points 28, 30, 34, 36, and 38 are for Non-Assured Multimedia

Conferencing) R 51 [28, 30, 34,36,38]*** 110 011 63

AS-SIP: Assured Services Session Initiation Protocol N/A: Not Applicable

BGP: Border Gateway Protocol OA&M: Operations, Administration, and Maintenance DSCP: Differentiated Services Code

Point OSPF: Open Shortest Path First

F: FLASH P: PRIORITY

FO: FLASH OVERRIDE R: ROUTINE

IM: Instant Messaging SRTCP: Secure Real-Time Transport Control Protocol I: INTERMEDIATE

* Priority precedence applies to AS-SIP only.

LEGEND:

Multimedia Streaming

Preferred Elastic Low-Latency Data: (IM, Chat, Presence)

High Throughput Data (Real-Time Data

Backup, Web Hosting)

DRAFT: D400.12663.04.RUC_VS – May 2021 17

4.3 Components

Error! Reference source not found. lists the components of the UC architecture, describes their function, and indicates where they are used.

Table 2 (FOUO) UC Architecture Components

Item Description Where Used

Local Session

Controller

Hardware and software to set up, tear down, and manage session-based information exchanges, including all switched voice and video calls.

Also addresses data sharing and collaboration activities if they are session-based.

All installations

Session Border

Controller

A network element that exerts control over the signaling and the media streams involved in setting up, conducting, and tearing down calls. The SBC enforces security, quality of service and admission control mechanism over the VoIP sessions.

All Installations

TMS Application

Server that enables Marine Corps telecom maintenance

/ administration personnel to access the TMS databases to update configuration records and create work tickets for moves, adds, changes, and repairs.

CEDC only

TMS Database Server that houses master configuration databases for all telecom assets CEDC only

TMS Management

Server that houses user accounts, permissions, and other information required to operate the TMS as a single entity for all B/P/C/S served by the region in question

CEDC only

Conference Bridge

Hardware and software that manages and provides voice conferences for all B/P/C/S served by the region in question

CEDC only

Voicemail Server that provides voicemail services for all

B/P/C/S served by the region in question CEDC only

Telephony gateways

Media gateways that translate IP-based telephony capabilities into non-IP (e.g., TDM, analog) telephony services. Gateways are used both to connect to analog telephone sets and to non-IP trunk circuits to access

DSN and the PSTN.

All installations

L3 switch

A physical or virtual Layer 3 switching device that connects all UC Architecture components to the

BAN Distribution Routers.

All installations

Administrative workstation

Workstation (e.g., PC) that is used to access the

UC Architecture components for local configuration.

DRAFT: D400.12663.04.RUC_VS – May 2021 18

4.4 Use Cases / Modes of Operation

Error! Reference source not found. lists some significant use cases for the UC Architecture.

This list is by no means exhaustive.

4.4.1 Local On-Base Call

All 7- or 10-digit dialing, call is routed on base.

4.4.2 Base-to-Base Call

(FOUO) All 10-digit dialing, call is routed to destination base without SBC involvement.

If 99 or 991 is dialed, call is routed as shown in Section 4.4.1.

4.4.3 Commercial Call

(FOUO) Calls originating on base shall be 10-digit dialing and be routed to the SBC for transmission to VISP SBC

Calls originating off base shall be routed to the SBC for transmission to the LSC.

4.4.4 E911 Calls

4.4.4.1 Installations with a PSAP

(FOUO) E911 calls originating from an on-base phone shall be routed directly to the PSAP.

Commercial calls shall route to the PSAP via ESInet from the commercial carrier.

4.4.4.2 Installations without a PSAP

(FOUO) E911 calls originating from an on-base phone shall be routed to ESInet via the DSN interface.

4.5 Adherence to Industry Standards and Best Practices

The UC Architecture uses open-standard protocols and Commercial Off-the-Shelf (COTS) products.

4.6 Architecture Implementation

(FOUO) The UC Architecture will be implemented in a phased manner. To the extent possible, Installation Processing Node (IPN) capabilities will be deployed prior to deployment of ISN capabilities. Because the phasing will extend across several years, continued interoperability of

IP and non-IP voice systems must be planned for and designed into the architecture from the beginning. This may, in some cases, result in a greater amount of hardware (e.g., telephony gateways) being deployed than would be required in a greenfield deployment.

4.7 Architecture Guidance

(FOUO) The UC Architecture will be managed by the NCI Program Office.

4.8 Continuing Governance

TBD

DRAFT: D400.12663.04.RUC_VS – May 2021 19

5 Solution Support

5.1 Roles and Responsibilities

Error! Reference source not found. lists the Roles and the Responsibilities for UC

Architecture.

Table 3 (FOUO) Roles and Responsibilities

Legend:

Responsible (R)

Accountable (A)

Support (S)

Consulted (C)

Informed (I)

M C

S C

H Q

M C

C

M F

C C

/M C

C O

G

M

IC

O

D

I

R eg io n al G

F A

Define Technical Requirements AR SC C R C C C

Conduct In-Service Engineering and Update

Solution Design Documentation

AR I S C C

Conduct FCA AR C S S

Conduct Applied Engineering and Create

Site Configuration Design Documentation –

Initial Solution Deployment

AR I S I S C

Conduct Applied Engineering and Update

Site Configuration Design Documentation –

Post Initial Solution Deployment

AR I C C C C

Conduct PCA AR C

Establish and Sustain Development Lab

Equipment (Includes Facility Dependencies)

AR S

Operate (Manage and Administer)

Development Lab

AR S

Establish and Sustain Production Equipment

(Includes Facility Dependencies)

AR C S S

Operate (Manage and Administer)

Production

C C AR

Maintain Type Accreditation R A S

Maintain Site Accreditations S A S R

R = Responsible - Those responsible for the task, who ensure that it is done as per the approver. There is at least one role with a participation type of responsible, although others can be delegated to assist in the work required

(see Support role).

A = Accountable - The one ultimately answerable for the correct and thorough completion of the deliverable or task, and the one who delegates the work to those responsible. In other words, an accountable must sign off (approve) work that responsible provides. There must be only one accountable specified for each task or deliverable.

S = Support - Resources allocated to Responsible. Unlike consulted, who may provide input to the task, support help complete the task.

C = Consulted - Those whose opinions are sought, typically subject matter experts; and with whom there is two-way communication. (Implies I-Informed)

I = Informed - Those who are kept up-to-date on progress, often only on completion of the task or deliverable; and with whom there is just one-way communication. Those who are assigned the “Informed” level of responsibility have no required work to support a task or deliverable, but are kept up-to-date on work progress or notified once the work or deliverable is completed. Typically, communications with those in an “Informed” role are purely one-way from those who are Accountable or Responsible.

DRAFT: D400.12663.04.RUC_VS – May 2021 20

5.2 Training Requirements

Error! Reference source not found. describes the training requirements for the UC

Architecture.

Table 4 (FOUO) UC Architecture Training Requirements

Area Item Users Maint

Personnel

Local

Admin

Enterprise

Admin

Local Session

Controller (LSC) End-user operations X X X X

Local Session

Controller (LSC)

Hardware / software maintenance X

Local Session

Controller (LSC) Administration X X X

Voice Firewalls Configuration X X

Voice Firewalls Maintenance X

ETM Database /

ETM Management Configuration X X X

ETM Database /

ETM Management Maintenance X

TMS Application Local administration X X X

TMS Application Ticket creation / annotation / resolution X X

TMS Application Report generation X X

TMS Application Configuration records X X

TMS Database Database administration X

TMS Database Hardware / software maintenance X

TMS Management Enterprise management X X

TMS Management Hardware / software maintenance X

Conference Bridge End-user operations X X X X

Conference Bridge Account management X X

Conference Bridge Hardware / software maintenance X

Voicemail End-user operations X X X X

Voicemail Account management X X

Voicemail Hardware / software maintenance X

Telephony gateways Configuration X X

DRAFT: D400.12663.04.RUC_VS – May 2021 21

Area Item Users Maint

Personnel

Local

Admin

Enterprise

Admin

Telephony gateways

Hardware / software maintenance X

L3 switch Configuration X X

L3 switch Hardware / software maintenance X

Administrative workstation Configuration X X

Administrative workstation

Hardware / software maintenance X

5.3 Personnel Requirements

(FOUO) The total number of personnel and their types required to maintain the UC Architecture, as well as their job classifications, are to be determined.

5.4 Non-Labor Resource Requirements

(FOUO) The UC Architecture will require at least the following non-labor resources. This is not a complete list:

A complete set of on-site spares at each B/C/P/S, or a regional depot of spares and a way to move them quickly (i.e., within 1 day) from the regional depot to any installation.

Test equipment for analyzing network performance.

Manufacturer’s recommended test assets (to be determined).

Electricity.

Heating, Ventilation, and Air Conditioning (HVAC) that operates independently of building HVAC, or which is otherwise configured to be continuously available.

Suitable space for installation.

Systems Integration Laboratory (SIL) support.

DRAFT: D400.12663.04.RUC_VS – Aug 2020 A-1

Appendix A: Acronyms and Abbreviations

Table 5 (FOUO) Appendix A: Acronyms and Abbreviations

Acronym or

Abbreviation

Definition

ACD Automatic Call Distribution

APL Approved Product List

AS-SIP Assured Services Session Initiation Protocol

B/P/C/S Base/Post/Camp/Station

BAN Base Area Network

BGP Border Gateway Protocol

C2 Command and Control

CEDC Component Enterprise Data Center

CM Configuration Management

CMP Configuration Management Plan

CONOPS Concept of Operations

CoS Class of Service

COTS Commercial Off-the-Shelf

CSSA Customer Service Support Application

DEVDOC Development Documentation

DISA Defense Information Systems Agency

DISN Defense Information Systems Network

DITCO Defense Information Technology Contracting Organization

DoD Department of Defense

DoDD Department of Defense Directive

DDoS Distributed Denial of Service

DSCP Differentiated Services Code Point

DSN Defense Switched Network

E911 Enhanced 911

EI End Instrument

EoL End-of-Life

EoS End-of-Support

ERC Emergency Response Center

ESInet Emergency Services IP Network

F Flash

FO Flash Override

FOUO For Official Use Only

DRAFT: D400.12663.04.RUC_VS – Aug 2020 A-2

Acronym or

Abbreviation

Definition

GSU Geographically Separated Unit

HQMC Headquarters Marine Corps

HVAC Heating, Ventilation, and Air Conditioning

I Intermediate

IAW In Accordance With

ID Identification

IM Instant Messaging

IP Internet Protocol

IPN Installation Processing Node

ISDN Integrated Services Digital Network

ISN Installation Services Node

ISP Internet Service Provider

IT Information Technology

IVR Interactive Voice Recognition

JB-PE Joint Base Provider Edge

JIE Joint Information Environment

KPP Key Performance Parameter

KSA Key System Attribute

L3VPN Layer 3 Virtual Private Network

LAN Local Area Network

LEC Local Exchange Carrier

LSC Local Session Controller

LSE Lead Systems Engineer

MAC Moves, Adds, Changes

MAGTF Marine Air-Ground Task Force

MARFORCOM U.S. Marine Corps Forces Command

MARFOREUR-AF U.S. Marine Corps Forces Europe – Africa

MARFORK U.S. Marine Corps Forces Korea

MARFORRES Marine Forces Reserve

MCAGCC Marine Corps Air Ground Combat Center

MCAS Marine Corps Air Station

MCB Marine Corps Base

MCBH Marine Corps Base Hawaii

MCEN Marine Corps Enterprise Network

MCEN-N Marine Corps Enterprise Network – Non-Classified Internet

Protocol Router Network

DRAFT: D400.12663.04.RUC_VS – Aug 2020 A-3

Acronym or

Abbreviation

Definition

MCICOM Marine Corps Installations Command

MCITC Marine Corps Information Technology Center

MCLB Marine Corps Logistics Base

MCMWTC Marine Corps Mountain Warfare Training Center

MCNOSC Marine Corps Network Operations and Security Command

MCRD Marine Corps Recruit Depot

MCSC Marine Corps Systems Command

MID PAC Middle Pacific

MITSC MAGTF Information Technology Support Center

MOS Mean Opinion Score

N&I Network and Infrastructure

N/A Not Applicable

NAS Naval Air Station

NCI Network Communications Infrastructure

NCR National Capital Region

NG911 Next Generation 911

NIPRNet Non-Classified Internet Protocol Router Network

NIWC Naval Information Warfare Center

NOLA New Orleans, Louisiana

O Objective

OA&M Operations, Administration, and Maintenance

OPNAVINST Office of the Chief of Naval Operations

OSP Outside Plant

OSPF Open Shortest Path First

P Priority

PAC Pacific

PC Personal Computer

PCA Physical Configuration Audit

PBX Private Branch Exchange

PC Personal Computer

PoP Point of Presence

PSAP Public Safety Answering Point

PSTN Public Switched Telephone Network

QoS Quality of Service

R Routine

RTM Requirements Traceability Matrix

DRAFT: D400.12663.04.RUC_VS – Aug 2020 A-4

Acronym or

Abbreviation

Definition

RUC Regional Unified Capabilities

SBC Session Border Controller

SBU Sensitive but Unclassified

SC Session Controller

SE Systems Engineering

SI System Integrator

SIL Systems Integration Laboratory

SIP Session Initiation Protocol

SME Subject Matter Expert

SRTCP Secure Real-Time Transport Control Protocol

T Threshold

TDM Time Division Multiplexing

TIA Telecommunications Industry Association

TCP Transmission Control Protocol

TMS Telecommunications Management System

TSB Technical Service Bulletins

UC Unified Capabilities

UCR Unified Capabilities Requirements

USMC United States Marine Corps

VDI Video Device Interface

VISP Voice Internet Service Provider

VLAN Virtual Local Area Network

VoIP Voice over Internet Protocol

VPN Virtual Private Network

VRF Virtual Routing and Forwarding

VS Voice Services

WAN Wide Area Network

WLAN Wireless Local Area Network