Just setup a new node (42928) using DIAL on a RPi which is registering on
both the Allstar and Echolink (518309) sites, showing up as valid on all
lists. The repeater works fine with radio calls, and incoming Allstarlink
node connections, but not from Echolink. CLI> indicates successful reception
from the Echolink servers... no errors or warnings of any type in CLI>. The
node just does not see any incoming contacts from Echolink. Any ideas?
By the way, simpleusb has way too much audio delay... hear whole words after
unkeying. Whereas it's not as noticable using usbradio.
Outside the obvious...
..One connection per Internet IP
..Proper port forwarding for udp 5198 & 5199 (if you are on a dhcp, your ip may
have changed)
..changing echolink servers in set-up
I wouldn't have a clue
...mike/kb8jnm
···
Just setup a new node (42928) using DIAL on a RPi which is registering on
both the Allstar and Echolink (518309) sites, showing up as valid on all
lists. The repeater works fine with radio calls, and incoming Allstarlink
node connections, but not from Echolink. CLI> indicates successful reception
from the Echolink servers... no errors or warnings of any type in CLI>. The
node just does not see any incoming contacts from Echolink. Any ideas?
By the way, simpleusb has way too much audio delay... hear whole words after
unkeying. Whereas it's not as noticable using usbradio.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the
bottom of the page. Enter your email address and press the "Unsubscribe or edit
options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If
you have trouble unsubscribing, please send a message to the list detailing the
problem.
EchoLink requires that your router or firewall allow inbound and
outbound UDP to ports 5198 and 5199, and outbound TCP to port
5200.� If you are using a home-network router, you will also
need to configure the router to “forward” UDP ports 5198 and
5199 to the PC on which EchoLink is running.**
This can be summarized as:
Allow UDP destination ports 5198-5199 between
Internet and PC in both directions
Allow TCP (source port any, destination port 5200) from PC to
Internet"
On 01/03/2016 03:36 PM,
wrote:
Outside the obvious...
..One connection per Internet IP
..Proper port forwarding for udp 5198 & 5199 (if you are on a dhcp, your ip may
have changed)
..changing echolink servers in set-up
I wouldn't have a clue ;)
...mike/kb8jnm
Just setup a new node (42928) using DIAL on a RPi which is registering on
both the Allstar and Echolink (518309) sites, showing up as valid on all
lists. The repeater works fine with radio calls, and incoming Allstarlink
node connections, but not from Echolink. CLI> indicates successful reception
from the Echolink servers... no errors or warnings of any type in CLI>. The
node just does not see any incoming contacts from Echolink. Any ideas?
By the way, simpleusb has way too much audio delay... hear whole words after
unkeying. Whereas it's not as noticable using usbradio.
Thanks,
Bob
kk6ecm
_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit
and scroll down to the
bottom of the page. Enter your email address and press the "Unsubscribe or edit
options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If
you have trouble unsubscribing, please send a message to the list detailing the
problem.
_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
That red glow you see in the west this evening is not the setting sun, but
the radiation from my red face... ugh!... I moved every piece of the setup
but the UDP addresses last week, and forgot I still needed to take care of
that one little detail. (sigh!)
Thanks much,
Bob
kk6ecm
"I get by with a little help from my friends." (Yup, I'm that old
···
-----Original Message-----
From: app_rpt-users-bounces@ohnosec.org
[mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of mike@midnighteng.com
Sent: Sunday, January 03, 2016 3:36 PM
To: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] Echolink Connection Issue
Outside the obvious...
..One connection per Internet IP
..Proper port forwarding for udp 5198 & 5199 (if you are on a dhcp, your ip
may
have changed)
..changing echolink servers in set-up
I wouldn't have a clue
...mike/kb8jnm
Just setup a new node (42928) using DIAL on a RPi which is registering on
both the Allstar and Echolink (518309) sites, showing up as valid on all
lists. The repeater works fine with radio calls, and incoming Allstarlink
node connections, but not from Echolink. CLI> indicates successful
reception
from the Echolink servers... no errors or warnings of any type in CLI>.
The
node just does not see any incoming contacts from Echolink. Any ideas?
By the way, simpleusb has way too much audio delay... hear whole words
after
unkeying. Whereas it's not as noticable using usbradio.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to
the bottom of the page. Enter your email address and press the "Unsubscribe
or edit options button"
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a message to
the list detailing the problem.
