8.2.2 Generation of Alarm Events

The GCEV_ALARM event can be generated by both blocking and non-blocking alarms. Blocking alarms are alarms that generate GCEV_BLOCKED and GCEV_UNBLOCKED events when the alarms set and clear. GCEV_ALARM events are for information purposes only and do not cause any channel state or call state changes.

Note: The previous method of retrieving alarm information was via the use of the dt_open( ) function. Using the GCEV_ALARM event is the preferred method for retrieving alarm information.

In order for the GCEV_ALARM event to be returned by the application, the notify attribute for the specified alarm source object must be set to "on" via the gc_SetAlarmConfiguration( ) function. In addition, the alarm source object must meet the alarm flow configuration requirements, which are set using the gc_SetAlarmFlow( ) function or the gc_NotifyAll( ) function. (See Section 8.2.3, "Configuration of Alarm Properties and Characteristics" for more information.)

When the application returns a GCEV_ALARM event, indicating that an alarm has been received, information about the alarm can be retrieved using the gc_AlarmName( ) function. The gc_AlarmName( ) function converts the alarm to its English name to allow for interpretation of the reason for the alarm. For more information on retrieving alarm data for a given ALARM_EVENT, see Section 8.2.5, "Retrieving Alarm Data".

Some of the ways the information provided by the GCEV_ALARM events can be used are:

• Administration of alarms (using alarm information to determine the appropriate configuration of GCAMS)
• Detection and transmission of alarm conditions between networks (drop and insert applications)
• Manual handling of alarms for drop and insert applications
• Generating reports
• Troubleshooting connections and protocols

Click here to contact Telecom Support Resources