Dialogic
®
System Release 6.1 CompactPCI for Windows
®
Release Update 35
Event handling in IPML for the network failure alarm is identical to that for QoS alarm
events, except that the handler needs to distinguish between alarm-on and alarm-off
events. The event that is generated when a network failure is detected is of type
IPMEV_QOS_ALARM, and it contains associated data of type
IPM_QOS_ALARM_DATA. The eQoSType field of this data structure is
QOSTYPE_NETWORKFAILURE, and the eAlarmState may be either
ALARM_STATE_ON or ALARM_STATE_OFF.
Global Call Library Considerations
To enable a Global Call application to receive media network failure alarm events, the
application must perform the following general steps:
• Explicitly open and obtain the Global Call line device handle for the IPM board device
with gc_OpenEx( ).
Note: It is not necessary to enable the EVT_NETWORKFAILURE event for the
board device (using ipm_EnableEvents( )). IPML alarm event setting is
taken care of automatically by the software, so the application should not
enable it explicitly.
• Register the device handle (from the open operation) with GCAMS using
gc_SetAlarmNotifyAll( ). This registration uses the wildcard alarm source object
(ASO) ID, ALARM_SOURCE_ID_NETWORK_ID, because the IP Call Control library
ASO ID is not known at this point.
When a media network failure alarm event occurs, the IPML library generates an
IPMEV_QOS_ALARM event, which contains data that identifies the alarm as type
QOSTYPE_NETWORKFAILURE. This event is processed by GCAMS, which generates a
GCEV_ALARM event. When this event is received, the alarm number
QOSTYPE_NETWORKFAILURE, the alarm name (the string “Network Failure”), the
alarm state, the ASO ID, and the ASO name can be retrieved using standard Global Call
alarm APIs.
Notes:1. The IPML ASO will pass the event to GCAMS and consume it, not reporting it directly
via IPML library event.
2. By the same token, Global Call will intercept the IPML EVT_NETWORKFAILURE event,
consume it and report it as a GCAMS alarm event.
Media LAN condition prior to application startup or alarm condition enablement is
reported only in the case of a network disruption (alarm-on); that is, this notification is only
for a disrupted network and not for a healthy network. Subsequent alarm events will occur
as they normally would upon a change in the alarm state.
1.8.2 Documentation
The online bookshelf provided with Dialogic
®
System Release 6.1 CompactPCI for
Windows
®
contains information about all system release features including features for
application development, configuration, administration, and diagnostics.
Comentarios a estos manuales