[arm-allstar] Echolink Connection Telemetry

[Sean McCarthy]

Cool, just wanted to make sure it wasn't something on my config.

I do notice, when I watch the asterisk debug info at level 4 or above, I
see the calls accurately 100%

Wouldn't this tell us the proper information is, in fact, reaching asterisk?

Thanks,
Sean

On Sun, May 28, 2017 at 7:13 AM, "Paul Aidukas via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Sean,
>
> SuperMon relies on the Asterisk "echolink" command to look these up.  It
> appears that the Echolink Servers are not always providing accurate
> callsign results to Asterisk.  Something to do with clients using relay and
> proxy servers.  I have noticed this for a few years and cannot come up with
> a perfect fix on the AllStar side.  Clients not using relay or proxy
> servers are always reporting correct and accurate.
>
> Maybe Doug and Dave can look closely at the Echolink code for AllStar and
> find a fix.
>
> Paul / KN2R
>
>
> On Sat, May 27, 2017 at 11:28 PM, "Sean McCarthy via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Here is a few entries from my connection log:
> >
> > Sat May 27 19:00:44 EDT 2017 == 43732 Connected EchoLink 3335524 ==>
> > KE7FHN EchoLink 335524 (107.23.146.139)
> > Sat May 27 19:01:30 EDT 2017 == 43732 Disconnected EchoLink 3335524
> > ==> No-Info... EchoLink 335524
> > Sat May 27 19:01:39 EDT 2017 == 43732 Connected EchoLink 3053351 ==>
> > No-Info... EchoLink 53351
> > Sat May 27 19:09:20 EDT 2017 == 43732 Disconnected EchoLink 3053351
> > ==> No-Info... EchoLink 53351
> > Sat May 27 19:36:09 EDT 2017 == 43732 Connected EchoLink 3053351 ==>
> > No-Info... EchoLink 53351
> > Sat May 27 19:59:26 EDT 2017 == 43732 Disconnected EchoLink 3053351
> > ==> No-Info... EchoLink 53351
> > Sat May 27 20:16:14 EDT 2017 == 43732 Connected EchoLink 3765887 ==>
> > No-Info... EchoLink 765887
> > Sat May 27 20:17:42 EDT 2017 == 43732 Disconnected EchoLink 3765887
> > ==> No-Info... EchoLink 765887
> > Sat May 27 20:20:54 EDT 2017 == 43732 Connected EchoLink 3111276 ==>
> > No-Info... EchoLink 111276
> > Sat May 27 20:22:20 EDT 2017 == 43732 Disconnected EchoLink 3111276
> > ==> No-Info... EchoLink 111276
> > Sat May 27 21:31:39 EDT 2017 == 43732 Connected EchoLink 3501912 ==>
> > No-Info... EchoLink 501912
> > Sat May 27 21:31:58 EDT 2017 == 43732 Disconnected EchoLink 3501912
> > ==> No-Info... EchoLink 501912
> > Sat May 27 21:35:23 EDT 2017 == 43732 Connected EchoLink 3685739 ==>
> > RV9CN EchoLink 685739 (137.226.114.33)
> > Sat May 27 21:35:28 EDT 2017 == 43732 Disconnected EchoLink 3685739
> > ==> RV9CN EchoLink 685739 (137.226.114.33)
> >
> > The 2 that appear correct, KE7FHN and RV9CN were me.
> >
> > Debugging at the CLI shows the correct call, so I know I'm receiving the
> > correct information
> >
> > -- new CALL=WX8L,ip=107.23.146.140,name=        Sean
> >     -- Executing [43732 at radio-secure:1] Rpt("echolink/el0-8", "43732")
> in
> > new stack
> >   == Spawn extension (radio-secure, 43732, 1) exited KEEPALIVE on
> > 'echolink/el0-8'
> >
> > And pointers would be appreciated...
> >
> >
> > On Sat, May 27, 2017 at 12:11 PM, Sean McCarthy <smccarthy61 at gmail.com>
> > wrote:
> >
> > > Hello all,
> > >
> > > I have echolinking working well on my node, however, the incoming
> > > connections are either completely wrong or show "no-info" and do not
> > > announce on the node.
> > >
> > > Anyone know what I might have done wrong?
> > >
> > > Thanks,
> > > Sean
> > >
> > _______________________________________________
> >
> > 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
>