[jdev] Gaim and gnomemeeting using jabber

[Richard Dobson]

> Or, you just advertise your VoIP capability when it's enabled.

Still need to advertise a feature in disco#info as this is a requirement for 
JEP-0115 to work.

> and then when you know the other side is VoIP capable, send them a URI 
> using JEP-66. (As JEP-66 states: "Going further afield, several existing 
> Jabber clients use the callto: URI scheme to initiate voice conferencing 
> via NetMeeting or GnomeMeeting.")
>
> <message from='stpeter at jabber.org/work'
>          to='MaineBoy at jabber.org/home'>
>   <x xmlns='jabber:x:oob'>
>     <url>callto:whatever</url>
>   </x>
> </message>

It would work but it would be far better to use "jabber:iq:oob" (as I 
described) rather than "jabber:x:oob" as you can detect when the other side 
has rejected the call and tell the calling client (and probably 
automatically close down the voip client) so they wont be just left there 
hanging wating for a call that will never come. Also unless we are going to 
specify callto: urls as the only allowable url formats it either needs to 
determine the allowed formats using JEP-0020 as I described or using disco 
features.

> You can add in some disco nodes and such (perhaps about which different 
> uri schemes clients support) when GAIM supports that or you when you want 
> to make a JEP for it. (since Entity capabilities and Disco are linked).

As far as I read it entity capabilities require that they have a 
corresponding disco node so other clients can determine what a particular 
entity cap identifier means, so a disco#info feature is required to be able 
to use JEP-0115, similar to what I had in my example.

> You can implement this using existing protocols that work today, still 
> have your functionality requirments met, and not expose your IP until you 
> initiate a call. You'll just need to patch GAIM to support 115.

And JEP-0030 if it does not support it already, as well as adding in the 
feature var for it.

Richard