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
Check your echolink.conf file and see if you have: confmode=no That is telling Asterisk that connections to conferences is prohibited. 73 Ken
-----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users- bounces@ohnosec.org] On Behalf Of Matt Roberts Sent: Friday, January 11, 2013 11:06 AM To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] Echolink Connection Issue
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
I do have that. Should I change it to "yes?" Matt Roberts Phone: 386-679-1986 n9gmr@me.com Sent from my iPhone On Jan 11, 2013, at 5:22 PM, Ken <ke2n@cs.com> wrote:
Check your echolink.conf file and see if you have:
confmode=no
That is telling Asterisk that connections to conferences is prohibited.
73
Ken
-----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users- bounces@ohnosec.org] On Behalf Of Matt Roberts Sent: Friday, January 11, 2013 11:06 AM To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] Echolink Connection Issue
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
That would be a good guess. Actually - looking at my systems, the actual *use* of this variable is only a fairly recent development. If your ACID version is a bit old, it does not matter what you set it to ... I am guessing yours is fairly new, so it will just hang up on you if you try to link to a conference and this is set to "no". 73 Ken
-----Original Message----- From: Matt Roberts [mailto:n9gmr@me.com] Sent: Friday, January 11, 2013 5:38 PM To: Ken Cc: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Echolink Connection Issue
I do have that. Should I change it to "yes?"
Matt Roberts Phone: 386-679-1986 n9gmr@me.com
Sent from my iPhone
On Jan 11, 2013, at 5:22 PM, Ken <ke2n@cs.com> wrote:
Check your echolink.conf file and see if you have:
confmode=no
That is telling Asterisk that connections to conferences is prohibited.
73
Ken
-----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users- bounces@ohnosec.org] On Behalf Of Matt Roberts Sent: Friday, January 11, 2013 11:06 AM To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] Echolink Connection Issue
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
I just tried connecting to it. The first time it would not connect, so I tried it again and it connected right away. Sounds like they have a net going on right now... Corey N3FE -----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Ken Sent: Friday, January 11, 2013 5:22 PM To: 'Matt Roberts'; app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Echolink Connection Issue Check your echolink.conf file and see if you have: confmode=no That is telling Asterisk that connections to conferences is prohibited. 73 Ken
-----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users- bounces@ohnosec.org] On Behalf Of Matt Roberts Sent: Friday, January 11, 2013 11:06 AM To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] Echolink Connection Issue
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
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users -- This message was scanned and is believed to be clean. Click here to report this message as spam. http://simba.repeater.net/cgi-bin/learn-msg.cgi?id=191AA221F.AA135
participants (3)
-
Corey Dean -
Ken -
Matt Roberts