Bug 753838

Summary: Non automatic STUN discovery is not working
Product: [Fedora] Fedora Reporter: Robert Marcano <robert>
Component: telepathy-rakiaAssignee: Brian Pepple <bdpepple>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: bdpepple
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 09:12:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Robert Marcano 2011-11-14 16:24:35 UTC 
Description of problem:

Trying to setup a SIP account on ekiga.net, that has no DNS records for their STUN server, I changed the advanced settings and wrote different STUN servers. Every try resulted on "Network error" (generic error that does not say much).

Started Wireshark, the captured packets are like this:

1)  DNS - Standard query A stunserver.org
2)  DNS - Standard query response A 132.177.123.13
3)  DNS - Standard query NAPTR ekiga.net
4)  DNS - Standard query response
5)  DNS - Standard query SRV _sip._udp.ekiga.net
6)  DNS - Standard query response, No such name
7)  DNS - Standard query A ekiga.net
8)  DNS - Standard query response A 86.64.162.35
9)  SIP - Request: REGISTER sip:ekiga.net
10) SIP - Status: 606 Not Acceptable    (0 bindings)

The error "Not Acceptable" is because it is trying to register the internal ip of my laptop and not the external side of the NAT

SIP record says "Contact: <sip:user.x.x:47617>"

Analyzing the Wireshark log, there is a query for the address of stunserver.org, but that address is never used for an STUN query. I tried with other open STUN servers with the same results
Comment 1 Fedora End Of Life 2013-01-16 10:27:59 UTC 
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 2 Fedora End Of Life 2013-02-13 09:12:36 UTC 
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.