[App_rpt-users] Allstar connecting to Echolink?

[Kevin Oleniczak]

Thanks to those that responded... i had waited several hours/days without
the node appearing active and do not have a second client running
simultaneously within my network. The later responses indicated the search
for my node failed to find a match, but that was because the wrong callsign
was used. See below.

cruiser*CLI> echolink dbget c N9JPG-L
960818|N9JPG-L|71.194.253.53

>> Below that is my echolink.conf file for reference. Note the servers
listed - 1,5,3.
I used these in my conf file as it noticed that was what my echolink client
was using.

server1=nawest.echolink.org
server2=nasouth.echolink.org
server3=servers.echolink.org

>>Make sure you point the echolink ports in your router to your allstar
server and as was mentioned you can only run one echolink node per public
IP address.

As noted earlier, that is all set as suggested on the howto page for
allstar to do echolink.

Any other ideas?


On Sun, Mar 2, 2014 at 6:00 PM, Kevin Oleniczak <n9jpg.ham at gmail.com> wrote:

> Does anyone know if this should work still? I can't seem to be able to get
> my allstar node to register on the echolink system as active. Everything
> works when i use the echlink app and the firewall settings are in place.
> Callsign is N9JPG-L.
>
> thanks
>
> [Mar  1 19:20:00] WARNING[539]: chan_iax2.c:10127 iax2_do_register:
> REGISTER-LOG: Sending registration request for '28970'
> [Mar  1 19:20:00] WARNING[541]: chan_iax2.c:7690 registry_rerequest:
> REGISTER-LOG: registry rereqquest
>     -- Received OK from Echolink server nawest.echolink.org
>     -- Directory pgm done downloading(partial,
> compressed), 647 records
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20140303/8e1dfed2/attachment.html>