[App_rpt-users] Endless telemetry output with chan_echolink

[Simon Kofler]

Thanks for the replies!

Currently we have telemdefault set to 0, because otherwise the repeater
causes problems with these 5 minutes long telemetry transmissions..

The eannmode is set to 2 (announce only the call of the EL station) and
the echolinkdefault to 0 (echolink stations should not hear telemetry).
Simply disabling telemetry output does not resolve the problem for me,
because we would like to keep telemetry output enabled, in order to get
some feedback when you type DTMF numbers to connect to an Echolink
station (so that the users could know, if the station actually was
connected or not).

I also tried to enable the "timed telemetry output" by setting
telemdefault=2, but it does not help against this issue with multiple
connect attempts.

So the actual problem is not how to disable telemetry output completely,
but how to get rid of these repeated telemetry transmissions caused by
multiple connect attempts by one single Echolink station


Thanks and 73s
Simon, IN3FQQ

Am 16.07.2015 um 16:09 schrieb Doug Crompton:
> http://ohnosec.org/drupal/node/107
>
> I think that will answer your question.
>
>
> *73 Doug
> WA3DSP
> http://www.crompton.com/hamradio*
>
>
> > Date: Thu, 16 Jul 2015 13:59:32 +0200
> > From: simko1994 at gmail.com
> > To: app_rpt-users at ohnosec.org
> > Subject: [App_rpt-users] Endless telemetry output with chan_echolink
> >
> > Hi all,
> > we are operating a bunch of Allstar/app_rpt nodes here in South Tyrol,
> > and they are all working perfectly!
> > A couple of weeks ago we decided to switch one of our old 2M echolink
> > nodes to app_rpt with chan_echolink.
> >
> > So far so good, seems to work - but - here comes the problem: in certain
> > cases (I think it is when users connect via Echolink App over a relay
> > connection) in the asterisk cli you can see, that there are 30 and more
> > echolink connections being accepted by the system. And in that case, the
> > telemetry output starts for all these connections - so the node keeps
> > sending out telemetry "node x connected to node y" for about 5 minutes
> > or even longer.
> >
> > Is there anyone having the same problem? I have no idea how to resolve
> > this issue
> >
> > Best regards
> > Simon, IN3FQQ
> > _______________________________________________
> > App_rpt-users mailing list
> > App_rpt-users at ohnosec.org
> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> >
> > To unsubscribe from this list please visit
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll
> down to the bottom of the page. Enter your email address and press the
> "Unsubscribe or edit options button"
> > You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message
> to the list detailing the problem.
> >

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20150717/989d9ad8/attachment.html>