Well it is actually a bug, but i am not sure how often it happens. The
correct behaviour would be for smsbox to know the parts of the original sms
and call the OK dlr-url only when all parts to the original SMS are
delivered OK. Imagine 2 parts of a 3-part sms are delivered and something
happens (line dropped, etc.) and the 3rd part is never sent. 3rd DLR by SMSc
could be failure. But kannel will treat this as success, because the first
part was delivered OK.
This is not actually frequent, since most of SMSc failures are temporary and
the SMSc has a queue and will retry. But what if a permanent one happens?
BR,
Nikos
----- Original Message -----
From: Alejandro Guerrieri
To: Ivan Kurnosov
Cc: Nikos Balkanas ; [email protected]
Sent: Wednesday, September 15, 2010 4:36 PM
Subject: Re: registered_delivery and multi-parts message
Yes. I wouldn't call it a bug, it was a design decision. Of course you're
absolutely entitled to disagree with it and change it on your local tree, as
you already did :)
Now, the issue is, since you define one dlr-url (probably with a unique id
you created) and Kannel splits the message into 2 or 3 parts, you'd get 2 or
3 hits on that URL, sharing the same id. Are you sure that that's what you
want?
Regards,
Alex
On Wed, Sep 15, 2010 at 1:24 PM, Ivan Kurnosov <[email protected]> wrote:
Actually, I can ;-) I already fixed kannel (to be clear - i've just
commented 3 lines of code) to send only one DLR msg. So now I get N
delivery messages.
But I'm very curious - is it just kannel "feature" or some smpp
specification mandatory? I've asked this question because one of my
SMSC (currently i'm working with 3 different companies) does not send
me delivery messages if it is 0x1 just at first and not at second
message. So I need to know whether I need to ask their support to
reconfigure SMSC or make some tricks to get that info
2010/9/15 Nikos Balkanas <[email protected]>:
Hi,
This is a known kannel limitation. In a multpart SMS it will request DLR
only for the first part. Nothing you can do about it.
BR,
Nikos
----- Original Message ----- From: "Ivan Kurnosov" <[email protected]>
To: <[email protected]>
Sent: Wednesday, September 15, 2010 8:28 AM
Subject: registered_delivery and multi-parts message
Hello there.
Why does
2010-09-15 16:26:32 [25217] [6] DEBUG: registered_delivery: 0 =
0x00000000
for second part even though it was 0x1 for first one?
Is not it a bug?
While reading SMPP v3.4 specification I did not see any
recommendations about how to set registered_delivery if there are
multiple parts.
--
With best regards, Ivan Kurnosov
--
With best regards, Ivan Kurnosov
