Miracast is a mirroring protocol and wireless technology used to project your screen to the AirMedia receiver without the need to install an AirMedia sender application on your computer. Miracast is supported on AirMedia Series 3 and AirMedia 2.0 (CCS‑UC‑1, CCS‑UC‑1‑X, AM‑200, and AM‑300) products.
Miracast on AirMedia 2.0 requires the addition of a Wi-Fi network USB Adapter (sold separately). There are two iterations of this adapter available:
Both versions of the adapter support 802.1A/B/G/N/AC wireless networking standards on both the 2.4 GHz and 5 GHz frequencies.
The difference between the US and International Model is the supported Wi-Fi channels.
2G Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
5G Channels: 36, 40, 44, 48, 149, 153, 157, 161, 165
2G Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
5G channels: 36, 40, 44, 48, 149, 153, 157, 161, 165
Users connect to a Miracast receiver using the Windows connect menu. The Windows connect menu can be accessed via the Windows notification center or using the shortcut (Windows) + K. On touch-capable Windows 10 devices, swipe in from the right edge of the screen.
Miracast connection has two phases: the discovery phase and the connection phase. The discovery phase uses Wi-Fi based discovery. For this reason, the AirMedia Wi-Fi USB adapter is required for Miracast functionality.
After the list of Miracast receivers is discovered, the user will select a device from the list. Windows 10 will first connect to the Miracast receiver via the existing infrastructure. This is done by resolving the host name through mDNS, then connecting to the receiver over the infrastructure. If the host name cannot be resolved or the connection over infrastructure fails, Windows 10 will establish the Miracast session using the standard Wi-Fi Direct® connection. Wi-Fi Direct is a peer-to-peer connection that establishes a private network between the user device and the receiver. The private peer-to-peer network coexists with the user’s other network connections. Once the network is established, Windows 10 will then establish connections over the peer-to-peer network. This two-fold connection mechanism is useful for guest users who may not be connected to the same network.
NOTE: When a Miracast session is connected via Wi‑Fi Direct, the connection may automatically terminate after a period of time (typically 60 minutes) due to restrictions placed on a Wi‑Fi Direct type connection.
Crestron supports using Miracast from Windows 10 (version 1809 or later) and Windows 11. Miracast from Android devices is supported as a preview feature. A Miracast connection over Wi‑Fi Direct may produce mixed results. Other limitations may exist.
- For optimal performance, the network switch that the AirMedia receiver connects to must have a sufficient buffer size (>2.5 Mb per AirMedia device attached to that switch). In most cases, switches and routers are configured for best-effort packet forwarding. This means that the router forwards all packets it receives to the best of its ability. Everything functions with best-effort forwarding until an interface is oversubscribed. Once an interface is oversubscribed, the router must queue packets to avoid dropping them. The amount of queuing available on an interface determines the amount of momentary oversubscription that the router can tolerate without dropping packets and causing performance degradation.
- Miracast Wi-Fi Direct requires a PIN code to be set. For this reason, AirMedia devices will not allow you to disable the login PIN code if Wi‑Fi Direct is enabled.
- When commissioning the device and configuring the login code mode, the device may not initially recognize a change. Within a few minutes, the change will be reflected.
- Crestron recommends that the host name of the device should be 22 characters or less to ensure proper discovery by a Windows device and to ensure readability on the front‑of‑room experience screen.
- (AirMedia 2.0 only) Crestron recommends connecting a USB extension cable to the Wi-Fi adapter (not supplied). Place the adapter in an optimal location to minimize interference from the connected device's chassis.
- (AirMedia 2.0 only) Ensure the Wi-Fi adapter is enabled on the client device and that the latest drivers are installed for that adapter.
- Ensure the network is not blocking any of the Miracast related ports (7236, 7250) listed in the Firewall Settings & Port Table.
- Ensure the network is not blocking the mDNS discovery port (5353) listed in the Firewall Settings & Port Table.
- Check for Miracast support on the client device:
Press (Windows) + R and type dxdiag.
Select Save All information….
Open the saved DxDiag.txt and find Miracast. It should say Available, with HDCP.
- Check the firewall on the client device.
Disable the firewall and test projection. If Miracast works with the firewall disabled, add an exception for
Allow In/Out connections for TCP and UDP, Ports: All.
- Check the group policy settings on the client device. On domain-joined devices, Group Policy can also block Miracast.
Press (Windows) + R and type rsop.msc to execute the Resultant Set of Policy snap-in. This will show the current policies applied to the computer.
Review Computer Configuration > Windows Settings > Security Settings > Wireless Network (IEEE 802.11) Policies.
Double-click the setting for wireless policies and a dialog box will appear.
Open the Network Permissions tab and select Allow everyone to create all user profiles.