OpenSS7
SS7 for the
Common Man
© Copyright 1997-2007 OpenSS7 Corporation All Rights Reserved.
Last modified: Sat, 01 Nov 2008 10:42:33 GMT
Home TopIndex FirstPrev Next LastMore Download Info FAQ Mail  Home -> Documentation -> Man Pages -> Manpage of T_RCVCONNECT
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

Manpage of T_RCVCONNECT

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


T_RCVCONNECT

Section: OpenSS7 XTI/TLI Networking Library Calls (3)
Updated: 2008-10-31
Index Return to Main Contents

NAME

t_rcvconnect - receive connection request confirmation

SYNOPSIS

#include <xti.h>

int t_rcvconnect(int fd, struct t_call *call);

ARGUMENTS

fd

the transport endpoint upon which to receive the connection confirmation.
call
a pointer to a t_call structure to contain returned information about the connected peer.

DESCRIPTION

fd specifies the local transport endpoint upon which to receive the connection confirmation.

call is a pointer to a t_call structure that returns information about the responding transport endpoint including the remote address, options and connection data. The t_call structure is formatted as follows:

struct t_call {
        struct netbuf addr;             /* address */
        struct netbuf opt;              /* options */
        struct netbuf udata;            /* user data */
        int sequence;                   /* sequence number */
};

The t_call structure returns the following members and information:

addr
is a netbuf(3) structure that returns the responding transport address. The call->addr.maxlen field is significant on call and the call->addr.len field is significant on return. When call->addr.maxlen is zero, no responding address will be returned. When call->addr.len returns zero, no responding address was available.
opt
is a netbuf(3) structure that returns the responding transport options. The call->opt.maxlen field is significant on call and the call->opt.len field is significant on return. When call->opt.maxlen is zero, no responding options will be returned. When call->opt.len returns zero, no responding options were available.
udata
is a netbuf(3) structure that returns the responding connection data. The call->udata.maxlen field is significant on call and the call->udata.len field is significant on return. When call->udata.maxlen is zero, no responding connection data will be returned. When call->udata.len returns zero, no responding connection data was available.
sequence
is not used by t_rcvconnect() and is left unchanged.

CAVEATS

t_rcvconnect() is only valid in state T_OUTCON.

In synchronous mode, t_rcvconnect() will block until a connection confirmation or asynchronous event occurs on fd. In asynchronous mode, if a connection confirmation is not immediately available, t_rcvconnect() will fail, return -1 and set t_errno(3) to TNODATA.

A call to t_rcvconnect() is not normally necessary in synchronous mode. In synchronous mode, t_connect(3) normally blocks until a connection confirmation is received. t_rcvconnect() is typically used in asynchronous mode, where t_connect(3) returns immediately after call and t_rcvconnect() is needed to receive the connection confirmation.

RETURN VALUE

Upon success, t_rcvconnect() returns zero (0). Upon failure, t_rcvconnect() returns -1 and sets t_errno(3) to an appropriate error number.

ERRORS

When t_rcvconnect() fails, it returns -1 and sets t_errno(3) to an appropriate error number as follows:

[TBADF]
fd is invalid.
[TBUFOVFLW]
The maxlen field of a netbuf(3) structure, (addr, opt, udata), passed to the call was non-zero, but insufficient to hold the available information. See, netbuf(3) for more information.
[TLOOK]
An asynchronous event occured before the call could complete. See t_look(3) for more information.
[TNODATA]
An attempt was made to read data but no data indication was available and fd was set for asynchronous mode operation with O_NONBLOCK or O_NDELAY in a call to t_open(3) or fcntl(2).
[TNOTSUPPORT]
The call requires the use of a TLI primitive not supported by the underlying transport provider. This can occur when the underlying transport provider is of the connectionless service type [RT_CLTS.]
[TOUTSTATE]
The call was issued with the interface in a state other than [RT_OUTCON.]
[TPROTO]
A protocol error occured between the XTI/TLI library and the underlying transport provider.
[TSYSERR]
A Linux system error occured and the Linux error number is set in errno(3).

SEE ALSO

errno(3), fcntl(2), netbuf(3), t_connect(3), t_errno(3), t_look(3), t_open(3).

BUGS

t_rcvconnect() has no known bugs. t_rcvconnect() has been tested for the described behavior using the test-xnet(8) and test-xnet_thr(8) conformance test suites.

COMPATIBILITY

The XTI/TLI library functions are compatible with SVR4.2[1], XNS 5.2[2], SUSv2[3]. Compatibility is tested using the test-xnet(8) and test-xnet_thr(8) test case executables and the OpenSS7 XTI/TLI Networking autotest test suite.

CONFORMANCE

XTI/TLI[4], TPI[5], XPG5, XNS 5.2[2], SUSv2[3]. Conformance is tested using the test-xnet(8) and test-xnet_thr(8) test case executables and the OpenSS7 XTI/TLI Networking autotest test suite.

HISTORY

t_rcvconnect first appeared in SVR4.2[1].

VERSIONS

This manpage was written for the OpenSS7 XTI/TLI Library.

REFERENCES

[1]
SVR 4.2, UNIX® System V Release 4.2 Programmer's Manual, 1992, (Englewood Cliffs, New Jersey), AT&T UNIX System Laboratories, Inc., Prentice Hall.
[2]
XNS, Open Group CAE Specification: Technical Standard: Network Services (XNS), Issue 5.2, Draft 2, 1999, (Berkshire, UK), OpenGroup, Open Group Publication. [ISBN 1-85912-241-8] <http://www.opengroup.org/onlinepubs/>
[3]
SUS Version 2, Single UNIX Specification, OpenGroup, Open Group Publication. <http://www.opengroup.org/onlinepubs/>
[4]
XTI/TLI Revision 1.0, Open Group CAE Specification: XOpen Transport Interface, Revision 1, n.d., (Berkshire, UK), XPG, X Programmer's Group. <http://www.opengroup.org/onlinepubs/>
[5]
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/>

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


OpenSS7 XTI/TLI Networking: Package strxnet version 0.9.2.12 released 2008-10-31.

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



Index

NAME
SYNOPSIS
ARGUMENTS
DESCRIPTION
CAVEATS
RETURN VALUE
ERRORS
SEE ALSO
BUGS
COMPATIBILITY
CONFORMANCE
HISTORY
VERSIONS
REFERENCES
TRADEMARKS
IDENTIFICATION

This document was created by man2html, using the manual pages.
Time: 13:28:13 GMT, May 21, 2013
OpenSS7
SS7 for the
Common Man
Home TopIndex FirstPrev Next LastMore Download Info FAQ Mail  Home -> Documentation -> Man Pages -> Manpage of T_RCVCONNECT
Last modified: Sat, 01 Nov 2008 10:42:33 GMT
© Copyright 1997-2007 OpenSS7 Corporation All Rights Reserved.