Fill out a support request and we’ll ensure that a member of the technical team contacts you today.
Also, here is some useful information that may assist you;
BONJOUR/MULTICAST separate subnet/VLAN issues.
ActivConnect supports two main ways of allowing your devices to “discover” the ActivConnect Airplay Receiver.
The first is Bonjour which is multicast protocol that broadcasts it’s name and IP address over a network. However if the sending device and the ActivConnect are on separate subnets or VLAN’s then this auto discovery does not work. This is unconnected from the ability of ActivConnect to operate on two entirely different networks as it makes no difference if Bonjour is not not supported on your network.
Even if Bonjour is supported then the auto discovery process could take a long time if you have many ActivConnect receivers on the same broadcasting network(s)
With the ActivCast senders which are available for Windows, Android and iOs you can connect the sending device to the target ActivConnect by identifying the ActivConnect unit directly via a QR code or a connection ID. Using direct identification the device and the computer do not have to be on the same subnet as long as they are ROUTABLE.
We currently support this functionality only in-LAN (when the Sender and the Receiver are routable) – this way the session traffic does not have to be relayed, and we get the highest performance connection between the two endpoints.
However the ActivConnect and the sending device need to be able to reach a Promethean cloud server which does the following.
1. The meeting starts.
ActivConnect contacts a server through a secure SSL connection and tells the server it’s IP address on the network(s) it is on. Additionally it also tells the server what it is called. For example : meeting room 2
The server only uses this information to create a unique connection ID number and passes this back to the ActivConnect so it can display.
NOTE: WE DO NOT DO ANYTHING ELSE WITH THIS DATA AND THE RECORD IS REMOVED ONCE THE MEETING HAS ENDED.
Now a user brings up the app on their device and enters the connection code displayed on the ActivConnect screen.
The app then contacts the cloud service and passes this ID to that service. The service looks up this ID and passes back the IP address and name of the device associated with it.
Then it connects.
NOTE: This connection ID does not supplement/remove the pin security code requirement. It is only used to perform the discovery.
If using a cloud server is a concern or not possible to reach which might be the issue in your environment then we do have the capability to relay the connections, and we’re sometimes asked for in-room solutions which don’t require an Internet connection, but using the cloud server provides the best usability. This work would have to be scoped as we would require further analysis of your use case.
PORTS / FIREWALLS
Additionally Airplay needs the following ports open which could be causing issues.
AirPlay. If you are under a restricted networking environment, please consult your networking department to have the below allowed/trusted for access.
For AirPlay* protocol:
* TCP 6000-7000, 7100, 47000, 47010
* UDP 5353, 6000-7000, 7011
Make sure your Windows Firewall (or 3rd party firewall) is allowing the sending and receiveing application to access the network, either by:
a. Allow the sender applications to be trusted and applies to ‘Domain’, ‘Private’, and ‘Public’ profiles
b. Allow the following port ranges be allowed by the firewall:
i. TCP 6000-7000, 7100, 47000, 47010
ii. UDP 5353, 6000-7000, 7011