The node looks good here - grep 27086 /tmp/rpt_extnodes 27086=radio@72.224.76.51:4569/27086,72.224.76.51 If you are running Acid on a PC then grep 27086 /var/lib/asterisk/rpt_extnodes 27086=radio@72.224.76.51:4569/27086,72.224.76.51 Sometimes you have to reboot or restart. Are you registered? CLI>iax2 show registry What is the failure? No response or an actual failure voice message? Also any CLI messages? 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Fri, 12 Sep 2014 11:36:47 -0400 From: N1XBM@amsat.org To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] Connection failed So the power was cut to the building my repeater is in. My repeater functions, I'm able to connect via IAX. I'm also able to SSH in and ping the IP of the node I'm trying to connect too (27066) I'm also able to ping google.com. but when I go to the CLI and type rpt fun 27086 *327066 it fails. So what gives? I'm running acid and a DMK URI. _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.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.

Sometimes it takes like 30 minutes before all nodes get updated. Or maybe longer? Maybe someone can provide clarification on this and if there is a way to force an update to a node that has not yet received the latest ip? Also going static does help as well on the wan side. Lu Vencl

On Sep 12, 2014, at 11:36 AM, Robert Newberry <N1XBM@amsat.org> wrote:

So the power was cut to the building my repeater is in. My repeater functions, I'm able to connect via IAX. I'm also able to SSH in and ping the IP of the node I'm trying to connect too (27066) I'm also able to ping google.com. but when I go to the CLI and type rpt fun 27086 *327066 it fails.

So what gives?

I'm running acid and a DMK URI.

_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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 09/12/2014 10:36 AM, Robert Newberry wrote:

So the power was cut to the building my repeater is in. My repeater functions, I'm able to connect via IAX. I'm also able to SSH in and ping the IP of the node I'm trying to connect too (27066) I'm also able to ping google.com <http://google.com>. but when I go to the CLI and type rpt fun 27086 *327066 it fails.

So what gives?

I'm running acid and a DMK URI.

Do you have access to the firewall on the router? If it were me, I think I'd first find out who/what/where/when I was getting an IP address from (since the building's power was cut, it stands to reason that perhaps the IT guy plugged in the router/switch to a non-emergency line (like your repeater is plugged into) and if you're on wifi, no telling WHERE that thing might be connected. I'm thinking that you're probably connected to another system that doesn't have the port forwarded in the firewall to allow incoming connections. Why it's not allowing -outgoing- connections, well... that's a horse of a different corral. Soooo... Your machine, right? You have control codes, right? Does the repeater respond to radio DTMF controls? how about from the command prompt? Let's first verify this is going to work. Some ssh terminal programs have problems. So, going on the assumption you do not have physical access to that machine, let's first SSH into it: local_system:#~> ssh -p222 root@ip.address.to.node the wait for the password prompt and enter it correctly. Once you're in, let's see who we're connected to, without going through the command line. [root@[your_call] /] asterisk -rx "rpt nodes 27086" and observe the output. then try [root@[your_call] /]# asterisk -rx "rpt fun 27086 *327066" Anything?