Enable Sharing with Miracast
Screen mirroring for Windows devices is available through Solstice's support for Miracast streaming. This allows users to wirelessly mirror or extend their screen to the Solstice display in real-time without having to install an app.
Solstice's support for Miracast works in two stages. In the discovery stage, a Miracast-enabled device searches for active Miracast receivers nearby for the user to connect and stream to. This requires the Solstice Pod’s wireless network interface card to be enabled and not acting as a wireless access point. In the second stage, the device streams content to the Miracast receiver using either an existing network (Miracast over Existing Network) or a peer-to-peer wireless connection (WiFi Direct).
Solstice's Miracast support has three modes:
- Over Existing Network and WiFi Direct (recommended). Allows Pods to dynamically select best video streaming mode. Most robust device connection and setup configuration. Supported devices: Win8, Win10, Android
- Over Existing Network. Leverages existing network to support larger number of simultaneous Miracast users. All Miracast traffic is subjected to network security and monitoring. Supported devices: Windows 10 only
- WiFi Direct. Good for use cases where one Miracast device will be used at a time. Supported devices: Win8, Win10, Android
Network Routing Requirements
The following network ports/routes are required to support Miracast streaming to Solstice Pods.
- TCP port 7236: WiFi Direct control port used to establish and manage sessions between the source device and the Pod.
- TCP port 7250: Port on which the Pod listens for Miracast packets when Over Existing Network mode is enabled.
- UDP port 5353: If Miracast Over Existing Network mode is enabled, this port is used for multicast DNS (mDNS). mDNS is broadcasted to the local subnet of each network interface the Pod is connected to. If the computer that is attempting to make an infrastructure connection is on a different subnet, this broadcast will fail. If this happens, a workaround is to create a DNS entry to the Pod’s hostname.
- Confirm that port 32768:60999 (for Gen2i Pods) is also open.
Miracast may utilize any non-privileged UDP port from 1024 to 65536 for video streaming.
- Miracast requires that the Pod be located in close proximity to the display. Miracast discovery operates over a range of approximately 150-200 feet. Only Pods within this range will be displayed in the Miracast source list on the client device.
- There are many factors that can affect the performance of Miracast streaming. For more information on Miracast performance by configuration and use case, view the Miracast Performance Tech Note.
Find the Pod's network configuration in the table below and apply the corresponding configuration in the Solstice Dashboard.
|Pod's Network Configuration||Pod Configuration for Miracast via Solstice Dashboard|
|Ethernet Only (recommended)||
Wireless attached to existing network only
|Ethernet + Wirelessly Attached to Existing Network||
|Ethernet + Wireless Access Point||Miracast Not Supported. When the Pod is acting as an access point, Miracast discovery cannot operate. Contact Mersive to discuss other options like attaching your Pod to an existing network.|
|Wireless Access Point Only|