On Fri, Oct 7, 2011 at 3:41 PM, Gustavo <ggb at tid.es> wrote: >> One of the easier workaround is to shorten the keep alive interval to >> say slightly less than half of what your server setting is, I think >> that should cover problem no 3 and 4. > > 3. If you don't control the server you don't know what the Flow-Timer is > going to be to manually configure it in the client. Sure. I already acknowledged what are missing. So do you have the control over the server or not? If yes, why complain? If no, well too bad then. > 4. If you are sending a lot of INVITEs, MESSAGEs.... you are not going > to send any CRLFCRLF keepalive and the server will assume the connection > is broken. > Why would you disconnect a perfectly fine connection with a lot of messages going? >> > Any idea of what is the problem? >> > >> >> There's no way to tell without seeing the stack trace. > > Find attached a screenshot with the stack trace. > Still no idea, sorry.
