Just assign a different dlr-url for each message that you sent.

It is what Alvaro meant as well...

== Rene

-----Original Message-----
From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of dorian
Sent: Thursday, 16 September, 2010 21:28
To: Alvaro Cornejo
Cc: users@kannel.org
Subject: Re: sms - dlr bounding

Thanks a lot for reply.

Using the sqlbox I see now the MT and DLR record in the database which
has the same 'dlr_url' field with my id and it looks like the problem is
solved.

Anyway is it the only solution?

The 'dlr_url' field contains the whole http link which for me is
completely useless and is needlessly long as the only sms id is interesting.

Next subject is that having database I do not need to fire up any http
url when delivery report is sent back. It waste of CPU time only.
So I am looking for something which could give me same/similar results
in database without necessity of creating dlr http site Such site is
completely useless for me.



> you need to add your own different id to each of your messages in the
> dlr-url you send with the message.
>
>
>
|---------------------------------------------------------------------------
--------------------------------------|
> Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
> celular y Nextel
> en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
> SMS y GPRS online
>               Visitenos en www.perusms.NET www.smsglobal.com.mx y
> www.pravcom.com
>
>
>
> 2010/9/16 dorian <doria...@o2.pl>:
>   
>> Let's assume that I am sending 3 sms'es (MTs) to switched off terminal.
>> Next the terminal is switched on.
>> Let's assume the only 2 of them are delivered.
>>
>> The (maybe stupid) question is:
>> how to find out which dlr report refers to which sms sent?
>>
>> I cannot find a "key" which could be used to "bind" dlr report with sms
>> as a result I don't know how to detect which sms has been discarded.
>>
>> I am using bearerbox-sqlbox-smsbox with CIMD2 smsc.
>>
>>
>> Regards
>> Dorian
>>
>>
>>
>>     
>
>   





Reply via email to