Hi,

you have to restart kannel if you changed it.
if this still not work, please post debug logs for submit_sm and deliver_sm with SQLs.

Thanks,
Alex

jyotiranjan panda schrieb:
Hi Alex,

 I have tryed with msg-id-type = 1.
 But kannel is showing same error as before.

Thanks & Regards
Jyoti Ranjan Panda

On Wed, Mar 4, 2009 at 4:16 PM, Alexander Malysh <[email protected] <mailto:[email protected]>> wrote:

    Hi,

    try msg-id-type = 1

    Thanks,
    Alex

    jyotiranjan panda schrieb:

        Still Waiting For suggestion...................................

        Regards
        Jyoti Ranjan Panda

        On Wed, Mar 4, 2009 at 9:40 AM, jyotiranjan panda
        <[email protected] <mailto:[email protected]>
        <mailto:[email protected] <mailto:[email protected]>>> wrote:

           Hi ,

           Waiting for any opnion.

           Regards
           Jyoti Ranjan Panda


           On Tue, Mar 3, 2009 at 5:47 PM, jyotiranjan panda
           <[email protected] <mailto:[email protected]>
        <mailto:[email protected] <mailto:[email protected]>>> wrote:

               Hi,
               I am using kannel-1.4.3, when I am sending message kannel
        shows
               the below error.

               2009-03-03 15:42:50 [5575] [6] WARNING: DLR[internal]:
        DLR from
               SMSC<hrtestgw1> for DST<919911274740> not found.

               2009-03-03 15:42:50 [5575] [6] ERROR: SMPP[hrtestgw1]:
        got DLR
               but could not find message or was not interested in it
               id<55857128> dst<919911274740>, type<1>

               from this error I came to know that I have to configure
               msg-id-type, since the *message-id* of submit_sm_resp is
        in HEX
               where as the deliver_sm is in DECIMAL.
               i.e
                 type_name: submit_sm_resp
               2009-03-03 15:42:46 [5575] [6] DEBUG:   command_id:
        2147483652 =
               0x80000004
               2009-03-03 15:42:46 [5575] [6] DEBUG:   command_status: 0 =
               0x00000000
               2009-03-03 15:42:46 [5575] [6] DEBUG:   sequence_number: 2 =
               0x00000002
               2009-03-03 15:42:46 [5575] [6] DEBUG:   message_id: "3544FE8"
               2009-03-03 15:42:46 [5575] [6] DEBUG: SMPP PDU dump ends.
               2009-03-03 15:42:50 [5575] [6] DEBUG: SMPP[hrtestgw1]:
        Got PDU:
               2009-03-03 15:42:50 [5575] [6] DEBUG: SMPP PDU 0x9d596a8
        dump:
               2009-03-03 15:42:50 [5575] [6] DEBUG:   type_name: deliver_sm
               2009-03-03 15:42:50 [5575] [6] DEBUG:   command_id: 5 =
        0x00000005
               2009-03-03 15:42:50 [5575] [6] DEBUG:   command_status: 0 =
               0x00000000
               2009-03-03 15:42:50 [5575] [6] DEBUG:   sequence_number: 1 =
               0x00000001
               2009-03-03 15:42:50 [5575] [6] DEBUG:   service_type: NULL
               2009-03-03 15:42:50 [5575] [6] DEBUG:   source_addr_ton: 1 =
               0x00000001
               2009-03-03 15:42:50 [5575] [6] DEBUG:   source_addr_npi: 1 =
               0x00000001
               2009-03-03 15:42:50 [5575] [6] DEBUG:   source_addr:
        "919911274740"
               2009-03-03 15:42:50 [5575] [6] DEBUG:   dest_addr_ton: 2 =
               0x00000002
               2009-03-03 15:42:50 [5575] [6] DEBUG:   dest_addr_npi: 1 =
               0x00000001
               2009-03-03 15:42:50 [5575] [6] DEBUG:   destination_addr:
        "TM-AMEX"
               2009-03-03 15:42:50 [5575] [6] DEBUG:   esm_class: 4 =
        0x00000004
               2009-03-03 15:42:50 [5575] [6] DEBUG:   protocol_id: 0 =
        0x00000000
               2009-03-03 15:42:50 [5575] [6] DEBUG:   priority_flag: 0 =
               0x00000000
2009-03-03 15:42:50 [5575] [6] DEBUG: schedule_delivery_time: NULL
               2009-03-03 15:42:50 [5575] [6] DEBUG:   validity_period: NULL
2009-03-03 15:42:50 [5575] [6] DEBUG: registered_delivery: 0 =
               0x00000000
2009-03-03 15:42:50 [5575] [6] DEBUG: replace_if_present_flag:
               0 = 0x00000000
               2009-03-03 15:42:50 [5575] [6] DEBUG:   data_coding: 0 =
        0x00000000
2009-03-03 15:42:50 [5575] [6] DEBUG: sm_default_msg_id: 0 =
               0x00000000
               2009-03-03 15:42:50 [5575] [6] DEBUG:   sm_length: 108 =
        0x0000006c
               2009-03-03 15:42:50 [5575] [6] DEBUG:   short_message:
               2009-03-03 15:42:50 [5575] [6] DEBUG:    Octet string at
        0x9d586b8:
               2009-03-03 15:42:50 [5575] [6] DEBUG:      len:  108
               2009-03-03 15:42:50 [5575] [6] DEBUG:      size: 109
               2009-03-03 15:42:50 [5575] [6] DEBUG:      immutable: 0
               2009-03-03 15:42:50 [5575] [6] DEBUG:      data: 69 64 3a
        35 35
               38 35 37 31 32 38 20 73 75 62 3a   id:55857128 sub:
               2009-03-03 15:42:50 [5575] [6] DEBUG:      data: 30 30 30
        20 64
               6c 76 72 64 3a 30 30 31 20 73 75   000 dlvrd:001 su
               2009-03-03 15:42:50 [5575] [6] DEBUG:      data: 62 6d 69
        74 20
               64 61 74 65 3a 30 39 30 33 30 33   bmit date:090303
               2009-03-03 15:42:50 [5575] [6] DEBUG:      data: 30 33 35
        35 20
               64 6f 6e 65 20 64 61 74 65 3a 30   0355 done date:0
               2009-03-03 15:42:50 [5575] [6] DEBUG:      data: 39 30 33
        30 33
               30 33 35 35 20 73 74 61 74 3a 44   903030355 stat:D
               2009-03-03 15:42:50 [5575] [6] DEBUG:      data: 45 4c 49
        56 52
               44 20 65 72 72 3a 30 30 30 20 74   ELIVRD err:000 t
               2009-03-03 15:42:50 [5575] [6] DEBUG:      data: 65 78 74
        3a 35
               35 38 35 37 31 32 38               ext:55857128

               But when I am configuring msg-id-type = 0x01,
               Kannel is repeting the same error as before.

               Regards
               Jyoti Ranjan Panda








Reply via email to