Most SMSCs that I work with require a link interval of 30 to 60 seconds. Check your logs closely to see if your link is being dropped and restarted. It may be that the link is down when your SMS is queued, and the link comes back up when you restart. It also may be that because you don't send your enquire link, the remote side shuts down the link and kannel is instructed not to retry to reconnect.
Set your enquire-link-interval to 30 seconds and restart. See if that helps.
On Sun, 27 Feb 2005, Pieter Natte wrote:
Richard,
I am having the same problem with 1.4.0. The messages are received routed to the correct handler. A reply is being prepared and routed via the smsbox back to the bearerbox for transmission. There is stops and is stored in the kannel.store queue. What I see in the kannel.log is that the following message.
2005-02-16 05:47:49 [15461] [27] DEBUG: boxc_receiver: heartbeat with load value 0 received
Once I stop and restart the bearer and smsbox the message is transmitted correctly. I have been checking the logs what can cause the problem. What I noticed was that it takes about 60 seconds to process all the enquire_link and enquire_link_resp processes. As I had set the enquire-link-interval to 290 seconds it may be the case that the link to the smsc was dropped at that time. I have as of a couple of hours ago reduced that time to 240 seconds.
I have no idea whether that was the problem and whether this will fix it. I would not even be surprised if I am totally wrong. I just hope that this guess is correct as it is an annoying problem. Time will tell whether this will do it. If it does I will let you know.
Sincerely,
Pieter Natte
[EMAIL PROTECTED] wrote:
Hi,
I'm running kannel 1.3.1 and have this problem where due to some unkown
conditions, smsbox seems to hang. I can receive messages but i can't send back
a reply.
One of the solutions i was thinking of, is being able to send an sms to my
system that triggers a script to restart smsbox (run killall -9 smsbox) or even
restart bearerbox.
Are there other users experiencing the same problem?? Any ideas on how to solve
this??
The other idea is to attempt some sort of fault tolerance where i have two
identical system (both connecting to the smsc using smpp) and then if one fails
or is overloaded, the smsc should route the messages to the other alternate
system.
These are just ideas, but i'd like to know if they are feasible. Has someone
done this before and how did they go about it??
Thanks, Richard.
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
--------------------------------------------------------------------------- Peter Beckman Internet Guy [EMAIL PROTECTED] http://www.purplecow.com/ ---------------------------------------------------------------------------
