Hello Kannel Users, I need some help tracking down an issue that was reported to us by the SMSC we are connected to. They sent the following notification:
We are seeing an increase in “Windows on receiver links full (message queue full)” on the RX binds to you, which is translating to x14 being sent back from you to the SMSC. These are primarily notifications (DAN) but a small percentage of these do appear to be actual messages (DAM). I am not really sure how to go about troubleshooting this. We did a tremendous amount of SMS Volume the day they reported these errors. Our kannel instance sent over 3.1 million MTs this day. I am guessing the issue was caused by the volume of delivery receipts generated by these MTs. We only have 2 incoming binds connected to the SMSC. Could that be the cause of the problem? Or is the problem related to latency in our application when processing the MO or DLR url? Here is the an excerpt of our kannel configuration. Is the error that the SMSC is reporting due to kannel itself or because our mo.php script is taking too long to return? Would additional incoming binds address the issue? group = core admin-port = 13000 admin-password = xxxxxx status-password = xxxxxx admin-deny-ip = "*.*.*.*" admin-allow-ip = "192.168.*.*" smsbox-port = 13001 #wapbox-port = 13002 box-deny-ip = "*.*.*.*" box-allow-ip = "192.168.*.*" wdp-interface-name = "*" log-file = "/var/log/kannel/bearerbox.log" log-level = 0 dlr-storage = mysql store-type = file store-location = /var/log/kannel/msg-store.db sms-incoming-queue-limit = 0 group = sms-service keyword-regex = .* catch-all = yes max-messages = 0 get-url = " http://192.168.11.100/sms/mo.php?id=%I&sc=%P&phone=%p&text=%a&meta=%D&dt=%t&unixts=%T " Thank you for your help! Jeff -- Jeff Thorn Principal Software Architect Thorn Technologies, LLC www.thorntech.com @thorntech <http://twitter.com/thorntech> | LinkedIn<http://www.linkedin.com/in/jeffthorn> | Facebook <http://www.facebook.com/thorntechnologies>
