Monthly Archives: November 2010

In the current version of Pidgin 2.7.5 can be in the settings (Menu / Werzeuge / Einstellungen / Netzwerk) Enter a STUN Server. A STUN server is used to, that a computer (or. In this case, Pidgin) can find, on which public IP address (and what UDP port) He can be reached, when it is itself a local IP, p.E.. has the power 192.168.xy. This is important for file transfers, where between two chat partners usually a direct connection is established.
Unfortunately, the designation “STUN-Server” Pidgin in the settings not quite right. Because Pidgin is realistic to expect there not to specify the STUN server, but the specification of a domain, within it then looks for a STUN server.
An example to illustrate:
The STUN server of the provider “Sipgate” has address stun.sipgate.net.
Now I would have expected, that you just must enter this address in pidgin, if you want to use the STUN server from sipgate. – Not at all!
In this case, try Pidgin by DNS for a STUN server and asks for:
SRV _stun._udp.stun.sipgate.net
Pidgin is looking for a server that is (SRV) in the domain stun.sipgate.net for the STUN protocol, reached by the UDP is. There is none. But under the domain sipgate.de he would find. And actually – when sipgate.de enters into the Pidgin settings, asks for Pidgin SRV _stun._udp.sipgate.de and receives a response SRV stun.sipgate.net , then uses the pidgin.