<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Do to the fact that some may have issues while others may not,<br>
</p>
<p>It should be considered that the DNS/routing issues as handled
(and sometimes interrupted) by the ISP can also be a issue.</p>
<p>So, I might suggest when seeking help with echolink network
issues, provide some additional data like DNS and ISP and perhaps
we might see a link.</p>
<p>...mike/kb8jnm<br>
</p>
<br>
<div class="moz-cite-prefix">On 7/20/2018 4:20 PM, Michael Wolthuis
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DM5PR22MB0569DE0E89ABF5EAFEE8364CF7510@DM5PR22MB0569.namprd22.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal">John,<o:p></o:p></p>
<p class="MsoNormal">I have had all kinds of issues with
Echolink’s nameservers in the last several weeks. I used to
use server1, server2, server3, server4. However, Server2 and
Server 3 have same IP address now. Not sur about all yours
below, I didn’t look them up. However, I am having this issue
on items that are regular Echolink as well – especially if
coming from an AMPRNet IP address on the 44.x.x.x network.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It's time we all got together and built a
user app around Allstar that can replace the Echolink client
if you ask me.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Wish I had a solution, but I haven’t found
a good one yet.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mike<o:p></o:p></p>
<p class="MsoNormal">Kb8zgl<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:12.0pt;color:black">From: </span></b><span
style="font-size:12.0pt;color:black">App_rpt-users
<a class="moz-txt-link-rfc2396E" href="mailto:app_rpt-users-bounces@lists.allstarlink.org"><app_rpt-users-bounces@lists.allstarlink.org></a> on
behalf of John Rudolph- N2YP <a class="moz-txt-link-rfc2396E" href="mailto:John@n2yp.com"><John@n2yp.com></a><br>
<b>Reply-To: </b>Users of Asterisk app_rpt
<a class="moz-txt-link-rfc2396E" href="mailto:app_rpt-users@lists.allstarlink.org"><app_rpt-users@lists.allstarlink.org></a><br>
<b>Date: </b>Friday, July 20, 2018 at 4:11 PM<br>
<b>To: </b><a class="moz-txt-link-rfc2396E" href="mailto:app_rpt-users@lists.allstarlink.org">"app_rpt-users@lists.allstarlink.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:app_rpt-users@lists.allstarlink.org"><app_rpt-users@lists.allstarlink.org></a><br>
<b>Subject: </b>Re: [App_rpt-users] Echolink timeout<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">I've tried pinging them all includeding
echolink.org from my node server, my cellphone via WiFi, my
cell via Verizon, my laptop and all my pings come back as
10,000+ ms pings or completely lost packets. I'm guessing this
is causing the issue. If I use a website to do the ping it
goes quick which I find interesting since I've tried it on two
different networks, Spectrum-Time Warner and Verizon. Does
anyone else this problem when trying to ping echolink? Is it
possible it's a regional issue?
<br>
<br>
I've tried echolink.org, naeast.echolink. org,
nasouth.echolink.org, servers.echolink.org, aprs.echolink.org.
<br>
John Rudolph<br>
Amateur Radio Op N2YP<br>
Unadilla,NY<br>
<br>
<o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
App_rpt-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:App_rpt-users@lists.allstarlink.org">App_rpt-users@lists.allstarlink.org</a>
<a class="moz-txt-link-freetext" href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a>
To unsubscribe from this list please visit <a class="moz-txt-link-freetext" href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a> 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. </pre>
</blockquote>
<br>
</body>
</html>