[LUNI] [OT] ekiga setup ...

[Chad Sutton]

Have you run the echo test? Ekiga doesn't need anything special network 
wise. You just need to make sure that STUN is running.

I'm a little confused about your WAN port being 192.168.0.9. That 
doesn't seem correct to me. It looks like you are NAT'ing through your 
wireless router and then NAT'ing again through your DSL router. There is 
no reason to do that. I'm not sure if that is your issue or not.

If there is no specific reason to have two network segments, I would set 
your wireless router to 192.168.0.X and turn off DHCP and NAT. Just use 
it as an access point and not as a router. Your issue may be solved that 
way.

With just one router and one network segment, at the very least your 
setup will be simplified and perhaps your issues with VOIP will go away.

Arun Khan wrote:
> I am trying to use ekiga but have not had much success.
>
> During setup of the ekiga client it correctly detects that my system is 
> behind a NAT and configures it appropriately.  The client is able to 
> login to "ekiga.net" and I guess I am "online" because I am notified of 
> incoming calls.
>
> However, when I accept the call, I cannot hear the far party nor can the 
> far party hear me.
>
> My network setup is as follows:
>
>                      |
>   ekiga client-------|                   |
>                     *|-------------------|
>                                         +|--------- Internet (ADSL)
>
> ekiga client is 192.168.1.68 (Ubuntu 8.04, ekiga v2.0.12)
>
> * Linksys WiFi AP - LAN port is 192.168.1.1, WAN port is 192.168.0.9 
> (Nodes on LAN NAT'd on the WAN port)
>
> + DLink DSL502T router/modem - LAN port is 192.168.0.1, WAN port is dyn. 
> IP (PPPoE)
> (Nodes on LAN NAT'd on the WAN port)
>
> Would appreciate pointers from anyone who has used ekiga successfully - 
> please share your setup.
>
> TIA
>   


-- 
Later,
Chad Sutton
csutton at chadarius.com
http://chadarius.com
http://stephandchadsutton.com