Re: [App_rpt-users] App_rpt-users Digest, Vol 47, Issue 15
Matt, should it not be "*3494492. EchoLink is padded to 6 digits. You had two 3's Chris kc%izr On Fri, Jan 11, 2013 at 10:00 AM, <app_rpt-users-request@ohnosec.org> wrote:
Send App_rpt-users mailing list submissions to app_rpt-users@ohnosec.org
To subscribe or unsubscribe via the World Wide Web, visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users or, via email, send a message with subject or body 'help' to app_rpt-users-request@ohnosec.org
You can reach the person managing the list at app_rpt-users-owner@ohnosec.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of App_rpt-users digest..."
Today's Topics:
1. Echolink Connection Issue (Matt Roberts)
----------------------------------------------------------------------
Message: 1 Date: Fri, 11 Jan 2013 11:06:25 -0500 From: Matt Roberts <n9gmr@me.com> To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] Echolink Connection Issue Message-ID: <517ECCE6-B152-4D6B-839E-1C7BBDACCF6D@me.com> Content-Type: text/plain; CHARSET=US-ASCII
I am attempting to connect to Echolink 494492. I enter the command on my repeater, "*33494492." This is the *handiham* conference. The repeater acknowledges the command, and then I get a connection refused message from my repeater. The owner of the conference has tried to connect to my system, and could not do so either. Any other Echolink node I have ever connected to, or has connected to me has been able to do so. My repeater is set as a DMZ host on my router. With this configuration, no port forwarding should be required. I don't know if there is a log file which will allow me to diagnose this problem. I found one, but it was over 100MB in size. That file appeared to not have any useful information in it. I also tried from the CLI, and that didn't give me any information either. Has anyone else experienced this kind of problem? The owner of the conference is saying it's an issue with Allstar, but I don't think so! If it was an Allstar issue, I wouldn't be able to connect to Echolink nodes at all.
Matt Roberts Phone: 386-679-1986 n9gmr@me.com
Sent from my iPhone
------------------------------
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
End of App_rpt-users Digest, Vol 47, Issue 15 *********************************************
ahhh, no.. *3 3 494492 *3 - link 3 - echolink prefix 494492 - echolink node number Jim WB6NIL Date: Fri, 11 Jan 2013 17:16:31 -0700 From: cdeced@gmail.com To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] App_rpt-users Digest, Vol 47, Issue 15 Matt, should it not be "*3494492. EchoLink is padded to 6 digits. You had two 3's Chris kc%izr On Fri, Jan 11, 2013 at 10:00 AM, <app_rpt-users-request@ohnosec.org> wrote: Send App_rpt-users mailing list submissions to app_rpt-users@ohnosec.org To subscribe or unsubscribe via the World Wide Web, visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users or, via email, send a message with subject or body 'help' to app_rpt-users-request@ohnosec.org You can reach the person managing the list at app_rpt-users-owner@ohnosec.org When replying, please edit your Subject line so it is more specific than "Re: Contents of App_rpt-users digest..." Today's Topics: 1. Echolink Connection Issue (Matt Roberts) ---------------------------------------------------------------------- Message: 1 Date: Fri, 11 Jan 2013 11:06:25 -0500 From: Matt Roberts <n9gmr@me.com> To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] Echolink Connection Issue Message-ID: <517ECCE6-B152-4D6B-839E-1C7BBDACCF6D@me.com> Content-Type: text/plain; CHARSET=US-ASCII I am attempting to connect to Echolink 494492. I enter the command on my repeater, "*33494492." This is the *handiham* conference. The repeater acknowledges the command, and then I get a connection refused message from my repeater. The owner of the conference has tried to connect to my system, and could not do so either. Any other Echolink node I have ever connected to, or has connected to me has been able to do so. My repeater is set as a DMZ host on my router. With this configuration, no port forwarding should be required. I don't know if there is a log file which will allow me to diagnose this problem. I found one, but it was over 100MB in size. That file appeared to not have any useful information in it. I also tried from the CLI, and that didn't give me any information either. Has anyone else experienced this kind of problem? The owner of the conference is saying it's an issue with Allstar, but I don't think so! If it was an Allstar issue, I wouldn't be able to connect to Echolink nodes at all. Matt Roberts Phone: 386-679-1986 n9gmr@me.com Sent from my iPhone ------------------------------ _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users End of App_rpt-users Digest, Vol 47, Issue 15 ********************************************* _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
participants (2)
-
Chris Drummond -
Jim Duuuude