After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 568560 - ekiga does not honour port ranges defined in config
ekiga does not honour port ranges defined in config
Status: RESOLVED FIXED
Product: ekiga
Classification: Applications
Component: general
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2009-01-21 15:25 UTC by Vincent Untz
Modified: 2009-01-21 21:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vincent Untz 2009-01-21 15:25:03 UTC
Forwarding https://bugzilla.novell.com/show_bug.cgi?id=464285

This is for ekiga 3.0.1, and I can reproduce this.

===========
as the default port range (udp 5000-5100) is already used on my router and
behind a symmetric NAT , I used gconf-editor to change following values:
udp_port_range from 5000-5100 to 5200-5300 and
listen_port from 5060 to 5260 (the ports that the router forwards to my host)

The STUN server gets the address of my router and sends it to ekiga, but then
ekiga uses port 5000 to start the registration

Looking at the source code, the port range seems to come from the hard coded
values at line 111 ekiga-3.0.1/src/endpoints/manager.cpp : "SetUDPPorts (5000,
5100);" and not from the configured value in
~/.gconf/apps/ekiga/protocols/ports/%gconf.xml :
<?xml version="1.0"?>
<gconf>
        <entry name="udp_port_range" mtime="1231062914" type="string">
                <stringvalue>5200-5300</stringvalue>
        </entry>
</gconf>

So sip registration fails and ekiga cannot be used (could make twinkle work):

2009/01/04 13:14:31.856   0:03.603      StunDetector:0xf34f0950 OPAL    STUN
server "stun.ekiga.net" replies Symmetric NAT, external IP 87.66.159.236
....
Via: SIP/2.0/UDP
87.66.159.236:5000;branch=z9hG4bK06070cea-c6d8-dd11-9d61-00138fde0375;rport
-> wrong port
and of course: Set state Terminated_Timeout for transaction 1 REGISTER
because the router does not forward port 5000
===========

There's a debug log at https://bugzilla.novell.com/attachment.cgi?id=263710
Comment 1 Damien Sandras 2009-01-21 20:05:49 UTC
With 3.1.x it works (at least here).

I'm not 100% sure I will have the time to fix 3.0.x
Comment 2 Damien Sandras 2009-01-21 21:08:15 UTC
I backported a fix from trunk in the stable branch that could fix the issue. Please reopen if it is not the case. Thanks!