Kannel hits the dlr-url wherever a dlr "event" occurs. Even if your carrier
doesn't send you dlr messages, kannel generates some dlr "events" by itself.
For example, when the carrier accepts or rejects a message.

Those messages does not generate traffic over the SMPP link (apart from the
submit_sm / submit_sm_response of course) but they generate a hit to the
dlr-url anyway. I used to joke about this being "false dlrs" (because
they're not being generated after a deliver_sm PDU).

I hope this clarifies things a little more.

Regards,

Alejandro

On Thu, Sep 18, 2008 at 6:29 PM, Gustavo Mohme C. <[EMAIL PROTECTED]> wrote:

> That would be great! What you mean that "dlr" will come from Kannel itself?
> Thanks,
> Gustavo
>
>
> On Thu, Sep 18, 2008 at 3:50 PM, Alejandro Guerrieri <
> [EMAIL PROTECTED]> wrote:
>
>> I'm finishing a patch to be able to grab the submit_sm_resp message_id
>> field and use it with a paremter on the dlr-url (I've chose the "%w"
>> parameter for this). You'll need a mask anyway, only that the "dlr" won't
>> come from the carrier but from inside kannel itself.
>>
>> Will post it to the list later so it can be also tested by other people.
>>
>> Stay tuned ;)
>>
>> Regards,
>>
>> Alejandro
>>
>>
>>
>> On Thu, Sep 18, 2008 at 4:49 PM, Gustavo Mohme C. <[EMAIL PROTECTED]>wrote:
>>
>>>
>>> Hi All,
>>> I am currently using mask=31. Nevertheless, it is generating unnecessary
>>> traffic since I am only interested in getting the message_id from the
>>> submit_sm_resp. Is there a way to get the message_id without using mask=#?
>>>  The reason I only need to get the message_id is because, after the id is
>>> stored, I use query_sm to check the status(SMSC doesn't support DLR) of the
>>> message. What would be the simplest mask value that would get this job
>>> done(mask=1 maybe?).
>>> Thanks a lot!
>>> Gustavo
>>>
>>>
>>
>

Reply via email to