ASL-Corp members, Bureaucrats, Check users, Structured Discussions bots, oversight, Suppressors, Administrators, Upload Wizard campaign editors
1,714
edits
Changes
Jump to navigation
Jump to search
Line 90:
Line 90: + + + + + + +
Added Miscellaneous section that contains two pieces of advice regarding trying to run the EchoLink app (mobile and Windows) on the same network as your AllStar node.
| Query EchoLink station by ip address || echolink dbget ip <EchoLink node ip address>
| Query EchoLink station by ip address || echolink dbget ip <EchoLink node ip address>
|}
|}
=Miscellaneous=
When debugging EchoLink connectivity issues with your AllStar node, remember the following:
*Never run the EchoLink application from your mobile device (cell phone/tablet/etc) using the '''same network''' as your AllStar node. This will lead to problems with one or the other not being able to connect/register/use to the EchoLink servers or other EchoLink nodes. (This also applies to running the Windows application on the same network as your AllStar node).
*If running the EchoLink application on your mobile device (cell phone/tablet/etc), make sure that the EchoLink application is '''not set to run/is not running in the background'''. Having the application running in the background can cause problems with your AllStar node not being able to connect/register/use to the EchoLink servers or other EchoLink nodes.
<pre>
Note: Same network refers to the the Public IP address that both your AllStar node AND the device running the EchoLink application are using -- even if they are on different subnets internally. The Public IP is what the EchoLink servers/network sees and uses when communicating with your node/device.
</pre>
[[Category:Node Configuration]]
[[Category:Node Configuration]]