That's a kannel, not a spec limitation. And these 3 lines of code you
changed propably have broken your kannel.
BR,
Nikos
----- Original Message -----
From: "Ivan Kurnosov" <[email protected]>
To: "Nikos Balkanas" <[email protected]>; <[email protected]>
Sent: Wednesday, September 15, 2010 2:24 PM
Subject: Re: registered_delivery and multi-parts message
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
