The port inventory prevents hidden listener conflicts. Release is a recovery action, not routine cleanup: identify and stop the owning resource first.
Before you start
Administrator access.
A confirmed maintenance window if the port may belong to a live resource.
Settings explained
These are the controls an operator needs to understand. Internal field names and implementation events are intentionally omitted.
Port inventory
Read ownership before taking action.
- Port
Allocated network port.
- Transport
TCP or UDP context associated with the allocation.
- Owning module
Resource that reserved the port.
- Open owner
Navigate to the module responsible for the allocation.
- Release
Remove a stale port allocation.
Stop and verify the owner first; releasing a live listener can interrupt service.
Safe first workflow
- 01
Locate the conflicting port and read its transport and owning module.
- 02
Open the owner and confirm whether it is active or still required.
- 03
Stop or remove the stale resource through its own module.
- 04
Release the allocation only when the owner is inactive and the port remains stale.
- 05
Create or restart the intended listener and verify the port now belongs to it.
Workflow examples
Resolve an SRT listener conflict
A new SRT server cannot bind to the requested UDP port.
How to build it
- 1
Find the UDP port in Active ports and open its owner.
- 2
Confirm whether that resource is live, stale or misconfigured.
- 3
Stop/remove the stale owner and release only the leftover allocation.
- 4
Start the intended SRT server and connect a real client.
Verify the result
- Every important listener has a recognizable owning module.
- A released stale allocation disappears from the inventory.
- The intended resource can bind and accept a real connection.
Troubleshooting
A released port immediately returns
Check- Check whether the owning resource is still active or restarting.
- Inspect the module lifecycle state.
Stop or reconfigure the real owner; repeated release cannot override an active listener.