<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3243" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=796392816-14032008><FONT face=Arial
color=#0000ff size=2>Hi Luis,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=796392816-14032008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=796392816-14032008><FONT face=Arial
color=#0000ff size=2>I'm sure you have already tried this - but I've had
reasonably good success using V4L webcam drivers with Debian and
Fedora.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=796392816-14032008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=796392816-14032008><FONT face=Arial
color=#0000ff size=2>Cheers, Ben.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=796392816-14032008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=796392816-14032008><!-- Converted from text/plain format -->
<P><FONT size=2>-----------------------------------------<BR>Ben
Green<BR><BR>Access Grid Support Centre<BR>Research Computing
Services<BR>University of Manchester<BR>Room G49-H, Kilburn Building<BR>Oxford
Road, Manchester, M13 9PL<BR><BR>tel: +44 (0)161 306 6621<BR>fax: +44 (0)161 275
0637<BR>email - ben.green@manchester.ac.uk<BR>web -
www.agsc.ja.net<BR>-----------------------------------<BR></FONT></P></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> owner-ag-dev@mcs.anl.gov
[mailto:owner-ag-dev@mcs.anl.gov] <B>On Behalf Of </B>Luis
Galárraga<BR><B>Sent:</B> 14 March 2008 16:22<BR><B>To:</B> Thomas D.
Uram<BR><B>Cc:</B> ag-dev@mcs.anl.gov;
openasel-commits@proyectossw.espol.edu.ec; "Ing. Verónica Macías"; Marisol
Villacrés<BR><B>Subject:</B> Re: [AG-DEV] Identity
certificates<BR></FONT><BR></DIV>
<DIV></DIV>Our problem is that it seems VIC does not recognize the connected
webcams. We did the test in four computers: two laptops with Ubuntu 7.10, one
laptop and a PC with Windows XP. In all cases cameras were tested and recognized
by other applications: Cheese, aMSN and VLC in Ubuntu Linux, VLC and Windows
Messenger in Windows. VLC did not recognize it automatically in Linux so we had
to provide the name of the device file.<BR><BR>Then we ran the Venue Client and
entered a venue. VIC and RAT started running as expected and audio could be
transmitted without any problem, VIC only showed a "Waiting for video" message.
When pressing the Menu button in VIC window, we realized that "Transmit button"
was disabled in all computers. I read that happens when video capture hardware
is not properly configured. We are looking for a way of telling vic the path to
the device file of the camera, but no success until now. By the way, these are
the webcams we used: Creative VF0050, Genius VideoCam Messenger and VGA Matrix
Webcam.<BR><BR>We also did another tests transmitting multicast camera streams
with vlc with relative success (when transmitting from Windows, there were
several problems, VLC frequently froze; in Linux complete happiness)<BR><BR>In
relation with the add-on services you mentioned, those are good news for us, as
we want to provide both Windows and Linux users a simple way to participate in
our webinars. Another question: Where can we found the most updated vic
and rat documentation?<BR><BR>Thanks in advance,<BR>Luis<BR><BR>
<DIV><SPAN class=gmail_quote>2008/3/14, Thomas D. Uram <<A
href="mailto:turam@mcs.anl.gov">turam@mcs.anl.gov</A>>:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV text="#000000" bgcolor="#ffffff"><BR>Luis:<BR><BR>The video capture
machine has, in the past, often run Linux, which is why you got that
impression from looking at older documentation. <BR><BR>In AG3, vic can
use USB cameras, firewire cameras, and dedicated capture cards with either a
VFW (older) or WDM/DirectShow (newer) driver. You should be having
success in either of these cases. If you're not, we need to look into
the cause a little deeper. Provide more details of the problems you ran
into, and your configuration, and I/we can help.<BR><BR>There are add-on
services for transmitting/receiving video using VLC (<A
onclick="return top.js.OpenExtLink(window,event,this)"
href="http://netmedia.gist.ac.kr/agdv/download.html"
target=_blank>http://netmedia.gist.ac.kr/agdv/download.html</A>). These
have so far only been made available on Windows, but it would be trivial to
make them also work under Linux (with VLC; DVTS would be more
difficult).<BR><BR>Tom
<DIV><SPAN class=e id=q_118abed63e2487b0_1><BR><BR><BR>On 3/13/08 10:07 AM,
Luis Galárraga wrote:
<BLOCKQUOTE type="cite">Thanks a lot for your help Tom. I have two
additional questions, but they related to audio and video transmision. As I
mentioned, our objective are single node users which should have just a
webcam and a microphone to participate in a webinar. People here in ESPOL
(colleagues but not members of this project), have successfully tested AG in
node configuration, but when we tried with a single computer, we could not
transmit video. Worried about this fact, I read all documentation about VIC
and understood that it requires a video capture card (our colleagues had
one) for transmitting video. Reviews and documentation about node
configurations indicate that the video capture computer should be a Linux
machine with a video capture card and that only in Windows it is possible do
it with a usb webcam or a firewire camera (no video card needed). Our tests
were in both platforms without success. Do Linux users need a frame grabber
for transmit video? Is it possible to use another tool like VLC for
transmitting video? We had successful results transmitting multicast video
streams from a webcam using VLC in Ubuntu Linux and Windows XP. In addition,
we found a way of redirecting raw video to another application instead of
showing it with VLC. <BR><BR>Thanks again.<BR><BR>Luis,<BR><BR>
<DIV><SPAN class=gmail_quote>2008/3/13, Thomas D. Uram <<A
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:turam@mcs.anl.gov"
target=_blank>turam@mcs.anl.gov</A>>:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">Hi
Luis:<BR><BR>There are a few things you need to know in this
regard:<BR><BR>- By default, AG3 venues do not require that clients have a
certificate<BR>to enter. Venues can be optionally configured to
require a certificate,<BR>in which case the user must present a
certificate that satisfies the<BR>access controls on the venue.<BR><BR>-
You can run your own CA and issue your own certificates. In
that<BR>case, you'll need to make sure your clients have both your
CA<BR>certificate and their personal certificate.<BR><BR>Otherwise, this
is general PKI. If you have other questions, don't<BR>hesitate
to ask.<BR><BR>Tom<BR><BR><BR>On 3/6/08 3:41 PM, Luis Galárraga
wrote:<BR>> Greetings:<BR>><BR>> I am part of project for
developing a webinar infraestructure based on<BR>> Access Grid. After a
long discussion in which suggestions in this<BR>> mailing list were
strongly considered, we have decided to implement a<BR>> simple client
for venues (in servers 3.x) using Java Web Start Apps.<BR>> As you can
see, there are many things to do, and developers have<BR>> started by
making tests with the soap interfaces in the our AG server,<BR>>
however they are not clear about the concepts behind
the<BR>> authentication process. We know AG uses digital certificates
for<BR>> everything: users and services and those certificates are
generated by<BR>> AG developers (after a process request). Can our
developer team<BR>> generate certificates signed by us or it is
required your sign?<BR>> Several people in our university will probably
use the system so we<BR>> would like to have the privilege to generate
the certificates. Could<BR>> someone explain us in a better way, the
technical issues behind<BR>> authentication based on certificates (=
how you implemented it)?. I<BR>> hope you can help us.<BR>><BR>>
Thanks in advance,<BR>><BR>> Regards,<BR>> Luis
Galárraga<BR></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></SPAN></DIV></DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>