smi.7

No7信令,我需要交换类似的代码, 请店长审核,谢谢了,急着交换,谢谢

Upon failure, the layer specific provider will return a \fBSDM_ERROR_ACK\fR to
reject the state request.  The provider attaches a \fBM_DATA\fR block which
contains a \fImodname\fR\fB_stats_t\fR structure with \fI0xffffffff\fR in any
values which are in error.

If the layer service provider fails in an attempt to generate a statistics
indications, it will instead deliver a \fBSDM_ERROR_IND\fR to indicate the
failure to provide the statistics indication.  The provider may provide a
partial indication using an attached \fBM_DATA\fR block which contains a
\fImodname\fR\fB_stats_t\fR structure with \fI0xffffffff\fR in any values
which are in error.

Error numbers in \fIsmi_errno\fR which are specific to a statistics request
rejection and indication failure are as follows:
.RS
.TP 16
.B SMI_STATSOOM
Statistic collection has run out of memory.
.TP
.B SMI_STATSSUS
Statistics collection is congested and has been temporarily suspended.
.TP
.B SMI_STATSRES
Statistics collection congestion has cleared and has been resumed.
.RE

.SS "Protocol Events"

.sp
.nf
typedef \fImodname\fR_event {
} \fImodname\fR_event_t;
.fi
.PP
Protocol management primitives may be delivered by the layer service provider
to the stack or layer management to indicate the occurence of a protocol event
which is of interest.  Any \fBM_DATA\fR block attached to the primitive
contains a layer-specific \fImodname\fR\fB_event_t\fR structure (see above)
which represents detailed layer-specific event information.  Event indications
are delivered as low priority \fBM_PROTO\fR, \fBM_EVENT\fR or \fBM_CTL\fR
messages.  This allows data exchange and configuration to take precedence over
event reporting.  Event reporting, however takes precedence over statistics
reporting.
.TP
.B SMI_EVENT_IND
.RS
.sp
.nf
typedef struct {
    smi_ulong   smi_primitive;  /* SMI_EVENT_IND */
    smi_utime   smi_timestamp;
    smi_ulong   smi_severity;
    smi_caddr   smi_module_name;
    smi_caddr   smi_clli;
} \fImodname\fR_event_t;
.fi
.RE
.TP
\fBERRORS\fR (see also "ERROR HANDLING")


.SH "ERROR HANDLING"
.TP
.B SMI_OK_ACK
Upon success, the layer service provider will return a \fBSMI_OK_ACK\fR to
confirm a successful request.  The provider may attach a \fBM_DATA\fR block
which contains a request-specific structure with the results of the request.
This primitive uses the \fBsmi_ok_ack_t\fR structure as follows:
.RS
.sp
.nf
typedef struct {
    smi_ulong  smi_primitive; /* SMI_OK_ACK */
    smi_ulong  smi_state;
    smi_ulong  smi_correct_primitive;
} smi_ok_ack_t;
.fi
.TP
.I smi_state
Contains the management state of the interface.
.TP
.I smi_correct_primitive
Contains the request primitive which this response is acknowledging.
.RE
.TP
.B SMI_ERROR_ACK
Upon failure, the layer service provider will return a \fBSMI_ERROR_ACK\fR to
reject the request due to an error.  The provider may attach a \fBM_DATA\fR
block which contains a request-specific structure which indicates the elements
of the request which are in error.  This primitive uses the
\fBsmi_error_ack_t\fR structure as follows:
.RS
.sp
.nf
typedef struct {
    smi_ulong  smi_primitive; /* SMI_ERROR_ACK */
    smi_ulong  smi_state;
    smi_ulong  smi_error_primitive;
    smi_ulong  smi_errno;
    smi_ulong  smi_reason;
} smi_error_ack_t;
.fi
.TP
.I smi_state
Contains the management state of the interface.
.TP
.I smi_error_primitive
Contains the request primitive which this response is acknowledging.
.TP
.I smi_errno
The error number indicating which error occured.
.TP
.I smi_reason
An additional error reason code.
.RE
.SS "ERRORS"
.IP
Error numbers which are specific to a configuration request rejection are as
follows:
.RS
.TP
.B SMI_CONFLOCKED
The request attempted to perform an illegal operation on a locked
configuration.
.TP
.B SMI_NOCONFDATA
The request was missing configuration data (i.e. missing \fBM_DATA\fR block or
\fBM_DATA\fR block too short.
.TP
.B SMI_BADCONFDATA
Some configuration data was invalid.  The attached \fBM_DATA\fR block contains
\fI0xffffffff\fR in the data elements which are considered invalid.
.RE


.SH "SS7 STREAMS INTERFACES"

The \fIOpenSS7\fR stack provides drivers and modules at all levels of the SS7
stack below ISUP and TCAP.  That is, it provides SS7 Level 2 (Link), SS7 Level
3 (Network), and SCCP (Signalling Connection Control Part) functionality.
These protocol components have been broken into a number of sublevels,
starting from the bottom-most, as follows:
.TP 8
.BR sdli (7)
The \fISignalling Data Link Interface (SDLI)\fR implements SS7 Level 1 [Q702].
SDLI allows real and emulated transmission channels to be implemented for use
under the
.BR sdt (8)
module.  It provides access to the DAEDT and DAEDR
functions of the SS7 Signalling Link [Q703].  Header file \fI<sys/sdli.h>\fR
provides definitions for the interface.  \fIOpenSS7\fR drivers planned or
released at this interface include:
.RS
.TP 12
.BR sdl_eth (8)
SDL emulation using raw Ethernet (IEEE 802.2/802.3).
.TP
.BR sdl_ip (8)
SDL emulation using raw Internet Protocol (IP).
.TP
.BR sdl_udp (8)
SDL emulation using User Datagram Protocol (UDP).
.TP
.BR sdl_tcp (8)
SDL emulation using Transmission Control Protocol (TCP).
.TP
.BR sdl_rtp (8)
SDL emulation using Real-Time Transport Protocol (RTP).
.TP
.BR sdl_sctp (8)
SDL emulation using Strean Control Transport Protocol (SCTP).
.RE
.TP
.BR sdti (7)
The \fISignalling Data Terminal Interface (SDTI)\fR implements partial SS7
Level 2 [Q703].  SDTI allows real and emulated data terminals to be
implemented for use under the
.BR sl (8)
module.  It provides access to the
AERM, SUERM, EIM, DAEDR and DAEDT functions of the SS7 Signalling Link [Q703].
Header file \fI<sys/sdti.h>\fR provides definitions for the interface.
\fIOpenSS7\fR drivers planned or released at this interface include:
.RS
.TP 12
.BR sdt (8)
SDT module for use with SDLI compliant streams.
.TP
.BR vsdt (8)
SDT module for emulating a virtual SDT.
.TP
.BR acb56t (8)
SDT driver for the SeaLevel ACB56 ISA card.
.TP
.BR m2tp (8)
SDT driver for the MTP Level 2 Tunneling Protocol (M2TP).
.TP
.BR soip (8)
SDT driver for SS7 over IP.
.RE
.TP
.BR sli (7)
The \fISignalling Link Interface (SLI)\fR implements complete SS7 Level 2
[Q703].  SLI allows real and emulated signalling links to be implemented for
use under the
.BR sls (8)
module.  It provides access to all SS7 Level 2
state machine functions of the SS7 Signalling Link [Q703].  Header file
\fI<sys/sli.h>\fR provides definitions for the interface.  \fIOpenSS7\fR
drivers planned or released at this interface include:
.RS
.TP 12
.BR sl (8)
SL module for use with SDTI compliant streams.
.TP
.BR vsl (8)
SL module for emulating a virual SL.
.TP
.BR acb56l (8)
SL driver for the SeaLevel ACB56 ISA card.
.TP
.BR m2pa (8)
SL driver for the MTP Level 2 Peer Adaptation (M2PA).
.TP
.BR m2ua (8)
SL driver for the MTP Level User Adaptation (M2UA).
.RE
.TP
.BR slsi (7)
The \fISignalling Link Set Interface (SLSI)\fR implements partial SS7 Level 3
[Q704].  SLSI allows real and emulated signalling link sets to be implemented
for use under the
.BR mtp (8)
multipexor.  It provides access to SS7 Level 3
Link Set state machine functions of the SS7 Message Transfer Part [Q704].
Header file \fI<sys/slsi.h>\fR provides definitions for the interface.
\fIOpenSS7\fR drivers planned or released at this interface include:
.RS
.TP 12
.BR sls (8)
SLS multiplexor for use with SLI compliant streams.
.TP
.BR vsls (8)
SLS module for emulating a virtual SLS.
.TP
.BR m3tp (8)
SLS driver for the MTP Level 3 Tunelling Protocol (M3TP).
.RE
.TP
.BR mtpi (7)
The \fIMessage Transfer Part Interface (MTPI)\fR implements complete SS7 Level
3 [Q704].  MTPI allows real and virtual signalling points and signalling
transfer points to be implemented for use under the
.BR sccp (8)
and
.BR tcap (8)
modules.  It provides access to all SS7 Level 3 state machines
and functions of SS7 Message Transfer Part [Q704].  Header file
\fI<sys/mtpi.h>\fR provides definitions for the interface.  \fIOpenSS7\fR
drivers planned or released at this interface include:
.RS
.TP 12
.BR mtp (8)
MTP multiplexor for use with SLSI compliant streams.
.TP
.BR m3pa (8)
MTP module for the MTP Level 3 Peer Adaptation (M3PA).
.TP
.BR m3ua (8)
MTP module for the MTP Level 3 User Adaptation (M3UA).
.RE
.TP
.BR sccpi (7)
The \fISignalling Connection Control Part Interface (SCCPI)\fR implements
complete SS7 Level 4 [Q711].  SCCPI allows real and virtual subsystems and
global title translations to be implemented for use under the
.BR tcap (8)
module.  It provides access to all SS7 Level 4 state machines of the SS7
Signalling Connnection Control Part [Q711].  Header file \fI<sys/sccpi.h>\fR
provides definitions for the interface.  \fIOpenSS7\fR drivers planned or
released at this interface include:
.RS
.TP 12
.BR sccp (8)
SCCP module for use with MTPI compliant streams.
.TP
.BR sua (8)
SCCP module for the SCCP User Adaptation (SUA).
.RE
.TP
.BR isupi (7)
The \fIIntegrated Services Digital Network (ISDN) User Part Interface (ISUPI)\fR
implements partial SS7 ISUP [Q767].  ISUPI allows call processing agents to
attach to specific PC-PC-CIC ranges in control of trunk groups.  It provides
some basis low-level ISUP state machines (e.g. Unequipped CIC) of the SS7
ISUP [Q767].  Header file \fI<sys/isupi.h>\fR provides definitions for the
interface.  \fIOpenSS7\fR drivers planned or released at this interface
include:
.RS
.TP 12
.BR isup (8)
ISUP module for use with MTPI compliant streams.
.TP
.BR iua (8)
ISUP module for the ISDN User Adaptation (IUA).
.RE
.TP
.BR tcapi (7)
The \fITransaction Capabilities Application Part Interface (TCAPI)\fR
implements partion SS7 TCAP [Q7??].  TCAPI allows transaction processing
agents to attach to specific subsystem instances in control of database
queries.  It provides the TC state machines of the SS7 TCAP [Q???].  Header
file \fI<sys/tcapi.h>\fR provides definitions for the interface.
\fIOpenSS7\fR drivers planned or released at this interface include:
.RS
.TP 12
.BR tcap (8)
TCAP module for use with SCCPI compliant streams.
.RE
.\" .SH "CONFIGURATION"
.\" .SH "ERROR HANDLING"
.SH "SEE ALSO"
.BR isupi (7),
.BR mtpi (7),
.BR sccpi (7),
.BR sdli (7),
.BR sdti (7),
.BR sli (7),
.BR slsi (7),
.BR tcapi (7),
.BR acb56l (8),
.BR acb56t (8),
.BR isup (8),
.BR iua (8),
.BR m2pa (8),
.BR m2tp (8),
.BR m2ua (8),
.BR m3pa (8),
.BR m3tp (8),
.BR m3ua (8),
.BR mtp (8),
.BR sccp (8),
.BR sdl_eth (8),
.BR sdl_ip (8),
.BR sdl_rtp (8),
.BR sdl_sctp (8),
.BR sdl_tcp (8),
.BR sdl_udp (8),
.BR sdt (8),
.BR sl (8),
.BR sls (8),
.BR soip (8),
.BR ss7d (8),
.BR sua (8),
.BR tcap (8),
.BR vsdt (8),
.BR vsl (8),
.BR vsls (8)
.SH "BUGS"
Too many to mention.
.SH "AUTHOR"
.PP
Brian F. G. Bidulock,
.IR "" < [e-mail] >.
.SH "HISTORY"
This STREAMS interface for SS7 is an orignal part of the \fIOpenSS7\fR
package.
.SH "REFERENCES"
.IP "[Q702]" 7
ITU-T Recommendation Q.702 Signalling Data Link
.IP "[Q703]"
ITU-T Recommendation Q.703 Signalling Link
.IP "[Q704]"
ITU-T Recommendation Q.704 Message Transfer Part
.IP "[Q711]"
ITU-T Recommendation Q.711 Signalling Connection Control Part
.IP "[Q767]"
ITU-T Recommendation Q.767 Integrated Services Digital Network (ISDN) User Part
.IP "[Q77?]"
ITU-T Recommendation Q.77? Transaction Capabilities Application Part

.SH COPYRIGHT NOTICE

.sp
Copyright \(co 1997-2001  Brian Bidulock.  All Rights Reserved.

Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.

Permission is granted to copy and distribute modified versions of this
manual under the conditions for verbatim copying, provided that the
entire resulting derived work is distributed under the terms of a
permission notice identical to this one

Since the Linux kernel and libraries are constantly changing, this
manual page may be incorrect or out-of-date.  The author(s) assume no
responsibility for errors or omissions, or for damages resulting from
the use of the information contained herein.  The author(s) may not
have taken the same level of care in the production of this manual,
which is licensed free of charge, as they might when working
professionally.

Formatted or processed versions of this manual, if unaccompanied by
the source, must acknowledge the copyright and authors of this work.