lmi.7

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

by the SS7 Configuration Daemon \fBss7d\fR(8) when enabling an assembled or
reconfigured SS7 protocol stack.
.TP
.B LMI_ENABLE_REQ
Requests that the LMI provider enable itself for data transfer and protocol
operations.  \fBLMI_ENABLE_REQ\fR is valid for both \fIStyle 1\fR and
\fIStyle 2\fR LMI providers in the \fBLMI_DISABLED\fR state.  The
\fBLMI_ENABLE_REQ\fR uses the \fBlmi_enable_req_t\fR structure which contains
only the \fIlmi_primitive\fR which is set to \fBLMI_ENABLE_REQ\fR.
.TP
.B LMI_ENABLE_CON
Returned once the enable request is successful.  For some \fIStyle 2\fR LMI
providers, this may take some time and is not necessarily returned in
immediate response to the enable request.
.TP
.B LMI_ERROR_ACK
Returned with the error number and explanation set if the enable request
fails.
.PP
.B LMI_DISABLE_REQ, LMI_DISABLE_CON, LMI_ERROR_ACK
.PP
Invoked by the LMI user on a \fIStyle 1\fR or \fIStyle 2\fR LMI provider to
disable the provider from further data transfer and protocol operations.  This
primitive is normally used by the SS7 Configuration Daemon \fBss7d\fR(8) when
disabling an SS7 protocol stack for disassembly or reconfiguration.
.TP
.B LMI_DISABLE_REQ
Requests that the LMI provider disable itself from further data transfer and
protocol operations.  \fBLMI_DISABLE_REQ\fR is valid for both \fIStyle 1\fR
and \fIStyle 2\fR LMI providers in the \fBLMI_ENABLED\fR state.  The
\fBLMI_DISABLE_REQ\fR uses the \fBlmi_disable_req_t\fR structure which
contains only the \fIlmi_primitive\fR which is set to \fBLMI_DISABLE_REQ\fR.
.TP
.B LMI_DISABLE_CON
Returned once the disable request is successful.  For some \fIStyle 2\fR LMI
providers, this may take some time and is not necessarily returned in
immediate response to the disable request.
.TP
.B LMI_ERROR_ACK
Returned with the error number and explanation set if the disable request
fails.

.SS "ERROR HANDLING"
.TP
.B LMI_OK_ACK
Upon success, the layer service provider will return a \fBLMI_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; /* LMI_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 LMI_ERROR_ACK
Upon failure, the layer service provider will return a \fBLMI_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; /* LMI_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.  This error number
corresponds to the Unix \fIerrno\fR (see \fBstrerror\fR(2)) if applicable.
.TP
.I smi_reason
An additional error reason code.
.RE
.TP
.B ERRORS
Error numbers which are specific to a configuration request rejection are as
follows:
.sp
.RS
.TS
tab(:);
lb 2 l.
.TH
LMI_UNSPEC:Unknown or unspecified
LMI_BADADDRESS:Address was invalid
LMI_BADADDRTYPE:Invalid address type
LMI_BADDIAL:(not used)
LMI_BADDIALTYPE:(not used)
LMI_BADDISPOSAL:Invalid disposal parameter
LMI_BADFRAME:Defective SDU received
LMI_BADPPA:Invalid PPA identifier
LMI_BADPRIM:Unregognized primitive
LMI_DISC:Disconnected
LMI_EVENT:Protocol-specific event ocurred
LMI_FATALERR:Device has become unusable
LMI_INITFAILED:Link initialization failed
LMI_NOTSUPP:Primitive not supported by this device
LMI_OUTSTATE:Primitive was issued from invalid state
LMI_PROTOSHORT:M_PROTO block too short
LMI_SYSERR:UNIX system error
LMI_WRITEFAIL:Unitdata request failed
LMI_CRCERR:CRC or FCS error
LMI_DLE_EOT:DLE EOT detected
LMI_FORMAT:Format error detected
LMI_HDLC_ABORT:Aborted frame detected
LMI_OVERRUN:Input overrun
LMI_TOOSHORT:Frame too short
LMI_INCOMPLETE:Partial frame received
LMI_BUSY:Telephone was busy
LMI_NOANSWER:Connection went unanswered
LMI_CALLREJECT:Connection rejected
LMI_HDLC_IDLE:HDLC line went idle
LMI_HDLC_NOTIDLE:HDLC link no longer idle
LMI_QUIESCENT:Line being reassigned
LMI_RESUMED:Line has been reassigned
LMI_DSRTIMEOUT:Did not see DSR in time
LMI_LAN_COLLISIONS:LAN excessive collisions
LMI_LAN_REFUSED:LAN message refused
LMI_LAN_NOSTATION:LAN no such station
LMI_LOSTCTS:Lost Clear to Send signal
LMI_DEVERR:Start of device-specific error codes
.TE
.RE

.SH "INPUT OUTPUT CONTROL INTERFACE"
.PP
All device drivers or modules which provide a Local Management Interface (LMI)
provide a set of IOCTLs which are used to configure and change the
characteristics of the operation of the driver or module.  Each driver or
module named \fIxxx\fR provides IOCTLs of the form
\fIxxx\fB_IOC\fIfunction\fR.  For the particulars of datastructures and
specific control commands see the \fIxxx\fR man page (e.g, \fBsdli\fR(7))
for the \fIxxx\fR protocol level driver.

Controls which should be provided by all drivers are as follows:

.TP
\fIxxx\fB_IOCGOPTIONS, \fIxxx\fB_IOCSOPTIONS
Used to get or set the options associated with the protocol for a specific
LMI driver.  The two common fields for all protocol drivers and modules are
contained in the \fBlmi_option_t\fR structure as follows:
.RS
.sp
.nf
typedef struct lmi_option {
    lmi_ulong   pvar;
    lmi_ulong   popt;
} lmi_option_t;
.fi
.TP
.I pvar
Contains a protocol variant number which defaults to \fBSS7_PVAR_ITUT_88\fR.
The protocol variant number is one of the following values:
.RE
.RS
.IP
.TS
tab(:);
lb 2 l.
.TH
SS7_PVAR_ITUT_88:ITU-T 1988 (Blue Book)
SS7_PVAR_ITUT_93:ITU-T 1993 (White Book)
SS7_PVAR_ITUT_96:ITU-T 1996 (Grey Book)
SS7_PVAR_ITUT_00:ITU-T 2000 (? Book)
SS7_PVAR_ANSI_88:ANSI T1.111-1988
SS7_PVAR_ANSI_92:ANSI T1.111-1992
SS7_PVAR_ETSI_88:ETSI ETS 300 008 1988
SS7_PVAR_ETSI_93:ETSI ETS 300 008 1993
SS7_PVAR_ETSI_96:ETSI ETS 300 008 1996
SS7_PVAR_ETSI_00:ETSI ETS 300 008 2000
SS7_PVAR_JTTC_94:JTTC JQ.700-Series 1994
.TE
.RE
.RS
.TP
.I popt
Contains a bit vector which contains a bitwise OR of the following flags.
When the resepective bit is set it indicates that the option is in effect.
.RE
.RS
.IP
.TS
tab(:);
lb 2 l.
.TH
SS7_POPT_MPLEV:Multiple prio/cong levels
SS7_POPT_PCR:Preventative cyclic retrans
SS7_POPT_HSL:High speed links
SS7_POPT_XSN:Extended sequence numbers
SS7_POPT_ALL:All options
.TE
.RE
.RE
.TP
\fIxxx\fR\fB_IOCGCONFIG\fR, \fIxxx\fR\fB_IOCSCONFIG\fR
Used to get or set the configuration variables associated with the protocol
for a specific LMI driver or module.  There are no common configuration
fields.  See the specific driver man page for details.
.TP
\fIxxx\fR\fB_IOCTCONFIG\fR, \fIxxx\fR\fB_IOCCCONFIG\fR
Used to test and commit a configuration using SNMP setup/commit semantics for
a specific LMI driver or module.  There are no common configuration fields.
See the specific driver man page for details.
.TP
\fIxxx\fR\fB_IOCGSTATEM\fR
Get state machine state variables, flags, timer-values and other protocol
state machine attributes for a particular protocol driver or module.  There
are no common state machine fields.  See the specific driver man page for
details.
.TP
\fIxxx\fR\fB_IOCCMRESET\fR
Perform a master reset on the state machine.  This returns the state machine
to Power-On conditions.  This control returns the same information as a
\fIxxx\fR\fB_IOCGSTATEM\fR call.  There are no common state machine fields.
See the specific driver man page for details.
.TP
\fIxxx\fR\fB_IOCGSTATSP\fR, \fIxxx\fR\fB_IOCSSTATSP\fR
Used to get or set the statistics collection interval for the collection of
statistics from the LMI driver or module.  The three common fields form a
common header for all statistics period information and are contains in the
\fBlmi_sta_t\fR structure as follows:
.sp
.RS
.nf
typedef struct lmi_sta {
    lmi_ulong   object_id;  /* object id for stats      */
    lmi_ulong   colperiod;  /* collection period        */
    lmi_ulong   timestamp;  /* timestamp end of period  */
} lmi_sta_t;
.fi
.TP
.I object_id
Contains the object id of the statistics.
.TP
.I colperiod
Contains the collection period which is being set for specified statistics.
The collection period is in jiffies (1/HZ seconds) and indicates the
aggregation period for specified statistics.
.TP
.I timestamp
Contains a timestamp (secconds since epoch) which indicates the time boundary
at which at least on collection period occured in the past.  This value can be
used to determine the system clock time at which the next collection interval
is to occur.
.RE
.TP
\fIxxx\fR\fB_IOCGSTATS\fR, \fIxxx\fR\fB_IOCSSTATS\fR
Gets or sets statistics which have been collected for the LMI driver or module
in the current (or just previous but not notified) collection interval.  The
common field of all statistics structures is the \fIheader\fR field which
contains the timestamp of the collection interval for which the current
statistics apply.
.TP
\fIxxx\fR\fB_IOCGNOTIFY\fR, \fIxxx\fR\fB_IOCSNOTIFY\fR, \fIxxx\fR\fB_IOCCNOTIFY\fR
Gets, sets or clears notifications from the LMI driver or module.  There are
no common notification fileds.  See the specific driver man page for more
details.

.\" .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"
.PP
.TS
tab(:);
l 1 li.
.TH
[Q702]:ITU-T Rec. Q.702 Signalling Data Link
[Q703]:ITU-T Rec. Q.703 Signalling Link
[Q704]:ITU-T Rec. Q.704 Message Transfer Part
[Q711]:ITU-T Rec. Q.711 Signalling Connection Control Part
[Q767]:ITU-T Rec. Q.767 ISDN User Part
[Q77?]:ITU-T Rec. Q.77? Transaction Capabilities Appl. Part
.TE

.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.