Handle hard-coded RTCP ports in the Runner, not the Scenario

I have run into some issues running a scenario with a hard-coded RTCP port multiple times in a row (strange RTCP data). This allows for RTCP port to be specified at run-time rather than scenario creation time.