Home |
Search |
Today's Posts |
#1
![]() |
|||
|
|||
![]()
I am trying to help a friend get started on Echolink. He uses AT&T as a
dialup provider. Does AT&T support the protocols required to make Echolink work? Thanks ----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==---- http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups ----= East and West-Coast Server Farms - Total Privacy via Encryption =---- |
#2
![]() |
|||
|
|||
![]()
EchoLink requires that your router or firewall allow inbound and
outbound UDP to destination ports 5198 and 5199, and outbound TCP to port 5200. Source ports are dynamically assigned. 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. See http://www.echolink.org/firewall_solutions.htm On Wed, 17 Aug 2005 16:15:52 -0700, "tubeham" wrote: I am trying to help a friend get started on Echolink. He uses AT&T as a dialup provider. Does AT&T support the protocols required to make Echolink work? Thanks |
#3
![]() |
|||
|
|||
![]()
If you're having trouble getting EchoLink to work correctly, the
EchoLink Troubleshooter utility may help. The Troubleshooter helps solve the two most common problems that new EchoLink users might encounter. See http://www.echolink.org/troubleshooter.htm On Wed, 17 Aug 2005 16:15:52 -0700, "tubeham" wrote: I am trying to help a friend get started on Echolink. He uses AT&T as a dialup provider. Does AT&T support the protocols required to make Echolink work? Thanks |
#4
![]() |
|||
|
|||
![]()
Echolink worked perfectly with standard setup for me on AT&T dialup.
Alan WA4SCA |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
BPL in California | Policy | |||
competition coil antennas | CB |