GNOME Bugzilla – Bug 618607
trying to contact ekiga.net:5060 even without an account configured!
Last modified: 2020-06-06 16:31:30 UTC
I have 3.2.6 here from Ubuntu Lucid. I am noticing, by way of my firewall, that despite not even having any ekiga.net accounts configured here, ekiga is still trying to contact ekiga.net:5060 (UDP). Why is this? I am sure it's simple an oversight of some sorts but it could be construed by a tin-foil-hat wearing, delusional, paranoid, conspiracy theorist[1] to be some sort of "phone home" information leak. It might be interesting to network sniff this traffic and open up the firewall to see what's trying to get out, but I'd rather not. [1] not that i am one of those, nor do i mean to offend or denigrate those who are. after-all, just because you are paranoid and delusional, doesn't mean that everyone isn't out to get you. :-)
It tries to: - find out your network type using STUN protocol - find out the publish presence of your contacts, if you have any (by default, you echo test and conference room from ekiga.net) Note: ekiga is a program which does not work without network connection, contrary to other programs. What do you propose?
(In reply to comment #1) > It tries to: > - find out your network type using STUN protocol Which is moot if I don't have any accounts configured for any servers outside of my network. > - find out the publish presence of your contacts, Which again, if I don't have any outside of my network, there is no need to try to go outside of my network. > if you have any (by default, > you echo test and conference room from ekiga.net) I would think that if I don't have an ekiga.net account, then I don't want (can I even use) the conference room facilities at ekiga.net. > Note: ekiga is a program which does not work without network connection, Of course not. It does not require a network connection outside of the local network though, to be useful, as is my case here. I have my own SIP server and it's that server that people have accounts on and use. Hence, no need for STUN tests, ekiga.net conferencing tests and whatnot. > What do you propose? Simply, if I don't have an ekiga.net (or other server outside of the local network/subnet) then don't try to assess things outside of the network as I won't be trying to leave the network. At a point where an account registration is attempted outside of the local network/subnet, then do the STUN tests, etc.
*** Bug 628293 has been marked as a duplicate of this bug. ***
In asterisk logs appear 33 times in a second after launching ekiga: [2010-09-03 10:12:52] NOTICE[3754] chan_sip.c: Sending fake auth rejection for user "Javier Barroso" <sip:javi@myip>;tag=04f882b7-a0b5-df11-9570-0017a420b5ad ... I suppose this have to do with subscribe to contacts (but have less than 30 contacts) My username in my ekiga host is javi, but I have configured other number as extension. Sorry if this comment is noise for this bug
Since this is in 3.2.7 also, any chance of it getting prioritized?
*** Bug 633260 has been marked as a duplicate of this bug. ***
I am sorry, but in my opinion this is less important than other bugs: there are bugs which prevent ekiga to work, while yours is that ekiga adds a noise. For STUN, you can remove the server in gconf settings, so I suppose STUN will not bother you anymore. Still, this bug might be simple to fix, so maybe it will get fixed sometimes soon.
Detect that at least two account entries are necessary that ekiga works. Also if I want it only use in my internal home network.
*** Bug 683961 has been marked as a duplicate of this bug. ***
*** Bug 683962 has been marked as a duplicate of this bug. ***
Ekiga is not under active development anymore: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/273 Ekiga saw its last release 7 years ago. The last code commits were 4 years ago. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (and transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active Ekiga development again in the future.