[cisco-voip] Video Architecture

[Ed Leatherman]

To Anthony's original message - personally I find having video stuff pop up
on this list to be valuable, and doesn't seem out of place to me at all.
Although it's not widely adopted where I work, we have a few strategic uses
for it that are key. I feel like I need to keep at least support for some
basics fresh just for those strategic curveballs I get now and then. As we
roll out Jabber I think we'll see some uptick in usage for certain groups.

On Mon, Oct 19, 2015 at 9:45 AM, Rob Dawson <rdawson at force3.com> wrote:

> Personally, I am definitely seeing video as a component a lot more. In the
> last year I’ve had to implement a large VTC pilot with all the requisite
> infrastructure (TMS, Telepresence Server, Conductor, etc.), Collaboration
> Meeting rooms, etc. I view it all as just another part of convergence and
> an integral part of both “cisco-voip” and the Cisco Collaboration platform.
> As you said, the architecture is moving to 100% CUCM call control. We have
> gone from bespoke TDM solutions and working a punch down tool to needing to
> be network/systems/application/voice engineers. At the end of the day video
> is just another application on the network.
>
>
>
> For a lot of customers video is still just kind of a gimmick and it is not
> ubiquitous enough to drive adoption widely. I think that as those of us in
> pre-sales become better at tying the video use case to a holistic
> collaboration solution then adoption will ramp up and we will start to find
> some pull through for customers that are on the ledge.
>
>
>
> As for your follow-up question about resources, I think that the Cisco
> Preferred Architecture guides are pretty good. The latest one for video is
> here -
> http://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/midmarket/11x/video11x.pdf.
> Vidoe is also covered as a component of the mid-market and enterprise
> collaboration architectures too. You can find them, as well as the Cisco
> Validated Design docs here -
> http://www.cisco.com/c/en/us/solutions/enterprise/design-zone-collaboration/index.html
> .
>
>
>
> Rob
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net
> <cisco-voip-bounces at puck.nether.net>] *On Behalf Of *Anthony Holloway
> *Sent:* Saturday, October 17, 2015 10:26 AM
> *To:* Cisco VoIP Group
> *Subject:* [cisco-voip] Video Architecture
>
>
>
> 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 at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>


-- 
Ed Leatherman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151019/cafd17bf/attachment.html>