There was a bug (fixed now) when TimerF fired when the transaction was past the Calling state. It would send a 408 to the TU. This would mean that a TU would see both a final response and a subsequent 4xx when the timer fired. It probably wouldn't have happened unless the timeout value for Timer F were reduced.