I changed the host property so that it will always match the proxy JID, but I think the wildfire server is sending a different host name as a response. I took a screenshot of my wildfire admin screen to show you what I am talking about.
the 127.0.0.1 is OK. Wildfire automatically shows the IP of your machine. I invite you again to create a account on our server and use it for your testing.
the server is available under ag-software.de. You should be able to create a account with any jabber
Here is a list of available jabber clients: http://www.jabber.org/software/clients.shtml
I am still having this problem. No matter which client I use, it is unable to connect to the offered streamhosts. the 206.158.107.6 is the outside IP address of the wildfire server, while the 192.168.10.71 is the local IP. Do you have any more suggestions to why a connection cannot be made?
I assume the debug from an attempt of sending an file to another user.
Look at the second packet you send. Host is there 127.0.0.1, but it should be one of the IP's 206.158.107.6, 192.168.10.71. But i can't connect to your external IP on port 7777. So this IP is configured not correctly in your firewall or router.
You also should change the order of the packets you send. But this is not related to your problem. The first query you send is getting the information (host and port) from your proxy. And this is the data which you should include with your second packet which offers the streamhost(s). So you should wait until you get the response of your first query, and use this information for building your second packet. The best is to use an IQGrabber for sending this packets.
Everything seems to be configured correctly in the Wildfire admin console. Are there any specific settings I should set other than:
1) enabling file transfer proxy on port 7777?
2) enabling s2s?
I am curious because I am able to use Spark to send and recieve messages using my Wildfire server, but not with the MiniClient. That is why I can only assume the issue is in the code.