Hi, when using kannel with CMG SMSC and a provider which uses one connection to do both sending and receiving messages (incl. notification) there seems to be a kind of "Dead Lock" problem with sending messages and sending notifications. Situation is like this (I tried to simplify the description to make it easier to understand): I send 100 messages to Kannel. Kannel puts those 100 messages into its send queue. Then it sends out the first 5 messages (assuming WindowsSize is 5). Then I get back 5 ACKs and 5 notifications. After I got back the ACKs, Kannel sends out the next 5 messages. Then I get back 5 ACKs and 5 notifications, and so on. The problem is: Kannel seems to put the ACKs to the notifications in the same queue as the outgoing messages without any priority. So those ACKs are not sent until the last of the 100 MOs was sent. But we get into trouble, because the CMG SMSC keeps waiting for those ACKs and since they don't come, it's assuming that our side (meaning Kannel) is busy, so it delays sending the MT ACKs. Finally, we get into the situation when Kannel waits for MT ACKs (because CMG refuses sending them) and CMG waits for notification ACKs, since they are in the Kannel message queue. I think, to prevent this, Kannel would have to send any ACKs before sending any messages, meaning Kannel needs to set a higher priority on ACKs than on MTs. Is there any (configuration) solution for this problem? Thanks!
Kind regards, Holger -- COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test -------------------------------------------------- 1. GMX TopMail - Platz 1 und Testsieger! 2. GMX ProMail - Platz 2 und Preis-Qualit�tssieger! 3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post
