Wilfried Goesgens wrote:
after a long time of tracking the problem of messages not traversing over to
bearerbox from smsbox it seems as if the monitoring system (which queries
/status.txt on a regular base) itself is responsible for this issue.
It seems, as if this issue is a primary matter with the at driver. (perhaps
because of it sleeps on a more regular base than the other smsc's?) though ucp
and smpp suffer from that too, but not in a such heavy way (about 25 messages
per smsc per day get lost)
I use gwthread_sleep for idling, that should be correct?
The first counter measure was to lower the frequency status.txt is requested,
but this doesn't solve the problem, just reduce...
any ideas on that?
Hi Wilfried,
thanks for the hint. No idea yet from my side. Did you had a chance to track
issues more down?
You say msgs get lost while passed from smsbox to bearerbox. Now, if bearerbox
would not accept the msg within the TCP stream between smsbox and bearerbox it
would not send a ack'ing msg to smsbox for it, right? Hence smsbox should
resend. I'm not aware now how smsbox handles this. We'll have to review.
Of course it is not acceptable that bearerbox "blocks" incoming msgs from smsbox
side, if this is the case.
BTW, it would be great if you submit a bug report on this with as much details
as you have, via http://bugs.kannel.org/
Thanks.
Stipe
mailto:stolj_{at}_wapme-group.de
-------------------------------------------------------------------
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
-------------------------------------------------------------------
