jingle error cause account to disconnect
Bug description
When I receive the following xml from empathy ( for example, when gajim crashed but the other side didn't and I chose to stop the video call, once gajim is back and connected ), gajim disconnect :
\<!-- In -->
\<iq type="set" id="131851144379" to='misc@example.org/Portable/Akroma' from='phoebe@example.org/takara'>
\<jingle xmlns='urn:xmpp:jingle:1' action='session-info' sid='66' initiator='misc@example.org/Portable/Akroma'>
\<ringing xmlns='urn:xmpp:jingle:apps:rtp:info:1'/>
\</jingle>
\</iq>
\<!-- In -->
\<iq type="result" id="67" to='misc@example.org/Portable/Akroma' from='phoebe@example.org/takara'>
\</iq>
\<!-- Out -->
\<iq xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" to="phoebe@example.org/takara" type="error" id="131851144379" from="misc@example.org/Portable/Akroma">
\<jingle action="session-info" initiator="misc@example.org/Portable/Akroma" xmlns="urn:xmpp:jingle:1" sid="66">
\<ringing xmlns="urn:xmpp:jingle:apps:rtp:info:1" />
\</jingle>
\<error code="500" type="cancel">
\<feature-not-implemented />
\</error>
\<unsupported-info xmlns="urn:xmpp:jingle:errors:1" />
\</iq>
\<!-- In -->
\<stream:error>
\<unsupported-stanza-type xmlns='urn:ietf:params:xml:ns:xmpp-streams'/>
\</stream:error>
\<!-- In -->
\</stream:stream>
misc@example is gajim hg, phoebe@example is running empathy 2.29. Both are on the same subnet.