[arm-allstar] Echolink Still Not Working....

[John]

Happy to report significant progress and share some information with the
group. It appears that at least some of the problems I've had with node
configuration are the result of extraneous characters being introduced into
files I've edited on my node. I think it may be due to the Zterm program I
was using occasionally to edit files via USB/serial communication with my
node. I had noticed a few random characters on the screen while editing,
but apparently some of those characters were being written to the
files.When I replaced iax.conf, rpt.conf and other .conf files with example
files and then edited those files using using Putty and Nano - my problems
started to disappear - at least then I began to get error messages that
made some sense and allowed me to find other problems I had created. There
are still some rough edges to smooth out, but finally today I've made
significant progress. Many thanks to Doug, David, TJ and others for their
help in troubleshooting.

John

On Wed, Aug 27, 2014 at 7:59 PM, John <wb5nfc at gmail.com> wrote:

> I thought I had all of the gremlins slain when I got a VPN working on my
> node. It appears that is not the case. Two different stations tried to
> connect to my node tonight via Echolink. Neither was successful. My node is
> listed on Echolink as an active station as well as on Allstar as an active
> node. How do I begin to troubleshoot this problem? I'm utilizing AT&T on an
> iPhone hotspot with a Cradlepoint router. When logged in on the BBB, I can
> ping Echolink servers. What am I missing???
>
>
> John
>



-- 
John Kenney
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20140907/58e9d321/attachment.html>