Le lundi 13 d�cembre 2004 � 13:33 +0100, PUYDT Julien a �crit : > 1) if the other end never received a 'voipgm2' cap, then it will send a > disco request on it (either to me or some other) and learn for example > that it means: > <feature var='http://jabber.org/protocol/voip/h323'/> > <feature var='http://jabber.org/protocol/voip/callto'/>
Now, that part is probably not in any jep yet, and this has to be common for the feature to work: what would be the correct features to report and tell we're able to manage voip calls. Shall the client just declare some <feature var='http://jabber.org/protocol/voip'/> then use feature-neg to precise what it means (Dobson's original proposal -- see his mockup) or do things more precisely at that point, and already declare several sub-features (like I did above). I think doing like I said is less protocol-compliant in some sense, but at least we won't end up in the situation where some clients negociate voip-cap, then discover later that they have nothing in common :-/ Anyway, once that question is settled, I'll need to: * make the chosen feature(s) registered somewhere ; * find time to implement things since they're now clear enough in my mind. JP _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mail.jabber.org/mailman/listinfo/jdev
