After binding to an M3UA NSAP, the application receives a M3UARUNSTATEIND event indicating the redundancy state of the M3UA layer on the board. The event type associated with this event indicates one of the following states:
Event type |
Description |
SN_HAST_STANDALONE |
Application is in a non-redundant configuration; normal operation can begin. |
SN_HAST_PRIMARY |
M3UA layer is configured on the primary board in a redundant board pair; normal operation is allowed as long as the board remains the primary. |
SN_HAST_BACKUP |
M3UA layer is configured on the backup board in a redundant board pair, monitoring the status of the primary board; no active traffic passes through this SAP until the board becomes the primary member of the pair. |
The M3UARUNSTATEIND event is the first message posted to the application queue for each SAP after the binding is confirmed. No data traffic (unitdata or connections requests) should be directed to this SAP until this event is received.
See the Dialogic® TX Series SS7 Boards Health Management Developer's Reference Manual for details on writing redundant M3UA applications.