[arm-allstar] echolink not starting

[LaRoy McCann]

Doug,
The noload command is commented out.  Just seems strange.

Since there have been fixes in V1.5, I will upgrade in the next day or 
so and see how that goes.
I have been wanting to upgrade  but just have not got around to doing it 
yet.

Thanks.

On 7/13/2017 12:20 PM, "Doug Crompton via arm-allstar" wrote:
> LaRoy,
>
>   First of all there were significant Echolink module fixes in V1.5. I would
> recommend upgrading. I am not sure why it is not loading at boot or
> restart. Are you sure you have the Echolink module loading (not commented)
> in /etc/asterisk/modules.conf ?
>
> If it loads without errors when you do it manually it should also when
> booting or restarting. Also as long a three servers are defined it does not
> matter if one or more are offline. It will still run. You will see an error
> about it in the client or log that can be ignored.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
> On Thu, Jul 13, 2017 at 1:04 PM, "LaRoy McCann via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> I have been having issues with my echolink node not connecting and did
>> some troubleshooting.
>>
>> I have this error in /var/log/asterisk/messages.
>> /[Jul 13 10:13:37] ERROR[251] chan_echolink.c: Unable to resolve echolink
>> APRS server IP address//
>> /
>> I can do a ping of the servers that I have in the config file and they all
>> resolve, they do not ping but they resolve.
>> I'm using
>> server1=server1.echolink.org
>> server2=server2.echolink.org
>> server3=server5.echolink.org
>>
>> I tried reloading the echolink module and got this
>> /k5tw-hub*CLI> module reload chan_echolink.so//
>> //[Jul 13 10:16:04] NOTICE[799]: loader.c:580 ast_module_reload: The
>> module 'chan_echolink.so' was not properly initialized.  Before reloading
>> the module, you must run "module load chan_echolink.so" and fix whatever is
>> preventing the module from being initialized.//
>> //k5tw-hub*CLI>
>>
>> /I then loaded the module.
>> /k5tw-hub*CLI> module load chan_echolink.so//
>> //  == Registered channel type 'echolink' (Echolink channel driver)
>> /
>> Now it works.
>>
>> I am still running 1.02beta on this node and I know I need to upgrade but
>> just have not done it yet.
>>
>> Has anyone seen this behavior before?
>>
>> LaRoy K5TW
>> /
>> /
>>
>>
>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> https://www.avast.com/antivirus
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>
>>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>