Hi.
I don't really know as I've not used that feature.
Keep in my that in my solution I am tricking Kannel with a VIEW (for
SELECTs) and a couple of TRIGGERs (for UPDATEs).
I think there should be no detectable difference.
Which RDBMS are you using?
2014-11-07 17:43 GMT+01:00 Alvaro Cornejo :
> Hi
Hi Vincenzo
I still wonder how does it is reflected on the status admin page. Does
queued/pending dlr/sms counters grow indefinitely?
Regards
Alvaro
|-|
Envíe y Reciba Datos y mensaje
2014-11-05 18:27 GMT+01:00 Alvaro Cornejo :
>
>> > - use sqlbox.
>>
>> What's that?
>
> Is an additional module that allows you to send/receive sms through a
> database. Instead of calling smsbox for sending an sms, just do an insert on
> a specific table and sqlbox will take care of everything.
I
2014-11-05 17:49 GMT+01:00 Christopher Burke :
> I'm not too sure, I saw the sqlbox as a bit overkill / heavy for my needs. I
> guess they're using insert instead of update as they're not updating a
> record but adding a new record (I.e. Dlrs mean different things, so an
> update is misleading).
>
> > - use sqlbox.
>
> What's that?
Is an additional module that allows you to send/receive sms through a
database. Instead of calling smsbox for sending an sms, just do an insert
on a specific table and sqlbox will take care of everything.
> > - hack kannel code to handle dlr as needed.
>
> Thi
2014-11-05 17:54 GMT+01:00 Alvaro Cornejo :
> Hi
>
> Those sql commands are for kannel internal queue management only. That is
> why there is no UPDATE.
>
> You have 3 options:
>
> - do your own dlr handler. It can be as simple as a php script that receives
> the call and insert info in a database.
Hi
Those sql commands are for kannel internal queue management only. That is
why there is no UPDATE.
You have 3 options:
- do your own dlr handler. It can be as simple as a php script that
receives the call and insert info in a database. You use dlr-url to call it.
- use sqlbox.
- hack kannel co
I'm not too sure, I saw the sqlbox as a bit overkill / heavy for my needs.
I guess they're using insert instead of update as they're not updating a
record but adding a new record (I.e. Dlrs mean different things, so an
update is misleading).
If you want to just store dlr, sqlbox is probably fine,
2014-11-05 16:01 GMT+01:00 Christopher Burke :
> Yeah, I believe that DLR storage can be achieved using the Kannel SQLBox
> project. I think GET-URL is possibly less complex. Depends if you’re only
> storing DLRs or acting on them I guess.
I don't want to write another program when all other bits
Yeah, I believe that DLR storage can be achieved using the Kannel SQLBox
project. I think GET-URL is possibly less complex. Depends if you’re only
storing DLRs or acting on them I guess.
Christopher Burke
http://simulity.com
Office: +44 (0) 1248 679 281
Fax: +44 (0) 1248 660 323
Skype:krslynx
2014-11-05 15:23 GMT+01:00 Christopher Burke :
> Do I need to implement a web service to be linked with the dlr-url
> parameter, of should I simply enable an SQL based dlr-storage?
>
> I use a web service for this. The GET-URL is called, which allows me to
> process the content of the message and
Hi Vincenzo
Yes and no to your first question. You can ask your provider all
intermediate status with dlr-status=31; however it is to operator to decide
which, if any dlr status, they will provide you. They will configure this
on their smsc servers. With modems they usually only gives you final dl
This means that, for example, if I
submit a message that cannot be delivered immediately (for some
reason) I should get a DLR for "enqueueing to the SMSC" and later on
one for the actual delivery to the handset.
Is this true?
Yes - you’ll get a DLR from the SMPP interface (depending on whom p
**>Date: Fri, 25 Feb 2005 16:20:08 +0200
**>From: Kaspars Foigts <[EMAIL PROTECTED]>
**>To: users@kannel.org
**>Subject: DLR handling
**>
**>
**> Hello!
**>
**> I got a problem with DLR handling in Kannel (latest). When kannel
**> submits short message via SMPP v3.4, it receives message_id in
**
14 matches
Mail list logo
