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

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_CONN_REQ

Section: Transport Provider Interface (TPI) (7)
Updated: 2008-10-31
Index Return to Main Contents

NAME

T_CONN_REQ - Connect Request

SYNOPSIS

This message consists of one M_PROTO message block followed by zero or more M_DATA blocks if any user data is specified by the transport user. The format of the M_PROTO message block is as follows:

struct T_conn_req {
    t_scalar_t   PRIM_type;      /* Always T_CONN_REQ */
    t_scalar_t   DEST_length;
    t_scalar_t   DEST_offset;
    t_scalar_t   OPT_length;
    t_scalar_t   OPT_offset;
};

DESCRIPTION

This primitive requests that the transport provider connect to the specified destination.

PARAMETERS

PRIM_type
identifies the primitive type.
DEST_length
is the length of the destination address
DEST_offset
is the offset (from the beginning of the M_PROTO message block) where the destination address begins.
OPT_length
is the length of the requested options associated with the primitive.
OPT_offset
is the offset (from the beginning of the M_PROTO message block) of the requested options associated with the primitive.

The proper alignment of the destination address and options in the M_PROTO message block is not guaranteed. The destination address and options in the M_PROTO message block are however, aligned the same as they were received from the transport user.

Note:
The information located by the defined structures may not be in the proper alignment in the message blocks, so the casting of structure definitions over these fields may produce incorrect results. It is advised that the transport providers supply exact format specifications for the appropriate information to the transport users.

RULES

This primitive requires the transport provider to generate one of the following acknowledgments on receipt of the primitive, and the transport user must wait for the acknowledgment before issuing any other primitives:

Successful

Correct acknowledgment of the primitive is indicated via the T_OK_ACK(7) primitive described in reference TPI-SMD.

Non-fatal errors

These errors will be indicated via the T_ERROR_ACK(7) primitive described in reference TPI-SMD.

ERRORS

The allowable errors are as follows:
[TACCES]
This indicates that the user did not have proper permissions for the use of the requested address or options.
[TADDRBUSY]
The transport provider does not support multiple connections to the same destination address. This error indicates that a connection already exists for the requested destination.
[TBADADDR]
This indicates that the protocol address was in an incorrect format or the address contained invalid information. It is not intended to indicate protocol connection errors, such as an unreachable destination. Those error types are indicated via the T_DISCON_IND(7) primitive.
[TBADDATA]
The amount of user data specified was invalid.
[TBADOPT]
This indicates that the options were in an incorrect format, or they contained invalid information.
[TNOTSUPPORT]
This primitive is not supported by the transport provider.
[TOUTSTATE]
The primitive would place the transport interface out of state.
[TSYSERR]
A system error has occurred and the Linux system error is indicated in the primitive.

MODES

Only connection-mode.

ORIGINATOR

Transport user.

SEE ALSO

T_CONN_CON(7), T_ERROR_ACK(7).

HISTORY

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

CONFORMANCE

This interface conforms to TPI Version 2, Draft 2[2].

REFERENCES

[1]
SVR 4, UNIX® System V Release 4 Programmer's Manual, 1990, (Englewood Cliffs, New Jersey), AT&T UNIX System Laboratories, Inc., Prentice Hall.
[2]
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/>
[3]
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]
[4]
Advanced Programming in the UNIX®Environment, 15th edition, December 1997, (Reading, Massachusetts), W. R. Stevens, Addison Wesley. [ISBN 0-201-56317-7]

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©1992UNIX International, Inc.
Copyright©1997-2008OpenSS7 Corp. All Rights Reserved.
(See roff source for permission notice.)



Index

NAME
SYNOPSIS
DESCRIPTION
PARAMETERS
RULES
Successful
Non-fatal errors
ERRORS
MODES
ORIGINATOR
SEE ALSO
HISTORY
CONFORMANCE
REFERENCES
TRADEMARKS
IDENTIFICATION

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