Investigate why Jingle is connecting to stun.xten.net
Users are questioning why Spark is trying to connect to stun.xten.net if Stun is disabled on the server. Reported at: http://www.igniterealtime.org/community/message/197294
As the code is in Smack, i'm registering this as a Smack ticket.
I installed 11186 and see the same behavior. When I remove jingle.jar from the plugins directory and launch Spark, I do not see the connection attempts to 18.104.22.168.
I could be misinterpreting the cause, but am wondering if this explains the static connection attempts when there are no STUN servers configured in Openfire? It at least matches the host and port we are seeing in the connection attempts.
(from STUNResolver.java within Smack)
// Fallback values when we don't have any STUN server to use...
private final static String FALLBACKHOSTNAME = "stun.xten.net";
private final static int FALLBACKHOSTPORT = 3478;
The default server has been removed. This will result in an IllegalStateException when Jingle tries to use STUN and no stun server is actually configured.
Can you please review this issue? There is a fixed URL in Smack that is causing significant trouble in several corporate environment due to heavy load on firewalls. The corporate network security guys are really upset and want this to be fixed.
A patch might be simple by removing the FALLBACKHOSTNAME or setting it to localhost.
There is also a similar fix needed for Jingle in the Spark trunk.
This strange behavior is STILL the same!
The client is trying to connect a strange server - there is no explaination so far.
Please comment or fix this behavior!