Руководство Пользователя для Cisco DNCS System Release 2.8.1 3.8.1 4.3.1



For information on configuring, maintaining, or testing an EAS in an RCS, refer to the Distributed EAS

on the Regional Control System, Configuration and Troubleshooting Guide (part number 4002342).



Because many digital systems are very large, an EAM could be very disruptive to a community that is

not affected by a particular alert. Therefore, we offer a software product that you can purchase
separately to enable the DNCS to filter and send EAMs to only targeted states, counties, or
subdivisions. For more information about this software product, contact the representative who
handles your account.

Important: This process describes how the digital EAS works in a system that uses a Regional Control
System (RCS). The topic 

, describes how the digital EAS functions in a system

without an RCS.

In an RCS, processes that manage Emergency Alert Messages (EAMs) reside both on the DNCS and on each
remote RNCS/LIONN. Where the EAM originates determines how the EAM is processed. When the EAM
originates from an Emergency Alert Controller (EAC) in a remote site, it forwards the EAM on to a process on
the RNCS/LIONN, which forwards the EAM on to the DNCS. Together, the DNCS and the RNCS/LIONN deliver
the EAM to affected DHCTs in the RCS:



EAMs processed by the DNCS are distributed to third-party DHCTs using OpenCable compliance

without a PowerKEY CableCARD module.



EAMs processed by an RNCS/LIONN are distributed to third-party DHCTs that use OpenCable

compliance with a PowerKEY CableCARD module and to our DHCTs.

The following illustration explains in more detail the processes that are required to process an EAM. When
reviewing this illustration, keep in mind that the equipment that receives the EAM—the RF receiver and the
Emergency Alert Controller (EAC)—is provided by a vendor other than us.