media server logo
Guida utente del prodotto

Porte attive

See which module owns each listener or transport port, open the owner and safely release only stale allocations.

Dove trovarlo in CallabaAdvanced → Active ports
Cosa fa questo modulo

The port inventory prevents hidden listener conflicts. Release is a recovery action, not routine cleanup: identify and stop the owning resource first.

Prima di iniziare

  • Administrator access.

  • A confirmed maintenance window if the port may belong to a live resource.

Impostazioni spiegate

Sono mostrati i controlli necessari all’operatore. Nomi interni dei campi ed eventi di implementazione sono intenzionalmente esclusi.

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.

Primo workflow sicuro

  1. 01

    Locate the conflicting port and read its transport and owning module.

  2. 02

    Open the owner and confirm whether it is active or still required.

  3. 03

    Stop or remove the stale resource through its own module.

  4. 04

    Release the allocation only when the owner is inactive and the port remains stale.

  5. 05

    Create or restart the intended listener and verify the port now belongs to it.

Esempi di workflow

Usalo quando

Resolve an SRT listener conflict

A new SRT server cannot bind to the requested UDP port.

Requested portBind failure
Port inventoryFind owner
Owning resourceStop / correct
SRT serverBind + test
Diagramma animato del workflow: Resolve an SRT listener conflict

Come costruirlo

  1. 1

    Find the UDP port in Active ports and open its owner.

  2. 2

    Confirm whether that resource is live, stale or misconfigured.

  3. 3

    Stop/remove the stale owner and release only the leftover allocation.

  4. 4

    Start the intended SRT server and connect a real client.

Verifica il risultato

  • 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.

Risoluzione dei problemi

A released port immediately returns

Controlla
  • Check whether the owning resource is still active or restarting.
  • Inspect the module lifecycle state.
Poi procedi così

Stop or reconfigure the real owner; repeated release cannot override an active listener.