Verification note: Results are design aids, not stamped engineering or code approval. Always check the current project specification, adopted code, manufacturer data and latest edition of the cited standard before construction or procurement.
SIGNAL & NETWORK
Clearport
Port matrix builder for IT handover.
Use this page to prepare a concise IT handover sheet listing source device, destination, protocol, direction and port requirements.
IT handover port matrix
Presets are protocol references only; they are not proof that a selected AV product uses those services.
| Device / service | Target | Transport | Port(s) | Purpose | Source |
|---|
There is no universal “AV firewall formula.” A correct handover row must be tied to the selected endpoint/service, direction, source and destination scope, transport, port, discovery/multicast behavior, firmware/version and manufacturer documentation.
WORKED EXAMPLE
Example — control and AVoIP port matrix
The example diagram illustrates why IT teams need a simple matrix instead of scattered notes. Group ports by function and protocol to reduce approval time.
Source details
- IANA Service Name and Transport Protocol Port Number Registry — canonical registered service/port reference.
- RFC 6762 — mDNS.
- RFC 3411 — SNMP architecture.
- AV endpoint port requirements must still be verified against manufacturer documentation; registered ports do not prove a product uses a service.
- AVIXA AV-over-IP planning resource — networked AV design context.