SCCP redundant application startup

Step

Action

1

Creates one or more CTA queues on which to receive events.

A single queue can be used for SCCP and HMI service events, or separate queues can be used, depending on the organization of the application (single-threaded versus multi-threaded).

2

Creates CTA contexts for the HMI service and for each instance of the SCCP service being opened.

For a single-node application opening both boards in a redundant pair, a separate context must be created for each SCCP user SAP (SSCP subsystem) being opened on each board. These contexts can be assigned to the same or to separate queues.

3

Opens the appropriate service (SCCP or HMI) for each context and waits for the CTAEVN_OPEN_SERVICES_DONE event.

If a single queue is used for multiple contexts, be prepared to process events from other contexts while waiting for the CTAEVN_OPEN_SERVICES_DONE event; failure to do so may result in an infinite loop.

4

Waits for the SCCPRUNSTATEIND event from the SCCP service before starting traffic.

If the SCCP layer on the target board is already in the primary or backup state, a SCCPRUNSTATEIND event is immediately delivered to the application identifying the state (event type = SPRS_PRIMARY or SPRS_BACKUP).

If still in the starting state (has not yet been designated primary or backup by the system manager application), a SCCPRUNSTATEIND event is not generated until the board is set to primary or backup state.

If the board is operating in a standalone (non-redundant) configuration, the application immediately receives a SCCPRUNSTATEIND event with an event type of SPRS_STANDALONE.