Closed GoogleCodeExporter closed 9 years ago
If everything is working fine over a WiFi network, maybe your 3G provider is
filtering some of the UDP ports used for the RTP (Voice) traffic.
Have you tried the same think with WiFi ?
Original comment by electro...@gmail.com
on 17 Sep 2010 at 8:35
I can talk to pbxes.org over 3G with pbxes.org accounts. It only happens on
Ekiga.net between Ekiga.net over 3G.
Original comment by runner...@gmail.com
on 19 Sep 2010 at 12:48
So, maybe Ekiga doesn't like the NAT gateway, between your device and their
server. (I noticed that Pbxes.org deals quite well with NAT)
Have you tried with stun.ekiga.net:3478 in Options > Media > STUN server, and
enable STUN support ?
Original comment by electro...@gmail.com
on 20 Sep 2010 at 10:48
Ekiga cannot be registered without STUN server (stun.ekiga.net) enabled.
Original comment by runner...@gmail.com
on 20 Sep 2010 at 11:30
Issue 232 has been merged into this issue.
Original comment by r3gis...@gmail.com
on 21 Sep 2010 at 4:53
Original comment by r3gis...@gmail.com
on 17 Oct 2010 at 11:26
For echo test in nated environement use :sip:*673500@ekiga.net instead of
sip:500@ekiga.net
I tested over all available sip client except ekiga on nated env, 500 doesn't
work at all.
I think they do something of another protocol than sip & stun to resolve ip (or
they send rtp packets)
Original comment by r3gis...@gmail.com
on 27 Oct 2010 at 8:58
Issue 1338 has been merged into this issue.
Original comment by r3gis...@gmail.com
on 3 Nov 2011 at 12:24
Original issue reported on code.google.com by
runner...@gmail.com
on 7 Sep 2010 at 11:24