Doesn't ASL create the tcp connection for Echolink therefore allowing traffic to reach ASL? This was working fine until recently.. The only question is did something change with my ISP ( Fronteir Fios). From: App_rpt-users <app_rpt-users-bounces@lists.allstarlink.org> On Behalf Of Mike Sent: Saturday, May 26, 2018 12:43 PM To: app_rpt-users@lists.allstarlink.org Subject: Re: [App_rpt-users] Echolink.... Whel, there is more to know about your install and the failed attempts. Where they are and what the failed devices are and what network they might be on. But I will point out if your attempt is from your phone or any device behind your nat, and your NODE is also behind the same nat, it will be refused. Only one echolink connect per ip address (echolink rules). But, don't forget to add tcp port 5200 to your nat forward list. But I will say, in cellphones, after you switch to/from a proxy, it seems to be buggy if you do not first get a update to the nodes list. So do that right after switching type direct/proxy/relay and before you try to connect to anyone. Perhaps is a start... but I don't know enough to your particulars to say more. ...mike/kb8jnm On 5/26/2018 12:30 PM, Steve Siesel wrote: All... I have been having some issues with Echolink lately..First, I do believe my UDP ports 5198 and 5199 are being blocked. As I understand it.This only concerns operations via Smartphone. My Echolink link node K4KSA-L is listed as being on in the Echolink status page. However, when using the desktop client, I do see the following..However the desktop app does not make a connection and times out.. Any thoughts? Steve -- 9 variables -- Channel echolink/el0-1 answering -- Name changed from Steve to Steve Siesel -- Received OK from Echolink server server2.echolink.org -- Received OK from Echolink server server1.echolink.org -- Directory pgm done downloading(partial,compressed), 459 records -- <DAHDI/pseudo-2138142179> Playing 'rpt/node' (language 'en') -- <DAHDI/pseudo-2138142179> Playing 'digits/3' (language 'en') -- <DAHDI/pseudo-2138142179> Playing 'digits/9' (language 'en') -- <DAHDI/pseudo-2138142179> Playing 'digits/5' (language 'en') -- <DAHDI/pseudo-2138142179> Playing 'digits/0' (language 'en') -- Name changed from Steve Siesel to Steve -- <DAHDI/pseudo-2138142179> Playing 'digits/0' (language 'en') -- <DAHDI/pseudo-2138142179> Playing 'digits/7' (language 'en') -- <DAHDI/pseudo-2138142179> Playing 'digits/7' (language 'en') -- <DAHDI/pseudo-2138142179> Playing 'rpt/connected' (language 'en') -- <DAHDI/pseudo-2138142179> Playing 'digits/2' (language 'en') -- <DAHDI/pseudo-2138142179> Playing 'rpt/node' (language 'en') -- <DAHDI/pseudo-2138142179> Playing 'digits/4' (language 'en') -- Name changed from Steve to Steve Siesel -- <DAHDI/pseudo-2138142179> Playing 'digits/6' (language 'en') -- <DAHDI/pseudo-2138142179> Playing 'digits/0' (language 'en') -- Name changed from Steve Siesel to Steve -- <DAHDI/pseudo-2138142179> Playing 'digits/3' (language 'en') -- <DAHDI/pseudo-2138142179> Playing 'digits/1' (language 'en') Node Variable dump for node 46031: RPT_TXKEYED=0 RPT_ETXKEYED=1 RPT_NUMLINKS=2 RPT_LINKS=2,T1999,T3950077 RPT_NUMALINKS=2 RPT_ALINKS=2,1999TU,3950077TU RPT_AUTOPATCHUP=0 RPT_RXKEYED=0 TRANSFERCAPABILITY=SPEECH -- 9 variables Node Variable dump for node 46031: RPT_ETXKEYED=0 RPT_TXKEYED=0 RPT_NUMLINKS=2 RPT_LINKS=2,T1999,T3950077 RPT_NUMALINKS=2 RPT_ALINKS=2,1999TU,3950077TU RPT_AUTOPATCHUP=0 RPT_RXKEYED=0 TRANSFERCAPABILITY=SPEECH -- 9 variables -- Hungup 'DAHDI/pseudo-2138142179' -- Name changed from Steve to Steve Siesel -- Name changed from Steve Siesel to Steve -- Name changed from Steve to Steve Siesel [May 26 12:25:38] WARNING[2694]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '46031' [May 26 12:25:38] WARNING[2693]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org <mailto:App_rpt-users@lists.allstarlink.org> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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.

On 05/26/2018 11:36 AM, Mike wrote:

ASL does not 'try' to do anything but emulate a echolink port in attachment to a ASL node..

Can it (tcp 5200) forward though the NAT ?  ASL will not do that for you. It will take it if it can get there.

It should be in the norm with your udp 5198 5199 forwards.

And there can't be some other device with echolink on the same side of the nat.

So switching your phone to use cell data is a must unless you have more than 1 ip at home./site

It might appear that it can be done, but I suggest not correctly for both.

...mike/kb8jnm

In addition to what Mike has stated above: Also restart your node/Asterisk, run the following command on the Asterisk console, try to connect and post the output to the mailing list (someone may be able to help you with your problem using this information): echolink debug level 7 (To turn off, echolink debug level 0) This will turn on chan_echolink debugging and may give an indication of what is going wrong. Note that you may have to connect to the Asterisk console using something similar to "asterisk -cvvvvr" to get the output from the echolink debugging command. -Stacy KG7QIN