Hide Forgot
Description of problem: I am trying to configure two Empathy instances, but behind separate NAT devices, so that they can make video calls to each other. It seems that Empathy does not properly use STUN to identify the public IP address which should be used to set up the call. This seems to be because telepathy-gabble uses stun.telepathy.im for STUN, but this host does not seem to provide a STUN service. Would it be possible to patch telepathy-gabble to use another STUN service? Version-Release number of selected component (if applicable): empathy-3.12.12-2.fc24.x86_64 telepathy-gabble-0.18.2-6.fc24.x86_64 How reproducible: Every time Steps to Reproduce: 1. Try to make a video call from a host behind at NAT device to another host behind another NAT device. 2. Watch the communication in Wireshark. Actual results: The host making the call tries to use STUN to discover its public IP address. stun.telepathy.im replies with ICMP destination unreachable (port unreachable) messages. As a result, the host making the call tries to use its private IP address, and this fails. Expected results: The video call should complete. Additional info: Another user reported this bug upstream: https://bugs.freedesktop.org/show_bug.cgi?id=93969
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora 'version' of '24'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.