| Message Transfer Part (MTP) Level 3 DocumentationDescription: OpenSS7 Resources Library.A PDF version of this document is available here. Message Transfer Part Interface (MTPI)Message Transfer Part Interface (MTPI) SpecificationAbout This ManualThis is Edition 7.20141001, last updated 2014-10-25, of The Message Transfer Part Interface (MTPI) Specification, for Version 1.1 release 7.20141001 of the OpenSS7 package. PrefaceNoticeSoftware in this document and related software is released under the AGPL (see GNU Affero General Public License). Please note, however, that there are different licensing terms for some of the manual package and some of the documentation. Consult permission notices contained in the documentation of those components for more information. This document is released under the FDL (see GNU Free Documentation License) with no invariant sections, no front-cover texts and no back-cover texts. AbstractThis document is a Specification containing technical details concerning the implementation of the Message Transfer Part Interface (MTPI) for OpenSS7. It contains recommendations on software architecture as well as platform and system applicability of the Message Transfer Part Interface (MTPI). This document specifies a Message Transfer Part Interface (MTPI) Specification in support of the OpenSS7 Message Transfer Part (MTP) protocol stacks. It provides abstraction of the Message Transfer interface to these components as well as providing a basis for Message Transfer control for other Message Transfer protocols. PurposeThe purpose of this document is to provide technical documentation of the Message Transfer Part Interface (MTPI). This document is intended to be included with the OpenSS7 STREAMS software package released by OpenSS7 Corporation. It is intended to assist software developers, maintainers and users of the Message Transfer Part Interface (MTPI) with understanding the software architecture and technical interfaces that are made available in the software package. IntentIt is the intent of this document that it act as the primary source of information concerning the Message Transfer Part Interface (MTPI). This document is intended to provide information for writers of OpenSS7 Message Transfer Part Interface (MTPI) applications as well as writers of OpenSS7 Message Transfer Part Interface (MTPI) Users. AudienceThe audience for this document is software developers, maintainers and users and integrators of the Message Transfer Part Interface (MTPI). The target audience is developers and users of the OpenSS7 SS7 stack. Revision HistoryTake care that you are working with a current version of this documentation: you will not be notified of updates. To ensure that you are working with a current version, check the OpenSS7 Project website for a current version. A current version of this specification is normally distributed with the OpenSS7 package, openss7-1.1.7.20141001.1 Version ControlAlthough the author has attempted to ensure that the information in this document is complete and correct, neither the Author nor OpenSS7 Corporation will take any responsibility in it. OpenSS7 Corporation is making this documentation available as a reference point for the industry. While OpenSS7 Corporation believes that these interfaces are well defined in this release of the document, minor changes may be made prior to products conforming to the interfaces being made available. OpenSS7 Corporation reserves the right to revise this software and documentation for any reason, including but not limited to, conformity with standards promulgated by various agencies, utilization of advances in the state of the technical arts, or the reflection of changes in the design of any techniques, or procedures embodied, described, or referred to herein. OpenSS7 Corporation is under no obligation to provide any feature listed herein. $Log: mtpi.texi,v $ Revision 1.1.2.2 2011-02-07 02:21:40 brian - updated manuals Revision 1.1.2.1 2009-06-21 10:54:11 brian - added files to new distro ISO 9000 ComplianceOnly the TeX, texinfo, or roff source for this maual is controlled. An opaque (printed, postscript or portable document format) version of this manual is a UNCONTROLLED VERSION. DisclaimerOpenSS7 Corporation disclaims all warranties with regard to this documentation including all implied warranties of merchantability, fitness for a particular purpose, non-infrincement, or title; that the contents of the manual are suitable for any purpose, or that the implementation of such contents will not infringe on any third party patents, copyrights, trademarks or other rights. In no event shall OpenSS7 Corporation be liable for any direct, indirect, special or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action or contract, negligence or other tortious action, arising out of or in connection with any use of this documentation or the performance or implementation of the contents thereof. U.S. Government Restricted RightsIf you are licensing this Software on behalf of the U.S. Government ("Government"), the following provisions apply to you. If the Software is supplied by the Department of Defense ("DoD"), it is classified as "Commercial Computer Software" under paragraph 252.227-7014 of the DoD Supplement to the Federal Aquisition Regulations ("DFARS") (or any successor regulations) and the Government is acquiring only the license rights granded herein (the license rights customarily provided to non-Government users). If the Software is supplied to any unit or agency of the Government other than DoD, it is classified as "Restricted Computer Software" and the Government’s rights in the Software are defined in paragraph 52.227-19 of the Federal Acquisition Regulations ("FAR") (or any successor regulations) or, in the cases of NASA, in paragraph 18.52.227-86 of the NASA Supplerment to the FAR (or any successor regulations). AcknowledgementsThe OpenSS7 Project was funded in part by: Thanks to the subscribers to and sponsors of The OpenSS7 Project. Without their support, open software like this would not be possible. As with most open source projects, this project would not have been possible without the valiant efforts and productive software of the Free Software Foundation, the Linux Kernel Community, and the open source software movement at large. 1 IntroductionThis document specifies a STREAMS-based kernel-level instantiation of the ITU-T Message Transfer Part Interface (MTPI) definition. The Message Transfer Part Interface (MTPI) enables the user of a Message Transfer service to access and use any of a variety of conforming Message Transfer providers without specific knowledge of the provider’s protocol. The service interface is designed to support any network Message Transfer protocol and user Message Transfer protocol. This interface only specifies access to Message Transfer service providers, and does not address issues concerning Message Transfer management, protocol performance, and performance analysis tools. This specification assumes that the reader is familiar with ITU-T state machines and Message Transfer interfaces (e.g. Q.704, T1.111.4), and STREAMS. 1.1 Related Documentation
1.1.1 RoleThis document specifies an interface that supports the services provided by the Signalling System No. 7 (SS7) for ITU-T, ANSI and ETSI applications as described in ITU-T Recommendation Q.704, ANSI T1.111.4, ETSI ETS 300 008-1. These specifications are targeted for use by developers and testers of protocol modules that require Message Transfer service. 1.2 Definitions, Acronyms, Abbreviations
2 The MTP LayerThe MTP Layer provides the means to manage the association of MTP-Users into connections. It is responsible for the routing and management of data to and from SS7 network connections between MTP-user entities. 2.1 Model of the MTPIThe MTPI defines the services provided by the signalling link layer to the signalling link user at the boundary between the signalling link provider and the signalling link user entity. The interface consists of a set of primitives defined as STREAMS messages that provide access to the signalling link layer services, and are transferred between the MTP user entity and the MTP provider. These primitives are of two types; ones that originate from the MTP user, and other that originate from the MTP provider. The primitives that originate from the MTP user make requests to the MTP provider, or respond to an indication of an event of the MTP provider. The primitives that originate from the MTP provider are either confirmations of a request or are indications to the CCS user that an event has occurred. Figure 1 shows the model of the MTPI. Figure 1. Model of the MTPI
The MTPI allows the MTP provider to be configured with any MTP user
(such as ISUP) that also conforms to the MTPI. A call control layer user can also be a
user program that conforms to the MTPI and accesses the MTP provider via
2.2 MTPI ServicesThe features of the MTPI are defined in terms of the services provided by the MTP, and the individual primitives that may flow between the MTP-User and the MTP. The services supported by the MTPI are based on two distinct modes of communication, connectionless (CLMS) and connection oriented (COMS). Within these modes, the MTPI provides support for both sequenced and unsequenced message transfer. Also, the MTPI supports services for local mangement. 2.2.1 CLMSThe main features of the connectionless mode of communication are:
Connectionless mode communication has no separate phases. Each unit of data is transmitted from source to destination independently, appropriate addressing information is included with each unit of data. Although the units of data are transmitted independently from source to destination, MTP provides a high level of assurance of sequencing if sequenced service is requested. When unsequenced service is requested, there are no guarantees of proper sequence. Although MTP services are inherently unreliable, MTP provide a high level of assurance that messages are not lost. The connectionless service of MTP is suited to MTP User protocols such as the Signalling Connection Control Part (SCCP).2 2.2.2 COMSThe main features of the MTP connection oriented mode of communication are:
There are three phases to each instance of communication: Connection Establishment, Data Transfer; and Connection Termination. Units of data arrive at their destination in the same order as they departed their source when the sequenced delivery service is requested and the data is protected against duplication or loss of data within some specified quality of service. The connection oriented service of MTP is suited to MTP User protocols such as the Integrated Services Digital Network User Part (ISUP), [Q.764] Telephone User Part (TUP), [Q.724] and Bearer Indexed Call Control (BICC).3 2.2.3 Local ManagementThe MTPI specifications also defines a set of local management functions that apply to COMS and CLMS modes of communication. These services have local significance only. 2.2.4 Provider ManagementThe MTPI specification also defines a set of provider management functions that apply to the MTP service provider. These services have local and end-to-end significance. 2.3 MTP Service PrimitivesTable 1, Table 2, Table 3 and Table 4 summarize the MTPI service primitives by their state and service Table 1. MTPI Service Primitives for Local Management
Table 2. MTPI Service Primitives for Connectionless Mode Data Transfer
Table 3. MTPI Service Primitives for Connection Mode Data Transfer
Table 4. MTPI Service Primitives for MTP Management
3 MTPI Services DefinitionThis section describes the services of the MTPI primitives. Time-sequence diagrams that illustrate the sequence of primitives are included.4 The format of the primitives will be defined later in this document. 3.1 Local Management ServicesThe services defined in this section are outside the scope of international standards. These services apply to COMS and CLMS modes of communication. They are invoked for the initialization/de-initialization of a stream connected to the MTP. They are also used to manage options supported by the MTP and to report information on the supported parameter values. 3.1.1 Message Transfer Part Information Reporting ServiceThis service provides information on the options supported by the MTP provider.
The sequence of primitives for MTP information management is shown in Figure 2. Figure 2. Message Transfer Part Information Reporting Service
3.1.2 MTP Address ServiceThis service allows an MTP-User to determine the MTP address (MTP-SAPI or signalling point code and service indicator) that has been associated with a Stream. It permits the MTP-User to not necessarily retain this information locally, and allows the MTP-User to determine this information from the MTP provider at any time.
The sequence of primitives is shown in Figure 3. Figure 3. Message Transfer Part User Address Service
3.1.3 MTP User Bind ServiceThis service allows an MTP address (MTP-SAPI: signalling point code and service indicator) to be associated with a Stream. It allows the MTP-User to negotiate the number of connect indications that can remain unacknowledged for that MTP-User (a connect indication is considered unacknowledged while it is awaiting a corresponding connect response or release request from the MTP-User). This service also defines a mechanism that allows a Stream (bound to an MTP address of the MTP-User) to be reserved to handle incoming connections only. This Stream is referred to as the listener Stream.
The sequence of primitives is shown in Figure 4. Figure 4. Message Transfer Part User Bind Service
3.1.4 MTP User Unbind ServiceThis service allows the MTP-User to be unbound from an MTP address.
The sequence of primitives is shown in Figure 5. Figure 5. Message Transfer Part User Unbind Service
3.1.5 Receipt Acknowledgement Service
An example showing the sequence of primitives for successful receipt acknowledgement is depicted in Figure 6. Figure 6. Message Transfer Part Receipt Ackknowledgement Service
3.1.6 Options Management ServiceThis service allows the MTP-User to manage options parameter values associated wtih the MTP.
Figure 7 shows the sequence of primitives for MTP options management. Figure 7. Message Transfer Part Options Management Service
3.1.7 Error Acknowledgement Service
Figure 8 shows the sequence or primitives for the error management primitive. Figure 8. Message Transfer Part Error Acknowledgement Service
3.2 Connectionless ServicesThe CLMS allows for the transfer of MTP-User data in one or both directions simultaneously without establishing an association between MTP-User peers. A set of primitives are defined that carry user data and control information between the MTP-User and MTP entities. The primitives are modeled as requests initiated by the MTP-User and indications initiated by the MTP provider. Indications may be initiated by the MTP independently from requests by the MTP-User. The connectionless MTP service consists of one phase. 3.2.1 Data Transfer3.2.1.1 User Primitives for Data Transfer
3.2.1.2 Provider Primitives for Data Transfer
Figure 9 shows the sequence of primitives for the connectionless mode of data transfer. Figure 9. Message Transfer Part Data Transfer
3.2.2 Error Management3.2.2.1 Provider Primitives for Error Management
Figure 10 shows the sequence of primitives for the connectionless mode error management primitives. Figure 10. Message Transfer Part Error Management
3.3 Connection Oriented ServicesThis section describes the required MTP service primitives that define the CLMS interface. The queue model for CLMS is discused in more detail in ITU-T Q.704. [Q.704] For Q.704 specific conformance considerations, see Addendum 1. The queue model represents the operation of an MTP connection in the abstract by a pair of queues linking the two MTP addresses. There is one queue for each direction of signalling transfer. The ability of a user to add objects to a queue will be determined by the behavior of the user removing objects from that queue, and the state of the queue. The pair of queues is considered to be available for each potential association. Objects that are entered or removed from the queue are either as a result of interactions at the two MTP addresses, or as the result of MTP initiatives.
Table 5 shows the ordering relationship amoung the queue model objects. Table 5. Flow Control Relationships Between Queue Model Objects
3.3.1 Connection Establishment PhaseA pair of queues is associated with an MTP association between two MTP addresses
when the MTP receives an The MTP association procedure will fail if the MTP is unable to route to the remote MTP-User. 3.3.1.1 User primitives for Successful MTP Association Establishment
3.3.1.2 Provider primitives for Successful MTP Association Establishment
The sequence of primitives in a successful MTP association establishment is defined by the time sequence diagram as shown in Figure 11. Figure 11. Message Transfer Part Association Service
3.3.2 Data Transfer PhaseFlow control on the MTP association is done by management of queue capacity, by allowing objects of certain type to be inserted to the queues as shown in Table 5. 3.3.2.1 User primitives for MTP Data Transfer3.3.2.2 Provider primitives for MTP Data TransferFigure 12 shows the sequence of primitives for successful data transfer. The sequence of
primitives may remain incomplete if an Figure 12. Message Transfer Part Data Transfer
This sequence of primtives may remain incomplete if an 3.3.3 Error Management PrimitivesThe MTP error management service is used by the MTP to report detected loss of unrecoverable data. 3.3.3.1 Provider Primitives for Management
Figure 13 shows the sequence of primitives for the connection mode error management primitives.
The sequence of primitives may remain incomplete if an Figure 13. Message Transfer Part Error Management
3.3.4 Connection Termination PhaseThe MTP association release procedure is initialized by the insertion of a disconnect
object (associated with an 3.3.4.1 User Primitives for MTP Association TerminationThe sequence of primitives are shown in the time sequence diagram in Figure 14. Figure 14. Message Transfer Part Connection Termination
3.4 MTP Provider Management ServicesThis section describes the required MTP service primitives that define the MTP Provider Management interface. MTP Provider Management allows for the coordination of MTP management messages between MTP Provider peers. A set of primitives are defined that invoke management actions that are communicated from MTP to MTP entities. The primitives are modeled as requires initiated by the MTP management and indications initiated by the MTP. Indications may be initiated by the MTP independently from requests by the MTP management. The MTP Provider Management service consists of one phase. 3.4.1 Link ManagementThe MTP link management service allows MTP management to inhibit or uninhibit a link, linkset or combined linkset. 3.4.1.1 User Primitives for Link Inhibit Service3.4.1.2 Provider Primitives for Link Inhibit Service
Figure 15 shows the sequence of primitives for the MTP management link inihibit service, for a successful link inhibit. Figure 15. Message Transfer Part Successful Link Inhibit
Figure 16 shows the sequence of primitives for the MTP management link inihibit service, for an unsuccessful link inhibit. Figure 16. Message Transfer Part Unsuccessful Link Inhibit
3.4.1.3 User Primitives for Link Uninhibit Service
3.4.1.4 Provider Primitives for Link Uninhibit Service
Figure 17 shows the sequence of primitives for the MTP management link uninihibit service. Figure 17. Message Transfer Part Link Uninhibit Service
3.4.2 Route ManagementThe MTP route management service allows MTP management to allow or prohibit a route or routeset to a specific destination. 3.4.2.1 User Primitives for Route Allow Service
3.4.2.2 Provider Primitives for Route Allow Service
Figure 18 shows the sequence of primitives for the MTP management route allow service. Figure 18. Message Transfer Part Route Allow Service
3.4.2.3 User Primitives for Route Prohibit Service
3.4.2.4 Provider Primitives for Route Prohibit Service
Figure 19 shows the sequence of primitives for the MTP management route prohibit service. Figure 19. Message Transfer Part Route Prohibit Service
3.4.3 Layer ManagementThe MTP layer management service allows MTP management to request and receive event indications (alarms and 1st and deltas) and to request and receive stats indications (statistics and operational measurements) for specified intervals. 3.4.3.1 User Primitives for Event Indications
3.4.3.2 Provider Primitives for Event Indications
Figure 20 shows the sequence of primitives for the MTP management event service. Figure 20. Message Transfer Part Event Service
3.4.3.3 User Primitives for Statistics Indications
3.4.3.4 Provider Primitives for Statistics Indications
Figure 21 shows the sequence of primitives for the MTP management statistics service. Figure 21. Message Transfer Part Measurements Service
4 MTPI PrimitivesThis section describes the format and parameters of the MTPI primitives (Mapping MTPI Primitives, shows the mapping of MTPI primitives for the primitives defined in Q.701 [Q.701] and T1.111.1 [T1.111.1]). Also, it discusses the states the primitive is valid in, the resulting state, and the acknowledgement that the primitive expects. (The state/event tables for these primitives are shown in State/Event Tables. The precedence tables for the MTPI primitives are shown in Precedence Tables.) Rules for ITU-T conformance [Q.704] are described in addendum to this document in Addendum for MTP Conformance, rules for ANSI conformance [T1.111] are described in addendum Addendum for MTP Conformance, and rules for JITC conformance [JQ.704] are described in addendum Addendum for MTP Conformance. Table 6, Table 7 and ‘Table 8’ provide a summary of the MTP MTP primitives and their parameters. 4.1 Local Management PrimitivesThese primitives apply to CLMS and COMS. 4.1.1 Message Transfer Part Information RequestMTP_INFO_REQThis primitive requests the MTP to return the values of all supported protocol parameters (see under MTP_INFO_ACK), and also the current state of the MTP (as defined in Appendix B). This primitive does not affect the state of the MTP and does not appear in the state tables. FormatThe format of the message is one typedef struct MTP_info_req { mtp_ulong mtp_primitive; /* always MTP_INFO_REQ */ } MTP_info_req_t; ParametersValid StatesThis primitive is valid in any state where a local acknowledgement is not pending. New StateThe new state remains unchanged. AcknowledgementsThis primitive requires the MTP to generate one of the following acknowledgements upon receipt of the primitive:
4.1.2 Message Transfer Part Information AcknowledgementMTP_INFO_ACKThis primitive indicates to the MTP-User any relevant protocol-dependent parameters. It should be initiated in response to the MTP_INFO_REQ primitive described above. FormatThe format of this message is one typedef struct MTP_info_ack { mtp_ulong mtp_primitive; /* always MTP_INFO_ACK */ mtp_ulong mtp_msu_size; /* maximum MSU size for guaranteed delivery */ mtp_ulong mtp_addr_size; /* maximum address size */ mtp_ulong mtp_addr_length; /* address length */ mtp_ulong mtp_addr_offset; /* address offset */ mtp_ulong mtp_current_state; /* current interface state */ mtp_ulong mtp_serv_type; /* service type */ mtp_ulong mtp_version; /* version of interface */ } MTP_info_ack_t; #define M_COMS 1 /* Connection-mode MTP service supported */ #define M_CLMS 2 /* Connection-less MTP service supported */ ParametersThe above fields have the following meaning:
FlagsValid StatesThis primitive is valid in any state in response to an MTP_INFO_REQ primitive. New StateThe state remains the same. 4.1.3 Protocol Address RequestMTP_ADDR_REQThis primitive requests that the MTP return information concerning the MTP addresses upon which the MTP-User is bound or engaged in an association. The format of the message is one typedef struct MTP_addr_req { mtp_ulong mtp_primitive; /* always MTP_ADDR_REQ */ } MTP_addr_req_t; ParametersValid StatesThis primitive is valid in any state. New StateThe new state is MTPS_WACK_AREQ. Rules
AcknowledgementsThe MTP will generate on of the following acknowledgements upon receipt of the MTP_ADDR_REQ primitive:
4.1.4 Protocol Address AcknowledgementMTP_ADDR_ACKThis primitive acknowledges the corresponding request primitive and is used by the MTP to return information concerning the local and remote protocol addresses for the stream. The format of the message is one typedef struct MTP_addr_ack { mtp_ulong mtp_primitive; /* always MTP_ADDR_ACK */ mtp_ulong mtp_loc_length; /* length of local MTP address */ mtp_ulong mtp_loc_offset; /* offset of local MTP address */ mtp_ulong mtp_rem_length; /* length of remote MTP address */ mtp_ulong mtp_rem_offset; /* offset of remote MTP address */ } MTP_addr_ack_t; Parameters
Valid StateThis primitive is valid in state MTP_WACK_AREQ. New StateThe new state is the state previous to the MTP_ADDR_REQ. Rules
4.1.5 Bind Protocol Address RequestMTP_BIND_REQThis primitive requests that the MTP bind an MTP-User entity to an MTP address (MTP-SAPI). FormatThe format of the message is one typedef struct MTP_bind_req { mtp_ulong mtp_primitive; /* always MTP_BIND_REQ */ mtp_ulong mtp_addr_length; /* length of MTP address */ mtp_ulong mtp_addr_offset; /* offset of MTP address */ mtp_ulong mtp_bind_flags; /* bind flags */ } MTP_bind_req_t; Parameters
FlagsOnly one of the following flags may be set:
When all flags are clear, the COMS or CLMS service type will be chosen according to the Service Indicator in the specified address. Valid StatesThis primitive is valid in state MTPS_UNBND (see Appendix B). New StateThe new state is MTPS_WACK_BREQ. AcknowledgementsThe MTP will generate one of the following acknowledgements upon receipt of the MTP_BIND_REQ primitive:
4.1.6 Bind Protocol Address AcknowledgementMTP_BIND_ACKThis primitive indicates to the MTP-User that the specified MTP-User entity has been bound to the requested MTP address (MTP-SAPI). FormatThe format of the meessage is one typedef struct MTP_bind_ack { mtp_ulong mtp_primitive; /* always MTP_BIND_ACK */ mtp_ulong mtp_addr_length; /* length of bound MTP address */ mtp_ulong mtp_addr_offset; /* offset of bound MTP address */ } MTP_bind_ack_t; Parameters
RulesThe following rules apply to the binding of the specified MTP address to the stream:
If the above rules result in an error condition, then the MTP must issue an MTP_ERROR_ACK primitive to the MTP-User specifying the error as defined in the description of the MTP_BIND_REQ primitive. Valid StatesThis primitive is in response to an MTP_BIND_REQ primitive and is valid in the state MTPS_WACK_BREQ. New StateThe new state is MTPS_IDLE. 4.1.7 Unbind Protocol Address RequestMTP_UNBIND_REQThis primitive requests that the MTP unbind the MTP-User entity that was previously bound to the MTP address (MTP-SAPI). FormatThe format of the message is one typedef struct MTP_unbind_req { mtp_ulong mtp_primitive; /* always MTP_UNBIND_REQ */ } MTP_unbind_req_t; ParametersValid StatesThis primitive is valid in the MTPS_IDLE state. New StateThe new state is MTPS_WACK_UREQ. AcknowledgementsThis primitive requires the MTP to generate the following acknolwedgements upon receipt of the primitive:
4.1.8 Message Transfer Part Options Management RequestMTP_OPTMGMT_REQThis primitive allows the MTP-User to manage the MTP parameter values associated with the stream. FormatThe format of the message is one typedef struct MTP_optmgmt_req { mtp_ulong mtp_primitive; /* always MTP_OPTMGMT_REQ */ mtp_ulong mtp_opt_length; /* length of options */ mtp_ulong mtp_opt_offset; /* offset of options */ mtp_ulong mtp_mgmt_flags; /* management flags */ } MTP_optmgmt_req_t; #define MTP_DEFAULT 0UL #define MTP_CHECK 1UL #define MTP_NEGOTIATE 2UL #define MTP_CURRENT 3UL Parameters
Flags
Only one of the above flags can be set. Valid StatesThis primitive is valid in the MTPS_IDLE state. New StateThe new state is MTPS_WACK_OPTREQ. AcknowledgementsThe MTP_OPTMGMT_REQ primitive requires the MTP to generate one of the following acknowledgements upon receipt of the primitive:
4.1.9 Error AcknowledgementMTP_ERROR_ACKThis primitive indicates to the MTP-User that a non-fatal error has occured in the last MTP-User or MTP-Management originated primitive. This may only be initiated as an acknowledgement for those primitives that require one. It also indicates to the user that no action was taken on the primitive that caused the error. FormatThe format of the mssage is one typedef struct MTP_error_ack { mtp_ulong mtp_primitive; /* always MTP_ERROR_ACK */ mtp_ulong mtp_error_primitive; /* primitive in error */ mtp_ulong mtp_mtpi_error; /* MTP interface error */ mtp_ulong mtp_unix_error; /* UNIX error */ } MTP_error_ack_t; Parameters
Valid Error CodesThe following error codes are allowed to be returned:
Valid StatesThis primitive is valid in all states that have a pending acknowledgment or confirmation. New StateThe new state is the same as the one from which the acknowledged request or response was issued. 4.1.10 Successful Receipt AcknowledgementsMTP_OK_ACKThe primitive indicates to the MTP-User that the previous MTP-User or management originated primitive was received successfully by the MTP. It does not indicate to the MTP-User any MTP protocol action taken due to the issuance of the last primitive. The MTP_OK_ACK primitive may only be initiated as an acknowledgement for those user or management originated primitives that have no other means of confirmation. FormatThe format of the mssage is one typedef struct MTP_ok_ack { mtp_ulong mtp_primitive; /* always MTP_OK_ACK */ mtp_ulong mtp_correct_prim; /* correct primitive */ } MTP_ok_ack_t; Parameters
Valid StatesThis primitive is issued in states MTPS_WACK_UREQ, MTPS_WACK_OPTREQ, MTPS_WACK_CREQ and MTPS_WACK_DREQ. New StateThe resulting state depends on the current state (see Appendix B, Tables B-7 and B-8.). 4.2 Connection Mode and Connectionless PrimitivesThis section describes the format of the COMS primitives and the rules associated with these
primitives. The default values of the options parameters associated with an MTP
association may be selected via the 4.2.1 Signalling Relation Establishment PhaseThe following MTP service primitives pertain to the establishment of an association between local and remote MTP-SAPs, provided the MTP users exist, and are known to the MTP. 4.2.1.1 Message Transfer Part Connection RequestMTP_CONN_REQThis primitive requests that the MTP form an association to the specified destination. FormatThe format of the message is one typedef struct MTP_conn_req { mtp_ulong mtp_primitive; /* always MTP_CONN_REQ */ mtp_ulong mtp_addr_length; /* length of MTP address to connect */ mtp_ulong mtp_addr_offset; /* offset of MTP address to connect */ mtp_ulong mtp_conn_flags; /* connect flags */ } MTP_conn_req_t; Parameters
FlagsRulesThe following rules apply to the establishment of associations between the specified addresses:
The following rules apply to the MTP addresses (MTP-SAPIs):
Valid StatesThis primitive is valid in state MTPS_IDLE. New StateThe new state is MTPS_DATA_XFER. AcknowledgementsThe following acknolwedgements are valid for this primitive:
4.2.2 Signalling Relation Data Transfer PhaseThe data transfer service primitive provide for an exchange of MTP-User data, known as MSDUs, in either direction or in both directions simultaneously on a signalling relation. The MTP service preserves the sequence of MSDUs that have the same Signalling Link Selection (SLS) value specified in the MTP_TRANSFER_REQ. MSDUs are self-contained messages with implicit boundaries. The following MTP service primtiives pertain to the Data Transfer phase of a signalling relation. 4.2.2.1 Message Transfer Part Transfer RequestMTP_TRANSFER_REQThis user-originated primitive indicates to the MTP that this message contains MTP-User data. It allows the transfer of MTP-User data between MTP-Users, without modification by the MTP provider. The MTP-User must send an integral number of octets of data greater than zero. In a case
where the size of the MSDU exceeds the MIDU (as specified by the size of the FormatThe format of the message is one or more
Guidelines for the use of The following guidelines must be followed with respect to the use of the
The format of the typedef struct MTP_transfer_req { mtp_ulong mtp_primitive; /* always MTP_TRANSFER_REQ */ mtp_ulong mtp_dest_length; /* length of destination address */ mtp_ulong mtp_dest_offset; /* offset of destination address */ mtp_ulong mtp_mp; /* message priority */ mtp_ulong mtp_sls; /* signalling link selection */ } MTP_transfer_req_t; Parameters
RulesIf the signalling relation is associated with a single destination address (MTP-SAPI),
Valid StatesThis primitive is valid in state MTP_IDLE for connectionless streams and in state MTP_DATA_XFER for pseudo-connection oriented streams. New StateThe new state is unchanged. AcknowledgementsThis primitive does not require any acknowledgements, although it may generate a fatal error. This
is indicated to the MTP-User via a
4.2.2.2 Message Transfer Part Transfer IndicationMTP_TRANSFER_INDFormatThe format of this message is one typedef struct MTP_transfer_ind { mtp_ulong mtp_primitive; /* always MTP_TRANSFER_IND */ mtp_ulong mtp_srce_length; /* length of source address */ mtp_ulong mtp_srce_offset; /* offset of source address */ mtp_ulong mtp_mp; /* message priority */ mtp_ulong mtp_sls; /* signalling link selection */ } MTP_transfer_ind_t; Parameters
RulesValid StatesThis primitive is valid in state MTP_DATA_XFER. New StateThe new state is unchanged. 4.2.2.3 Message Transfer Part Status IndicationMTP_STATUS_INDFormatThe format of the message is one typedef struct MTP_status_ind { mtp_ulong mtp_primitive; /* always MTP_STATUS_IND */ mtp_ulong mtp_addr_length; /* length of affected MTP address */ mtp_ulong mtp_addr_offset; /* offset of affected MTP address */ mtp_ulong mtp_type; /* type */ mtp_ulong mtp_status; /* status */ } MTP_status_ind_t; /* Type for MTP_STATUS_IND */ #define MTP_STATUS_TYPE_CONG 0x00 /* congestion */ #define MTP_STATUS_TYPE_UPU 0x01 /* user part unavailability */ /* Status for MTP_STATUS_IND, with MTP_STATUS_TYPE_UPU */ #define MTP_STATUS_UPU_UNKNOWN 0x01 /* unknown */ #define MTP_STATUS_UPU_UNEQUIPPED 0x02 /* unequipped remote user. */ #define MTP_STATUS_UPU_INACCESSIBLE 0x03 /* inaccessible remote user. */ /* Status for MTP_STATUS_IND, with MTP_STATUS_TYPE_CONG */ #define MTP_STATUS_CONGESTION_LEVEL0 0x00 /* congestion level 0 */ #define MTP_STATUS_CONGESTION_LEVEL1 0x01 /* congestion level 1 */ #define MTP_STATUS_CONGESTION_LEVEL2 0x02 /* congestion level 2 */ #define MTP_STATUS_CONGESTION_LEVEL3 0x03 /* congestion level 3 */ #define MTP_STATUS_CONGESTION 0x04 /* congestion */ Parameters
Type and Status
MTP user part status is protocol variant and provider specific. See the Addendum for more information. RulesValid StatesThis primitive is valid in state MTPS_DATA_XFER. New StateThe new state is unchanged (MTPS_DATA_XFER). 4.2.2.4 Message Transfer Part Pause IndicationMTP_PAUSE_INDThis primitive indicates to the MTP-User that the indicated remote MTP-entity (signalling point) is temporarily inaccessible. This implies the inaccessibility of remote MTP-User at the affected signalling point. FormatThe format of the message is one typedef struct MTP_pause_ind { mtp_ulong mtp_primitive; /* always MTP_PAUSE_IND */ mtp_ulong mtp_addr_length; /* length of affected MTP address */ mtp_ulong mtp_addr_offset; /* offset of affected MTP address */ } MTP_pause_ind_t; Parameters
RulesValid StatesThis primitive is valid in state MTPS_DATA_XFER. New StateThe new state is unchanged (MTPS_DATA_XFER). 4.2.2.5 Message Transfer Part Resume IndicationMTP_RESUME_INDThis primitive indicates to the MTP-User that a previously inaccesible remote MTP-entity (signalling point) is now accessible. This does not imply the accessibility of the remote MTP-User at the affected signalling point: the MTP-User is responsible for sending protocol messages to the remote MTP-User to test its accessibility. FormatThe format of the message is one typedef struct MTP_resume_ind { mtp_ulong mtp_primitive; /* always MTP_RESUME_IND */ mtp_ulong mtp_addr_length; /* length of affected MTP address */ mtp_ulong mtp_addr_offset; /* offset of affected MTP address */ } MTP_resume_ind_t; Parameters
RulesValid StatesThis primitive is valid in state MTPS_DATA_XFER. New StateThe new state is unchanged (MTPS_DATA_XFER). 4.2.2.6 Message Transfer Part Restart Complete IndicationMTP_RESTART_COMPLETE_INDFormatThe format of the message is one typedef struct MTP_restart_complete_ind { mtp_ulong mtp_primitive; /* always MTP_RESTART_COMPLETE_IND */ } MTP_restart_complete_ind_t; ParametersRulesValid StatesThis primitive is valid in state MTPS_DATA_XFER. New StateThe new state is unchanged (MTPS_DATA_XFER). 4.2.3 Signalling Relation Release Phase4.2.3.1 Message Transfer Part Disconnect RequestMTP_DISCON_REQFormatThe format of the message is one typedef struct MTP_discon_req { mtp_ulong mtp_primitive; /* always MTP_DISCON_REQ */ } MTP_discon_req_t; ParametersRulesValid StatesThis primitive is valid in state MTPS_DATA_XFER. New StateThe new state is MTPS_WACK_DREQ. Acknowledgements4.3 MTP Provider Management Primitives4.3.1 Link Management Primitives4.3.1.1 Link Inhibit RequestMTP_INHIBIT_REQFormatThe format of the message is one ParametersValid StatesNew StateAcknowledgements4.3.1.2 Link Inhibit IndicationMTP_INHIBIT_INDFormatThe format of the message is one ParametersRulesValid StatesNew State4.3.1.3 Link Inhibit ConfirmationMTP_INHIBIT_CONFormatThe format of the message is one ParametersRulesValid StatesNew State4.3.1.4 Link Uninhibit RequestMTP_UNINHIBIT_REQFormatThe format of the message is one ParametersValid StatesNew StateAcknowledgements4.3.1.5 Link Uninhibit IndicationMTP_UNINHIBIT_INDFormatThe format of the message is one ParametersRulesValid StatesNew State4.3.1.6 Link Uninhibit ConfirmationMTP_UNINHIBIT_CONFormatThe format of the message is one ParametersRulesValid StatesNew State4.3.2 Route Management Primitives4.3.2.1 Route Prohibit RequestMTP_PROHIBIT_REQFormatThe format of the message is one ParametersValid StatesNew StateAcknowledgements4.3.2.2 Route Prohibit IndicationMTP_PROHIBIT_INDFormatThe format of the message is one ParametersRulesValid StatesNew State4.3.2.3 Route Prohibit ConfirmationMTP_PROHIBIT_CONFormatThe format of the message is one ParametersRulesValid StatesNew State4.3.2.4 Route Allow RequestMTP_ALLOW_REQFormatThe format of the message is one ParametersValid StatesNew StateAcknowledgements4.3.2.5 Route Allow IndicationMTP_ALLOW_INDFormatThe format of the message is one ParametersRulesValid StatesNew State4.3.2.6 Route Allow ConfirmationMTP_ALLOW_CONFormatThe format of the message is one ParametersRulesValid StatesNew State4.3.3 Layer Management Primitives4.3.3.1 Layer Event IndicationMTP_EVENT_INDFormatThe format of the message is one ParametersRulesValid StatesNew State4.3.3.2 Statistics IndicationMTP_STATS_INDFormatThe format of the message is one ParametersRulesValid StatesNew State5 Diagnostics RequirementsTwo error handling facilities should be provided to the MTP user: one to handle non-fatal errors, and the other to handle fatal errors. 5.1 Non-Fatal Error Handling FacilityThese are errors that do not change the state of the MTP service interface as seen by the
MTP service user, and provide the user the option of reissuing the MTP service
primitive with the corrected options specification. The non-fatal error handling is provided only
to those primitive that require acknowledgements, and uses the 5.2 Fatal Error Handling FacilityThese errors are issued by the MTP provider when it detects errors that are not
correctable by the MTP user, or if it is unable to report a correctible error to the
MTP user. Fatal errors are indicated via the STREAMS message type These errors are issued by the MTP when it detects errors that are not correctable by the
MTP service user, or if it is unable to report a correctable error to the MTP
service user. Fatal errors are indicated via the STREAMS message type 6 MTPI Input-Output Controls6.1 MTP Protocol Object OptionsArgument Formattypedef struct mtp_option { ulong type; /* object type */ ulong id; /* object id */ /* followed by object-specific protocol options structure */ } mtp_option_t; Fields
6.1.1 Get MTP Protocol Object OptionsMTP_IOCGOPTIONGet the protocol options associated with the identified object. 6.1.2 Set MTP Protocol Object OptionsMTP_IOCSOPTIONSet the protocol options associated with the identified object. 6.1.3 Signalling Link Optionstypedef struct mtp_opt_conf_sl { /* signalling link timers */ ulong t1; /* timer t1 value */ ulong t2; /* timer t2 value */ ulong t3; /* timer t3 value */ ulong t4; /* timer t4 value */ ulong t5; /* timer t5 value */ ulong t12; /* timer t12 value */ ulong t13; /* timer t13 value */ ulong t14; /* timer t14 value */ ulong t17; /* timer t17 value */ ulong t19a; /* timer t19a value */ ulong t20a; /* timer t20a value */ ulong t21a; /* timer t21a value */ ulong t22; /* timer t22 value */ ulong t23; /* timer t23 value */ ulong t24; /* timer t24 value */ ulong t31a; /* timer t31a value */ ulong t32a; /* timer t32a value */ ulong t33a; /* timer t33a value */ ulong t34a; /* timer t34a value */ ulong t1t; /* timer t1t value */ ulong t2t; /* timer t2t value */ ulong t1s; /* timer t1s value */ } mtp_opt_conf_sl_t; 6.1.4 Link Set Optionstypedef struct mtp_opt_conf_lk { /* signalling link timers */ ulong t1; /* timer t1 value */ ulong t2; /* timer t2 value */ ulong t3; /* timer t3 value */ ulong t4; /* timer t4 value */ ulong t5; /* timer t5 value */ ulong t12; /* timer t12 value */ ulong t13; /* timer t13 value */ ulong t14; /* timer t14 value */ ulong t17; /* timer t17 value */ ulong t19a; /* timer t19a value */ ulong t20a; /* timer t20a value */ ulong t21a; /* timer t21a value */ ulong t22; /* timer t22 value */ ulong t23; /* timer t23 value */ ulong t24; /* timer t24 value */ ulong t31a; /* timer t31a value */ ulong t32a; /* timer t32a value */ ulong t33a; /* timer t33a value */ ulong t34a; /* timer t34a value */ ulong t1t; /* timer t1t value */ ulong t2t; /* timer t2t value */ ulong t1s; /* timer t1s value */ /* link timers */ ulong t7; /* timer t7 value */ } mtp_opt_conf_lk_t; 6.1.5 Combined Link Set Optionstypedef struct mtp_opt_conf_ls { /* signalling link timers */ ulong t1; /* timer t1 value */ ulong t2; /* timer t2 value */ ulong t3; /* timer t3 value */ ulong t4; /* timer t4 value */ ulong t5; /* timer t5 value */ ulong t12; /* timer t12 value */ ulong t13; /* timer t13 value */ ulong t14; /* timer t14 value */ ulong t17; /* timer t17 value */ ulong t19a; /* timer t19a value */ ulong t20a; /* timer t20a value */ ulong t21a; /* timer t21a value */ ulong t22; /* timer t22 value */ ulong t23; /* timer t23 value */ ulong t24; /* timer t24 value */ ulong t31a; /* timer t31a value */ ulong t32a; /* timer t32a value */ ulong t33a; /* timer t33a value */ ulong t34a; /* timer t34a value */ ulong t1t; /* timer t1t value */ ulong t2t; /* timer t2t value */ ulong t1s; /* timer t1s value */ /* link timers */ ulong t7; /* timer t7 value */ } mtp_opt_conf_ls_t; 6.1.6 Route Optionstypedef struct mtp_opt_conf_rt { /* route timers */ ulong t6; /* timer t6 value */ ulong t10; /* timer t10 value */ } mtp_opt_conf_rt_t; 6.1.7 Route List Optionstypedef struct mtp_opt_conf_rl { /* route timers */ ulong t6; /* timer t6 value */ ulong t10; /* timer t10 value */ } mtp_opt_conf_rl_t; 6.1.8 Route Set Optionstypedef struct mtp_opt_conf_rs { /* route timers */ ulong t6; /* timer t6 value */ ulong t10; /* timer t10 value */ /* route set timers */ ulong t8; /* timer t8 value */ ulong t11; /* timer t11 value */ ulong t15; /* timer t15 value */ ulong t16; /* timer t16 value */ ulong t18a; /* timer t18a value */ } mtp_opt_conf_rs_t; 6.1.9 Signalling Point Optionstypedef struct mtp_opt_conf_sp { /* signalling link timers */ ulong t1; /* timer t1 value */ ulong t2; /* timer t2 value */ ulong t3; /* timer t3 value */ ulong t4; /* timer t4 value */ ulong t5; /* timer t5 value */ ulong t12; /* timer t12 value */ ulong t13; /* timer t13 value */ ulong t14; /* timer t14 value */ ulong t17; /* timer t17 value */ ulong t19a; /* timer t19a value */ ulong t20a; /* timer t20a value */ ulong t21a; /* timer t21a value */ ulong t22; /* timer t22 value */ ulong t23; /* timer t23 value */ ulong t24; /* timer t24 value */ ulong t31a; /* timer t31a value */ ulong t32a; /* timer t32a value */ ulong t33a; /* timer t33a value */ ulong t34a; /* timer t34a value */ ulong t1t; /* timer t1t value */ ulong t2t; /* timer t2t value */ ulong t1s; /* timer t1s value */ /* link timers */ ulong t7; /* timer t7 value */ /* route timers */ ulong t6; /* timer t6 value */ ulong t10; /* timer t10 value */ /* route set timers */ ulong t8; /* timer t8 value */ ulong t11; /* timer t11 value */ ulong t15; /* timer t15 value */ ulong t16; /* timer t16 value */ ulong t18a; /* timer t18a value */ /* signalling point timers */ ulong t1r; /* timer t1r value */ ulong t18; /* timer t18 value */ ulong t19; /* timer t19 value */ ulong t20; /* timer t20 value */ ulong t21; /* timer t21 value */ ulong t22a; /* timer t22a value */ ulong t23a; /* timer t23a value */ ulong t24a; /* timer t24a value */ ulong t25a; /* timer t25a value */ ulong t26a; /* timer t26a value */ ulong t27a; /* timer t27a value */ ulong t28a; /* timer t28a value */ ulong t29a; /* timer t29a value */ ulong t30a; /* timer t30a value */ } mtp_opt_conf_sp_t; 6.1.10 Network Appearance Optionstypedef struct mtp_opt_conf_na { /* signalling link timers */ ulong t1; /* timer t1 value */ ulong t2; /* timer t2 value */ ulong t3; /* timer t3 value */ ulong t4; /* timer t4 value */ ulong t5; /* timer t5 value */ ulong t12; /* timer t12 value */ ulong t13; /* timer t13 value */ ulong t14; /* timer t14 value */ ulong t17; /* timer t17 value */ ulong t19a; /* timer t19a value */ ulong t20a; /* timer t20a value */ ulong t21a; /* timer t21a value */ ulong t22; /* timer t22 value */ ulong t23; /* timer t23 value */ ulong t24; /* timer t24 value */ ulong t31a; /* timer t31a value */ ulong t32a; /* timer t32a value */ ulong t33a; /* timer t33a value */ ulong t34a; /* timer t34a value */ ulong t1t; /* timer t1t value */ ulong t2t; /* timer t2t value */ ulong t1s; /* timer t1s value */ /* link timers */ ulong t7; /* timer t7 value */ /* route timers */ ulong t6; /* timer t6 value */ ulong t10; /* timer t10 value */ /* route set timers */ ulong t8; /* timer t8 value */ ulong t11; /* timer t11 value */ ulong t15; /* timer t15 value */ ulong t16; /* timer t16 value */ ulong t18a; /* timer t18a value */ /* signalling point timers */ ulong t1r; /* timer t1r value */ ulong t18; /* timer t18 value */ ulong t19; /* timer t19 value */ ulong t20; /* timer t20 value */ ulong t21; /* timer t21 value */ ulong t22a; /* timer t22a value */ ulong t23a; /* timer t23a value */ ulong t24a; /* timer t24a value */ ulong t25a; /* timer t25a value */ ulong t26a; /* timer t26a value */ ulong t27a; /* timer t27a value */ ulong t28a; /* timer t28a value */ ulong t29a; /* timer t29a value */ ulong t30a; /* timer t30a value */ } mtp_opt_conf_na_t; 6.1.11 Default Optionstypedef struct mtp_opt_conf_df { } mtp_opt_conf_df_t; 6.2 MTP Protocol Object ConfigurationArgument Formattypedef struct mtp_config { ulong type; /* object type */ ulong id; /* object id */ ulong cmd; /* configuration command */ /* followed by object-specific configuration structure */ } mtp_config_t; #define MTP_GET 0 /* get configuration */ #define MTP_ADD 1 /* add configuration */ #define MTP_CHA 2 /* cha configuration */ #define MTP_DEL 3 /* del configuration */
6.2.1 Get MTP Protocol Object ConfigurationMTP_IOCGCONFIG6.2.2 Set MTP Protocol Object ConfigurationMTP_IOCSCONFIG6.2.3 Test MTP Protocol Object ConfigurationMTP_IOCTCONFIG6.2.4 Commit MTP Protocol Object ConfigurationMTP_IOCCCONFIG6.2.5 Signalling Link Configurationtypedef struct mtp_conf_sl { ulong muxid; /* lower multiplexor id */ ulong lkid; /* link set id */ ulong slc; /* signalling link code in lk */ } mtp_conf_sl_t; 6.2.6 Link Set Configurationtypedef struct mtp_conf_lk { ulong lsid; /* combined link set id */ ulong rsid; /* routeset of adjacent signalling point */ ulong ni; /* network indicator for link set */ ulong slot; /* slot of SLS for this link set */ } mtp_conf_lk_t; 6.2.7 Combined Link Set Configurationtypedef struct mtp_conf_ls { ulong spid; /* signalling point id */ ulong sls_mask; /* mask of bits selecting link set */ } mtp_conf_ls_t; 6.2.8 Route Configurationtypedef struct mtp_conf_rt { ulong rlid; /* route list id */ ulong lkid; /* link id */ ulong slot; /* slot of SLS for this route */ } mtp_conf_rt_t; 6.2.9 Route List Configurationtypedef struct mtp_conf_rl { ulong rsid; /* route set id */ ulong lsid; /* combined link set id */ ulong cost; /* cost in routeset */ } mtp_conf_rl_t; 6.2.10 Route Set Configurationtypedef struct mtp_conf_rs { ulong spid; /* signalling point id */ ulong dest; /* destination point code */ ulong flags; /* options flags */ } mtp_conf_rs_t; 6.2.11 Signalling Point Configurationtypedef struct mtp_conf_sp { ulong naid; /* network appearance id */ ulong pc; /* point code */ ulong users; /* mask of equipped users */ ulong flags; /* options flags */ } mtp_conf_sp_t; 6.2.12 Network Appearance Configurationtypedef struct mtp_conf_na { lmi_option_t options; /* protocol options */ struct { ulong member; /* PC member mask */ ulong cluster; /* PC cluster mask */ ulong network; /* PC network mask */ } mask; ulong sls_bits; /* bits in SLS */ } mtp_conf_na_t; /* additional MTP protocol options */ #define SS7_POPT_TFR 0x00010000 /* old broadcast method - no responsive */ #define SS7_POPT_TFRB 0x00020000 /* new broadcast method - no regulation */ #define SS7_POPT_TFRR 0x00040000 /* new responsive method - regulated */ #define SS7_POPT_MCSTA 0x00080000 /* multiple congestion states */ 6.2.13 Default Configurationtypedef struct mtp_conf_df { } mtp_conf_df_t; 6.3 MTP Protocol Object State MachineArgument Formattypedef struct mtp_statem { ulong type; /* object type */ ulong id; /* object id */ ulong flags; /* object flags */ ulong state; /* object state */ /* followed by object-specific state structure */ } mtp_statem_t; 6.3.1 Signalling Link Statetypedef struct mtp_timers_sl { ulong t1; /* timer t1 */ ulong t2; /* timer t2 */ ulong t3; /* timer t3 */ ulong t4; /* timer t4 */ ulong t5; /* timer t5 */ ulong t12; /* timer t12 */ ulong t13; /* timer t13 */ ulong t14; /* timer t14 */ ulong t17; /* timer t17 */ ulong t19a; /* timer t19a */ ulong t20a; /* timer t20a */ ulong t21a; /* timer t21a */ ulong t22; /* timer t22 */ ulong t23; /* timer t23 */ ulong t24; /* timer t24 */ ulong t31a; /* timer t31a */ ulong t32a; /* timer t32a */ ulong t33a; /* timer t33a */ ulong t34a; /* timer t34a */ ulong t1t; /* timer t1t */ ulong t2t; /* timer t2t */ ulong t1s; /* timer t1s */ } mtp_timers_sl_t; typedef struct mtp_statem_sl { struct mtp_timers_sl timers; } mtp_statem_sl_t; #define SLS_OUT_OF_SERVICE 0 /* out of service */ #define SLS_PROC_OUTG 1 /* processor outage */ #define SLS_IN_SERVICE 2 /* in service */ #define SLS_WACK_COO 3 /* waiting COA/ECA in response to COO */ #define SLS_WACK_ECO 4 /* waiting COA/ECA in response to ECO */ #define SLS_WCON_RET 5 /* waiting for retrieval confrimation */ #define SLS_WIND_CLRB 6 /* waiting for clear buffers indication */ #define SLS_WIND_BSNT 7 /* waiting for BSNT indication */ #define SLS_WIND_INSI 8 /* waiting for in service indication */ #define SLS_WACK_SLTM 9 /* waiting SLTA in response to 1st SLTM */ #define SL_RESTORED (MTP_ALLOWED) /* Sig link Activated/Restored/Resumed */ #define SL_DANGER (MTP_DANGER) /* Sig link Danger of congestion (overloaded) */ #define SL_CONGESTED (MTP_CONGESTED) /* Sig link Congested (link congestion) */ #define SL_UNUSABLE (MTP_RESTRICTED) /* Sig link Unusable (Local Processor Outage) */ #define SL_RETRIEVAL (MTP_RESTART) /* Sig link Retrieving */ #define SL_FAILED (MTP_PROHIBITED) /* Sig link Failed */ #define SL_INHIBITED (MTP_INHIBITED) /* Sig link Inhibited (Management inhibited) */ #define SL_BLOCKED (MTP_BLOCKED) /* Sig link Blocked (Processor Outage) */ #define SL_INACTIVE (MTP_INACTIVE) /* Sig link Inactive (Out of Service) */ #define SL_NODANGER (MTP_NODANGER) /* Sig link Out of Danger (transient state) */ #define SL_UNCONGESTED (MTP_UNCONGESTED) /* Sig link Uncongested (transient state) */ #define SL_UPDATED (MTP_RESTARTED) /* Sig link Buffer Update Complete (transient state) */ #define SL_UNINHIBITED (MTP_UNINHIBITED) /* Sig link Uninhibited (transient state) */ #define SL_UNBLOCKED (MTP_UNBLOCKED) /* Sig link Unblocked (transient state) */ #define SL_ACTIVE (MTP_ACTIVE) /* Sig link Active (Link in service) */ #define SLF_TRAFFIC (MTPF_TRAFFIC) /* Sig link has sent traffic */ #define SLF_COO_RECV (MTPF_COO_RECV) /* Sig link has received a COO */ #define SLF_ECO_RECV (MTPF_ECO_RECV) /* Sig link has received a ECO */ #define SLF_WACK_SLTM (MTPF_WACK_SLTM) /* Sig link waiting for response to 1st SLTM */ #define SLF_WACK_SLTM2 (MTPF_WACK_SLTM2) /* Sig link waiting for response to 2nd SLTM */ #define SLF_WACK_SSLTM (MTPF_WACK_SSLTM) /* Sig link waiting for response to 1st SSLTM */ #define SLF_WACK_SSLTM2 (MTPF_WACK_SSLTM2) /* Sig link waiting for response to 2nd SSLTM */ #define SLF_RESTORED (MTPF_ALLOWED) /* Sig link Activated/Restored */ #define SLF_DANGER (MTPF_DANGER) /* Sig link Danger of congestion (overloaded) */ #define SLF_CONGESTED (MTPF_CONGESTED) /* Sig link Congested (link congestion) */ #define SLF_UNUSABLE (MTPF_RESTRICTED) /* Sig link Unusable (Local Processor Outage) */ #define SLF_RETRIEVAL (MTPF_RESTART) /* Sig link Retrieving */ #define SLF_FAILED (MTPF_PROHIBITED) /* Sig link Failed */ #define SLF_INHIBITED (MTPF_INHIBITED) /* Sig link Inhibited (Management inhibited) */ #define SLF_BLOCKED (MTPF_BLOCKED) /* Sig link Blocked (Processor Outage) */ #define SLF_INACTIVE (MTPF_INACTIVE) /* Sig link Inactive (Out of Service) */ #define SLF_LOSC_PROC_A (MTPF_LOSC_PROC_A) /* Sig link uses link oscillation procedure A */ #define SLF_LOSC_PROC_B (MTPF_LOSC_PROC_B) /* Sig link uses link oscillation procedure B */ 6.3.2 Link Set Statetypedef struct mtp_timers_lk { ulong t7; /* timer t7 */ } mtp_timers_lk_t; typedef struct mtp_statem_lk { struct mtp_timers_lk timers; } mtp_statem_lk_t; #define LK_ALLOWED (MTP_ALLOWED) /* Link Allowed */ #define LK_DANGER (MTP_DANGER) /* Link Danger of congestion (primary or secondary) */ #define LK_CONGESTED (MTP_CONGESTED) /* Link Congested (Link Set congestion, primary or secondary ) */ #define LK_RESTRICTED (MTP_RESTRICTED) /* Link Restricted (Route Failure or received TFR) */ #define LK_RESTART (MTP_RESTART) /* Link Restarting */ #define LK_PROHIBITED (MTP_PROHIBITED) /* Link Prohibited (Received TFP) */ #define LK_INHIBITED (MTP_INHIBITED) /* Link Inhibited (Management inhibited) */ #define LK_BLOCKED (MTP_BLOCKED) /* Link Blocked (Local Link Set failure) */ #define LK_INACTIVE (MTP_INACTIVE) /* Link Inactive (Link out of service) */ #define LK_NODANGER (MTP_NODANGER) /* Link Out of Danger (transient state) */ #define LK_UNCONGESTED (MTP_UNCONGESTED) /* Link Uncongested (transient state) */ #define LK_RESTARTED (MTP_RESTARTED) /* Link Restarted */ #define LK_UNINHIBITED (MTP_UNINHIBITED) /* Link Uninhibited (transient state) */ #define LK_UNBLOCKED (MTP_UNBLOCKED) /* Link Unblocked (transient state) */ #define LK_ACTIVE (MTP_ACTIVE) /* Link Active (Link in service) */ 6.3.3 Combined Link Set Statetypedef struct mtp_timers_ls { } mtp_timers_ls_t; typedef struct mtp_statem_ls { struct mtp_timers_ls timers; } mtp_statem_ls_t; #define LS_ALLOWED (MTP_ALLOWED) /* Linkset Allowed */ #define LS_DANGER (MTP_DANGER) /* Linkset Danger of congestion (primary or secondary) */ #define LS_CONGESTED (MTP_CONGESTED) /* Linkset Congested (Link Set congestion, primary or secondary ) */ #define LS_RESTRICTED (MTP_RESTRICTED) /* Linkset Restricted (Route Failure or received TFR) */ #define LS_RESTART (MTP_RESTART) /* Linkset Restarting */ #define LS_PROHIBITED (MTP_PROHIBITED) /* Linkset Prohibited (Received TFP) */ #define LS_INHIBITED (MTP_INHIBITED) /* Linkset Inhibited (Management inhibited) */ #define LS_BLOCKED (MTP_BLOCKED) /* Linkset Blocked (Local Link Set failure) */ #define LS_INACTIVE (MTP_INACTIVE) /* Linkset Inactive (Link out of service) */ #define LS_NODANGER (MTP_NODANGER) /* Linkset Out of Danger (transient state) */ #define LS_UNCONGESTED (MTP_UNCONGESTED) /* Linkset Uncongested (transient state) */ #define LS_RESTARTED (MTP_RESTARTED) /* Linkset Restarted */ #define LS_UNINHIBITED (MTP_UNINHIBITED) /* Linkset Uninhibited (transient state) */ #define LS_UNBLOCKED (MTP_UNBLOCKED) /* Linkset Unblocked (transient state) */ #define LS_ACTIVE (MTP_ACTIVE) /* Linkset Active (Link in service) */ 6.3.4 Route Statetypedef struct mtp_timers_rt { ulong t6; /* timer t6 */ ulong t10; /* timer t10 */ } mtp_timers_rt_t; typedef struct mtp_statem_rt { struct mtp_timers_rt timers; } mtp_statem_rt_t; #define RT_ALLOWED (MTP_ALLOWED) /* Route Allowed */ #define RT_DANGER (MTP_DANGER) /* Route Danger of congestion (primary or secondary) */ #define RT_CONGESTED (MTP_CONGESTED) /* Route Congested (Link Set congestion, primary or secondary ) */ #define RT_RESTRICTED (MTP_RESTRICTED) /* Route Restricted (Route Failure or received TFR) */ #define RT_RESTART (MTP_RESTART) /* Route Restarting */ #define RT_PROHIBITED (MTP_PROHIBITED) /* Route Prohibited (Received TFP) */ #define RT_INHIBITED (MTP_INHIBITED) /* Route Inhibited (Management inhibited) */ #define RT_BLOCKED (MTP_BLOCKED) /* Route Blocked (Local Link Set failure) */ #define RT_INACTIVE (MTP_INACTIVE) /* Route Inactive (Link out of service) */ #define RT_NODANGER (MTP_NODANGER) /* Route Out of Danger (transient state) */ #define RT_UNCONGESTED (MTP_UNCONGESTED) /* Route Uncongested (transient state) */ #define RT_RESTARTED (MTP_RESTARTED) /* Route Restarted */ #define RT_UNINHIBITED (MTP_UNINHIBITED) /* Route Uninhibited (transient state) */ #define RT_UNBLOCKED (MTP_UNBLOCKED) /* Route Unblocked (transient state) */ #define RT_ACTIVE (MTP_ACTIVE) /* Route Active (Link in service) */ //#define RT_RESTART_PHASE_1 (MTP_RESTART_PHASE_1) /* Route Restarting Phase 1 */ //#define RT_RESTART_PHASE_2 (MTP_RESTART_PHASE_2) /* Route Restarting Phase 2 */ #define RTF_ALLOWED (MTPF_ALLOWED) /* Route is allowed */ #define RTF_DANGER (MTPF_DANGER) /* Route is in danger of congestion */ #define RTF_CONGESTED (MTPF_CONGESTED) /* Route is congested */ #define RTF_RESTRICTED (MTPF_RESTRICTED) /* Route is restricted */ #define RTF_RESTART (MTPF_RESTART) /* Route is restarting */ #define RTF_PROHIBITED (MTPF_PROHIBITED) /* Route is prohibited */ #define RTF_INHIBITED (MTPF_INHIBITED) /* Route is inhibited */ #define RTF_BLOCKED (MTPF_BLOCKED) /* Route is blocked */ #define RTF_INACTIVE (MTPF_INACTIVE) /* Route is inactive */ 6.3.5 Route List Statetypedef struct mtp_timers_rl { } mtp_timers_rl_t; typedef struct mtp_statem_rl { struct mtp_timers_rl timers; } mtp_statem_rl_t; //#define RL_ALLOWED (MTP_ALLOWED) /* Routelist Allowed */ //#define RL_DANGER (MTP_DANGER) /* Routelist Danger of congestion (primary or secondary) */ //#define RL_CONGESTED (MTP_CONGESTED) /* Routelist Congested (Link Set cong, primary or secondary) */ #define RL_RESTRICTED (MTP_RESTRICTED) /* Routelist Restricted (Route Failure or received TFR) */ #define RL_RESTART (MTP_RESTART) /* Routelist Restarting */ //#define RL_PROHIBITED (MTP_PROHIBITED) /* Routelist Prohibited (Received TFP) */ //#define RL_INHIBITED (MTP_INHIBITED) /* Routelist Inhibited (Management inhibited) */ //#define RL_BLOCKED (MTP_BLOCKED) /* Routelist Blocked (Local Link Set failure) */ //#define RL_INACTIVE (MTP_INACTIVE) /* Routelist Inactive (Link out of service) */ //#define RL_NODANGER (MTP_NODANGER) /* Routelist Out of Danger (transient state) */ //#define RL_UNCONGESTED (MTP_UNCONGESTED) /* Routelist Uncongested (transient state) */ //#define RL_RESTARTED (MTP_RESTARTED) /* Routelist Restarted */ //#define RL_UNINHIBITED (MTP_UNINHIBITED) /* Routelist Uninhibited (transient state) */ //#define RL_UNBLOCKED (MTP_UNBLOCKED) /* Routelist Unblocked (transient state) */ //#define RL_ACTIVE (MTP_ACTIVE) /* Routelist Active (Link in service) */ //#define RL_RESTART_PHASE_1 (MTP_RESTART_PHASE_1) /* Routelist Restarting Phase 1 */ //#define RL_RESTART_PHASE_2 (MTP_RESTART_PHASE_2) /* Routelist Restarting Phase 2 */ 6.3.6 Route Set Statetypedef struct mtp_timers_rs { ulong t8; /* timer t8 */ ulong t11; /* timer t11 */ ulong t15; /* timer t15 */ ulong t16; /* timer t16 */ ulong t18a; /* timer t18a */ } mtp_timers_rs_t; typedef struct mtp_statem_rs { struct mtp_timers_rs timers; } mtp_statem_rs_t; #define RS_ALLOWED (MTP_ALLOWED) /* Routeset Allowed */ #define RS_DANGER (MTP_DANGER) /* Routeset Danger of congestion (primary or secondary) */ #define RS_CONGESTED (MTP_CONGESTED) /* Routeset Congested (Link Set cong, primary or secondary) */ #define RS_RESTRICTED (MTP_RESTRICTED) /* Routeset Restricted (Route Failure or received TFR) */ #define RS_RESTART (MTP_RESTART) /* Routeset Restarting */ #define RS_PROHIBITED (MTP_PROHIBITED) /* Routeset Prohibited (Received TFP) */ #define RS_INHIBITED (MTP_INHIBITED) /* Routeset Inhibited (Management inhibited) */ #define RS_BLOCKED (MTP_BLOCKED) /* Routeset Blocked (Local Link Set failure) */ #define RS_INACTIVE (MTP_INACTIVE) /* Routeset Inactive (Link out of service) */ #define RS_NODANGER (MTP_NODANGER) /* Routeset Out of Danger (transient state) */ #define RS_UNCONGESTED (MTP_UNCONGESTED) /* Routeset Uncongested (transient state) */ #define RS_RESTARTED (MTP_RESTARTED) /* Routeset Restarted */ #define RS_UNINHIBITED (MTP_UNINHIBITED) /* Routeset Uninhibited (transient state) */ #define RS_UNBLOCKED (MTP_UNBLOCKED) /* Routeset Unblocked (transient state) */ #define RS_ACTIVE (MTP_ACTIVE) /* Routeset Active (Link in service) */ #define RS_RESTART_PHASE_1 (MTP_RESTART_PHASE_1) /* Routeset Restarting Phase 1 */ #define RS_RESTART_PHASE_2 (MTP_RESTART_PHASE_2) /* Routeset Restarting Phase 2 */ #define RSF_ALLOWED (MTPF_ALLOWED) /* Routeset is allowed */ #define RSF_DANGER (MTPF_DANGER) /* Routeset is in danger of congestion */ #define RSF_CONGESTED (MTPF_CONGESTED) /* Routeset is congested */ #define RSF_RESTRICTED (MTPF_RESTRICTED) /* Routeset is restricted */ #define RSF_RESTART (MTPF_RESTART) /* Routeset is restarting */ #define RSF_PROHIBITED (MTPF_PROHIBITED) /* Routeset is prohibited */ #define RSF_INHIBITED (MTPF_INHIBITED) /* Routeset is inhibited */ #define RSF_BLOCKED (MTPF_BLOCKED) /* Routeset is blocked */ #define RSF_INACTIVE (MTPF_INACTIVE) /* Routeset is inactive */ #define RSF_TFR_PENDING (MTPF_TFR_PENDING) /* Routeset has TFR pending */ #define RSF_CLUSTER (MTPF_CLUSTER) /* Routeset is cluster route */ #define RSF_XFER_FUNC (MTPF_XFER_FUNC) /* Routeset has transfer function */ #define RSF_ADJACENT (MTPF_ADJACENT) /* Routeset is adjacent */ 6.3.7 Signalling Point Statetypedef struct mtp_timers_sp { ulong t1r; /* timer t1r */ ulong t18; /* timer t18 */ ulong t19; /* timer t19 */ ulong t20; /* timer t20 */ ulong t21; /* timer t21 */ ulong t22a; /* timer t22a */ ulong t23a; /* timer t23a */ ulong t24a; /* timer t24a */ ulong t25a; /* timer t25a */ ulong t26a; /* timer t26a */ ulong t27a; /* timer t27a */ ulong t28a; /* timer t28a */ ulong t29a; /* timer t29a */ ulong t30a; /* timer t30a */ } mtp_timers_sp_t; typedef struct mtp_statem_sp { struct mtp_timers_sp timers; } mtp_statem_sp_t; #define SP_ALLOWED (MTP_ALLOWED) /* Sig Point Allowed */ #define SP_DANGER (MTP_DANGER) /* Sig Point Danger of congestion (primary or secondary) */ #define SP_CONGESTED (MTP_CONGESTED) /* Sig Point Congested (Link Set cong, primary or secondary ) */ #define SP_RESTRICTED (MTP_RESTRICTED) /* Sig Point Restricted (Route Failure or received TFR) */ #define SP_RESTART (MTP_RESTART) /* Sig Point Restarting */ #define SP_PROHIBITED (MTP_PROHIBITED) /* Sig Point Prohibited (Received TFP) */ #define SP_INHIBITED (MTP_INHIBITED) /* Sig Point Inhibited (Management inhibited) */ #define SP_BLOCKED (MTP_BLOCKED) /* Sig Point Blocked (Local Link Set failure) */ #define SP_INACTIVE (MTP_INACTIVE) /* Sig Point Inactive (Link out of service) */ #define SP_NODANGER (MTP_NODANGER) /* Sig Point Out of Danger (transient state) */ #define SP_UNCONGESTED (MTP_UNCONGESTED) /* Sig Point Uncongested (transient state) */ #define SP_RESTARTED (MTP_RESTARTED) /* Sig Point Restarted */ #define SP_UNINHIBITED (MTP_UNINHIBITED) /* Sig Point Uninhibited (transient state) */ #define SP_UNBLOCKED (MTP_UNBLOCKED) /* Sig Point Unblocked (transient state) */ #define SP_ACTIVE (MTP_ACTIVE) /* Sig Point Active (Link in service) */ #define SP_RESTART_PHASE_1 (MTP_RESTART_PHASE_1) /* Sig Point Restarting Phase 1 */ #define SP_RESTART_PHASE_2 (MTP_RESTART_PHASE_2) /* Sig Point Restarting Phase 2 */ #define SPF_RESTART (MTPF_RESTART) /* Sig Point restarting */ #define SPF_CLUSTER (MTPF_CLUSTER) /* Sig Point is cluster route */ #define SPF_XFER_FUNC (MTPF_XFER_FUNC) /* Sig Point has transfer function */ #define SPF_SECURITY (MTPF_SECURITY) /* Sig Point has additional security procedures */ #define SPF_LOSC_PROC_A (MTPF_LOSC_PROC_A) /* Sig Point uses link oscillation procedure A */ #define SPF_LOSC_PROC_B (MTPF_LOSC_PROC_B) /* Sig Point uses link oscillation procedure B */ #define SPF_RESTART_PHASE_1 (MTPF_RESTART_PHASE_1) /* Sig Point restarting */ #define SPF_RESTART_PHASE_2 (MTPF_RESTART_PHASE_2) /* Sig Point restarting */ 6.3.8 Network Appearance Statetypedef struct mtp_timers_na { } mtp_timers_na_t; typedef struct mtp_statem_na { struct mtp_timers_na timers; } mtp_statem_na_t; 6.3.9 Default Statetypedef struct mtp_timers_df { } mtp_timers_df_t; typedef struct mtp_statem_df { struct mtp_timers_df timers; } mtp_statem_df_t; 6.3.10 Get MTP Protocol Object State MachineMTP_IOCGSTATEM6.3.11 Reset MTP Protocol Object State MachineMTP_IOCCMRESET6.4 MTP Protocol Object StatisticsArgument Formattypedef struct mtp_stats { ulong type; /* object type */ ulong id; /* object id */ ulong header; /* object stats header */ /* followed by object-specific statistics structure */ } mtp_stats_t; 6.4.1 Get MTP Protocol Object Statistics PeriodsMTP_IOCGSTATSP6.4.2 Set MTP Protocol Object Statistics PeriodsMTP_IOCSSTATSP6.4.3 Get MTP Protocol Object StatisticsMTP_IOCGSTATS6.4.4 Set MTP Protocol Object StatisticsMTP_IOCSSTATS6.5 MTP Protoocl Object NotificationsArgument Formattypedef struct mtp_notify { ulong type; /* object type */ ulong id; /* object id */ /* followed by object-specific notification structure */ } mtp_notify_t; 6.5.1 Get MTP Protocol Object NotificationsMTP_IOCGNOTIFY6.5.2 Set MTP Protocol Object NotificationsMTP_IOCSNOTIFY6.5.3 Clear MTP Protocol Object NotificationsMTP_IOCCNOTIFY6.6 MTP Protocol Object ManagementArgument Formattypedef struct mtp_mgmt { ulong type; /* object type */ ulong id; /* object id */ ulong cmd; /* mgmt command */ } mtp_mgmt_t; #define MTP_MGMT_ALLOW 0 #define MTP_MGMT_RESTRICT 1 #define MTP_MGMT_PROHIBIT 2 #define MTP_MGMT_ACTIVATE 3 #define MTP_MGMT_DEACTIVATE 4 #define MTP_MGMT_BLOCK 5 #define MTP_MGMT_UNBLOCK 6 #define MTP_MGMT_INHIBIT 7 #define MTP_MGMT_UNINHIBIT 8 #define MTP_MGMT_CONGEST 9 #define MTP_MGMT_UNCONGEST 10 #define MTP_MGMT_DANGER 11 #define MTP_MGMT_NODANGER 12 #define MTP_MGMT_RESTART 13 #define MTP_MGMT_RESTARTED 14 6.6.1 Manage MTP Protocol ObjectMTP_IOCCMGMT6.7 MTP Provider Pass-Along ControlArgument Formattypedef struct mtp_pass { ulong muxid; /* mux index of lower SL structure to pass message to */ ulong type; /* type of message block */ ulong band; /* band of mesage block */ ulong ctl_length; /* length of cntl part */ ulong dat_length; /* length of data part */ /* followed by cntl and data part of message to pass to signalling link */ } mtp_pass_t; MTP_IOCCPASS7 MTPI Management Information BaseAddendum for MTP ConformanceAddendum for ITU-T Q.704 ConformanceThis addendum describes the formats and rules that are specific to ETSI EN 300 008-1 V3.2.2. The addendum must be used along with the generic MTPI as defined in the main document, and the EN 300 008-1 conformance defined in Addendum 2, when implementing an MTP that will be configured with the EN 300 008-1 Message Transfer Part. Primitives and Rules for ETSI EN 300 008-1 V3.2.2 ConformanceThe following are the additional rules that apply to the MTPI primitives for ETSI EN 300 008-1 V3.2.2 compatibility. Local Management PrimitivesParametersFlagsRulesConnection Mode PrimitivesParametersFlagsRulesConnectionless PrimitivesParametersFlagsRulesAddendum for ANSI T1.111.4 ConformanceAddendum for ETSI ETS 300 008-1 ConformanceAddendum for ITU-T Q.2210 ConformanceAppendix A Mapping MTPI PrimitivesA.1 Mapping MTPI Primitives to Q.701Table A-1 shows the mapping of the MTPI primitives to the MTP definition primitives listed in ITU-T Recommendation Q.704. The mapping of MTPI primitives to Q.701 primitives is shown in Table 6. For the most part, this mapping is a one to one mapping of service primitives, with the exception of Connect Request and Disconnect Request. In Q.701 there is no concept of an association between MTP-entities. In OpenSS7
MTPI, the Table 6. Mapping of MTPI primitives to Q.701 Primitives
A.2 Mapping MTPI Primitives to ANSI T1.111.1The mapping of MTPI primitives to T1.111.1 primitives is shown in Table 7. For the most part, this mapping is a one to one mapping of service primitives, with the exception of Connect Request and Disconnect Request. In T1.111.1 there is no concept of an association between MTP-entities. In OpenSS7
MTPI, the Table 7. Mapping of MTPI primitives to T1.111.1 Primitives
A.3 Mapping MTPI Primitives to ETSI ETS 300 008-2The mapping of MTPI primitives to ETS 300 008-2 primitives is shown in ‘Table 8’. For the most part, this mapping is a one to one mapping of service primitives, with the exception of Connect Request and Disconnect Request. In ETS 300 008-2 there is no concept of an association between MTP-entities. In OpenSS7
MTPI, the Appendix B State/Event TablesAppendix C Precedence TablesAppendix D MTPI Header Files#ifndef __SS7_MTPI_H__ #define __SS7_MTPI_H__ #define MTP_VERSION_1 0x10 #define MTP_CURRENT_VERSION MTP_VERSION_1 typedef int32_t mtp_long; typedef u_int32_t mtp_ulong; typedef u_int16_t mtp_ushort; typedef u_int8_t mtp_uchar; #define MTP_BIND_REQ 1+120 /* Bind to an MTP-SAP */ #define MTP_UNBIND_REQ 2+120 /* Unbind from an MTP-SAP */ #define MTP_CONN_REQ 3+120 /* Connect to a remote MTP-SAP */ #define MTP_DISCON_REQ 4+120 /* Disconnect from a remote MTP-SAP */ #define MTP_ADDR_REQ 5+120 /* Address service */ #define MTP_INFO_REQ 6+120 /* Information service */ #define MTP_OPTMGMT_REQ 7+120 /* Options management service */ #define MTP_STATUS_REQ 8+120 /* MTP status request */ #define MTP_TRANSFER_REQ 9+120 /* MTP data transfer request */ #define MTP_OK_ACK 10+120 /* Positive acknowledgement */ #define MTP_ERROR_ACK 11+120 /* Negative acknowledgement */ #define MTP_BIND_ACK 12+120 /* Bind acknowledgement */ #define MTP_ADDR_ACK 13+120 /* Address acknowledgement */ #define MTP_INFO_ACK 14+120 /* Information acknowledgement */ #define MTP_OPTMGMT_ACK 15+120 /* Options management acknowledgement */ #define MTP_TRANSFER_IND 16+120 /* MTP data transfer indication */ #define MTP_PAUSE_IND 17+120 /* MTP pause (stop) indication */ #define MTP_RESUME_IND 18+120 /* MTP resume (start) indication */ #define MTP_STATUS_IND 19+120 /* MTP status indication */ #define MTP_RESTART_BEGINS_IND 20+120 /* MTP restart begins (impl. dep.) */ #define MTP_RESTART_COMPLETE_IND 21+120 /* MTP restart complete (impl. dep.) */ /* * Interface States */ #define MTPS_UNBND 0UL #define MTPS_WACK_BREQ 1UL #define MTPS_IDLE 2UL #define MTPS_WACK_CREQ 3UL #define MTPS_WCON_CREQ 4UL #define MTPS_CONNECTED 5UL #define MTPS_WACK_UREQ 6UL #define MTPS_WACK_DREQ6 7UL #define MTPS_WACK_DREQ9 8UL #define MTPS_WACK_OPTREQ 9UL #define MTPS_WREQ_ORDREL 10UL #define MTPS_WIND_ORDREL 11UL #define MTPS_WRES_CIND 12UL #define MTPS_UNUSABLE 0xffffffffUL #ifndef __HAVE_MTP_ADDR #ifndef AF_MTP #define AF_MTP 0 #endif typedef struct mtp_addr { unsigned int family __attribute__ ((packed)); unsigned short int ni __attribute__ ((packed)); /* network identifier */ unsigned short int si __attribute__ ((packed)); /* service indicator */ unsigned int pc __attribute__ ((packed)); /* point code */ } mtp_addr_t; #define __HAVE_MTP_ADDR #endif /* * MTP_INFO_REQ, M_PROTO */ typedef struct MTP_info_req { mtp_ulong mtp_primitive; /* always MTP_INFO_REQ */ } MTP_info_req_t; /* * MTP_INFO_ACK, M_PCPROTO */ typedef struct MTP_info_ack { mtp_ulong mtp_primitive; /* always MTP_INFO_ACK */ mtp_ulong mtp_msu_size; /* maximum MSU size for guaranteed delivery */ mtp_ulong mtp_addr_size; /* maximum address size */ mtp_ulong mtp_addr_length; /* address length */ mtp_ulong mtp_addr_offset; /* address offset */ mtp_ulong mtp_current_state; /* current interface state */ mtp_ulong mtp_serv_type; /* service type */ mtp_ulong mtp_version; /* version of interface */ } MTP_info_ack_t; #define M_COMS 1 /* Connection-mode MTP service supported */ #define M_CLMS 2 /* Connection-less MTP service supported */ /* * MTP_ADDR_REQ, M_PCPROTO */ typedef struct MTP_addr_req { mtp_ulong mtp_primitive; /* always MTP_ADDR_REQ */ } MTP_addr_req_t; /* * MTP_ADDR_ACK, M_PCPROTO */ typedef struct MTP_addr_ack { mtp_ulong mtp_primitive; /* always MTP_ADDR_ACK */ mtp_ulong mtp_loc_length; /* length of local MTP address */ mtp_ulong mtp_loc_offset; /* offset of local MTP address */ mtp_ulong mtp_rem_length; /* length of remote MTP address */ mtp_ulong mtp_rem_offset; /* offset of remote MTP address */ } MTP_addr_ack_t; /* * MTP_BIND_REQ, M_PROTO */ typedef struct MTP_bind_req { mtp_ulong mtp_primitive; /* always MTP_BIND_REQ */ mtp_ulong mtp_addr_length; /* length of MTP address */ mtp_ulong mtp_addr_offset; /* offset of MTP address */ mtp_ulong mtp_bind_flags; /* bind flags */ } MTP_bind_req_t; /* * MTP_BIND_ACK, M_PCPROTO */ typedef struct MTP_bind_ack { mtp_ulong mtp_primitive; /* always MTP_BIND_ACK */ mtp_ulong mtp_addr_length; /* length of bound MTP address */ mtp_ulong mtp_addr_offset; /* offset of bound MTP address */ } MTP_bind_ack_t; /* * MTP_UNBIND_REQ, M_PROTO */ typedef struct MTP_unbind_req { mtp_ulong mtp_primitive; /* always MTP_UNBIND_REQ */ } MTP_unbind_req_t; /* * MTP_CONN_REQ, M_PROTO */ typedef struct MTP_conn_req { mtp_ulong mtp_primitive; /* always MTP_CONN_REQ */ mtp_ulong mtp_addr_length; /* length of MTP address to connect */ mtp_ulong mtp_addr_offset; /* offset of MTP address to connect */ mtp_ulong mtp_conn_flags; /* connect flags */ } MTP_conn_req_t; /* * MTP_DISCON_REQ, M_PROTO, M_PCPROTO */ typedef struct MTP_discon_req { mtp_ulong mtp_primitive; /* always MTP_DISCON_REQ */ } MTP_discon_req_t; /* * MTP_OPTMGMT_REQ, M_PROTO or M_PCPROTO */ typedef struct MTP_optmgmt_req { mtp_ulong mtp_primitive; /* always MTP_OPTMGMT_REQ */ mtp_ulong mtp_opt_length; /* length of options */ mtp_ulong mtp_opt_offset; /* offset of options */ mtp_ulong mtp_mgmt_flags; /* management flags */ } MTP_optmgmt_req_t; #define MTP_DEFAULT 0UL #define MTP_CHECK 1UL #define MTP_NEGOTIATE 2UL #define MTP_CURRENT 3UL /* * MTP_OPTMGMT_ACK, M_PCPROTO */ typedef struct MTP_optmgmt_ack { mtp_ulong mtp_primitive; /* always MTP_OPTMGMT_ACK */ mtp_ulong mtp_opt_length; /* length of options */ mtp_ulong mtp_opt_offset; /* offset of options */ mtp_ulong mtp_mgmt_flags; /* management flags */ } MTP_optmgmt_ack_t; /* * MTP_OK, MTP_ERROR, M_PCPROTO */ typedef struct MTP_ok_ack { mtp_ulong mtp_primitive; /* always MTP_OK_ACK */ mtp_ulong mtp_correct_prim; /* correct primitive */ } MTP_ok_ack_t; typedef struct MTP_error_ack { mtp_ulong mtp_primitive; /* always MTP_ERROR_ACK */ mtp_ulong mtp_error_primitive; /* primitive in error */ mtp_ulong mtp_mtpi_error; /* MTP interface error */ mtp_ulong mtp_unix_error; /* UNIX error */ } MTP_error_ack_t; #define MSYSERR 0UL #define MACCESS 1UL #define MBADADDR 2UL #define MNOADDR 3UL #define MBADPRIM 4UL #define MOUTSTATE 5UL #define MNOTSUPP 6UL #define MBADFLAG 7UL #define MBADOPT 8UL /* * MTP_TRANSFER_REQ, M_PROTO */ typedef struct MTP_transfer_req { mtp_ulong mtp_primitive; /* always MTP_TRANSFER_REQ */ mtp_ulong mtp_dest_length; /* length of destination address */ mtp_ulong mtp_dest_offset; /* offset of destination address */ mtp_ulong mtp_mp; /* message priority */ mtp_ulong mtp_sls; /* signalling link selection */ } MTP_transfer_req_t; /* * MTP_TRANSFER_IND, M_PROTO (band 0) */ typedef struct MTP_transfer_ind { mtp_ulong mtp_primitive; /* always MTP_TRANSFER_IND */ mtp_ulong mtp_srce_length; /* length of source address */ mtp_ulong mtp_srce_offset; /* offset of source address */ mtp_ulong mtp_mp; /* message priority */ mtp_ulong mtp_sls; /* signalling link selection */ } MTP_transfer_ind_t; /* * MTP_PAUSE_IND, M_PROTO (band 1) */ typedef struct MTP_pause_ind { mtp_ulong mtp_primitive; /* always MTP_PAUSE_IND */ mtp_ulong mtp_addr_length; /* length of affected MTP address */ mtp_ulong mtp_addr_offset; /* offset of affected MTP address */ } MTP_pause_ind_t; /* * MTP_RESUME_IND, M_PROTO (band 1) */ typedef struct MTP_resume_ind { mtp_ulong mtp_primitive; /* always MTP_RESUME_IND */ mtp_ulong mtp_addr_length; /* length of affected MTP address */ mtp_ulong mtp_addr_offset; /* offset of affected MTP address */ } MTP_resume_ind_t; /* * MTP_STATUS_REQ, M_PROTO or M_PCPROTO */ typedef struct MTP_status_req { mtp_ulong mtp_primitive; /* always MTP_STATUS_REQ */ mtp_ulong mtp_addr_length; /* length of affected MTP address */ mtp_ulong mtp_addr_offset; /* offset of affected MTP address */ mtp_ulong mtp_type; /* type */ mtp_ulong mtp_status; /* status */ } MTP_status_req_t; /* * MTP_STATUS_IND, M_PROTO (band 1) */ typedef struct MTP_status_ind { mtp_ulong mtp_primitive; /* always MTP_STATUS_IND */ mtp_ulong mtp_addr_length; /* length of affected MTP address */ mtp_ulong mtp_addr_offset; /* offset of affected MTP address */ mtp_ulong mtp_type; /* type */ mtp_ulong mtp_status; /* status */ } MTP_status_ind_t; /* Type for MTP_STATUS_IND */ #define MTP_STATUS_TYPE_CONG 0x00 /* MTP-STATUS refers to congestion */ #define MTP_STATUS_TYPE_UPU 0x01 /* MTP-STATUS refers to user part unavailability */ #define MTP_STATUS_TYPE_RSTR 0x02 /* MTP-STATUS refers to restriction */ /* Status for MTP_STATUS_IND, with MTP_STATUS_TYPE_UPU */ #define MTP_STATUS_UPU_UNKNOWN 0x01 /* User part unavailable: unknown */ #define MTP_STATUS_UPU_UNEQUIPPED 0x02 /* User part unavailable: unequipped remote user. */ #define MTP_STATUS_UPU_INACCESSIBLE 0x03 /* User part unavailable: inaccessible remote user. */ /* Status for MTP_STATUS_IND, with MTP_STATUS_TYPE_CONG */ #define MTP_STATUS_CONGESTION_LEVEL0 0x00 /* Signalling network congestion level 0 */ #define MTP_STATUS_CONGESTION_LEVEL1 0x01 /* Signalling network congestion level 1 */ #define MTP_STATUS_CONGESTION_LEVEL2 0x02 /* Signalling network congestion level 2 */ #define MTP_STATUS_CONGESTION_LEVEL3 0x03 /* Signalling network congestion level 3 */ #define MTP_STATUS_CONGESTION 0x04 /* Signalling network congestion */ /* * MTP_RESTART_BEGINS_IND, M_PCPROTO */ typedef struct MTP_restart_begins_ind { mtp_ulong mtp_primitive; /* always MTP_RESTART_BEGINS_IND */ } MTP_restart_begins_ind_t; /* * MTP_RESTART_COMPLETE_IND, M_PCPROTO */ typedef struct MTP_restart_complete_ind { mtp_ulong mtp_primitive; /* always MTP_RESTART_COMPLETE_IND */ } MTP_restart_complete_ind_t; union MTP_primitives { mtp_ulong mtp_primitive; MTP_info_req_t info_req; MTP_info_ack_t info_ack; MTP_addr_req_t addr_req; MTP_addr_ack_t addr_ack; MTP_bind_req_t bind_req; MTP_bind_ack_t bind_ack; MTP_unbind_req_t unbind_req; MTP_conn_req_t conn_req; MTP_discon_req_t discon_req; MTP_optmgmt_req_t optmgmt_req; MTP_optmgmt_ack_t optmgmt_ack; MTP_ok_ack_t ok_ack; MTP_error_ack_t error_ack; MTP_transfer_req_t transfer_req; MTP_transfer_ind_t transfer_ind; MTP_pause_ind_t pause_ind; MTP_resume_ind_t resume_ind; MTP_status_ind_t status_ind; MTP_restart_complete_ind_t restart_complete_ind; MTP_status_req_t status_req; }; typedef struct { mtp_ulong mtp_affected_dpc; } mtp_pause_ind_t; typedef struct { mtp_ulong mtp_affected_dpc; } mtp_resume_ind_t; /* * 8.1 Transfer * * The primitive "MTP-TRANSFER" is used between level 4 and level 3 (SMH) to * provide the MTP message transfer service. */ /* * 8.2 Pause * * The primitive "MTP-PAUSE" indicates to "Users" the total inability of * providing the MTP service to the specified destination (see 7.2.6). * * NOTE - The signalling point is inacessible via the MTP. The MTP will * determine when the signalling point is again acessible and send MTP-RESUME * indication. The user should wait for such an indication and, meanwhile is * not allowed to send messages on that signalling point. If the remote peer * user is thought to be unavailable, that condition may be maintained or * cancelled at the local user's discretion. */ /* * 8.3 Resume * * The primitive MTP-RESUME indications to the "User" the ability of * providing the MTP service to the specified destination (See 7.2.6) * * This primitive corresponds to the destination accessible state as defined * in Recommendation Q.704. * * NOTE - When the MTP-RESUME indicaiton is given to each user, the MTP does * not know whether the remote peer user is available. This is the * responsibility of each user. */ /* * 8.4 Status * * The primitive "MTP-STATUS" indicates to the "Users" the partial inability * of providing the MTP service to the specified destination. The primitive * is also used to indicate to a User that a remote corresponding User is * unavailable and the cause for unavailability (see 11.2.7/Q.704). * * In the case of national option with congestion priorities or multiple * signalling link congestion states without prioritites as in Recommendation * Q.704 are implemented, this "MTP-STATUS" primitive is also used to * indicate a change of congestion level. * * This primitive corresponds to the destination congested/User Part * unavailable states as defined in Recommendation Q.704. * * NOTE - In the case of remote user unavailability, the user is responsible * for determining the availability of this peer user. The user is * cautioned not to send normal traffic to the peer user because, * while such peer is unavailable, no message will be delivered but * each will result in a repeated "MTP-STATUS" indication. The MTP * will not send any further indications about the unavailability or * availability of this peer user unless the local user continues to * send messages to the peer user. */ /* * 8.5 Restart * * When the MTP restart procedure is terminated, the MTP indicates the end of * MTP restart to all local MTP Users showing each signalling point's * accessibility or inaccessibility. The means of doing this is * implementation dependent (see 9/Q.704). */ /* * MTP_STATUS_IND, M_PROTO or M_PCPROTO */ typedef struct { mtp_ulong mtp_affected_dpc; mtp_uchar mtp_cause; mtp_uchar mtp_level; } mtp_status_ind_t; typedef struct { mtp_ulong dpc; mtp_ulong opc; mtp_ulong sls; } mtp_rl_t; typedef struct { mtp_uchar si; mtp_uchar mp; mtp_uchar ni; mtp_rl_t rl; } mtp_hdr_t; typedef struct { mtp_uchar si; mtp_uchar mp; mtp_uchar ni; mtp_rl_t rl; mtp_uchar h0; mtp_uchar h1; } mtp_msu_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_COO */ mtp_msu_t mtp_msg; mtp_ulong mtp_slc; mtp_ulong mtp_fsnc; } mtp_signal_coo_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_COA */ mtp_msu_t mtp_msg; } mtp_signal_coa_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_CBD */ mtp_msu_t mtp_msg; } mtp_signal_cbd_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_CBA */ mtp_msu_t mtp_msg; } mtp_signal_cba_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_ECO */ mtp_msu_t mtp_msg; } mtp_signal_eco_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_ECA */ mtp_msu_t mtp_msg; } mtp_signal_eca_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_RCT */ mtp_msu_t mtp_msg; } mtp_signal_rct_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_TFC */ mtp_msu_t mtp_msg; } mtp_signal_tfc_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_TFP */ mtp_msu_t mtp_msg; } mtp_signal_tfp_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_TFR */ mtp_msu_t mtp_msg; } mtp_signal_tfr_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_TFA */ mtp_msu_t mtp_msg; } mtp_signal_tfa_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_RSP */ mtp_msu_t mtp_msg; } mtp_signal_rsp_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_RSR */ mtp_msu_t mtp_msg; } mtp_signal_rsr_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_LIN */ mtp_msu_t mtp_msg; } mtp_signal_lin_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_LUN */ mtp_msu_t mtp_msg; } mtp_signal_lun_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_LIA */ mtp_msu_t mtp_msg; } mtp_signal_lia_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_LUA */ mtp_msu_t mtp_msg; } mtp_signal_lua_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_LID */ mtp_msu_t mtp_msg; } mtp_signal_lid_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_LFU */ mtp_msu_t mtp_msg; } mtp_signal_lfu_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_LLT */ mtp_msu_t mtp_msg; } mtp_signal_llt_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_LRT */ mtp_msu_t mtp_msg; } mtp_signal_lrt_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_TRA */ mtp_msu_t mtp_msg; } mtp_signal_tra_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_DLC */ mtp_msu_t mtp_msg; } mtp_signal_dlc_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_CSS */ mtp_msu_t mtp_msg; } mtp_signal_css_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_CNS */ mtp_msu_t mtp_msg; } mtp_signal_cns_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_CNP */ mtp_msu_t mtp_msg; } mtp_signal_cnp_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_UPU */ mtp_msu_t mtp_msg; } mtp_signal_upu_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_SLTM */ mtp_msu_t mtp_msg; } mtp_signal_sltm_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_SLTA */ mtp_msu_t mtp_msg; } mtp_signal_slta_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_SSLTM */ mtp_msu_t mtp_msg; } mtp_signal_ssltm_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_SSLTA */ mtp_msu_t mtp_msg; } mtp_signal_sslta_t; typedef struct { mtp_long mtp_primitive; /* MTP_MSU_REQ, MTP_MSU_IND */ mtp_ulong mtp_signal; /* MTP_SIGNAL_USER */ mtp_hdr_t mtp_msg; } mtp_signal_user_t; typedef union { mtp_long mtp_primitive; mtp_signal_user_t msg; mtp_signal_coo_t coo; mtp_signal_coa_t coa; mtp_signal_cbd_t cbd; mtp_signal_cba_t cba; mtp_signal_eco_t eco; mtp_signal_eca_t eca; mtp_signal_rct_t rct; mtp_signal_tfc_t tfc; mtp_signal_tfp_t tfp; mtp_signal_tfr_t tfr; mtp_signal_tfa_t tfa; mtp_signal_rsp_t rsp; mtp_signal_rsr_t rsr; mtp_signal_lin_t lin; mtp_signal_lun_t lun; mtp_signal_lia_t lia; mtp_signal_lua_t lua; mtp_signal_lid_t lid; mtp_signal_lfu_t lfu; mtp_signal_llt_t llt; mtp_signal_lrt_t lrt; mtp_signal_tra_t tra; mtp_signal_dlc_t dlc; mtp_signal_css_t css; mtp_signal_cns_t cns; mtp_signal_cnp_t cnp; mtp_signal_upu_t upu; mtp_signal_sltm_t sltm; mtp_signal_slta_t slta; mtp_signal_ssltm_t ssltm; mtp_signal_sslta_t sslta; mtp_signal_user_t user; } MTP_signals; /* * MTP_MSU_REQ , M_PROTO or M_PCPROTO (M_DATA) */ typedef MTP_signals mtp_msu_req_t; /* * MTP_MSU_IND , M_PROTO or M_PCPROTO (M_DATA) */ typedef MTP_signals mtp_msu_ind_t; #define MTP_SIGNAL_NONE 0 #define MTP_SIGNAL_COO 1 /* STM */ #define MTP_SIGNAL_COA 2 /* STM */ #define MTP_SIGNAL_CBD 3 /* STM */ #define MTP_SIGNAL_CBA 4 /* STM */ #define MTP_SIGNAL_ECO 5 /* STM */ #define MTP_SIGNAL_ECA 6 /* STM */ #define MTP_SIGNAL_LIN 14 /* STM */ #define MTP_SIGNAL_LUN 15 /* STM */ #define MTP_SIGNAL_LIA 16 /* STM */ #define MTP_SIGNAL_LUA 17 /* STM */ #define MTP_SIGNAL_LID 18 /* STM */ #define MTP_SIGNAL_LFU 19 /* STM */ #define MTP_SIGNAL_LLT 20 /* STM */ #define MTP_SIGNAL_LRT 21 /* STM */ #define MTP_SIGNAL_TRA 22 /* STM */ #define MTP_SIGNAL_RCT 7 /* SRM */ #define MTP_SIGNAL_TFC 8 /* SRM */ #define MTP_SIGNAL_TFP 9 /* SRM */ #define MTP_SIGNAL_TFR 10 /* SRM */ #define MTP_SIGNAL_TFA 11 /* SRM */ #define MTP_SIGNAL_RSP 12 /* SRM */ #define MTP_SIGNAL_RSR 13 /* SRM */ #define MTP_SIGNAL_UPU 27 /* SRM */ #define MTP_SIGNAL_DLC 23 /* SLM */ #define MTP_SIGNAL_CSS 24 /* SLM */ #define MTP_SIGNAL_CNS 25 /* SLM */ #define MTP_SIGNAL_CNP 26 /* SLM */ #define MTP_SIGNAL_SLTM 28 /* SLTC */ #define MTP_SIGNAL_SLTA 29 /* SLTC */ #define MTP_SIGNAL_SSLTM 30 /* SLTC */ #define MTP_SIGNAL_SSLTA 31 /* SLTC */ #define MTP_SIGNAL_USER 32 /* L4 */ #endif /* __SS7_MTPI_H__ */ Appendix E MTPI LibraryAppendix F MTPI Drivers and ModulesAppendix G MTPI UtilitiesAppendix H MTPI File FormatsAppendix I MTPI Compatibility and PortingGlossary
Acronyms
References
LicensesAll code presented in this manual is licensed under the GNU Affero General Public License. The text of this manual is licensed under the GNU Free Documentation License, with no invariant sections, no front-cover texts and no back-cover texts. Please note, however, that it is just plain wrong to modify statements of, or attribute statements to, the Author or OpenSS7 Corporation. GNU Affero General Public LicenseThe GNU Affero General Public License.
Version 3, 19 November 2007
Copyright © 2007 Free Software Foundation, Inc. http://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. PreambleThe GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program–to make sure it remains free software for all its users. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software. A secondary benefit of defending all users’ freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate. Many developers of free software are heartened and encouraged by the resulting cooperation. However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public. The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version. An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals. This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New ProgramsIf you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found. one line to give the program's name and a brief idea of what it does. Copyright (C) year name of author This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see http://www.gnu.org/licenses/. Also add information on how to contact you by electronic and paper mail. If your software can interact with users remotely through a network, you should also make sure that it provides a way for users to get its source. For example, if your program is a web application, its interface could display a “Source” link that leads users to an archive of the code. There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements. You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see http://www.gnu.org/licenses/. GNU Free Documentation LicenseGNU FREE DOCUMENTATION LICENSE
Version 1.3, 3 November 2008
Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. http://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
ADDENDUM: How to use this License for your documentsTo use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page: Copyright (C) year your name. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled ``GNU Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with…Texts.” line with this: with the Invariant Sections being list their titles, with the Front-Cover Texts being list, and with the Back-Cover Texts being list. If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation. If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software. Index
Short Table of Contents
Table of Contents
Footnotes(1)http://www.openss7.org/repos/tarballs/openss7-1.1.7.20141001.tar.bz2 (2)‘Q.711’. (3)ISUP consists of signalling relations between two switches which also have digital facilities between them. In general an ISUP MTP-User can communicate with many other MTP-User peers, however, signalling between any given two enpoints only concerns the digital facilities which exist between the two endpoints. So, management of ISUP switches is best performed on a pairing of endpoints (signalling relations). Also, the COMS mode of operation is provided in support of DPC list Routing Keys for M3UA. [RFC 4666] (4)Conventions for the time-sequence diagrams are defined in ITU-T X.210. [X.210] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Last modified: Fri, 10 Oct 2014 10:40:36 GMT Copyright © 2014 OpenSS7 Corporation All Rights Reserved. |