<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><br><div id="AppleMailSignature" dir="ltr">Sent using SMTP.</div><div dir="ltr"><br>On Mar 16, 2019, at 9:22 PM, Bob Pyke <<a href="mailto:k6ecm1@gmail.com">k6ecm1@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="content-type" content="text/html; charset=utf-8">All connections are peer-to-peer. This is facilitated by an Allstarlink server sending a file to each computer hosting a node or nodes a list of all registered nodes ( read that as identifying number), an IP address, and a UDP port number (bindport=xxxx in iax.conf).<div><br></div><div>When a connection (link) takes place, the host computer uses the information in the app_rpt config files associated with each node (number) to process communications and control of the repeater, or what ever you are controlling. EchoLink, SIP, and iax are supported. IRLP is not.<br></div></div></blockquote><div><br></div><div>IRLP not supported? What happened to chan_irlp? Here’s a mailing list reference to it from Steve Rodgers:</div><div><br></div><div><a href="http://lists.allstarlink.org/pipermail/app_rpt-users/2009-May/001016.html">http://lists.allstarlink.org/pipermail/app_rpt-users/2009-May/001016.html</a></div><div><br></div><div><br></div><br><blockquote type="cite"><div dir="ltr"><div><br><div id="AppleMailSignature" dir="ltr"><div><span style="background-color: rgba(255, 255, 255, 0);">Thanks,</span><div><span style="background-color: rgba(255, 255, 255, 0);">Bob</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">K6ECM</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Sent from iPad</span><div></div></div></div><div><br></div></div><div dir="ltr"><br>On Mar 16, 2019, at 8:53 PM, Eric Fort <<a href="mailto:eric.fort.listmail@fortconsulting.org">eric.fort.listmail@fortconsulting.org</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div dir="ltr"><span></span></div><div dir="ltr">Ok so after reading some more of the responses maybe I need to differentiate between a node and node number. A node (or possibly node number, I’m not sure at this point) had been described as an internet connection identifier. We have hardware, a computer of some sort running Linux with appropriate hardware interfaces to allow radio interfacing, and some software that I thought was asterisk and app_rpt and this manages a bunch of channels that can be interconnected in various ways. A computer can apparently run one or more nodes and or at least have multiple node numbers assigned to it. Now let’s say I have a computer with 5 radios attached (say 2 repeaters, 2 link radios, a frequency agile remote base radio), along with channels for echolink, IRLP, sip, iax, pots, etc. when I connect to this “node” er dial a node number what do I connect to? Maybe some of the confusion here is use of proper nomenclature. Is a node and node number one in the same? Does it have to be? When I dial a node number what actually happens under the hood? How does the node number get translated and routed to where it needs to go and whatever one is requesting a connection to? Is an allstar node number handled as an extension on the computer/PBX/er node ( what’s the proper wording here?) via extensions.conf? Maybe some examples of how people are implementing setups that have more than a single radio (maybe an Hf remote base like an ft-897, a repeater, connections to echolink, irlp, iax, sip, dstar, dmr, pots, etc) are being done. These at least at one time were simply channel drivers and handled in extensions.conf as to how things happened. Has this changed? What and how are node numbers handled under the hood?</div><div dir="ltr"><br></div><div dir="ltr">Thanks,</div><div dir="ltr"><br></div><div dir="ltr">Eric</div><div dir="ltr">Af6ep <br><br><div id="AppleMailSignature" dir="ltr">Sent using SMTP.</div><div dir="ltr"><br>On Mar 16, 2019, at 3:12 AM, Bob Pyke <<a href="mailto:k6ecm1@gmail.com">k6ecm1@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="content-type" content="text/html; charset=utf-8">A node is an internet connection identifier (a number). It has no more than one public IP associated with it, but one public IP number can have multiple node numbers when using port forwarding in a NAT router. <span style="background-color: rgba(255, 255, 255, 0);">Node numbers for public access are assigned by Allstarlink, whereas a private node is unassigned, and must be numerically less than 2000 and not registered in AllstarLink by the node</span> <div><br></div><div>A node can have no radio (known as a hub and other nodes can connect (link) to it over the internet as a central connection point), or one radio (a repeater). Since private nodes are not registered, a connecting node at a different IP address must be told (hard coded in its config file), how to locate it. A node can have SIP access (a hub or repeater), as in using an internet connected VoIP phone to control (using <span style="background-color: rgba(255, 255, 255, 0);">DTMF</span> commands) or use the node to connect to and interface with other nodes by linking them together using DTMF commands (ie from a iPhone using Zoiper, or iaxRpt on an android phone or computer that is internet connected).</div><div><br></div><div>I do not recognize your port types, but AllstarLink software is designed to interface with specific interface hardware such as the DMk engineering URIx, or any number of modified USB audio interfaces based on the CM119 chip family.</div><div><br></div><div>See <a href="https://wiki.allstarlink.org/wiki/Main_Page">https://wiki.allstarlink.org/wiki/Main_Page</a><br><div><br></div><div>Hope this helps.</div><div><br><div id="AppleMailSignature" dir="ltr"><div><span style="background-color: rgba(255, 255, 255, 0);">Thanks,</span><div><span style="background-color: rgba(255, 255, 255, 0);">Bob</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">K6ECM</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Sent from iPad</span><div></div></div></div><div><br></div></div><div dir="ltr"><br>On Mar 16, 2019, at 12:24 AM, Eric Fort <<a href="mailto:eric.fort.listmail@fortconsulting.org">eric.fort.listmail@fortconsulting.org</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><span>Could someone help me get a better idea of the concept of what a node is in asterisk/app_rpt/all star terminology. I have a computer with 4 radio ports, an fxo port, an fxs port, and an Internet connection which allows connection to any number of endpoints over sip or iax. Now what is a node? I’d like to be able via DTMF to bring one or more radios on and off link. Some of my understanding that needs to happen here is how AllStarLink is architected but also relating concepts to what I know and am familiar with which is a network of linked remotes (anyone here a cactus member or at least familiar with how a srs controller is architected as an 8x8 full duplex audio switch matrix. ) where a remote may have up to 8 radios and each of those can be linked or unlinked individually to any one or more of the other 8. Finally, how does AllStarLink prevent loops in routing? I know this seems odd at first glance but I can easily foresee audio from one source being linked to multiple places and those sources being mixed and linked back in a twisted mess. Please help me to understand</span><br><span></span><br><span>Af6ep</span><br><span></span><br><span>Sent using SMTP.</span><br><span>_______________________________________________</span><br><span>App_rpt-users mailing list</span><br><span><a href="mailto:App_rpt-users@lists.allstarlink.org">App_rpt-users@lists.allstarlink.org</a></span><br><span><a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a></span><br><span></span><br><span>To unsubscribe from this list please visit <a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"</span><br><span>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. </span><br></div></blockquote></div></div></div></blockquote><blockquote type="cite"><div dir="ltr"><span>_______________________________________________</span><br><span>App_rpt-users mailing list</span><br><span><a href="mailto:App_rpt-users@lists.allstarlink.org">App_rpt-users@lists.allstarlink.org</a></span><br><span><a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a></span><br><span></span><br><span>To unsubscribe from this list please visit <a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"</span><br><span>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. </span><br></div></blockquote></div></div></blockquote><blockquote type="cite"><div dir="ltr"><span>_______________________________________________</span><br><span>App_rpt-users mailing list</span><br><span><a href="mailto:App_rpt-users@lists.allstarlink.org">App_rpt-users@lists.allstarlink.org</a></span><br><span><a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a></span><br><span></span><br><span>To unsubscribe from this list please visit <a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"</span><br><span>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. </span><br></div></blockquote></div></div></blockquote><blockquote type="cite"><div dir="ltr"><span>_______________________________________________</span><br><span>App_rpt-users mailing list</span><br><span><a href="mailto:App_rpt-users@lists.allstarlink.org">App_rpt-users@lists.allstarlink.org</a></span><br><span><a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a></span><br><span></span><br><span>To unsubscribe from this list please visit <a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"</span><br><span>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. </span><br></div></blockquote></body></html>