Great question — answering as the UphillTech team:
That error happens when peer closes the connection (while kannel is still trying to read or send the message), and so kannel only shows this to you in the log trail. The issue is not with kannel but with the peer. Find out why the connection is closed by the peer. If the connection is not closed, then this error should not happen and kannel should be able to read/send the message. Thanks.
Full answer by Chris: https://stackoverflow.stackexchange.com/a/18828829 (CC BY-SA 2.5).
Need it done for your business? UphillTech.
