
“Let’s turn off screen casting for now until a solution is available.”
This is the first response many hotels adopt after experiencing screen-casting incidents. Shutting it down is the easiest way out — no more cross-room casting, no complaints, no compliance risks. But what happens after the feature is disabled? Guests turn on the TV only to find screen casting unavailable, leaving negative OTA reviews calling the TV “a useless decoration” and gradually driving down repeat booking rates.
Screen casting is no longer a value-added service. Business travelers want to resume their favorite shows on the big screen; meeting attendees need to present documents; parents wish to play cartoons for their kids. Casting content onto the in-room TV delivers a straightforward, low-cost guest experience upgrade.
Disabling screen casting means removing a service guests take for granted.
Is there a solution that keeps screen casting active while balancing user experience and privacy?
Many hotels implement well-designed networks. For security purposes, the guest WiFi network and the IoT network for TVs and large displays are separated into different VLANs and subnets with strict isolation. This is correct and forms the baseline for security compliance.
The conflict arises during the device discovery phase of screen casting.
Before casting, mobile phones send multicast packets such as mDNS or SSDP to broadcast queries across the local network to locate available devices. Multicast traffic only works within the same broadcast domain. Once network segments are isolated, these discovery packets cannot reach the TV. The phone cannot “see” the TV, and screen casting cannot start.
The industry mainly relies on three workarounds:
Most hotels are forced to pick one from the three options, trapped between security and user experience.
AINOPOL’s solution is the Screen Casting Reflector, a built-in software add-on module for Dream Gateway, not standalone hardware.
This solution breaks the forced trade-off: it does not interconnect network segments or permit multicast forwarding. Instead, it performs application-layer proxy inside the gateway.
Analogy: There is a soundproof wall between two rooms; voices cannot pass through normally. Rather than demolishing the wall or drilling holes in it, the Screen Casting Reflector installs an audio transmission system inside the wall. Signals can be relayed from one side to the other, but the two sides remain isolated and inaccessible to each other.
It is implemented via six core design features:
Lightweight deployment: Bundled with Dream Gateway with no extra hardware or license required. Enable it with one click on the gateway web portal; simply assign ports or VLANs for each network domain to go live. No changes to existing VLANs, no global multicast activation, and no client installation required on every TV.
Keeping screen casting available must not come at the cost of guest privacy. The Screen Casting Reflector protects guest privacy through four layers of controls.
Layer 1: Room-level isolation, preventing casting to other rooms
Mobile phones only discover and cast to approved TVs within the same room. Guests scan the QR code on their own in-room TV and bind to the local device. TVs in neighboring rooms never appear in the casting list.
Layer 2: Preemptive real-name authentication with traceable casting activities
After connecting to guest-room WiFi and completing Portal real-name authentication, the system automatically binds the authenticated identity to the TV casting permissions for that room. Full records of the caster’s real-name information, room number and casting timestamp are retained. In case of disputes, hotels can quickly export complete casting logs.
Layer 3: Three-state device review to block unauthorized devices
TV devices are categorized into three statuses: Approved / Pending Review / Blacklisted. Only approved legitimate devices are eligible for screen casting; unreviewed devices will not show up in the casting list.
Layer 4: Automatic unbinding upon check-out, permissions revoked after departure
Bindings expire automatically after 24 hours by default and become invalid once guests check out, eliminating manual front-desk operations. Integration with the PMS system enables automatic unbinding on check-out and credential reset for new check-ins.
Five protocols are currently supported: mDNS, SSDP, DLNA, Lebo (Lelink) and AirPlay. They cover mainstream ecosystems including Apple, Android, domestic smart TVs and third-party screen casting applications.
These five protocols fall into two layers: mDNS and SSDP belong to the discovery layer, which determines whether devices can be detected by mobile phones. DLNA, Lebo and AirPlay belong to the casting layer, responsible for signal control and media transmission. The reflector captures, rewrites and proxies traffic across both layers uniformly.
Note: Huawei Cast+ is not supported at present. Huawei/Honor users are recommended to use the Lebo Screen Casting App or DLNA-compatible clients.
Network isolation ensures security, while screen casting enhances guest experience. For a long time, hotels had to choose one over the other.
The Screen Casting Reflector delivers smooth casting with full traceability for every session. No need to disable screen casting, no compromise on privacy — experience and privacy can both be achieved.
Starting now, purchase the M1 Dream Gateway and receive the Screen Casting Reflector for free. The gateway handles network entry compliance, while the reflector manages screen casting experience. Hotels avoid separate procurement and maintenance of two systems.
Q: What is the Screen Casting Reflector? Is it hardware?
The Screen Casting Reflector is a built-in software add-on module for AINOPOL Dream Gateway, not standalone hardware. It comes bundled with the gateway at no extra cost.
Q: Can content be cast to another guest’s room?
No. Mobile phones can only discover and cast to approved TVs in the same room. Dual filtering with binding association and VLAN validation ensures TVs from adjacent rooms will not appear in the casting list.
Q: What happens to screen casting permissions after guests check out?
Bindings expire automatically in 24 hours by default and are revoked once guests check out, requiring no manual front-desk unbinding. Integration with PMS supports automatic unbinding upon check-out and credential reset upon new check-in.