Events from the TCP Interface to the Application Layer
The TCP Interface can send the events described in the following table.
Table 220: TCP Interface to Application Layer
| Event | Notes |
|---|---|
OPC_INTRPT_REMOTE |
The following interrupt codes should be expected: • TCPC_IND_CONNECT_REQUEST (5)• 0 Note: TCPC_COMMAND_STATUS_IND (10) is sent only to the tcp_manager process. |
OPC_INTRPT_STRM |
These events can come with an ICI. Each possible ICI will have an "ICI type" field, which can be used to identify the type but is not required. |
The "tcp_status_ind" ICI has the following five fields:• " conn_id"• " status"• " urgent"• " ICI type" (value is 2, but there is no #define for this)• " packet count" |
|
The "tcp_open_ind_inet" and "tcp_open_ind" ICI both have these six fields. The difference is that "rem addr" is an integer for "tcp_open_ind."These ICIs are sent only with code, TCPC_IND_CONNECT_REQUEST.• " conn_id"• " rem addr"• " local port"• " accept status"• " rem port"• " ICI type" |
For more information in the next section, see:
For more information in the previous sections, see: