On Tue, 2014-12-02 at 17:07, ha...@aeon.pk wrote: > A good question! :-) > > I did use 63, as I am using it since quite some time (and it works). > However on your alert, I checked the userguide to see that 63 should not be > a combination at all. But I am pretty sure that I read it somewhere else, > that's why I started using it. It would be something like 63=31+32, where I > need to dig out what 32 status is for.
Mask is binary but dlr-mask parameter is decimal encoding of the desired delivery reports. Decimal values for particular delivery report are: 16 == SMSC Rejected, response would be NACK/##/SOMETEXT 8 == SMSC Accepted, response would be ACK/ 4 == Carrier Accepted 2 == Handset Rejected/Failed 1 == Handset Delivered So, if you set dlr-mask to 63 it have all five (lower) bits set to 1 and you get the same result as with dlr-mask equal to 31. I didn't looked at code but I presume that dlr-mask could be set to 127 or even 255 (all lower five bits are set to 1) and you will have the reports as with mask set to 31. 31 is 11111 in binary form 63 is 111111 in binary Notice that lower five bits have all 1 values. Kannel ignores unused bits in dlr-mask probably, I didn't checked the source. > Will update you as I find some info. > > On Tue, Dec 2, 2014 at 6:38 AM, spameden <spame...@gmail.com> wrote: > > > >with DLR mask 63 > > > > did you mean 31 ? > > > > 2014-12-01 23:34 GMT+03:00 ha...@aeon.pk <ha...@aeon.pk>: > > > > Resolved. > >> > >> In connection 'group = smsc', add line 'msg-id-type = 0x01' to fix the > >> issue. > >> > >> On Tue, Dec 2, 2014 at 12:04 AM, ha...@aeon.pk <ha...@aeon.pk> wrote: > >> > >>> Hi, > >>> > >>> I have 2 SMSC connections. I am sending the same message with DLR mask > >>> 63 (to get all possible delivery states). One SMSC connection is giving me > >>> submission-to-SMSC DLR and then DELIVERED DLR, both appearing in kannel > >>> traffic logs. The other connection is only giving me submission-to-SMSC > >>> DLR, and not the DELIVERED DLR in traffic logs. I took tcpdump trace to > >>> discover that the DELIVERED DLR is infact coming to kannel but for some > >>> reason, kannel is not showing it in the traffic log. > >>> > >>> Any idea which parameter to change for this DLR to appear in the logs? > >>> > >>> Regards, > >>> Hamza > >>> > >> > >> > > -- Kind regards, Milan -------------------------------------------------- Arvanta, http://www.arvanta.net Please do not send me e-mail containing HTML code or documents in proprietary format (word, excel, pps and so on)
