8.1.1 Alarm Management System Components

The alarm management system is made up of several components, including GCAMS. The other components are the customer application's alarm management system (AMS), and the alarm source objects (ASOs). ASOs can either reside within a call control library (cclib) or separate from a call control library. Figure 30 illustrates the relationship between the alarm management system components.

Figure 30. Architectural Diagram of Alarm Management Components

The customer application is responsible for configuring the behavior of GCAMS, including designating which alarms are blocking, which alarms the application wants to be notified of, and controlling the flow of alarms to the application. For more information, see Section 8.2.3, "Configuration of Alarm Properties and Characteristics".

GCAMS acts as an interface between the customer application and the alarm source objects. GCAMS passes requests from the application to the ASOs, processes application configuration requests, and processes ASO alarm events. GCAMS also maintains a database of the current configuration attributes by alarm source object and line device. In addition, GCAMS implements the ASOs that are common across multiple technologies. For more on the operation and configuration of GCAMS, see Section 8.2, "Operation and Configuration of GCAMS".

The final components of the alarm management system are the ASOs. ASOs are responsible for generating alarm events when alarms occur and then clear. If configured to do so, ASOs are also responsible for starting and stopping the transmission of alarms and setting and getting alarm parameters, such as timing parameters.

Click here to contact Telecom Support Resources