Hi Jeff,
it makes maybe sense for your case but not for all cases, therefore I don’t see
a sense to invest time into it.
Thanks,
Alex
> Am 02.06.2018 um 15:26 schrieb Jeff Thorn :
>
> Hi Alex,
> Thanks for explaining, makes sense.
>
> The most common status we get is invalid destination add
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 Technologie
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 Thor
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
