Repeater Linking Information

[WRKC935]

I am getting ready to put a second repeater on the air on 675 with the traveler PL 141.3 on the air.

Thoughts were to tie this into the midwest gmrs system.

This brings up some questions.

 

First is should i have it nailed up as a constant connection or have it switchable.  My thoughts are leave it nailed up so that users that are not aware it's linked or how to operate the links will still

see the benefit of the widened user base.  And of course the traveler channel being linked give anyone requesting help a better chance of getting ahold of someone to at least make a call for them if needed.

 

I have looked at the interface and it's straight forward.  Looks like Allstar which I have.  Assuming this also requires a R-Pi or some SBC,

Has anyone run this on a full computer and if a full computer, has anyone experimented with running it on a VM in a container?

My P25Link R-Pi is actually a VM (natively a R-pi with a Perl application) that works well.

Hoping to continue that trend and virturalize the computer part of this link to save space. 

 

Does anyone see an issue with putting the traveler channel on the link and specifically the midwest link... I am in central Ohio if there is a better system to be linking to I am all ears.

 

Comments and thoughts are welcome here.  If this is a bad idea, let me know.

 

 

[WRAK968]

Ok, bit of info to go over here.

I believe the Midwest GMRS system is a private linked network, and while it is accessible via the network, I would ask the owner of the group for permission before setting up a permanent link to that, or any other per-existing system you do not currently manage.

The Asterisk program always gives you the option of changing what is or is not connected via radio. (Check with Rich just in case I am wrong however I do not believe that can be disabled.) It uses DTMF codes to control the system. I believe the codes can be changed to a custom set-up, however dont hold me on that either. The codes allow the following; (This is a list, the actual codes are different)
1: Disconnect ~ Allows disconnect of normal connected or monitored node
2: Monitor ~ Allows monitoring of a node, will not transmit to said node.
3: Connect ~ Connects to node, allows cross RX/TX

4: Permanent Disconnect ~ Disconnects Permanent connected or monitored nodes
5: Permanent Monitor ~ Permanently monitors selected node

6: Permanent Connect ~ Permanently connects nodes

7: Status ~ Announces connection status

 

I cannot give any input about how a VM may affect the network. If you know how to properly set it up I would presume that it could work, however I have no idea how to do it so take that as it is.