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 438297 - Look at the port number of the incoming RTP traffic
Look at the port number of the incoming RTP traffic
Status: RESOLVED WONTFIX
Product: ekiga
Classification: Applications
Component: OPAL
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2007-05-14 11:45 UTC by Jan "Yenya" Kasprzak
Modified: 2020-06-06 16:28 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Jan "Yenya" Kasprzak 2007-05-14 11:45:03 UTC 
References: http://mail.gnome.org/archives/ekiga-list/2007-May/msg00080.html

In short, ekiga should try to work around the broken NATs when the NATed site guesses its source port (or maybe even address) incorrectly: the ekiga on a public IP should look at the port number and maybe even IP address of the incoming RTP stream, and display a warning message, when this is different from what the remote side announced in the SIP call setup. It may even start sending further RTP traffic to this IP address and port instead (changing the IP address may have security implications, though).
Comment 1 André Klapper 2020-06-06 16:28:42 UTC 
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.