Get the math right.
Instead of a fixed 1-second dispatcher throttle this creates a DispatchThrottle configuration item so that the time amount can be configurable.
Reverse r2856 as it is reported to no longer be needed (for some uncertain reason).
This is needed at least to get the free(block) that is in the abort function... or we'll leak 64K.
The session was already destroyed. Doing it again causes problems.
Fix a couple of memory leaks, I think.
It's possible for the receiver to support V.29 only (and not also V.27ter).
While it's not clear in what configurations we should be signaling metric preferences, we certainly shouldn't be indicating inch preferences if Class1Resolutions doesn't include the inch-based resolutions.