Ideal Remote Endpoint Dashboard/Support Interface

I'd like to solicit some feedback primarily from the individuals who support Lifesize Endpoints in the field on what the ideal administration/support dashboard would look like on an endpoint. What are the things you need to quickly see, test, and do in the field to keep your endpoints running and connected, and your users happy?

As an example I've seen more than a few posts about how useful it was with the 220s interface to be able to see snapshots of the camera and presentation inputs remotely and manipulate these from a remote location. So clearly, being able to see what the system is receiving and manipulate those inputs is important.

What other things would be helpful? What are the high level issues you run into most commonly that an endpoint dashboard could help with?

-recording from the web interface without having to be in a call that is a big one for people who record/stream locally in a room outside of a call. I would love to be able to start a recording from my desk instead of having to run across campus to help someone that doesn't know how to restart a recording. I have also heard feedback from other about wanting to change camera inputs remotely from an icon 800 or at least being able to distinguish between which input is which on an icon. I will keep adding to this as I remember stuff that I have mentioned in the past.

Thanks Jon for commenting. Just created the discussion yesterday so you are early to the party!

I could see how ideally you would like to have a virtual version of the user interface as part of the endpoint dashboard that would allow you to manipulate the system as if you were in the room. This would cover your remote recording enable and camera input changes needs.

Regarding input sources I would also expect that hot-plug detect and valid video signal status for each input would be useful status on the dashboard as well.

To be honest, I didn't know that recording outside of a call wasn't available in the UI until someone called me one day from across campus that was live streaming something and experienced a power surge that caused the endpoint to reboot. I was so accustomed to how the 220's functioned that I just figured this option was there. I looked a little silly and out of breath after running over to the room to restart the stream when I said I would do it remotely. It's just something that has to be there when you have 30+ endpoints all over campus and most of them are operated by faculty who really just call me for every little issue

Being able to run the initial configuration on an icon system would be great as well. Often times our contractor will install icon systems and leave it on its initial configuration menu which if left there for long a period of time seems to lock up a system forcing us to factory reset this system. I would like to be able to go through the initial config remotely to set the system up.

Initial config is tricky primarily because of security concerns or the fact that out of box the system may not even be able to get on the network at all. That may better be part of a higher level support function at the account level rather than the endpoint dashboard.