Re: Multipart sms sending behaviour - Sending all the parts of a multipart 1 after the other

2017-12-21 Thread amalysh
Hi Grant,

as far as I see 1.4.4 already using prio queue and Kannel does it best to send 
all messages/parts in the right order but it’s impossible to do
in all the cases. What you can do, as a workaround, to add a delay between 
sending, e.g. 20 longs msgs then min 1 sec delay and other 20 msgs.

Thanks,
Alex


> Am 20.12.2017 um 08:25 schrieb Grant Saicom :
> 
> Hi Alex
> 
> Thank you for your reply and time. Kannel is splitting the messages before 
> sending them down the bind to the SMSC. The whole messages arrives via smsbox 
> and is then passed to bearerbox for delivery to SMSC via smpp.
> 
> The problem is that if I have more than 40 multipart messages in the queue, 
> the sending will stop as bearerbox submits one part of each queued message as 
> described. Because of the way the server works, it locks up all the available 
> max pending sessions.
> 
> I need kannel to send each multipart of the whole sequentially. Borrowing 
> from printing jargon, I need the multipart sending to be collated: a1, a2, a3 
> ; b1, b2, b3 ; c1, c2 ; d1, d2, d3
> 
> Thanks,
> Grant
>> On 20 Dec 2017, at 00:37, amal...@kannel.org wrote:
>> 
>> Hi,
>> 
>> who is responsible for splitting long messages? you should let Kannel do it 
>> for you, then Kannel take care to send
>> all parts via the same SMSC and in the right order.
>> 
>> Thanks,
>> Alex
>> 
>> 
>>> Am 19.12.2017 um 14:32 schrieb Grant Saicom :
>>> 
>>> Hi Kannel Users
>>> 
>>> I have an issue which I need to address with respect to how kannel(1.44) 
>>> sends multipart messages to a SMSC.
>>> 
>>> Let me explain the situation/limitations:
>>> 
>>> -I have a server which manages and distributes smses to my modems.
>>> -I communicate to this server via smpp using bearerbox.
>>> -These modems are hosted on gateways at various locations linked via IP.
>>> -The server sends the messages to the gateways which then send to the 
>>> modems via serial.
>>> -The server requires that it has the entire message (all multiparts) before 
>>> it can send it to the gateway and ultimately the modem for sending via GSM.
>>> -I have a max pending sms limit of 40 on the server. This is the licensing 
>>> model.
>>> 
>>> Example Scenario of the issue:
>>> If I have 100 messages with 200 characters in them, kannel sends the first 
>>> part of the first 40 messages i.e.
>>> 
>>> message1 : 1 of 2
>>> message2 : 1 of 2
>>> message3 : 1 of 2
>>> message4 : 1 of 2
>>> …
>>> message39 : 1 of 2
>>> message40 : 1 of 2
>>> 
>>> The server acks these messages, but it starts rejecting any further 
>>> messages because its max pending queue is now full. None of these messages 
>>> will go out. The client side will eventually time-out these messages and 
>>> fail them.
>>> 
>>> How do I get bearerbox to send the messages like this:
>>> 
>>> message1 : 1 of 2
>>> message1 : 1 of 2
>>> message2 : 1 of 2
>>> message2 : 2 of 2
>>> …
>>> 
>>> message39 : 1 of 2
>>> message39 : 2 of 2
>>> message40 : 1 of 2
>>> message40 : 2 of 2
>>> 
>>> I have not found anything in the documentation that indicates how I could 
>>> do this.
>>> 
>>> Kind regards
>>> Grant
>>> 
>>> 
>> 
> 




Re: Multipart sms sending behaviour - Sending all the parts of a multipart 1 after the other

2017-12-19 Thread Grant Saicom
Hi Alex

Thank you for your reply and time. Kannel is splitting the messages before 
sending them down the bind to the SMSC. The whole messages arrives via smsbox 
and is then passed to bearerbox for delivery to SMSC via smpp.

The problem is that if I have more than 40 multipart messages in the queue, the 
sending will stop as bearerbox submits one part of each queued message as 
described. Because of the way the server works, it locks up all the available 
max pending sessions.

I need kannel to send each multipart of the whole sequentially. Borrowing from 
printing jargon, I need the multipart sending to be collated: a1, a2, a3 ; b1, 
b2, b3 ; c1, c2 ; d1, d2, d3

Thanks,
Grant
> On 20 Dec 2017, at 00:37, amal...@kannel.org wrote:
> 
> Hi,
> 
> who is responsible for splitting long messages? you should let Kannel do it 
> for you, then Kannel take care to send
> all parts via the same SMSC and in the right order.
> 
> Thanks,
> Alex
> 
> 
>> Am 19.12.2017 um 14:32 schrieb Grant Saicom :
>> 
>> Hi Kannel Users
>> 
>> I have an issue which I need to address with respect to how kannel(1.44) 
>> sends multipart messages to a SMSC.
>> 
>> Let me explain the situation/limitations:
>> 
>> -I have a server which manages and distributes smses to my modems.
>> -I communicate to this server via smpp using bearerbox.
>> -These modems are hosted on gateways at various locations linked via IP.
>> -The server sends the messages to the gateways which then send to the modems 
>> via serial.
>> -The server requires that it has the entire message (all multiparts) before 
>> it can send it to the gateway and ultimately the modem for sending via GSM.
>> -I have a max pending sms limit of 40 on the server. This is the licensing 
>> model.
>> 
>> Example Scenario of the issue:
>> If I have 100 messages with 200 characters in them, kannel sends the first 
>> part of the first 40 messages i.e.
>> 
>> message1 : 1 of 2
>> message2 : 1 of 2
>> message3 : 1 of 2
>> message4 : 1 of 2
>> …
>> message39 : 1 of 2
>> message40 : 1 of 2
>> 
>> The server acks these messages, but it starts rejecting any further messages 
>> because its max pending queue is now full. None of these messages will go 
>> out. The client side will eventually time-out these messages and fail them.
>> 
>> How do I get bearerbox to send the messages like this:
>> 
>> message1 : 1 of 2
>> message1 : 1 of 2
>> message2 : 1 of 2
>> message2 : 2 of 2
>> …
>> 
>> message39 : 1 of 2
>> message39 : 2 of 2
>> message40 : 1 of 2
>> message40 : 2 of 2
>> 
>> I have not found anything in the documentation that indicates how I could do 
>> this.
>> 
>> Kind regards
>> Grant
>> 
>> 
> 




Re: Multipart sms sending behaviour - Sending all the parts of a multipart 1 after the other

2017-12-19 Thread amalysh
Hi,

who is responsible for splitting long messages? you should let Kannel do it for 
you, then Kannel take care to send
all parts via the same SMSC and in the right order.

Thanks,
Alex
 

> Am 19.12.2017 um 14:32 schrieb Grant Saicom :
> 
> Hi Kannel Users
> 
> I have an issue which I need to address with respect to how kannel(1.44) 
> sends multipart messages to a SMSC.
> 
> Let me explain the situation/limitations:
> 
> -I have a server which manages and distributes smses to my modems.
> -I communicate to this server via smpp using bearerbox.
> -These modems are hosted on gateways at various locations linked via IP.
> -The server sends the messages to the gateways which then send to the modems 
> via serial.
> -The server requires that it has the entire message (all multiparts) before 
> it can send it to the gateway and ultimately the modem for sending via GSM.
> -I have a max pending sms limit of 40 on the server. This is the licensing 
> model.
> 
> Example Scenario of the issue:
> If I have 100 messages with 200 characters in them, kannel sends the first 
> part of the first 40 messages i.e.
> 
> message1 : 1 of 2
> message2 : 1 of 2
> message3 : 1 of 2
> message4 : 1 of 2
> …
> message39 : 1 of 2
> message40 : 1 of 2
> 
> The server acks these messages, but it starts rejecting any further messages 
> because its max pending queue is now full. None of these messages will go 
> out. The client side will eventually time-out these messages and fail them.
> 
> How do I get bearerbox to send the messages like this:
> 
> message1 : 1 of 2
> message1 : 1 of 2
> message2 : 1 of 2
> message2 : 2 of 2
> …
> 
> message39 : 1 of 2
> message39 : 2 of 2
> message40 : 1 of 2
> message40 : 2 of 2
> 
> I have not found anything in the documentation that indicates how I could do 
> this.
> 
> Kind regards
> Grant
> 
> 




Multipart sms sending behaviour - Sending all the parts of a multipart 1 after the other

2017-12-19 Thread Grant Saicom
Hi Kannel Users

I have an issue which I need to address with respect to how kannel(1.44) sends 
multipart messages to a SMSC.

Let me explain the situation/limitations:

-I have a server which manages and distributes smses to my modems.
-I communicate to this server via smpp using bearerbox.
-These modems are hosted on gateways at various locations linked via IP.
-The server sends the messages to the gateways which then send to the modems 
via serial.
-The server requires that it has the entire message (all multiparts) before it 
can send it to the gateway and ultimately the modem for sending via GSM.
-I have a max pending sms limit of 40 on the server. This is the licensing 
model.

Example Scenario of the issue:
If I have 100 messages with 200 characters in them, kannel sends the first part 
of the first 40 messages i.e.

message1 : 1 of 2
message2 : 1 of 2
message3 : 1 of 2
message4 : 1 of 2
…
message39 : 1 of 2
message40 : 1 of 2

The server acks these messages, but it starts rejecting any further messages 
because its max pending queue is now full. None of these messages will go out. 
The client side will eventually time-out these messages and fail them.

How do I get bearerbox to send the messages like this:

message1 : 1 of 2
message1 : 1 of 2
message2 : 1 of 2
message2 : 2 of 2
…

message39 : 1 of 2
message39 : 2 of 2
message40 : 1 of 2
message40 : 2 of 2

I have not found anything in the documentation that indicates how I could do 
this.

Kind regards
Grant