Cisco Room Bar Wireless

[WarrenMaistry2067]

Hi All

I trust you are well

I need some help setting a Cisco Room Bar device on our internal network 

.We connect the device via the LAN port and try connecting the end point to our laptop /mobile device, its connects for a few seconds the disconnects via Wi-Fi direct 

We thought it could be due to WIPS enabled on our WLAN but we have isolated that and still the issue persists.

Tested the Room Bar from our home network and works fine so this make me think we have some kind of FW rules possibly dropping the connection.

Is there a configuration needed on the switch or switchport perhaps?

IOS is up to date 

Is there someone who could help advice on any common causes ?

Thanks

[Nithin Eluvathingal]

Miracast and Airplay need ports to be opened.

For Airplay

ort	TCP or UDP	Service or protocol name	Service name	Used by
80	TCP	Hypertext Transfer Protocol (HTTP)	http	AirPlay
443	TCP	Secure Sockets Layer (SSL or HTTPS)	https	AirPlay
319, 320	UDP	Precision Time Protocol (PTP)	ptp	AirPlay
554	TCP/UDP	Real Time Streaming Protocol (RTSP)	rtsp	AirPlay
3689	TCP	Digital Audio Access Protocol (DAAP)	daap	AirPlay
5353	UDP	Multicast DNS (MDNS)	mdns	AirPlay
7000	TCP	AirPlay HTTP server	http	AirPlay
32768-60999	TCP/UDP	Ephemeral port range required between subnets for share	http	AirPlay

For Miracast, you should check firewall settings and verify that TCP port 7236 is open on Windows devices in your organization.

[WarrenMaistry2067]

Hi Nithin

Thank you for your response back, can it not be a wireless protocol?

We have tested from a open laptop and no FW rules in place and we see the same error.

Like it connects then drops after a few seconds

[Nithin Eluvathingal]

Which feature are you using Mira cast or Intelligent proximity  ?

[WarrenMaistry2067]

Mira Cast 

[WarrenMaistry2067]

Hi @Nithin Eluvathingal 

Trust you are well

We managed to figure out the problem which is relating to our WIPS setup on our WLAN.
We have Rogues rules applied from our WLC which is blocking the wireless beacons from the Miracast signal so when disabled the rule 03, we connect instantly , we are also whitelisted the MIraCast SSID on our Rogue rules but once we re-enable the rule below (attached) we face the same issue all over again but i'm thinking since both these hardware are cisco surely there must be a solution to get this working without impacting security ? any advice on this perhaps