Meeting Room Deployment Checklist for AV Integrators
For an integrator, margin is made or lost on repeatability. A rollout that goes smoothly in the first room and stalls in the second is rarely a hardware problem. It is almost always a network surprise: a blocked port, an isolated VLAN, a proxy nobody mentioned, or a firewall change that needs a week of approvals.
This checklist applies to any wireless presentation, conferencing or room scheduling device, whichever vendor you deploy. It helps you find those surprises before install day, so every room after the first one is a repeat of the same routine.
Phase 1: Before you visit (site survey)
- Confirm the room list. For each room, note the display type and inputs, mounting method, power availability and the location of the nearest network drop.
- Decide how each device will connect. Wired Ethernet is usually the most reliable choice for a fixed room device. WiFi, a guest network or a standalone access point may be options, but each has trade offs for stability and security.
- Ask whether isolation is required. Some customers want meeting traffic kept apart from the corporate network. Confirm early, because it changes how users discover and connect to the room device.
- Ask IT about the basics. Is there a proxy, VLAN segmentation, client isolation on WiFi, or a policy that blocks multicast traffic? Who approves firewall changes, and how long does that take?
- List the sharing methods and apps in scope. AirPlay, Miracast, Google Cast, browser sharing and vendor apps each behave differently on a network. If the room will also host video calls, check the firewall requirements of the conferencing platform separately.
Phase 2: Network readiness and ports
Hand this section to the customer’s network team. Exact port numbers differ by vendor and software version, so always ask the vendor for a current firewall and port matrix instead of relying on a generic list. In most deployments you will want to confirm the following:
| Area | What to check |
|---|---|
| IP addressing | DHCP or static addresses for each room device, and a plan for reservations |
| DNS | Name resolution works, including for any vendor cloud services |
| Time sync | NTP (UDP 123) is reachable, since many certificates and calendar syncs depend on correct time |
| Outbound internet | HTTPS (TCP 443) to vendor and calendar services, plus any additional ports the vendor lists |
| Device discovery | Whether multicast DNS (UDP 5353) and similar discovery traffic can pass between where users sit and where the room device sits |
| Vendor specific ports | The ports and ranges used for screen sharing, casting and control, as listed in the vendor documentation |
| Proxy and inspection | Whether traffic goes through a proxy or SSL inspection, and whether the device supports it |
Points worth discussing with the customer:
- Peer to peer versus network based connections. Some casting methods, such as Miracast over WiFi Direct, connect devices directly and do not depend on the corporate firewall. Network based modes, including Miracast in infrastructure mode, rely on the network, so firewall rules and segmentation apply.
- Discovery across VLANs. If laptops and the room device sit on different network segments, discovery often fails unless the network team permits or relays the traffic. This is the most common reason a room works in the lab and not in the office.
- Guest and visitor access. Decide how visitors will share. Options include a guest network, a browser based method, or an app, and each has different network implications.
- Video conferencing. Teams, Zoom and Google Meet each publish their own network requirements. Check them alongside the room device requirements.
Phase 3: Install and configure each room
- Mount the display and connect power and the network cable.
- Connect the room device and record its IP address and MAC address for the handover sheet.
- Protect the settings with an admin code or equivalent so only authorized staff can change them.
- Configure the network mode and any isolation or proxy settings.
- Update the firmware or software to the version approved for the project.
- Name the room consistently, so users can find the right one in a list.
Phase 4: Test and hand over
Run the same test list in every room so the results are comparable:
- Share from Windows, Mac, iPhone, Android and a browser where applicable.
- Test the guest flow from a device that is not on the corporate network.
- Launch the video conferencing platform and confirm audio, camera and content sharing.
- Reboot the device and confirm the room recovers without anyone touching it.
- Record the results and give the customer a one page summary for each room.
Planning rollout time per room
Avoid quoting a fixed number to a customer before the survey. Rollout time depends on three things: how ready the network is, how many rooms are in scope, and how many features are enabled. A simple way to plan it:
Total time = one time network approval + (install and test time per room x number of rooms) + customer acceptance.
Frequently Asked Questions
Do meeting room devices need internet access?
It depends on the product and the features in use. Some features, such as cloud services or calendar sync, need outbound internet access. Others can work on a local network only. Confirm this with the vendor before the survey.
Can a room device sit on an isolated network?
Often yes, but how it works varies by product. Check whether the device supports a second network connection, a dedicated access point or VLAN placement, and how users will discover it from the corporate network.
Why does screen sharing work in the lab but not in the office?
Usually because the lab network is flat and the office network is segmented. Discovery traffic, blocked ports and client isolation are the usual causes.
Do video conferencing apps need extra firewall rules?
Yes. Each platform publishes its own requirements, which you should check in addition to those of the room device.
How do I standardize many rooms?
Use one configuration template, one naming convention and one test list for every room, and record the IP and MAC address of each device on the handover sheet.







