not reachable after some stand-by time

Mobile client, f-droid without GCM push, dhtproxy and permanent notification enabled.

Receiving calls seems to work first, but after some hours it stops working.

A guess: Is the dhtproxy properly sending keep-alives to the clients every 14 Minutes? (To avoid NAT Gateway timeouts. Most mobile devices access the Internet through a device operated by the mobile service provider called a NAT (Network Address Translation) gateway. These will typically time out an idle connection after 15 minutes. https://www.isode.com/whitepapers/imap-idle.html)

Related to https://github.com/Corvusoft/restbed/issues/324 and the PR is her https://github.com/Corvusoft/restbed/pull/349

Normally it's ok. But yeah, it's a lead.

changed the description

Thanks, missing keep-alives would explain it for sure.

The 14 minute intervals are for TCP, UDP would require even shorter intervals. I'm not sure, but think I remember these NAT timeouts to be 2-5 minutes?

changed the description

the proxy use TCP :)

Perfect.

Hm, is the patch applied to the jami binaries, or are you waiting for it to come through upstream?

Or, applied to dhtproxy.j.n

In fact, I have just checked. I never finished nor merged upstream my work about TCP keep alive...

So indeed, this could be a major problem.

assigned to @sblin

added 1 deleted label

marked #548 (closed) as a duplicate of this issue

I'm wondering what effect the switch from restbed to restinio will have, for reliability and keep alive.

Edit: The keep alive patch here seems still not applied in upstream restbed.

Will be tested.

For restbed I did a PR here https://github.com/Corvusoft/restbed/pull/349 and https://github.com/savoirfairelinux/opendht/pull/384. But restbed seems dead. So, in fact, we currently choose to wait for @vivanov :)

assigned to @vivanov and unassigned @sblin

changed milestone to %Iteration 9

@ringthing

It will be an enhancement by going away from threads to std::async on top of which restinio is build!

Just tested it with handle-request-timeout and linux time, it works see: 61b4375;