Re: SMS command_status for long MT messages

[Jeff Thorn]

Hi Alex,
Thanks for explaining, makes sense.

The most common status we get is invalid destination address (0x000b).
In this case all 3 parts in your example would have the same status. Would
it make sense to include the status of it was the same for all parts?

Jeff Thorn
CEO
Thorn Technologies, LLC
https://www.thorntech.com

On Sat, Jun 2, 2018, 8:09 AM  wrote:

> Hi,
>
> this is expected behaviour because we have to put all statuses into one
> DLR message.
> Just imagine if you have 3 parts and each of this part will be rejected
> with different error code,
> would you expect all 3 error codes in the status?
>
> Thanks,
> Alex
>
>
> Am 30.05.2018 um 20:50 schrieb Jeff Thorn :
>
> 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[]: SMSC returned error
> code 0x000b (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[]: creating DLR message
> 2018-04-11 19:00:38 [30573] [6] DEBUG: SMSC[]: DLR =
> https://myurl/api/dlr?status=%d=%A=123456=%t
>
> Normally for rejected messages the value of the %A parameter is something
> like:
>
> NACK/0x000b/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  | LinkedIn
>  | Facebook
> 
>
>
>

Re: SMS command_status for long MT messages

[amalysh]

Hi,

this is expected behaviour because we have to put all statuses into one DLR 
message.
Just imagine if you have 3 parts and each of this part will be rejected with 
different error code,
would you expect all 3 error codes in the status?

Thanks,
Alex


> Am 30.05.2018 um 20:50 schrieb Jeff Thorn :
> 
> 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[]: SMSC returned error code 
> 0x000b (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[]: creating DLR message
> 2018-04-11 19:00:38 [30573] [6] DEBUG: SMSC[]: DLR = 
> https://myurl/api/dlr?status=%d; 
> code=%A=123456=%t
> 
> Normally for rejected messages the value of the %A parameter is something 
> like:
> 
> NACK/0x000b/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  | LinkedIn 
>  | Facebook 
>