Hi,

seems you are right, forgot that I fixed it already :-)

Alex

Am 30.07.2013 um 14:47 schrieb Brian McCavour <[email protected]>:

> Hi Alex,
> 
> Thanks for your response. I wish I had known 1.5.0 was stable before I 
> started modifying 1.4.3 about 8 months ago :(
> Now it will be a big task to rebase it with my changes, since I modified it 
> quick and dirty with the thought of never rebasing (beginner mistakes...)
> 
> Right before seeing your response though, I noticed this bug fixed by you: 
> https://redmine.kannel.org/issues/529
> Looking briefly through the patch it seems to add the retry count to the 
> SMSCCONN_FAILED_TEMPORARILY case for split messages.
> Isn't this a fix for that issue?
> 
> 
> Brian
> 
> From: Alexander Malysh <[email protected]>
> To: Brian McCavour <[email protected]> 
> Cc: "[email protected]" <[email protected]> 
> Sent: Tuesday, July 30, 2013 3:59:36 AM
> Subject: Re: Another sms-resend-retry thread...
> 
> Hi,
> 
> sms-resend-retry is still ignored in 1.5 but 1.5 SMPP has better throughout 
> handling so that this issue may be considered as fixed
> if you configure right throughput for SMPP connection.
> 
> Tip: Better to use SVN trunk version because we did a lot of changes since 
> 1.5 and it may be considered as stable.
> 
> Alex
> 
> Am 29.07.2013 um 20:25 schrieb Brian McCavour <[email protected]>:
> 
>> 
>> Hi guys,
>> 
>> I'm having the same old problem of "sms-resend-retry being ignored" for 
>> concatenated msg with coding=2, when the smsc return a Queue full error. 
>> Kannel just spams the SMSC and all kind of nasty happens.
>> Looking around the threads I've seen a LOTS of people with the same issue 
>> but never a proper resolution other then code changes or to disable 
>> concatenation (ew).
>> 
>> Ex: 
>> http://kannel.6189.n7.nabble.com/Kannel-ignoring-sms-resend-retry-td13400.html
>> http://kannel.6189.n7.nabble.com/sms-resend-retry-ignored-td4759.html
>> 
>> There is also this bug that is many years old, but never set to fixed:
>> https://redmine.kannel.org/issues/352
>> 
>> I am using Kannel 1.4.3
>> Is there any news on this? Is it fixed in 1.5.0 ?
>> 
>> Thanks,
>> Brian
> 
> 
> 

Reply via email to