(Page 7 of 7 in this chapter) Version
MTP3SendData
Description
- Requests that data be transmitted to a specified signaling point.
Prototype
- DWORD NMSAPI MTP3SendData (CTAHD ctahd,
S16 sapId,
U32 opc,
U32 dpc,
U8 lnkSel,
U8 priority,
U8 *data,
S16 length,
U8 srvInfo)
- ctahd Natural Access Handle.
- sapID Service Access Point ID.
- opc Specifies the 24 or 14-bit originating point code to be inserted in the outgoing message.
- dpc Specifies the 24 or 14-bit destination point code of the remote system.
- lnkSel Specifies which link of a linkset to use. Valid ranges are 0 - 15 for ITU-T and 0 -31 for ANSI.
- priority Specifies the priority of the message. Valid range is 0 (lowest) to 3 (highest).
- data Pointer to the address of a buffer of data to transmit.
- length Specifies the length (in octets) of the data in the data field.
- srvInfo The Service Information Octet in which the application is interested.
Return Values
Details
- When specifying a value for sapId, the same value used for the ctaOpenServices request should be specified here as well.
- Both opc and dpc are passed as 32 bit values. For example, the 24-bit point code 5.49.7 would be passed as 0x053107.
- For TUP only, all 8 bits are available to the application with no lnkSel range checking. For a thorough description of this field, refer to Section 2.3.2, Outbound Message Routing.
- The user data sent is unique in that the first byte corresponds to the first byte following the routing label in the underlying SS7 data message. For example, when constructing an ISUP message, the first byte of user data would be the first byte of the circuit identification code (CIC). The MTP layer 3 constructs the routing label and SIO values from other parameters and bind information. The user application is responsible for any byte-order translation necessary for all data in the data field.
- The SIO must be unique for each application. The service information field is composed of Service Indicator and Network Indicator fields. Only the Service Indicator field is used for routing of incoming messages.
(Page 7 of 7 in this chapter) Version
Want to send us feedback on our documentation? Email: Tech_Pubs@nmss.com
Copyright © 2002, NMS Communications Corporation. All rights
reserved.