Hi Derek, <br><br>Many of the items you listed are infact integral to the insors machines - the only problem with the insors nodes is that sometimes it is difficult to interact with AG nodes - but having the other features you mention creates a really nice tool.
<br><br>Julie<br><br><div><span class="gmail_quote">On 1/22/07, <b class="gmail_sendername">Derek Piper</b> <<a href="mailto:dcpiper@indiana.edu">dcpiper@indiana.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br> Yes, looks like Steve Smith was right on the money with that. So what<br>happened with that project? I'd think that would have been a smarter way<br>to go with AG3.. ah well.<br><br> Derek<br><br>Andrew Sharpe wrote:
<br>> Hi Derek, you might like a read of<br>> <a href="http://people.vislab.usyd.edu.au/~ssmith/apac05/apac05-presentation.pdf">http://people.vislab.usyd.edu.au/~ssmith/apac05/apac05-presentation.pdf</a><br>><br>
> Andrew<br>><br>> Derek Piper wrote:<br>>><br>>> Hi all,<br>>><br>>> Something I was thinking about was the differences between AG and<br>>> H.323 and I was wondering if a 'blend' of the two, in a way, would be
<br>>> an interesting direction to go in.<br>>> What I'm thinking about is this, and of course there are many<br>>> questions and details to work out but I thought I'd bring it up to see<br>>> what people might think:
<br>>><br>>> A 'Call server' that people log in to when the 'AG caller' client<br>>> starts, analogous to the IM server, Jabber server or H.323 'gateway'<br>>> Allows IM communication with all those connected
<br>>> 'Buddy lists' to see who's on?<br>>> What about distribution of servers.. would you need an account on<br>>> every server in the world? what about a registry of servers?<br>>>
<br>>> IM 'calling' ..i.e. make a noise, flash something.. get user attention.<br>>> nicer than speakers on hanging around in a venue<br>>> people who don't know you're on or where you're on may stand a
<br>>> better chance of contacting you :><br>>><br>>> Initiate video call just allocates IP addresses in the same way as a<br>>> venue and runs media tools against either multicast or unicast to a
<br>>> bridge if that preference is set.<br>>> Simple 2-way video conferencing. We've achieved 'AG Skype'<br>>><br>>> Add another participant to a 'call' by invite or by messaging each
<br>>> participant.<br>>><br>>> Could also move to 'conference room' which is the same as an AG venue<br>>> is now.<br>>> Maybe launch full AG VenueClient at that venue?<br>>> Then you could do the same shared-app stuff as we have now.
<br>>><br>>><br>>> I'm kicking this around as a possibility and a direction for a<br>>> project either as something that the AGtk moves towards or is an<br>>> add-on for it. One of the things I've noticed is that polycoms are
<br>>> often used as a back channel and an ad-hoc meeting method because you<br>>> can *call* someone. It's a videophone. AG relies on someone turning up<br>>> where you are, and that's sometimes very awkward and not what people
<br>>> want to do.<br>>> Basically to implement it seeing as we have a Jabber integration<br>>> doesn't seem that hard on the surface. The client would start off to<br>>> appearing something like GAIM, Psi or Skype and you place a video call
<br>>> to someone or start a conference in a venue.<br>>><br>>> I'm curious to hear some points of view about it.<br>>><br>>> Derek<br>>><br>><br>><br><br>--<br>Derek Piper -
<a href="mailto:dcpiper@indiana.edu">dcpiper@indiana.edu</a> - (812) 856 0111<br>IRI 323, School of Informatics<br>Indiana University, Bloomington, Indiana<br><br></blockquote></div><br>