The only difference is that the payload is reduced from 140 bytes to 134 or 133 bytes (1 or 2bytes reference number) due to udh header.
BR V. From: Grant Saicom Sent: Τρίτη, 21 Νοεμβρίου 2017 - 11:20 To: amal...@kannel.org Cc: Kannel Users Subject: Re: SMPP 3.4 Protocol: Concatenated Message Flow That is what I thought. Thank you for confirmation. On 21 Nov 2017, at 10:49, amal...@kannel.org<mailto:amal...@kannel.org> wrote: Hi, there is submit_sm_resp for each submit_sm for concatenated message as well. Thanks, Alex Am 21.11.2017 um 08:23 schrieb Grant Saicom <grant.sai...@gmail.com<mailto:grant.sai...@gmail.com>>: Hello Kannel Users I have a question with regards to the signaling flow of a concatenated SMS. Simplistically, when we send a single (successful) sms of less than 160 chars (gsm7) on an established bind, the ESME sends a single submit_sm to the SMSC, then the SMSC responds to the ESME with a submit_sm_resp for that message. According to a document I found at docs.nimta.com/SMPP_v3_4_Issue1_2.pdf<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.nimta.com%2FSMPP_v3_4_Issue1_2.pdf&data=02%7C01%7Cvtypal%40outlook.com%7Cfa94c213891b4bc5365008d530c12b75%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636468528564945801&sdata=1CFo2N2WvOra8JQraBmpppJGpQ34OjL8QDF3GK2%2BKgA%3D&reserved=0>, it says that for each submit_sm, there should be a submit_sm_resp (pages 21 - 22). What does the message flow look like when a message of more than 160 characters (concatenated message) is sent using GSM SMS User Data and UDH? Is there a submit_sm_resp for each submit_sm or a single submit_sm_resp for the several submit_sm of the concatenated message? Kind regards Grant
