Miracast - special hints |
Version V1.62 |
Depending on the setup and your third-party devices used, your Android or Windows devices may not support Miracast MS-MICE.
Miracast MS-MICE is supported with Windows 10 (built 1703 and later).
Even when MS-MICE is enabled, Miracast P2P mode will be used to support Android and older Windows 8 or 10 systems.
All: mDNS (DNS) will be used for the information in the beacon
LAN: only the IP address of the LAN interface will be used for the information in the beacon
WLAN: only the IP address of the WLAN interface will be used for the information in the beacon
If MS-MICE "ALL" mode is enabled, multicast DNS (mDNS) uses the UDP port 5353 for Miracast connection over an existing network.
mDNS is broadcast to the local subnet of each network interface the Cynap Core PRO is connected to. If mDNS is blocked in the network, the Miracast connection fails. In this case it is necessary to create a DNS entry at the existing DNS server to the Cynap Core hostname. Cynap Core PRO sends a beacon via the integrated Miracast module with information about which Miracast settings have been made, to initiate a session.
UDP ports 67, 68: DHCP communication between device and receiver
UDP ports 137, 138: used for NetBIOS to allow Miracast MS-MICE.
TCP port 7236: MS-MICE RTSP control port is used to establish and manage the session
TCP port 7250: MS-MICE control port on which Cynap systems listen for Miracast packets when over existing network mode is enabled.
UDP Port 5353: mDNS (Multicast DNS) - If mDNS is blocked, DNS entry at the existing DNS server necessary as workaround.
UDP port 19000 ~ 19007 and 19010 ~ 19017: RTP media traffic port for delivering audio and video.
UDP port 19020 ~ 19027 / 19030 ~ 19037: Hardware cursor to reduce latency when using touchback
TCP port 50000: Touch back (User Input Back Channel)
Ensure Miracast is not blocked by any security application, e.g. Endpoint Security Software and virus scanners.