In my experience, I find the largest resistance to video from the customer's perspective is that it is still a "board room" or "conference room" feature. I think the industry is still a while off from video being adopted at the desk, or rather being used frequently at the desk. I have had engagements where it was heavily adopted, but more often am asked to disable it on the endpoints.
To the point of your thoughts; with Telepresence endpoints now being in the fold and the new changes to the Expressway series licensing it seems logical to me that Video is and will continue to be an increasingly present member of the UC family. To that end, I think it should be part of this list. This list has a serious wealth of talent, more than I know is advertised. It has and continues to help me significantly. As Cisco video deployments become more standard, I think there will be a big need for the sort of ad-hoc support this list can offer for UC Video. As with Cisco voice, I think one of the many key contributors to widespread adoption is having forums like this, that are full of people who love what they do and like helping people. I say bring on the Video! Sent from my iPad > On Oct 17, 2015, at 10:26 AM, Anthony Holloway > <avholloway+cisco-v...@gmail.com> wrote: > > Does this list, being labeled "VoIP" and not "Voice", include Video in the > "V", or is the "V" for Voice only? A bit of tongue-in-cheek there, but I > think you know what I mean. > > With every day that passes, I feel like, as a Voice Engineer, I am being > asked to know and implement Video more and more. > > From CUCM taking on more of the video call control (just about 100% now, > no?), to video being a part of the CCIE Collab (to some degree, don't flame > me for mentioning it), the line between voice and video engineering roles is > blurring. > > I know there has been quite a bit of Expressway talk on here this year, but I > don't think I've explicitly read a thread which was 100% focused on video > technology. What's the direction you see these two technologies heading, and > should/could this list serve as both a Voice and Video discussion group? > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
