Pandion file transfer openfire

I am curious to know what gaim is sending to cause that error… Which version of gaim are you using? I have been testing Gaim2 beta 4 and just yesterday I setup two tests of Gaim2 beta 5.

I have the problem with both versions. Any answers to this would help out greatly. I changed the logon on the IM client Pandion 2. I also changed the file transfer settings in the client to point to the wildfire server name and the port on the file transfer settings on the server.

Still no luck. Here are some debug files that I got of my wildfire server. Host: Connection: org. Prefix: jabber:client. You may want to check with the Pandion developers as it appears as though they may not be using the standard set out in the XEP.

I just upgraded my 3. I followed the full upgrade instructions from the forums page. I then tried a very large file some mb , and it transfered, however I got the same problem. Why would this be? Improve this question. Andy A. Andy A Andy A 3, 7 7 gold badges 35 35 silver badges 56 56 bronze badges.

The XMPP stanzas before the error from both sides would be interesting. Thanks for your response Flow. I've added more logs from my app from before the AndyA I am facing the same problem, can you see over this link and help in solving the issue — Android Rockss.

Add a comment. Active Oldest Votes. Use transfer. Improve this answer. Robin Robin This works. The following code can be used to read the file. And also you need the following permission in your manifest file I am facing the same problem, can you see over this link and help in solving the issue — Android Rockss.

Note : please change any thing if you want any details in Xmpp. Tushar Pandey Tushar Pandey 3, 3 3 gold badges 28 28 silver badges 46 46 bronze badges. We focused heavily on the file transfer user interface for the Spark 1. Some of the major areas of improvement over version 1. All too often with other IM clients , we've had to give up on a file transfer that fails to connect and resort to sending the file by email.

The usual culprit is a firewall or other network setting problems. The combination of Spark 1. Each approach offers a different balance of speed and reliability -- but the key point is that the transfer method is always negotiated automatically. If one fails, the next approach is tried until the file transfer can proceed. Spark will always attempt to establish a peer to peer p2p file transfer first.

Peer to peer connections are the fastest option and work great when both users are on the same network such as when they're in the same office location. However, p2p transfers almost always fail when one user is behind a firewall or using NAT network address translation. Peer to peer file transfers are shown in the top diagram on the right. If a peer to peer connection fails, Spark looks for a proxy server to complete the file transfer the middle diagram on the right.