Miracast / Miracast over Infrastructure
Miracast provides wireless display sessions. Classic Wi-Fi Direct and Microsoft infrastructure extension use different discovery/setup paths; transport and security depend on both source and sink.
Scope: Miracast / Miracast over Infrastructure — requirements depend on the selected profile.
protocol · Catalog reviewed 2026-09-27
Infrastructure Requirements
- Compatible wireless-display source and sink
- Wi-Fi P2P discovery
- for infrastructure mode, reachable sink setup and source RTSP listeners plus negotiated media paths.
Network & Physical Requirements
| Port / allocation | Transport | Connection / signal flow | Feature and requirement | Evidence |
|---|---|---|---|---|
| 7250 | TCP | Projection source → Projection sink | Profile requirement · Core Infrastructure projection setup Microsoft MS-MICE infrastructure extension | Source checked 2026-09-27 Projection: source connection to sink on TCP 7250; Source Ready exchange |
| 7236 (default) | TCP | Miracast display sink → Miracast display source | Profile requirement · Core Infrastructure projection RTSP control MS-MICE source RTSP listener The source announces its RTSP port in Source Ready; use the announced value. This reverse connection is separate from source-to-sink TCP 7250. | Source checked 2026-09-27 Projection: Begin Session2024-04-23 |
Physical, link and configuration requirements
configuration · Profile requirement · Core
Establish the RTSP session, then provision its negotiated media and optional input-backchannel paths.
Microsoft MS-MICE infrastructure projection
TCP 7250 handles infrastructure setup. The sink then connects to the source RTSP port; RTP and optional UIBC are separate session traffic.
link-layer · Optional · Wi-Fi Direct
Wireless P2P discovery uses beacon and probe management frames.
Classic Miracast Wi-Fi Direct
Infrastructure capability is advertised during discovery. Unsupported infrastructure projection falls back to standard Miracast.
Gotchas & IT Notes
- ⚠MS-MICE setup on TCP 7250 does not carry the complete session. The sink also connects back to the source RTSP listener.
- ⚠Check the announced RTSP port and negotiated media/input channels; do not apply a universal UDP range.