Discussion:
bug? command_status field (%A) missing in DLR of split messages
Jeff Thorn
2018-04-11 20:07:16 UTC
Permalink
Hello,
I think we are experiencing a bug in kannel (1.4.4) that does not include
command_status details in the DLR url for long messages that were split.
See the excerpt of the debug log below.

2018-04-11 19:00:38 [30573] [6] ERROR: SMPP[xxxx]: SMSC returned error code
0x0000000b (Invalid Destination Address) in response to submit_sm PDU.
2018-04-11 19:00:38 [30573] [6] DEBUG: Set split msg status to 3
2018-04-11 19:00:38 [30573] [6] DEBUG: Parts of concatenated message failed.
2018-04-11 19:00:38 [30573] [6] DEBUG: SMSC[xxxx]: creating DLR message
2018-04-11 19:00:38 [30573] [6] DEBUG: SMSC[xxxx]: DLR =
https://myurl/api/dlr?status=%d&code=%A&id=123456&dt=%t

Normally for rejected messages the value of the %A parameter is something
like:

NACK/0x0000000b/Invalid Destination Address

However, when the original MT message is a long message that gets split,
the %A parameter in the DLR url looks like this:

NACK/

Is this a known issue? Is there a fix for this?

Thanks,
Jeff Thorn
Jeff Thorn
2018-04-18 19:47:43 UTC
Permalink
Hi Kannel Users,
I wanted to follow up on this issue I reported last week. Has anyone seen
this before? I am having trouble getting the command_status field (%A) in
my dlrs if the original MT message was a long sms message.

Thanks,
Jeff



Jeff Thorn
CEO / Principal Software Architect
Thorn Technologies, LLC
(410) 429-0255
www.thorntech.com
@thorntech <http://twitter.com/thorntech> | LinkedIn
<http://www.linkedin.com/in/jeffthorn> | Facebook
<http://www.facebook.com/thorntechnologies>
Post by Jeff Thorn
Hello,
I think we are experiencing a bug in kannel (1.4.4) that does not include
command_status details in the DLR url for long messages that were split.
See the excerpt of the debug log below.
2018-04-11 19:00:38 [30573] [6] ERROR: SMPP[xxxx]: SMSC returned error
code 0x0000000b (Invalid Destination Address) in response to submit_sm PDU.
2018-04-11 19:00:38 [30573] [6] DEBUG: Set split msg status to 3
2018-04-11 19:00:38 [30573] [6] DEBUG: Parts of concatenated message failed.
2018-04-11 19:00:38 [30573] [6] DEBUG: SMSC[xxxx]: creating DLR message
2018-04-11 19:00:38 [30573] [6] DEBUG: SMSC[xxxx]: DLR =
https://myurl/api/dlr?status=%d&code=%A&id=123456&dt=%t
Normally for rejected messages the value of the %A parameter is something
NACK/0x0000000b/Invalid Destination Address
However, when the original MT message is a long message that gets split,
NACK/
Is this a known issue? Is there a fix for this?
Thanks,
Jeff Thorn
Loading...