After receiving any deliver_sm (DLR-4, DLR-1 or DLR-2), kannel checks the dlr-storage (REDIS in yours) to find the entry and call the specified dlr-url if available.
Both DLRs seem OK to me. As you mentioned, still *dlr:?:?* is the problem in both versions. Let me check more. On Fri, Apr 15, 2022 at 7:47 PM lbrezs...@gmx.co.uk <lbrezs...@gmx.co.uk> wrote: > We considered DLR 27, but unfortunately some small number of ISPs don't > send DLR 1 or 2 at all. > > They just acknowledged they received the request, but not that end user > (mobile phone) received it. > > Question: why code handling DLR1 and DLR4 is different? I compared the > structure of both DLRa and they are the same: > > DLR4: > id:0273822961 sub:001 dlvrd:000 submit date:2204142257 done date > 2204142257 stat ACCEPTD err:003 text:Test DLR 4 > DLR1 > id:0274640129 sub:001 dlvrd:001 submit date:2204151041 done date > 2204151041 stat DELIVRD err:000 text:Test DLR 1 > > Why even make a trip to REDIS? As you need to wait for DLR 1/2 anyways, > why even bother? > They are still forwarded to smsbox, no? Shouldn't be just an "IF" > statement that DLR 1 or DLR 2 make a trip to REDIS, everything else is > forwarded to smsbox as is? > > By the way, I double-check the WARNING exists on 1.4.4 > (redis_version:3.2.6) vs ERROR on 1.4.5 (redis_version:6.0.16) > > old message, 1.4.4 (redis_version:3.2.6) : > > 2022-04-15 02:57:01 [24496] [6] DEBUG: DLR[redis]: DLR not destroyed, > still waiting for other delivery report > 2022-04-15 02:57:01 [24496] [6] DEBUG: Updating DLR status in keystore > 2022-04-15 02:57:01 [24496] [6] WARNING: DLR: REDIS: No dlr found to > update for dlr:?:? > 2022-04-15 02:57:01 [24496] [6] DEBUG: new group created `smpp' > 2022-04-15 02:57:01 [24496] [6] DEBUG: group=`smpp' key=`dlr_err' value=' > > new message, 1.4.5 (redis_version:6.0.16): > > 2022-04-07 16:05:40 [612] [6] ERROR: REDIS: redisCommand() failed: `ERR > unknown command `smsc_id`, with args beginning with: `1117930062`, `4`, ' > 2022-04-07 16:05:40 [612] [6] ERROR: DLR: REDIS: Error while updating > dlr entry for dlr:?:? > > On 4/14/2022 20:55, lbrezs...@gmx.co.uk wrote: > > I don't think it's the message. > > > > bearer-box access-log looks ordinary > > > > 2022-04-14 18:49:56 send-SMS request added - sender:smsuser:XX999 > > 192.168.27.35 target:1XXX9562019 request: 'Test DLR 4' > > > > Hower, there is an important piece of information I forgot to mention. > > > > Machine that handles DLR 4s correctly: > > > > Kannel bearerbox version 1.4.4. > > Compiler 6.2.1 20161124. > > System Linux, release 4.9.0-13-amd64 > > debian 10 = SMP Debian 4.9.228-1 (2020-07-05), machine x86_64 > > hiredis API 0.13.3 > > redis_version:3.2.6 > > > > Machine that handles DLR 4s incorrectly: > > > > Kannel bearerbox version 1.4.5. > > Compiler 10.1.0. > > System Linux, release 5.10.0-13-amd64, > > debian 11 = SMP Debian 5.10.106-1 (2022-03-17), machine x86_64 > > Using hiredis API 0.14.1 > > redis_version:6.0.16 > > > > On 4/14/2022 18:38, Sayed Hadi Rastgou Haghi wrote: > >> REDIS: redisCommand() > > > > -- Sincerely, Sayed Hadi Rastgou Haghi
