[Pidgin] Implementing a XEP-0047 In-Band File Transfer client testing with Pidgin Client

Paul Aurich paul at darkrain42.org
Sun Oct 25 23:36:15 EDT 2009

And Tharindu Madushanka spoke on 10/25/2009 07:37 PM, saying:
> Hi,
> I have installed OpenFire Jabber Server and trying to implement XEP 0047
> client with it. When I send the following message to initiate the
> session after login I get feature-not-implemented error message. I am
> trying to send this message to a Pidgin 2.6.3 Client logged into my
> OpenFire server. I am not sure from where I get this message. Could
> anyone kindly explain me about this.
> <iq type="set" from="wizzle at ctx10/ctx10" to="wizzle2 at ctx10/ctx10"
> id="ftreq1"><open xmlns="http://jabber.org/protocol/ibb"
> block-size="4096" sid="i781hf64" stanza="iq"></open></iq>
> I have recieved a response similar to this then.
> <iq type="error" id="ftreq1" from="wizzle2 at ctx10/ctx10"
> to="wizzle at ctx10/ctx10"><open xmlns="http://jabber.org/protocol/ibb"
> block-size="4096" sid="i781hf64" stanza="iq"/><error code="503"
> type="cancel"><service-unavailable
> xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq>

The error you're showing here is a service-unavailable error, not
feature-not-implemented.  My guess is that you're not negotiating Stream
Initiation (XEPs 0095 and 0096) first, because that seems to be the way
pidgin would generate a feature-not-implemented.

> But it says OpenFire supports this XEP - 0047. And also I have Pidgin
> 2.6.3 that says it also supports In-Band File Transfer

The server shouldn't really make a difference (unless it's actively
blocking file transfers).


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://pidgin.im/pipermail/devel/attachments/20091025/35fad80e/attachment.sig>

More information about the Devel mailing list