DMR Network Inclusion

Unified Radios includes both DMR/IP and DMR/RF networks in its directories. Initial listings are based on publicly available data, but we welcome direct cooperation with additional networks.

We believe collaboration benefits the entire HAM community by increasing visibility, adoption, and ease of use.

What We Consider a Network

We define a network as a group of repeaters or servers under shared administration, typically evidenced by coordinated talkgroups. Individual repeaters should not be submitted as their own networks; some level of scale in users or infrastructure is expected.

Requirements for Inclusion

1. Network Name: The name you want displayed in our directory.
2. Public API Access: A reliable, unrestricted API (no attribution or commercial use restrictions). We can assist if you don’t yet have one.
3. Talkgroup Information: An API endpoint listing talkgroup ID, description, and optional extended description.
4. Unified Radios Talkgroup: While optional, a talkgroup on ID 3161 is requested for community and testing purposes across networks.

Additional Requirements for DMR/IP Networks

• A list of connectable servers including:
• Unique server description or number
• Hostname or IP address (please ensure DNS/PTR resolution where possible)
• Port
• Password

Additional Requirements for DMR/RF Networks

• Repeater information must include:
• RadioID (callsigns are not unique to a single repeater in the US)
• Callsign
• RX frequency
• TX frequency or offset
• Color code
• Timeslot 1 static talkgroups
• Timeslot 2 static talkgroups
• Strongly encouraged: Latitude and longitude
• Optional: City, state, country (we can geocode if coordinates are not available)
• Optional: Description, allowed dynamic talkgroups per timeslot

If your network is ready to participate or you need assistance with API development, please reach out at help at unifiedradios dot com. We’re here to help make digital radio more accessible, reliable, and community-driven.