PDA

View Full Version : help a journalist: what should a newbie know?


estherschindler
05-17-2005, 12:49 PM
I'm working on an for Labrat Magazine (http://www.labratmagazine.com) about business videoconferencing, and in particular "How Video Rollout Impacts Back Office Operations" (that's my working title). I'm trying to make this a best-practices article: that is, what do you wish someone had told you, when you were new to the subject?

If you've done this, in your own company or for clients: what did you learn the hard way? What advice would you offer an IT department that's planning to start a video project? Where are the bodies buried, particularly in deployment and testing? War stories are particularly appreciated. (We all love to read them, don't we?)

Let me know if I can quote you in the article; the usual format is "Joe Jones, network admin at Foobar, Inc. in St. Louis." If you don't want to post the information publicly, or can't be quoted on the record, feel free to send me a private e-mail message at esther@bitranch.com.

I have to hand in the article by Monday, which means I need help ASAP. (I wasn't being lazy; I just got the assignment!)

Esther Schindler
senior contributing editor, Labrat Magazine

mazzarak
05-17-2005, 02:35 PM
well from where I sit, I see one question that needs to be asked -

"Why do you want Videoconferencing implemented in your company?"

For some its cost cutting, for others its reaching those remote places... you find that some companies haven't given this much thought.

One of the I.T. things I've seen, particularly when it comes to IP conferencing, is fighting for the network in the first place. People need to be educated that VC works far better if part of the network is "ring fenced" and only available for VC.

I expect there will be some choice stories on here soon - come on everyone, lets hear your stories...

Andy

estherschindler
05-17-2005, 03:37 PM
One of the I.T. things I've seen, particularly when it comes to IP conferencing, is fighting for the network in the first place. People need to be educated that VC works far better if part of the network is "ring fenced" and only available for VC.

Can you explain to me why?

(Also, how can I refer to you in the article?)
--Esther

tom9933
05-17-2005, 04:25 PM
Esther,
I would agree with Andy, asking what you expect a system to give you is always a great start. From my perspective I think one of the biggest issues is to get the network guys involved as early as possible. Also taking them out to lunch once in a while doesn’t hurt either :) Beyond that starting small and minimizing the number of vendors are other good things to think about.

estherschindler
05-17-2005, 06:55 PM
Esther,
I would agree with Andy, asking what you expect a system to give you is always a great start. From my perspective I think one of the biggest issues is to get the network guys involved as early as possible. Also taking them out to lunch once in a while doesn’t hurt either :) Beyond that starting small and minimizing the number of vendors are other good things to think about.

Lunch is good. Lunch is okay. In fact, a beer sounds pretty good by this point in the day, too.

Okay, let's assume that the users have answered that question, and they didn't have a stupid answer. And, for the sake of discussion, you've all determined that the best answer is some sort of room-based videoconferencing system. It's going to happen. Now what?

I'm writing this primarily from the viewpoint of deployment and testing. Who should be in charge of the project? What network questions need to be resolved -- and with what priority? Since videoconferencing *has* to get network priority (or everybody on the screen will look as though they're in a bad Japanese monster movie), how do you integrate the video with existing legacy infrastructure?

In other words, is it only the network guys for whom you have to buy lunch? And can I come along?

mazzarak
05-18-2005, 02:05 AM
Can you explain to me why?

(Also, how can I refer to you in the article?)
--Esther

Hi Esther

the way I experience it is as follows. If you are using an IP VPN network, its often the case that you use the same network as all other applications. The trick is that VC requires quite large (and more importantly, consistently large) amounts of bandwidth. We are talking MBps. Now if you were on your broadband connection at 1MBps at home, imagine trying to have a VC call and surf the internet at the same time.

The fight is trying to convince IT guys that the bandwidth for VC needs to be kept separate from the rest of the traffic, as in a lot of cases, the rest of the traffic will take priority over the VC and cause packet loss and freezing etc etc.

that's a very basic view point, from someone who usually only sees the finished product after all these battles have been fought.

you can refer to me as Andy, Forum Moderator, VTCTalk.com :D

CamSys
05-18-2005, 07:45 AM
Esther,

I attempted to send you an email today, but it bounced back.

Feel free to contact us with any questions that you may have about videoconferencing.

CamSys
http://www.camsysco.com
sales@camsysco.com
614-436-1777

estherschindler
05-18-2005, 08:07 AM
The fight is trying to convince IT guys that the bandwidth for VC needs to be kept separate from the rest of the traffic, as in a lot of cases, the rest of the traffic will take priority over the VC and cause packet loss and freezing etc etc.

Any recommendations on how best to do that? Either the convincing or the infrastructure?

Morgan81
05-18-2005, 08:14 AM
... what do you wish someone had told you, when you were new to the subject?

That all your clients will second guess every move you make so have EVERYTHING documented, and outside of this site, there isn't much support out there so be prepared to do a lot of testing and a lot of reading.

Slightly jaded, I know, but feel free to PM me if you wish.

estherschindler
05-18-2005, 08:22 AM
That all your clients will second guess every move you make so have EVERYTHING documented, and outside of this site, there isn't much support out there so be prepared to do a lot of testing and a lot of reading.

I'll PM separately... but you raise two general questions:

* How do you test? (this is an important one)

* What ARE your other resources? What books, sites, etc.? I know how hard it was to find _this_ place; are there others?

estherschindler
05-20-2005, 09:51 AM
you can refer to me as Andy Marczak, Forum Moderator, VTCTalk.com :D

Actually, if you don't want to give you full affliation, I'd be better off quoting you as "Andy Marczak, a network administrator at a large midwestern insurance company" or something equally specific-yet-vague. The whole point is credibility, without putting your job in danger.

Anybody have any more advice? I've gotta write this thing. I was rather hoping for deep-tech suggestions, like "Interactive-Video traffic should be marked to DSCP AF41; excess videoconferencing traffic can be marked down by a policer to AF42 or AF43." But I'll take anything technical at all! <appreciative smile>

mazzarak
05-20-2005, 10:19 AM
Hi Esther - don't worry, this isn't my day job! Or you can call me "Helpdesk Manager of a global video bridging service provider"

estherschindler
06-03-2005, 04:58 PM
Hi all: thought I'd let you know that my article's gone live at
http://www.labratmagazine.com/content/view/181/40/1/0/

Thanks again for all your help!

AZA43
07-17-2007, 08:18 AM
Howdy Esther,
This article from CIO.com, 7 Quick Tips for Videoconferencing Beginners, might be helpful. Check it Out:

http://www.cio.com/article/124000

AZA :rambo: