Then I would suggest you send it as a different feature cap of "voipgm2" or
something else rather than "voip" and this time include both h323 and sip as
features in the response, e.g.
<presence> <c xmlns='http://jabber.org/protocol/caps' node='http://exodus.jabberstudio.org/caps' ver='0.9' ext='ftrans xhtml voipgm2'/> </presence>
It doesnt matter what the cap string is so long as its nice and short, it
can be anything you like (so long as its not already used by that version of
the client), what matters is what you return in the disco#info response when
other clients query what it means.
Uh... bad: if I put the name of the voip client in the caps, I lose all the benefits of having several clients for the same protocol. Let's call it voip_h323 and voip_sip!
?? A bit confused here, what benefits are you loosing??, the caps in and of themselves do not mean anything, it is the disco#info requests that you make for them that allow you to gain any meaning for it, if anything you will want to send a cap of voiphs and include both the h323 and sip features in the response, as otherwise you are wasting bandwidth by requiring that clients make two disco#info requests when they only need make one.
e.g. rather than the following as you suggest (which will require two disco#info requests)
<presence> <c xmlns='http://jabber.org/protocol/caps' node='http://exodus.jabberstudio.org/caps' ver='0.9' ext='ftrans xhtml voip_h323 voip_sip'/> </presence>
Just do (which only requires one disco info request)
<presence> <c xmlns='http://jabber.org/protocol/caps' node='http://exodus.jabberstudio.org/caps' ver='0.9' ext='ftrans xhtml voiphs'/> </presence>
You need to remember that this protocol is trying to reduce bandwidth consumption so you must always strive towards this and eliminate any unnecessary round trips, also remember that you could have if you really wanted "eefefe" as the cap, e.g.
<presence> <c xmlns='http://jabber.org/protocol/caps' node='http://exodus.jabberstudio.org/caps' ver='0.9' ext='ftrans xhtml eefefe'/> </presence>
as you should not be trying to get any meaning from the caps themselves.
Richard
_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mail.jabber.org/mailman/listinfo/jdev
