Tushar,
Please copy the bit from your smsc log file where you submit the
message and the ID is returned for it and inserted into the database.
Obvioulsy it should be the message that matches the DLR you showed
below, or copy both bits for a new message.
Regards
Ben
On 8 Feb 2007, at 06:06, Tushar wrote:
Hi,
I tried for all the options of msg-id-type but it didn’t work out.
So plz help me out with this DLR stuff
Thanx and regards,
tushar
From: Ben Suffolk [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 08, 2007 12:16 AM
To: Tushar
Cc: [email protected]
Subject: Re: DLR help
Hi Tushar,
I think your problem is maybe related to the message being returned
in hex. You need to look at the bit in the same log where the
message is submitted and what is stored in the DLR table. Sometimes
the message ID format is different in the submit_resp PDU than in
the deliver_sm PDU.
There is a setting called msg-id-type that you might want to look
up in the userguide.
Regards
Ben
----------------------------------------------------------------------
----------------------------------------------------------------------
-----------------------
On 7 Feb 2007, at 12:14, Tushar wrote:
Hi all,
I m configuring kannel message reception. The DLRs
received by kannel is not getting saved MYSQL.. The log of
bearerbox is as follows:-
Please help me with the configuration of DLRs…..
2007-02-07 17:15:51 [15840] [7] DEBUG: Octet string at 0x81cc2f0:
2007-02-07 17:15:51 [15840] [7] DEBUG: len: 113
2007-02-07 17:15:51 [15840] [7] DEBUG: size: 114
2007-02-07 17:15:51 [15840] [7] DEBUG: immutable: 0
2007-02-07 17:15:51 [15840] [7] DEBUG: data: 69 64 3a 34 35 43
42 38 44 35 39 20 73 75 62 3a id:45CB8D59 sub:
2007-02-07 17:15:51 [15840] [7] DEBUG: data: 20 20 30 20 64 6c
76 72 64 3a 20 20 30 20 73 75 0 dlvrd: 0 su
2007-02-07 17:15:51 [15840] [7] DEBUG: data: 62 6d 69 74 20 64
61 74 65 3a 30 37 30 32 30 37 bmit date:070207
2007-02-07 17:15:51 [15840] [7] DEBUG: data: 31 36 35 38 20 64
6f 6e 65 20 64 61 74 65 3a 30 1658 done date:0
2007-02-07 17:15:51 [15840] [7] DEBUG: data: 37 30 32 30 37 31
36 35 39 20 73 74 61 74 3a 44 702071659 stat:D
2007-02-07 17:15:51 [15840] [7] DEBUG: data: 45 4c 49 56 52 44
20 65 72 72 3a 30 30 30 20 54 ELIVRD err:000 T
2007-02-07 17:15:51 [15840] [7] DEBUG: data: 65 78 74 3a 74 65
73 74 20 6d 65 73 73 61 67 65 ext:test message
2007-02-07 17:15:51 [15840] [7] DEBUG: data:
34 4
2007-02-07 17:15:51 [15840] [7] DEBUG: Octet string dump ends.
2007-02-07 17:15:51 [15840] [7] DEBUG: message_state: 2 = 0x00000002
2007-02-07 17:15:51 [15840] [7] DEBUG: receipted_message_id:
"45CB8D59"
2007-02-07 17:15:51 [15840] [7] DEBUG: SMPP PDU dump ends.
2007-02-07 17:15:51 [15840] [7] DEBUG: SMPP[mysmpp] handle_pdu, got
DLR
2007-02-07 17:15:51 [15840] [7] DEBUG: DLR[mysql]: Looking for DLR
smsc=mysmpp, ts=45CB8D59, dst=919820245371, type=1
2007-02-07 17:15:51 [15840] [7] DEBUG: sql: SELECT mask, service,
url, source, destination, boxc FROM dlr WHERE smsc='mysmpp' AND
ts='45CB8D59';
2007-02-07 17:15:51 [15840] [7] DEBUG: no rows found
2007-02-07 17:15:51 [15840] [7] WARNING: DLR[mysql]: DLR for
DST<919820245371> not found.
2007-02-07 17:15:51 [15840] [7] ERROR: SMPP[mysmpp]: got DLR but
could not find message or was not interested in it id<45CB8D59>
dst<919820245371>, type<1>
