Tried opening he example RTP ports, no success...I tried using another
router and PC only by capturing with wireshark it seems that RTP traffic
is using port 5062...But in my setup port 5062 is open and still no
success...
On 11/1/2010 5:00 PM, Stuart Gathman wrote:
On 10/31/2010 06:41 AM, Aramil wrote:
I am using a NanoStation 2 in Router mode.The NS is connected
wirelessly to my neighbor's router and a switch is connect via
ethernet to the NS for LAN use.
The past few days I'm trying to use a VoIP client software to connect
to my VoIP account.I use Ekiga Softphone to do so, which requires UDP
ports 3478-3479 and 5000-5100 to be open.
So I have opened these ports both on my neighbor's router and on the
NS.The problem that I'm encountering is that although I manage to
register to the VoIP service, when I answer an incoming call the
caller is able to hear me, but I'm not able to hear the caller.So I
used wireshark and figured that there is no incoming traffic on my end.
I have used many linux VoIP clients with PCs connecting straight
forward to an ADSL router and worked perfectly.So this has something
to do with NS...
You also need incoming RTP ports open.
SIP 5000 to 5100 UDP SIP signalling, listen port: 5060
STUN 3478 to 3479 UDP Outgoing traffic to the STUN server
RTP Random/Various UDP Incoming traffic from the other end. Often
5004, 7070, 16382
Somehow the incoming RTP ports happen automagically in most case, I'd
like to understand how.
Treating it as magic for the moment, I've noticed that turning on
ip_nat_sip on linux iptables has the effect of
blocking *outgoing* audio. Ekiga seems to work best with no fancy
help from the router. Is there some kind of
"stateful SIP" option that can be turned off?
_______________________________________________
ekiga-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/ekiga-list
_______________________________________________
ekiga-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/ekiga-list
