Agreed with you Ken, I don't like using Software TOT. I had a couple of mishaps with software freezing up and keying the transmitter continuously... My general rule is to have a hardware time set hard at 3.5m with software TOT begin 3m. Paul _______________________________ Paul Agamata Sysman@Xceptions.COM ________________________________________ From: app_rpt-users-bounces@ohnosec.org [app_rpt-users-bounces@ohnosec.org] On Behalf Of Ken [ke2n@cs.com] Sent: Monday, September 05, 2011 4:00 PM To: 'app_rpt mailing list' Subject: Re: [App_rpt-users] Found one of my nodes "stuck" this morning Hmmmm – interesting. Of course RF could do it but - I tested it here just now – the TOT does not work on the “remote command” BTW: For an unoccupied/remote site its recommended to have an external hardware TOT … there is a schematic somewhere …. Ken From: Ken [mailto:ke2n@cs.com] Sent: Monday, September 05, 2011 12:43 PM To: 'Lu Vencl' Subject: RE: [App_rpt-users] Found one of my nodes "stuck" this morning (assuming the URI was in fact updating/working … that is, the green light is flashing) If your time out timer is active, this should never happen. The time out timer can be de-activated with an instruction though … I use that when I play back bulletins. The same script that de=activates it, turns it back on again after a while. Ken From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Lu Vencl Sent: Monday, September 05, 2011 8:00 AM To: 'app_rpt list' Subject: [App_rpt-users] Found one of my nodes "stuck" this morning All, Just found one of my nodes “stuck” sending out continuous transmission. No audio coming in but I can IAXRPT to it and TX outbound.. Is this a known issue? This is the first time this has happened to one of my nodes. A simple asterisk restart fixed it, but before I did I collected a few things.. Note : The node that had the issue was 27875.. I tried connecting various nodes to it and all had the same issue.. Continuous key up on the network. AKEWORTH*CLI>