Question: Upon receiving an MCPTT (Mission Critical Push To Talk) call release step 2 request, what actions does the IWF (Interworking Function) floor control server's floor control arbitration logic undertake regarding resource management and state transition?
Option 1: Only pause running timers associated with state machines without releasing media plane resources.
Option 2: Release some, but not all, reserved media plane resources and enter an 'Idle' state.
Option 3: Release all reserved media plane resources, including those for specific floor control server state transition diagrams, and enter the 'Start-stop' state.
Option 4: Ignore the request if there are ongoing transmissions from other participants.
Explanation: This is correct because, according to the specified behavior, upon receiving an MCPTT call release step 2 request, the IWF floor control server must comprehensively manage resources by releasing all reserved media plane resources. This includes instances used for both general and basic floor control operations towards participants, as well as stopping any associated timers. Following resource release, transitioning into the 'Start-stop' state is mandated to properly reset for future operations. This ensures efficient resource utilization and prepares the system for new requests.