Ok then here you go:
[snip a long protocol]
Or, you just advertise your VoIP capability when it's enabled.
<presence> <c xmlns='http://jabber.org/protocol/caps' node='http://exodus.jabberstudio.org/caps' ver='0.9' ext='tins ftrans xhtml voipuri'/> </presence>
When you disable it (for example when you're in a call)
<presence> <c xmlns='http://jabber.org/protocol/caps' node='http://exodus.jabberstudio.org/caps' ver='0.9' ext='tins ftrans xhtml'/> </presence>
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='[EMAIL PROTECTED]/work'
to='[EMAIL PROTECTED]/home'>
<x xmlns='jabber:x:oob'>
<url>callto:whatever</url>
</x>
</message>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).
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.
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mail.jabber.org/mailman/listinfo/jdev
