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.
you need access to your router and or firewall, and set up PORT forwarding read more here: http://www.echolink.org/firewall_solutions.htm Best Regards, Chris Carruba Co-Admin irc.spidernet.org http://www.spidernet.org CompuTec Data Systems Custom Written Software, Networking, Forensic Data Recovery ________________________________ From: Wesley Bazell <wesley...@verizon.net> To: Repeater-Builder@yahoogroups.com Sent: Sunday, April 5, 2009 1:39:55 PM Subject: Re: [Repeater-Builder] Re: Awfully quiet today Thanks Anyway Nate. This is an Weslell 6100 Modem ----- Original Message ----- From: Nate Duehr To: Repeater-Builder@ yahoogroups. com Sent: Sunday, April 05, 2009 2:31 PM Subject: Re: [Repeater-Builder] Re: Awfully quiet today On Apr 5, 2009, at 12:11 PM, Wesley Bazell wrote: > Hi Nate > > Have you any experiance on Echolink, opening Ports 5198,5199 with > verizon.net? Have not been sucessful in doing this. I realize this > may be off Topic. > > Wesley AB8KD Not Verizon specifically, they're (mostly) not a carrier for anything other than cellular and wireline IP for big business out here in Colorado. We're "Qwest country", for better or for worse... on residential service. Haven't seen any complaints from the EchoIRLP mailing list on YahooGroups about Verizon specifically though... AFAIK they're not blocking anything, the router just has to be told what to route to whatever internal IP address you're using... I could be wrong... might be worth asking on a more VoIP linking focused mailing list like that one, or whatever lists Echolink has going. (I don't know on that one... I only do EchoIRLP and use the Windows EchoLink client from time to time, or EchoMac...) -- Nate Duehr, WY0X n...@natetech. com
