<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7232.11">
<TITLE>RE: [AG-TECH] One-page summary of AG port usage -- please help us complete it</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText98674 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>This is exactly why the AG community must
agree on FIXED port numbers (can I suggest a port registry for venues/rooms??
e.g. NCSA Titan will also use these ports ... for video and audio). Which (along
with the URLs of individual rooms) should not change when servers are rebooted,
serviced, etc. This would make it possible to write simple batch files or apps
that could pull up individual rooms with set preferences (unicast, multicast,
etc) automatically with a click of a button. This would be extremely important
for regular meetings with individual "lay" participants.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Zsolt</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV></DIV>
<DIV id=idSignature49040 dir=ltr>
<DIV><FONT face=Arial color=#000000 size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#000000 size=2>_ _ _</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#000000 size=2>Zsolt Nagykaldi, PhD</FONT></DIV>
<DIV><FONT face=Arial size=2>Research Associate, Clinical IT
Specialist</FONT></DIV>
<DIV><FONT face=Arial size=2>University Of Oklahoma Health Sciences
Center</FONT></DIV>
<DIV><FONT face=Arial size=2>Department Of Family And Preventive
Medicine</FONT></DIV>
<DIV><FONT face=Arial size=2>Oklahoma Center For Family Medicine
Research</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>900 NE 10th Street</FONT></DIV>
<DIV><FONT face=Arial size=2>Oklahoma City, OK 73104</FONT></DIV>
<DIV><FONT face=Arial size=2>Phone: (405) 271-8000 Ext.:1-32212</FONT></DIV>
<DIV><FONT face=Arial size=2>Fax: (405)
271-1682</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> owner-ag-tech@mcs.anl.gov on behalf of
Ivan R. Judson<BR><B>Sent:</B> Mon 2/13/2006 11:41 AM<BR><B>To:</B> 'R. P.
Channing ["Rick"] Rodgers'; ag-tech@mcs.anl.gov;
michael.daw@manchester.ac.uk<BR><B>Cc:</B> bernholdtde@ornl.gov;
jsummers@bachman.cs.ou.edu; terrazas@labmed2.ucsf.edu<BR><B>Subject:</B> RE:
[AG-TECH] One-page summary of AG port usage -- please help us complete
it<BR></FONT><BR></DIV>
<DIV><BR>
<P><FONT size=2>I think what you're hearing is unwillingness for anyone to
commit to a wrong<BR>answer.<BR><BR>From memory, the ports for vic, rat, and the
rest of the tools are allocated<BR>by the venue server. It can be a static
allocation configured by the<BR>provider or a dynamic allocation (I think the
default).<BR><BR>Given this configurability, it's impossible to state exactly
what ports the<BR>media tools will or won't use.<BR><BR>Sorry for the
complicated answer.<BR><BR>--Ivan<BR><BR>> -----Original Message-----<BR>>
From: owner-ag-tech@mcs.anl.gov [<A
href="mailto:owner-ag-tech@mcs.anl.gov">mailto:owner-ag-tech@mcs.anl.gov</A>]
On<BR>> Behalf Of R. P. Channing ["Rick"] Rodgers<BR>> Sent: Monday,
February 13, 2006 11:36 AM<BR>> To: rodgers@nlm.nih.gov; ag-tech@mcs.anl.gov;
michael.daw@manchester.ac.uk<BR>> Cc: bernholdtde@ornl.gov;
jsummers@bachman.cs.ou.edu;<BR>> terrazas@labmed2.ucsf.edu<BR>> Subject:
RE: [AG-TECH] One-page summary of AG port usage -- please help us<BR>>
complete it<BR>><BR>> Michael,<BR>><BR>> Thanks, I agree that AG
Central would be an excellent development resource<BR>> and then final home
for our summary of AG port usage. We certainly need<BR>> help
completing it. The biggest gap right now is port ranges for vic
and<BR>> rat.<BR>> I just *know* that folks working with the code for
these applications more<BR>> actively than we do could produce these numbers
in a few minutes.<BR>><BR>> In browsing around in the AG Central forums,
it appears that they have<BR>> only<BR>> received light traffic thus far,
not that that should stop us from helping<BR>> to<BR>> kick-start the
community there. It's not clear which forums would be<BR>>
optimal<BR>> for our purposes -- I suppose "AG Toolkit/General"? So I'm
taking your<BR>> advice,<BR>> reattaching our two documents here, and also
posting my original message<BR>> to<BR>> "AG Toolkit/General" on the forum
at <A href="http://agcentral.org">http://agcentral.org</A> as
wel.<BR>><BR>> CORRECTION: just tried to do the above, and got completely
wedged -- not<BR>> clear that I have permissions to post to the forum, even
though I'm<BR>> registered.<BR>> Then my web client got completely
stuck. Will try again later, sigh...<BR>><BR>> Cheers, Rick
Rodgers<BR>><BR>> > From: "Michael Daw"
<michael.daw@manchester.ac.uk><BR>> > Subject: RE: [AG-TECH]
One-page summary of AG port usage -- please help<BR>> us<BR>> complete
it<BR>> > Date: Mon, 13 Feb 2006 09:43:55 +0000<BR>> ><BR>> >
Great work guys! This is going to be good.<BR>> ><BR>> > But, can I
suggest using <A href="http://agcentral.org">http://agcentral.org</A> for this?
If the document<BR>> is<BR>> discussed and refined in a forum, it will be
easy to find. Once it's<BR>> ready, it<BR>> can be posted to the help
center. Because most of us still aren't<BR>> completely<BR>> used to using
agcentral, you can always post frequently to ag-tech too<BR>> with<BR>>
pointers.<BR>> ><BR>> ><BR>> > > -----Original
Message-----<BR>> > > From: owner-ag-tech@mcs.anl.gov<BR>> > >
[<A
href="mailto:owner-ag-tech@mcs.anl.gov">mailto:owner-ag-tech@mcs.anl.gov</A>] On
Behalf Of R. P.<BR>> > > Channing ["Rick"] Rodgers<BR>> > >
Sent: 10 February 2006 20:21<BR>> > > To: ag-tech@mcs.anl.gov<BR>>
> > Cc: rodgers@nlm.nih.gov; bernholdtde@ornl.gov;<BR>> > >
jsummers@bachman.cs.ou.edu; terrazas@labmed2.ucsf.edu<BR>> > > Subject:
[AG-TECH] One-page summary of AG port usage --<BR>> > > please help us
complete it<BR>> > ><BR>> > > Dear AG Colleagues,<BR>> >
><BR>> > > I now realize that the work I started last December,
trying<BR>> > > to create a<BR>> > > one-page summary of AG
port usage (based on the commendable<BR>> > > document created
by<BR>> > > Javier Gomez Alonso of the Access Grid Support Centre at
the<BR>> > > University<BR>> > > of Manchester) is not easily
locatable in the list archives.<BR>> > > I resend it,<BR>> > >
attached, along with the Excel version that David E.<BR>> > > Bernholdt
of ORNL kindly<BR>> > > created. As I said earlier, all of these
documents are missing some<BR>> > > key information, such as the port
ranges used by vic and rat.<BR>> > > I send this out<BR>> >
> again in the hope that another AG colleague will pick it up<BR>> >
> and complete it.<BR>> > > We all really need to have something
like this, and i would<BR>> > > hope that eventually<BR>> > >
it would end up on the AG web site(s), and be maintained to<BR>> > >
reflect any<BR>> > > coding changes/additions made to AG
software.<BR>> > ><BR>> > > Best Regards, Rick Rodgers<BR>>
> ><BR>> > >
--------------------------------------------------------------<BR>> > >
------------------<BR>> > > R. P. C. Rodgers, M.D. *
rodgers@nlm.nih.gov * (301)435-3267<BR>> > > (voice, fax)<BR>> >
> OHPCC, LHNCBC, U.S. National Library of Medicine, NIH<BR>> > >
Bldg 38, Rm. B1N-30F2, 8600 Rockville Pike, Bethesda MD 20894 USA<BR>> >
> <A
href="http://lhc.nlm.nih.gov/staff/rodgers/rodgers.html">http://lhc.nlm.nih.gov/staff/rodgers/rodgers.html</A><BR>>
> ><BR>> > ><BR>> > ><BR>> ><BR>><BR>>
--------------------------------------------------------------------------<BR>>
------<BR>> R. P. C. Rodgers, M.D. * rodgers@nlm.nih.gov * (301)435-3267
(voice, fax)<BR>> OHPCC, LHNCBC, U.S. National Library of Medicine,
NIH<BR>> Bldg 38, Rm. B1N-30F2, 8600 Rockville Pike, Bethesda MD 20894
USA<BR>> <A
href="http://lhc.nlm.nih.gov/staff/rodgers/rodgers.html">http://lhc.nlm.nih.gov/staff/rodgers/rodgers.html</A><BR><BR></FONT></P></DIV>
</BODY>
</HTML>