As I am not in the telepathy mailing list, I saw the answer on http://www.mail-archive.com/[email protected]/msg03504.html (Please CC me if you answer)
> From: Alban Crequy >>Le Wed, 23 Sep 2009 17:32:48 +0200, >>Yann Simon <[email protected]> a écrit : >> At work, we have a Jabber-Server (I do not know which one). >> With this server, I am always disconnected and connected again every >> 7 minutes. >> >> A chat window always looks like this: >> Contact: bla bla bla >> - 16:42 - >> - Disconnected >> - Connected >> >> - 16:49 - >> - Disconnected >> - Connected [...] >> With other Jabber clients, I do not have this behavior. >> >> With other Jabber-Servers (like gmail), I do not have this behavior >> neither. >> >> Questions: >> - has somebody an idea of where this disconnection/connection comes >> from? >> - are there are parameters / settings... I can try to make these >> disappear? > >I have no idea, but you can have a look in the debug messages from >Empathy: >Menu Help -> Debug, and select the gabble component. >Then, wait until it disconnects and check if there is some error >messages somewhere. I do not see any error messages. An extract of the log: (telepathy-gabble:4655): tp-glib-DEBUG: started version 0.8.7 (telepathy-glib version 0.9.0) [...] [when the disconnect / connect happens:] (telepathy-gabble:4655): gabble-DEBUG: connection_iq_disco_cb: got disco request for node (null), caps are 3bf3ff (telepathy-gabble:4655): gabble-DEBUG: reply_with_features: sending disco response: <iq type="result" to="jabber.adesso.de" id="496-19491"> <query xmlns="http://jabber.org/protocol/disco#info"> <identity type="pc" name="Telepathy Gabble 0.8.7" category="client"></identity> <feature var="http://www.google.com/xmpp/protocol/session"></feature> <feature var="http://www.google.com/transport/p2p"></feature> <feature var="urn:xmpp:jingle:transports:raw-udp:1"></feature> <feature var="urn:xmpp:jingle:transports:ice-udp:1"></feature> <feature var="http://jabber.org/protocol/jingle"></feature> <feature var="urn:xmpp:jingle:1"></feature> <feature var="http://jabber.org/protocol/chatstates"></feature> <feature var="http://jabber.org/protocol/nick"></feature> <feature var="http://jabber.org/protocol/nick+notify"></feature> <feature var="http://jabber.org/protocol/si"></feature> <feature var="http://jabber.org/protocol/ibb"></feature> <feature var="http://telepathy.freedesktop.org/xmpp/tubes"></feature> <feature var="http://jabber.org/protocol/bytestreams"></feature> <feature var="http://jabber.org/protocol/si/profile/file-transfer"></feature> <feature var="http://www.google.com/xmpp/protocol/voice/v1"></feature> <feature var="http://www.google.com/xmpp/protocol/video/v1"></feature> <feature var="http://jabber.org/protocol/jingle/description/audio"></feature> <feature var="http://jabber.org/protocol/jingle/description/video"></feature> <feature var="urn:xmpp:jingle:apps:rtp:1"></feature> <feature var="urn:xmpp:jingle:apps:rtp:audio"></feature> <feature var="urn:xmpp:jingle:apps:rtp:video"></feature> <feature var="http://jabber.org/protocol/geoloc+notify"></feature> </query> </iq> (telepathy-gabble:4655): gabble-DEBUG: response_cb: got reply for request 0x91921a0 (telepathy-gabble:4655): gabble-DEBUG: replace_reply_cb: called: some error (telepathy-gabble:4655): gabble-DEBUG: gabble_vcard_manager_remove_edit_request: request == 0x916de60 >Because of bug https://bugzilla.gnome.org/show_bug.cgi?id=596101 you >can read the logs in the debug window only if: >1. you are fast, or >2. you use GABBLE_PERSIST=1 as explained on > http://telepathy.freedesktop.org/wiki/Debugging Thank you for the links. >What are your versions of telepathy-gabble, telepathy-mission-control >and empathy? Telepathy-gabble: 0.8.7-1 telepathy-mission-control: 5.3.1-1 empathy: 2.28.1.1 (coming for the PPA http://ppa.launchpad.net/telepathy/ppa/ubuntu) Yann _______________________________________________ telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
