📄 ss7.7
字号:
'\" t.\" -*- nroff -*-.\".\" @(#) ss7.7,v 0.7.8.1 2001/12/11 13:16:08 brian Exp.\".\" =========================================================================.\".\" This manpage is Copyright (C) 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..\".\" =========================================================================.\".\" Last Modified 2001/12/11 13:16:08 by brian.\".\" ss7.7,v.\" Revision 0.7.8.1 2001/12/11 13:16:08 brian.\" Branched for new development..\".\" Revision 0.7.6.1 2001/02/18 12:11:15 brian.\" New working branch for next release..\".\" Revision 0.7.4.1 2001/02/18 09:44:48 brian.\" Added new working branch..\".\" Revision 0.7.2.5 2001/01/18 09:15:47 brian.\" More work on SLS..\".\" Revision 0.7.2.4 2001/01/17 00:29:10 brian.\" Working on man pages..\".\" Revision 0.7.2.3 2001/01/14 23:29:12 brian.\" Changed copyright notice..\".\" Revision 0.7.2.2 2001/01/14 11:07:53 brian.\" Changed headers back to GPL..\".\" Revision 0.7.2.1 2001/01/08 09:17:23 brian.\" Updated man pages somewhat..\".\" Revision 0.7 2000/11/29 02:09:56 brian.\" Added man pages for interfaces..\".\" Revision 0.7 2000/11/19 00:25:57 brian.\" Added man pages for streams drivers..\".\" =========================================================================.TH SS7 7 "2001/12/11 13:16:08" "SS7 STREAMS Man Page" "Linux STREAMS Programmer's Manual" .SH "NAME"ss7 \- Signalling System No. 7 for STREAMS.SH "SYNOPSIS".nf\fB#include <ss7/ss7.h>\fR\fIfd\fB = open("\fI/dev/module\fB", \fIflags\fB);\fIret\fB = ioctl(\fIfd\fB, \fIcmd\fB, ... /* \fIarg\fB */ );.fi.SH "DESCRIPTION"The \fIOpenSS7\fR STREAMS package for SS7 consists of a number of loadabledrivers and modules for Linux which are based on the LiS (Linux STREAMS)package. These drivers and modules implement the traditional SS7 stack aswell as providing some IETF SIGTRAN and other SS7 over IP components.\fIOpenSS7\fR protocol layers and levels are implemented as STREAMS drivers, modules andmultiplexors. The \fIOpenSS7\fR package provides an open specification of theinterface to each of these drivers, modules and multiplexors to permit themixing and matching of components in the SS7 stack as well as driver andmodule development at various levels.Also included in \fIOpenSS7\fR is an SS7 Conifguration Daemon.BR ss7d (8)which is responsible for configuration and intialization of the SS7 stack onthe target host. This daemon is normally run from system initializationscripts reads an SS7 configuration file and opens drivers, pushes modules andlinks the resulting streams under multiplexors to form the entire SS7 stackfor a particular configuration. The.BR ss7d (8)is also responsible forinterfacing with system level utilitities for collecting statistics andperforming maintenance and manual configuration of a running SS7 stack.This man page describes some of the features which are common to the\fIOpenSS7\fRstreasms drivers, modules and multiplexors which are defined in the headerfile \fI<ss7/ss7.h>\fR..SS Protocol Configuration.PPEach \fIOpenSS7\fR module defines a configuration structure (e.g.\fBsl_conf_t\fR) which contains the following two members:.RS.sp.nftypedef struct module_config { ss7_ulong pvar; /* protocol variant */ ss7_ulong popt; /* protocol options */ \fI...\fR \fI/* additional level specific options */\fR \fI...\fR} module_config_t;.fi.RE.TP.I pvarThe \fIOpenSS7\fR stack provides the capability to run many SS7 protocolvariants simultaneously. Therefore, all \fIOpenSS7\fR stack modules contain a\fIpvar\fR configuration parameter which contains the selected protocolvariant. Currently defined protocol variants are as follows:.IP.B SS7_PVAR_ITUT_88ITU-T Q.700 Series Blue Book.br.B SS7_PVAR_ITUT_93ITU-T Q.700 Series White Book.br.B SS7_PVAR_ITUT_96ITU-T Q.700 Series Grey Book.br.B SS7_PVAR_ITUT_00ITU-T Q.700 Series Black Book.br.B SS7_PVAR_ETSI_88ETSI ETS 300 Series (based on Blue Book).br.B SS7_PVAR_ETSI_93ETSI ETS 300 Series (based on White Book).br.B SS7_PVAR_ETSI_96ETSI ETS 300 Series (based on Grey Book).br.B SS7_PVAR_ETSI_00ETSI ETS 300 Series (based on Black Book).br.B SS7_PVAR_ANSI_88ANSI T1.111-1988.br.B SS7_PVAR_ANSI_92ANSI T1.111-1992.br.B SS7_PVAR_ANSI_96ANSI T1.111-1996.br.B SS7_PVAR_ANSI_00ANSI T1.111-2000.br.B SS7_PVAR_JTTC_94Japan TTC JQ.700 Series (based on Blue Book).IPThese protocol variant parameters are defined in such a way that they can betested against the following to find the major variant:.IP.B SS7_PVAR_ITUTITU-T Q.700 Series.br.B SS7_PVAR_ETSIETSI ETS 300 Series (based on ITU-T).br.B SS7_PVAR_ANSIANSI T1.111.br.B SS7_PVAR_JTTCTTC JQ.700 Series.TP.I poptIn addition, each \fIOpenSS7\fR module can enable or disable a number of major optionswhich are described in the standards specifications. Each \fIOpenSS7\fR module has a\fIpopt\fR configuration parameter which contains a bit vector of the enabledprotocol options for that module. For a definition of the options at eachlevel, see the man page for the specific interface..PPEach \fIOpenSS7\fR module recognizes protocol management primitives forconfiguration. These primitives are invoked by protocol layer management toconfigure or request configuratoin information from the layer serviceprovider. Any \fBM_DATA\fR block attached to the primitives contains a\fBmodule_conf_t\fR structure (see above) which represents the configurationparameters. Configuration request should normally be sent as \fBM_PCPROTO\fRmessages..TP.B MGMT_CONFIG_SETUPTest if the configuration parameters provided in the attached \fBM_DATA\fRblock are settable and correct. Any values set to \fI0xffffffff\fR in theconfiguration parameters should not be tested for change by the layer serviceprovider. When successful, this request also write locks the configurationuntil a successful \fBMGMT_CONFIG_COMMIT\fR is executed.This primitive contains only the \fImgmt_primitive\fR member..TP.B MGMT_CONFIG_COMMITCommits the changes of a previous successful \fBMGMT_CONFIG_TEST\fR operation.No configuration data is associated with this request and any attached\fBM_DATA\fR is ignored. When successful, this request also releases thewrite locks on the configuration.This primitive contains only the \fImgmt_primitive\fR member..TP.B MGMT_CONFIG_SETSets the configuration parameters to the values provided in the attached\fBM_DATA\fR block. This request will fail if the configuration is writelocked.This primitive contains only the \fImgmt_primitive\fR member..TP.B MGMT_CONFIG_GETGet the configuration parameters. Any attached \fBM_DATA\fR is ignored. Ifthe configuration is write locked, this request will only return the valueswhich have been setup for a commit and not necessarily the current values.This primitive contains only the \fImgmt_primitive\fR member..TP.B MGMT_OK_ACKUpon success, the layer service provider will return a \fBMGMT_OK_ACK\fR toconfirm a successful configuration request. The provider attached a\fBM_DATA\fR block which contains the \fImodule_conf_t\fR structure withthe results of the configuration request. This primitive uses the\fBmgmt_ok_ack_t\fR structure as follows:.RS.sp.nftypedef struct { mgmt_ulong mgmt_primitive; /* MGMT_OK_ACK */ mgmt_ulong mgmt_state; mgmt_ulong mgmt_correct_primitive;} mgmt_ok_ack_t;.fi.TP.I mgmt_stateContains the management state of the interface..TP.I mgmt_correct_primitiveContains the request primitive which this response is acknowledging..RE.TP.B MGMT_ERROR_ACKUpon failure, the layer service provider will return a \fBMGMT_ERROR_ACK\fR toreject the configuration request due to an error. The provider attaches a\fBM_DATA\fR block which contains a \fBmodule_conf_t\fR structure with\fI0xffffffff\fR in any values which are in error. This primitive uses the\fBmgmt_error_ack_t\fR structure as follows:.RS.sp.nftypedef struct { mgmt_ulong mgmt_primitive; /* MGMT_ERROR_ACK */ mgmt_ulong mgmt_state; mgmt_ulong mgmt_error_primitive; mgmt_ulong mgmt_errno; mgmt_ulong mgmt_reason;} mgmt_error_ack_t;.fi.TP.I mgmt_stateContains the management state of the interface..TP.I mgmt_error_primitiveContains the request primitive which this response is acknowledging..TP.I mgmt_errnoThe error number indicating which error occured..TP.I mgmt_reasonAn additional error reason code..RE.IPError numbers which are specific to a configuration request rejection are asfollows:.RS.TP.B MGMT_CONFLOCKEDThe request attempted to perform an illegal operation on a locked
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -