Jabber user goes offline for a while after receiving a ping stanza when data/wifi is switched ON

Hi,

In my XMMP client-server implementation, i noticed my client (iOS/Android) going momentarily offline for few seconds after receiving a ping from the ejabberd.

So, digging a bit in the logs, this happens when the first ping packet is sent to the client by the server AFTER the client has switched back ON the data/wifi connection.

I believe the client comes online due to the retry mechanism for xmpp requests that i have in place. If it wasn't there, the client would not have come online at all (GUESSING!).

Observerd:
A socket disconnect is initiated after the first ping is sent by the ejabberd server.

FYI, i have configured mod_ping's interval to be 15 seconds.

The Client-side console says: "Socket closed by remote peer." 
What could be wrong? Any pointers as to what should i look into?

Could this be any sort of timeout values which need to be configured in the ejabberd's yml or something?

Thanks!