Tom, I do not have the itxctcss = line anywhere in my rpt.conf file. Where in the file should I add it? On Wed, Aug 9, 2017 at 11:28 AM, Tom Hayward <tom@tomh.us> wrote:
On Wed, Aug 9, 2017 at 8:12 AM, Michael "Lee" Lockwood <michael@lockwood.us.com> wrote:
So, if I key the repeater using 146.2, it broadcasts out using 146.2 and other radios hear audio just fine. But, as soon as I release PTT on the mobile/portable radio, the squelch tail is broadcast using 151.4, not 146.2. This results in the users programmed with 146.2 not hearing the courtesy tone or squelch tail.
Just for comparison... Around here, this behavior is considered the "proper" way to build a repeater. Tone is not encoded during the courtesy tone or tail so that these are muted at the receiver. Many people don't like listening to the courtesy tone or squelch crash, especially when scanning. It is also essential if the repeater output is being used as the input for an RF link, because you don't want courtesy tones going over the link--the would result in multiple courtesy tones on the remote repeater.
If I was listening to your repeater, I would prefer no tone on the courtesy tone and tail, so that my scanner would not hang on dead air.
There have been some other threads about this lately. We found that the itxctcss parameter in rpt.conf controls this behavior (although community repeater mode may override it). Check that itxctcss = 0 for the behavior you want.
Tom KD7LXL _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.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.
-- *Michael "Lee" Lockwood* michael@lockwood.us.com