Instead of the ultrasonic token having the proximity app use htttps could we have it use Bluetooth? That way users that are non-employees (can not get on the network) that are part of the meeting can connect the app to the TP endpoint?
Bluethooth is unfortunately not an option and will raise simplicity issues that we are initially trying to avoid using ultrasound. Pairing makes the user have to turn on bluethooth, locate, connect, authenticate and eventually no one is going to use it because it is too cumbersome. It also raises other concerns in terms of security. We want the app to be simple, you walk into the room and open the app and you are connected. If a company want to have the non-employees paired with the system then they should be allowed to connect to the corporate network. Some might find a solution to this if needed. Unfortunately, companies not allowing their employees handheld devices on the corporate network simply cannot use the app. There might be improvements on this in a later release so that it is not restircted to the network. Stay tuned.
Please let me know if you have further questions or suggestions :)
sound is only used to prove proximity in our solution. All other communication to & from the endpoint is done over the local network (wifi on iPad to network port on endpoint). We continue to listen for sound to prove you're still in the room (and disconnect you if you leave), but we cannot transfer presentation data or other data in the one-directional audio stream (very low bw).
We investigated Bluetooth in the early days of this project.
BT travels way further than ultrasound (which is limited by the walls of the room). This means it does not give a good poitner about real proximity. In early testing with bluetooth (before we got the ultrasound to a working solution), I could pair with meeting rooms on other floors (over/under the room I was in), or even offices far away. It all depends on how the BT signal travels.
Since BT travels far, it won't give you good enough ensurance of being in the same room. That would require us to implement something on the endpoint menu ("allow ... to connect to the system"), and we lose the "instant" feeling and simplicity of the solution.
To your PS: Sharing has been considered and we are discussing possibilities of doing this. Not committed yet, though.
The current version of Cisco Proximity requires a direct network connection between mobile device and endpoint.
We realize not not all deployments will accept this, and are discussing other solutions. We have plans to deliver proximity functionality also in other parts of the collaboration portfolio from Cisco, taking the network topology limitations of the current solution into consideration. (Future solution could for example leverage a Cisco cloud to route media from your device on 4G to the endpoint on corp network).
Cisco Proximity Troubleshooting GuideIntroduction Supported endpoints
and softwareSupport and other resourcesNetwork requirements The Cisco
Proximity Services Additional configurations Maximum simultaneous
connections Cisco Proximity for MobileVideo Syste...
Cisco Support Community was developed to allow Cisco customers and IT
professionals to collaborate and find solutions to their technical
needs. Over the years the community continues to flourish and is
strengthened with contributions from our users. Withi...
Engage, collaborate and co-create using your iPadiPad users - you asked,
and we listened! We are very excited to announce the RELEASE of an iPad
application designed to enable you to connect and interact with Cisco
Support Community, your one-stop technic...