Hytera Repeater

Here is a link to all you wanted to know about Hytera. Some quick points: Hytera is the parent to HYT but NOT TYT. Hytera prides itself on being the world leader in DMR Tier II and III standards based systems. Worldwide it is only second to Motorola in the public safety market. https://en.wikipedia.org/wiki/Hytera

Hytera Model Breakdown

Hytera distinguishes its models by the use of letters and numbers, typically in a LL-NNN format, which is explained below. X is used as a null placeholder for the model breakout.

Letters

LX: Radio Type

• R: Repeater
• M: Mobile
• P: Portable

XL: Radio Capability

• D: Digital

Numbers

#XX: Class of equipment

• 6: Medium Tier – Feature Limited
• 9: High Tier – Feature Rich

X#X: Interface Type

• 2: Power Switch, Programming Software, or Remote Software Access (XNMS) (Wall Mount, Shore Power ready, 25 Watt Continuous Duty)
• 6: Power, Numeric Display, Channel, Speaker/Microphone with Volume (Backpack, Battery [10 hour] Powered, IP67 Rating, 10 Watt Continuous Duty)
• 8: Full Menu, Volume, Full Display (Communications Site 19″ rack mount repeater, Site Battery Power only, 50 Watt Continuous Duty)

XX#: Country Code

• 0: China
• 2: North America / Oceania
• 5: EMEA / UK / Europe
• 6: South & Latin America
• 8: Asia

Tested equipment

Repeater models

• Hytera RD-622
• Hytera RD-625
• Hytera RD-962
• Hytera RD-965
• Hytera RD-982
• Hytera RD-982S
• Hytera RD-985
• Hytera RD-985S

Firmwares

• 6.00
• 6.05
• 7.00
• 7.06
• 8.00
• 8.05

Configuration guide

Configuration of Hytera Repeater IP Multi-Site Connect:

Manual Set DNS On/Off: checked
DNS Server IP: 8.8.8.8 (for example)
Repeater Type: IP Multi-Site Slave
Jitter Buffer Length: 8
Master UDP-Port: 50000
IP Multi-Site Networking UDP-Port: 50000
IP Multi-Site Service: checked
IP Multi-Site Service UDP Port: 50001
Remote RDAC: checked
Remote RDAC UDP-Port: 50002
Master Domain On/Off: checked
Domain Names: master.dmrnet.org

Issues with connectivity

Authentication

Typically the Hytera repeater has issues with an empty Network Authentication Key field. When you clear the password, it is still sending encrypted connection requests to the server. To solve this problem, you need to fill some text into the password field and upload the codeplug into the repeater, then clear the password and upload the codeplug again.

NAT traversal

BrandMeister has a NAT traversal mechanism for Hytera repeaters. If you have experience with network DMR+ you need to switch off all existing rules of port forwarding.

Specific cases

To avoid problems with strong NAT or multiple repeaters behind a single IP, a special tool called TellusAgent was created. TellusAgent is a simple daemon that can run on very cheap hardware such as a Raspberry Pi and act as a proxy server for a repeater. TellusAgent supports single port IPv4/IPv6 connection on the uplink side and can be run multiple times on a single host inside your intranet.

TellusAgent should be run as many times as you have repeaters connected (one instance proxies a single repeater only)

Arguments:

• ––connect-port <local port for Master service>
• ––control-port <local port for RDAC service>
• ––media-port <local port for DMR service>
• ––server-address <domain name of BrandMeister DMR Server>
• ––server-port <service port of BrandMeister DMR Server>
• ––service-mode <set of bits>
  • bit 0 – print to standard output
  • bit 1 – print to system log
  • bit 2 – run as daemon

Source code of TellusAgent: https://code.brandmeister.network/r3abm/TellusAgent

Unexpected VSWR alarm

With the latest firmware (A8) there seems to be some bug with false VSWR alarms. Uncheck the forward power / VSWR alarm options to get rid of those annoying messages until they are fixed in some later release.

Wrong frequency on Dashboard or other strange behaviour

After changing the frequency on a Hytera RD625, the BM dashboard still shows the original frequency, not the actual one. The repeater otherwise operates without problems. Looking into the logs, BM is seeing that the master sends the wrong frequency (still the original one before the change). The following will not help: reboot, power OFF / ON, change of channel.

The solution was to take a CPS file from another repeater, modify it and apply it to the RD625 in question. The probable cause of this problem was the upgrade from version 7.0.x to 7.6.x — that upgrade should convert the repeater’s codeplug to the newer CPS and it probably was not successful.

To connect your DMR Repeater to our network, kindly contact us at for linking details.