Long ago we had a similar situation and did not want the link ID to be heard on the output of the repeater.  Our solution was to have the link ID at 2125 hz sine wave and then have a very sharp notch filter on the repeater receiver so that it would not pass the received 2125 hz sine wave ID.  If I remember correctly we used a quad op amp notch filter and it was only a few hz wide.  It required an accurate CDID tone and clean keying. There was no noticeable effect on voice audio. We had the link ID on each and every transmission and on short transmissions the link would abort the ID on unkey, unless it had been 10 minutes since a successful complete ID.
This was long before we went with allstarlink but I think the concept might be usable  for your project.  
Chuck


On Fri, Jul 4, 2014 at 7:12 AM, Jon Rorke <jrorke@cogeco.ca> wrote:
This should be fairly strait forward if the repeater is set up to pass the CTCSS tone only when keyed.

All you need to do is program your link radio like a mobile to work the repeater with CTCSS on TX and RX.

Then set up your Allstar node to be a simplex node. Use duplex=0 in the rpt.conf file and the usbradio.conf  files.

When using the duplex=0 setting in the rpt.conf file makes the node a simplex node but has no telemetry, nop tail no peeps and so on. No CW IDs will come out except when someone is talking on the node.

Jon VA3RQ



On 7/3/2014 10:50 AM, Skyler F wrote:
I know this is a major problem that has showed up, and I would like to know if anybody knows how to fix it for the best operation.

Thanks for any help, I am a newbie at the software and CentOS ACID is the first time I have used command line.

Background
-There is a remote repeater on a mountain west of me
-No internet exists at the site
-I can't add any other link in because of antenna expenses
-The Rocky Mountain Radio League has held approval for an RF link to the repeater using the input frequency of the repeater

What they will do
-Because of the loonngg hang time, they will disable the TX CTCSS right away after the transmission is done.
-They will NOT TX CTCSS on their CW ID so I don't have to hear that in the node.

What I am expected to do
-Only CW ID when a remote person is transmitting, so when they are coming in from the internet to my node, only ID over their transmission (yes I know the morse will be playing at the same time as the talking)
-NO random ID's coming up 10 mins after the conversation is done. I don't want my node to just come up at random times and ID

Any suggestions, any previous attempts for a link like that?

Thanks so much, and any help would be greatly appreciated. The RMRL wants to start getting this along so I would really like some help.

73's

Skyler KDØWHB

--
Skyler Fennell
KDØWHB


_______________________________________________
App_rpt-users mailing list
App_rpt-users@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.


_______________________________________________
App_rpt-users mailing list
App_rpt-users@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.