[Rtcomm] [Rtcomm] [Bug 3120] New: Never contacts STUN server in auto/manual setup, doesn't connect through NAT?

[From: bugzilla-daemon at maemo.org]

https://bugs.maemo.org/show_bug.cgi?id=3120

           Summary: Never contacts STUN server in auto/manual setup, doesn't
                    connect through NAT?
           Product: Communication
           Version: 4.0
          Platform: N800
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Low
         Component: SIP
        AssignedTo: rtcomm at maemo.org
        ReportedBy: maemo at intrepid.cx
         QAContact: sip-bugs at maemo.org


SOFTWARE VERSION: 2.2007.51-3 (with rtcom-beta-os2008 v2.3 and without)

STEPS TO REPRODUCE THE PROBLEM:
Setup new SIP account:
In Advanced:    transport:auto
                Outgoing Proxy: blank
                Port:   5060
                Discover public address: on
                Keep-alive-mech: auto
                Keep-alive-freq: 0

                Auth name: blank
                Auth pass: blank

                Auto-detect STUN: on
                -or-
                Stun server: caretaker.intrepid.co.uk
                Stun port:   3478

Then attempt to connect to the SIP account from behind a NAT appliance.


EXPECTED OUTCOME:
If the device is located behind NAT I would expect it to try and contact the
STUN server (as specified in the DNS SRV entry) or specified manually to
determine the clients external IP address


ACTUAL OUTCOME:
Although the client does submit a DNS request for the SRV _stun._udp and it
does receive a reply, it never attempts to connect to the STUN server. Even if
specified manually, it makes no attempt. Instead it uses its local address
192.168.x.x in the SIP registration packets and the SIP Server tries to reply
directly back to the 192.168 addresses.

I've used tcpdump to watch the traffic, I can see the port53 requests and
replies, but nothing is ever made to udp/3478

It does work if no NAT is involved or I am behind a NAT device that intercepts
and re-writes NAT (iptables SIP helper I think) but in those circumstances I
wouldn't expect it to need to use a STUN server anyhow.

REPRODUCIBILITY:
always, whenever the device is behind a NAT appliance

EXTRA SOFTWARE INSTALLED:
I have tried it with rtcom-beta-os2008 v2.3 and without. Fresh install of OS
still fails

OTHER COMMENTS:

DNS entry for stun service:
_stun._udp.boatman.intrepid.co.uk. IN SRV 10 1 3478 caretaker.intrepid.co.uk.

Even if I specify a host directly, I would expect it to try and talk to that
STUN server (for example if I specify stun.ekiga.net) but it doesn't!


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.