Re: Update: Messages getting stuck in store

"Alex Kinch" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <00a201c3c698$993bd630$0501a8c0@alex>
Just had a little look through the archives, found this:

http://www.kannel.org/pipermail/bugs/2002-August/000093.html

Looks like it's the same sort of problem I'm experiencing here. The post is over a year old though, and refers to 1.2.0, so I hope it's been fixed by now :-)

Alex
  ----- Original Message ----- 
  From: Alex Kinch 
  To: [email protected] 
  Sent: Saturday, December 20, 2003 1:15 AM
  Subject: Update: Messages getting stuck in store 


  Hi,    

  I've been doing some more testing with outbound messages getting stuck in the store. Here's an example log. The required SMPP connection was up and running fine at the time, so there was no reason the message shouldn't have been submitted to the SMSC.

  The outbound message ends up in the store, and only a restart of bearerbox gets it moving. It's not just happening on one SMPP connection - it's happening on a few of them. I think we can rule out the SMPP connection at this point as there's nothing in the debug log that shows the message was even attempted to be delivered...?

  Version is cvs-20031125. smsbox and bearerbox are running on the same server.

  Any help greatly appreciated

  Alex

  smsbox log:

  2003-12-20 00:59:08 [3] INFO: sendsms used by <xxxx>
  2003-12-20 00:59:08 [3] INFO: sendsms sender:<xxxx:xxxx> (xxx.xxx.xxx.xxx) to
  :<44xxxxxxxxxx> msg:<xxxxxx>
  2003-12-20 00:59:08 [3] DEBUG: message length 74, sending 1 messages
  2003-12-20 00:59:08 [3] DEBUG: Status: 202 Answer: <Sent.>

  bearerbox log:

  2003-12-20 00:59:08 [40] DEBUG: boxc_receiver: sms received
  2003-12-20 00:59:08 [40] DEBUG: send_msg: sending msg to box: <127.0.0.1>
  2003-12-20 00:59:08 [39] DEBUG: sms_router: time to sleep
  2003-12-20 00:59:08 [39] DEBUG: sms_router: list_len = 1
  2003-12-20 00:59:08 [39] DEBUG: sms_router: time to sleep
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.