Unsolicited Indications

Applications displaying node information can use these indications (which are issued when a change occurs and return summary information only) to trigger the query verbs (returning detailed information). The node only produces the signals listed below as unsolicited indications of the named events if there are any applications registered to receive the information. Applications should therefore unregister if they no longer require the information.
  • DLC_INDICATION
  • DLUR_LU_INDICATION
  • DLUS_INDICATION
  • DOWNSTREAM_LU_INDICATION

    The Communications Server icon lets you know that there is a change in the way things operate.
    		 DOWNSTREAM_LU_INDICATION is Communications Server only.
  • DOWNSTREAM_PU_INDICATION

    The Communications Server icon lets you know that there is a change in the way things operate.
    		 DOWNSTREAM_PU_INDICATION is Communications Server only.
  • FOCAL_POINT_INDICATION
  • ISR_INDICATION

    The Communications Server icon lets you know that there is a change in the way things operate.
    		 ISR_INDICATION is Communications Server only.
  • LOCAL_LU_INDICATION
  • LOCAL_TOPOLOGY_INDICATION
  • LS_INDICATION
  • LU_0_TO_3_INDICATION
  • MODE_INDICATION
  • NN_TOPOLOGY_NODE_INDICATION

    The Communications Server icon lets you know that there is a change in the way things operate.
    		 NN_TOPOLOGY_NODE_INDICATION is Communications Server only.
  • NN_TOPOLOGY_TG_INDICATION

    The Communications Server icon lets you know that there is a change in the way things operate.
    		 NN_TOPOLOGY_TG_INDICATION is Communications Server only.
  • PLU_INDICATION
  • PORT_INDICATION
  • PU_INDICATION
  • REGISTRATION_FAILURE
  • RTP_INDICATION
  • SESSION_INDICATION
  • SESSION_FAILURE_INDICATION
The entry points used for indications are:
WinNOFRegisterIndicationSink
Register to receive an indication
WinNOFUnregisterIndicationSink
Unregister from receiving an indication
WinNOFGetIndication
Receive an indication

These indications are passed to any indication sinks that have registered with the Node Operator Facility. If the component generating the indication is unable to send it, then it sets the data_lost indicator on the next indication it issues. If the data_lost flag has been set to AP_YES on an indication, then subsequent data fields can be set to null. This flag is used to notify the application that a change has occurred whose details have been lost, indicating that the application should respond by issuing the appropriate query verb.

Note that the signal LULU_EVENT is also classified as an indication as it is sent unsolicited by the node to a process registered using the verbs REGISTER_LULU_EVENT and UNREGISTER_LULU_EVENT. It is not listed above, since its behavior is significantly different: registration is for an LU-Partner LU pair, and there is no equivalent of data_lost — these LULU event indications are generated without fail.