The Remote UNIX Connection is you or some process connecting and disconnecting to the running asterisk process.  (asterisk -rc)

Make sure you remove or rename the echolink.conf file on the node it used to be on.  Also, try rebooting both nodes.

Try connecting to the asterisk process using a lot of v's on the command line --- asterisk -cvvvvvvvvvvvvvvvvr will work. You can also use "set verbose 15" to turn it on too.

This will give you a lot of text on the terminal.  Look for messages from chan_echolink.

You can also issue an "echolink debug level 7" command from the terminal as well.  This should give you quite a bit of info from chan_echolink


Stacy
KG7QIN



On 10/27/2015 08:03 PM, Jamey Wright wrote:

Is there a way to troubleshoot Echolink?  I had echolink connected to one of my nodes but decided to move it to another one for technical reasons.  Each node has its’ own public IP.  I configured all of the ports as they should be in my firewall but after ½ an hour or more, it has not shown back up in the list at echolink.   Watching the Asterisk CLI, I see  a lot of the following:

-- Remote UNIX connection

-- Remote UNIX connection disconnected   

 

Thanks

 

Jamey

WR4JW



_______________________________________________
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.