The Fire and Emergency Services (F&ES) communications over a site's private telephone system must provide the originating telephone number to the emergency services answering point or call center through a transfer of Automatic Number Identification (ANI) or Automatic Location Identification (ALI) information.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-259921 | SRG-VOIP-000410 | SV-259921r948767_rule | CCI-001606 | medium |
| Description | ||||
| The implementation of Enhanced F&ES telecommunications services requires that the emergency services answering point or call center be able to automatically locate the calling party in the event they cannot provide their location. This is a two-part process. First the telephone system must be able to provide the answering station with the telephone number from which the emergency call originated. This is ANI information. Second, this phone number must be correlated to a physical address or location. This is called ALI information. ANI information comes from the telephone system controller. ALI information may come from an external database that associates the ANI information to the ALI information, or the telephone system controller may maintain the ALI database internally. If the ALI database is internal to the telephone system controller, emergency services answering point or call center only needs to receive ALI information, providing it contains the originating telephone number. For enterprise systems, the support for E911 by the enterprise Local Session Controller (LSC) (or any remote LSC construct) is governed by Federal Communications Commission (FCC) rules, as well as other federal, state, and local law. The design and implementation of all telephone system systems must include reasonable efforts to provide E911, even when the access connection to the Enterprise LSC is severed. | ||||
| STIG | Date | |||
| Enterprise Voice, Video, and Messaging Policy Security Requirements Guide | 2025-12-23 | |||
Related Frameworks
1 mapping across 3 frameworks
Related Frameworks
SCF0 mappings
No source states a mapping between these directly.
Also reachable in 3 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V1R4intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- SCF Secure Traceability Relationship Mapping (STRM)2026.2equal to
NIST 800-530 mappings
No source states a mapping between these directly.
Also reachable in 2 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V1R4intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
CCI1 mapping
CCI-001606
1.00
- DISA STIG Benchmark (XCCDF)V1R4intersects(normalised)
Details
Check Text (C-259921r948767_chk)
Inspect the telephone system configuration to determine compliance with the requirement. Verity the local DOD telephone system, VoIP or traditional, is configured to provide the originating telephone number of an F&ES call to the emergency services answering point or call center through a transfer of ANI or ALI information.
If the originating telephone number of an F&ES call is not available or is not provided to the emergency services answering point or call center, this is a finding.
Fix Text (F-63559r946683_fix)
Configure the local DOD telephone system, VoIP or traditional, to provide the originating telephone number of an F&ES call to the emergency services answering point or call center through a transfer of ANI or ALI information.