[arm-allstar] Echolink module fix

[David McGough]

Hi Max,

Many thanks for the positive feedback, and I'm glad echolink is now happy!


73, David KB4FXC


On Mon, 30 Jan 2017, "Max via arm-allstar" wrote:

> Hi Doug,
> 
> That is what I discovered after playing with it for a few minutes.  I do
> get the "module chan_echolink.so already exists" message if I try to load
> the Echolink module manually, but I assume it is because it has already
> loaded.
> 
> After completing the upgrade I have rebooted the node several times and
> Echolink becomes functional in about 3 or 4 minutes.  Many thanks for the
> 'fix'.
> 
> Personally, I find it extremely impressive that the two very minor issues
> associated with the upgrade were 'fixed' within scant minutes through the
> built-in update process.  I can't ever remember seeing that kind and level
> of support any other place.  Many, many thanks!
> 
> On Sun, Jan 29, 2017 at 10:44 AM, "Doug Crompton via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
> 
> > Max,
> >
> >   I think what you are seeing (or not seeing) is that it sometimes takes
> > echolink awhile (5-10 minutes) to populate the database.
> >
> > Enter the client and look for the echolink in the command list. If it is
> > there then echolink is loading. Do  'echolink dbdump'  at some point after
> > boot you should see the database.
> >
> > echolink dbdump
> >
> > Do -
> >
> > grep echo /var/log/asterisk/messages | more
> >
> > and view any error messages. Disregard messages like -
> >
> >    [Jan 29 04:45:07] ERROR[2013] chan_echolink.c: connect() failed to
> > connect to the Echolink server server5.echolink.org
> >
> > as not all the servers may be operational.
> >
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Sun, Jan 29, 2017 at 6:59 AM, "Max via arm-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > I'm sorry, but this did not fix the problem.  Also, I cannot load
> > Echolink
> > > from CLI.  when I try to load the chan_echolink.so module from CLI it
> > says
> > > "module chan_echolink.so already exists".
> > >
> > > On Sat, Jan 28, 2017 at 11:46 PM, "David McGough via arm-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > > >
> > > > Hi Max and Everyone,
> > > >
> > > > Doug and I found and resolved this issue with echolink tonight. This
> > was
> > > > a long-standing bug that dates back to the ACID days, which would cause
> > > > the echolink module to fail to load when Asterisk starts.
> > > >
> > > > To resolve this bug in version 1.5, please run the system update menu
> > > > item ("1 - Perform a System UPDATE") from the Admin Menu. Once the
> > update
> > > > is complete, Asterisk will automatically restart. No reboot should be
> > > > needed.
> > > >
> > > > Please give it a try-
> > > >
> > > > 73, David KB4FXC
> > > >
> > > >
> > > >
> > > > On Sat, 28 Jan 2017, "Max via arm-allstar" wrote:
> > > >
> > > > > I just checked modules.conf and the "noload=chan_echolink.so" line
> > has
> > > a
> > > > > semicolon ; in front of it.  However, the echolink.so module isn't
> > > > > loading.  I can manually load it from CLI, but it is not loading on
> > > > bootup.
> > > > >
> > > > > On Sat, Jan 28, 2017 at 4:58 PM, "Steve Agee via arm-allstar" <
> > > > > arm-allstar at hamvoip.org> wrote:
> > > > >
> > > > > > enable the Echolink Channel Driver in /etc/asterisk/modules.conf
> > > > > >
> > > > > > N5ZUA
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 1/28/2017 3:54 PM, "Max via arm-allstar" wrote:
> > > > > >
> > > > > >> Echolink does not appear to be loading when V1.5 boots.  After
> > > > booting I
> > > > > >> can go into CLI client and issue an echolink dbdump and get
> > nothing.
> > > > > >> However, when I load the Echolink module from CLI using the
> > "module
> > > > load
> > > > > >> chan_echolink.so" command then Echolink loads and the echolink
> > > dbdump
> > > > > >> returns the usual long list of Echolink nodes.
> > > > > >>
> > > > > >> What loads Echolink?  Where might I look?
> > > > > >> _______________________________________________
> > > > > >>
> > > > > >> 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
> > > > > >
> > > > > _______________________________________________
> > > > >
> > > > > 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
> > > >
> > > _______________________________________________
> > >
> > > 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
> >
> _______________________________________________
> 
> 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
>