sent_sms table.
> You have a quote mismatch in that INSERT statement.
>
> -Original Message-
> From: dorian [mailto:doria...@o2.pl]
> Sent: Thursday, 07 October, 2010 08:32
> To: Rene Kluwen
> Cc: 'Alejandro Guerrieri'; users@kannel.org
> Subject: Re: sms - dl
You have a quote mismatch in that INSERT statement.
-Original Message-
From: dorian [mailto:doria...@o2.pl]
Sent: Thursday, 07 October, 2010 08:32
To: Rene Kluwen
Cc: 'Alejandro Guerrieri'; users@kannel.org
Subject: Re: sms - dlr bounding
Rene,
Thanks a lot a lot for
e with boxc_id the same as you defined as sqlbox-id.
>
> Judging from your emails, I think this is what you want.
>
> == Rene
>
> -Original Message-
> From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of
> dorian
> Sent: Friday, 17 S
ilto:users-boun...@kannel.org] On Behalf Of
dorian
Sent: Friday, 17 September, 2010 11:33
To: Alejandro Guerrieri
Cc: users@kannel.org
Subject: Re: sms - dlr bounding
Well. I know the difference between fork and pthread_create.
Anyway the http client work (even if it is thread not a process) is
waste
inal Message -
From: "dorian"
To: "Alejandro Guerrieri"
Cc:
Sent: Friday, September 17, 2010 12:32 PM
Subject: Re: sms - dlr bounding
Well. I know the difference between fork and pthread_create.
Anyway the http client work (even if it is thread not a process) is
waste of t
and then there is no need for dlr handling at all.
> > >
> > >
> > >>> Hi,
> > >>>
> > >>> The "exec" script is another process started each time and is
> more
> > >>> exp
is another process started each time and is more
> >>> expensive than attempting to fetch a dlr-url. The http server,
> >>> initially takes up some resources (memory) but it remains
> constant and
> >>> CPU utilization is overall lower.
>
;> Hi,
> >>>
> >>> The "exec" script is another process started each time and is more
> >>> expensive than attempting to fetch a dlr-url. The http server,
> >>> initially takes up some resources (memory) but it remains constant and
> >
to fetch a dlr-url. The http server,
>>> initially takes up some resources (memory) but it remains constant and
>>> CPU utilization is overall lower.
>>>
>>> That's the whole purpose of the dlr-url. To get your dlrs in a databse
>>> in the format
s (memory) but it remains constant and
> > CPU utilization is overall lower.
> >
> > That's the whole purpose of the dlr-url. To get your dlrs in a databse
> > in the format that you want.
> >
> > BR,
> > Nikos
> > - Original Message - From:
ll lower.
>
> That's the whole purpose of the dlr-url. To get your dlrs in a databse
> in the format that you want.
>
> BR,
> Nikos
> - Original Message ----- From: "dorian"
> To: "Alvaro Cornejo"
> Cc:
> Sent: Friday, September 17, 2010 1:
rl. To get your dlrs in a databse in
the format that you want.
BR,
Nikos
- Original Message -
From: "dorian"
To: "Alvaro Cornejo"
Cc:
Sent: Friday, September 17, 2010 1:06 AM
Subject: Re: sms - dlr bounding
There is nothing magical in sqlbox.
It sits betwe
There is nothing magical in sqlbox.
It sits between bearerbox and smsbox and it just records data in the
database.
Each message = 1 record in the table independetly if the message is
outgoing sms (MT) , incoming sms (MO) or delivery report.
It is nice and simple way to have a full history of commun
How it works is, once kannel receives a dlr, it matches against its
dlr database, if got a macth, it then calls your own dlr-url to
trigger your own application so you can reccord the status and do
whatever you want with it. If the dlr is for a final status, the
kannel deletes that dlr reccord.
Wi
@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
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
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
celul
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" d
18 matches
Mail list logo
