Hi,I am a new user of kannel. I am using kannel with a GSM modem, but I have noticed this one issue. Suppose I try and send a message using sendsms the message is sent only after some irregular interval. But, if I send a sms from my mobile, to which the reply is sent using sendsms the message is
There are usually two threads on AT driver. One sitting on the device to READ. So its waiting in a poll call until some data arrives to be read. The other sits on a list and waits until bearerbox main driver puts something in it and wakes the thread by doing that.On 20.08.2006, at 09:04, Akshat
On 20.08.2006, at 02:12, Stipe Tolj wrote:Hi list,I wonder if we should/can change logic to refuse any deliver_sm PDU containing a DLR information when we don't find the associated DLR temp data in our internal storage?This could be done by responding with deliver_sm_resp.command_status =
Andreas Fink wrote:
Would be very implementation specific. on our SMSC it would simply
keep the message in the queue and retry with a 50% luck to end up on
the other session.
ok, that's the default behaviour, round-robin or random transmission of DLRs
to any RX session bound for the
Yeah, I noticed the two threads. The one which is supposed to write to the modem is the one that appears to be blocking and delaying the whole system. The outgoing_sms list is getting populated for that device but it is not waking up as soon as the message is forwarded. How can we wake this thread
On 20.08.2006, at 16:31, Stipe Tolj wrote:Andreas Fink wrote: Would be very implementation specific. on our SMSC it would simply keep the message in the queue and retry with a 50% luck to end up on the "other" session. ok, that's the "default" behaviour, round-robin or random transmission of
Found another detail. The write thread seems to be blocking inside tcdrain() call from at2_write_line.what could be the issue here?thanks,akshatOn 8/20/06,
Akshat Choudhary [EMAIL PROTECTED] wrote:
Yeah, I noticed the two threads. The one which is supposed to write to the modem is the one that
I think this is an SMSC related issue.
Probably you will get different results based on different SMSC's.
Especially if it is not mentioned in any specs.
You are right about this being a client-side issue.
I know for once that -in my platforms- I have a single receive process
that receives
On Sun, 20 Aug 2006 16:29:34 +0200
Stipe Tolj [EMAIL PROTECTED] wrote:
Denis V. Gudtsov wrote:
On Sat, 19 Aug 2006 21:58:28 +0200
Stipe Tolj [EMAIL PROTECTED] wrote:
Denis V. Gudtsov wrote:
Can kannel 1.4.0 sends PDU Enquire_link only when there are no
activity in SMPP connection, not
I am new to kannel and am using it to sed/recv sms's using a wavecom gsm modem. I have noticed that the system blocks at tcdrain() within at2_write_line.I found a patch to this problem while googling. but the patched kannel had many other issues.
Is there any other known solution to this problem.
Thanks for bringing this up,
we use many kannel instances, some with the same operator, and on occasion a
DLR would return
via a different bind/instance to which the MT went on...the numbers were
small in comparison so we didn't
do anything about it yet - actually don't know if its still
11 matches
Mail list logo
