On 3/8/07, XSG Telecom M.I. de Jong <[EMAIL PROTECTED]> wrote:
Kannel keeps putting DLRs into it's store and refuses to send them out... It DOES sent DLRs, some do get sent, some don't OR DLRs get sent with u huge delay. Looking at processor info the machine itself isn't stressed at all and Kannel doesn't seem to be stressed either. So why are the DLRs getting queued? Why isn't it just sending them out? And is there a way to FORCE Kannel to process it's DLR queue?
Try flushing the DLR queue. As always, details in User's Guide. http://www.kannel.org/download/1.4.1/userguide-1.4.1/userguide.html#AEN834 Totally off-topic though, after reading many books on Agile Software Development processes, including those from Ken Schwaber and Alistair Cockburn, I think I understand why conventional development processes tend to regard documentation as a required donkeywork. Now, agile processes value working software over complete documentation but in the case of Kannel we have both working software and excellent documentation yet people actually don't read it. Now it feels like there's something wrong here. Is this because documentation is so big and full of so much information, or is it so badly organized that people are having hard times reading it, or the product is so good people think they can figure out themselves without the need of reading the documentation, or people are being just lazy? Anyone? Hmm. -- Enver
