Opened 8 years ago

Last modified 4 months ago

#4741 new enhancement

Allow STUN on non-standard ports

Reported by: chemistrydioxide Owned by:
Milestone: Component: libpurple
Version: 2.3.1 Keywords: STUN port
Cc:

Description

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.

Change History (6)

comment:1 Changed 8 years ago by chemistrydioxide

I think this is rather an enhancement than a defect, but i can't change it any longer. Sorry for choosing the wrong one.

comment:2 Changed 8 years ago by rlaager

  • Type changed from defect to enhancement

comment:3 Changed 8 years ago by chemistrydioxide

I just noticed that Sipgate is advertising their STUN server via DNS. This means that i can use it without needing to change Pidgin.

chemistrydioxide@localhost:~$ host -t SRV _stun._udp.sipgate.de
_stun._udp.sipgate.de has SRV record 0 0 10000 stun.sipgate.net.
_stun._udp.sipgate.de has SRV record 10 0 3478 stun.sipgate.net.
_stun._udp.sipgate.de has SRV record 10 0 10000 stun.sipgate.net.

comment:4 Changed 7 years ago by lschiere

  • Owner lschiere deleted

comment:5 Changed 7 years ago by darkrain42

  • Component changed from unclassified to libpurple

comment:6 Changed 4 months ago by dlenski

This problem still seems to exist as of January 2016.

As a result, Pidgin can't use any of the Google STUN servers which run on a non-standard port: https://gist.github.com/zziuni/3741933

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!