Will post it soon. Just enabled access logs and set log level to 0.
--------
Thanks
Jinson


On Fri, Sep 25, 2009 at 3:20 PM, Nikos Balkanas <[email protected]> wrote:

> Hi,
> Can you please post relvant bb logs (access + aplication) showing the
> problem?
> BR,
> Nikos
>
> On Fri, Sep 25, 2009 at 12:46 PM, Jinson <[email protected]> wrote:
>
>> Hello Users,
>>
>> Seems like reties are still happening at my end. is there anything else to
>> configure other than *sms-resend-retry = 0*
>>
>>
>> --------
>> Thanks
>> Jinson
>>
>>
>> On Wed, Sep 23, 2009 at 9:53 AM, Jinson <[email protected]> wrote:
>>
>>> Yes. DLRs are getting failed. But this should solve my problem of retries
>>> for the time being.
>>> --------
>>> Thanks
>>> JJinson
>>>
>>>
>>> 2009/9/23 Nikos Balkanas <[email protected]>
>>>
>>>>  Yeap. That should do it. However, it will be logged as an error, and
>>>> the DLR will probably be discarded.
>>>>
>>>> BR,
>>>> Nikos
>>>>
>>>> ----- Original Message -----
>>>>  *From:* Jinson <[email protected]>
>>>> *To:* Nikos Balkanas <[email protected]>
>>>> *Cc:* users <[email protected]>
>>>> *Sent:* Tuesday, September 22, 2009 1:56 PM
>>>> *Subject:* Re: How to stop message retries
>>>>
>>>> Hi,
>>>>
>>>> I got the point. The provider fail to send ACK sometimes. They are still
>>>> not able to solve the issue.
>>>>
>>>> My current concern is to stop retries from Kannel, other than setting
>>>> the wait-ack-expire.
>>>>
>>>> I set the sms-resend-retry = 0, that means no messages will be
>>>> retried...rite?
>>>>
>>>> --------
>>>>
>>>>
>>>>
>>>> 2009/9/18 Nikos Balkanas <[email protected]>
>>>>
>>>>>  Hi,
>>>>>
>>>>> You probably want to say that "kannel was not able to submit messages
>>>>> and queued up heavily". That is accurate, unless the SMSc sends an ACK,
>>>>> kannel won't remove SMS from Q. However, with 2, it won't try to resend it
>>>>> either. Note that this doesn't mean that the SMS was not sent. Just that
>>>>> kannel is pending on an ACK.
>>>>>
>>>>> So what's the deal? Your SMSc never sends ACKs? You may want to talk to
>>>>> them. Otherwise check also flow-control and window. But at the end, you 
>>>>> will
>>>>> need to get an ACK from them, for SMPP to work.
>>>>>
>>>>> BR,
>>>>> Nikos
>>>>>
>>>>> ----- Original Message -----
>>>>>  *From:* Jinson <[email protected]>
>>>>> *To:* Nikos Balkanas <[email protected]>
>>>>> *Cc:* users <[email protected]>
>>>>> *Sent:* Friday, September 18, 2009 11:16 AM
>>>>> *Subject:* Re: How to stop message retries
>>>>>
>>>>>
>>>>> I tried wait-ack-expire  = 0x02 before, but the SMSC was not able to
>>>>> submit messages and queued up heavily.
>>>>>
>>>>> Something to do with sms-resend-retry in core group?
>>>>>
>>>>> --------
>>>>> Thanks
>>>>> Jinson
>>>>>
>>>>>
>>>>> MobME storms into Emerging 50 Companies in India by Nasscom
>>>>>
>>>>>
>>>>>
>>>>> 2009/9/18 Nikos Balkanas <[email protected]>
>>>>>
>>>>>>  Hi,
>>>>>>
>>>>>> There are 2 options in SMPP configuration that will solve your
>>>>>> problem:
>>>>>>
>>>>>> wait-ack
>>>>>> wait-ack-expire
>>>>>>
>>>>>> Please read User guide on how to use them.
>>>>>>
>>>>>> BR,
>>>>>> Nikos
>>>>>>
>>>>>> ----- Original Message -----
>>>>>>  *From:* Jinson <[email protected]>
>>>>>> *To:* users <[email protected]>
>>>>>> *Sent:* Friday, September 18, 2009 8:53 AM
>>>>>> *Subject:* How to stop message retries
>>>>>>
>>>>>> Hello ,
>>>>>> Im getting the following warning very frequently
>>>>>>
>>>>>> *2009-09-18 05:48:48 [18220] [10] WARNING: SMPP[SMPP1]: Not ACKED
>>>>>> message found, will retransmit. SENT<93>sec. ago, SEQ<94598>,
>>>>>> DST<xxxxxxxxxxxx>*
>>>>>> *
>>>>>> *
>>>>>> Is there any way to stop the resending completely, Some people are
>>>>>> getting messages more than twice.
>>>>>>
>>>>>> I have the following line in my core group.
>>>>>>
>>>>>> sms-resend-retry = 1
>>>>>>
>>>>>>
>>>>>> --------
>>>>>> Thanks
>>>>>> Jinson Abraham
>>>>>> MobME Wireless Solutions Pvt. Ltd
>>>>>> Cochin
>>>>>> +91 4846492646
>>>>>>
>>>>>>
>>>>>> MobME storms into Emerging 50 Companies in India by Nasscom
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to