[App_rpt-users] TX Timeout

Wed Jun 7 14:27:51 UTC 2017

I am using a smartphone to access my node so that I can listen to  the radio
channel, and when required,  transmit on the channel. 

 All is well, but I want to implement a timeout so that if I put the node
into transmit mode from my smartphone  and do not return it to receive, the
transmitter will turn off, after say, 30 seconds. I am using the default IAX
configuration for the smartphone.

The tx_timeout parameter makes the transmitter turn off at the required time
as expected.  But when a radio user subsequently transmits on the channel
and then goes back to receive, the node keys the transmitter again and
continues to send audio from the smartphone on the channel. It is as if the
smartphone PTT is still "closed" and so the timeout timer resets itself and
waits another 30 seconds before switching off again.  

So I guess I need a way to disconnect the smartphone after x seconds of PTT
from it ? 

Google is failing me on this one and I'd be grateful for any help.

Thanks

Bernie
GM4WZG

> -----Original Message-----
> From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-
> bounces at ohnosec.org] On Behalf Of app_rpt-users-request at ohnosec.org
> Sent: 03 December 2016 17:00
> To: app_rpt-users at ohnosec.org
> Subject: App_rpt-users Digest, Vol 94, Issue 3
> 
> Send App_rpt-users mailing list submissions to
> 	app_rpt-users at ohnosec.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> or, via email, send a message with subject or body 'help' to
> 	app_rpt-users-request at ohnosec.org
> 
> You can reach the person managing the list at
> 	app_rpt-users-owner at ohnosec.org
> 
> When replying, please edit your Subject line so it is more specific than
"Re:
> Contents of App_rpt-users digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: Podcast Server (Danny)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 2 Dec 2016 19:03:17 +0200
> From: Danny <mynixmail at gmail.com>
> To: app_rpt-users at ohnosec.org
> Subject: Re: [App_rpt-users] Podcast Server
> Message-ID: <20161202170316.GA3444 at fever.havannah.local>
> Content-Type: text/plain; charset=us-ascii
> 
> >On Dec 02 16, Eric Guth :
> >
> > Dear Danny,
> >
> > This is very clever.  Thanks for including my podcast, QSO Today, in
your
> Allstar jukebox of podcasts.
> >
> > 73,
> >
> > Eric Guth
> > 4Z1UG
> > Allstar: 28422
> > QSO Today
> >
> 
> Hi Eric,
> 
> It is only a pleasure. I have been listening to your podcast for so long
and I
> thought it would be befitting to repay you and all the others that have
> podcasts in such a manner.
> 
> Would you believe me if I told you the same evening I advertised "Play
> Something" on this list we experienced heavy thunderstorms which forced
> me to shut down the whole system ... lol ...
> 
> But at least I got to test my skills at unplugging everything within a
flash. I
> think I broke my own record ... less than 4 minutes to pull the plug and
> disconnect all feedlines ...
> 
> However, on a slightly different note ... please guys, if you register
with a
> mistyped callsign contact me immediately in order for me to rectify it.
Too
> many hams blamed the system, but when I checked the database and their
> original registration e-mail, they mistyped/misspelled their own callsigns
> and/or e-mail address.
> 
> Some of you asked me to give a little more detail, so here goes.
> 
> "Play Something" does exactly what it's name says, it "Plays Something".
You
> don't know what you are going to get. But I guarantee you will not hear
the
> same podcast played more than once in 3 months or more (except for ARRL
> news). The algorithm I have developed will prevent this from happening.
> Podcasts are not randomly selected, but rather in a fashion where you will
be
> able to follow a certain podcast provider from his first podcast to his
last
> podcast in a sequential order. Also, you will not hear the same podcaster
> twice in a row.
> 
> "Play Something" observes time-outs. It transmits for 150 seconds, then
> unkeys for 10 seconds. I think 10 seconds should be enough for anyone to
> squeeze through a DTMF code ... ;) ...
> 
> Oh yes ... one important thing ... YOU NEED TO CONNECT TO MY NODE to
> listen ...
> people send me mails telling me "Play Something" is not working but they
> never even connected ... ;) ...
> 
> "Play Something" is for EVERYONE and ANYONE for FREE (for as long as
> possible).
> I have no problem if you park your node permanently at my node whilst you
> are just listening ... that's just fine by me ...
> 
> I am open to suggestions ... and if you have a podcaster you would like to
add
> you are more than welcome to make a suggestion
> 
> Thank you
> 
> Danny
> ZS6XOX
> 73's
> 
> AllStar node 44081
> EchoLink ZS6XOX-R
> 
> zs6xox at gmail.com
> 
> (p.s: Thank you for listening ...)
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> 
> 
> End of App_rpt-users Digest, Vol 94, Issue 3
> ********************************************