[arm-allstar] Pulse-Back & Building a Repeater

[R. Wayne]

I don’t know if I should be sending this here or to arm-app_rpt.

Our repeater is temporarily using a remote base to talk up to our machine. We have Internet there but have not configured it yet. Our emote base is sending pulse-backs and I don’t know how to stop it. It is also sending our CWID from our MSF using its internal controller. I cannot turn it off without violating part 97. AFAIK the MSF doesn’t allow me to tell it to wait until the hang time drops to ID. I am using a RTCM on the remote base and I can turn off CWID on the repeater and let the RTCM send the CWID. But we’re back to pulse-backs. How do I deal with them?

Next, we want to drop our MSF’s and build repeaters for our three sites using Motorola CDM 750’s and their 20KHz channel spacing is more favorable to us. The MSF’s are 30KHz channel spacing with a 2MHz wide front-end. I can use a RTCM as the controller on each repeater. Or I’d rather use our external link controllers. We have RF links that come in as well. I know that this is a lot to ask but what is the best way to do this? I am assuming that the repeater goes on port 1. The RTCM will go on port 2 or I can build a BBB and use a USB FOB. Port 3 would be for an external RF link that comes in. Our Allstar server is setup using .0320 and id bridged to another RoIP service. It also has Echolink but it is not active. Our link controller is fully addressable with a preamble that should allow me to avoid DTMF issues. I don’t know abut users in the repeater trying to control it or autopatch, which we have. Is this doable or have I misunderstood?

I am grateful to this group for getting me this far. I look forward to get Allmon setup, announcements, etc., although our link controller has 250 DVR tracks.

Thank you again in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150628/8a975e57/attachment-0001.html>