You missunderstood me. Source code only selects on db based on ts and smsc. Patch was supposed to add destination matching as well, but looking at the source code never made it. Therefore selects are still done using ts and smsc only. Arguments to the functions include destination, which is, however, not used in the final select.

I don't know how the http smsc will handle this case. Please post logs.

BR,
Nikos
----- Original Message ----- From: "Willy Mularto" <sangpr...@gmail.com>
To: "Nikos Balkanas" <nbalka...@gmail.com>
Cc: <users@kannel.org>
Sent: Friday, April 23, 2010 3:46 AM
Subject: Re: DLR without destination information


Thanks for the reply Nikos, the telco used SMPP before. But now they migrate to HTTP, and on it's new system they don't provide the destination information on DLR. But if we check Kannel architecture, it checks the destination information (I don't use 1.4.3). Do you know the patch name in order to get DLR without destination address?



sangprabv
sangpr...@gmail.com


On Apr 22, 2010, at 9:41 PM, Nikos Balkanas wrote:

Hi,

Interesting. Up till start of 2009, launch of 1.4.3, dlr matching would actually get done only with message_id (ts) and smsc. Sure all calling functions passed also destination, but it was never used in the actual select. That created a problem, since a lot of SMPP smscs used as ts the timestamp to the second, and during high traffic, it didn't guarantee uniqueness. So it was patched to select also based on the destination number.

At that point it was not considered that there were SMScs with DLRs without destination numbers. According to SMPP 3.4 spec SMPP PDUs are not allowed to have destination_addr NULL.

What is your SMSc?

BR,
Nikos
----- Original Message ----- From: "Willy Mularto" <sangpr...@gmail.com>
To: <users@kannel.org>
Sent: Thursday, April 22, 2010 4:43 PM
Subject: DLR without destination information


Hi list,
Is it possible for Kannel to lookup DLR without destination information? Since my telco only send message id, date, and status information. Thanks alot.



sangprabv
sangpr...@gmail.com





Reply via email to