Hi, Someone else observed similar behavior of validity period parameter?
I've done more tests on it and it really seems that all SMS keep in sms_rounter thread more than 10 minutes (sometimes 20, sometimes more than 30 minutes, and so on). Thanks Anderson ________________________________ Hi, I'm testing the validity-period parameter with Kannel, since I started to get complaints about a big amount of SMS in the smsbox queue. More precisely, I've discovered that such SMS were using invalid phone numbers as target (like unexisting numbers and/or number is wrong format in mine region, with 13, 14 numbers). Actually, when the queue gets 200, 250 SMS or more in the same day, the 'well-formed' SMS deliver is delayed (probably because of sms routing thread concurrency). So far, I've to restart the SMSC (it's a local GSM modem, Cinterion M35i model, connected by serial port), or even restart the whole Kannel to clean up this queue. My point: change the default behavior for validity period = 24 hours, to a lesser number, like 10 minutes. If this is the best possible solution I'm not sure yet. Attached, I have the config file and the smsc logs. I've set "validityperiod = 1" and then, logs started to show: DEBUG: AT2[mc35i]: TP-Validity-Period: 10 minutes My question: I sent an 'invalid SMS' (wrong number, for simulation) at 14:12. On each 30 sec, re-routing thread attempted to send it again. Fine so far. But, I saw the queue "clear" (equal a 0) only at 14:42, 30 minutes later. Shouldn't it be clear something around 10 minutes after first try? Thanks is advance Anderson
