Difference between revisions of "Transport"
From ss7api.null.ro
(→MTP) |
|||
| Line 2: | Line 2: | ||
==MTP== | ==MTP== | ||
| + | The <mtp> transport section describes message parameters specific to MTP. Normally these parameters are just informative for the applications and on new outbound messages are added automatically. | ||
| + | |||
| + | This section may be missing for error reports created higher in the protocol stack or if the SS7 transport is not MTP. | ||
| + | <mtp> | ||
| + | <LocalPC>101</LocalPC> | ||
| + | <RemotePC>5000</RemotePC> | ||
| + | <sls>2</sls> | ||
| + | </mtp> | ||
| + | |||
| + | ===Parameters=== | ||
| + | * LocalPC – Point Code on the local side; DPC for inbound messages, OPC for outbound | ||
| + | * RemotePC – Point Code on the local side; OPC for inbound messages, DPC for outbound | ||
| + | * sls – Signaling Link Selection Code | ||
==SCCP== | ==SCCP== | ||
Revision as of 15:33, 23 August 2013
The transport part of the message contains parameters related to the lower level transports. On receive these parameters are filled from the received message. On send these parameters are used by the transports to properly form and route the message.
Contents |
MTP
The <mtp> transport section describes message parameters specific to MTP. Normally these parameters are just informative for the applications and on new outbound messages are added automatically.
This section may be missing for error reports created higher in the protocol stack or if the SS7 transport is not MTP.
<mtp>
<LocalPC>101</LocalPC>
<RemotePC>5000</RemotePC>
<sls>2</sls>
</mtp>
Parameters
- LocalPC – Point Code on the local side; DPC for inbound messages, OPC for outbound
- RemotePC – Point Code on the local side; OPC for inbound messages, DPC for outbound
- sls – Signaling Link Selection Code
