This article applies to the following ScreenBeam products:
When configuring Miracast over Infrastructure for Windows 10, native screen mirroring for Apple devices, and Google Cast with the ScreenBeam it may be necessary to add the Service IDs used by ScreenBeam into the wireless controller. Exactly where the Service IDs need to be added varies by vendor, for Aruba the Service IDs need to be added in AirGroup.
The Service IDs used for the ScreenBeam are shown in the table below.
| Wireless Display Protocol | Service IDs Required |
| Miracast over Infrastructure (Windows) |
_display._tcp.local |
| AirPlay (macOS, iOS) |
_airplay._tcp.local _raop._tcp.local |
| Google Cast (Android, ChromeOS) |
_googlecast._tcp.local |
Comments
0 comments
Please sign in to leave a comment.