[jitsi-dev] Problem with jitsi vs iChat – kind of Service Discovery loop


#1

Hello,

I observed occasional traffic peaks on my server. The reason turned out to be two clients – one jitsi and one iChat user who are subscribed to each other. The iChat CLients sends an disco-iq to jitsi, which answers with an error. This error is ignored by iChat, it asks again (see extract below). While I think that the bigger error is on the iChat side there may be an error on jiti's side too: To my (limited) xmpp understanding the error type is case-sensitive, so I think jitsi should send „<errorcode="404" type="cancel">“ instead of „<errorcode="404" type="CANCEL">“

   <iq id="iChat_44608B90"to="ZZ@yy.de/jitsi-nbitjc"from="XX@yy.de/XX-iMac"type=“get”>
     <query xmlns=“http://jabber.org/protocol/disco#info"node="http://jitsi.org#video-v1”/>
   </iq>
   <iq id="iChat_44608B90"to="XX@yy.de/XX-iMac"type=“error”>
     <query xmlns=“http://jabber.org/protocol/disco#info"node="http://jitsi.org#video-v1”/>
     <error code="404"type=“CANCEL”>
       <item-not-found xmlns=“urn:ietf:params:xml:ns:xmpp-stanzas”/>
     </error>
   </iq>
   <iq id="iChat_3978BF88"to="ZZ@yy.de/jitsi-nbitjc"from="XX@yy.de/XX-iMac"type=“get”>
     <query xmlns=“http://jabber.org/protocol/disco#info"node="http://jitsi.org#voice-v1”/>
   </iq>
   <iq id="iChat_3978BF88"to="XX@yy.de/XX-iMac"type=“error”>
     <query xmlns=“http://jabber.org/protocol/disco#info"node="http://jitsi.org#voice-v1”/>
     <error code="404"type=“CANCEL”>
       <item-not-found xmlns=“urn:ietf:params:xml:ns:xmpp-stanzas”/>
     </error>
   </iq>
   <iq id="iChat_1B361B5F"to="ZZ@yy.de/jitsi-nbitjc"from="XX@yy.de/XX-iMac"type=“get”>
     <query xmlns=“http://jabber.org/protocol/disco#info"node="http://jitsi.org#camera-v1”/>
   </iq>
   <iq id="iChat_1B361B5F"to="XX@yy.de/XX-iMac"type=“error”>
     <query xmlns=“http://jabber.org/protocol/disco#info"node="http://jitsi.org#camera-v1”/>
     <error code="404"type=“CANCEL”>
       <item-not-found xmlns=“urn:ietf:params:xml:ns:xmpp-stanzas”/>
     </error>
   </iq>
   <iq id="iChat_1E1FE2D8"to="ZZ@yy.de/jitsi-nbitjc"from="XX@yy.de/XX-iMac"type=“get”>
     <query xmlns=“http://jabber.org/protocol/disco#info"node="http://jitsi.org#”/>
   </iq>
   <iq id="iChat_1E1FE2D8"to="XX@yy.de/XX-iMac"type=“error”>
     <query xmlns=“http://jabber.org/protocol/disco#info"node="http://jitsi.org#”/>
     <error code="404"type=“CANCEL”>
       <item-not-found xmlns=“urn:ietf:params:xml:ns:xmpp-stanzas”/>
     </error>
   </iq>
   <iq id="iChat_37DA3F42"to="ZZ@yy.de/jitsi-nbitjc"from="XX@yy.de/XX-iMac"type=“get”>
     <query xmlns=“http://jabber.org/protocol/disco#info"node="http://jitsi.org#video-v1”/>
   </iq>
   <iq id="iChat_37DA3F42"to="XX@yy.de/XX-iMac"type=“error”>
     <query xmlns=“http://jabber.org/protocol/disco#info"node="http://jitsi.org#video-v1”/>
     <error code="404"type=“CANCEL”>
       <item-not-found xmlns=“urn:ietf:params:xml:ns:xmpp-stanzas”/>
     </error>
   </iq>

This loops in a rather high speed for a long time, giving a significantly increased bandwith usage.

Regards
     Michael