# Sending messages

For sending messages, `submit_sm` and `data_sm` can be used.

When sending more data in the message body or data field than can be submitted in a single submission to the carrier, Sinch will split transactions. These are charged as multiple transaction events.

To help ensure successful delivery, we'll review the way Sinch interprets source and destination addresses below.

## Source address

As the interpretation of [TON](https://community.sinch.com/t5/Glossary/TON/ta-p/7760) and [NPI](https://community.sinch.com/t5/Glossary/NPI/ta-p/7646) values has been different depending on carriers and aggregators, we’ll clarify the way we interpret TON and NPI values.

Any values other than those listed below will be interpreted as TON 0x0 and NPI 0x1.

div
div
table
thead
tr
th
Source Address
th
Arrives on handset
tr
th
Sent to Sinch
th
Type Of Number(TON)
th
Number Plan Indicator(NPI)
tbody
tr
td
00461234567889
td
0x00
td
Unknown
td
0x01
td
MSISDN
td
046123456789
tr
td
01234567889
td
0x00
td
Unknown
td
0x01
td
MSISDN
td
123456789
tr
td
461234567889
td
0x01
td
International
td
0x01
td
MSISDN
td
+46123456789
tr
td
1234567889
td
0x02
td
National
td
0x01
td
MSISDN
td
123456789
tr
td
Sinch
td
0x05
td
Alphanumeric
td
0x00
td
Unknown
td
Sinch
The type of source address is defined by the source address TON and NPI parameters.

- Alphanumeric sender is limited to a maximum length of 11 characters.
- MSISDN sender maximum length is 18.
- To enable a handset to respond to a short code, we recommend using TON=0x00 and NPI=0x01.


## Destination address

A sinch destination address should always be sent as the [E.164](https://community.sinch.com/t5/Glossary/E-164/ta-p/7537) [CC](https://community.sinch.com/t5/Glossary/Country-Code-CC/ta-p/7502) + NDC + subscriber number. This is also referred to as the “MSISDN” of a subscriber.
For further information on the MSISDN format, see the [ITU-T specification E.164](https://www.itu.int/rec/T-REC-E.164/en).

table
tr
th
Sent to Sinch
th
Type Of Number (TON)
th
Number Plan Indicator (NPI)
tr
td
46123456789
td
0x01 | International
td
0x01 | MSISDN
## Status report formatting

Sinch follows the delivery receipt formatting outlined in [SMPP Protocol Specification v3.4 Issue 1.2, Appendix B](https://smpp.org/SMPP_v3_4_Issue1_2.pdf#page=167). Contact your [account manager](https://dashboard.sinch.com/dashboard) to add additional information to the delivery receipt by including MCC/MNC information.

## MCC + MNC in status reports

[MCC](https://community.sinch.com/t5/Glossary/MCC/ta-p/7604) + [MNC](https://community.sinch.com/t5/Glossary/MNC/ta-p/7615)  information in SMPP delivery receipts can be included as an optional parameter. This information, optionally configured per SMPP account, is passed in a vendor-specific TLV (0x1403).

In the value field, you will receive the MCC + MNC of the destination operator.

Example:
Optional parameter: 0x1403 (0x1403):

- Tag: 0x1403
- Length: 6
- Value (hex): 32 33 34 33 30 00 (Text: 23430n)


Result is MCC=234 and MNC=30

## Next Step

Review the [receiving messages SMPP documentation](/docs/sms/smpp/receive-message).

## Additional resources

- [SMPP Connectivity](/docs/sms/smpp/connectivity)
- Prefer a REST API? [Get started with the REST SMS API](/docs/sms/getting-started).