[arm-allstar] Incoming echolink connections failing

[Phil Visalli]

I've been troubleshooting this issue for a few days now and cant seem to
figure it out, and was wondering if others are having this same issue using
version 1.0 on the Pi2.

I've renamed echlink.xxxx to echolink.conf and edited it to suit my needs.
The permit and deny lines are commented out.  Im able to connect out to
echolink servers (and pass traffic) from my allstar node, but incoming
connections fail.

I have udp ports 5298 and 5199 forwarded to the Pi2 and have confirmed my
port forwards are indeed working.  When there is a connection attempt i see
the following line in /var/log/asterisk/messages:

ERROR[367] chan_echolink.c: Cannot find DB entry for IP addr 192.168.1.1

The client gets the following message:

Cannot connect to KD2IAN-L - UN-AUTHORIZED

I am able to poll the echolink db from cli:

asterisk -rx "echolink dbdump" | grep KD2IAN
336512|KD2IAN|32.138.245.81
356468|KD2IAN-L|74.67.157.29

Can anyone give me a bump in the right direction?  I cant explain why that
error message in messages refers to "192.168.1.1", but im sure that has
something to do with the problem.  Just as a sidenote, I had an original pi
running an echolink node using svxlink running prior to moving over to the
Pi2 and allstar.  i have not run that and my new allstar node at the same
time, but if I turn off my allstar node, fire up the PI, and change my port
forwards to point to that machine I am able to make a successful incoming
connection to it..... so i am 99% sure the network (port forwards, isp
blocking, ect) is not the issue.

Phil V
KD2IAN
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150719/823b9afb/attachment.html>