Yes, I also would like to approach this patch. Because sometimes when client doesn't have enough memory in his phone or any other device he would receive only 1 or 2 messages instead of 5 for example.
But, I'd like to minimize number of records of MySQL/PGSQL or any other DB, so let's say you have MT with 5 parts and you are basically updating counter of parts received by client. Is it possible? Let me know If I was clean. Sorry for my english. 2012/8/7 Rene Kluwen <[email protected]> > Interesting!**** > > ** ** > > How would one distinguish (dlr-wise) between the different parts?**** > > ** ** > > == Rene**** > > > *From:* [email protected] [mailto:[email protected]] > *On Behalf Of *Paul Cook > *Sent:* Tuesday, 07 August, 2012 18:09 > *To:* [email protected] > *Subject:* Concatenated MT - configurable registered_delivery behaviour*** > * > > ** ** > > Hi, > > We have a number of clients who use kannel as a client to submit to our > messaging service. > A common problem they encounter is that when sending a long MT, it is > split correctly into multiple parts, but registered_delivery is set to 0 > for all parts greater than 0. > > This attached patch makes that behavior optional, by adding the following > config line to an smsc group: > > concatenated-sms-dlr-for-all-parts = true > > If set, then registered_delivery will not be altered for the subsequent > parts of the concatenated set, and the client app will receive delivery > receipts for all parts. > > > Please consider this patch for inclusion in the next release > > > Thanks > > > Paul Cook**** >
