I found this issue was filed as a bug and was reported as fixed on May 1st, 2017.
But, the result shows the bug hasn’t been fixed yet as of ttn v2.7.1. The ‘fport=0’ is still changed to ‘fport=1’ in the downlink message process.
See this posting for reference on filing this issue as a bug.