This guide will show you how to troubleshoot Air Sharing issue with your Room Video Conferencing System (RVC).
To get started,
Click Apps >> Air Sharing - before scanning for the available connections with your device.
Click Apps >> Air Sharing - before scanning for the available connections with your device.
For IOS devices (Multicast Technology)
1. First, make sure that your iOS device & RVC System are on the same network.
2. Some AP "Access Points" have a special security setting called network isolation or wireless isolation which prevents wireless clients from communicating with each other. If such a setting is enabled in your router, turn it off.
3. Check that Multicasting is enabled on the network (Access Point), as it is needed for discovery. If multicasting is disabled, enable it.
4. If you are unable to connect Try turning off the Wi-Fi on your iOS device for 5 seconds and then turn it back on.
5. If this does not fix the issue try powering off your iOS device, wait for 5 seconds and then turn it back on.
Note: This is a common iOS issue and it is always good to restart your iOS device every couple of months.
6. If restarting the device does not fix the issue, try restarting the Access Point as well.
7. Make sure that your AP "Access point" is running the latest firmware which can usually be downloaded from the manufacturers website.
8. Make sure that ports used by AirServer are opened through firewall:
• AirPlay - TCP 7000
• AirPlay Mirroring - TCP 7100
• AirPlay Audio - TCP 5000
• AirPlay Audio - UDP 6010-6012
Note: Older IOS devices with single core processor, such as iPad 1, iPhone 4, iPhone 3GS or iPod Touch, do not support AirPlay mirroring.
1. First, make sure that your iOS device & RVC System are on the same network.
2. Some AP "Access Points" have a special security setting called network isolation or wireless isolation which prevents wireless clients from communicating with each other. If such a setting is enabled in your router, turn it off.
3. Check that Multicasting is enabled on the network (Access Point), as it is needed for discovery. If multicasting is disabled, enable it.
4. If you are unable to connect Try turning off the Wi-Fi on your iOS device for 5 seconds and then turn it back on.
5. If this does not fix the issue try powering off your iOS device, wait for 5 seconds and then turn it back on.
Note: This is a common iOS issue and it is always good to restart your iOS device every couple of months.
6. If restarting the device does not fix the issue, try restarting the Access Point as well.
7. Make sure that your AP "Access point" is running the latest firmware which can usually be downloaded from the manufacturers website.
8. Make sure that ports used by AirServer are opened through firewall:
• AirPlay - TCP 7000
• AirPlay Mirroring - TCP 7100
• AirPlay Audio - TCP 5000
• AirPlay Audio - UDP 6010-6012
Note: Older IOS devices with single core processor, such as iPad 1, iPhone 4, iPhone 3GS or iPod Touch, do not support AirPlay mirroring.
For Android devices & Windows 8.1 devices (Miracast Technology)
Here are a few steps you can try if your Miracast device is unable to connect to RVC System:
1. Check if another Miracast device is connected. If so, disconnect it and then try again.
2. Wait 2 minutes between retries - this delay is due to the WiFi Direct design.
3. If AirServer is only showing a black screen, you may need to restart your sending device and try again.
Note: Clients can take up to 20 seconds to connect.
4. Please make sure that your windows 8.1 has August 2014 Update (KB2975719) is installed. It is available via Windows Updates, and also make sure that WiFi adapter running Windows 8.1 specific driver (NDIS 6.4).
5. To find out if the WiFi adapter is running Windows 8.1 (NDIS 6.4) driver, open PowerShell and run the below command:
Get-NetAdapter | Select Name, NdisVersion
Here are a few steps you can try if your Miracast device is unable to connect to RVC System:
1. Check if another Miracast device is connected. If so, disconnect it and then try again.
2. Wait 2 minutes between retries - this delay is due to the WiFi Direct design.
3. If AirServer is only showing a black screen, you may need to restart your sending device and try again.
Note: Clients can take up to 20 seconds to connect.
4. Please make sure that your windows 8.1 has August 2014 Update (KB2975719) is installed. It is available via Windows Updates, and also make sure that WiFi adapter running Windows 8.1 specific driver (NDIS 6.4).
5. To find out if the WiFi adapter is running Windows 8.1 (NDIS 6.4) driver, open PowerShell and run the below command:
Get-NetAdapter | Select Name, NdisVersion