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 342433 - uPNP
uPNP
Status: RESOLVED DUPLICATE of bug 337166
Product: ekiga
Classification: Applications
Component: general
GIT master
Other Linux
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-20 16:50 UTC by elias
Modified: 2006-05-20 17:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description elias 2006-05-20 16:50:00 UTC 
It would be great if ekiga would support uPNP to automatically forward the necessary ports on your uPNP capable router (all newer ADSL routers on the market support it). Therefore ekiga would get closer to skype in terms of connectivity.

As for now, the greatest disadvantage of SIP phones in general is the fact, that in most network setups they don't work out of the box! If you don't have access to the NAT/firewall/router you are lost!!!

This has to change in order to make SIP a great success like skype! I would love to see an OSS protocol take skypes place!

But I am afraid even with uPNP OSS VoIP protocols have to evolve to make that happen. I don't understand, why OSS developers don't try to use the Gnutella network in the way, skype uses their P2P network.

If we all are honest to ourselves, we have to admit, that SIP like it it now is a bunch of crap for the everyday user, because he does not want to nor is able to do the necessary changes to the NAT/firewall/router in order to make it work.

STUN is no help here either! This is simply for the fact, that the user has to take care about enabling STUN in the configuration. The user should not have to touch anything! And by the way, not even me could get ekiga to work with STUN yet, eventhough I have the proper education! I am pretty sure I will not get it to work without touching port-forwarding!

In the end of course it will work in MY home network, but as soon as I leave my home to go to work, I will have the same trouble again. And when I am in someone elses WLAN it wont work either. 

In 90% of all these cases I wont have access to the firewall. Therefore in 90% of all possible setups SIP will simply not work.

Therefore, SIP is not ready for the mass market!
Comment 1 Damien Sandras 2006-05-20 17:02:50 UTC 
This is a DUP of #337166.

"In 90% of all these cases I wont have access to the firewall. Therefore in 90%
of all possible setups SIP will simply not work."

When you start from a false hypothesis, you can conclude everything.

In 95% of the cases, the router will work with STUN. So your 90% are only 90% of the 5 remaining %.





*** This bug has been marked as a duplicate of 337166 ***