Ok, are you sure that the carrier has enabled DLR's for your account?
Regards,
Alejandro
On 8/15/07, Ady Wicaksono [EMAIL PROTECTED] wrote:
Kannel don't even recognized this MO SMS as DLR, so kannel hit my default
SMS handler
not dlr-url :)
dlr-url is urlencoded
On 8/15/07, Alejandro
Ady,
From what I understand, you send a message and gets loaded on the dlr
table, but when the dlr comes back (it comes back, right) kannel does
not recognize it and the dlr stays forever on the table?
Or, kannel recognizes it but doesn't hit dlr-url?
First of all, check the logs and make sure
I have one SMSC connection and already setup DLR for kannel.
I use DLR-MySQL with configuration like this
--- cut here -
group = dlr-db
id = mydlr
table = t_kannel_dlr
field-smsc = smsc
field-timestamp = timestamp
field-destination = destination
field-source = source
Ady,
Check the user guide for the %d parameter, it's what you're looking for.
Regards,
Alejandro
On 8/12/07, Ady Wicaksono [EMAIL PROTECTED] wrote:
I have one SMSC connection and already setup DLR for kannel.
I use DLR-MySQL with configuration like this
--- cut here -
Hi Alejandro
The problem is not on delivery report value itself. The problem is, I need
to know which message is delivered, or undelivered
I send SMS A (submit_sm) -- to kannel HTTP Service only got status
Accepted for delivery.
By common case, kannel will maintain SMSC, one kannel found DLR it
Ady,
Have you really _read_ the docs? Think about a little, what purpose
could have a dlr engine if you cannot have a mean to identify each
particular message?
The %d parameter carries the message id, so you can identify the
delivery when it gets back.
Pass the %d parameter on the dlr-url, and
I think we have a little missunderstanding :)
the problem is dlr-url is not working :)
if when DLR comes and kannel could detect it then it should be hit dlr-url
right?
the problem is, kannel never hit dlr-url I defined when doing submit SMS
On 8/13/07, Alejandro Guerrieri [EMAIL PROTECTED]
