Concept visualisation of an engineer commissioning a professionally cabled AV-over-IP rack room
Solution 10 / 10

AV systems integration

AV over IPin Dubai & the UAE

The right source. Wherever it is needed.

Route media across an agreed network, with clear capacity and access rules.

  • Acceptance on your scenarios
  • Documentation and training
  • 12-month workmanship warranty
  • Media across spacesDefine where each source needs to go.

  • An agreed networkPlan capacity, multicast and boundaries.

  • Controlled accessSeparate viewing and device control.

  • A documented systemRecord routes, limits and acceptance checks.

01 What we deliver

Plan the routes before choosing the network.

AV over IP connects source encoders and display decoders through managed Ethernet switches. A source can serve several displays, while each display selects its own permitted route. We coordinate the source formats, endpoints, network, controls and operating responsibilities as one design.

The three reference configurations below distribute HDMI video with its accompanying audio. They use one compatible endpoint platform and one AV network segment. USB control of remote computers, independent networked audio, recording and browser streaming need their own agreed interfaces and capacity checks.

Reference designs · example quantities · project selection and system tests required. These are starting points for a project, not completed installations or fixed procurement packages.

For remote computer operation, see Control rooms & command centres. For playlists, schedules and content publishing, see Digital signage & retail displays. Those workflows add functions beyond the video routes below.

Where it is used

Real spaces, the people in them and what matters.

Who works in each kind of av over ip space, what they work with, and which typical configuration it usually starts from.

Application register
No.EnvironmentWho uses itWork and contentWhat matters mostTypical systems
A01A group of meeting roomsStaff and facilities teamShare two presentation sources with four displaysSimple routes and known source formatsIP-01
A02Training and overflow roomsTrainers and AV staffShow a lesson or presentation in nearby roomsPicture, accompanying audio and measured delayIP-01 or IP-02
A03Offices on two floorsCommunications and IT teamsSelect shared sources independently on each floorSimultaneous routes across the floor linkIP-02
A04Hotel event spacesVenue techniciansDistribute event feeds to breakout displaysRepeatable presets and operator permissionsIP-02
A05A three-building campusCampus AV and IT teamsRoute twelve sources to eighteen displaysFibre paths, multicast load and recovery boundariesIP-03
A06Existing local AV systemsRoom operatorsShare a matrix output with another roomConfirmed HDMI handoff and source ownershipAny configuration after interface review

02 Typical configurations

Three starting points, side by side.

Choose the workflow closest to your brief. Compare its scope, interfaces and operating limits before selecting equipment.

AttributeIP-01Local source sharingSelect two sources across four displays on one switch.IP-02Two-floor distributionRoute six sources to eight displays across a calculated fibre link.IP-03Three-building distributionConnect twelve sources and eighteen displays through a shared fibre core.
ScenarioTwo sources shared by four displaysSix sources shared by eight displaysTwelve sources shared by eighteen displays
LocationsOne switch locationTwo floorsThree buildings
Encoder / decoder count2 / 4; 6 endpoints6 / 8; 14 endpoints12 / 18; 30 endpoints
Local distribution2 encoders + 4 decoders3 encoders + 4 decoders per floor4 encoders + 6 decoders per building
NetworkOne access switchTwo access switchesThree access switches and one shared core
Optical links in the baseNoneOne 10 Gb/s link between floorsThree 10 Gb/s links, one per building
Route controlOne controller, one operator clientOne controller, two operator clientsOne controller, three operator clients
Concurrent viewingFour displays, each with one selected sourceEight displays, each with one selected sourceEighteen displays, each with one selected source
Recovery boundaryRestore the single switch and controllerRestore the affected floor or linkRestore the affected building or core; optional spare fibre paths

Reference configurations. Example quantities require project selection, compatibility checks and system acceptance tests. The 10 Gb/s links are calculated choices for these route matrices. They do not guarantee capacity for additional streams, USB, multiple windows or future endpoints. All three configurations use L2 media distribution; routing media between IP subnets is a separate design.

Starting points, not fixed packages: we confirm the room, the platform and the quantities with you, and run the acceptance checks in your space before handover. Not sure which fits? Describe your space →

03 How each option works

Every connection drawn before anything is installed.

Each option with its schematic: the devices and every link between them, the signal paths in plain words, what the system holds, what is agreed separately and how you accept it. Your project gets its own drawings from the site survey.

IP-01

Local source sharing

Staff select either of two HDMI sources on each of four displays. One source may be shown on all four displays at once.

Reference design; tests required

  • Two sources · four displays
  • One local access switch
  • One selected feed per display
IP-01 · system schematic

Signal flow

IP-01 signal flow: Two HDMI sources feed two encoders, one switch and four decoders connected to four displays; the operator client and controller exchange commands and status.
  • Video / LED data
  • Network / data

Typical architecture · not a project drawing

Connection schedule 4 links
  1. L012 HDMI sources 2 encoders - fixed TX2 HDMI with audio
  2. L022 encoders - fixed TX 1 access switch A2 x 1G + PoE+
  3. L031 access switch A 4 decoders - fixed RX4 x 1G + PoE+
  4. L044 decoders - fixed RX 4 displays4 HDMI with audio

Control & status

IP-01 control & status: Two HDMI sources feed two encoders, one switch and four decoders connected to four displays; the operator client and controller exchange commands and status.
  • Control / status

Typical architecture · not a project drawing

Connection schedule 8 links
  1. L054 decoders - fixed RX 1 access switch AIGMP membership + status
  2. L061 wired operator client 1 access switch A1G wired access
  3. L071 route controller 1 access switch Acommands via switch
  4. L081 access switch A 1 route controllerendpoint status via switch
  5. L091 client IT gateway interface 1 access switch Aallowed unicast services
  6. L10Client IT services and administration 1 client IT gateway interfacefirewall policy
  7. L111 access switch A 4 decoders - fixed RXroute commands
  8. L122 encoders - fixed TX 1 access switch Asource status
Trace routes in the interactive drawing

How it works

Intended result. Operators can recall permitted routes and see endpoint status. Commissioning checks all eight source-to-display pairs and simultaneous viewing on all four displays.

  1. Local media
    1. Two sourcesOne fixed encoder per HDMI source.
    2. Managed AV switchCarries selected streams to four fixed decoders.
    3. Four displaysOne picture with source audio per display.

Operators can share one source across all four displays. A separate controller manages permissions and status. There is no USB control, multiview, recording or redundant network in the base.

In the system

Two source encoders, four display decoders, one managed PoE+ access switch, one route controller and one wired operator client. The example includes six HDMI connections, endpoint network cabling and one local rack/power installation set. Two sources, four displays and the agreed IT service connection are client interfaces.

Source encoders
2
Display decoders
4
Managed PoE+ access switches
1
Shared controller / operator clients
1 / 1
Local installation sets
1

Example quantities: makes, models and compatibility are confirmed in your BOQ.

Agreed separately

  • The six endpoints have fixed encoder or decoder roles.
  • There is one selected video feed per display, with its source audio.
  • The base has no inter-switch backbone or automatic network recovery.
  • Remote keyboard/mouse control, multiview and recording are outside this scope.

How you accept it

The test plan is agreed before procurement. Every result records equipment and firmware, source/display formats, the route set and pass limits. The example designs have not yet undergone these tests. - IP-01: all 8 source-to-display pairs, both sources active, and one source on all four displays. - IP-02: all 48 pairs, all eight displays active, and three distinct remote feeds in each direction at the same time. - IP-03: all 216 pairs, all eighteen displays active, and the designed worst-case incoming and outgoing building traffic. - Every configuration: picture and accompanying audio, source switching, EDID/HDCP where required, delay, PoE startup, multicast containment, status feedback and access permissions. - Recovery: agreed device restarts and backup restoration; for selected R01, fibre loss and restoration with measured interruption and no network loop. Single-device failures remain inside the stated recovery boundary.

Handover record: Agreed criteria, equipment and version schedule, measured test results and recovery procedure.

These are planned project checks. The reference configuration has not passed physical system acceptance.

Discuss IP-01 with an engineer
IP-02

Two-floor distribution

Each floor has three sources and four displays. Operators can select local or other-floor sources without moving patch cables.

Reference design; tests required

  • Six sources · eight displays
  • Two floors with one fibre uplink
  • Local failure behaviour needs testing
IP-02 · system schematic

Signal flow

IP-02 signal flow: Each floor has three encoders and four decoders, joined by access switches and a fibre link; two clients use one controller.
  • Video / LED data
  • Network / data

Typical architecture · not a project drawing

Connection schedule 9 links
  1. L013 HDMI sources 3 encoders - fixed TX3 HDMI with audio
  2. L023 encoders - fixed TX 1 access switch A3 x 1G + PoE+
  3. L031 access switch A 4 decoders - fixed RX4 x 1G + PoE+
  4. L044 decoders - fixed RX 4 displays4 HDMI with audio
  5. L073 HDMI sources 3 encoders - fixed TX3 HDMI with audio
  6. L083 encoders - fixed TX 1 access switch B3 x 1G + PoE+
  7. L091 access switch B 4 decoders - fixed RX4 x 1G + PoE+
  8. L104 decoders - fixed RX 4 displays4 HDMI with audio
  9. L131 access switch A 1 access switch B1 duplex fibre / 2 SFP+ 10G each direction; budget 3.75G each

Control & status

IP-02 control & status: Each floor has three encoders and four decoders, joined by access switches and a fibre link; two clients use one controller.
  • Control / status

Typical architecture · not a project drawing

Connection schedule 12 links
  1. L054 decoders - fixed RX 1 access switch AIGMP membership + status
  2. L061 wired operator client 1 access switch A1G wired access
  3. L114 decoders - fixed RX 1 access switch BIGMP membership + status
  4. L121 wired operator client 1 access switch B1G wired access
  5. L141 route controller 1 access switch Acommands via switch
  6. L151 access switch A 1 route controllerendpoint status via switch
  7. L161 client IT gateway interface 1 access switch Aallowed unicast services
  8. L17Client IT services and administration 1 client IT gateway interfacefirewall policy
  9. L181 access switch A 4 decoders - fixed RXroute commands
  10. L193 encoders - fixed TX 1 access switch Asource status
  11. L201 access switch B 4 decoders - fixed RXroute commands
  12. L213 encoders - fixed TX 1 access switch Bsource status
Trace routes in the interactive drawing

How it works

Intended result. Eight displays can use an agreed mix of local and remote sources, supported by a tested route matrix and a measured inter-floor load. All 48 source-to-display pairs enter the acceptance schedule.

  1. Within either floor
    1. Three sources per floorSix fixed encoders in total.
    2. Local access switchesOne per floor; eight decoders in total.
    3. Four displays per floorEach receives one selected source.
  2. Between floors
    1. Floor A switchOne duplex 10 Gb/s fibre link; three distinct remote feeds each way.
    2. Floor B switchSame AV VLAN. Displays may share a received source.

The single uplink is not resilient. Local behaviour during uplink or controller failure must be tested. The base is one extended AV VLAN, not routed media across the corporate network.

In the system

Six encoders, eight decoders, two managed PoE+ access switches, one duplex optical link with two 10 Gb/s transceivers, one shared controller and two wired operator clients. Fourteen HDMI connections and two local installation sets complete the example.

Source encoders
6
Display decoders
8
Managed PoE+ access switches
2
Duplex optical links / transceivers
1 / 2
Shared controller / operator clients
1 / 2
Local installation sets
2

Example quantities: makes, models and compatibility are confirmed in your BOQ.

Agreed separately

  • The calculation allows three different remote sources in each direction at once; displays may share a source.
  • One AV VLAN extends between the switches.
  • The base optical link is single, so its loss removes inter-floor distribution.
  • Local operation during a controller or uplink failure is tested and documented rather than assumed.

How you accept it

The test plan is agreed before procurement. Every result records equipment and firmware, source/display formats, the route set and pass limits. The example designs have not yet undergone these tests. - IP-01: all 8 source-to-display pairs, both sources active, and one source on all four displays. - IP-02: all 48 pairs, all eight displays active, and three distinct remote feeds in each direction at the same time. - IP-03: all 216 pairs, all eighteen displays active, and the designed worst-case incoming and outgoing building traffic. - Every configuration: picture and accompanying audio, source switching, EDID/HDCP where required, delay, PoE startup, multicast containment, status feedback and access permissions. - Recovery: agreed device restarts and backup restoration; for selected R01, fibre loss and restoration with measured interruption and no network loop. Single-device failures remain inside the stated recovery boundary.

Handover record: Agreed criteria, equipment and version schedule, measured test results and recovery procedure.

These are planned project checks. The reference configuration has not passed physical system acceptance.

Discuss IP-02 with an engineer
IP-03

Three-building distribution

Buildings A, B and C each contain four sources and six displays. A shared operator system controls routes across the site.

Reference design; tests required

  • 12 sources · 18 displays
  • Three buildings through one core
  • Optional second link does not protect the core
IP-03 · system schematic

Signal flow

IP-03 signal flow: Three groups of four encoders and six decoders connect through access switches to one core, with a central controller and one client per building.
  • Video / LED data
  • Network / data

Typical architecture · not a project drawing

Connection schedule 15 links
  1. L014 HDMI sources 4 encoders - fixed TX4 HDMI with audio
  2. L024 encoders - fixed TX 1 access switch A4 x 1G + PoE+
  3. L031 access switch A 6 decoders - fixed RX6 x 1G + PoE+
  4. L046 decoders - fixed RX 6 displays6 HDMI with audio
  5. L074 HDMI sources 4 encoders - fixed TX4 HDMI with audio
  6. L084 encoders - fixed TX 1 access switch B4 x 1G + PoE+
  7. L091 access switch B 6 decoders - fixed RX6 x 1G + PoE+
  8. L106 decoders - fixed RX 6 displays6 HDMI with audio
  9. L134 HDMI sources 4 encoders - fixed TX4 HDMI with audio
  10. L144 encoders - fixed TX 1 access switch C4 x 1G + PoE+
  11. L151 access switch C 6 decoders - fixed RX6 x 1G + PoE+
  12. L166 decoders - fixed RX 6 displays6 HDMI with audio
  13. L191 access switch A 1 shared core10G fibre TX budget 5G / RX 7.5G
  14. L201 access switch B 1 shared core10G fibre TX budget 5G / RX 7.5G
  15. L211 access switch C 1 shared core10G fibre TX budget 5G / RX 7.5G

Control & status

IP-03 control & status: Three groups of four encoders and six decoders connect through access switches to one core, with a central controller and one client per building.
  • Control / status

Typical architecture · not a project drawing

Connection schedule 17 links
  1. L056 decoders - fixed RX 1 access switch AIGMP membership + status
  2. L061 wired operator client 1 access switch A1G wired access
  3. L116 decoders - fixed RX 1 access switch BIGMP membership + status
  4. L121 wired operator client 1 access switch B1G wired access
  5. L176 decoders - fixed RX 1 access switch CIGMP membership + status
  6. L181 wired operator client 1 access switch C1G wired access
  7. L22OPTION R01 ONLY 1 shared coreuses second uplink on A, B and C
  8. L231 route controller 1 shared corecommands via switch
  9. L241 shared core 1 route controllerendpoint status via switch
  10. L251 client IT gateway interface 1 shared coreallowed unicast services
  11. L26Client IT services and administration 1 client IT gateway interfacefirewall policy
  12. L271 access switch A 6 decoders - fixed RXroute commands
  13. L284 encoders - fixed TX 1 access switch Asource status
  14. L291 access switch B 6 decoders - fixed RXroute commands
  15. L304 encoders - fixed TX 1 access switch Bsource status
  16. L311 access switch C 6 decoders - fixed RXroute commands
  17. L324 encoders - fixed TX 1 access switch Csource status
Trace routes in the interactive drawing

How it works

Intended result. The site has an explicit routing and ownership plan for all eighteen displays. Acceptance covers all 216 source-to-display pairs, concurrent building traffic and the selected recovery scope.

  1. Local building paths
    1. Four sources per buildingTwelve encoders across A, B and C.
    2. Three access switchesEach serves its local decoders.
    3. Six displays per buildingEighteen selected primary feeds in total.
  2. Between buildings
    1. Access switchesUp to four outgoing local feeds per building.
    2. Shared coreThree duplex fibre links; one single core.
    3. Other buildingsUp to six distinct incoming feeds per building.

Optional R01 adds a second fibre path to the same core, with controlled link failover. It does not protect the core or access switches and does not imply doubled usable bandwidth.

In the system

Twelve encoders, eighteen decoders, three managed PoE+ access switches, one shared core, three duplex fibre links with six 10 Gb/s transceivers, one shared controller and three wired operator clients. There are thirty HDMI connections, three access installation sets and one core installation set.

Source encoders
12
Display decoders
18
Managed PoE+ access switches
3
Shared core switch
1
Duplex optical links / transceivers
3 / 6
Shared controller / operator clients
1 / 3
Local installation sets
4

Example quantities: makes, models and compatibility are confirmed in your BOQ.

Agreed separately

  • Each display receives one selected primary feed.
  • The example permits up to six distinct incoming remote feeds and four outgoing local feeds per building.
  • The core, controller and each endpoint are single devices.
  • The separately selected R01 option adds a second fibre path to the same core for each building, with controlled link failover; it does not protect against a core or access-switch failure.
  • Core redundancy or routed inter-building media requires a revised design.

How you accept it

The test plan is agreed before procurement. Every result records equipment and firmware, source/display formats, the route set and pass limits. The example designs have not yet undergone these tests. - IP-01: all 8 source-to-display pairs, both sources active, and one source on all four displays. - IP-02: all 48 pairs, all eight displays active, and three distinct remote feeds in each direction at the same time. - IP-03: all 216 pairs, all eighteen displays active, and the designed worst-case incoming and outgoing building traffic. - Every configuration: picture and accompanying audio, source switching, EDID/HDCP where required, delay, PoE startup, multicast containment, status feedback and access permissions. - Recovery: agreed device restarts and backup restoration; for selected R01, fibre loss and restoration with measured interruption and no network loop. Single-device failures remain inside the stated recovery boundary.

Handover record: Agreed criteria, equipment and version schedule, measured test results and recovery procedure.

These are planned project checks. The reference configuration has not passed physical system acceptance.

Discuss IP-03 with an engineer

04 Project experience of our team

The working drawing, as we issue it.

A demonstration hall of RC‑08 run over Dante: the console, an expansion module and five network amplifiers on one switch, feeding eleven loudspeakers and two subwoofers. Audio travels as network streams from the console to every amplifier.

Structural connection diagram, creative industries lab: a working drawing of project RC-08 with device tags, connectors and numbered cables
Sheet 7 — Creative industries labRC-08 · A2 · anonymised
All 9 sheets of RC-08, PDF (303 KB)

05 Engineering

What the design has to get right.

The checks behind every drawing. Rules of thumb are starting points; the project values are confirmed with the people named.

Design parameters
No.ParameterGuidanceRule of thumbConfirmed with
D01Independent feedsCount sources and destinations separatelyOne encoder per source and one decoder per display; no simultaneous encoder/decoder double countingAV designer
D02Formats and protectionRecord actual resolution, frame rate, colour format, audio and protected-content needsQualify every required end-to-end route; agree display EDID and content permissionsAV team and source owner
D03Simultaneous routesSpecify which sources each display needs togetherOne primary feed per display in all three examplesClient and AV designer
D04Backbone capacityBudget unique subscribed streams per direction on every linkThe example 10 Gb/s links apply only to the documented matricesNetwork designer
D05Switch ports and powerCount control and service links as well as AV endpointsReserve access ports and check total PSE budget with the installed power suppliesNetwork and electrical teams
D06Multicast and VLANsAgree membership, querier and forwarding behaviourOne L2 AV segment in the base; separate switch management and controlled IT accessIT team
D07Delay and switchingMeasure with the real source and display chainNumerical acceptance limits are agreed before procurementClient and commissioning engineer
D08ResilienceList exactly which failures must be survivedSingle core/controller in the base; R01 protects selected fibre-link failures onlyClient and IT team
D09Distance and optical lossSurvey the actual route and terminationsMatch transceivers and fibre; verify the optical budgetCabling contractor
D10ExpansionRecalculate after adding endpoints or servicesSpare ports alone do not establish spare media or power capacityAV and IT teams

Common mistakes

And how the design process prevents them.

  1. M01

    Mistake: Counting one transceiver as an encoder and decoder at the same time

    Prevention: Assign one operating role to every endpoint

  2. M02

    Mistake: Assuming all Ethernet AV devices interoperate

    Prevention: Qualify the exact platform, stream type and firmware combination

  3. M03

    Mistake: Selecting the backbone from the display count alone

    Prevention: Calculate distinct subscribed streams in both directions

  4. M04

    Mistake: Using per-port PoE capability as the switch's total power budget

    Prevention: Check the installed PSE supply and all allocated loads

  5. M05

    Mistake: Connecting a spare fibre without a loop-control plan

    Prevention: Configure and test the selected redundant topology

  6. M06

    Mistake: Treating a routed management interface as routed media support

    Prevention: Document AV VLAN boundaries and design multicast routing separately

How a typical system fits together

Four layers, from the sources to the people operating the system, and the interfaces between them.

  1. L1

    Sources

    Where the content comes from

    • Client source devices
    • One encoder for each independent source

    One independent source for each encoder. HDMI video and accompanying audio; one fixed encoding role per endpoint

  2. L2

    Processing & transport

    How signals are routed and processed

    • Managed access switches
    • Inter-floor fibre or shared core where required

    1 Gb/s endpoint links; calculated 10 Gb/s optical backbone; multicast membership and PoE

  3. L3

    Displays & audio

    What people see and hear

    • One decoder for each independent display
    • Destination displays

    HDMI to the display; a selected source and its audio; actual display formats checked One selected source and its accompanying audio per display.

  4. L4

    Control & operation

    How the system is run every day

    • Operator clients
    • Shared route controller, network administration

    Commands and endpoint feedback over IP; authorised IT access through the agreed gateway

Connected to the building and its IT

The systems this solution exchanges signals or data with, and why. Each interface is agreed with the system owner.

  • I01

    Existing room AV

    HDMI from an agreed local output

    Share the selected room programme; it is one encoded source, not all matrix inputs

  • I02

    Corporate IT services

    Allowed unicast services through a gateway/firewall

    Addressing, time, name resolution and administration; no automatic media transit to corporate networks

  • I03

    Operator control

    Supported IP control interface

    Select permitted routes and show endpoint feedback; client licences and programming included in final scope

  • I04

    Signage players

    HDMI from the player to an encoder

    Distribute the player's selected content; playlist management stays with its CMS

  • I05

    Recording or web streaming

    Dedicated, compatible output and capture/streaming interface

    Separate option; a platform's native multicast stream is not automatically browser or recorder compatible

  • I06

    Remote computer operation

    Qualified USB/KVM extension and host/device assignment

    Separate option with its own peripherals, permissions and bandwidth budget

  • I07

    Audio systems

    HDMI audio, or a separately qualified audio interface

    The base follows video audio; independent audio routing and clocking require separate design

  • I08

    Facilities monitoring

    Supported switch/controller alarms

    Agreed power, temperature and link alarms; no assumed building-management protocol

The references we design to

Equipment documentation, industry guides and project requirements. Applicable editions and acceptance criteria are confirmed for the site.

Equipment documentation and industry guides04

  • IEEE 802.1Q — Bridges and Bridged NetworksProject design referenceVLAN boundaries and bridge topologyCheck current edition
  • IEEE 802.3 — EthernetProject design referenceCopper, optical and PoE interfaces; the selected endpoint requires Type 2 PoE+ powerCheck current edition
  • RFC 4541 — IGMP/MLD snooping considerationsProject design referenceInformational guidance for multicast forwarding; switch implementation still requires qualificationCheck current edition
  • RFC 9776 — Internet Group Management Protocol, Version 3Project design referenceIGMP reference; choose the version supported by the actual endpoint and switch configurationCheck current edition

Local and project requirements01

  • Client IT and ICT policiesProject design referenceAddressing, approved switches, cabling, access, software changes and support ownershipCheck current edition

06 From brief to handover

Six stages, with what you receive at each.

Start with the people, activities and operating conditions. You approve the design before procurement and accept the system on your own scenarios.

  1. Stage 01

    Scope and architecture

    Source, display and simultaneous-route inventory Format, delay and recovery requirements Agreed AV/IT responsibilities

    • Source and display inventory
    • Simultaneous route matrix
    • Agreed AV and IT ownership
  2. Stage 02

    Design and approval

    Network, port and fibre drawings Per-link traffic and per-switch power budgets VLAN, multicast and control design

    • Network and fibre drawings
    • Traffic and power budgets
    • Multicast and control plan
  3. Stage 03

    Selection and supply

    Matched endpoint and switch schedule Confirmed optics, power supplies and licences Bench qualification of critical interfaces

    • Matched encoders and decoders
    • Qualified switches and optics
    • Power and licence schedule
  4. Stage 04

    Installation and programming

    Installed and labelled links and endpoints Addressing, multicast and route presets Permissions, feedback and monitoring configuration

    • Labelled links and endpoints
    • Configured multicast and routes
    • Operator permissions and feedback
  5. Stage 05

    Commissioning and tests

    Route and concurrent-load test report Format, protected-content and delay checks Recorded restart and selected failure tests

    • Route and concurrent-load tests
    • Picture, audio and delay checks
    • Restart and recovery records
  6. Stage 06

    Handover

    As-built network and multicast maps Configuration backups and recovery guide Operator/admin training and support boundary

    • Network maps and settings
    • Operator and admin training
    • Recovery and support guide

Ready to start? Send a plan, a brief or a BOQ — or just describe the space. AV design, programming and commissioning →

Request a project review

07 Questions

What people ask before a av over ip project.

Practical answers before the project starts. Anything else, ask an engineer.

Can we use our existing network?

Possibly. We review switch features, current loading, available ports, power, fibre and IT policies. A VLAN provides separation but does not create bandwidth or prove multicast compatibility.

Does a 10 Gb/s backbone cover every system?

No. In IP-02 and IP-03 it follows the stated source and display arrangement, with one primary feed per display. Extra streams, USB or new endpoints require a new calculation and load test.

Can encoders and decoders from different platforms work together?

Only when their exact media and control interfaces have been qualified together. Ethernet connectivity alone establishes no media compatibility, even when the connectors and advertised resolution match.

Can one endpoint send and receive two independent pictures?

The endpoints selected for these examples operate as an encoder or a decoder. A room that must send one source and receive another independently needs separate endpoints in this design.

Does this include USB, KVM or web streaming?

The base distributes video and accompanying audio to displays. Remote USB control and browser streaming are separate workflows that need qualified interfaces, permissions and additional capacity where applicable.

Can the system cross subnets or link buildings?

Fibre links connect the buildings in IP-03 while keeping media within one L2 AV segment. Routed L3 distribution is possible only after a separate multicast, discovery, control and security design for the selected platform.

What happens when a link or switch fails?

The base has single links and devices. The affected paths may be unavailable until restoration. IP-03's optional R01 spare fibre paths address link failures to the same core; they do not duplicate the core, access switches, endpoints or controller. Agreed interruption limits are tested.

Who runs the system after handover?

A written support boundary assigns switch, endpoint, control, account and firmware duties. Operators receive a route guide; administrators receive configurations, test records and a recovery procedure.

What helps us reply with substance

  1. Source and display inventory, including connector types and exact models.
  2. Required formats, protected content and accompanying audio.
  3. Simultaneous route matrix and any future growth allowance.
  4. Room/floor/building plan and measured cable distances.
  5. Existing switch models, firmware, optics, port use and PoE supplies.
  6. VLAN, addressing, multicast, access and remote-support policies.
  7. Required switching time, end-to-end delay and tolerated interruption.
  8. USB, independent audio, recording or streaming needs, plus named AV and IT owners.

Request a project review

Share your AV network brief.

Send your source and display list, network topology and simultaneous routes. A floor plan or a short description is enough to start.

  1. 01
    We review your materials

    The system composition, links with adjacent trades and the scope of work.

  2. 02
    We come back with questions

    A preliminary approach to the system and the points that need closing.

  3. 03
    We propose the next step

    The scope of further design and the path to a commercial proposal.

Have a BOQ or tender drawings? Send an RFQ

AV over IPReply from an engineer