We assume you have set your dlr-mask. Try to set dlr-mask=8 , all ACK assume as 
success while others are failed. This will be related to your back end 
script/programming. 


Willy Mularto
SMS Gateway, Content Provider, Mobile Solution Specialist
M: +62811923464, +62818923464
PIN BBM: 74924429



On Feb 7, 2014, at 2:17 AM, dhcmega <dhcad...@gmail.com> wrote:

> Ok, my service provider is telling this to me:
> 
> "These result codes are additional to the SMPP protocol specific codes. These 
> codes are sent in the command_status field."
> 
> And there is a huge list of codes.
> Could this be my problem?
> Thanks
> 
> 
> 
> 
> On Thu, Feb 6, 2014 at 3:21 PM, dhcmega <dhcad...@gmail.com> wrote:
> Hi all
> It looks like that when I receive a command_status: 0, there is no DLR 
> notification triggered, like in this response:
> 
> 2014-02-06 14:33:22 [21859] [6] DEBUG: SMPP[smsc_conn_1]: Got PDU:
> 2014-02-06 14:33:22 [21859] [6] DEBUG: SMPP PDU 0x2aaaac0720d0 dump:
> 2014-02-06 14:33:22 [21859] [6] DEBUG:   type_name: submit_sm_resp
> 2014-02-06 14:33:22 [21859] [6] DEBUG:   command_id: 2147483652 = 0x80000004
> 2014-02-06 14:33:22 [21859] [6] DEBUG:   command_status: 0 = 0x00000000
> 2014-02-06 14:33:22 [21859] [6] DEBUG:   sequence_number: 2309 = 0x00000905
> 2014-02-06 14:33:22 [21859] [6] DEBUG:   message_id: "d1e113b"
> 2014-02-06 14:33:22 [21859] [6] DEBUG: SMPP PDU dump ends.
> 
> 
> if the command_status is not 0, like this:
> 
> 
> 2014-02-06 14:34:02 [21859] [6] DEBUG: SMPP PDU 0x2aaaac0720d0 dump:
> 2014-02-06 14:34:02 [21859] [6] DEBUG:   type_name: submit_sm_resp
> 2014-02-06 14:34:02 [21859] [6] DEBUG:   command_id: 2147483652 = 0x80000004
> 2014-02-06 14:34:02 [21859] [6] DEBUG:   command_status: 1003 = 0x000003eb
> 2014-02-06 14:34:02 [21859] [6] DEBUG:   sequence_number: 2312 = 0x00000908
> 2014-02-06 14:34:02 [21859] [6] DEBUG:   message_id: "d1e357d"
> 2014-02-06 14:34:02 [21859] [6] DEBUG: SMPP PDU dump ends.
> 
> 
> Then I get the DLR notification.
> Do I have a configuration error?
> Thanks
> 
> dhcmega
> 
> 
> 
> 
> 

Reply via email to