Venue intercom: coverage gaps and roaming between bases

Locate the dropout before moving bases

Mark control, stage, entrances, and adjoining rooms on the plan. Ask the operator to identify where reception stops and whether the director can still hear them. Note whether the issue appears while walking, standing still, or when more users gather.

Repeat a phrase and its reply beside the base. If it also fails there, first review roles, groups and permission to speak (Spanish). That comparison helps separate a misconfigured conversation from a location-dependent problem.

Keep the full model and version of each base and headset. Two similarly named devices may support different connections and base changes. Photograph which port each cable uses too; an RJ45 label alone does not describe that connection’s function.

Two linked hubs do not prove continuous coverage

During testing, check two things separately: conversation between stations on both bases, and an operator retaining that conversation while moving between their zones. A successful first test leaves the second pending.

Roaming Hub: review cascading, roles and startup sequence

The Hollyland Roaming Hub V1.0 manual, EN-14 distinguishes IP cascading for expanding stations and roaming from 4-wire cascading for expanding stations. It requires at least two meters between hubs. This instruction is for that model; it does not turn a conventional C1 Pro base into a Roaming Hub.

For two Roaming Hubs over IP, follow EN-15/17: turn on bases and headsets, keep headsets on, and verify connection to their respective bases before linking them through RJ45 1/2 (LAN). Then select Master/Remote Switch, one Master base and one Remote; from the Remote, Scan and select the Master by IP. The manual requires DHCP OFF before assigning those roles.

Record the previous network state and chosen diagram before changing it. Test speech and route after configuring the cascade. If Scan does not show the Master or the route still drops out, keep versions, connections, and results for support; repeating pairings without that information makes changes harder to compare.

A switch changes the scope of Hollyland’s setup instructions

The official V2.0.7.12 note dated 20/12/2024 allows a general network switch with up to two hubs per system but warns that seamless roaming is lost and base-change time increases. This does not ensure that a director’s instruction arrives complete while moving between rooms.

The IP roaming FAQ states that it does not work through a switch or fiber equipment, without specifying firmware. The documents do not express the same scope. For V2.0.7.12, we retain the note’s condition; for another version or a fiber path, Hollyland still needs to confirm the exact combination’s behavior.

The current firmware portal, consulted on 11/10/2026, also offers V2.0.7.24, dated 18/08/2026, and states C1 Air compatibility. We do not present it as a fix for switch-based roaming: that page does not confirm this point. Published versions do not identify the firmware on your units either.

Request the diagram and compatibility from the provider before testing. Measure any silence when changing base, with one person speaking and another replying. If a camera cue must arrive during that segment, agree with the director on how to handle it while the dropout is resolved. Do not update during the event; Hollyland asks users to avoid that time for firmware work.

STRIDE: count connections where the team gathers

The STRIDE manual, Technical specifications → Wireless limits each antenna to five simultaneous clients. The product page confirms this figure. A system with several antennas also needs review of how many people share each location.

The official Wireless Guidance, Green-GO DECT Access Points guide lists up to one hundred beltpacks and 250 antennas for STRIDE. This is the platform’s published scope; each antenna remains limited to five connections and RF availability must be checked in each zone.

As a preliminary calculation, six simultaneous users exceed one STRIDE’s five connections. Two antennas add up to ten aggregate connections; this does not prove both cover that location or that a free connection is available when walking there. Mark where production gathers and repeat the test with that occupancy.

Count stations passing through the zone too. A camera operator arriving at the stage while the team waits for a cue adds demand at that moment. Record the greatest expected overlap as well as the total requested beltpack count.

In Control, Wireless → Home, observe antenna occupancy and PTP status, plus beltpack battery and RF. Record those details as each operator joins. If several antennas are present but users concentrate near one, total pool capacity does not describe what happens there.

STRIDE: check network and pool before the walk test

The STRIDE guide, Preparations requires Green-GO Control, STRIDE antennas, and WBPX/WBPXSP beltpacks from 5.1.0, plus properly configured switches between antennas supporting PTPv2 (IEEE 1588-2008). These are minimum requirements, not an instruction to install that version.

The manual, Setup a Stride wireless system specifies the same system configuration and a network connection between antennas for Join Pool. Antennas do not join the pool over radio. Review those details before creating another pool. Create Pool replaces DECT configuration and closes connections; Clear also interrupts them.

Record model, firmware, ports, and configuration of the switch linking antennas. Supplying PoE and showing a link do not verify the required synchronization. If that segment cannot be identified, leave it pending before promising continuity between rooms.

Slow reconnection needs evidence from the actual equipment

For STRIDE, Monitor Your System and Troubleshooting let you review PTP status and associate dropouts during antenna changes with poor synchronization or power loss. In Control, connection → PTP, save the graph and dropout time; the tab appears when a STRIDE is detected. Also compare power and cabling. This guide’s diagnosis is limited to STRIDE. Another kit requires its own identification and documentation.

During the proposed test, walk one route with continuous conversation and another with pauses to check that the station responds again. Record silence time, audible recovery, antenna, occupancy, and direction of travel. If restarting a unit, first record observations and then compare; do not treat the cause as resolved just because the link returned.

Leave a coverage worksheet for operation

Use the coverage and base-change worksheet. It is blank: results are entered by whoever performs the test. It includes units, versions, zones, simultaneous users, network, and conversations in both directions.

Keep untested segments and their reasons. If a zone still depends on support or an unconfirmed version, agree on the continuity plan with the director. Relate routes to the event cameras and venue-authorized access points.

To coordinate installation, send GLMedia that worksheet and plan. The production and technical coordination service helps prepare conversations and testing with the intended equipment. Availability and coverage remain to be checked for each event.

STRIDE: if several beltpacks drop, record PTP alongside the dropout

If several beltpacks lose audio at once, note which units stop receiving and whether wired stations keep talking. Simultaneous loss warrants reviewing shared elements. Preserve the state before restarting: a visible IP and powered antenna do not show what its clock was doing during silence.

To observe it, open Green-GO Control, connection view → PTP, after detecting a STRIDE. The guide, PTPv2 Connection Status displays the last 60 seconds and expresses offset in microseconds (μs). Record the graph when the dropout occurs, visible antennas, selected clock, and time; if you wait, that segment leaves the window.

Also check the logo above the screen: the STRIDE manual, The DECT status indicator distinguishes steady green (clock synchronized), flashing green (Discovery Mode), and steady red (PTPv2 No Sync). The lower LED indicates network and configuration, a separate check. The E-Ink screen may retain data while off; do not use it alone to confirm power.

As a test, compare speech with operators stationary and on the same out-and-back route. If silence coincides with synchronization loss, review the network path and preserve that coincidence for support. If PTP stays stable, continue with per-antenna occupancy, coverage, and each station’s status. None of these results was measured here.

Switch for STRIDE: verify model, system and ports

The STRIDE guide, Network Setup requires correctly configured PTPv2 on every switch between antennas. The following examples have model-specific documentation. The list covers manufacturer checks; the actual event topology still needs testing.

On SW6, the manual, Status LED → Port LEDs states that orange on a port in normal link view means 10/100 Mbps. STRIDE has a 10/100 EtherCON connection: that color may be expected. Do not confuse it with fault red. Also review the total PoE budget of 90 W on SW6 for all connected loads.

SW6 also has a PTPv1 (Dante) warning: it does not support that synchronization. If the switch will share an audio network, verify that design separately using the Dante clock guide. This STRIDE check does not validate the other equipment.

For CRS328-24P-4S+RM, record whether it started RouterOS or SwOS: the device manual, Configuration documents both systems. The cited STRIDE instructions apply to RouterOS. In the RouterOS PTP manual, Supported devices and Configure PTP, check port restrictions and profile interface assignments. An available SFP+ uplink does not make it a supported PTP port on this model.

Draw the complete path between antennas, including uplinks and venue switches. If VLANs or IGMP snooping are involved, ask the network lead to check PTP passage in that configuration too. Prepare changes outside operation, with backup and a way to restore the previous state; do not paste an example configuration onto the show switch.

STRIDE: preserve domain and clock before changing priorities

The Green-GO PTPv2 guide documents the AES67 profile and default values Domain 0 and Priority2 128. Antennas that must synchronize need the same domain. That profile is used for clocking; Green-GO clarifies that its audio does not use AES67. Do not interpret it as audio compatibility with another console.

Record domain, priorities, and each antenna’s selected clock before testing. If they differ, compare the intended design and saved configuration with the system lead. Changing numbers until green appears leaves the actual correction unexplained.

The same guide warns that connecting a higher-priority clock may interrupt DECT connections. Lowering Priority2 increases preference, but selection considers other clock attributes. Prepare any change with the equipment that will be present at the event, then compare synchronization and conversation.

The manufacturer includes Load Defaults in Troubleshooting. This operation overwrites custom PTP parameters. Before using it, save their values and check whether domains were intentionally separated; reserve the intervention for preparation, with the ability to restore them.

Use the STRIDE, PTP and switch worksheet to record states, dropouts, and one change at a time. It is blank. Attach it to the coverage plan so production and technical coordination can prepare the route and pending items with operations.

WBPX: check the reply as well as hearing the director

First test a conversation near the antenna with an identified wired station: the director speaks, the operator repeats the message, and the director confirms hearing the reply. Keep the group, TALK/MUTE, and units used. If it fails there, review roles and permission to speak (Spanish) before attributing it to the route.

The RF guide, Interference Challenges in High-RF Environments describes a WBPX continuing to receive while the antenna loses its return signal. This is a documented possibility; hearing clearly does not confirm two-way communication or identify an interference source.

On the proposed route, repeat the same conversation at entrances, stage, and adjoining rooms. Record received speech and the reply heard in control separately, together with antenna, RF, occupancy, and time. If PTP stays stable and only one direction fails, keep that evidence and compare locations; if it returns closer to the antenna, record the recovery point too. This test was not performed here.

Antenna placement: distinguish WAA from STRIDE

The WAA Antenna X manual distinguishes OTA, without roaming, from X-Pool for up to seven antennas. Do not carry a test with that equipment over to STRIDE. The RF guide, Roaming describes a disconnection and reconnection of about 5–10 seconds for WAA in X-Pool; for STRIDE it requires some zone overlap and PTPv2 synchronization.

The same guide, Antenna placement and RF Blockers, recommends line of sight where possible and at least two meters between antennas. Walls, metal, and people may affect signal. Use those guidelines as a starting point; they do not provide a guaranteed venue coverage distance.

Mark the transition between bases and antenna location on the plan, with doors, structures, and expected occupancy. Compare speech both ways in the transition zone. For STRIDE, record which antenna serves the beltpack before and after, together with PTP and occupied connections.

If proposing an antenna move, do it during preparation and repeat the failed segment without also changing group or user count. Keep the previous result too. A walk test in an empty room leaves testing under event-like conditions pending.

STRIDE Monitor: prepare the RF environment scan

In Control, Wireless → Access points → Access point settings, select the STRIDE and open EDIT, or double-click. Operational mode distinguishes Normal from Monitor. The manufacturer warns that switching to Monitor stops normal operation, disconnects current devices, and removes the antenna from the pool. Do not use it on an antenna serving stations during the show.

Prepare the scan outside operation or with a dedicated STRIDE. Record which antennas keep serving users and what coverage/capacity remains available. At the end, check mode, pool membership, and conversations before returning the system to operation; closing the window alone does not restore service.

In Wireless → Monitor, choose the antenna configured to scan in the dropdown. With none selected, the view only shows devices connected to STRIDE; this is not an environment scan. The reading corresponds to the selected antenna’s physical location.

Save screenshot, location, time, and equipment powered on at the venue. History averages between 10 and 120 seconds; note the interval used to compare screenshots. Relate the grid to the recorded silence and conversation; a red slot indicates Control’s interpreted state, not the identity of the interfering device.

Complete the STRIDE coverage, occupancy and scanning worksheet. It is blank and retains untested zones. Give it with the plan to production and technical coordination to prepare the test and continuity plan.