OpenSS7
SS7 for the
Common Man
© Copyright 1997-2007 OpenSS7 Corporation All Rights Reserved.
Last modified: Mon, 28 Apr 2008 22:52:07 GMT
Home TopIndex FirstPrev Next LastMore Download Info FAQ Mail  Home -> Documentation -> Man Pages -> Manual Page
Quick Links

Download

SCTP

SIGTRAN

SS7

Hardware

STREAMS

Asterisk

Related

Package

Manual

FAQ

Man Pages

Applications

SS7 Stack

ISDN Stack

SIGTRAN Stack

VoIP Stack

MG Stack

SS7/ISDN Devices

IP Transport

Embedded Systems

OS

Documentation

FAQ

SIGTRAN

Design

Conformance

Performance

References

Man Pages

Manuals

Papers

Home

Overview

Status

Documentation

Resources

About

News

Description: Manual Page

Keywords: ss7 ss7/ip ss7 over ip ss7 mtp ss7 sccp ss7 tcap sigtran mtp sccp tcap openss7 acb56 linux telephony pstn linux telephony linux nebs linux compactpci


TPI-SCTP

Section: Transport Provider Interface (TPI) (7)
Updated: Mon, 21 Aug 2017 12:25:42 GMT
Index Return to Main Contents

NAME

tpi_sctp - Transport Provider Interface (TPI) - Stream Control Transmission Protocol (SCTP) Corrigendum

SYNOPSIS

#include <sys/tihdr.h>
#include <sys/tpi_ip.h>
#include <sys/tpi_sctp.h>

int sctp_stream = open(``/dev/sctp_t'', flags);

DESCRIPTION

TPI-SCTP
provides a stream supporting the Transport Provider Interface, tpi(7), to the Stream Control Transmission Protocol[1..3], sctp(7). This STREAMS(4) interface provides the sctp(7) protocol service interface using the T-primitives of the tpi(7). This interface is intended solely for use by user programs or protocol modules requiring the common tpi(7) interfae, such as the xti(3) and sockets(3) library.

ADDRESS FORMATS

The SCTP address format is structured as follows:

struct sockaddr_in {
    sa_family_t         sin_family;  /* Address family */
    unsigned short int  sin_port;    /* Port number */
    struct in_addr      sin_addr;    /* Internet address */
    /* padding */
};

The sockaddr_in structure contains the following members:

sin_family
The address family. Always set to AF_INET or AF_UNSPEC.
sin_port
The port number of the transport endpoint in network byte order.
sin_addr
The IP address of the transport endpoint in network byte order.
(padding)
Padding to pad the size of the sockaddr_in structure to the size of a sockaddr structure.

The structure is padded to the size of a sockaddr structure.

SCTP adresses can also be formed as an array of sockaddr_in structure to represent multiple addresses for multi-homed hosts.

OPTIONS

Options are formatted according to the t_opthdr structure described in xti(3). A SCTP transport provider compliant to this specification supports none, all or any subset of the options defined here. An implementation may restrict the use of any of these options by offering them only in a privileged or read-only mode.

TPI-SCTP provides options at the XTI_GENERIC, T_INET_IP and T_INET_SCTP option levels as described in the subsections that follow. Of the T_INET_SCTP level protocol options, none of the options are of end-to-end significance.

XTI_GENERIC

Options at this level are specific to the X/Open Transport Interface (XTI/TLI) and are common to all transport providers. For more information, see xti(3).

The options defined with the option level XTI_GENERIC are as follows:

XTI_DEBUG
Sets debugging flags for the Stream. This option is formatted as an array of t_uscalar_t. Legal values are implementation defined. For more information, see xti(3).
XTI_LINGER
Sets whether, and the amount of time if, the Stream will linger waiting for unsent data to be delivered. This option is formatted as a t_linger structure as follows:
struct t_linger {
    t_scalar_t l_onoff;   /* option on/off */
    t_scalar_t l_linger;  /* linger time */
};

l_onoff
Specifies whether to linger (T_YES) or not (T_NO). Legal values are T_YES and T_NO.
l_linger
Specifies the amount of time (in seconds) to linger. Legal values are T_INFINITE, T_UNSPEC and all positive numbers including zero.
For more information, see xti(3).
XTI_RCVBUF
Specifies the size, in bytes, of the receive buffer. This option is formatted as a t_uscalar_t. Legal values are all positive, non-zero numbers. For more information, see xti(3).
XTI_RCVLOWAT
Specifies the low water mark above which received data will be indicated and delivered to the user. This option is formatted as t_uscalar_t. Legal values are all positive, non-zero numbers. For more information, see xti(3).
XTI_SNDBUF
Specifies the size, in bytes, of the transmit buffer. This option is formatted as a t_uscalar_t. Legal values are all positive, non-zero numbers. For more information, see xti(3).
XTI_SNDLOWAT
Specifies the low water mark above which queued data will be transmitted to the peer. This option is formatted as a t_uscalar_t. Legal values are all positive, non-zero numbers. For more information, see xti(3).

T_INET_IP

Options with this level are specific to the Internet Protocol (IP)[4] and are common to all the protocol levels in IP. For more information, see tpi_ip(7).

The options defined with the option level T_INET_IP are as follows:

T_IP_OPTIONS
Provides control for the T_IP OPTIONS field. Used for debugging. This option is formatted as an array of unsigned char, up to 40 elements. For more information, see tpi_ip(7).
T_IP_TOS
Provides control of the type-of-service byte present in each transmited T_IP packet. This option is formated as an unsigned char. Legal values can be generated with the SET_TOS() macro described in tpi_ip(7). For more information, see tpi_ip(7).
T_IP_TTL
Provides control of the time-to-live byte present in each transmitted T_IP packet. This option is formatted as an unsigned char. Legal values are from 0 to 255. For more information, see tpi_ip(7).
T_IP_REUSEADDR
Allows multiple non-listening binds to the same address. This option is formatted as an unsigned int. Legal values are T_YES and T_NO. For more information, see tpi_ip(7).
T_IP_DONTROUTE
Bypasses routing tables and routes directly to an interface. Used for debugging. This option is formatted as an unsigned int. Legal values are T_YES and T_NO. For more information, see tpi_ip(7).
T_IP_BROADCAST
Allows broadcast addresses to be used. This option is not applicable to SCTP and is always set to T_NO. This options is formatted as an unsigned int. Legal values are T_YES and T_NO. For more information, see tpi_ip(7).

T_INET_SCTP

Options within this level are specific to the Stream Control Transmission Protocol (SCTP)[1] yet are used by protocol levels using SCTP transport.

The options defined with the option level T_INET_SCTP are as follows:

T_SCTP_NODELAY
T_SCTP_CORK
T_SCTP_PPI
T_SCTP_SID
T_SCTP_SSN
T_SCTP_TSN
T_SCTP_RECVOPT
T_SCTP_COOKIE_LIFE
T_SCTP_SACK_DELAY
T_SCTP_PATH_MAX_RETRANS
T_SCTP_ASSOC_MAX_RESTRANS
T_SCTP_MAX_INIT_RETRIES
T_SCTP_HEARTBEAT_ITVL
T_SCTP_RTO_INITIAL
T_SCTP_RTO_MIN
T_SCTP_RTO_MAX
T_SCTP_OSTREAMS
T_SCTP_ISTREAMS
T_SCTP_COOKIE_INC
T_SCTP_THROTTLE_ITVL
T_SCTP_MAC_TYPE
T_SCTP_HB

typedef struct t_sctp_hb {
    uint32_t hb_dest;           /* destination address */
    t_uscalar_t hb_onoff;       /* activation flag */
    t_uscalar_t hb_itvl;        /* interval in milliseconds */
} t_sctp_hb_t;

T_SCTP_RTO

typedef struct t_sctp_rto {
    uint32_t rto_dest;          /* destination address */
    t_uscalar_t rto_initial;    /* RTO.Initial (milliseconds) */
    t_uscalar_t rto_min;        /* RTO.Min (milliseconds) */
    t_uscalar_t rto_max;        /* RTO.Max (milliseconds) */
    t_uscalar_t max_retrans;    /* Path.Max.Retrans (retries) */
} t_sctp_rto_t;

T_SCTP_MAXSEG
T_SCTP_STATUS

typedef struct t_sctp_dest_status {
    t_uscalar_t dest_addr;      /* dest address */
    t_uscalar_t dest_cwnd;      /* dest congestion window */
    t_uscalar_t dest_unack;     /* dest unacknowledged chunks */
    t_uscalar_t dest_srtt;      /* dest smooth round trip time */
    t_uscalar_t dest_rvar;      /* dest rtt variance */
    t_uscalar_t dest_rto;       /* dest current rto */
    t_uscalar_t dest_sst;       /* dest slow start threshold */
} t_sctp_dest_status_t;

typedef struct t_sctp_status {
    t_uscalar_t curr_rwnd;      /* current receive window */
    t_uscalar_t curr_rbuf;      /* current receive buffer */
    t_uscalar_t curr_nrep;      /* current dests reported */
    t_sctp_dest_status_t curr_dest[0];  /* current primary dest */
} t_sctp_status_t;

T_SCTP_DEBUG
SCTP_OPTION_DROPPING
causes the stream to drop packets.
SCTP_OPTION_BREAK
causes the stream to break the first destination.
SCTP_OPTION_DBREAK
causes the stream to break destinations in both directions.
SCTP_OPTION_RANDOM
causes the stream to drop packets at random.

LOCAL MANAGEMENT INTERFACE

T_INFO_REQ(7)

This primitive is interpreted as in tpi(7).

T_INFO_ACK(7)

This primitive is interpreted as in tpi(7).

TSDU_size
The TPI-SCTP provider has an unlimited TSDU and returns T_INFINITE in this field in accordance with tpi(7).
ETSDU_size
The TPI-SCTP provider supports the concept of expedited data. Expedited data is data that is sent unordered. This field should always return the same value as the TSDU_size above.
CDATA_size
The TPI-SCTP provider supports the concept of connection data. This field will be the maximum amount of data that will fit in a COOKIE-ECHO or COOKIE-ACK message.
DDATA_size
The TPI-SCTP provider does not support the concept of disconnection data and, therefore, returns T_INVALID in this field.
ADDR_size
The maximum size of the SCTP address. This field will always return an integer multiple of the sockaddr_in structure size as described under ``ADDRESS FORMAT'', above.
OPT_size
The TPI-SCTP provider can support any number of options and returns T_INFINITE in this field.
TIDU_size
This is the maximum size of the interface data unit, which is the maximum size of data that can be transferred across the interface in a single getmsg(2) or putmsg(2) system call. This size is always less than or equal to the TSDU_size above.
SERV_type
The service type is one of the following:
T_CLTS
Connectionless service. TPI-SCTP does not support connectionless service. This value will never be returned by TPI-SCTP.
T_COTS
Connection-oriented service. TPI-SCTP does not support connection-oriented service without orderly release. This value will never be returned by TPI-SCTP.
T_COTS_ORD
Connection-oriented service with orderly release. TPI-SCTP supports connection-oriented service with orderly release.
CURRENT_state
The current state of the service interface as described in tpi(7).
PROVIDER_flag
Provider flags are a bitwise OR of the following:
T_SNDZERO
Indicates that the transport user is permitted to send data with a message length of zero. TPI-SCTP does not support the transmission of zero-length TSDUs. This flag must be clear.
XPG4_1
Indicates that the transport provider conforms to XTI in XTP4 and supports the new primitives T_ADDR_REQ(7) and T_ADDR_ACK(7). This flag is normally set.

T_ADDR_REQ(7)

This primitive is interpreted as in tpi(7).

T_ADDR_ACK(7)

This primitive is interpreted as in tpi(7).

LOCADDR_length, LOCADDR_offset
Indicates the length and offset from the beginning of the message block of the sockaddr_in structures that describes the TPI-SCTP addresses to which the Stream is bound. If the Stream is not in a bound state, then LOCADDR_length and LOCADDR_offset return zero (0).
REMADDR_length, REMADDR_offset
Indicates the length and offset from the beginning of the message block of the sockaddr_in structures that describes the TPI-SCTP addresses to which the Stream is connected. If the Stream is not in a connected or connecting state, REMADDR_length and REMADDR_offset return zero (0).

T_CAPABILITY_REQ(7)

This primitive is interpreted as in tpi(7).

T_CAPABILITY_ACK(7)

This primitive is interpreted as in tpi(7).

This primitive returns the T_info_ack(7) structure interpreted as described under T_INFO_ACK , above.

T_BIND_REQ(7)

This primitive is interpreted as in tpi(7).

ADDR_length, ADDR_offset
Specifies the length and offset from the beginning of the message block of the sockaddr_in structures that contain the TPI-SCTP addresses to bind. The TPI-SCTP provider supports wildcard addresses and the address INADDR_ANY. This field can contain an integer number of addresses.
CONIND_number
Specifies the number of connection indications. Specifying a non-zero number of connection indications will place the Stream in listening mode. Any COOKIE-ECHO packet received from a unique source address will generate a connection indication. Connection indications can be accepted or refused (without data). This number specifies the maximum number of outstanding connection indications (those that have neither been accepted nor refused) that the provider will deliver. Because this limit is reached does not mean that the provider discards additional connection indications, but may queue them internally until the number of outstanding connection indications drops beneath the number specified. See tpi(7) for more information.

T_BIND_ACK(7)

This primitive is interpreted as in tpi(7).

ADDR_length, ADDR_offset
Indicates the length and offset from the beginning of the message block of the sockaddr_in structures that contain the TPI-SCTP addresses that were bound. This field can contain an integer number of addresses.
The bound address, sin_addr, returned in this field may be INADDR_ANY if INADDR_ANY was requested, or no address was provided to the bind. However, the sin_port component of the address will be allocated dynamically and set to a non-zero port number if zero (indicating any port) was specified on bind, or no address was provided to the bind. If a non-zero port number could not be dynamically allocated, [TNOADDR] is returned in accordacne with tpi(7).
CONIND_number
Indicates the negotiated number of connection indications. This is normally the same value as was requested; however, if the user requests a number that is considered too large, this number might be a more conservative value.

T_UNBIND_REQ(7)

This primitive is interpreted as in tpi(7).

T_OK_ACK(7)

This primitive is interpreted as in tpi(7).

T_ERROR_ACK(7)

This primitive is interpreted as in tpi(7).

T_OPTMGMT_REQ(7)

This primitive is interpreted as in tpi(7), with the options described under OPTIONS , above.

T_OPTMGMT_ACK(7)

This primitive is interpreted as in tpi(7), with the options described under OPTIONS , above.

PROTOCOL SERVICE INTERFACE

The /dev/sctp_t driver provides a single interface type: connection-oriented mode with orderly release.

T_UNITDATA_REQ(7)

This primitive is interpreted as in tpi(7). The TPI-SCTP provider does not support connectionless mode service and any attempt to issue this primitive will result in a T_ERROR_ACK(7) primitive with the error number [TNOTSUPPORT].

T_UNITDATA_IND(7)

This primitive is interpreted as in tpi(7). The TPI-SCTP provide does not support connectionless mode service and will not issue this primitive.

T_UDERROR_IND(7)

This primitive is interpreted as in tpi(7). The TPI-SCTP provide does not support connectionless mode service and will not issue this primitive.

T_CONN_REQ(7)

This primitive is interpreted as in tpi(7), with the options described under ``OPTIONS'', above and the following considerations:

DEST_length, DEST_offset
Specifies the length and offset from the beginning of the message block of the sockaddr_in structures that contains the TPI-SCTP IP addresses to which to connect the stream. For connection to multi-homed TPI-SCTP hosts, this address may contain multiple sockaddr_in structures.
OPT_length, OPT_offset
Specifies the length and offset from the beginning of the message block of the options containing the connection options to use when forming an association with the peer. These option values can be changed with the T_OPTMGMT_REQ(7) primitive, or overridden for a specific message with the T_OPTDATA_REQ(7) primitive.

Options that have end-to-end significance are: T_SCTP_OSTREAMS and T_SCTP_ISTREAMS.

Options that have significance at connection are: T_SCTP_SACK_DELAY, T_SCTP_PATH_MAX_RETRANS, T_SCTP_ASSOC_MAX_RETRANS, T_SCTP_MAX_INIT_RETRIES, T_SCTP_HEARTBEAT_ITVL, T_SCTP_RTO_INITIAL, T_SCTP_RTO_MIN and T_SCTP_RTO_MAX.

T_CONN_CON(7)

This primitive is interpreted as in tpi(7), with the options described under ``OPTIONS'', above and the following considerations:

RES_length, RES_offset
Indicates the length and offset from the beginning of the message block of the sockaddr_in structures that contains the TPI-SCTP addresses to which the stream is confirmed connected. For responding multi-homed TPI-SCTP hosts, this address may contain multiple sockaddr_in structures.
OPT_length, OPT_offset
Indicates the length and offset from the beginning of the message block of the options present in the connection request and options that are negotiated end-to-end. See OPTIONS , above. The option values represent the negotiation with the local provider as well as end-to-end negotiation with the SCTP peer.

T_CONN_IND(7)

This primitive is interpreted as in tpi(7), with the options described under ``OPTIONS'', above and the following considerations:

SRC_length, SRC_offset
Indicates the length and offset from the beginning of the message block of the sockaddr_in structures that contains the TPI-SCTP IP addresses from which the remote TPI-SCTP is connecting. For connecting multi-homed SCTP hosts, this address may contain multiple sockaddr_in structures.
OPT_length, OPT_offset
Indicates the length and offset from the beginning of the message block of the options of end-to-end significance that were present in the connection request. See OPTIONS , above. The only options indicated are those that are of end-to-end significance and which do not have default values.
SEQ_number
Indicates the sequence number that can be used to accept or reject this connection indication.

T_CONN_RES(7)

This primitive is interpreted as in tpi(7), with the options described under ``OPTIONS'', above and the following considerations:

ACCEPTOR_id
Specifies the acceptor identifier of the Stream onto which the connection is to be accepted. If the connection is to be accepted on the same Stream upon which the corresponding T_CONN_IND(7) was received, this field should be zero (0). It is an error to accept a connection on the listening Stream if there is more than one connection indication outstanding.
OPT_length, OPT_offset
Specifies the length and offset from the beginning of the message block of the options requested for the connection. See OPTIONS , above. Options of local significance are negotiated locally. Options of end-to-end significance are negotiated with the peer.
SEQ_number
Specifies the sequence number in the corresponding T_CONN_IND(7) primitive to which this primitive is responding.

T_DATA_REQ(7)

This primitive is interpreted as in tpi(7).

Data will be sent ordered on the stream.

T_DATA_IND(7)

This primitive is interpreted as in tpi(7).

Data was sent ordered on the stream.

T_EXDATA_REQ(7)

This primitive is interpreted as in tpi(7).

Data will be sent unordered on the stream.

T_EXDATA_IND(7)

This primitive is interpreted as in tpi(7).

Data was sent unordered on the stream.

T_OPTDATA_REQ(7)

This primitive is interpreted as in tpi(7).

DATA_flag
This field can contain a bitwise OR of the following flags:
T_ODF_MORE
Specifies that the next T_OPTDATA_REQ(7) primitive contains data belonging to the same TSDU.
T_ODF_EX
Specifies that the data is expedited. TPI-SCTP does not support true expedited data. Data will be sent unordered within the association.
OPT_length, OPT_offset
Specifies the length and offset from the beginning of the message block of options associated with the data. Options that are significant are: T_SCTP_CORK, T_SCTP_PPI and T_SCTP_SID. T_SCTP_CORK specifies that data should be held from transmission until subsequent data is sent. T_SCTP_PPI specifies the Protocol Payload Identifier to associate with the data. T_SCTP_SID specifies the TPI-SCTP stream within the association upon which to send the data.

T_OPTDATA_IND(7)

This primitive is interpreted as in tpi(7).

DATA_flag
This field can contain a bitwise OR of the following flags:
T_ODF_MORE
Indicates that the next T_OPTDATA_REQ(7) primitive contains data belonging to the same TSDU.
T_ODF_EX
Indicates that the data is expedited. TPI-SCTP does not support true expedited data. Data was received unordered within the association.
OPT_length, OPT_offset
Options that are significant are: T_SCTP_PPI, T_SCTP_SID, T_SCTP_SSN and T_SCTP_TSN. T_SCTP_PPI indicates the Protocol Payload Identifier associated with the data. T_SCTP_SID indicates the stream identifier of the TPI-SCTP stream within the association upon which the data was received. T_SCTP_SSN indicates the stream sequence number for the current data chunk. T_SCTP_TSN indicates the transmission sequence number for the current data chunk.

T_DISCON_REQ(7)

This primitive is interpreted as in tpi(7). This will result in the refusal of an outstanding TPI-SCTP connection indication or an abortive release of an existing TPI-SCTP association.

T_DISCON_IND(7)

This primitive is interpreted as in tpi(7). It indicates the refusal of an outstanding TPI-SCTP outgoing connection request, or the abortive release of an existing TPI-SCTP association.

DISCON_reason
The disconnect reason may be one of the following values:
SEQ_number
The sequence number of a currently outstanding connection indication to which the disconnect corresponds. This value is non-zero only on a listening Stream for which an outstanding T_CONN_IND(7) primtiive has been issued with no T_DISCON_REQ(7) or T_CONN_RES(7) primitive having been issued by the TS user with the same sequence number.

T_ORDREL_REQ(7)

This primitive is interpreted as in tpi(7). This primitive requests or responds to the TPI-SCTP provider orderly release function.

T_ORDREL_IND(7)

This primitive is interpreted as in tpi(7). This primitive indicates or confirms the TPI-SCTP provider orderly release function.

IOCTLS

The TPI-SCTP provider does not support input-output controls. For a standard set of input-output controls supporting the xti(3) library functions, push the timod(4) module.

ERROR HANDLING

Error handling is in accordance with tpi(7).

ERRORS

Errors are in accordance with tpi(7). They are repeated here as follows:

Error Acknowledgement Codes

The following error codes can be present in the TLI_error field of the T_ERROR_ACK(7) message.

[TBADADDR]
A specified address was improperly formatted or contained invalid information.
[TBADOPT]
The specified options were improperly formatted or contained invalid information.
[TACCES]
The user did not have permission to a requested address or option.
[TBADF]
The ACCEPTOR_id does not identify a valid open Stream.
[TNOADDR]
The user did not specify an address and one could not be allocated by the TS provider.
[TOUTSTATE]
The primitive would place the interface out of state.
[TBADSEQ]
The sequence number provided did not correspond to an outstanding connection indication.
[TSYSERR]
A system error occured and the UNIX error code is present in the UNIX_error field of the primitive.
[TBADDATA]
The user specified an amount of data that exceeds the corresponding limit as reported in the T_INFO_ACK(7) primitive.
[TBADFLAG]
The flags specified were invalid or not supported.
[TNOTSUPPORT]
The primitive is not support by the service provider, or not supported in the current mode of operation.
[TADDRBUSY]
The user specified an address that is already bound to another Stream.
[TPROVMISMATCH]
The user specified an ACCEPTOR_id that corresponds to a Stream that belongs to another provider.
[TRESQLEN]
The user specified an ACCEPTOR_id that corresponds to a Stream that is bound in the listening mode.
[TRESADDR]
The user specified an ACCEPTOR_id that corresponds to a Stream that is bound to a different address than that of the listening Stream (and the provider does not support this).

Disconnect Codes

The following error codes can be present in the DISCON_reason field of a T_DISCON_IND(7) primitive:

NOTICES

SCTP has several imlementations. This manpage is for the sctp_t(4) implementation that provides tpi(7) access to the Linux Fast-STREAMS version of TCP. For more information on the Linux NET4 version, see sctp(7).

SEE ALSO

sctp(7), sctp(4), sctp_t(4), tpi(7), tpi_ip(7), xti(3), xti_ip(3), xti_sctp(3), sockets(3).

COMPATIBILITY

The The OpenSS7 Project implementation of SCTP for STREAMS is largely compatible with STREAMS-based implementations such as Lachman or Mentat TCP/IP stacks and Solaris® documentation[5].

CONFORMANCE

This interface conforms to TPI Version 2, Draft 2[6], except where indicated.

HISTORY

The Transport Provider Interface first appeared in SVR 4[7].

REFERENCES

[1]
RFC 2960, Stream Control Transmission Protocol (SCTP), October 2000, Randall R. Stewart, ed., The Internet Society. (Obsoleted by RFC 4960) (Updated by RFC 3309) (Status: PROPOSED STANDARD) <http://www.ietf.org/rfc/rfc2960.txt>
[2]
RFC 3309, Stream Control Transmission Protocol (SCTP) Checksum Change, September 2002, Jonathan Stone, ed., The Internet Society. (Obsoleted by RFC 4960) (Updates RFC 2960) (Status: PROPOSED STANDARD) <http://www.ietf.org/rfc/rfc3309.txt>
[3]
RFC 4460, Stream Control Transmission Protocol (SCTP) Specification Errata and Issues, April 2006, R. Stewart, I. Aria-Rodriguez, K. Poon, A. Caro and M. Tuexen, The Internet Society. (Status: INFORMATIONAL) <http://www.ietf.org/rfc/rfc4460.txt>
[4]
RFC 791/STD 5, Internet Protocol --- DARPA Internet Program --- Protocol Specification, September 1981, J. Postel, ed., The Internet Society. (Also ST0005) (Status: STANDARD) (Updated by RFC 1349) <http://www.ietf.org/rfc/rfc0791.txt>
[5]
Solaris® 8, Solaris 8 Docmentation, 2001, (Santa Clara, California), Sun Microsystems, Inc., Sun. <http://docs.sun.com/>
[6]
TPI Revision 2.0.0, Open Group CAE Specification: Transport Provider Interface (TPI) Specification, Revision 2.0.0, Draft 2, 1999, (Berkshire, UK), OpenGroup, Open Group Publication. <http://www.opengroup.org/onlinepubs/>
[7]
SVR 4, UNIX® System V Release 4 Programmer's Manual, 1990, (Englewood Cliffs, New Jersey), AT&T UNIX System Laboratories, Inc., Prentice Hall.
[8]
Magic Garden, The Magic Garden Explained: The Internals of UNIX® System V Release 4 / An Open Systems Design, 1994, (Australia), B. Goodheart, J. Cox, Prentice Hall. [ISBN 0-13-098138-9]
[9]
Advanced Programming in the UNIX®Environment, 15th edition, December 1997, (Reading, Massachusetts), W. R. Stevens, Addison Wesley. [ISBN 0-201-56317-7]
[10]
RFC 3873, Stream Control Transmission Protocol (SCTP) Mangement Information Base (MIB), September 2004, J. Pastor, M. Belinchon, The Internet Society. (Status: PROPOSED STANDARD) <http://www.ietf.org/rfc/rfc3873.txt>
[11]
RFC 3758, Stream Control Transmission Protocol (SCTP) Partial Reliability Extension, May 2004, Randall R. Stewart, ed., The Internet Society. (Status: PROPOSED STANDARD) <http://www.ietf.org/rfc/rfc3758.txt>
[12]
draft-ietf-tsvwg-addip-sctp-08.txt, Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration, September 24, 2003, Randall R. Stewart, ed., Internet Engineering Task Force - Signalling Transport Working Group. Work In Progress. <http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-addip-sctp-08.txt>

TRADEMARKS

OpenSS7tm
is a trademark of OpenSS7 Corporation.
Linux®
is a registered trademark of Linus Torvalds.
UNIX®
is a registered trademark of The Open Group.
Solaris®
is a registered trademark of Sun Microsystems.

Other trademarks are the property of their respective owners.

IDENTIFICATION

The OpenSS7 Project: Package OpenSS7 version 0.9.2 released Mon, 21 Aug 2017 12:25:42 GMT.

Copyright©1997-2008OpenSS7 Corp.
All Rights Reserved.
(See roff source for permission notice.)



Index

NAME
SYNOPSIS
DESCRIPTION
ADDRESS FORMATS
OPTIONS
XTI_GENERIC
T_INET_IP
T_INET_SCTP
LOCAL MANAGEMENT INTERFACE
T_INFO_REQ(7)
T_INFO_ACK(7)
T_ADDR_REQ(7)
T_ADDR_ACK(7)
T_CAPABILITY_REQ(7)
T_CAPABILITY_ACK(7)
T_BIND_REQ(7)
T_BIND_ACK(7)
T_UNBIND_REQ(7)
T_OK_ACK(7)
T_ERROR_ACK(7)
T_OPTMGMT_REQ(7)
T_OPTMGMT_ACK(7)
PROTOCOL SERVICE INTERFACE
T_UNITDATA_REQ(7)
T_UNITDATA_IND(7)
T_UDERROR_IND(7)
T_CONN_REQ(7)
T_CONN_CON(7)
T_CONN_IND(7)
T_CONN_RES(7)
T_DATA_REQ(7)
T_DATA_IND(7)
T_EXDATA_REQ(7)
T_EXDATA_IND(7)
T_OPTDATA_REQ(7)
T_OPTDATA_IND(7)
T_DISCON_REQ(7)
T_DISCON_IND(7)
T_ORDREL_REQ(7)
T_ORDREL_IND(7)
IOCTLS
ERROR HANDLING
ERRORS
Error Acknowledgement Codes
Disconnect Codes
NOTICES
SEE ALSO
COMPATIBILITY
CONFORMANCE
HISTORY
REFERENCES
TRADEMARKS
IDENTIFICATION

This document was created by man2html, using the manual pages.
Time: 12:25:42 GMT, August 21, 2017
OpenSS7
SS7 for the
Common Man
Home TopIndex FirstPrev Next LastMore Download Info FAQ Mail  Home -> Documentation -> Man Pages -> Manual Page
Last modified: Mon, 28 Apr 2008 22:52:07 GMT
© Copyright 1997-2007 OpenSS7 Corporation All Rights Reserved.