Hello,
We have a connection to a carrier using SMPP and some intermediate DLRs
are considered by kannel as final.
The typical message sent is:
2018-10-18 15:30:49 [13585] [9] DEBUG: SMPP PDU 0x7f8c3c0052a0 dump:
2018-10-18 15:30:49 [13585] [9] DEBUG: type_name: submit_sm
2018-10-18
Subject: RE: SMPP DLR
Hi,
Yes. Rene is correct.
I think that I was misreading the SMPP v3.4 Section 5.2.17
"registered_delivery".
If I set the value to 1. Everything appears to work up to a point. I see DLR
records created in my bearerbox DLR queue and in my opensmppbox DLR queue.
rom: devel [mailto:devel-boun...@kannel.org] On Behalf Of Porter, Kelvin
Sent: Friday, February 14, 2014 3:45 PM
To: Rene Kluwen
Cc: de...@kannel.org
Subject: RE: SMPP DLR
Hi,
Thank you for the corrections. I will investigate further.
Regards,
Kelvin R. Porter
From: Rene Kluwen [mailto:rene.klu...
Hi
On your dlr-url just add a field where you set your own id i.e.
...&my_id=1234&...
Then the app/script that receives the dlr-url call will get that value
and do the magic you need.
Regards
Alvaro
|--
Hi all,
I need to have some relation b/w the sms I send out from kannel and the dlr
that is received.
e.g. like a custom message ID I send along with my sendsms URL, the dlr-url
should have that same sms id in one of the parameters
Can this be acheived? How?
Thanks.
Kluwen [mailto:rene.klu...@chimit.nl]
Sent: Thursday, February 13, 2014 5:12 AM
To: Porter, Kelvin; users@kannel.org
Subject: RE: SMPP DLR
I see that's a bug in opensmppbox.
Try to set registered_delivery to 1 instead, meanwhile I come up with a fix.
== Rene
From: users [mailto:users
I see thats a bug in opensmppbox.
Try to set registered_delivery to 1 instead, meanwhile I come up with a fix.
== Rene
From: users [mailto:users-boun...@kannel.org] On Behalf Of Porter, Kelvin
Sent: woensdag 12 februari 2014 23:52
To: users@kannel.org
Subject: SMPP DLR
Hi,
I
Hi,
I have a simple problem. I have the following set up:
Client -[SMPP]--> opensmppbox --> sqlbox --> bearerbox
-[SMPP]--> SMSC
My clients sends a submit_sm request into the opensmppbox, I can see that the
submit_sm message is marked requested_delivery: 31 = 0x001f in the
If kannel receives a dlr that it is not waiting for -its reccord was
deleted on kannel restart- kannel will issue a warning that does not
know what to do with it and discart it.
Regards
Alvaro
On 7/24/13, spameden wrote:
> If you need to keep DLR you need to use spool or file storage and store
If you need to keep DLR you need to use spool or file storage and store DLR
in database so kannel could match DLR after restart.
2013/7/24 Rudy Matela
> Hello, Qqblog,
>
> Someone correct me if I'm wrong.
>
> When using internal storage for DLRs, to keep interpreting DLRs after a
> restart you'
Hello, Qqblog,
Someone correct me if I'm wrong.
When using internal storage for DLRs, to keep interpreting DLRs after a
restart you'll have to use a spool (or file) to backup message state. That
way, kannel will treat the DLRs that arrive for messages already sent.
That can be done in the core
If DLR is empty queue after restarting kannel with internal storage, does
kannel still receive DLR and run DLR-URL when SMPP send back DLR ?
Hi!
> Hello,
> i'm suppose i'm facing a similar problem as alexander bukharin below.
> kannel is looking for the id<905343726889613> and can not find it.
> i would be thankfull if someone had an idea where to look for the mistake.
> 2007-10-10 22:48:28 [17639] [7] DEBUG: DLR[internal]: Looking
Hello,
i'm suppose i'm facing a similar problem as alexander bukharin below.
kannel is looking for the id<905343726889613> and can not find it.
i would be thankfull if someone had an idea where to look for the mistake.
2007-10-10 22:48:28 [17639] [7] DEBUG: DLR[internal]: Looking for DLR
smsc=
Hi,
on SMPP 3.4 and above kannel will always try to use receipted_message_id: if
this present. There is 100% bug at SMSC because receipted_message_id: must
be the same as in submit_sm_resp. You should contact your SMSC operator or
you can try to switch to version 3.3 (see userguide).
Alexander Bu
Hello! After i changed source-addr-ton to 5 and source-addr-npi to 0
(it was 1 and 1 before) kannel started to interpret message id in
deliver_sm SMPP message in a wrong way:
2007-08-09 11:18:26 [2769] [6] DEBUG: SMPP[smpp]: Manually forced source addr
ton = 5, source add npi = 0
2007-08-09 11:18:
u receive the DLR's via an smpp connection called
(see previous posts)
Tom
> **>Date: Tue, 1 Feb 2005 16:57:11 +0100 (CET)
> **>Subject: Re: smpp DLR problem
> **>From: <[EMAIL PROTECTED]>
> **>To:
> **>In-Reply-To: <[EMAIL PROTECTED]>
> **>
Tom --
The message ID is handed to you in HEX, 459D58BB -> 1167939771 (hex to
binary). Your DLR report (delivery receipt) comes with id:1167939771 thus
matching your message.
http://kannel.org/download/1.3.2/userguide-1.3.2/userguide.html#AEN1535
Look at msg-id-type. This tells kannel about the t
**>Date: Tue, 1 Feb 2005 16:57:11 +0100 (CET)
**>Subject: Re: smpp DLR problem
**>From: <[EMAIL PROTECTED]>
**>To:
**>In-Reply-To: <[EMAIL PROTECTED]>
**>
**>Hello Dave,
**>
**>thanks for your answer,
**>
**>Here is a dump of the smpp transactions, h
2-01 16:36:57 [6119] [7] ERROR:
SMPP[]: got DLR but could
not find message or was not interestedin it ts<1167939771>
dst<32XXXX>, type<1>
Regards,
Tom
> **>Date: Tue, 1 Feb 2005 14:42:47 +0100 (CET)
> **>Subject: smpp DLR problem
> **>From: <[EMAIL PROTECTED]>
**>Date: Tue, 1 Feb 2005 14:42:47 +0100 (CET)
**>Subject: smpp DLR problem
**>From: <[EMAIL PROTECTED]>
**>To:
**>
**>i have this weird problem with DLR reports and SMPP that is breaking my
**>head. DLR reporting seems to work fine for the other EMI connections but
**&
Hello all,
i have this weird problem with DLR reports and SMPP that is breaking my
head. DLR reporting seems to work fine for the other EMI connections but
the SMPP connection however gives
WARNING: DLR[internal]: DLR for DST<32> not found.
2005-02-01 13:51:16 [15102] [7] ERROR: SMPP[]: g
22 matches
Mail list logo
