[cisco-voip] anonymous proximity issues?

[Ryan Ratliff (rratliff)]

Being EDU I foresee an engineering student’s senior project to create a device to wash out the 20-22kHz ultrasound, making an invisible fence for proximity's ultrasound when used in open spaces.

Also, for all of your Proximity questions:
https://community.cisco.com/t5/mobile-applications-documents/troubleshooting-guide-cisco-proximity/ta-p/3148841#toc-hId--2135534734


-Ryan

On Oct 11, 2018, at 10:32 PM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:


Hmmmm, I don’t remember seeing anything on the screen when I connected via proximity. Will have to check again. My head was likely looking down at my device.

The idea of macros is nice, but not sure it really helps secure the system while they actually want to use it.

It’s not ideal, but in EDUs, there’s very little segmentation when it comes to a student logging into wireless vs staff/faculty. Not to say all students are looking to cause trouble, but, well, you know.

And in today’s cubicle environment, those frequencies are reaching far outside the glass walls. But I’ll need to do more testing once the device is in place. Even a quick site survey might appease our concerns.

-sent from mobile device-

Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1<x-apple-data-detectors://1/0>
519-824-4120 Ext. 56354<tel:519-824-4120;56354> | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 11, 2018, at 9:50 PM, Ryan Ratliff (rratliff) <rratliff at cisco.com<mailto:rratliff at cisco.com>> wrote:

It’s not PIN controlled, the idea is that if the device is in range of the ultrasound and on a network that has https connectivity to the codec then it can connect.

Users in the room also see a notification on the screen when a proximity client connects, so it’s not hidden.

If you want your users to have control over toggling the feature take an example from https://github.com/CiscoDevNet/roomdevices-macros-samples and create a macro that works with in-room-controls to give your users a button to flip the config on/off.

-Ryan

On Oct 10, 2018, at 5:04 PM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:


Unless I am completely mistaken, it seems that proximity participation in a t/p session enabled for proximity is completely anonymous without acknowledgement from the t/p operator side of things. At least one document says that if you are afraid of people outside your office participating, you should disable proximity on your device. Wait, what?

I read somewhere where you can lower the proximity HF volume(?), but that’s like lowering the wifi antenna power to restrict wifi access.

I’m thinking of enabling only proximity itself and not sharing, so at least webex users can select the endpoint. I mean, they may call a user’s endpoint, but in the end, they have to accept the call. No biggie there.

But it really is a shame that there was no acknowledgement or PIN displayed, like on an Apple TV when you want to join the session.

Does anyone know if proximity will be PIN controlled (or anything like this) any time soon?

Lelio


---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

<image001.png>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20181012/fe76b853/attachment.html>