SMS command_status for long MT messages

Hi group,
Looking for a little help on this.... The DLR command status flag (%A)
appears blank when the original MT message was a long message ( > 160
chars).

Is there a solution to this issue?  Here is an example from our logs.....

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/

Any feedback is appreciated. Thanks!


Jeff Thorn
CEO / Principal Software Architect
Thorn Technologies, LLC
www.thorntech.com
@thorntech <http://twitter.com/thorntech> | LinkedIn
<http://www.linkedin.com/in/jeffthorn> | Facebook
<http://www.facebook.com/thorntechnologies>