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 corre
Dear akamat,
Can you send the failed DLR message as well?
In my opinion, the problem is in connection with dlr-message parsing.
It can be found in bearer-box access-log or captured with wireshark.
On Fri, Apr 15, 2022 at 12:28 AM lbrezs...@gmx.co.uk
wrote:
> Using Redis for dlr-storage.
>
>
Using Redis for dlr-storage.
dlr-mask=31, which means everything.
Lately getting redis errors when receiving DLR 4
Anybody came across the same issue?
Logs:
2022-04-14 19:03:08 [2603] [6] DEBUG: DLR[redis]: DLR not destroyed,
still waiting for other delivery report
2022-04-14 19:03:08 [2603]
