you might want to include it in your extension.config under radio-secure if you still want connections to it. ...mike/kb8jnm On 07/22/2018 03:10 PM, Jim Aspinwall No1PC wrote:
Good news - some struggle over. I just built two fresh ASL nodes, updated, upgraded - private for now.
Now I want one of my working ASL/public nodes to also be accessible as a private node.
I assume for both the existing public node and new separate private node all I need to do is...
In /etc/asterisk/rpt.conf on the existing node, add lines:
[nodes]
; 1085 is the new/added private node number for existing public node 1085 = radio@127.0.0.1/1085,NONE,y ; 1002 is the new private node 1002 = radio@192.168.10.96/1002,NONE,y
In /etc/asterisk/rpt.conf on the new private node (same network), add lines:
[nodes]
; 1085 is the new/added private node number for existing public node on same LAN 1085 = radio@192.168.10.76/1085,NONE,y
; 1002 is this new private node 192.168.10.96 on LAN) 1002 = radio@127.0.0.1/1002,NONE,y
What if any additional context/extension or other parameters need to be setup in which file??
What else do the nodes need to know about each other to communicate and establish connection?
What am I missing?
I should be able to issue a connect from 1002 to 1085, and vice versa - yes?
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.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.