rdunajewski

Hi Bob, The main part is the /etc/asterisk directory which has all the config files. As long as you overwrite the ASL ones with the myGMRS ones you should be good to go. There are a couple of extra services that run which would need to be installed under the VM to have the full benefit. One is for adding your node to Node Manager (web-based control of linking commands) and the other is a script that runs every 10 minutes to update your local list of nodes which is basically your whitelist of other nodes that you will allow to connect to you. I can help you set that up once you're ready, we can do a TeamViewer session and I'll show you the steps -- it should take less than 10 minutes.

They are selling modified Part 90 Baofeng radios (poor quality ones at that) as the simplex transmitter. That's in violation of the Part 95 certification requirements, for one. I also don't know the legality of holding bingo over the air, which it looks like they removed mention of on the website. I don't recall if they were playing for a cash prize or if it was just "for fun" but that brings interstate gambling rules into question.

Editor's note, the linked site runs a network that runs against FCC rules. Furthermore, they have been contacting our network users to try to bring them over to their network, sometimes by offering help and logging into their node and switching them over. I strongly recommend you steer clear of them, and certainly we won't tolerate cross-linking between the two networks as it has caused problems.

PHP 7 is installed on the command line by default but there's no web server (Apache or Nginx) installed by default, but it can certainly be added using apt-get. I know some people have installed Allmon or Supermon on their nodes easily as well. The question is can you tap into the GPIO pins of the URI device while app_rpt is using it, and I'm not sure. However, you can use the app_rpt features to toggle these pins like by DTMF command or by setting a schedule, for example.

You're just not using enough heat sinking. 100% duty cycle or bust!

There's one input tone that I'm aware of, and there's no tone on output. This was done to force everyone to monitor before transmitting since NYC is so RF dense. I haven't tried to use it in many years, so I didn't even know it was operational. There's a note on the listing from 2017 saying it was suspended for interference reasons, but I don't know if that's the latest info. Here's the listing for it: https://mygmrs.com/view?id=2604

I got a small batch of them in, but they all sold out (have one left) in only a few days. I placed a larger order so there will be a bunch more coming in. Don't have an ETA yet. Retevis wasn't even stocking them in their US warehouse yet, so I think I'm the only US dealer for the RT76P at the moment. They sell them on eBay but they're shipping out of China.

I use a Cradlepoint mobile hotspot on Verizon for 2 of my sites. Generally speaking, they're pretty bulletproof. The issue with using mobile Internet is that the cell companies block port forwarding, so you won't be able to accept incoming connections from other nodes or open up SSH access if you want remote access for yourself. However, you can use a VPN server with some fancy routing to get around the limitation, or you can add the Static IP privileges to your Verizon account (costs a one-time $500 and allows unlimited static IPs, I believe). One of my repeaters is using the static IP method, but I don't hold the account so I don't know every detail. It may only apply to business accounts, not sure. I do hear it's one-time and NOT per-IP). The only thing I recommend is that you have a way to reboot the Raspberry Pi remotely (i.e. via DTMF or if a ping to a server fails and a power outlet can be set to reset everything). It's rare, but once in a while I lose the VPN connection to my server and it won't reconnect automatically. Not all of my repeaters are nearby (one is in Florida), so I need backup methods to make sure I can reset everything if the normal connection fails. If you can easily get to your repeater site to fix something, then that's fine.

It's possible there's an issue on that particular hub. It was recently added so I'm not sure if something is up with it. Sometimes if you just power on your node the other nodes haven't had a chance to learn about your node, so when you attempt to connect they will reject you since you're not on the whitelist of registered nodes. Waiting 5-10 minutes at most will solve that issue since they will fetch the list of known repeaters and yours will then be on the list.

They didn't even ask me to pay, they just wanted me gone. Either they were upset they agreed to no rent and wanted to kick me out, or they saw the non-compete clause in the contract with the wireless companies and wanted to clean house. Either way, I ended up scoring a much better site with patience and hunting around. I'm on a 500' tower a few miles away now. There was a company who needed a new site to cover their customers so I found the site and piggy-backed on their combiner. It helps to know people in the industry, so I lucked out there. There were other issues where the person who granted me access to the site was on the board, and got approval from the president of the association, but the whole association didn't vote on it. So I think there was some bad blood between the members and I was the casualty. As far as the install, I had a local radio tech do the install since I live in NJ, and that way everything was done professionally and someone could be on-site with a day's notice to fix anything. We did a minimal install, small antenna, small wall-mount rack out of the way so it didn't bother anyone. He worked with the building maintenance guy to make sure everything was good. I also think the antenna drew the attention of the wireless companies because they figured that condo had contracts to lease the roof space already, so it'd be easier to talk to them than to start from scratch with another building.

Sounds like this was a Midwest net on Saturday, and not the regular regional or national net. That's run by the Midwest GMRS group, so I would mention it to them if there's a problem. I know the Midwest group has some nets throughout the week and the regional net is on Thursdays (whereas all the other regional nets in our network are on Sundays before the national net).

I was able to get free access to the top of a condo in Florida on the beach by mentioning that it would be perfect for emergency use and residents of the building could get a license and use it for free. I eventually lost the site because wireless companies were snooping around and wanting to kick any "competition" out, and the condo association was wondering why I was there rent-free when they had a paying tenant looking to come in. My mistake was not getting a contract or lease agreement with them. If I had that, they would have been able to tell the wireless companies tough, we already have an agreement and you'll have to deal with it. It can be an informal contract, just says why you're there, what you'll pay, and for the longest period of time you can negotiate at a time (so you're not having to renegotiate each year, for example).

You can run a NOAA weather alert from the node, it'll fetch high-priority alerts like tornado warnings and such, and announce them over the air.

I sell them on the store but I don't have any in-hand. I'm testing the waters and shipping them from Retevis directly but was just about to place an order for some stock. Sounds like I should play around with one and provide feedback to them before placing the order!

4G has many bands which vary by carrier. None are in the 400-500 MHz range of course, so it should be okay as long as harmonics don't pose an issue with one of the bands. Even so, that usually wouldn't be catastrophic to 4G as I believe multiple bands may be leveraged concurrently depending on the area.

Unfortunately, no. The database is synchronized with the FCC database so we can't go in and manually enable licenses. The FCC publishes a copy of their DB every week with updates given every day. However, these updates are always at least 1 day behind. Your license was issued yesterday, so it will either be in today's update or tomorrow's. So far, we have not received the Wednesday update.

I imposed this restriction for a few reasons: Depending on the skill level of the person wishing to join the network, it may take a lot of hand-holding to get them set up. Unfortunately a lot of people want something completely plug-and-play and that's impossible when you have different radios being used. If we allowed every individual to purchase a kit and had to spend time helping them get their audio levels right and open up the ports in their router, we'd have to charge way more money just to cover our support time. When you have hundreds of nodes trying to link together, you end up with problems with audio loops, poor audio quality, audio level problems, and too many people connecting and disconnecting during a net. This becomes very disruptive when nodes announce the connect and disconnect events, and this makes the net almost impossible to listen to. It goes against the spirit of GMRS and two-way radio in general. If you want to just sit at home and listen to the network, you don't need to use GMRS as an RF link. You'd be better off using a bluetooth speakerphone to your PC or just listen on your phone. I personally don't believe GMRS is meant as a personal hotspot service. Use the RF to cover a wide area, more than just your house. When it comes to expending the least amount of effort for the most amount of return, the best option is to prioritize high-level repeater systems for joining the network. If we have to spend an hour tuning audio for someone and their repeater covers maybe 50 users, that is much more efficient than having to spend 50 hours of effort to get the same people on the air each with their personal "hotspots". If the goal is to sell as many linking bundles as possible, then we'd want to allow simplex nodes on the network. However the goal is to build a robust network, and we really sell the bundles at-cost so we can easily add more repeaters to the network.

There is no forum access via the app. The Tapatalk app should be able to be used with this forum, however, plus there is a mobile web version of these forums when used on a mobile device.

Hey John, can you PM me the info as well? I had both but I think you've changed PLs over time. You can list the repeater as Member's Only so people know it's private.

Welcome! 1) The Midland radios have the ability to enable the 8 extra channels for repeater use. These will transmit on 467.xxx MHz and receive on 462.xxx MHz, whereas the simplex (direct) channels will transmit and receive on the same 462.xxx MHz frequency. In addition to the frequency a repeater transmits, there is also the CTCSS tone (also known as PL tone) which allows a repeater to selectively repeat transmissions from one group of users when others may be on the same shared frequency. On more advanced radios, you would set up a channel for each repeater in the radio's memory, where they would each be one of the 8 repeater channels (i.e. 462.550 MHz), but the CTCSS tone would vary for each repeater. On the Midlands, you need to manually change the tone to use a different repeater. So in the example above, you'd tune to channel 15R (repeater channel) and set the tone in the menu to whatever the local repeater on Channel 15 (462.550) requires. If you go to a new area where there is another repeater also on 462.550, you would stay on Channel 15 but change the tone to whatever that new repeater uses. 2) A repeater will extend the range a single radios has by many miles, depending on the height of the repeater in elevation. If two radios are nearby but suddenly cannot communicate due to the terrain or distance, a nearby repeater located in a tall spot (a tower, a tall building, or a mountain top) will allow those radios to communicate by retransmitting the signal at higher power and at a higher location. UHF frequencies are almost line-of-sight, where two stations can communicate if there is an unobstructed view between antennas. By putting the repeater antenna high up, it will be able to "see" a much larger area and thus extend the mobile units' coverage over the greater area it can "see" from its height. So a radio with a 1 mile range can suddenly get 15-30 mile range if there is a repeater in a good spot high above the average terrain height by having the repeater retransmit its signal at a higher power and elevation. Repeaters have a limit to their range based on this elevation, as the visual horizon distance changes with regard to height above the ground. Since the Earth is curved (flat-earthers will be disappointed), the further away you go from a station, you begin to curve below the horizon and eventually the Earth itself will block the signal. The only way around that is more height, and that's how satellites can have such wide coverage. They are essentially a repeater at an extreme altitude and thus they have visual line-of-sight to a much, much larger area than a tower on the ground could ever have.

Just a caution to be civil here. This thread has the potential to get political fast, and that's not okay here. For casual listening to the protesters, I have no issue with sharing that information. I do have a problem with using that information for nefarious purposes, however. Just like how it's okay to share information for monitoring police and the military within the confines of the law, but once you try to use it for nefarious purposes that goes out the window and becomes a problem here.

Travel Tone is when a repeater enables 141.3 Hz as an open tone for travelers to use when in the area. For example, you could tune your radio to each GMRS repeater channel with 141.3 as your tone, and the repeaters with a Travel Tone are open for temporary use without permission. Good for when you don't have time to program each repeater along your route. ORI stands for the Open Repeater Initiative which was created by Popular Wireless many years ago. It was a way to indicate a repeater is open for any licensed GMRS operator to use without having to ask the owner's permission. These repeaters you can just jump on and use as long as you follow GMRS rules and use your callsign.

Originally "Handie-Talkie" from the old Motorola terminology for a handheld radio (I believe they were the first to have one that "fit" in your hand, so they coined the term). Now HT is more of just a quick abbreviation for a handheld radio in general, many of us aren't thinking of "Handie-Talkie" unless we're REALLLLLY old.

CCR is a common one for "Cheap Chinese Radio" which includes Baofengs, Wouxuns, and such. I think having a list would be good!

For now, yes. We don't want simplex nodes right now because: 1. It kind of goes against the spirit of radio. If you're using a simplex node to just cover your house to talk over the Internet, you don't really need GMRS to do that. 2. Having one node per person adds a lot of complexity and load to the network. It's a lot more that can go wrong and then you have audio issues, announcements or IDs going off, and people connecting and disconnecting a lot. 3. We (mostly me) don't have the time to hold everyone's hand and set them up with a personal node. There's still a steep learning curve to setting up a node if you've never used Asterisk before, and it requires some comfort with running Linux commands. A lot of people don't have that experience and we just can't spend hours on each person for free setting them up. It's much easier to spend time on a single node that is on a repeater with good coverage so you're potentially linking many people together and not just one at his house. We're more interested in covering as many people as possible with as few nodes as possible to keep the overall quality of the network up and minimize problems. Lately we've started to have some growing pains during the National Net where the nodes aren't all cooperating, and trying to fix things with potentially hundreds of new nodes would just be a nightmare. Zello is one avenue I've explored as a way to tie into the network. Zello is a great app but it has several issues that make it hard to adapt to our network. Zello sends the audio to their central servers, then forwards on to the recipient in a non-realtime manner. This is great for ensuring the message got to the recipient and is fairly clear, but there is latency introduced in sending the audio to the client particularly on a poor connection. The problem is people end up doubling over one another. It's still a possibility but it would probably be a single node that people can choose to connect to, rather than many nodes.