[Pidgin] #4741: Allow STUN on non-standard ports
Pidgin
trac at pidgin.im
Tue Jan 29 09:45:14 EST 2008
#4741: Allow STUN on non-standard ports
-----------------------------+----------------------------------------------
Reporter: chemistrydioxide | Owner: lschiere
Type: defect | Status: new
Priority: minor | Component: unclassified
Version: 2.3.1 | Keywords: STUN port
Pending: 0 |
-----------------------------+----------------------------------------------
Usually, STUN uses port 3478, but some STUN servers run on another port
than 3478, e.g. 10000. Using such a STUN server, e. g.
stun.sipgate.net:10000, doesn't work because Pidgin doesn't recognize the
port number. Instead, it considers the port number to be a part of the
domain and sends it to the dns(!):
{{{
(15:00:50) dnsquery: resolving failed for stun.sipgate.net:10000:
name or service not known
(14:57:21) stun: got 0 SRV responses, server: stun.sipgate.net:10000,
port: 3478
}}}
I'm not shure whether we need to change libpurple in order to make it
recognize the port entered into the same input box or add an additional
port input box to Pidgin.
--
Ticket URL: <http://developer.pidgin.im/ticket/4741>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list