⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 sdti.7

📁 No7信令,我需要交换类似的代码, 请店长审核,谢谢了,急着交换,谢谢
💻 7
📖 第 1 页 / 共 2 页
字号:
'\" t.\" -*- nroff -*-.\".\" @(#) sdti.7,v 0.7.8.1 2001/12/11 13:16:08 brian Exp.\".\" =========================================================================.\".\" This manpage is Copyright (C) 1997, 1998, 1999, 2000 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..\".\" Modified 2001/12/11 13:16:08 by brian.\".\" =========================================================================.\".\" sdti.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:14  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.6  2001/01/16 03:19:47  brian.\" Updated man pages..\".\" Revision 0.7.2.5  2001/01/15 10:14:30  brian.\" Worked up LMI and SDTI man pages..\".\" =========================================================================.TH SDTI 7 "2001/12/11 13:16:08" "OpenSS7 Man Page" "OpenSS7 Programmer's Manual".SH "NAME"sdti \- Signalling System No. 7 Signalling Data Terminal (SDT) Interface.SH "SYNOPSIS".nf.B #include <ss7/sdti.h>.B #include <ss7/sdti_ioctl.h>.sp\fIfd\fB = open ("\fI/dev/sdt\fB", \fIflags\fB);\fIret\fB = ioctl(\fIfd\fB, \fIcmd\fB, ... /* \fIarg\fB */ );.fi.SH "DESCRIPTION"This man page describes the STREAMS interface which is used to configure andexchange data with an SS7 Signalling Data Terminal Interface (SDTI) for allSS7 devices conforming to the \fIOpenSS7\fR Signalling Data Terminal Interface(SDTI) specification..SS "LOCAL MANAGEMENT INTERFACE".PPSDTI drivers are normally linked using \fBstreamio\fR(2) \fBI_PUSH\fR ioctlcommands under a Signalling Link (SL) STREAMS module conforming to theSignalling Link Interface (SLI) specification \fBsli\fR(7) such as\fBsl\fR(8), by the SS7 Configuration Daemon \fBss7d\fR(8).  Yet, thisinterface is available for the purpose of ferry-clip conformance anddiagnostic testing of the SS7 Signalling Data Terminal..PPSDTI \fRStype 1\fR and \fIStyle 2\fR drviers may be configured to autopush the\fBsl\fR(8) module and appear as \fBsli\fR(7) drivers.  Not all SS7 driversneed be written to the SDT interface: drivers may be written to the\fBsli\fR(7), \fBslsi\fR(7) and even \fBmtpi\fR(7) interfaces..PPSDTI provides a local management interface which utilizes \fBM_PROTO\fR and\fBM_PCPROTO\fR messages which can be exchanged with the interface using\fBputmsg\fR(2) and \fBgetmsg\fR(2) system calls on the stream head once theinterface is opened.  The local management interfae controls local management(STREAMS configuration functions) which are normally used by the SS7Configuration Daemon \fBss7d\fR(8) on the driver interface before pushing an\fBsl\fR(8) module onto the stream head..PPThe Local Management Interface (LMI) is common to all \fIOpenSS7\fR driversand modules and is described in detail in \fBlmi\fR(7)..SS "DEVICE CONTROL INTERFACE".PPSDTI provides a device control interface which utilizes \fBioctl\fR(2)transparent calls or an \fBI_STR\fR ioctl under \fBstreamio\fR(2) from astream head to the driver.  The device control interface controls aspects ofthe SDT driver device which are outside the scope of the SS7 protocol.  Thesecontrols are normally issued by the SS7 Configuration Daemon \fBss7d\fR(8) onthe driver interface or multiplexor control channel before or after theprotocol stack has been assembled..PPThe device control interface (DEVI) is common to all \fIOpenSS7\fR drivers andmodules and is described in detail in \fBdevi\fR(7)..SS "PROTOCOL SERVICE INTERFACE".PPSDTI provides a protocol service interface which uses \fBM_DATA\fR,\fBM_PROTO\fR and \fBM_PCPROTO\fR STREAMS messages which can be exchanged with\fBwrite\fR(2), \fBread\fR(2), \fBputmsg\fR(2) or \fBgetmsg\fR(2) system callson the stream head, or which can be exchanged with the driver by upstreampushed or linked modules.  The protocol service interface exchanges SS7protocol service primitives between the Signalling Link (SL) and theSignalling Data Terminal (SDT), but may also be used for ferry-clipconformance testing or diagnostics..PPThe protocol service interface for SDTI is described in detail in section\fIPROTOCOL SERVICE INTERFACE\fR, below..SS "PROTOCOL MANAGEMENT INTERFACE".PPSDTI provides a protocol mangement interface which uses \fBM_CTL\fR messagesbetween modules or \fBM_IOCTL\fR messages from a stream head.  This interfaceuses the controls defined in the Local Management Interface (LMI) as detailedunder \fIINPUT OUTPUT CONTROL INTERFACE\fR in \fBlmi\fR(7).  The protocolmanagement interface provides protocol configuration, state inquiry,statistics and event management (SNMP functions).  This interface is normallyused by the SS7 Configuration Daemon \fBss7d\fR(8) on the stream after openingor during operation..PPThe protocol service interface for SDTI is described in detail in section\fIPROTOCOL MANAGEMENT INTERFACE\fR below..SH "PROTOCOL SERVICE INTERFACE".PPProtocol service interface commands are from the stream head to the SDT driverusing \fBputmsg\fR(2) and \fBgetmsg\fR(2) commands as follows:.RS 4.nf\fIfd\fB = open("\fI/dev/sdt\fB");\fIret\fB = putmsg(\fIfd\fB, \fIctlptr\fB, \fIdataptr\fB, \fIflags\fB);\fIret\fB = getmsg(\fIfd\fB, \fIctlptr\fB, \fIdataptr\fB, \fIflags\fB);.fi.RE.PPDownstream messages are sent from the stream head using \fBputmsg\fR(2);upstream messages are received at the stream head using \fBgetmsg\fR(2)..PP\fIflags\fR is either \fBRS_HIPRI\fR or not indicating a \fBM_PCPROTO\fRor an \fBM_PROTO\fR message respectively.  \fIctlptr\fR and \fIdataptr\fR arepointers to a \fBstrbuf\fR structure which contains the following members:.RS 4.nfstruct strbuf {    int     maxlen;     /* not used       */    int     len;        /* length of data */    void    *buf;       /* ptr to buffer  */};.fi.RE.PP\fIbuf\fR contains a pointer to a \fBSDT_primitive\fR union whichcontains one of the following primitives and structures:.SS Downstream Primitives.PPDownstream primitives are sent from the stream head to the protocol statemachines using \fBputmsg\fR(2) system calls as described above.Except where otherwise noted, \fIbuf\fR contains only the \fBsdt_primitive\fRfield which is set to the value of the primitive..TP.B SDT_DAEDT_TRANSMISSION_REQTransmit data.  This primitive must be sent with an accompanying \fBM_DATA\fRblock which is pointed to by the \fIdataptr\fR in a \fBputmsg\fR(2) or is thebuffer which is the argument of a \fBwrite\fR(2) on the stream file descriptor..TP.B SDT_DAEDT_START_REQStart the DAEDT state machine..TP.B SDT_DAEDR_START_REQStart the DAEDR state machine..TP.B SDT_AERM_START_REQStart the AERM state machine..TP.B SDT_AERM_STOP_REQStop the AERM state machine..TP.B SDT_AERM_SET_TI_TO_TIN_REQSet the AERM proving period to normal proving..TP.B SDT_AERM_SET_TI_TO_TIE_REQSet the AERM proving period to emergency proving..TP.B SDT_SUERM_START_REQStart the SUERM state machine..TP.B SDT_SUERM_STOP_REQStop the SUERM state machine..PP.SS Upstream PrimitivesUpstream primitives are collected at the stream head from the protocol statemachines using \fBgetmsg\fR(2) system calls as described above.  Except whereotherwise noted, \fIbuf\fR contains only the \fBsdt_primitive\fR field whichis set to the value of the primitive..TP.B SDT_RC_SIGNAL_UNIT_INDReceive data.  This primitive is received with an accompanying \fBM_DATA\fRblock which is pointed to by the \fIdataptr\fR in a \fBgetmsg\fR(2) or is thebuffer which is returned from a \fBread\fR(2) on the stream file descriptor..TP.B SDT_RC_CONGESTION_ACCEPT_INDCongestion accept indication..TP.B SDT_RC_CONGESTION_DISCARD_INDCongestion discard indication..TP.B SDT_RC_NO_CONGESTION_INDCongestion ceases indication..TP.B SDT_IAC_CORRECT_SU_INDCorrect Signal Unit received indication..TP.B SDT_IAC_ABORT_PROVING_INDProving aborted indication..TP.B SDT_LSC_LINK_FAILURE_INDLink failure indication..SH "PROTOCOL MANAGEMENT INTERFACE".PPProtocol management interface comands are from the stream head to the SDTdriver using \fBstreamio\fR(8) \fBI_STR\fR commands as follows:.RS 4.nf\fIfd\fB = open("\fI/dev/sdt\fB");\fIret\fB = ioctl(\fIfd\fB, \fRI_STR\fB, \fIarg\fB);.fi.RE.PPWhere \fIarg\fR is a pointer to a \fBstrioctl\fR structure which contains thefollowing members:.sp.RS 4.nfstruct strioctl {    int     ic_cmd;    int     ic_timout;    int     ic_len;    char    *ic_dp;};.fi.RE.PP\fIic_cmd\fR can be one of the protocol management interfacecommands described in the following subsections:.SS "Protocol Options".PPProtocol management controls which affect protocol options are used by localmanagement to set protocol variants and protocol options inherent to the SDTprovider..PPThe \fIic_cmd\fR contains one of the following options commands:.TP.B SDT_IOCGOPTIONSGets the protocol variant \fIpvar\fR and protocol options \fIpopt\fRassigned to the Signalling Data Terminal into the provided \fBlmi_option\fRstructure..TP.B SDT_IOCSOPTIONSSets the protocol variant \fIpvar\fR and protocol options \fIpopt\fR to theSignalling Data Terminal as provided in the \fBlmi_option\fR structure..PP\fIic_dp\fR points to a \fBlmi_option\fR structure whichrepresents the protocol variant and options parameters as follows:.PP.RS 4.nftypedef struct lmi_option {    lmi_ulong   pvar;    lmi_ulong   popt;} lmi_option_t;.fi.TP.I pvarSpecifies the protocol variant to be used for the Signalling Data Terminal andmay be one of the following values:.RE.RS 4.IP.TStab(:);lbw(16) 2 l..THSS7_PVAR_ITUT_88:ITU-T Q.703 1988 (Blue Book)SS7_PVAR_ITUT_93:ITU-T Q.703 1993 (Grey Book)SS7_PVAR_ITUT_96:ITU-T Q.703 1996 (White Book)SS7_PVAR_ITUT_00:ITU-T Q.703 2000 (? Book)SS7_PVAR_ANSI_88:ANSI T1.113-1988SS7_PVAR_ANSI_92:ANSI T1.113-1992SS7_PVAR_ANSI_96:ANSI T1.113-1996SS7_PVAR_ANSI_00:ANSI T1.113-2000SS7_PVAR_ETSI_88:ETSI 300 008-1 1988SS7_PVAR_ETSI_93:ETSI 300 008-1 1993SS7_PVAR_ETSI_96:ETSI 300 008-1 1996SS7_PVAR_ETSI_00:ETSI 300 008-1 2000SS7_PVAR_JTTC_94:JTTC JQ.703 1994.TE.RE.RS 4.TP.I poptSpecifies the protocol options to be used for the Signalling Data Terminal andmay be a bitwise OR of any of the following values:.RE.RS 4.IP.TStab(:);lbw(16) 2 l..THSS7_POPT_MPLEV:Multi Priority/Cong LevelsSS7_POPT_PCR:Preventative Cyclic RetransSS7_POPT_HSL:High Speed LinksSS7_POPT_XSN:Extended Sequence NumbersSS7_POPT_ALL:All options.TE.RE.SS "Protocol Configuration".PPProtocol management controls which affect protocol configuration are invokedby local management to configure or request configuration information from theSDT provider..PPThe \fIic_cmd\fR contains one of the following configuration commands:.TP.B SDT_IOCGCONFIGGets the protocol configuration of the Signalling Data Terminal into theprovided \fBsdt_config\fR structure..TP.B SDT_IOCSCONFIGSets the protocol configuration of the Signalling Data Terminal from theprovided \fBsdt_config\fR structure..TP.B SDT_IOCTCONFIGTests the protocol configuration as provided in the \fBsdt_config\fR structureagainst the Signalling Data Terminal for consistency and validity.  Also locks

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -