Inactivity timeout trigger missing. #737
Description
It appears that start_inactivity() is not being called upon incoming network traffic (regression). The activity timer is active on the base for all channels, it's just not being reset on activity. This should be handled at the base channel, using any receive to reset the timer. Note that this is reset by calling channel::start_inactivity(), which is internally called by both channel::waiting() and cannel::resume(), though these are not invoked to continue the read loop, only to start it.