Hey Group; In the past I had a phoneline connection that worked great (except buffering) with a VoIP HAM related program called echoLinux and echogui. As a matter of fact I used to talk on the 442.150 repeater in Austin form Sugar Land. Trouble is when we got a adsl line from Altell and a DSL Speed Stream 5200 router it ended. Our router has a DHCP IP# that is stable and all boxes on the LAN have 192.168.1.# If I call uup echogui it goes out and comes back with a list of stations available. Thats when the problem starts - I never connect with a out station. I think it is a port forwarding problem - to which I have setup on the DSL router tcp, port number (as shown in /etc/services), my IP# (192.168.1.#) and the rebooted it. No luck! Anyone have a clue or know of a way to track the problem. -- 73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email: " n5xwb@hal-pc.org " 307 Savoy St. HAMs: " n5xwb@arrl.net " Sugar Land, TX 77478 BMW MOA #: 4146 - Ambassador LL# 1.281.242.3256 " http://counter.li.org " #279316
Donn Washburn wrote:
Hey Group;
In the past I had a phoneline connection that worked great (except buffering) with a VoIP HAM related program called echoLinux and echogui. As a matter of fact I used to talk on the 442.150 repeater in Austin form Sugar Land.
Trouble is when we got a adsl line from Altell and a DSL Speed Stream 5200 router it ended. Our router has a DHCP IP# that is stable and all boxes on the LAN have 192.168.1.#
If I call uup echogui it goes out and comes back with a list of stations available. Thats when the problem starts - I never connect with a out station.
I think it is a port forwarding problem - to which I have setup on the DSL router tcp, port number (as shown in /etc/services), my IP# (192.168.1.#) and the rebooted it. No luck!
Anyone have a clue or know of a way to track the problem.
See if it works without the router.
Donn Washburn wrote:
Hey Group;
In the past I had a phoneline connection that worked great (except buffering) with a VoIP HAM related program called echoLinux and echogui. As a matter of fact I used to talk on the 442.150 repeater in Austin form Sugar Land.
Trouble is when we got a adsl line from Altell and a DSL Speed Stream 5200 router it ended. Our router has a DHCP IP# that is stable and all boxes on the LAN have 192.168.1.#
If I call uup echogui it goes out and comes back with a list of stations available. Thats when the problem starts - I never connect with a out station.
I think it is a port forwarding problem - to which I have setup on the DSL router tcp, port number (as shown in /etc/services), my IP# (192.168.1.#) and the rebooted it. No luck!
Anyone have a clue or know of a way to track the problem.
The router needs to have UDP ports 5198 and 5199 enabled for (passed through) to the box running echolinux. I don't know what your router setup looks like as I'm using BBIagent as my router between my cable modem and internal network. BTW, I used echolinux/echogui for a few years, then switched to svxlink where the qtel prog does the same thing, but I like it better. For svxlink, you need to build libgsm, the gsm lib in SuSE is a homegrown version that's incompatible with the GNU version used by everyone else. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux for all Computing Tasks
participants (3)
-
Donn Washburn
-
James Knott
-
Sid Boyce