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

[tharindufit]

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@ctx10/ctx10" to="wizzle2@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@ctx10/ctx10" to="wizzle@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>

 

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

Could anyone give me a solution to test this implementation with Pidgin client.

Kind Regards,

Tharindu Madushanka

_______________________________________________
Devel mailing list
Devel@...
http://pidgin.im/cgi-bin/mailman/listinfo/devel

[tharindufit]

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@ctx10/ctx10" to="wizzle2@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@ctx10/ctx10" to="wizzle@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>

 

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

Could anyone give me a solution to test this implementation with Pidgin client.

Kind Regards,

Tharindu Madushanka

_______________________________________________
Devel mailing list
Devel@...
http://pidgin.im/cgi-bin/mailman/listinfo/devel

[Paul Aurich-4]

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@ctx10/ctx10" to="wizzle2@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@ctx10/ctx10"
> to="wizzle@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).

~Paul



_______________________________________________
Devel mailing list
Devel@...
http://pidgin.im/cgi-bin/mailman/listinfo/devel

[tharindufit]

Hi

Does it mean Pidgin doesn't support XEP-0047 alone ? Could you please tell since implementing 0096 seems to be really difficult :)

Thank you,

Tharindu

_______________________________________________
Devel mailing list
Devel@...
http://pidgin.im/cgi-bin/mailman/listinfo/devel

[Paul Aurich-4]

And Tharindu Madushanka spoke on 10/25/2009 09:32 PM, saying:
> Hi
>
> Does it mean Pidgin doesn't support XEP-0047 alone ? Could you please
> tell since implementing 0096 seems to be really difficult :)
>
> Thank you,
>
> Tharindu

XEP-0047 by itself does not facilitate file transfer; it simply
establishes a data channel between the two ends.

The SI spec describes the (current) standard for doing file transfer
between two clients, which involves requesting a file transfer (and
negotiating what sort of channel to use) and only then starting up an
IBB stream and sending the file.

~P



_______________________________________________
Devel mailing list
Devel@...
http://pidgin.im/cgi-bin/mailman/listinfo/devel