Re: Again SMPP DLR

Hi
At 02:26 PM 8/16/02 +0500, David Chkhartishvili wrote:
>Hi All,
>
>I've sent few messages regarding "got DLR but could not find message or 
>was not interested in it", but didn't get any answer.


this is probabally because the smscs use different std for the format of 
the msg_id in the submit_sm_resp and deliver_sm.. they use hex or decimal 
or a mixture...

I have a patch that lets you set them independently, I will extract and 
post it to the list later today..

The config file works like this.
smpp-msg-id-type;

bit 1 submit_sm_resp bit 2 deliver_sm
if he bit is set the value is hex

0x00 deliver_sm decimal, submit_sm_resp decimal
0x01 (default) deliver_sm decimal, submit_sm_resp hex
0x02 deliver_sm hex, submit_sm_resp decimal
0x03 deliver_sm hex, submit_sm_resp hex *

nisan


>I'm asking for help again, because that issue is very important for me.
>
>Here is problem description:
>
>kannel-snapshot, smsc_smpp debug switched on.
>SMPP DLR with mysql storage.
>
>Every time I submit message I get:
>ERROR: SMPP[test]: got DLR but could not find message or was not 
>interested in it
>
>Here is dump of smpp  submit_sm_resp:
>
>SMPP[test]: Got PDU:
>2002-08-16 14:08:44 [5] DEBUG: SMPP PDU 0x80d3f60 dump:
>2002-08-16 14:08:44 [5] DEBUG:   type_name: submit_sm_resp
>2002-08-16 14:08:44 [5] DEBUG:   command_id: 2147483652 = 0x80000004
>2002-08-16 14:08:44 [5] DEBUG:   command_status: 0 = 0x00000000
>2002-08-16 14:08:44 [5] DEBUG:   sequence_number: 2 = 0x00000002
>2002-08-16 14:08:44 [5] DEBUG:   message_id:
>2002-08-16 14:08:44 [5] DEBUG:    Octet string at 0x80d4210:
>2002-08-16 14:08:44 [5] DEBUG:      len:  50
>2002-08-16 14:08:44 [5] DEBUG:      size: 51
>2002-08-16 14:08:44 [5] DEBUG:      immutable: 0
>2002-08-16 14:08:44 [5] DEBUG:      data: 46 46 46 46 31 34 3a 30   FFFF14:0
>2002-08-16 14:08:44 [5] DEBUG:      data: 38 3a 34 32 3a 30 32 38   8:42:028
>2002-08-16 14:08:44 [5] DEBUG:      data: 31 20 30 38 2d 31 36 2d   1 08-16-
>2002-08-16 14:08:44 [5] DEBUG:      data: 32 30 30 32 20 30 30 39   2002 009
>2002-08-16 14:08:44 [5] DEBUG:      data: 37 34 36 38 34 31 36 20   7468416
>2002-08-16 14:08:44 [5] DEBUG:      data: 30 30 39 38 30 32 37 30   00980270
>2002-08-16 14:08:44 [5] DEBUG:      data: 30 34                     04
>2002-08-16 14:08:44 [5] DEBUG:    Octet string dump ends.
>2002-08-16 14:08:44 [5] DEBUG: SMPP PDU dump ends.
>
>
>deliver_sm:
>
>SMPP[test]: Got PDU:
>2002-08-16 14:08:49 [5] DEBUG: SMPP PDU 0x80d41c8 dump:
>2002-08-16 14:08:49 [5] DEBUG:   type_name: deliver_sm
>2002-08-16 14:08:49 [5] DEBUG:   command_id: 5 = 0x00000005
>2002-08-16 14:08:49 [5] DEBUG:   command_status: 0 = 0x00000000
>2002-08-16 14:08:49 [5] DEBUG:   sequence_number: 1 = 0x00000001
>2002-08-16 14:08:49 [5] DEBUG:   service_type: ""
>2002-08-16 14:08:49 [5] DEBUG:   source_addr_ton: 2 = 0x00000002
>2002-08-16 14:08:49 [5] DEBUG:   source_addr_npi: 1 = 0x00000001
>2002-08-16 14:08:49 [5] DEBUG:   source_addr: "99599182418"
>2002-08-16 14:08:49 [5] DEBUG:   dest_addr_ton: 2 = 0x00000002
>2002-08-16 14:08:49 [5] DEBUG:   dest_addr_npi: 1 = 0x00000001
>2002-08-16 14:08:49 [5] DEBUG:   destination_addr: "432"
>2002-08-16 14:08:49 [5] DEBUG:   esm_class: 4 = 0x00000004
>2002-08-16 14:08:49 [5] DEBUG:   protocol_id: 0 = 0x00000000
>2002-08-16 14:08:49 [5] DEBUG:   priority_flag: 0 = 0x00000000
>2002-08-16 14:08:49 [5] DEBUG:   schedule_delivery_time: ""
>2002-08-16 14:08:49 [5] DEBUG:   validity_period: ""
>2002-08-16 14:08:49 [5] DEBUG:   registered_delivery: 0 = 0x00000000
>2002-08-16 14:08:49 [5] DEBUG:   replace_if_present_flag: 0 = 0x00000000
>2002-08-16 14:08:49 [5] DEBUG:   data_coding: 0 = 0x00000000
>2002-08-16 14:08:49 [5] DEBUG:   sm_default_msg_id: 0 = 0x00000000
>2002-08-16 14:08:49 [5] DEBUG:   sm_length: 0 = 0x00000000
>2002-08-16 14:08:49 [5] DEBUG:   short_message: ""
>2002-08-16 14:08:49 [5] DEBUG: SMPP PDU dump ends.
>
>deliver_sm_resp:
>SMPP[test]: Sending PDU:
>2002-08-16 14:08:49 [5] DEBUG: SMPP PDU 0x80d40b8 dump:
>2002-08-16 14:08:49 [5] DEBUG:   type_name: deliver_sm_resp
>2002-08-16 14:08:49 [5] DEBUG:   command_id: 2147483653 = 0x80000005
>2002-08-16 14:08:49 [5] DEBUG:   command_status: 0 = 0x00000000
>2002-08-16 14:08:49 [5] DEBUG:   sequence_number: 1 = 0x00000001
>2002-08-16 14:08:49 [5] DEBUG:   message_id: NULL
>2002-08-16 14:08:49 [5] DEBUG: SMPP PDU dump ends.
>
>As you see, deliver_sm doesn't conatin any short_message, also 
>deliver_sm_resp contains no message_id.
>Please clarify, is it SMSC problem (may be message_id?) or SMPP DLR module.
>
>Looking forward for your response.
>
>Thank you.
>
>--
>David Chkhartishvili
>
>
>
>