How to ensure no message is lost on ejabberd due to broken socket connection

I have deployed latest ejabberd (2.1.11) on Ubuntu server. The problem i am facing is my client is smartphone based and in case of network disruption like picking up a call(on 2g) there is no notification to server of a broken socket connection. As a result of this ejabberd passes message to the client which are lost.

Can somebody guide me to what exactly i should do to ensure server identifies the socket state correctly before sending message hence making it loss proof.

Have you find a Solution?

Have you find a Solution?

Syndicate content