• 3.5.1.  Alarm Handling for DM3 boards
• 3.5.2.  Alarm Handling for Springware Boards

3.5.  Alarm Handling

Alarm handling using Global Call is different depending on the board architecture (DM3 or Springware). The following sections provide information about handling alarms in each architecture:

• Section 3.5.1.  Alarm Handling for DM3 boards
• Section 3.5.2.  Alarm Handling for Springware Boards

3.5.1.  Alarm Handling for DM3 boards

When using DM3 boards, alarms are recognized on a span basis. Once an alarm is detected, all open channels on that span receive a GCEV_BLOCKED event. When the alarm is cleared, open channels receive a GCEV_UNBLOCKED event.

The gc_SetEvtMsk( ) function can be used to mask events on a line device. Using the gc_SetEvtMsk( ) function on a line device for a time slot sets the mask for the specified time slot only and does not apply to all time slots on the same trunk as is the case when using Springware boards.

The set of Global Call functions that comprise the Global Call Alarm Management System (GCAMS) interface are supported with the following restrictions:

• Using GCAMS, the application has the ability to set which alarms are blocking and non-blocking as described in the Global Call API Programming Guide. However, this capability applies on a span basis only. Changing which alarms are blocking and non-blocking for one time slot results in changing which alarms are blocking and non-blocking for all time slots on the span.
• For T-1 technology, the following alarms can be transmitted:
  • YELLOW
  • BLUE
• For E-1 technology, the following alarms can be transmitted:
  • Remote alarm - DEA_REMOTE
  • Unframed all 1's alarm - DEA_UNFRAMED1
  • Signaling all 1's alarm - DEA_SIGNALALL1
  • Distant multi-framed alarm - DEA_DISTANTMF
• Using the gc_GetAlarmParm( ) and gc_SetAlarmParm( ) functions to retrieve and set specific alarm parameters, for example alarm triggers, is not supported.

The following list shows the alarms that are supported on E-1 for DM3 boards. The dagger symbol (_) next to an alarm name indicates that the alarm is blocking by default. The default can be changed using gc_SetAlarmConfiguration( ).

• DTE1_CRC_CFA_ - Time slot 16 CRC failure
• DTE1_CRC_CFAOK - Time slot 16 CRC failure recovered
• DTE1_FSERR - Received frame sync error
• DTE1_FSERROK - Received frame sync error recovered
• DTE1_LOOPBACK_CFA - Diagnostic mode on the line trunk
• DTE1_LOOPBACK_CFAOK - Diagnostic mode on the line trunk recovered
• DTE1_LOS - Received loss of signal
• DTE1_LOSOK - Received loss of signal recovered
• DTE1_MFSERR - Received multi-frame sync error
• DTE1_MFSERROK - Received multi-frame sync error recovered
• DTE1_RDMA - Received distant multi-frame alarm
• DTE1_RDMAOK - Received distant multi-frame alarm recovered
• DTE1_RED_ - Received red alarm
• DTE1_REDOK - Received red alarm recovered
• DTE1_RLOS - Received loss of sync
• DTE1_RLOSOK - Received loss of sync recovered
• DTE1_RRA_ - Received remote alarm
• DTE1_RRAOK - Received remote alarm recovered
• DTE1_RSA1 - Received signaling all 1's
• DTE1_RSA1OK - Received signaling all 1's recovered
• DTE1_RUA1 - Received unframed all 1's
• DTE1_RUA1OK - Received unframed all 1's recovered

The following list shows the alarms that are supported on T-1 for DM3 boards. The dagger symbol (_) next to an alarm name indicates that the alarm is blocking by default. The default can be changed using gc_SetAlarmConfiguration( ).

• DTT1_LOOPBACK_CFA - Diagnostic mode on the line trunk
• DTT1_LOOPBACK_CFAOK - Diagnostic mode on the line trunk recovered
• DTT1_LOS - Initial loss of signal detected
• DTT1_LOSOK - Signal restored
• DTT1_RBL - Received blue alarm
• DTT1_RBLOK - Received blue alarm restored
• DTT1_RCL - Received carrier loss
• DTT1_RCLOK - Received carrier loss restored
• DTT1_RED_ - Received a red alarm condition
• DTT1_REDOK - Red alarm condition recovered
• DTT1_RLOS - Received loss of sync
• DTT1_RLOSOK - Received loss of sync restored
• DTT1_RYEL_ - Received yellow alarm
• DTT1_RYELOK - Received yellow alarm restored

3.5.2.  Alarm Handling for Springware Boards

As described in the Global Call API Library Reference, the GCEV_BLOCKED event indicates that a line is blocked and the application cannot issue call-related function calls, and the GCEV_UNBLOCKED event indicates that the line has become unblocked. For example, an alarm condition has occurred or has been cleared, respectively. These events are generated on every opened line device associated with the trunk on which the alarm occurs, if the event is enabled. These events are enabled by default. The application may disable and enable the events by using the gc_SetEvtMsk( ) function.

Setting the event mask on any line device that represents a time slot will result in setting the mask to the same value on all time slot level line devices on the same trunk. Additionally, setting the event mask on a line device that represents the board will have the same effect (that is, it will set the mask for all time slot level line devices on that trunk).

When an alarm occurs on a Global Call line device, the application must call the dx_stopch( ) function to stop any application initiated voice processing, such as dx_play( ) and dx_record( ), that is associated with that line device. The application should wait for the receipt of the GCEV_UNBLOCKED event that signals the end of the alarm condition; then the application can proceed with its call processing (for example, making or receiving calls).

Alarm notification can be configured for time slot devices using the Global Call Alarm Management System (GCAMS). The set of Global Call functions that comprise the GCAMS interface for alarm management is supported. See the Global Call API Programming Guide for more information on GCAMS and the Global Call API Library Reference for more information on the GCAMS functions.

The following list shows the alarms that are supported on E-1 for Springware boards. The dagger symbol (_) next to an alarm name indicates that the alarm is blocking by default. The default can be changed using gc_SetAlarmConfiguration( ).

• DTE1_BPVS_ - Bipolar violation count saturation
• DTE1_BPVSOK - Bipolar violation count saturation recovered
• DTE1_CECS_ - CRC4 error count saturation
• DTE1_CECSOK - CRC4 error count saturation recovered
• DTE1_DPM_ - Driver performance monitor failure
• DTE1_DPMOK - Driver performance monitor failure recovered
• DTE1_ECS_ - Error count saturation
• DTE1_ECSOK - Error count saturation recovered
• DTE1_FSERR_ - Received frame sync error
• DTE1_FSERROK - Received frame sync error recovered
• DTE1_LOS_ - Received loss of signal
• DTE1_LOSOK - Received loss of signal recovered
• DTE1_MFSERR_ - Received multi-frame sync error
• DTE1_MFSERROK - Received multi-frame sync error recovered
• DTE1_RDMA_ - Received distant multi-frame alarm
• DTE1_RDMAOK - Received distant multi-frame alarm recovered
• DTE1_RED - Received red alarm
• DTE1_REDOK - Received red alarm recovered
• DTE1_RLOS_ - Received loss of sync
• DTE1_RLOSOK - Received loss of sync recovered
• DTE1_RRA_ - Received remote alarm
• DTE1_RRAOK - Received remote alarm recovered
• DTE1_RSA1_ - Received signaling all 1's
• DTE1_RSA1OK - Received signaling all 1's recovered
• DTE1_RUA1_ - Received unframed all 1's
• DTE1_RUA1OK - Received unframed all 1's recovered

The following list shows the alarms that are supported on T-1 for Springware boards. The dagger symbol (_) next to an alarm name indicates that the alarm is blocking by default. The default can be changed using gc_SetAlarmConfiguration( ).

• DTT1_B8ZSD_ - Bipolar eight zero substitution detected
• DTT1_B8ZSD - Bipolar eight zero substitution detected recovered
• DTT1_BPVS_ - Bipolar violation count saturation
• DTT1_BPVSOK - BPVS restored
• DTT1_DPM_ - Driver performance monitor
• DTT1_DPMOK - Driver performance monitor restored
• DTT1_ECS_ - Error count saturation
• DTT1_ECSOK - Error count saturation recovered
• DTT1_FERR_ - Frame bit error
• DTT1_FERROK - Frame bit error restored
• DTT1_LOS_ - Initial loss of signal detected
• DTT1_LOSOK - Signal restored
• DTT1_OOF_ - Out of frame error; count saturation
• DTT1_OOFOK - Out of frame restored
• DTT1_RBL_ - Received blue alarm
• DTT1_RBLOK - Received blue alarm recovered
• DTT1_RCL_ - Received carrier loss
• DTT1_RCLOK - Received carrier loss restored
• DTT1_RED_ - Received a red alarm condition
• DTT1_REDOK - Red alarm condition recovered
• DTT1_RLOS_ - Received loss of sync
• DTT1_RLOSOK - Received loss of sync restored
• DTT1_RYEL_ - Received yellow alarm
• DTT1_RYELOK - Received yellow alarm restored

Click here to contact Telecom Support Resources