[arm-allstar] tones on transmission

REDBUTTON_CTRL jrorke at cogeco.ca
Sat Sep 12 07:26:59 EST 2015 

I think whats going on here is there are stations using a simplex 
channel not intending to use the Allstar node. However the node is 
hearing one or both of the stations and keying up with its courtesy tone.

Perhaps a simple solution here is to put the node on PL (CTCSS). So if 
the simplex stations are not using tone, they wont bring up the node.
If they intend to use the node then use PL on transmit to access the node.


Jon VA3RQ

On 9/10/2015 11:48 PM, Doug Crompton wrote:
> I thought I explained it but either I am not understanding what you 
> are doing or you don't have an understanding of how Allstar works.
>
> When you setup a simplex node - connect allstar to a radio you are in 
> effect putting Allstar on that frequency. By default Allstar responds 
> with a courtesy tone to tell users on that frequency that Allstar is 
> there and active. It does not transmit over anyone only when they stop 
> transmitting like you would hear on a repeater. If it actually does 
> transmit over someone then your COS is probably not working properly. 
> The polarity might be reversed. To test -
>
> From the L:inux prompt go into the Asterisk client -
>
> asterisk -rvvv
>
> Key and hold the PTT of your radio that talks to your node radio. You 
> should not see anything yet. Unkey the radio. You should see the 
> hungup message in the display. If you are seeing the hungup message on 
> key down then COS polarity is reversed. If you are not see it at all 
> either way then COS is not working.
>
> To reverse COS polarity edit  /etc/asterisk/simpleusb.conf
>
> Look for the 'carrierfrom' line
>
> It can either be  usb for positive going on signal or usbinvert for 
> negative going (around 0 volts) on signal
>
> If this does not answer your question unless you explain exactly how 
> you have things hooked up that is the best I can do for an explanation.
>
> *73 Doug
> WA3DSP
> http://www.crompton.com/hamradio*
>
>
> ------------------------------------------------------------------------
> Date: Thu, 10 Sep 2015 22:22:50 -0400
> From: tukosei at gmail.com
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] tones on transmission
>
> I don't understand why the node would key the radio up over a couple 
> of people having a conversation, say HT to HT (locally) other than to 
> annoy the parties that have no idea there is a 3rd radio out there 
> TXing a tone over the start of their conversation. No one is connected 
> to the AllStar node, so why would it key up at all?
>
>
> On Sep 10, 2015 9:51 PM, "Doug Crompton" <doug at crompton.com 
> <mailto:doug at crompton.com>> wrote:
>
>     The courtesy tone goes out to any local device connected to the
>     node. So it would go out over the connected radio. For simplex
>     operation when COS drops indicating an RF station stopped
>     transmitting there is a delay (settable) and then the node TX keys
>     and the courtesy tone is sent. For full duplex at the end of an RF
>     transmission when COS drops the repeater stays keyed for the delay
>     period and then the courtesy tone is sent.
>
>     I think what you were hearing was normal. Courtesy tone is meant
>     to indicate end of transmission and the other party can talk. If
>     you are talking over it then you are keying up too fast.
>
>     *73 Doug
>     WA3DSP
>     http://www.crompton.com/hamradio*
>
>
>     ------------------------------------------------------------------------
>     Date: Thu, 10 Sep 2015 20:47:54 -0400
>     From: tukosei at gmail.com <mailto:tukosei at gmail.com>
>     To: arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>     Subject: Re: [arm-allstar] tones on transmission
>
>     The issue I was having was no one was using/ logged into or using
>     the node. The conversation was between 2 parties, radio to radio
>     (rf only) and the system was keying over the start of their
>     conversation.
>     I changed the setting and it seems to be gone.
>     Thanks!
>     Ryan
>
>     On Thu, Sep 10, 2015 at 5:48 PM, Doug Crompton <doug at crompton.com
>     <mailto:doug at crompton.com>> wrote:
>
>         In the node stanza in rpt.conf that you want to eliminate
>         courtesy tone add -
>
>         *nounkeyct=1
>
>         *Note that courtesy tones are there for two reasons. One is to
>         force users to wait until after the tone to speak. This
>         eliminates cutoff of audio due to delays in the system. you
>         should always wait 2-3 seconds to transmit. Fast keying is not
>         a good thing in Allstar. It also does not allow others to
>         break in. The other reason especially on simplex odes is to
>         show that the RX actually heard you. On repeaters Allstar is
>         often used as the controller and thus the courtesy tone would
>         be for the repeater. Most repeaters have courtesy tones.
>
>         *73 Doug
>         WA3DSP
>         http://www.crompton.com/hamradio*
>
>
>         ------------------------------------------------------------------------
>         Date: Thu, 10 Sep 2015 16:29:24 -0400
>         From: tukosei at gmail.com <mailto:tukosei at gmail.com>
>         To: arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>         Subject: [arm-allstar] tones on transmission
>
>
>         I am trying to eliminate a "courtesy tone" on my setup. It
>         seems that each time the system hears a radio transmission; it
>         has to transmit a tone about 2 seconds after the end of the
>         reception. Sometimes, it will transmit over the person trying
>         to talk (RF) back. This occurs when there is no one connected
>         to the node.
>         My setup is using a Pi2 > USB sound card > HT radio.
>         I tried adjusting some of the .conf files but haven't found
>         the setting yet.
>
>
>         Ryan
>         KK4OSG
>
>         _______________________________________________ arm-allstar
>         mailing list arm-allstar at hamvoip.org
>         <mailto:arm-allstar at hamvoip.org>
>         http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>         Visit the BBB and RPi2 web page - http://hamvoip.org
>
>         _______________________________________________
>
>         arm-allstar mailing list
>         arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>         http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
>         Visit the BBB and RPi2 web page - http://hamvoip.org
>
>
>
>     _______________________________________________ arm-allstar
>     mailing list arm-allstar at hamvoip.org
>     <mailto:arm-allstar at hamvoip.org>
>     http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>     Visit the BBB and RPi2 web page - http://hamvoip.org
>
>     _______________________________________________
>
>     arm-allstar mailing list
>     arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>     http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
>     Visit the BBB and RPi2 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 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 web page - http://hamvoip.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150912/f4b00ee0/attachment.html>

More information about the arm-allstar mailing list