<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>[AG-TECH] Problems using AG Connector</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText73887 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Yes. The connector will not use UDP
tunneling, if multicast is available no matter how "broken" it is. You are not
the only one having serious problems with the connector (and AGTk as a whole).
Our site for example is not multicast enabled and when we use the connector (and
IF the UMTP server isn't down) we can connect to NCSA and vv2 servers, but other
participants who are multicast-enabled can not see or hear us at all. This, by
definition, should not happen. Unicast doesn't work fully either, we have no
incoming video. The inSORS product has no problem connecting us to any unicast
bridged rooms using the same infrastructure.</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=idSignature80764 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
Adam Carter<BR><B>Sent:</B> Mon 11/7/2005 6:47 AM<BR><B>To:</B>
ag-tech@mcs.anl.gov<BR><B>Cc:</B> braitmaier@HLRS.DE<BR><B>Subject:</B>
[AG-TECH] Problems using AG Connector<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Hi to anyone who's tried out AG Connector...<BR><BR>Michael
Braitmaier and I spent about an hour this morning experimenting with<BR>AG
Connector. We're having some difficulties getting it to work, and I<BR>wonder if
anyone could cast some light on the problem. We tried various<BR>different
combinations of Multicast/Unicast/UMTP and we tried running UMTP<BR>servers at
both of our own sites, all to no avail.<BR><BR>It seems to be the case that if
you have working multicast, the AG Connector<BR>agent notices this and reverts
to multicast. Is this true?<BR><BR>We're using the set-up with what seems to be
half-broken multicast:<BR>Edinburgh can see Stuttgart, but Stuttgart can't see
Edinburgh. When<BR>Edinburgh connects with UMTP, the server (in Stuttgart, on a
different<BR>network) claims "You are multicast-reachable from Server." and
apparently<BR>reverts to multicast.<BR><BR>Has anyone else observed this
behaviour? Is this a bug in AG Connector?<BR><BR>Thanks,<BR><BR>/\ |) /\
|\/|<BR><BR>--<BR>Dr Adam Carter, Applications Consultant, EPCC, The University
of Edinburgh<BR>adam@epcc.ed.ac.uk | +44 131 650 6009 | <A
href="http://www.epcc.ed.ac.uk/~adam">http://www.epcc.ed.ac.uk/~adam</A><BR><BR><BR><BR></FONT></P></DIV>
</BODY>
</HTML>