Diagnosing problem with submission of MTs from Kannel's store file...

Hi, this is my first post to the Kannel Devel mailing list (and I've 
only been subscribed for maybe a month or so), so please excuse any 
cluelessness on my part...

We're becoming quite reliant on Kannel because of significant problems 
with our old SMS gateway, and a new SMS gateway we're trying to migrate to.

As such, I have a fairly urgent need to diagnose and resolve an issue 
that's cropped up a few times, with regards to Kannel's handling of MTs 
that are queued to its message store file.

The problem is this:

An SMPP link to a carrier goes down, for one reason or another, and MTs 
submitted to Kannel are queued in its store file. When the link comes 
back up (responds to bind requests again), *one* MT is submitted, but 
the rest of the queued MTs are *not* submitted, despite the bearer.log 
indicating (for sets of 10 MTs at a time) "WARNING: SMPP[optuschmt]: Not 
ACKED message found, will retransmit. SENT<90>sec. ago, SEQ<110>, 
DST<61402276846>" etc. (I've checked this with Etheral, monitoring 
traffic to the SMSC's IP address and port - only one SMPP submit_sm 
exchange occurs)

Also, all further MTs submitted to Kannel for that SMPP link will queue, 
even though the link is up (and responding to bind enquiries).

If I restart Kannel, again, *one* MT will be submitted, and that's it, 
and MTs will continue to queue.

The only way to resolve this, so far, is to stop Kannel, move its store 
file (and backup) aside, and restart Kannel so it has an empty store. 
Subsequent MTs are submitted fine, and don't queue.

I then have to parse the original store file and manually resend those 
MTs that were not submitted before.

This is a huge problem when we are experiencing heavy traffic, and it 
can sometimes take hours to resolve.

This is with Kannel 1.4.0 running on Redhat 8.0 (let me know if I should 
provide extra info, e.g. SMSC connection configuration, log excerpts etc.)

I am currently trying to replicate this problem on a test setup, but I 
wanted to check with people on the mailing list for any advice. Has 
anyone else encountered this problem? What are the chances of getting 
some help to diagnose & fix it? I (and some colleagues) have passable C 
skills, but any tips on where I should start to diagnose the problem 
would be greatly appreciated.

Thanks,

-- 
Giulio Harding
Systems Administrator

m.Net Corporation
Level 13, 99 Gawler Place
Adelaide SA 5000, Australia

Tel: +61 8 8210 2041
Fax: +61 8 8211 9620
Mobile: 0432 876 733
MSN: [email protected]

http://www.mnetcorporation.com