Multipart DLR issue

2010-06-17 Thread Rene Kluwen
This is the setup:

KANNEL 1 KANNEL 2
CGI PUSH -- SMSBOX 1 -- BEARERBOX 1 -- SMPP LINK -- Open SMPPBOX --- 
BEARERBOX 2

I am working on smppbox sending multi-part messages via the same SMSC (on 
Kannel 2). I do this by reassembling the submit_sm pdu's in smppbox back to one 
large SMS and sending it to bearerbox as a whole.
This works now and will be submitted to svn shortly.

I keep track of which smpp id's the message originally consisted of and when I 
get a DLR, I send a deliver_sm for each of these pdu's.

As you can see in the log files (attached) the second PDU doesn't seem to be 
stored in the DLR database of bearerbox 1. What exactly is the procedure here 
to be followed?

I assume that if an sms message consists of multiple parts, each part needs to 
be matched with a corresponding DLR receipt. But it seems that Kannel only 
stores the first part in the DLR table and is not interested in the rest.

Thank you for your time,

== Rene



bearerbox1.log
Description: Binary data


smppbox2.log
Description: Binary data


RE: FW: Issue with concatenated messages and load balancing over SMPP

2010-06-17 Thread Rene Kluwen
1. The bb is not an issue. I send one (long) message to bb and I get one dlr
back.
2. What if the message consists of 3 or more message? I generate a DLR for
the last message? Bearerbox, on the other hand can only find the first
message in the dlr table. The other ones are not found.

I agree with sending two (or more) DLR's: one for each message. But
smsc_smpp doesn't seem to be able to find the other ones.

== Rene


-Original Message-
From: Nikos Balkanas [mailto:nbalka...@gmail.com] 
Sent: donderdag 17 juni 2010 18:19
To: Rene Kluwen
Subject: Re: FW: Issue with concatenated messages and load balancing over
SMPP

The solution is simple:

1) As far as bb is concerned, ACK each Msg that is sending you, otherwise it

will keepon sending it to you.
2) If what you say is correct, and you need to emulate an SMSc to the ESME, 
you need to generate the DLR for the second part. But the question is: What 
if only the first part succeeds and the second fails (network issue, etc.) 
The final DLR for this should be FAILED. However, if BB keeps track of only 
the first part, it will be SUCCESS.

In the HLR that I implemented, I remember passing 2 DLRs from bb to the 
commercial SMPPbox by Stipe.

BR,
Nikos
- Original Message - 
From: Rene Kluwen rene.klu...@chimit.nl
To: 'Nikos Balkanas' nbalka...@gmail.com
Sent: Thursday, June 17, 2010 4:38 PM
Subject: RE: FW: Issue with concatenated messages and load balancing over 
SMPP


I also thought each part needs a separate dlr. But Kannel seems to think 
differently.

== Rene






RE: Multipart DLR issue

2010-06-17 Thread Rene Kluwen
So what I will continue to do send a DLR for each part. Even if Kannel
doesn't like it.

== Rene

-Original Message-
From: Alexander Malysh [mailto:malys...@googlemail.com] On Behalf Of
Alexander Malysh
Sent: donderdag 17 juni 2010 18:25
To: Rene Kluwen
Cc: 'Kannel Devel'
Subject: Re: Multipart DLR issue

Hi Rene,

this is a known Kannel limitation. Kannel request DLR only for the first
part.

Thanks,
Alexander Malysh

Am 17.06.2010 um 14:46 schrieb Rene Kluwen:

 This is the setup:
 
KANNEL 1 KANNEL
2
 CGI PUSH -- SMSBOX 1 -- BEARERBOX 1 -- SMPP LINK -- Open SMPPBOX
--- BEARERBOX 2
 
 I am working on smppbox sending multi-part messages via the same SMSC (on
Kannel 2). I do this by reassembling the submit_sm pdu's in smppbox back to
one large SMS and sending it to bearerbox as a whole.
 This works now and will be submitted to svn shortly.
 
 I keep track of which smpp id's the message originally consisted of and
when I get a DLR, I send a deliver_sm for each of these pdu's.
 
 As you can see in the log files (attached) the second PDU doesn't seem to
be stored in the DLR database of bearerbox 1. What exactly is the procedure
here to be followed?
 
 I assume that if an sms message consists of multiple parts, each part
needs to be matched with a corresponding DLR receipt. But it seems that
Kannel only stores the first part in the DLR table and is not interested in
the rest.
 
 Thank you for your time,
 
 == Rene
 
 bearerbox1.logsmppbox2.log






RE: Multipart DLR issue

2010-06-17 Thread Rene Kluwen
I tend to agree with Alex more :).

-Original Message-
From: Nikos Balkanas [mailto:nbalka...@gmail.com] 
Sent: donderdag 17 juni 2010 18:54
To: Alexander Malysh; Rene Kluwen
Cc: 'Kannel Devel'
Subject: Re: Multipart DLR issue

Hi Alex,

Actually, stated more correctly, kannel cannot request DLRs for only a 
specific part. It requests for all. SMScs will respond with a different DLR 
fo each part. Kannel seems to ignore all others than the first.

BR,
Nikos
- Original Message - 
From: Alexander Malysh amal...@kannel.org
To: Rene Kluwen rene.klu...@chimit.nl
Cc: 'Kannel Devel' devel@kannel.org
Sent: Thursday, June 17, 2010 7:24 PM
Subject: Re: Multipart DLR issue


Hi Rene,

this is a known Kannel limitation. Kannel request DLR only for the first 
part.

Thanks,
Alexander Malysh

Am 17.06.2010 um 14:46 schrieb Rene Kluwen:

 This is the setup:

KANNEL 1 KANNEL

 2
 CGI PUSH -- SMSBOX 1 -- BEARERBOX 1 -- SMPP LINK -- Open 
 SMPPBOX --- BEARERBOX 2

 I am working on smppbox sending multi-part messages via the same SMSC (on 
 Kannel 2). I do this by reassembling the submit_sm pdu's in smppbox back 
 to one large SMS and sending it to bearerbox as a whole.
 This works now and will be submitted to svn shortly.

 I keep track of which smpp id's the message originally consisted of and 
 when I get a DLR, I send a deliver_sm for each of these pdu's.

 As you can see in the log files (attached) the second PDU doesn't seem to 
 be stored in the DLR database of bearerbox 1. What exactly is the 
 procedure here to be followed?

 I assume that if an sms message consists of multiple parts, each part 
 needs to be matched with a corresponding DLR receipt. But it seems that 
 Kannel only stores the first part in the DLR table and is not interested 
 in the rest.

 Thank you for your time,

 == Rene

 bearerbox1.logsmppbox2.log







[PATCH] SMPP box multipart messages

2010-06-17 Thread Rene Kluwen
Okay, to comply with Kannel's common practices, hereby I send in a patch for
open smppbox that allows for all parts of multipart messages to be sent via
the same smsc (letting bearerbox split the message up).

The patch applies to current svn trunk of smppbox.

Known issue: This patch submits a deliver_sm message for all parts of the
original message. Kannel complains about it, because it can only find the
first part in the dlr table.
Since this seems to be a Kannel issue and not smppbox, I am letting it this
way. This doesn't affect any practical, operational issues.

Special thanks to Tomasz Konopka for letting me test in his production
environment.

Can I have any votes on this?

== Rene



multipart13.patch
Description: Binary data


Re: [PATCH] SMPP box multipart messages

2010-06-17 Thread Nikos Balkanas

Looks good. +1

Nikos
- Original Message - 
From: Rene Kluwen rene.klu...@chimit.nl

To: 'Kannel Devel' devel@kannel.org
Sent: Thursday, June 17, 2010 9:25 PM
Subject: [PATCH] SMPP box multipart messages


Okay, to comply with Kannel's common practices, hereby I send in a patch 
for
open smppbox that allows for all parts of multipart messages to be sent 
via

the same smsc (letting bearerbox split the message up).

The patch applies to current svn trunk of smppbox.

Known issue: This patch submits a deliver_sm message for all parts of the
original message. Kannel complains about it, because it can only find the
first part in the dlr table.
Since this seems to be a Kannel issue and not smppbox, I am letting it 
this

way. This doesn't affect any practical, operational issues.

Special thanks to Tomasz Konopka for letting me test in his production
environment.

Can I have any votes on this?

== Rene







Re: Multipart DLR issue

2010-06-17 Thread Alexander Malysh
it may not work for load balanced connection via different SMSCs...

Thanks,
Alexander Malysh

Am 17.06.2010 um 18:32 schrieb Rene Kluwen:

 So what I will continue to do send a DLR for each part. Even if Kannel
 doesn't like it.
 
 == Rene
 
 -Original Message-
 From: Alexander Malysh [mailto:malys...@googlemail.com] On Behalf Of
 Alexander Malysh
 Sent: donderdag 17 juni 2010 18:25
 To: Rene Kluwen
 Cc: 'Kannel Devel'
 Subject: Re: Multipart DLR issue
 
 Hi Rene,
 
 this is a known Kannel limitation. Kannel request DLR only for the first
 part.
 
 Thanks,
 Alexander Malysh
 
 Am 17.06.2010 um 14:46 schrieb Rene Kluwen:
 
 This is the setup:
 
   KANNEL 1 KANNEL
 2
 CGI PUSH -- SMSBOX 1 -- BEARERBOX 1 -- SMPP LINK -- Open SMPPBOX
 --- BEARERBOX 2
 
 I am working on smppbox sending multi-part messages via the same SMSC (on
 Kannel 2). I do this by reassembling the submit_sm pdu's in smppbox back to
 one large SMS and sending it to bearerbox as a whole.
 This works now and will be submitted to svn shortly.
 
 I keep track of which smpp id's the message originally consisted of and
 when I get a DLR, I send a deliver_sm for each of these pdu's.
 
 As you can see in the log files (attached) the second PDU doesn't seem to
 be stored in the DLR database of bearerbox 1. What exactly is the procedure
 here to be followed?
 
 I assume that if an sms message consists of multiple parts, each part
 needs to be matched with a corresponding DLR receipt. But it seems that
 Kannel only stores the first part in the DLR table and is not interested in
 the rest.
 
 Thank you for your time,
 
 == Rene
 
 bearerbox1.logsmppbox2.log
 
 
 




RE: Multipart DLR issue

2010-06-17 Thread Rene Kluwen
Yes, it also works for different load balanced SMSCs. We got that covered,
by testing.

That was the purpose of this patch, to begin with.

== Rene

-Original Message-
From: Alexander Malysh [mailto:malys...@googlemail.com] On Behalf Of
Alexander Malysh
Sent: donderdag 17 juni 2010 22:39
To: Rene Kluwen
Cc: 'Kannel Devel'
Subject: Re: Multipart DLR issue

it may not work for load balanced connection via different SMSCs...

Thanks,
Alexander Malysh

Am 17.06.2010 um 18:32 schrieb Rene Kluwen:

 So what I will continue to do send a DLR for each part. Even if Kannel
 doesn't like it.
 
 == Rene
 
 -Original Message-
 From: Alexander Malysh [mailto:malys...@googlemail.com] On Behalf Of
 Alexander Malysh
 Sent: donderdag 17 juni 2010 18:25
 To: Rene Kluwen
 Cc: 'Kannel Devel'
 Subject: Re: Multipart DLR issue
 
 Hi Rene,
 
 this is a known Kannel limitation. Kannel request DLR only for the first
 part.
 
 Thanks,
 Alexander Malysh
 
 Am 17.06.2010 um 14:46 schrieb Rene Kluwen:
 
 This is the setup:
 
   KANNEL 1 KANNEL
 2
 CGI PUSH -- SMSBOX 1 -- BEARERBOX 1 -- SMPP LINK -- Open SMPPBOX
 --- BEARERBOX 2
 
 I am working on smppbox sending multi-part messages via the same SMSC (on
 Kannel 2). I do this by reassembling the submit_sm pdu's in smppbox back
to
 one large SMS and sending it to bearerbox as a whole.
 This works now and will be submitted to svn shortly.
 
 I keep track of which smpp id's the message originally consisted of and
 when I get a DLR, I send a deliver_sm for each of these pdu's.
 
 As you can see in the log files (attached) the second PDU doesn't seem to
 be stored in the DLR database of bearerbox 1. What exactly is the
procedure
 here to be followed?
 
 I assume that if an sms message consists of multiple parts, each part
 needs to be matched with a corresponding DLR receipt. But it seems that
 Kannel only stores the first part in the DLR table and is not interested
in
 the rest.
 
 Thank you for your time,
 
 == Rene
 
 bearerbox1.logsmppbox2.log